{
  "schema": "varexis-index-free-publication-preview/1",
  "catalogue_version": "ice-05-tranche-61-v1",
  "route_id": "agentic_reviewed_stripe_issuing_refund_reversal_direction",
  "record_id": "VXI-EXT-ICE05-STRIPE-ISSUING-REFUND-REVERSAL-DIRECTION-01-v1",
  "question": "Does every Issuing transaction with type refund add a credit?",
  "answer": "A refund reversal retains type refund but has a negative amount, unlike a standard positive refund.",
  "records": [
    {
      "record_id": "VXI-EXT-ICE05-STRIPE-ISSUING-REFUND-REVERSAL-DIRECTION-01-v1",
      "url": "/varexis-index/records/stripe-issuing-refund-reversal-direction.json",
      "content_sha256": "ceace025ea167516e906657db1f7c13d47d5340f1d3755ee94f9340f737a26f0",
      "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-REVERSAL-DIRECTION-01-v1",
        "record_kind": "external_reference",
        "title": "Stripe Issuing refund reversals and amount direction",
        "system": "Stripe",
        "evidence_family": "vendor_evidence_review",
        "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
        "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
        "canonical_question": "Does every Issuing transaction with type refund add a credit?",
        "near_questions": [
          "Why is an Issuing refund amount negative?",
          "Can a refund transaction reverse an earlier credit?",
          "How do I avoid counting a refund reversal as income?",
          "Which fields establish the direction of an issuer refund?"
        ],
        "supported_claims": [
          {
            "claim": "A refund reversal retains type refund but has a negative amount, unlike a standard positive refund.",
            "reliance": "DOCUMENTED_CAPABILITY_ONLY"
          }
        ],
        "not_demonstrated_claims": [
          "Preserve amount direction when reconciling credits. Type alone must not cause a reversal to be counted as another refund.",
          "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": "A refund reversal retains type refund but has a negative amount, unlike a standard positive refund.",
        "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-REVERSAL-DIRECTION-01-v1",
          "candidate_record_sha256": "6ad431ab989cf700ace0d5a423508a47ad4483983bc89a5993da28163c5291cc",
          "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": "A refund reversal retains type refund but has a negative amount, unlike a standard positive refund.",
          "required_buyer_context": "Transaction type and signed amount; Currency; Original refund and reversal 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-29",
          "claim_to_check": "Does every Issuing transaction with type refund add a credit?",
          "documented_statement": {
            "status": "documented",
            "statement": "A refund reversal retains type refund but has a negative amount, unlike a standard positive refund.",
            "source_ids": [
              "stripe-transactions"
            ]
          },
          "review_inference": {
            "status": "review_inference",
            "statement": "Review stripe issuing refund reversals and amount direction before accepting the buyer claim. This adds the Issuing reversal encoding needed to avoid double-counting credits; invoice credit-note categories do not define that sign convention. This is a documentation-review judgment, not an observed deployment outcome.",
            "source_ids": [
              "stripe-transactions"
            ]
          },
          "buyer_evidence_required": [
            "Transaction type and signed amount",
            "Currency",
            "Original refund and reversal records"
          ],
          "review_condition": {
            "status": "varexis_review_policy",
            "statement": "Preserve amount direction when reconciling credits. Type alone must not cause a reversal to be counted as another refund."
          },
          "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 reversals and amount direction before accepting the buyer claim. This adds the Issuing reversal encoding needed to avoid double-counting credits; invoice credit-note categories do not define that sign convention.",
            "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": "Refund reversals"
          },
          "buyer_relevance": "Review stripe issuing refund reversals and amount direction before accepting the buyer claim. This adds the Issuing reversal encoding needed to avoid double-counting credits; invoice credit-note categories do not define that sign convention.",
          "refusal_conditions": [
            "Preserve amount direction when reconciling credits. Type alone must not cause a reversal to be counted as another refund.",
            "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 reversals and amount direction before accepting the buyer claim. This adds the Issuing reversal encoding needed to avoid double-counting credits; invoice credit-note categories do not define that sign convention.",
          "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-reversal-direction",
        "machine_readable_record": "/varexis-index/records/stripe-issuing-refund-reversal-direction.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": "30e23e75bd34bb5396f1d7244e36cdda7848b4cdda0501585dcf18190b7b16eb"
}
