{
  "schema": "varexis-index-free-publication-preview/1",
  "catalogue_version": "ice-05-tranche-61-v1",
  "route_id": "agentic_reviewed_stripe_issuing_refund_link_uncertainty",
  "record_id": "VXI-EXT-ICE05-STRIPE-ISSUING-REFUND-LINK-UNCERTAINTY-01-v1",
  "question": "Does an Issuing refund authorization link reliably identify the original purchase?",
  "answer": "Stripe describes refund linkage as inexact: the authorization can be unrelated or absent.",
  "records": [
    {
      "record_id": "VXI-EXT-ICE05-STRIPE-ISSUING-REFUND-LINK-UNCERTAINTY-01-v1",
      "url": "/varexis-index/records/stripe-issuing-refund-link-uncertainty.json",
      "content_sha256": "fa705c0c4241f92adae0b2f01d9edeeb27c9946e9ce8ddec52adf2e937e129be",
      "evidence": {
        "schema": "varexis-public-evidence-record/0.3",
        "generated_at_utc": "2026-10-29T01:09:39.613311Z",
        "record_id": "VXI-EXT-ICE05-STRIPE-ISSUING-REFUND-LINK-UNCERTAINTY-01-v1",
        "record_kind": "external_reference",
        "title": "Stripe Issuing refund linkage and invoice attribution",
        "system": "Stripe",
        "evidence_family": "vendor_evidence_review",
        "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
        "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
        "canonical_question": "Does an Issuing refund authorization link reliably identify the original purchase?",
        "near_questions": [
          "Can an Issuing refund link be wrong?",
          "How should an unlinked card refund be reconciled?",
          "Does null authorization mean the refund failed?",
          "What evidence binds a card refund to the supplier invoice?"
        ],
        "supported_claims": [
          {
            "claim": "Stripe describes refund linkage as inexact: the authorization can be unrelated or absent.",
            "reliance": "DOCUMENTED_CAPABILITY_ONLY"
          }
        ],
        "not_demonstrated_claims": [
          "Require corroboration before assigning a refund to an invoice. A missing link is not proof no refund occurred.",
          "Buyer implementation, live runtime enforcement, settled payment, certification or permission to act are not established.",
          "No expanded capabilities or licences for existing INDEX executables."
        ],
        "public_summary": "Stripe describes refund linkage as inexact: the authorization can be unrelated or absent.",
        "related_record_ids": [],
        "source_review": {
          "source_type": "official_external_documentation",
          "source_title": "Stripe: Issuing transactions",
          "source_url": "https://docs.stripe.com/issuing/purchases/transactions.md",
          "checked_on": "2026-10-29",
          "candidate_record_id": "VXI-EXT-ICE05-STRIPE-ISSUING-REFUND-LINK-UNCERTAINTY-01-v1",
          "candidate_record_sha256": "84b15b871a084945cbf5f414f0ad950d4821d6622dabe1f16dbcee20e99cfdcb",
          "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 refund linkage as inexact: the authorization can be unrelated or absent.",
          "required_buyer_context": "Refund transaction; Candidate original purchase; Merchant, amount and currency 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-29",
          "claim_to_check": "Does an Issuing refund authorization link reliably identify the original purchase?",
          "documented_statement": {
            "status": "documented",
            "statement": "Stripe describes refund linkage as inexact: the authorization can be unrelated or absent.",
            "source_ids": [
              "stripe-transactions"
            ]
          },
          "review_inference": {
            "status": "review_inference",
            "statement": "Review stripe issuing refund linkage and invoice attribution before accepting the buyer claim. Billing credit-note allocation is a different contract; this decision addresses unreliable issuer refund-to-authorization linkage. This is a documentation-review judgment, not an observed deployment outcome.",
            "source_ids": [
              "stripe-transactions"
            ]
          },
          "buyer_evidence_required": [
            "Refund transaction",
            "Candidate original purchase",
            "Merchant, amount and currency evidence"
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Require corroboration before assigning a refund to an invoice. A missing link is not proof no refund occurred."
          },
          "unknowns": "Buyer configuration, effective authority, complete usage and final business outcomes were not inspected.",
          "unknown_finding": {
            "status": "unknown",
            "statement": "Buyer configuration, effective authority, complete usage and final business outcomes were not inspected."
          },
          "evidence_sources": [
            {
              "source_id": "stripe-transactions",
              "url": "https://docs.stripe.com/issuing/purchases/transactions.md",
              "final_url": "https://docs.stripe.com/issuing/purchases/transactions.md",
              "captured_at_utc": "2026-10-29T00:50:21.087905+00:00",
              "status": 200,
              "content_type": "text/markdown; charset=utf-8",
              "bytes": 14114,
              "sha256": "5114b68904e4df54f9b63dd9f954c0909dd2feacc40e63ee621b262019de4beb",
              "title": "Stripe: Issuing transactions",
              "hash_basis": "SHA-256 of captured HTTP response body bytes",
              "checked_on": "2026-10-29",
              "capture_status": 200,
              "claim_review_completed": true,
              "reviewed_sections": [
                "Issuing transactions",
                "Refunds",
                "Refund reversals",
                "Force capture",
                "Partial capture",
                "Multi capture"
              ],
              "version_context": "Rolling official documentation captured 2026-10-29; exact response hash is pinned, not a stable vendor release. Verify the deployed API/version and account feature availability. ",
              "rights_review": "Original factual paraphrase and attributed source metadata only. Captured documentation and code remain private; no source prose, examples, images or vendor marks are redistributed. No licence to vendor software or buyer assurance is granted."
            }
          ],
          "observed_deployment": false,
          "commercial_reliance_boundary": "Source documentation supports only the stated boundary. Existing licensed checkers analyse supported supplied declarations; they do not query these providers, verify live systems, settle payments or certify compliance.",
          "paid_value": {
            "decision_context": "Review stripe issuing refund linkage and invoice attribution before accepting the buyer claim. Billing credit-note allocation is a different contract; this decision addresses unreliable issuer refund-to-authorization linkage.",
            "free": "Complete review, practical questions, source references and limitations; freely accessible and locally saveable.",
            "single_request": "Unavailable for this publication-only record; historical saved retrieval remains unchanged.",
            "evidence_receipt": "Unavailable for this publication-only record; no new paid retrieval entitlement.",
            "excluded": [
              "Fresh vendor research",
              "Live provider inspection",
              "Runtime enforcement or certification",
              "Expanded executable schemas or licences",
              "Native Coupa, Stripe Issuing, GitLab or Sigstore validation"
            ],
            "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
          },
          "revalidation": {
            "trigger": "Recheck the source and applicable API, account and configuration before current reliance. No monitoring or fresh research is included.",
            "specific_watch": "Refunds"
          },
          "buyer_relevance": "Review stripe issuing refund linkage and invoice attribution before accepting the buyer claim. Billing credit-note allocation is a different contract; this decision addresses unreliable issuer refund-to-authorization linkage.",
          "refusal_conditions": [
            "Require corroboration before assigning a refund to an invoice. A missing link is not proof no refund occurred.",
            "Do not infer buyer deployment conformance or successful business outcomes from source documentation."
          ]
        },
        "niche": {
          "niche_id": "ice05-payments",
          "label": "Agent Payments, Authority & Transaction Evidence",
          "classification_id": "payments",
          "classification_label": "Agent Payments, Authority & Transaction Evidence",
          "topic_id": "payments",
          "buyer_intent": "Review stripe issuing refund linkage and invoice attribution before accepting the buyer claim. Billing credit-note allocation is a different contract; this decision addresses unreliable issuer refund-to-authorization linkage.",
          "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-issuing-refund-link-uncertainty",
        "machine_readable_record": "/varexis-index/records/stripe-issuing-refund-link-uncertainty.json"
      }
    }
  ],
  "access": {
    "mode": "exact_http_only",
    "payment_required": false,
    "purchase_url": null,
    "mcp_preview_available": false,
    "paid_saved_retrieval_available": false,
    "natural_language_search_qualified": false
  },
  "boundary": "Catalogue additions are available free through the exact HTTP JSON links below. Enhanced natural-language discovery is not yet qualified for these records. They are outside MCP search, MCP preview and paid saved retrieval. No search qualification, executable capability or entitlement is added.",
  "content_sha256": "c6e66dd85c75071f4fa8c44d4c6ad36346fe2c3a13657a847f1ad4f33cde4d2e"
}
