AP2 · Google Agent Payments Protocol overview

Wiki route

This entry sits under AI Agent payment protocols overview · a 7-protocol survey. Read it against AP2 adoption landscape · Google closed loop vs the four-protocol war for peer / contrast context and payments index for the broader system / regulatory boundary.

Key facts

• AP2 v1.0 was released in 2026-Q1 ^•
• Together with MPP (Microsoft), ACP (Anthropic), x402 (Cloudflare/Coinbase/AWS), and A2A (Linux Foundation), it constitutes the agent economy’s “payment protocol four-kingdoms war” ^•
• The core question: when an AI agent pays on a user’s behalf, how does the merchant confirm the agent is genuinely authorized? ^•
• The settlement layer is neutral: Google Pay / card networks / USDC (via Coinbase) / bank instant rails are all viable ^•
• The entire process is based on the W3C Verifiable Credentials standard ^•

Mechanism / How it works

AP2 extends the traditional user-merchant two-party payment into a user-agent-merchant three-party structure, introducing 4 core components:

1. Authorization Mandate — a verifiable credential issued by the user that defines the scope (amount, merchant category, time window) the agent may spend within
2. Payment Intent — the payment intent the agent submits to the merchant, referencing the mandate
3. Settlement Channel — can route through any of Google Pay, card networks, stablecoin (USDC via Coinbase · see USD Stablecoin Interchange Market), or bank instant rails
4. Audit Trail — the entire process is verifiable, based on the W3C VC standard

3 core tensions: the authorization boundary (how much spending authority does the user grant the agent? is re-confirmation needed each time?), identity trustworthiness (how does the merchant know this agent genuinely represents the user?), and dispute resolution (when the agent acts in error, who bears responsibility?).

Origin & evolution

In 2025-09 Google first published the AP2 draft, reaching the v1.0 stable release in 2026-Q1 . The background: after the AI agent economy rose, traditional payments assumed a user-merchant two-party structure and could not handle the “agent pays on behalf” scenario. Google, holding both Google Pay (the world’s 2 位-largest mobile wallet · 6 億 users) and the Gemini agent (hundreds of millions of touchpoints), became the natural occupant of this gap (contrast with Embedded Wallet-Driven Fintech Disintermediation · Privy/CDP/Magic/Web3Auth).

On the timeline, it appeared almost contemporaneously with MPP / ACP / x402 / A2A — the standardization of agent payments is a parallel product under the 2025-2026 industry-consensus pressure.

Related

• Wiki Index
• AP2 Technical Spec
• AP2 Adoption
• ERC-7715(wallet permissions)

Sources

• Google AP2 spec(2026-Q1 v1.0)
• Google AP2 (Agent Payments Protocol) — https://github.com/google-agentic-commerce/AP2