AP2 (Agent Payments Protocol)

AP2 is an open protocol for agent payments. It is built so a merchant can trust that an agent’s request reflects what the user actually wants.¹ It uses mandates.

Mandates

AP2 uses signed digital credentials. There are two main mandates, each in two stages:¹

• Checkout Mandate, shared with the merchant. Open: the user’s limits and goals before a cart is final. Closed: approval of one finalized checkout.
• Payment Mandate, shared with the credential provider, the card networks and the merchant’s payment processor. Open: limits such as budget and allowed payment methods. Closed: approval of one amount for a finalized checkout.

The mandates chain together into an audit trail, whether or not the person is present at checkout.¹

Where it fits

• AP2 is available as an extension for the open Agent2Agent (A2A) protocol and for Universal Commerce Protocol. Its docs call it an open extension for A2A and MCP.¹
• Google’s GitHub repo has reference code and sample scenarios in Python, Go and Android. The samples use Google’s Agent Development Kit, but AP2 does not require it.²
• AP2 is a protocol, not a hosted service, so there is no endpoint.

More context: Mandates and data access. All programs: Payments.

Unknown

Which payment networks and wallets support AP2 in production. No cited source confirms it, so the wiki says unknown.

Sources

---

Suggest a correction (opens a GitHub issue)

Footnotes

1. AP2 - Agent Payments Protocol Documentation. AP2 Protocol, official, retrieved 2026-11-12. ↩ ↩² ↩³ ↩⁴

2. GitHub - google-agentic-commerce/AP2: Building a Secure and Interoperable Future for AI-Driven Payments. · GitHub. Google (GitHub), official, retrieved 2026-11-12. ↩