Skip to content
IAM Insights

Explainers · Glossary

Delegated vault token

vault token · delegated payment token

In the Agentic Commerce Protocol, a token a merchant's payment processor issues for one card that an agent platform may use only inside a stated allowance: one merchant, one checkout session, a maximum amount and an expiry.

In our briefings

What our briefings say about Delegated vault token itself, with the most direct claims first.

  1. ACP delegates payment by vaulting a card under a spending allowance. The one mandatory endpoint takes a card (the only credential type "today", as a primary account number or a network token; the security code is optional) and a required one-time allowance: reason, which MUST be one_time, plus max_amount in minor units, currency, checkout_session_id, merchant_id and expires_at. The request must also carry at least one card_testing risk signal with an integer score and a blocked, manual_review or authorized action. It returns a delegated vault token that the merchant's existing processor may use only within that allowance and not after its expiry; payments, settlement and compliance stay on the merchant's rails. The RFC states the constraint and never the mechanism: the conformance checklist asks that an implementation "enforces allowance constraints and expiry" and does not say how.

    The Agentic Commerce Protocol's agent checkout stores a card for one capped purchase, and the RFC never says who issues the caller's tokenBI-FIND-2025-0050

Cited in 1 briefing

Every briefing that discusses this term, newest first.

  1. The Agentic Commerce Protocol's agent checkout stores a card for one capped purchase, and the RFC never says who issues the caller's token

    Article · · Agentic Commerce Protocol (GitHub) · OpenAI et al. · Sep 29, 2025