{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T15:48:56.209Z",
  "record_id": "VXI-EXT-PROCUREMENT-STRIPE-DESTINATION-APPLICATION-FEE-REFUND-ALLOCATION-01-v1",
  "record_kind": "external_reference",
  "title": "Stripe destination refunds and application fees",
  "system": "Stripe",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does refunding a Stripe destination charge automatically refund the platform application fee?",
  "near_questions": [
    "Does Stripe retain an application fee when a destination charge is refunded?",
    "What does refund_application_fee change?",
    "How is the application fee handled for a partial destination refund?",
    "Which records reconcile customer refund, transfer reversal and fee refund?"
  ],
  "supported_claims": [
    {
      "claim": "For a destination charge, Stripe says the platform keeps the application fee by default when refunding the charge. refund_application_fee can return it, and that path also requires reversing the transfer. A full refund returns the full fee on that path; a partial refund returns a proportional fee. Customer refund, transfer reversal and application-fee refund are distinct records.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Refunding a charge automatically restoring every participant balance",
    "The chosen flags, separate fee refunds and completed money movements require account evidence.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "For a destination charge, Stripe says the platform keeps the application fee by default when refunding the charge. refund_application_fee can return it, and that path also requires reversing the transfer. A full refund returns the full fee on that path; a partial refund returns a proportional fee. Customer refund, transfer reversal and application-fee refund are distinct records.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Create destination charges",
    "source_url": "https://docs.stripe.com/connect/destination-charges?platform=web&ui=stripe-hosted",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-STRIPE-DESTINATION-APPLICATION-FEE-REFUND-ALLOCATION-01-v1",
    "candidate_record_sha256": "801bca141f9c302cc4dc8e9102f7d8d8ddcab001020fcbca065a6e745b96f222",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "For a destination charge, Stripe says the platform keeps the application fee by default when refunding the charge. refund_application_fee can return it, and that path also requires reversing the transfer. A full refund returns the full fee on that path; a partial refund returns a proportional fee. Customer refund, transfer reversal and application-fee refund are distinct records.",
    "required_buyer_context": "Charge refund amount and refund_application_fee setting; Transfer reversal outcome; Application fee and fee-refund records. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-24",
    "claim_to_check": "Does refunding a Stripe destination charge automatically refund the platform application fee?",
    "documented_statement": {
      "status": "documented",
      "statement": "For a destination charge, Stripe says the platform keeps the application fee by default when refunding the charge. refund_application_fee can return it, and that path also requires reversing the transfer. A full refund returns the full fee on that path; a partial refund returns a proportional fee. Customer refund, transfer reversal and application-fee refund are distinct records.",
      "source_ids": [
        "stripe-destination-full"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Reconcile all three allocations before declaring that the platform and recipient balances were restored.",
      "source_ids": [
        "stripe-destination-full"
      ]
    },
    "buyer_evidence_required": [
      "Charge refund amount and refund_application_fee setting",
      "Transfer reversal outcome",
      "Application fee and fee-refund records"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not infer that the platform fee was returned from the customer refund alone."
    },
    "unknowns": "The chosen flags, separate fee refunds and completed money movements require account evidence.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The chosen flags, separate fee refunds and completed money movements require account evidence."
    },
    "evidence_sources": [
      {
        "source_id": "stripe-destination-full",
        "url": "https://docs.stripe.com/connect/destination-charges?platform=web&ui=stripe-hosted",
        "final_url": "https://docs.stripe.com/connect/destination-charges?platform=web&ui=stripe-hosted",
        "status": "cli_success",
        "captured_at_utc": "2026-10-24T15:25:08.519Z",
        "sha256": "fc7437f433677ba0b9b6052ea45de689295937c1a284ee658fbc42a7f49bbff3",
        "bytes": 107051,
        "title": "Create destination charges",
        "hash_basis": "Exact Stripe CLI documentation response bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "capture_method": "stripe docs",
        "cli_exit_code": 0,
        "cli_version": "1.55.1",
        "checked_on": "2026-10-24",
        "capture_status": "cli_success",
        "claim_review_completed": true,
        "version_context": "Rolling Stripe documentation captured through Stripe CLI 1.55.1 on 2026-10-24; the merchant must check the applicable API version and configuration.",
        "reviewed_sections": [
          "Refund application fees",
          "reverse_transfer proportional refunds"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; the buyer must establish applicability and actual outcomes. INDEX does not inspect or control the deployment.",
    "paid_value": {
      "decision_context": "Avoid refund reconciliation gaps between buyer, platform and supplier.",
      "free": "Complete review, sources, practical questions and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "Recheck the documented behavior, product version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Avoid refund reconciliation gaps between buyer, platform and supplier.",
    "refusal_conditions": [
      "Do not infer that the platform fee was returned from the customer refund alone."
    ]
  },
  "niche": {
    "niche_id": "agent-authority-action-evidence",
    "label": "Agent Authority & Action Evidence",
    "classification_id": "payments",
    "classification_label": "Agent Payments, Authority & Transaction Evidence",
    "topic_id": "payments",
    "buyer_intent": "Avoid refund reconciliation gaps between buyer, platform and supplier.",
    "comparison_role": "supplementary_discovery"
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#stripe-destination-application-fee-refund-allocation",
  "machine_readable_record": "/varexis-index/records/stripe-destination-application-fee-refund-allocation.json"
}
