{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T15:48:56.209Z",
  "record_id": "VXI-EXT-PROCUREMENT-STRIPE-TRANSFER-SOURCE-TRANSACTION-FUNDS-AVAILABILITY-01-v1",
  "record_kind": "external_reference",
  "title": "Stripe transfer acceptance and available funds",
  "system": "Stripe",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a successful Stripe transfer request prove that the associated charge funds were already available?",
  "near_questions": [
    "Can Stripe accept a transfer before its source charge funds are available?",
    "What does source_transaction change about transfer timing?",
    "Does Stripe automatically retry a transfer that failed for insufficient balance?",
    "Which evidence separates accepted transfers from available funds?"
  ],
  "supported_claims": [
    {
      "claim": "For separate charges and transfers, a transfer using source_transaction can be accepted before the charge funds become available; Stripe waits for those funds before executing it. Without that linkage, available platform balance constrains transfers, and failed transfers are not automatically retried. Acceptance, funding availability and completed movement must therefore be distinguished.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Transfer acceptance proving bank receipt or immutable settlement",
    "The actual payment-method timing, balance availability and recipient payout were not observed.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "For separate charges and transfers, a transfer using source_transaction can be accepted before the charge funds become available; Stripe waits for those funds before executing it. Without that linkage, available platform balance constrains transfers, and failed transfers are not automatically retried. Acceptance, funding availability and completed movement must therefore be distinguished.",
  "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=checkout&ui=stripe-hosted",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-STRIPE-TRANSFER-SOURCE-TRANSACTION-FUNDS-AVAILABILITY-01-v1",
    "candidate_record_sha256": "1b2dcf2c384a2dec30e00a892ea343264dc13dc62df707ef0ee36a380dd87ed0",
    "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 separate charges and transfers, a transfer using source_transaction can be accepted before the charge funds become available; Stripe waits for those funds before executing it. Without that linkage, available platform balance constrains transfers, and failed transfers are not automatically retried. Acceptance, funding availability and completed movement must therefore be distinguished.",
    "required_buyer_context": "Transfer ID, source_transaction and linked charge; Balance availability and transfer outcome; Existing retry and supplier-delivery reconciliation 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 a successful Stripe transfer request prove that the associated charge funds were already available?",
    "documented_statement": {
      "status": "documented",
      "statement": "For separate charges and transfers, a transfer using source_transaction can be accepted before the charge funds become available; Stripe waits for those funds before executing it. Without that linkage, available platform balance constrains transfers, and failed transfers are not automatically retried. Acceptance, funding availability and completed movement must therefore be distinguished.",
      "source_ids": [
        "stripe-transfers-full"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Reconcile the transfer funding source and resulting balance state before representing the supplier as paid.",
      "source_ids": [
        "stripe-transfers-full"
      ]
    },
    "buyer_evidence_required": [
      "Transfer ID, source_transaction and linked charge",
      "Balance availability and transfer outcome",
      "Existing retry and supplier-delivery reconciliation records"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not treat request acceptance or unrelated platform balance as proof that the intended charge funded the supplier."
    },
    "unknowns": "The actual payment-method timing, balance availability and recipient payout were not observed.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The actual payment-method timing, balance availability and recipient payout were not observed."
    },
    "evidence_sources": [
      {
        "source_id": "stripe-transfers-full",
        "url": "https://docs.stripe.com/connect/separate-charges-and-transfers?platform=web&integration=checkout&ui=stripe-hosted",
        "final_url": "https://docs.stripe.com/connect/separate-charges-and-transfers?platform=web&integration=checkout&ui=stripe-hosted",
        "status": "cli_success",
        "captured_at_utc": "2026-10-24T15:25:08.345Z",
        "sha256": "c02f1789a75da7fa89c47a556113b192402585e7a18a230a7565bb7fb216ebe3",
        "bytes": 79937,
        "title": "Create separate charges and transfers",
        "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": [
          "source_transaction pending funds",
          "transfer_group association"
        ]
      }
    ],
    "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 releasing a supplier obligation based on a queued funds movement.",
      "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 releasing a supplier obligation based on a queued funds movement.",
    "refusal_conditions": [
      "Do not treat request acceptance or unrelated platform balance as proof that the intended charge funded the supplier."
    ]
  },
  "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 releasing a supplier obligation based on a queued funds movement.",
    "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-transfer-source-transaction-funds-availability",
  "machine_readable_record": "/varexis-index/records/stripe-transfer-source-transaction-funds-availability.json"
}
