Definition
The Agent Payments Protocol (AP2) is an open protocol for payments made by AI agents. It records what the user authorized in signed mandates, so a merchant or payment provider can check that a purchase matches the user's instructions. Google announced it in September 2025 and contributed it to the FIDO Alliance in April 2026.
Why it matters
When an AI agent pays for something, the hard question is whether the person really asked for it. AP2 answers that with signed records of the person's instructions. If an order is disputed later, there is evidence of what was approved, not just a claim from the agent.
For a store, those records are also something to check before accepting an order. If the cart matches the signed limits, the order fits what the shopper asked for. If it doesn't, you have a clear reason to decline it or hold it for review.
How it works
Google announced AP2 on September 16, 2025, as "an open protocol developed with leading payments and technology companies to securely initiate and transact agent-led payments across platforms." It said more than 60 organizations were helping shape it.
The core idea is the agent mandate. Google's post describes two kinds:
- Intent Mandate: captures what the user asked for. For tasks where the user isn't present, it sets the "rules of engagement", such as price limits and timing.
- Cart Mandate: records a specific cart. The user signs it on approval, or, for a delegated task, the agent generates it once the Intent Mandate's conditions are met. Google calls it "a secure, unchangeable record of the exact items and price."
AP2 doesn't stand alone. Google says it can be used as an extension of A2A and MCP. Google also launched an A2A x402 extension for agent payments in crypto, built on AP2's core ideas, and its developer blog says UCP is compatible with AP2.
On April 28, 2026, the FIDO Alliance announced that Google had contributed AP2, and Mastercard its Verifiable Intent framework. FIDO said both contributions would be reviewed and developed further in its Payments Technical Working Group. See AP2 moves to the FIDO Alliance.
Example
A shopper tells an agent: "Book the cheapest refundable train ticket to Leeds on Friday, up to £80." That instruction is signed as an Intent Mandate. The agent finds a £64 ticket on your site, builds the cart and sends it with the mandate. Your checkout can confirm that £64 is within the signed £80 limit before taking payment. For how AP2 compares with other payment standards, see ACP, AP2, UCP and x402 compared.
Sources
- Google Cloud: Announcing Agent Payments Protocol (AP2) · checked 16 Nov 2026
- FIDO Alliance to develop standards for trusted AI agent interactions · checked 16 Nov 2026
- Google Developers Blog: Under the hood of the Universal Commerce Protocol (UCP) · checked 16 Nov 2026