Mandate (AP2)
Checkout Mandate · Payment Mandate · open mandate · closed mandate · Mandate Pair
In Google's Agent Payments Protocol (AP2), a signed statement of what a person authorized an agent to buy and pay, either naming the exact checkout (closed) or setting limits (open).
In our briefings
What our briefings say about Mandate (AP2) itself, with the most direct claims first.
When the person is not present, AP2 delegates by binding a key. The Shopping Agent has open Checkout and Payment Mandates authorized on a Trusted Surface, where the person approves a set of constraints; the open mandates must carry the agent's public key as a cnf claim, and the spec recommends the shortest expiry that lets the agent finish its task. The agent may then sign the closed mandates with that key, and trust in that key comes from open mandates "signed by the User or a trust list of Agent Providers". The agent must not present another open mandate until it holds a rejection receipt for the previous one, a rule meant to stop one open mandate approving several checkouts. It must also show verifiers only the disclosures they need; today it picks them ad hoc, and the spec names a query language as future help. Delegation from one agent to another is outside the current specification. We read the key binding as the proof-of-possession pattern of workload-identity drafts, applied to a shopping agent.
Google's AP2 v0.2 ties an agent's purchase to the merchant's own signed checkout by hashBI-FIND-2026-0415
The part a verifier has to implement, checking that a closed mandate was derived from the open one a person signed, is delegated to a text the page cites and does not define: "Verify and process the SD-JWT chain according to Delegate SD-JWT", an individual draft by G. Oliver dated 2026. What the page itself fixes is the shape: an open mandate carries constraints and the agent's key as cnf, a closed one is bound to a transaction through a key-binding JWT, the verifier confirms the closed content keeps the open claims and satisfies every constraint, an unknown constraint must fail, and the verifier must return a signed Mandate Receipt whose reference is a hash of the final token. When a mandate holds selective disclosures, the agent must choose the ones that maximize the person's privacy while still providing authorization. Receipts reduce the open mandate's scope on the agent's side only; nothing lets a verifier or a person revoke an open mandate once issued.
Google's AP2 authorization companion lets a verifier trust a credential issuer or the agent's provider, and names no trust list or revocationBI-FIND-2026-0436
Lan, Kaul, Jones and Westrum of eBay argue that AP2 signs payment mandates and gives them an expiry, but leaves two checks to whoever deploys it. In their reading, AP2 "does not require (i) consume-once enforcement" to keep a mandate from executing more than once within its validity window, nor strict binding at execution time to the intended merchant when requests pass through a shared payment-processor endpoint. They read AP2 as Google announced it in September 2025. When we checked the v0.2 specification published in April 2026, the merchant half had moved: the merchant must match a checkout hash to the Checkout JWT it signed, and the processor must check the payment credential is scoped to that checkout. The spend-once half had not. The only reuse rule we found is on the agent, which may not present a second open mandate until the first is rejected; neither v0.2 document tells a verifier to treat a mandate as spent.
eBay researchers say AP2 does not make a payment mandate single-use, so they built a gateway that doesBI-FIND-2026-1085
›Cited in 8 briefings
Every briefing that discusses this term, newest first.
- Verifiable Intent stops an AI agent from passing its buying authority on, and v0.1 has no protocol to revoke it
Article · · Verifiable Intent (GitHub, agent-intent/verifiable-intent) · Verifiable Intent Working Group · Apr 18, 2026
- EMVCo's agent card-payment draft binds no one yet and points to a spec FIDO maintains for proof of consent
Article · · EMVCo · Aug 27, 2026
- Google's AP2 v0.2 ties an agent's purchase to the merchant's own signed checkout by hash
Article · · ap2-protocol.org · Google · Apr 28, 2026
- A new STIR draft would let a number's holder require AI agents calling from it to say so
Draft · · IETF Datatracker · Jon Peterson, TransUnion · Nov 2, 2026
- Nothing carries a person's limits on an agent through to the moment it acts, Yossif's problem statement argues
Draft · · IETF Datatracker · Mohamad Khalil Yossif · Jul 22, 2026
- OpenID experts tell EMVCo an agent's payment can look like the cardholder's, and no one vouches for the agent
Article · · OpenID Foundation · Serj Hallam et al. · Oct 8, 2026
- Google's AP2 authorization companion lets a verifier trust a credential issuer or the agent's provider, and names no trust list or revocation
Article · · ap2-protocol.org · Google · Apr 28, 2026
- eBay researchers say AP2 does not make a payment mandate single-use, so they built a gateway that does
Paper · · arXiv · Qianlong Lan et al. · Feb 6, 2026
Related terms
What appears alongside Mandate (AP2) in the same briefings.