Short answer
AP2, the Agent Payments Protocol, is an open protocol Google announced in September 2025 to prove that a person really authorized an AI agent's purchase. On April 28, 2026, the FIDO Alliance announced that Google had contributed AP2 to it, alongside Mastercard's Verifiable Intent framework, and said its working groups would develop standards. For most stores, AP2 arrives through checkout standards such as UCP rather than as a separate project.
Key takeaways
- AP2 proves what a shopper authorized, using signed mandates.
- Google contributed AP2 to the FIDO Alliance in April 2026.
- Stores usually meet AP2 inside UCP checkout, not on its own.
What is AP2?
AP2, the Agent Payments Protocol, is an open protocol for proving that a person really authorized a purchase an AI agent makes. Google announced it on September 16, 2025, and said it was developed with "more than 60 organizations."
Google framed the problem in three parts:
- Authorization: "Proving that a user gave an agent the specific authority to make a particular purchase."
- Authenticity: "Enabling a merchant to be sure that an agent's request accurately reflects the user's true intent."
- Accountability: "Determining accountability if a fraudulent or incorrect transaction occurs."
AP2 is not a checkout or a payment network. It is a layer of signed evidence that sits around a purchase. Google said "The protocol can be used as an extension of the Agent2Agent (A2A) protocol and Model Context Protocol (MCP)." For how it compares with ACP, UCP and x402, see the four ways AI agents pay, compared.
Why did AP2 move to the FIDO Alliance?
Google says it contributed AP2 to an industry body to keep it open and community-led. On April 28, 2026, the FIDO Alliance, the industry group known for its work on passkeys, announced: "Google has contributed its Agent Payments Protocol (AP2), which introduces a model for secure delegation" and trusted transactions.
Google's Stavan Parikh, VP/GM, Payments, said in the release that contributing AP2 to "a trusted industry association like the FIDO Alliance ensures it stays open, platform-agnostic, and community-led".
FIDO's executive director and CEO, Andrew Shikiar, said: "To scale this safely, people need to trust that these actions are secure, authorized and truly reflect their intent."
Two FIDO working groups are involved:
- Agentic Authentication Technical Working Group. It is "focused on how users securely and privately delegate actions" to AI agents, while keeping strong, phishing-resistant sign-in. FIDO says it is chaired by members from CVS Health, Google and OpenAI, and vice-chaired by members from Amazon, Google and Okta. The AP2 site says standardization will continue within this group and the Payments Technical Working Group below.
- Payments Technical Working Group. FIDO says it "is developing specifications for agent-initiated commerce," chaired by members from Mastercard and Visa.
FIDO gave no timeline. It said work has started and that it will report as it progresses.
How do AP2 mandates work?
A mandate is a signed record of what a person authorized an agent to do. Because it is signed, it cannot be quietly changed later. For a short definition, see what an agent mandate is.
Google's 2025 announcement described two mandates:
- An Intent Mandate records what the person asked for. For a task done while the person is away, they sign it up front. Google said it sets the "rules of engagement," such as price limits, timing and other conditions.
- A Cart Mandate is signed when the person approves a cart. Google said it "creates a secure, unchangeable record of the exact items and price, ensuring what you see is what you pay for."
The current AP2 site uses newer names. It describes a Checkout Mandate and a Payment Mandate, each with an open stage and a closed stage:
| Mandate | Open stage | Closed stage |
|---|---|---|
| Checkout Mandate | "Captures the user's constraints and goals for the transaction before a specific cart is finalized for autonomous execution." | Authorizes a specific, finalized checkout |
| Payment Mandate | Captures limits on payment, such as budget and allowed payment methods | Authorizes a specific amount bound to a finalized checkout |
The names changed, but the idea did not: a signed limit first, then a signed approval of the exact purchase. Expect the terms to keep shifting while FIDO works on the standard.
How does AP2 relate to UCP?
UCP, the Universal Commerce Protocol, is where most stores are likely to meet AP2. UCP handles the checkout. AP2 provides the signed proof of what the shopper approved. The AP2 site lists UCP as a related integration.
UCP carries AP2 through an "AP2 Mandates extension." UCP's spec says it "enables the secure exchange of user intents and authorizations." When both the store and the shopping platform turn it on, the checkout becomes locked to signed terms. The spec, at version 2026-08-25 at the time of writing, sets these rules for the store:
- "Businesses MUST embed a cryptographic signature in checkout responses," so the shopper's side can confirm the terms are genuine.
- The shopper's side returns a signed checkout mandate, and the payment mandate travels with the payment credential to the payment provider.
- The store must refuse to complete a checkout that arrives without the checkout mandate, and must check that the signed terms match the live session.
The extension only switches on when both sides say they support it. A store that has not turned it on runs a normal UCP checkout.
Where do the card networks fit in?
The card networks are part of the same FIDO effort, but the sources say little about how AP2 will run on their rails. Here is what they do say.
- Mastercard. FIDO says "Mastercard has contributed its Verifiable Intent framework, co-developed with Google and designed to work with AP2." Mastercard's Chief Digital Officer, Pablo Fourez, said: "For agent-initiated commerce to scale, user intent must be explicit, verifiable and trusted".
- Visa. Visa co-chairs FIDO's Payments Technical Working Group with Mastercard, and a Visa executive is quoted in the release.
- American Express. Amex also gave a quote in the release, referring to its Amex Agentic Commerce Experiences (ACE) Developer Kit.
On payment types, sources differ by date. Google's 2025 announcement said AP2 supports types "from credit and debit cards to stablecoins and real-time bank transfers," and launched an A2A x402 extension for crypto payments. The current AP2 site says the initial version "supports common 'pull' payment methods like credit and debit cards," with e-wallets, bank transfers and digital currencies on the roadmap. Cards come first.
What does AP2 moving to FIDO mean for your store?
In the short term, very little changes for most merchants. AP2 is still early, and you are more likely to receive mandates through a platform or a UCP checkout than to build AP2 yourself.
Over time, the move matters in three ways:
- Broader backing. Members from Google, Mastercard, Visa, OpenAI and Amazon chair or vice-chair FIDO's working groups. That gives AP2 wider backing than a single-company project.
- Better evidence in disputes. A signed record of the exact items and price gives you something concrete to check when an agent order is questioned.
- Something to set rules on. A mandate states a budget and an approved cart. You can approve orders that match, decline ones that don't, and hold unusual ones for review.
What to do now:
- Ask your platform or payment provider whether its UCP checkout supports the AP2 Mandates extension.
- Keep records of agent orders, including any mandate that came with them.
- Watch FIDO's reports. Names and fields may change before the standard settles.
Agent payments also depend on knowing which agent is acting. For that side, see Know Your Agent (KYA). This article explains the protocol and is not legal or payments-compliance advice.
How Sill helps
When an AI agent places an order, Sill applies your rules to approve it, decline it, or hold it for a person to review, and every decision is signed and recorded. AP2 mandates are evaluated at Sill's edge, and Sill's UCP checkouts, on sites with a connected Stripe account, carry signed merchant terms and verify shopper-signed AP2 mandates. You can start with a free readiness scan.
Questions people ask
Is AP2 still a Google project?
Google created AP2 and contributed it to the FIDO Alliance, announced on April 28, 2026. The AP2 site says standardization will continue within FIDO's Agentic Authentication Technical and Payments Technical Working Groups.
What is Mastercard Verifiable Intent?
The FIDO Alliance describes it as a framework, co-developed with Google and designed to work with AP2, that lets users authorize and control what agents do on their behalf. Mastercard contributed it to FIDO at the same time as AP2.
Does AP2 support stablecoins?
Google's 2025 announcement said AP2 supports payment types from cards to stablecoins and real-time bank transfers, and launched an A2A x402 extension for crypto payments. The current AP2 site says its initial version supports cards, with e-wallets, push payments and digital currencies on its roadmap.
Is AP2 a finished standard?
No. The AP2 site refers to a v0.2 release, and the FIDO Alliance says its work has started and it will report on progress. FIDO gave no completion date.
Sources
- FIDO Alliance: FIDO Alliance to Develop Standards for Trusted AI Agent Interactions · checked 16 Nov 2026
- Google Cloud: Announcing Agent Payments Protocol (AP2) · checked 16 Nov 2026
- AP2: Agent Payments Protocol · checked 16 Nov 2026
- AP2 on GitHub · checked 16 Nov 2026
- Universal Commerce Protocol: AP2 Mandates extension · checked 16 Nov 2026