AP2, Google's Agent Payments Protocol, answers one question: when an AI agent pays for something, how does everyone involved know you actually approved it? Its answer is the mandate, a signed digital record of your instructions that travels with the purchase. This guide explains AP2's mandates in plain English, based on the published spec at ap2-protocol.org and Google's launch announcement.

What is AP2?

AP2 is an open protocol, licensed under Apache 2.0, that Google announced on 16 September 2025 with more than 60 partners. Google describes it as an extension of its Agent2Agent (A2A) protocol, and it is designed to work with any payment type, from cards to bank transfers.

Mastercard was a named launch collaborator: its chief digital officer, Pablo Fourez, is quoted in Google's announcement. We found no comparable Visa statement on AP2, although Visa endorses Google's separate UCP standard.

AP2 announced by Google
16 Sep 2025
Launch partners
60+
Mandate types: Checkout and Payment
2
Current spec release
v0.2

What problem does AP2 solve?

Card payments were built on the assumption that a person is pressing "pay". When an agent presses it instead, a bank or store faces new questions:

  • Did the user really authorise this purchase, or did the agent misread the request?
  • Was the agent tricked by a malicious web page into buying something else?
  • If there is a dispute, who is accountable?

AP2's approach is to make authorisation verifiable. Instead of trusting the agent's word, the merchant and payment network can check a signed mandate.

What are AP2 mandates, in plain English?

The current spec describes two mandate types, each with two stages.

Mandate What it covers Open stage Closed stage
Checkout Mandate What is being bought, from whom, at what price Rules set in advance, e.g. "these trainers, size 10, under $120" Your approval of one specific final cart
Payment Mandate Authorisation of the payment itself Spending limits for an autonomous purchase Approval of one exact payment amount

Think of the open stage as a signed shopping brief and the closed stage as a signed receipt you approved before paying.

Launch-era materials called these the Intent Mandate, Cart Mandate and Payment Mandate. If you read older coverage, the Intent Mandate maps to the open stage and the Cart Mandate to the closed Checkout Mandate.

How does a mandate actually prove anything?

Mandates are cryptographically signed, so they can't be quietly edited after you approve them. Coverage of the spec describes them as verifiable credentials using the SD-JWT format, which allows selective disclosure: a merchant can confirm what it needs without seeing everything. The signed record creates an audit trail if a purchase is later disputed.

How does an AP2 purchase flow?

When you are present

  1. You askThe agent hears "find me a rain jacket under $150".
  2. Agent shopsIt finds options and builds a cart with a merchant.
  3. You approve the cartYour approval is signed as a closed Checkout Mandate.
  4. Payment authorisedA Payment Mandate goes with the transaction to the network and your bank.
  5. Store fulfilsThe merchant charges, ships and handles returns.

When you are not present

AP2 also covers delegated buying. You sign an open mandate in advance, for example "buy these concert tickets the moment they go on sale, up to $200 each". The agent can complete the purchase without you watching, but only within the signed limits. Anything outside them is invalid.

Google's own agentic checkout, launched in November 2025, shows the consumer version of this idea: you track a product with a size, colour and budget, and Google can buy it with Google Pay when the price drops. Google says it will "always ask for your permission first", so in practice that feature still asks you to confirm.

Where does AP2 stand in November 2026?

  1. Google announces AP2 with 60+ partners, including Mastercard
  2. Google launches agentic checkout with Google Pay in the US
  3. Revolut Pay reported to join AP2
  4. Google announces UCP at NRF; AP2-plus-UCP guidance follows

Since then, AP2 has published a v0.2 release and been donated to the FIDO Alliance.

The GitHub repository has no tagged releases, and most consumer-facing activity has moved to Google's Universal Commerce Protocol, which handles checkout and orders. AP2 is positioned as the payment-authorisation layer underneath. The move to the FIDO Alliance, the body behind passkeys, suggests AP2 is meant to become a neutral industry standard rather than a Google product.

How is AP2 different from ACP and UCP?

ACP (OpenAI and Stripe) and UCP (Google, Shopify and a large retailer group) both define how an agent places an order with a store. AP2 is about proving the payment was authorised. You could, in principle, check out via UCP and carry an AP2 mandate for the payment. Our ACP vs AP2 vs UCP comparison sets out the differences, and the agentic checkout walkthrough shows what you actually see.

What does AP2 mean for shoppers?

Pros

  • A signed record of what you approved helps if a purchase is disputed
  • Open mandates make hands-off buying possible within hard limits
  • Open standard, now at the FIDO Alliance, not tied to one company

Cons

  • Few consumer products describe their AP2 use directly
  • No tagged GitHub releases; still early
  • Protocol limits don't replace your card's dispute rights

For now, you will mostly meet AP2's ideas through Google's shopping features; see Gemini Spark shopping. A signed mandate is strong evidence, but your normal card protections still apply. If an agent buys something you didn't want, the steps in how to return something your AI agent bought cover returns and chargebacks. The card-network side is covered in Mastercard Agent Pay, and merchants can start with UCP and AP2 integration.

Bottom line

AP2 turns "the agent says you approved it" into "here is your signed approval". Its two mandates, Checkout and Payment, each come in an open form for rules set in advance and a closed form for one exact purchase. It is early, overshadowed in shopping by UCP, and moving to the FIDO Alliance, but the idea of carrying cryptographic proof of consent is likely to shape how delegated agent payments work. For a wider view of agent payment methods, see the payments explainer on Get Personal AI Agents.