# What is AP2, the Agent Payments Protocol?

> AP2 is an open protocol for proving that a person authorized an AI agent to make a purchase. It records that approval in signed documents called mandates, which the merchant, the payment network and the bank can check. Google announced it in September 2025 and donated it to the FIDO Alliance in April 2026. It does not move money itself.

## The problem it solves

Payment systems assume a person is pressing the button. When an AI agent buys something on your behalf, everyone else in the chain has a question they cannot answer: did you really ask for this?

AP2 answers it with evidence. Before the agent pays, your approval is written down and signed. Later, if there is a dispute, the record shows who agreed to what.

The protocol's site describes it as "an open protocol for the emerging Agent Economy".

## Mandates

A mandate is a signed record, issued as a verifiable digital credential. There are two kinds, and each comes in an open and a closed form.

| Mandate | Shared with | Open form | Closed form |
|---|---|---|---|
| Checkout Mandate | The merchant | Your goals and limits, before a specific cart exists | Your approval of one specific, final checkout |
| Payment Mandate | The credential provider, the networks and the merchant's payment processor | Your limits on payment, such as a budget and which payment methods may be used | Approval of one specific amount, tied to one checkout |

The open forms are for agents working on their own, for example an instruction to buy once a price falls below a limit you set. The closed forms are for a purchase you look at and confirm.

## What it does not do

AP2 does not carry the money. It establishes that a payment is authorized. Something else settles it, whether that is a card network or a protocol such as x402.

It also does not use HTTP status 402.

## Payment methods

The first version supports what the site calls "pull" payment methods, such as credit and debit cards. The roadmap lists e-wallets, "push" payments such as real-time bank transfers, and digital currencies.

## Key facts

| | |
|---|---|
| Started by | Google, announced September 16, 2025 |
| Governed by | The FIDO Alliance, since April 28, 2026 |
| Version | 0.2, published with the donation to FIDO |
| Format | An open extension for the A2A and MCP protocols |
| Core object | Mandates, as verifiable digital credentials |
| Moves money | No |

## AP2 and x402

They do different jobs and are meant to be combined. AP2 holds the proof of consent. x402 moves the funds. The AP2 project ships a sample where an agent, with no person present, pays through x402.

For most paid API calls an agent makes, the amounts are tiny and a spending limit on the wallet is control enough. AP2 matters more as purchases get larger and as cards, with their dispute rules, come into play.

The side-by-side comparison is in [x402 vs AP2](https://www.ask402.ai/x402/x402-vs-ap2).

## AP2 and ACP

They are often mentioned together and are not the same thing. AP2 is about authorization. [ACP](https://www.ask402.ai/x402/what-is-acp) is about the checkout conversation between an agent and a merchant. The [comparison table](https://www.ask402.ai/x402/agent-payment-protocols-compared) sets all of them side by side.

## Sources

- [AP2 protocol site](https://ap2-protocol.org/)
- [Google, AP2 and the FIDO Alliance (April 28, 2026)](https://blog.google/products-and-platforms/platforms/google-pay/agent-payments-protocol-fido-alliance/)
- [AP2 repository](https://github.com/google-agentic-commerce/AP2)

---

Facts checked against the sources above on 2026-11-20. Canonical page: https://www.ask402.ai/x402/what-is-ap2
