{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T15:48:56.209Z",
  "record_id": "VXI-EXT-PROCUREMENT-STRIPE-DISPUTE-AFTER-DELIVERY-FINANCIAL-REVERSAL-01-v1",
  "record_kind": "external_reference",
  "title": "Stripe disputes after licensed delivery",
  "system": "Stripe",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does successful software delivery make a Stripe card payment immune to a later dispute debit?",
  "near_questions": [
    "Can Stripe debit a payment after software was delivered?",
    "Does a delivery receipt prevent a card dispute?",
    "Which records link a delivered licence to a later chargeback?",
    "Is a successful charge an irreversible settlement guarantee?"
  ],
  "supported_claims": [
    {
      "claim": "Stripe documents that a formal card dispute causes the card network to debit Stripe and Stripe to debit the merchant balance for the disputed amount and a dispute fee. The dispute process can subsequently return funds or uphold the cardholder outcome. An application delivery record does not disable that provider process or prove irreversible funds.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Predicting dispute outcomes or providing legal entitlement advice",
    "The dispute merits, issuer decision and contractual rights are not determined here.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Stripe documents that a formal card dispute causes the card network to debit Stripe and Stripe to debit the merchant balance for the disputed amount and a dispute fee. The dispute process can subsequently return funds or uphold the cardholder outcome. An application delivery record does not disable that provider process or prove irreversible funds.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "How disputes work",
    "source_url": "https://docs.stripe.com/disputes/how-disputes-work",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-STRIPE-DISPUTE-AFTER-DELIVERY-FINANCIAL-REVERSAL-01-v1",
    "candidate_record_sha256": "e12ddb0cdf8db5b64286752b638eb2b50a13420f9ca4cb342a198422255e8317",
    "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 documents that a formal card dispute causes the card network to debit Stripe and Stripe to debit the merchant balance for the disputed amount and a dispute fee. The dispute process can subsequently return funds or uphold the cardholder outcome. An application delivery record does not disable that provider process or prove irreversible funds.",
    "required_buyer_context": "Original payment and immutable delivery records; Dispute state and related balance transactions; Applicable existing licence and dispute-handling policy. 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 successful software delivery make a Stripe card payment immune to a later dispute debit?",
    "documented_statement": {
      "status": "documented",
      "statement": "Stripe documents that a formal card dispute causes the card network to debit Stripe and Stripe to debit the merchant balance for the disputed amount and a dispute fee. The dispute process can subsequently return funds or uphold the cardholder outcome. An application delivery record does not disable that provider process or prove irreversible funds.",
      "source_ids": [
        "stripe-disputes"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Keep purchase, delivery and later dispute outcomes linked while applying the existing licence and dispute policies separately.",
      "source_ids": [
        "stripe-disputes"
      ]
    },
    "buyer_evidence_required": [
      "Original payment and immutable delivery records",
      "Dispute state and related balance transactions",
      "Applicable existing licence and dispute-handling policy"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not describe an entitlement delivery as proof of irreversible payment or automatically change licence rights from this review."
    },
    "unknowns": "The dispute merits, issuer decision and contractual rights are not determined here.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The dispute merits, issuer decision and contractual rights are not determined here."
    },
    "evidence_sources": [
      {
        "source_id": "stripe-disputes",
        "url": "https://docs.stripe.com/disputes/how-disputes-work",
        "final_url": "https://docs.stripe.com/disputes/how-disputes-work",
        "status": "cli_success",
        "captured_at_utc": "2026-10-24T15:10:54.261Z",
        "sha256": "3610f08e8552f07c46072190a00b42b5d7e68870312c8352dccecd7e4d368d2e",
        "bytes": 48684,
        "title": "How disputes work",
        "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": [
          "Dispute balance debit",
          "Response and dispute outcome"
        ]
      }
    ],
    "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": "Preserve auditable payment-to-delivery history when later financial reversals occur.",
      "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": "Preserve auditable payment-to-delivery history when later financial reversals occur.",
    "refusal_conditions": [
      "Do not describe an entitlement delivery as proof of irreversible payment or automatically change licence rights from this review."
    ]
  },
  "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": "Preserve auditable payment-to-delivery history when later financial reversals occur.",
    "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-dispute-after-delivery-financial-reversal",
  "machine_readable_record": "/varexis-index/records/stripe-dispute-after-delivery-financial-reversal.json"
}
