{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T15:48:56.209Z",
  "record_id": "VXI-EXT-PROCUREMENT-STRIPE-TRANSFER-GROUP-ASSOCIATION-NOT-FUNDING-PROOF-01-v1",
  "record_kind": "external_reference",
  "title": "Stripe transfer groups and funding provenance",
  "system": "Stripe",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a shared Stripe transfer_group prove a one-to-one funding relationship between a charge and transfer?",
  "near_questions": [
    "Does transfer_group enforce Stripe transfer funding rules?",
    "Can several transfers share one Stripe charge group?",
    "Must a transfer amount match its associated charge?",
    "What evidence ties grouped transfers to one purchased entitlement?"
  ],
  "supported_claims": [
    {
      "claim": "Stripe describes transfer_group as an association string that does not change standard transfer behavior. Charge and transfer amounts need not match: one charge can support several transfers, and several charges can be included in a transfer. A shared group alone therefore does not establish a unique funding allocation or completed delivery for a particular purchase.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "An association label as cryptographic or one-to-one funding proof",
    "The merchant allocation logic and actual delivered purchase remain outside the group field.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Stripe describes transfer_group as an association string that does not change standard transfer behavior. Charge and transfer amounts need not match: one charge can support several transfers, and several charges can be included in a transfer. A shared group alone therefore does not establish a unique funding allocation or completed delivery for a particular purchase.",
  "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-GROUP-ASSOCIATION-NOT-FUNDING-PROOF-01-v1",
    "candidate_record_sha256": "30eb5104f306b15d1894a8083f73db4264ba48c51595f9fb9966c892f4902251",
    "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": "Stripe describes transfer_group as an association string that does not change standard transfer behavior. Charge and transfer amounts need not match: one charge can support several transfers, and several charges can be included in a transfer. A shared group alone therefore does not establish a unique funding allocation or completed delivery for a particular purchase.",
    "required_buyer_context": "Charge and transfer IDs sharing the group; Amounts, currencies and source_transaction bindings; Order-level allocation and entitlement evidence. 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 shared Stripe transfer_group prove a one-to-one funding relationship between a charge and transfer?",
    "documented_statement": {
      "status": "documented",
      "statement": "Stripe describes transfer_group as an association string that does not change standard transfer behavior. Charge and transfer amounts need not match: one charge can support several transfers, and several charges can be included in a transfer. A shared group alone therefore does not establish a unique funding allocation or completed delivery for a particular purchase.",
      "source_ids": [
        "stripe-transfers-full"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Retain explicit charge, transfer, amount and order allocations instead of relying on a group label as payment provenance.",
      "source_ids": [
        "stripe-transfers-full"
      ]
    },
    "buyer_evidence_required": [
      "Charge and transfer IDs sharing the group",
      "Amounts, currencies and source_transaction bindings",
      "Order-level allocation and entitlement evidence"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse a claim of uniquely funded licensed delivery when only a transfer_group match is available."
    },
    "unknowns": "The merchant allocation logic and actual delivered purchase remain outside the group field.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The merchant allocation logic and actual delivered purchase remain outside the group field."
    },
    "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": "Reconstruct procurement funding without confusing a label with a verified allocation.",
      "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": "Reconstruct procurement funding without confusing a label with a verified allocation.",
    "refusal_conditions": [
      "Refuse a claim of uniquely funded licensed delivery when only a transfer_group match is available."
    ]
  },
  "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": "Reconstruct procurement funding without confusing a label with a verified allocation.",
    "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-group-association-not-funding-proof",
  "machine_readable_record": "/varexis-index/records/stripe-transfer-group-association-not-funding-proof.json"
}
