{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T15:48:56.209Z",
  "record_id": "VXI-EXT-PROCUREMENT-MPP-CHALLENGE-DESCRIPTION-NOT-MERCHANT-AUTHORITY-01-v1",
  "record_kind": "external_reference",
  "title": "MPP challenges and intended payment recipient",
  "system": "Machine Payments Protocol",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does an HTTP 402 MPP challenge establish that its stated merchant and payment terms are authorised?",
  "near_questions": [
    "Can an MPP challenge description be trusted as payment authority?",
    "Which MPP fields identify amount, currency and recipient?",
    "Does a 402 response prove the intended merchant is requesting payment?",
    "What should an agent compare before accepting an MPP challenge?"
  ],
  "supported_claims": [
    {
      "claim": "MPP clients are instructed to check the requested amount, recipient, currency or asset and validity window before authorising payment. The description is display text and must not be used for payment verification. A 402 challenge supplies payment requirements; its presence does not independently establish that the endpoint or recipient matches the buyer intent.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "HTTP 402 or human-readable text as merchant verification",
    "The endpoint owner, merchant relationship and actual buyer authority require independent evidence.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "MPP clients are instructed to check the requested amount, recipient, currency or asset and validity window before authorising payment. The description is display text and must not be used for payment verification. A 402 challenge supplies payment requirements; its presence does not independently establish that the endpoint or recipient matches the buyer intent.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Protocol overview | MPP",
    "source_url": "https://mpp.dev/protocol/",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-MPP-CHALLENGE-DESCRIPTION-NOT-MERCHANT-AUTHORITY-01-v1",
    "candidate_record_sha256": "963ea9c249d7fe4af4b91e9e6dd724b19dc22fe79869e2e8e87aff1f42238ba5",
    "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": "MPP clients are instructed to check the requested amount, recipient, currency or asset and validity window before authorising payment. The description is display text and must not be used for payment verification. A 402 challenge supplies payment requirements; its presence does not independently establish that the endpoint or recipient matches the buyer intent.",
    "required_buyer_context": "Expected endpoint and merchant or recipient identity; Decoded challenge amount, currency, recipient and expiry; Buyer spending authority and intended resource. 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 HTTP 402 MPP challenge establish that its stated merchant and payment terms are authorised?",
    "documented_statement": {
      "status": "documented",
      "statement": "MPP clients are instructed to check the requested amount, recipient, currency or asset and validity window before authorising payment. The description is display text and must not be used for payment verification. A 402 challenge supplies payment requirements; its presence does not independently establish that the endpoint or recipient matches the buyer intent.",
      "source_ids": [
        "mpp-protocol",
        "mpp-challenges"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Bind the requested payment to a previously established service identity and spending decision, using the structured terms rather than the description.",
      "source_ids": [
        "mpp-protocol",
        "mpp-challenges"
      ]
    },
    "buyer_evidence_required": [
      "Expected endpoint and merchant or recipient identity",
      "Decoded challenge amount, currency, recipient and expiry",
      "Buyer spending authority and intended resource"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not authorise a payment when the structured recipient or terms differ from the approved request."
    },
    "unknowns": "The endpoint owner, merchant relationship and actual buyer authority require independent evidence.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The endpoint owner, merchant relationship and actual buyer authority require independent evidence."
    },
    "evidence_sources": [
      {
        "source_id": "mpp-protocol",
        "url": "https://mpp.dev/protocol/",
        "final_url": "https://mpp.dev/protocol/",
        "status": 200,
        "captured_at_utc": "2026-10-24T15:10:55.047Z",
        "sha256": "d2dec7ff4cb5cb7ce170bde0ab0826ffa15fcc1aa44e821900f5a1aca8196be0",
        "bytes": 259178,
        "title": "Protocol overview | MPP",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "version_context": "Rolling MPP developer documentation captured on 2026-10-24; payment method and intent determine verification and settlement semantics.",
        "reviewed_sections": [
          "Challenge/credential/receipt flow",
          "Method-specific verification",
          "Authentication and policy status"
        ]
      },
      {
        "source_id": "mpp-challenges",
        "url": "https://mpp.dev/protocol/challenges",
        "final_url": "https://mpp.dev/protocol/challenges",
        "status": 200,
        "captured_at_utc": "2026-10-24T15:14:46.859Z",
        "sha256": "3e491b0dd642c4311f4cf70f2fb610d9b3fb938039444ec6c85c90e97ec214af",
        "bytes": 206406,
        "title": "Challenges | MPP",
        "hash_basis": "Decoded HTTP response body bytes",
        "rights_review": "Factual paraphrase and source metadata only; raw source retained privately and not redistributed.",
        "checked_on": "2026-10-24",
        "capture_status": 200,
        "claim_review_completed": true,
        "version_context": "Rolling MPP developer documentation captured on 2026-10-24; payment method and intent determine verification and settlement semantics.",
        "reviewed_sections": [
          "Request amount, currency and recipient",
          "expires and digest"
        ]
      }
    ],
    "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": "Prevent payment to a substituted recipient or different terms.",
      "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": "Prevent payment to a substituted recipient or different terms.",
    "refusal_conditions": [
      "Do not authorise a payment when the structured recipient or terms differ from the approved request."
    ]
  },
  "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": "Prevent payment to a substituted recipient or different terms.",
    "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#mpp-challenge-description-not-merchant-authority",
  "machine_readable_record": "/varexis-index/records/mpp-challenge-description-not-merchant-authority.json"
}
