Agent Payments Protocol (AP2)
AP2, the open protocol for proving user authorization of agent payments with signed mandates; now developed at the FIDO Alliance.
In short: The Agent Payments Protocol (AP2) gives every party in an agent-made payment cryptographic proof of what the user authorized. It does this with signed digital records called mandates. Google announced AP2 in September 2025 with more than 60 partners. In April 2026 it released version 0.2, which restructured the mandates and added support for agents paying without the user present, and contributed the protocol to the FIDO Alliance.
The problem AP2 addresses
Card payments assume a person is present: they enter details, pass 3-D Secure (the card-network step-up authentication), and the merchant sees a human checkout. When an agent pays, issuers, merchants and networks lose that signal. They need to answer three questions:
- Authorization: did the user actually allow this purchase?
- Authenticity: does the agent’s request match what the user wanted, or could the model have made a mistake or been manipulated?
- Accountability: if something goes wrong, who is responsible, and what evidence settles the dispute?
AP2’s answer is to replace inferred intent with signed, verifiable evidence that travels with the transaction. It is payment-method agnostic. It is not a checkout API. It is a trust layer meant to sit under checkout protocols such as UCP.
Mandates
A mandate is a tamper-evident, cryptographically signed digital object. AP2 builds mandates as verifiable digital credentials (VDCs), a W3C-style format for signed claims that any party can check.
Version 0.1 (2025): intent, cart and payment
The original design described three mandates:
| Mandate | What it records |
|---|---|
| Intent Mandate | The user’s instruction and limits, for example “buy these concert tickets when they go on sale, up to $200” |
| Cart Mandate | The exact items and price the user (or agent, within the intent) approved, signed so it can’t be altered |
| Payment Mandate | Information shared with the payment network and issuer, showing an agent was involved and whether the user was present |
Version 0.2 (April 2026): checkout and payment, open and closed
AP2 v0.2 replaced the Intent and Cart Mandates with two mandate types, each with two stages:
| Mandate | Open (constraints) | Closed (specific transaction) |
|---|---|---|
| Checkout Mandate: what is being bought | The user’s constraints and goals before a cart exists | Bound to a final checkout the merchant has signed |
| Payment Mandate: authorization against a payment instrument | Spending constraints for later autonomous use | Bound to a specific amount and payee |
Open mandates must include the agent’s public key and should include an expiry. The spec also stops an agent from presenting a second mandate for the same approval until it has a rejection receipt, which prevents double use.
Each party checks a different part. The merchant verifies the Checkout Mandate. The credentials provider verifies the Payment Mandate. The payment processor checks that the credential’s scope matches the checkout. In a dispute, each component can be validated on its own against the hashes it references.
Roles
The v0.2 specification defines five roles:
- Shopping agent: finds products, builds the checkout, and executes the purchase.
- Credentials provider: holds the user’s payment credentials (for example a wallet or issuer) and lets the agent use them.
- Merchant: presents and completes the checkout and checks that the user approved it.
- Merchant payment processor: processes the payment and validates the credentials.
- Trusted surface: a non-agentic user interface, such as a wallet or bank app, where the user reviews and signs mandates.
Sensitive payment data is kept away from the shopping agent. The spec warns that whenever a role is played by an agent, that agent must be treated as a possible attacker.
Human present and human not present
AP2 supports two modes:
- Human present (direct): the user sees and approves the closed Checkout and Payment Mandates before submission. Example: “find me white running shoes,” then the user confirms the cart.
- Human not present (autonomous): the user signs open mandates with constraints in advance. The agent later creates closed mandates within those limits without asking again. Example: buying limited-release tickets the moment they go on sale.
Version 0.2 made human-not-present payments a supported flow. For issuers and merchants, the signed open mandate is the evidence that the user agreed in advance. How this maps to liability and chargeback rules is still up to networks and regulators. See consumer protection and liability.
Relationship to A2A, MCP and UCP
- A2A: AP2 was first published as an extension of the Agent2Agent protocol. Google describes it as part of a family of protocols built on A2A’s extension model.
- MCP: Google’s launch materials also position AP2 for use with the Model Context Protocol, so agents can call mandate-aware payment tools.
- UCP: the Universal Commerce Protocol defines an AP2 mandates extension for autonomous, agent-signed transactions. The AP2 site describes AP2 as extending both A2A and UCP.
- ACP: ACP solves a different problem, the checkout API and delegated payment tokens. The two are not formally linked. Networks and PSPs say they aim to support both.
The x402 extension
At launch, Google released an x402 extension for agent payments in stablecoins and other crypto, built with Coinbase, the Ethereum Foundation, MetaMask and others. It lets the same mandate model authorize payments settled through x402, Coinbase’s HTTP 402 payment protocol. The AP2 documentation lists cards and x402 as supported, with e-wallets and real-time bank transfers on the roadmap.
Governance: the move to FIDO
On April 28, 2026, Google contributed AP2 to the FIDO Alliance, the industry body behind passkeys. The aim was to make AP2 platform-neutral. FIDO is developing standards through new technical working groups on agentic authentication and payments. In the same announcement, Google and Mastercard said Mastercard’s Verifiable Intent framework would also go to FIDO. Verifiable Intent is a record of user-authorized agent actions designed to work with AP2.
Partners
Google’s September 2025 launch named more than 60 organizations, including Adyen, American Express, Ant International, Coinbase, Etsy, Forter, Intuit, JCB, Mastercard, Mysten Labs, PayPal, Revolut, Salesforce, ServiceNow, UnionPay International and Worldpay. As of October 2026, AP2 is still pre-1.0. Most public deployments are pilots, reference implementations and integrations through UCP. Reference code is available in Python, Go and Android.
What it means in practice
- Merchants don’t usually integrate AP2 directly. It arrives through a checkout protocol (UCP), a PSP or a network program.
- Issuers and wallets are natural credentials providers and trusted surfaces. They are the parties best placed to show the user what they are signing.
- Agent developers need to handle key management for mandate signing and keep payment credentials out of the model’s context.
Sources
- Announcing Agent Payments Protocol (AP2) — Google Cloud Blog
- AP2 documentation — ap2-protocol.org
- Agentic Payment Protocol (v0.2) specification — ap2-protocol.org
- AP2 repository — GitHub
- Google donates Agent Payments Protocol to FIDO Alliance — Google
- Google and Mastercard contribute agentic commerce standards to FIDO Alliance — PYMNTS
- Overview — Universal Commerce Protocol
- A year of open collaboration: Celebrating the anniversary of A2A — Google Open Source Blog