{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T19:34:16.969Z",
  "record_id": "VXI-EXT-PROCUREMENT-STRIPE-REFUND-CREATED-PENDING-FAILED-REVERSAL-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "Stripe refunds: Creation and final outcomes differ",
  "system": "Stripe",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does creating a Stripe refund establish that the customer received it and the original effects were reversed?",
  "near_questions": [
    "Can a Stripe refund remain pending after creation?",
    "What does a failed Stripe refund mean for the returned funds?",
    "Why might a Stripe refund appear as a reversal instead of a credit?",
    "Does a Stripe refund automatically reverse delivered goods or entitlements?"
  ],
  "supported_claims": [
    {
      "claim": "Stripe documents refunds that remain pending when a card refund lacks sufficient available balance, and refunds that later fail when the bank or card issuer cannot process them. Failed refunds return funds to the Stripe balance and expose failure information. Some early refunds appear as reversals of the original charge rather than a separate credit.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Guaranteed customer receipt, automatic tax correction or reversal of non-payment effects",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Stripe documents refunds that remain pending when a card refund lacks sufficient available balance, and refunds that later fail when the bank or card issuer cannot process them. Failed refunds return funds to the Stripe balance and expose failure information. Some early refunds appear as reversals of the original charge rather than a separate credit.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Refund and cancel payments | Stripe Documentation",
    "source_url": "https://docs.stripe.com/refunds",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-STRIPE-REFUND-CREATED-PENDING-FAILED-REVERSAL-BOUNDARY-01-v1",
    "candidate_record_sha256": "4ca6d986a5da781a8ca6bba1e7290ab2c7371ea0279777c3bf61eea211c35a67",
    "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 refunds that remain pending when a card refund lacks sufficient available balance, and refunds that later fail when the bank or card issuer cannot process them. Failed refunds return funds to the Stripe balance and expose failure information. Some early refunds appear as reversals of the original charge rather than a separate credit.",
    "required_buyer_context": "Refund and original payment IDs, amount, currency and current refund status. Later failure or return events and available refund reference information. Separate tax, entitlement, inventory and delivery compensation 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-18",
    "claim_to_check": "Does creating a Stripe refund establish that the customer received it and the original effects were reversed?",
    "documented_statement": {
      "status": "documented",
      "statement": "Stripe documents refunds that remain pending when a card refund lacks sufficient available balance, and refunds that later fail when the bank or card issuer cannot process them. Failed refunds return funds to the Stripe balance and expose failure information. Some early refunds appear as reversals of the original charge rather than a separate credit.",
      "source_ids": [
        "stripe-refunds"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "A refund record does not by itself reverse business effects such as delivered goods or granted access.",
      "source_ids": [
        "stripe-refunds"
      ]
    },
    "buyer_evidence_required": [
      "Refund and original payment IDs, amount, currency and current refund status.",
      "Later failure or return events and available refund reference information.",
      "Separate tax, entitlement, inventory and delivery compensation records."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse completed-refund or all-effects-reversed claims based solely on refund creation."
    },
    "unknowns": "Customer receipt and the buyer's compensation state were not observed.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Customer receipt and the buyer's compensation state were not observed."
    },
    "evidence_sources": [
      {
        "source_id": "stripe-refunds",
        "url": "https://docs.stripe.com/refunds",
        "final_url": "https://docs.stripe.com/refunds",
        "title": "Refund and cancel payments | Stripe Documentation",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T19:20:57.404Z",
        "version_context": "Rolling official documentation captured 2026-10-18; exact response hash retained, no pinned release implied.",
        "sha256": "6ed0e3d5de86f14d771590ccc1cacc93240323165728d8242c914760a02f7798",
        "bytes": 587924,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Refund requests",
          "Handle failed refunds",
          "Refund and reversal"
        ],
        "capture_status": 200,
        "rights_review": "Factual paraphrase and source metadata only; response body retained privately and not redistributed."
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Documentation review only; no supplier clearance, configuration audit, observed execution or certification of the buyer's claim.",
    "paid_value": {
      "decision_context": "Reconcile spending authority or transaction state before approving financial reliance.",
      "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 payment-method-specific pending, failed and reversal behavior and later state changes."
    },
    "buyer_relevance": "Reconcile spending authority or transaction state before approving financial reliance.",
    "refusal_conditions": [
      "Refuse completed-refund or all-effects-reversed claims based solely on refund creation."
    ]
  },
  "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": "Reconcile spending authority or transaction state before approving financial reliance.",
    "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-refund-created-pending-failed-reversal-boundary",
  "machine_readable_record": "/varexis-index/records/stripe-refund-created-pending-failed-reversal-boundary.json"
}
