{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-22T21:15:08.873Z",
  "record_id": "VXI-EXT-PROCUREMENT-STRIPE-CONNECT-REFUND-TRANSFER-REVERSAL-SEPARATION-01-v1",
  "record_kind": "external_reference",
  "title": "Stripe Connect: Refunds and separate transfer recovery",
  "system": "Stripe Connect",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does refunding a Stripe separate charge automatically recover money transferred to connected accounts?",
  "near_questions": [
    "Must a Stripe platform reverse transfers after refunding a separate charge?",
    "Does a successful customer refund prove connected-account recovery?",
    "Can a Stripe transfer reversal fail for insufficient available balance?",
    "How should an agent reconcile refunds against multiple connected-account transfers?"
  ],
  "supported_claims": [
    {
      "claim": "With Stripe separate charges and transfers, refunding the charge does not reverse its associated transfers. The platform must reconcile recovery separately, for example through transfer reversals or adjusted later transfers. Reversals have balance or reserve requirements and may fail. A customer refund and recovery from recipients are different outcomes.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Automatic transfer recovery or applicability to every Connect charge model",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "With Stripe separate charges and transfers, refunding the charge does not reverse its associated transfers. The platform must reconcile recovery separately, for example through transfer reversals or adjusted later transfers. Reversals have balance or reserve requirements and may fail. A customer refund and recovery from recipients are different outcomes.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Create separate charges and transfers",
    "source_url": "https://docs.stripe.com/connect/separate-charges-and-transfers?platform=web&integration=custom&ui=elements&api-integration=paymentintents",
    "checked_on": "2026-10-22",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-STRIPE-CONNECT-REFUND-TRANSFER-REVERSAL-SEPARATION-01-v1",
    "candidate_record_sha256": "d6df85650512062d5e505b799e683ecca92595d268a075007177cbb1ed546a18",
    "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": "With Stripe separate charges and transfers, refunding the charge does not reverse its associated transfers. The platform must reconcile recovery separately, for example through transfer reversals or adjusted later transfers. Reversals have balance or reserve requirements and may fail. A customer refund and recovery from recipients are different outcomes.",
    "required_buyer_context": "Charge, refund and linked transfer identities; Reversal outcomes and recipient available balances or reserves; Amounts already recovered through later transfer adjustments. 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-22",
    "claim_to_check": "Does refunding a Stripe separate charge automatically recover money transferred to connected accounts?",
    "documented_statement": {
      "status": "documented",
      "statement": "With Stripe separate charges and transfers, refunding the charge does not reverse its associated transfers. The platform must reconcile recovery separately, for example through transfer reversals or adjusted later transfers. Reversals have balance or reserve requirements and may fail. A customer refund and recovery from recipients are different outcomes.",
      "source_ids": [
        "stripe-transfers"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Recovery accounting needs independent evidence for both the refund and each recipient leg.",
      "source_ids": [
        "stripe-transfers"
      ]
    },
    "buyer_evidence_required": [
      "Charge, refund and linked transfer identities",
      "Reversal outcomes and recipient available balances or reserves",
      "Amounts already recovered through later transfer adjustments"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not mark platform recovery complete solely from the refund or a reversal request."
    },
    "unknowns": "Recipient balances, reversals and actual recovery are unobserved.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Recipient balances, reversals and actual recovery are unobserved."
    },
    "evidence_sources": [
      {
        "source_id": "stripe-transfers",
        "url": "https://docs.stripe.com/connect/separate-charges-and-transfers?platform=web&integration=custom&ui=elements&api-integration=paymentintents",
        "final_url": "https://docs.stripe.com/connect/separate-charges-and-transfers?platform=web&integration=custom&ui=elements&api-integration=paymentintents",
        "title": "Create separate charges and transfers",
        "checked_on": "2026-10-22",
        "captured_at_utc": "2026-10-22T21:07:32.879Z",
        "version_context": "Stripe public documentation retrieved by official CLI 1.55.1 on review date; API v1 unless otherwise stated; no account accessed.",
        "sha256": "f440bea5c7e96720f0765398b7eb02c1056951e5ce73a6148b1ce3c9ea879503",
        "bytes": 153221,
        "hash_basis": "Exact stdout bytes from official Stripe CLI 1.55.1 public docs command; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Refunds",
          "Reverse transfers"
        ],
        "capture_status": "cli_success",
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed.",
        "capture_method": "stripe docs",
        "cli_version": "1.55.1",
        "cli_exit_code": 0
      }
    ],
    "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": "Prevent unreconciled platform losses after marketplace refunds.",
      "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": "Prevent unreconciled platform losses after marketplace refunds.",
    "refusal_conditions": [
      "Do not mark platform recovery complete solely from the refund or a reversal request."
    ]
  },
  "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": "Prevent unreconciled platform losses after marketplace refunds.",
    "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-connect-refund-transfer-reversal-separation",
  "machine_readable_record": "/varexis-index/records/stripe-connect-refund-transfer-reversal-separation.json"
}
