{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T15:48:56.209Z",
  "record_id": "VXI-EXT-PROCUREMENT-STRIPE-SUBSCRIPTION-ACTIVE-INVOICE-SETTLEMENT-BOUNDARY-01-v1",
  "record_kind": "external_reference",
  "title": "Stripe subscription status and outstanding invoices",
  "system": "Stripe",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an active Stripe subscription establish that every outstanding invoice is paid?",
  "near_questions": [
    "Can an active Stripe subscription still have unpaid invoices?",
    "Does past_due automatically revoke application access?",
    "Can marking an invoice uncollectible change subscription status?",
    "Which invoice settings determine Stripe subscription status?"
  ],
  "supported_claims": [
    {
      "claim": "Stripe explicitly states that active does not necessarily mean every outstanding subscription invoice has been paid. Status resolution can depend on the most recent invoice or all applicable invoices; settling can also include marking an invoice uncollectible. Failed-payment settings can leave a subscription past_due. Subscription status and invoice-level collection evidence are therefore separate.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Subscription status as complete cash-collection or access-control proof",
    "The merchant policy, applicable invoices and actual access enforcement are not observed.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "Stripe explicitly states that active does not necessarily mean every outstanding subscription invoice has been paid. Status resolution can depend on the most recent invoice or all applicable invoices; settling can also include marking an invoice uncollectible. Failed-payment settings can leave a subscription past_due. Subscription status and invoice-level collection evidence are therefore separate.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "How subscriptions work",
    "source_url": "https://docs.stripe.com/billing/subscriptions/overview",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-STRIPE-SUBSCRIPTION-ACTIVE-INVOICE-SETTLEMENT-BOUNDARY-01-v1",
    "candidate_record_sha256": "5b17a43516fa860c6e1409779569c54fb768f1db1cfe1a63a8bbf55bd2c8936c",
    "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 explicitly states that active does not necessarily mean every outstanding subscription invoice has been paid. Status resolution can depend on the most recent invoice or all applicable invoices; settling can also include marking an invoice uncollectible. Failed-payment settings can leave a subscription past_due. Subscription status and invoice-level collection evidence are therefore separate.",
    "required_buyer_context": "Subscription status-resolution and failed-payment settings; Applicable invoice statuses and payment evidence; Merchant access policy and current entitlement state. 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 an active Stripe subscription establish that every outstanding invoice is paid?",
    "documented_statement": {
      "status": "documented",
      "statement": "Stripe explicitly states that active does not necessarily mean every outstanding subscription invoice has been paid. Status resolution can depend on the most recent invoice or all applicable invoices; settling can also include marking an invoice uncollectible. Failed-payment settings can leave a subscription past_due. Subscription status and invoice-level collection evidence are therefore separate.",
      "source_ids": [
        "stripe-subscription-states"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Reconcile the invoices and merchant access policy instead of equating active with all debt collected or past_due with automatic service removal.",
      "source_ids": [
        "stripe-subscription-states"
      ]
    },
    "buyer_evidence_required": [
      "Subscription status-resolution and failed-payment settings",
      "Applicable invoice statuses and payment evidence",
      "Merchant access policy and current entitlement state"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Refuse a claim of fully paid subscription access from the aggregate subscription status alone."
    },
    "unknowns": "The merchant policy, applicable invoices and actual access enforcement are not observed.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The merchant policy, applicable invoices and actual access enforcement are not observed."
    },
    "evidence_sources": [
      {
        "source_id": "stripe-subscription-states",
        "url": "https://docs.stripe.com/billing/subscriptions/overview",
        "final_url": "https://docs.stripe.com/billing/subscriptions/overview",
        "status": "cli_success",
        "captured_at_utc": "2026-10-24T15:10:50.362Z",
        "sha256": "b1f722da974b8329843e9f5c5e99e4d19ba626473ce91878f35304005b60a3c4",
        "bytes": 59170,
        "title": "How subscriptions 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": [
          "Subscription statuses",
          "Active does not imply all invoices paid"
        ]
      }
    ],
    "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": "Avoid incorrect access and revenue decisions based on a single subscription flag.",
      "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": "Avoid incorrect access and revenue decisions based on a single subscription flag.",
    "refusal_conditions": [
      "Refuse a claim of fully paid subscription access from the aggregate subscription status alone."
    ]
  },
  "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": "Avoid incorrect access and revenue decisions based on a single subscription flag.",
    "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-subscription-active-invoice-settlement-boundary",
  "machine_readable_record": "/varexis-index/records/stripe-subscription-active-invoice-settlement-boundary.json"
}
