AP2 Checkout Mandate: open before the cart, closed at checkout
The Agent Payments Protocol now defines a Checkout Mandate in two forms. What each captures, who signs what, and what the merchant verifies.
The Agent Payments Protocol (AP2) is an open protocol for agent commerce, available as an extension for A2A and the Universal Commerce Protocol. Its documentation now describes version 0.2 and announces a donation to the FIDO Alliance for standards work. Earlier descriptions used "intent" and "cart" mandates; the current documentation defines a Checkout Mandate and a Payment Mandate, each open or closed.
The Checkout Mandate authorises the completion of a checkout:
- An open Checkout Mandate captures the user's constraints and goals before a specific cart exists, for example which merchants are allowed and which line items are acceptable.
- A closed Checkout Mandate captures authorisation for one finalised checkout. It contains the merchant-signed checkout and a hash that identifies it.
The shopping agent creates the mandate content, a trusted surface renders it to the user, and the merchant verifies it. Mandates are verifiable digital credentials, encoded as SD-JWT, so some fields can be disclosed selectively.
In a finance flow, an open mandate lets a customer say "these trainers or those, from these two shops"; the agent can then shop within those limits, and the merchant receives proof that the final cart fits.
Limits. AP2 is at version 0.2 and still changing. The checkout payload itself is outside the AP2 specification (it is the UCP checkout object when used with UCP). The documentation notes that the line-item constraint does not support splitting one open mandate across several checkouts.
Sources: Agent Payments Protocol (AP2) documentation, Agent Payments Protocol (AP2): Checkout Mandate, Agent Payments Protocol (AP2): glossary