{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T15:48:56.209Z",
  "record_id": "VXI-EXT-PROCUREMENT-STRIPE-CONNECT-CHARGE-MODEL-DISPUTE-LIABILITY-01-v1",
  "record_kind": "external_reference",
  "title": "Stripe Connect charge model and dispute liability",
  "system": "Stripe",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does Stripe on_behalf_of move dispute debits to a connected account for every charge model?",
  "near_questions": [
    "Does on_behalf_of change who Stripe debits for a dispute?",
    "Are direct and destination charge disputes debited to the same account?",
    "Can the business of record differ from the account funding a dispute?",
    "Which charge fields matter before assigning Connect payment responsibility?"
  ],
  "supported_claims": [
    {
      "claim": "Stripe separates direct charges from charges created on a platform. Direct-charge disputes debit the connected account for the disputed amount, while destination charges and separate charges and transfers debit the platform balance, with or without on_behalf_of. The parameter can make the connected account the business of record, but it does not erase charge-model-specific debit rules.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "A legal merchant-of-record or liability determination",
    "Contractual responsibility and account-specific arrangements require separate evidence; this review describes documented provider debits.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Stripe separates direct charges from charges created on a platform. Direct-charge disputes debit the connected account for the disputed amount, while destination charges and separate charges and transfers debit the platform balance, with or without on_behalf_of. The parameter can make the connected account the business of record, but it does not erase charge-model-specific debit rules.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Understand how charges work in a Connect integration",
    "source_url": "https://docs.stripe.com/connect/charges",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-STRIPE-CONNECT-CHARGE-MODEL-DISPUTE-LIABILITY-01-v1",
    "candidate_record_sha256": "d100f58fd0317b2d9f4688ff7e809d79e7c14e89152fb8b026d127d47ca84976",
    "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 separates direct charges from charges created on a platform. Direct-charge disputes debit the connected account for the disputed amount, while destination charges and separate charges and transfers debit the platform balance, with or without on_behalf_of. The parameter can make the connected account the business of record, but it does not erase charge-model-specific debit rules.",
    "required_buyer_context": "Charge account, charge model and on_behalf_of setting; Connected-account fee and liability configuration; Dispute and balance-transaction 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 Stripe on_behalf_of move dispute debits to a connected account for every charge model?",
    "documented_statement": {
      "status": "documented",
      "statement": "Stripe separates direct charges from charges created on a platform. Direct-charge disputes debit the connected account for the disputed amount, while destination charges and separate charges and transfers debit the platform balance, with or without on_behalf_of. The parameter can make the connected account the business of record, but it does not erase charge-model-specific debit rules.",
      "source_ids": [
        "stripe-connect-charges"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Identify the actual charge model, account context and fee configuration before assigning financial responsibility.",
      "source_ids": [
        "stripe-connect-charges"
      ]
    },
    "buyer_evidence_required": [
      "Charge account, charge model and on_behalf_of setting",
      "Connected-account fee and liability configuration",
      "Dispute and balance-transaction records"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not assign all dispute liability from a merchant label or on_behalf_of alone."
    },
    "unknowns": "Contractual responsibility and account-specific arrangements require separate evidence; this review describes documented provider debits.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Contractual responsibility and account-specific arrangements require separate evidence; this review describes documented provider debits."
    },
    "evidence_sources": [
      {
        "source_id": "stripe-connect-charges",
        "url": "https://docs.stripe.com/connect/charges",
        "final_url": "https://docs.stripe.com/connect/charges",
        "status": "cli_success",
        "captured_at_utc": "2026-10-24T15:10:52.104Z",
        "sha256": "40470c86e2992da890a5f58591d42761a163189f507bcf4ef6d22e1980495961",
        "bytes": 44531,
        "title": "Understand how charges work in a Connect integration",
        "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": [
          "Charge types",
          "Dispute handling and on_behalf_of"
        ]
      }
    ],
    "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 a procurement agent from attributing dispute risk to the wrong account.",
      "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 a procurement agent from attributing dispute risk to the wrong account.",
    "refusal_conditions": [
      "Do not assign all dispute liability from a merchant label or on_behalf_of 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": "Prevent a procurement agent from attributing dispute risk to the wrong account.",
    "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-charge-model-dispute-liability",
  "machine_readable_record": "/varexis-index/records/stripe-connect-charge-model-dispute-liability.json"
}
