{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-29T01:09:39.613311Z",
  "record_id": "VXI-EXT-ICE05-STRIPE-ISSUING-REPLACEMENT-BUDGET-CONTINUITY-01-v1",
  "record_kind": "external_reference",
  "title": "Stripe Issuing replacement cards and shared limits",
  "system": "Stripe",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does replacing an Issuing card reset its spending-limit history?",
  "near_questions": [
    "Does a replacement Stripe card have a fresh budget?",
    "Which cards share an Issuing cardholder limit?",
    "Must old-card spending be included after replacement?",
    "How is spending authority reconciled across card lineage?"
  ],
  "supported_claims": [
    {
      "claim": "The documented card limits extend across the replacement chain, while cardholder limits apply across that cardholder's cards.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Do not budget a replacement as an independent fresh allowance without reconciling the documented shared scope.",
    "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": "The documented card limits extend across the replacement chain, while cardholder limits apply across that cardholder's cards.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Stripe: Issuing spending controls",
    "source_url": "https://docs.stripe.com/issuing/controls/spending-controls.md",
    "checked_on": "2026-10-29",
    "candidate_record_id": "VXI-EXT-ICE05-STRIPE-ISSUING-REPLACEMENT-BUDGET-CONTINUITY-01-v1",
    "candidate_record_sha256": "33ecd4164bc533743208fc40ac6ec9a5274c2b1bdf96954cddb1c75f562b7370",
    "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": "The documented card limits extend across the replacement chain, while cardholder limits apply across that cardholder's cards.",
    "required_buyer_context": "Replacement-card lineage; Card and cardholder limits; Spending history across the relevant cards. 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 replacing an Issuing card reset its spending-limit history?",
    "documented_statement": {
      "status": "documented",
      "statement": "The documented card limits extend across the replacement chain, while cardholder limits apply across that cardholder's cards.",
      "source_ids": [
        "stripe-spending"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Review stripe issuing replacement cards and shared limits before accepting the buyer claim. This decision concerns identity continuity across replacement cards, not simply whether a configured budget is enforced. This is a documentation-review judgment, not an observed deployment outcome.",
      "source_ids": [
        "stripe-spending"
      ]
    },
    "buyer_evidence_required": [
      "Replacement-card lineage",
      "Card and cardholder limits",
      "Spending history across the relevant cards"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not budget a replacement as an independent fresh allowance without reconciling the documented shared scope."
    },
    "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-spending",
        "url": "https://docs.stripe.com/issuing/controls/spending-controls.md",
        "final_url": "https://docs.stripe.com/issuing/controls/spending-controls.md",
        "captured_at_utc": "2026-10-29T00:50:21.051844+00:00",
        "status": 200,
        "content_type": "text/markdown; charset=utf-8",
        "bytes": 7591,
        "sha256": "9787034b96115581c21b6a58790f6cd490e20f7f3a8cf48908df0478dc62db87",
        "title": "Stripe: Issuing spending controls",
        "hash_basis": "SHA-256 of captured HTTP response body bytes",
        "checked_on": "2026-10-29",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Spending limits",
          "Issuing spending controls"
        ],
        "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 replacement cards and shared limits before accepting the buyer claim. This decision concerns identity continuity across replacement cards, not simply whether a configured budget is enforced.",
      "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": "Spending limits"
    },
    "buyer_relevance": "Review stripe issuing replacement cards and shared limits before accepting the buyer claim. This decision concerns identity continuity across replacement cards, not simply whether a configured budget is enforced.",
    "refusal_conditions": [
      "Do not budget a replacement as an independent fresh allowance without reconciling the documented shared scope.",
      "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 replacement cards and shared limits before accepting the buyer claim. This decision concerns identity continuity across replacement cards, not simply whether a configured budget is enforced.",
    "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-replacement-budget-continuity",
  "machine_readable_record": "/varexis-index/records/stripe-issuing-replacement-budget-continuity.json"
}
