# What Is AP2 (Agent Payments Protocol) from Google?

> What AP2 is, Google's protocol for letting an AI agent pay for you: how its mandates work, what is available today and what has only been announced.

URL: https://clione.ai/glossary/ap2/
Lang: en

AP2 stands for Agent Payments Protocol, the payments protocol for agents that Google introduced. It matters for a very store-shaped reason: when whoever clicks "pay" is an [AI agent](/glossary/ai-agent/) and not a person, **the store needs to know someone authorized that purchase**, because if the charge is disputed, someone will have to prove it. AP2 is Google's proposal, built with its partners, for carrying that proof along with the order.

## How it works

Google introduced it on September 16, 2025 as an open protocol, developed with payments and technology companies, for starting and completing agent-led payments across different platforms, with more than 60 organizations collaborating, among them Adyen, American Express, Mastercard, PayPal, Revolut and Worldpay.[^google-ap2-launch] Its official site now describes it as an extension of the [A2A](/glossary/a2a/) and [UCP (Universal Commerce Protocol)](/glossary/ucp/) protocols.[^ap2-site]

The v0.2 specification splits the work across five roles:[^ap2-spec]

- **The [Shopping Agent](/glossary/shopping-agent/)**: finds products, builds the cart and runs the purchase.
- **The Credential Provider**: the source of the payment details, which checks that the agent is authorized.
- **The Merchant**: prepares and closes the order, and checks that the agent has permission to buy those items.
- **The Merchant Payment Processor**: processes the charge and verifies the credential's authorization.
- **The Trusted Surface**: the screen where the person gives consent. The specification requires that it not be agentic.

The central piece is the mandates, signed records of what the person authorized (the [AP2 mandate](/glossary/ap2-mandate/) has its own entry). In v0.2 there are two: **the checkout mandate**, which proves to the store that the agent may buy that cart, and **the payment mandate**, which proves to the credential provider, the network and the processor that it may pay for it.[^ap2-spec] Each can be open, when it captures the conditions the person sets before any cart exists, or closed, when it authorizes one specific order and amount.[^ap2-site] Mandates are signed as SD-JWT, a credential format that lets you reveal only part of the data.[^ap2-spec]

With those pieces, AP2 describes two ways to buy:[^ap2-flows]

1. **With the person present** (_Human Present_): the person sees the finished order and approves the checkout and the payment directly, for example with a fingerprint.
2. **Without the person present** (_Human Not Present_): the person first signs open mandates with their limits and walks away. The agent, on its own, builds an order that meets those conditions and signs the closed mandates itself. This is what is called [delegated payments](/glossary/delegated-payments/).

If the store or the credential provider sees that the order does not fit the signed conditions, they can return an unresolved-constraint error and **force the person to approve it again**.[^ap2-flows]

## What is available and what is only announced

The protocol moves fast, and its own documents have changed from one version to the next. This is where things stand as of October 6, 2026:

| Date               | What happened                                                                                                                                      | Status                       |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------- |
| September 16, 2025 | Google announces AP2 and publishes v0.1 on GitHub[^google-ap2-launch][^ap2-releases]                                                               | Available                    |
| January 11, 2026   | Google introduces UCP and declares it compatible with AP2 for agent payments[^google-ucp]                                                          | Available as a specification |
| April 28, 2026     | v0.2 ships, focused on purchases without the person present[^ap2-releases]                                                                         | Available                    |
| April 28, 2026     | Google hands AP2 to the FIDO Alliance, which creates two technical working groups, one on agentic authentication and one on payments[^fido-agents] | In progress, no end date     |
| Roadmap            | E-wallets, instant transfers such as UPI or PIX, and digital currencies[^ap2-site]                                                                 | Announced                    |

Watch the payment methods. The 2025 announcement said AP2 supported different payment types, from credit and debit cards to _stablecoins_ and instant transfers.[^google-ap2-launch] The official site, which is more recent, is more precise: **the initial version supports "pull" payments such as cards**, and the rest is on the roadmap.[^ap2-site] When two texts from the same owner disagree, the newer one wins. The FIDO Alliance, for its part, says it is already working on those groups and will report as it progresses, with no dates.[^fido-agents]

## In a store

A **fictitious example** of the flow without the person present, in a coffee shop. The customer tells her agent: "Buy a kilo of Ethiopian whole-bean coffee when it drops below 30 dollars." Step by step, following the flows AP2 publishes:[^ap2-flows]

| Step | Who                          | What happens                                                                                               |
| ---- | ---------------------------- | ---------------------------------------------------------------------------------------------------------- |
| 1    | Customer and trusted surface | Approves, with her fingerprint, an open checkout mandate and an open payment mandate with those conditions |
| 2    | Shopping Agent               | Watches the price, finds the offer, builds the cart at the store and reaches payment                       |
| 3    | Merchant                     | Creates a signed checkout and asks for a valid mandate to continue                                         |
| 4    | Shopping Agent               | Picks the open mandates that fit and signs the closed ones, linked to each other                           |
| 5    | Credential Provider          | Verifies the payment mandate and hands over a payment credential limited to that purchase                  |
| 6    | Merchant                     | Checks that the checkout mandate matches the current cart and starts the charge                            |
| 7    | Payment processor            | Verifies the mandate and returns the payment receipt                                                       |

For the store, the new work is in steps 3 and 6: **signing the order and checking that the mandate matches that cart** before charging. The agent and the payment intermediaries do the rest.


That AP2 is a payment method or a gateway that competes with yours. It is not: the specification declares itself **independent of the payment instrument** used,[^ap2-spec] and the charge is still made by the credential provider and the store's payment processor.[^ap2-flows] What AP2 adds is the signed proof that the person authorized that purchase. Nor is it what makes you show up in an assistant: that depends on your catalog and on the shopping protocols, not on the payment one.


## How to check it

1. **Open the specification and look at the version.** As of October 6, 2026 it is v0.2; if you see another, what this page says may have changed.[^ap2-spec]
2. **Check the versions published on GitHub**, with their dates: the changelog tells you whether a new feature is already code or only intent.[^ap2-releases]
3. **Check which payment methods the current version covers** on the official site before assuming your favorite method is in.[^ap2-site]
4. **If you sell to the United States, look at your [Google Merchant Center](/glossary/google-merchant-center/) account.** It is Google's requirement for products to enter the UCP reference checkout, in [AI Mode](/glossary/google-ai-mode/) and in the [Gemini](/glossary/gemini/) app.[^google-ucp]
5. **Ask your platform and your gateway** whether they accept orders with AP2 mandates and since when. The answer tells you whether this is your concern or theirs.

## Related concept: UCP

[UCP](/glossary/ucp/) and AP2 get cited together and do different things. UCP is an open-source standard for [agentic commerce](/glossary/agentic-commerce/) that today moves the checkout between an agent and the store, also supports identity linking and order management, and integrates through an API, A2A or [MCP](/glossary/mcp/).[^google-ucp] AP2 handles only the payment part: **UCP says what is bought and how; AP2 proves the person authorized it**. Google sums it up when introducing UCP: it is compatible with AP2 to support secure agent payments.[^google-ucp] The [ACP (Agentic Commerce Protocol)](/glossary/acp/) is another shopping protocol proposal, with its own entry.

To keep going, the [agentic commerce reading path](/learn/agentic-commerce/) orders these protocols and the rest of the vocabulary.