{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-24T15:48:56.209Z",
  "record_id": "VXI-EXT-PROCUREMENT-UCP-PAYMENT-HANDLER-CREDENTIAL-RECIPIENT-REVIEW-01-v1",
  "record_kind": "external_reference",
  "title": "UCP payment handlers and credential recipients",
  "system": "Universal Commerce Protocol",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Can an agent assume every UCP payment handler sends credentials to the same parties?",
  "near_questions": [
    "Which participants must a UCP payment handler describe?",
    "Can changing a UCP handler change credential acquisition or processing?",
    "Do business and response handler declarations carry identical configuration?",
    "What should be checked before sending a payment token through a new handler?"
  ],
  "supported_claims": [
    {
      "claim": "The UCP payment-handler guide requires each handler specification to identify participants, prerequisites, configuration, acquisition and processing flows. Business, platform and response declarations serve different purposes. The common architecture expects the platform to pass a token or mandate to the business while using the credential provider interface. The handler identity alone does not establish an unchanged credential destination.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "UCP compatibility as certification of credential handling or PCI compliance",
    "The deployed handler and pre-existing provider relationship were not inspected.",
    "Buyer deployment testing, live runtime enforcement, certification or permission to act",
    "Expanded capabilities or licences for existing INDEX executables"
  ],
  "public_summary": "The UCP payment-handler guide requires each handler specification to identify participants, prerequisites, configuration, acquisition and processing flows. Business, platform and response declarations serve different purposes. The common architecture expects the platform to pass a token or mandate to the business while using the credential provider interface. The handler identity alone does not establish an unchanged credential destination.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Guide - Universal Commerce Protocol (UCP)",
    "source_url": "https://ucp.dev/2026-08-25/specification/payment/guide/",
    "checked_on": "2026-10-24",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-UCP-PAYMENT-HANDLER-CREDENTIAL-RECIPIENT-REVIEW-01-v1",
    "candidate_record_sha256": "f9c4c71d8be8fbd06613e87211d79e5552222abc097d06bd025d5a2a8673c1eb",
    "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 UCP payment-handler guide requires each handler specification to identify participants, prerequisites, configuration, acquisition and processing flows. Business, platform and response declarations serve different purposes. The common architecture expects the platform to pass a token or mandate to the business while using the credential provider interface. The handler identity alone does not establish an unchanged credential destination.",
    "required_buyer_context": "Negotiated handler ID, version and specification; Business and credential-provider configuration and endpoints; Credential type, acquisition flow and intended recipient. 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 agent assume every UCP payment handler sends credentials to the same parties?",
    "documented_statement": {
      "status": "documented",
      "statement": "The UCP payment-handler guide requires each handler specification to identify participants, prerequisites, configuration, acquisition and processing flows. Business, platform and response declarations serve different purposes. The common architecture expects the platform to pass a token or mandate to the business while using the credential provider interface. The handler identity alone does not establish an unchanged credential destination.",
      "source_ids": [
        "ucp-payment-guide",
        "ucp-overview"
      ]
    },
    "review_inference": {
      "status": "review_inference",
      "statement": "Review the selected handler configuration and participants before switching the payment-credential path.",
      "source_ids": [
        "ucp-payment-guide",
        "ucp-overview"
      ]
    },
    "buyer_evidence_required": [
      "Negotiated handler ID, version and specification",
      "Business and credential-provider configuration and endpoints",
      "Credential type, acquisition flow and intended recipient"
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not send credentials through a changed handler until its actual recipient and scope are established."
    },
    "unknowns": "The deployed handler and pre-existing provider relationship were not inspected.",
    "unknown_finding": {
      "status": "unknown",
      "statement": "The deployed handler and pre-existing provider relationship were not inspected."
    },
    "evidence_sources": [
      {
        "source_id": "ucp-payment-guide",
        "url": "https://ucp.dev/2026-08-25/specification/payment/guide/",
        "final_url": "https://ucp.dev/2026-08-25/specification/payment/guide/",
        "status": 200,
        "captured_at_utc": "2026-10-24T15:14:46.978Z",
        "sha256": "b0ede8dd589ebf55991bc1b61b49dbd6fe11141841a3a869862dd88f53d3814d",
        "bytes": 226692,
        "title": "Guide - Universal Commerce Protocol (UCP)",
        "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": "UCP specification v2026-08-25, explicitly versioned documentation; deployment applicability must be checked.",
        "reviewed_sections": [
          "Payment handler participants",
          "Credential acquisition and processing"
        ]
      },
      {
        "source_id": "ucp-overview",
        "url": "https://ucp.dev/2026-08-25/specification/overview/",
        "final_url": "https://ucp.dev/2026-08-25/specification/overview/",
        "status": 200,
        "captured_at_utc": "2026-10-24T15:10:54.710Z",
        "sha256": "0898f8e754a4c123766153326f5d0fd5e73937f0e28346829acbde93671d8626",
        "bytes": 565554,
        "title": "Overview - Universal Commerce Protocol (UCP)",
        "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": "UCP specification v2026-08-25, explicitly versioned documentation; deployment applicability must be checked.",
        "reviewed_sections": [
          "Capability negotiation",
          "Authentication and principal binding",
          "Profile caching and versioning"
        ]
      }
    ],
    "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 credential disclosure or payment routing to an unintended participant.",
      "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 credential disclosure or payment routing to an unintended participant.",
    "refusal_conditions": [
      "Do not send credentials through a changed handler until its actual recipient and scope are established."
    ]
  },
  "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 credential disclosure or payment routing to an unintended participant.",
    "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#ucp-payment-handler-credential-recipient-review",
  "machine_readable_record": "/varexis-index/records/ucp-payment-handler-credential-recipient-review.json"
}
