The AP2 protocol (Agent Payments Protocol) is an open standard, started by Google and now developed at the FIDO Alliance, that lets an AI agent pay for you using signed “mandates” that record exactly what you approved. As of November 16, 2026, the latest release is version 0.2 from April 28, 2026, and Google says AP2 will come to its own products starting with Gemini Spark, but no Google shopping feature lists it as live yet.
This guide covers the current status, how the mandates work, where AP2 sits next to Google’s Universal Commerce Protocol (UCP), and what it means if you shop with an AI agent.
AP2 status in November 2026
Checked November 16, 2026, against the project’s own pages and Google’s announcements.
| Question | Status | Source |
|---|---|---|
| Latest version | v0.2.0, released April 28, 2026. The only earlier release is v0.1.0 from September 16, 2025. | GitHub releases |
| Who runs it | Google donated AP2 to the FIDO Alliance in April 2026. Work on the specification continues in FIDO’s Agentic Authentication and Payments Technical Working Groups. | ap2-protocol.org |
| What is live | The specification, a Python SDK and sample agents on GitHub. The samples mock real payment providers, and an SDK and MCP server built with payment companies are still in progress. | AP2 FAQ, GitHub |
| Payment methods | Cards and other “pull” payments today, plus sample flows for x402 and Android digital payment credentials. E-wallets, real-time bank transfers such as UPI and PIX, and digital currencies are on the roadmap. | ap2-protocol.org |
| Relationship to UCP | Offered as an extension to UCP, where it acts as the payment authorization layer of a checkout. | UCP documentation |
| Google products | On May 19, 2026, Google said it would begin bringing AP2 to its products “in the coming months, starting with Gemini Spark.” Google’s Universal Cart launched in the U.S. on October 15, 2026, with checkout powered by UCP and Google Pay; the launch post does not mention AP2. | Google, May 19, Google, October 15 |
| What a shopper sees | Nothing labeled AP2. In Google’s AI shopping you buy through Universal Cart or checkout in AI Mode and the Gemini app, and Gemini asks you to confirm before it makes a purchase. | Gemini Apps Help |
What AP2 is, and who is behind it
AP2 is a set of rules for messages, not an app or a wallet. When an AI agent shops for you, the agent, the merchant, whoever holds your card details and the payment network all need to trust each other. Google’s launch post of September 16, 2025 framed this as three problems: authorization (did you give the agent this authority?), authenticity (does the request match what you wanted?) and accountability (who answers for a fraudulent or wrong purchase?). Google built AP2 as an extension of its Agent2Agent (A2A) protocol and of the Model Context Protocol (MCP), and named more than 60 partners at launch, including Mastercard, American Express, PayPal, Adyen, Coinbase, Revolut and Etsy. A partner list is not the same as live support.
On April 28, 2026, Google donated AP2 to the FIDO Alliance, saying the move keeps AP2 “platform-agnostic and community-led,” and released version 0.2 at the same time. The FIDO Alliance announced it the next day. Google’s post also says Mastercard co-developed a compatible standard, Verifiable Intent, which is going to FIDO too.
So “Google AP2” today means a protocol Google started and still builds on, now run as a shared industry standard.
AP2 mandates, explained
A mandate is a digitally signed record of what you allowed. Once you sign it, any edit is detectable. The specification says mandate content is “created by the Shopping Agent, rendered to the User by the Trusted Surface and verified by the Merchant.” The trusted surface is the screen where you confirm, such as a wallet or your phone’s payment prompt, not the chat window.
At launch, Google described an Intent Mandate (your request and any limits) and a Cart Mandate (the exact items and price, so “what you see is what you pay for”). Version 0.2 renames and reorganizes these into two mandates, each with an open form and a closed form:
| Mandate | Open form (your limits) | Closed form (one transaction) |
|---|---|---|
| Checkout Mandate | Which merchants are allowed and which items the basket may contain | One specific checkout, including a checkout object the merchant signs |
| Payment Mandate | Budget, allowed payment methods and how often the agent may reuse it | One payment: payee, amount, payment method and a hash that ties it to the exact checkout |
The closed Payment Mandate is checked by the credential provider, the card network and the merchant’s payment processor. Because it carries a hash of the checkout, an approval for one basket cannot be reused for another. The open Payment Mandate can also allow repeat use, with a frequency from daily to annually, or on demand, and an optional cap on the number of uses (specification).
Human present and human not present
AP2 covers two cases. In a human-present purchase, you approve the final basket and the payment runs against it. In a human-not-present purchase, you sign conditions in advance and the agent buys when they are met, without asking again. Google says version 0.2 adds support for the second case. Google’s example is buying limited-run tickets the moment they go on sale (Google), and its May 2026 shopping post describes the same idea for consumers: you name the brands, products and spending limit, and the agent buys only when those criteria are met (Google).
AP2 and UCP: two layers, both from Google
The two get mixed up because Google is behind both. The AP2 FAQ separates them: UCP runs the shopping and checkout flow and “enables native buying on AI Mode and Gemini,” while AP2 is the layer that authorizes and signs the payment. The FAQ points merchants who want checkout inside Google’s AI surfaces to UCP, and points autonomous or agent-to-agent payments outside those surfaces to AP2.
They also work together. The UCP documentation calls AP2 “the trust layer for agent-led transactions.” When a merchant turns on the AP2 extension in a UCP checkout, the merchant signs the checkout, the platform creates a Checkout Mandate and a Payment Mandate after you consent, the merchant verifies the first and the payment processor verifies the second.
For how Google’s UCP compares with OpenAI’s Agentic Commerce Protocol (ACP) in ChatGPT, see ACP vs UCP. For who supports AP2, ACP, x402 and the card network programs this month, see the agentic commerce protocols tracker.
AP2 and x402
x402 is a way for software to pay per request in stablecoins over the web. At launch, Google said it had released an “A2A x402 extension” with Coinbase, the Ethereum Foundation, MetaMask and others (Google Cloud). That code lives in a separate repository, which describes itself as bringing crypto payments to A2A and is at specification version 0.1. The AP2 project itself includes human-present and human-not-present x402 sample flows (ap2-protocol.org).
What AP2 means for you as a shopper
You do not install AP2 or sign up for it. If it reaches you, it will be inside an assistant, wallet or checkout you already use, and what you would notice is a confirmation screen outside the chat showing the exact basket and price. Today, buying through Google’s AI shopping features runs on UCP and Google Pay; our guide to shopping in Google AI Mode explains that checkout.
Three parts of AP2’s design matter for you:
- Your approval becomes evidence. The FAQ says a card network can compare your signed Checkout Mandate with the disputed transaction. That can support you if an agent bought outside your limits, and it can count against you if you dispute a purchase you did sign.
- Limits are meant to hold. The security section says checks on the closed mandates keep “worst-case financial and logical impacts” strictly bounded, even if the agent is misled.
- Less of your data travels. The FAQ describes payload encryption and selective disclosure so shopping agents do not see card numbers or other sensitive details.
AP2 does not set refund or liability rules. Those still come from your card issuer, the merchant and consumer law. Our guide to an AI agent purchase gone wrong covers refunds and chargebacks.
What to watch out for
- It is early. The version number is 0.2, the samples use mocked payment providers, and the SDK and MCP server are still being built (FAQ).
- Prompt injection is assumed, not solved. The specification says “all LLMs and Agents MUST be considered potential attackers” and that AP2 “assumes that preventing prompt injection attacks is infeasible” (specification). AP2 caps the damage with signed limits. It does not stop an agent from making a poor choice inside those limits.
- Broad pre-approvals carry more risk. A human-not-present mandate with many merchants and a high budget gives an agent a lot of room. Narrow limits are the safer default.
- Implementation matters. A Cloud Security Alliance analysis flagged mandate spoofing and agent hijacking as risks, and recommended hardware-backed signing keys, key rotation and strong customer authentication.
- Names changed. Articles from 2025 describe Intent and Cart Mandates. Version 0.2 uses Checkout and Payment Mandates for the same idea.
If you run a business and are deciding whether to support AP2, ask your payments provider what it supports today.
How we checked this
We read the AP2 specification, FAQ and GitHub releases, the UCP documentation, Google’s announcements from September 2025 to October 2026, the Gemini Apps help center and an independent security analysis from the Cloud Security Alliance. Facts checked on November 16, 2026.
Changelog
November 16, 2026: Added an answer-first summary and an AP2 status table for November 2026; added Google’s May 2026 plan to bring AP2 to Gemini Spark and the October 15, 2026 U.S. launch of Universal Cart on UCP; corrected the x402 extension description, the repeat-use options and a quote from the security section; replaced the protocol comparison table with links to our comparison pages; rewrote the Questions.





