Loading…
Your Full-Service Digital Agency & AI Strategy Partner
Real strategists. Real AI tools. Real growth. — 1Digital® since 2012
Workspace by 1Digital® — the agency platform we built. Coming to select agencies. Join the early-access list →
AI SEO Glossary
TL;DR — AP2 (Agent Payments Protocol) is an open protocol announced by Google in September 2025 that defines how AI agents authenticate as a user's delegate, present cryptographically signed mandates to merchants, and complete payments without exposing the user's primary credentials.
Agent Payments Protocol (AP2)is an open protocol announced by Google in September 2025 that defines how AI agents (Gemini, ChatGPT Agent, Claude Computer Use, and others) authenticate as a user's delegate, present cryptographically signed mandates to merchants, and complete payments without exposing the user's primary credentials. Designed to work alongside the existing payment-network rails (Visa, Mastercard, Discover, Amex, PayPal — all named launch partners) rather than replacing them.
AP2 sits in the same conceptual layer as OpenAI's ACP (Agentic Commerce Protocol). The two protocols are not directly compatible but cover overlapping ground; expectation through 2026 is that merchants will implement both to maintain compatibility across the engine landscape. Full protocol detail and implementation work on /agentic-commerce.
In Google's developer documentation for Gemini agentic flows. In platform partner announcements (Shopify, BigCommerce, Adobe Commerce — all referenced in launch coverage as integrating partners). In vendor RFPs starting in 2026 as “agent-ready checkout” becomes a procurement requirement for enterprise eCommerce stacks.
For merchants, the practical question through 2026 is whether to implement AP2 native, ACP native, or use a platform/aggregator that abstracts both. Decision turns on the eCommerce platform you sit on, your current PSP, and how much of your traffic is already arriving from agentic sessions.
Google announced AP2 in September 2025 alongside a roster of launch partners including Visa, Mastercard, Discover, American Express, and PayPal.
Both protocols sit in the same conceptual layer — letting an AI agent complete a purchase on a user's behalf — but they're not directly compatible. AP2 is Google's spec; ACP (Agentic Commerce Protocol) is OpenAI's. Expectation through 2026 is that merchants will implement both to maintain compatibility across the engine landscape.
No. AP2 is designed to work alongside the existing payment-network rails (Visa, Mastercard, Discover, Amex, PayPal). The protocol handles agent identity, mandate signing, and merchant verification; the underlying money movement still flows through the same card or wallet networks.
Google Gemini-driven agent flows are the first-party use case. Google has positioned the protocol as open and cross-agent — expect ChatGPT Agent, Claude Computer Use, and others to adopt AP2 alongside their own preferred protocols through 2026.
Agent-detection at checkout, mandate verification (cryptographic signature check), and the cart/checkout flow needs to accept the protocol's session pattern. Many platforms (Shopify, BigCommerce, Adobe Commerce) are surfacing first-party AP2 / ACP support through 2026 — adoption work scoped on /agentic-commerce.
No. MCP (Model Context Protocol) is for data and tool access; AP2 is for payment authorization. Different layers, often deployed together on agentic-commerce projects.
We scope agentic-commerce readiness across your platform, PSP, and cart flow. Call 888-982-8269.