{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T21:35:02.243Z",
  "record_id": "VXI-EXT-PROCUREMENT-X402-PAYMENT-IDENTIFIER-REQUEST-SCOPE-01-v1",
  "record_kind": "external_reference",
  "title": "x402 retry identifiers and operation binding",
  "system": "x402 Foundation",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can an x402 payment identifier safely identify different paid operations across tenants?",
  "near_questions": [
    "Must x402 retry IDs be scoped to a merchant?",
    "What if an x402 payment ID is reused with a changed resource?",
    "Does an x402 identifier alone prove the same purchase?",
    "How should a multi-tenant x402 cache bind retries?"
  ],
  "supported_claims": [
    {
      "claim": "The reviewed payment-identifier extension calls for binding an identifier to a normalized request fingerprint. Reuse with changed operation details should produce a conflict. It also recommends scoping keys by tenant, merchant, route or facilitator account where those boundaries exist, rather than using the identifier alone for authorization.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Independent verification of payment, delivery or deployed controls",
    "Cache persistence, key scope and deployed conflict handling have not been tested.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "The reviewed payment-identifier extension calls for binding an identifier to a normalized request fingerprint. Reuse with changed operation details should produce a conflict. It also recommends scoping keys by tenant, merchant, route or facilitator account where those boundaries exist, rather than using the identifier alone for authorization.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Extension: `payment-identifier`",
    "source_url": "https://raw.githubusercontent.com/x402-foundation/x402/4241d56cae2fb7ed06cd18e3a9ff2a3457b1ce54/specs/extensions/payment_identifier.md",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-X402-PAYMENT-IDENTIFIER-REQUEST-SCOPE-01-v1",
    "candidate_record_sha256": "995443c4d997fafa3b87f16ec852fbe58c45ee1965c6bf840777ea2f18160e1b",
    "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 reviewed payment-identifier extension calls for binding an identifier to a normalized request fingerprint. Reuse with changed operation details should produce a conflict. It also recommends scoping keys by tenant, merchant, route or facilitator account where those boundaries exist, rather than using the identifier alone for authorization.",
    "required_buyer_context": "Identifier and original request fingerprint; Tenant, merchant and resource scope; Cached response and conflict-handling 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-24",
    "claim_to_check": "Can an x402 payment identifier safely identify different paid operations across tenants?",
    "documented_statement": {
      "status": "documented",
      "statement": "The reviewed payment-identifier extension calls for binding an identifier to a normalized request fingerprint. Reuse with changed operation details should produce a conflict. It also recommends scoping keys by tenant, merchant, route or facilitator account where those boundaries exist, rather than using the identifier alone for authorization.",
      "source_ids": [
        "x402-identifier"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Keep payment retries from returning another operation or tenant cached result. This is a review decision, not an observed buyer result.",
      "source_ids": [
        "x402-identifier"
      ]
    },
    "buyer_evidence_required": [
      "Identifier and original request fingerprint",
      "Tenant, merchant and resource scope",
      "Cached response and conflict-handling evidence"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not reuse cached authorization merely because the payment identifier matches."
    },
    "unknowns": "Cache persistence, key scope and deployed conflict handling have not been tested.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "Cache persistence, key scope and deployed conflict handling have not been tested."
    },
    "evidence_sources": [
      {
        "source_id": "x402-identifier",
        "url": "https://raw.githubusercontent.com/x402-foundation/x402/4241d56cae2fb7ed06cd18e3a9ff2a3457b1ce54/specs/extensions/payment_identifier.md",
        "final_url": "https://raw.githubusercontent.com/x402-foundation/x402/4241d56cae2fb7ed06cd18e3a9ff2a3457b1ce54/specs/extensions/payment_identifier.md",
        "status": 200,
        "captured_at_utc": "2026-10-24T21:23:35.499Z",
        "sha256": "a48b79d0c1fc10f82b0939efdabfa363e9367391664bb00bf6fed0beb193d2d3",
        "bytes": 3427,
        "title": "Extension: `payment-identifier`",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Original factual paraphrase and source metadata only; Apache-2.0 repository captures retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "reviewed_sections": [
          "Idempotency Behavior",
          "Request Binding",
          "Responsibilities"
        ],
        "version_context": "Pinned x402-foundation/x402 revision 4241d56cae2fb7ed06cd18e3a9ff2a3457b1ce54 captured 2026-10-24. Documentation revision, not evidence that any buyer deployment conforms."
      }
    ],
    "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": "Keep payment retries from returning another operation or tenant cached result.",
      "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 pinned specification against the selected scheme, network, provider version and buyer evidence before relying on a current outcome."
    },
    "buyer_relevance": "Keep payment retries from returning another operation or tenant cached result.",
    "refusal_conditions": [
      "Do not reuse cached authorization merely because the payment identifier matches."
    ]
  },
  "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": "Keep payment retries from returning another operation or tenant cached result.",
    "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#x402-payment-identifier-request-scope",
  "machine_readable_record": "/varexis-index/records/x402-payment-identifier-request-scope.json"
}