Agentic Commerce Protocols: Overview
A map of the open protocols behind agentic commerce: tool access, agent messaging, checkout, payment authorization and agent identity, and how they fit.
In short: No single protocol covers agentic commerce. A purchase made by an AI agent usually touches several layers: how the agent calls tools, how it talks to other agents, how it runs a merchant’s checkout, how the payment is authorized, and how the agent proves who it is. As of October 2026, most of these layers have one or two leading specifications, and many are now run by neutral foundations or standards bodies.
Why there are so many protocols
In ordinary e-commerce a person is at the keyboard, and the browser, the checkout form and 3-D Secure (the card-network step-up authentication) answer most trust questions. When a software agent acts for that person, several questions need new answers:
- How does the agent find products and call a merchant’s systems? (tool access)
- How does it work with other agents, such as a merchant’s own sales agent? (agent-to-agent)
- How does it build a cart, get shipping and tax, and place the order? (checkout)
- How does the payment system know the user actually approved this purchase? (payment authorization)
- How does the merchant’s website tell a legitimate agent from a scraper or a fraud bot? (agent identity)
Each protocol below answers one or two of these questions. They overlap in places, but they are mostly built to be used together.
The layers
1. Agent ↔ tool
The Model Context Protocol (MCP) is the common way for an AI application to connect to external tools and data. In commerce, merchants and platforms run MCP servers for catalog search, carts and orders. MCP is a general-purpose protocol and has no commerce-specific objects of its own.
2. Agent ↔ agent
Agent2Agent (A2A) lets independent agents discover each other through “agent cards” and exchange tasks and messages. It is used when a shopping agent works with a merchant agent, rather than calling a plain API. AP2 and UCP both define A2A bindings.
3. Agent ↔ merchant checkout
Two specifications define how an agent runs a merchant’s checkout:
- The Agentic Commerce Protocol (ACP), from OpenAI and Stripe, defines checkout sessions, product feeds and delegated payment.
- The Universal Commerce Protocol (UCP), from Google and Shopify with a growing governance council, covers catalog, cart, checkout, identity linking and orders, with REST, MCP and A2A transports.
Both leave the merchant as the merchant of record (the party legally selling the goods and handling the payment).
4. Payment authorization
These protocols prove that the user approved a payment, and limit what an agent can spend:
- The Agent Payments Protocol (AP2) uses signed “mandates” as a verifiable record of what the user authorized. Google contributed it to the FIDO Alliance in April 2026.
- Card-network programs, Visa Intelligent Commerce and Mastercard Agent Pay, issue agent-specific network tokens (card substitutes tied to one agent and set limits) and register agents.
- x402 builds payment into HTTP itself using the 402 “Payment Required” status code, mostly with stablecoins. It suits per-request and machine-to-machine payments.
PSP (payment service provider) token schemes such as Stripe’s Shared Payment Tokens sit here too, but they are products of one provider, not open protocols.
5. Agent identity
Web Bot Auth uses HTTP message signatures (RFC 9421) so an agent can sign its requests with a published key. Visa’s Trusted Agent Protocol and Mastercard’s Agent Pay Acceptance Framework are built on it. The IETF adopted the core draft as a working-group document in September 2026.
Comparison table
Status as of October 2026.
| Protocol | Main backers | Layer | Status | Open / closed |
|---|---|---|---|---|
| MCP | Created by Anthropic; now Agentic AI Foundation (Linux Foundation) | Agent ↔ tool | Stable; spec version 2026-07-28 | Open spec, open governance |
| A2A | Created by Google; Linux Foundation project | Agent ↔ agent | v1.0 released in 2026 | Open spec, open governance |
| ACP | OpenAI, Stripe | Checkout, product feeds, delegated payment | Stable; latest release 2026-04-17 | Open spec (Apache 2.0); maintained by its two founders |
| UCP | Google, Shopify, plus Etsy, Target, Wayfair, Stripe and others on its councils | Catalog, cart, checkout, identity linking, orders | Stable; latest release 2026-08-25 | Open spec (Apache 2.0); multi-company councils |
| AP2 | Created by Google; now FIDO Alliance | Payment authorization (mandates) | v0.2 (April 2026); in FIDO standards process | Open spec, standards body |
| Visa Intelligent Commerce / Trusted Agent Protocol | Visa | Network tokens, agent identity | In pilot and early production | Network program; TAP spec published openly |
| Mastercard Agent Pay | Mastercard | Network tokens, agent registration, intent proof | Live with issuers in US and Europe | Network program; Verifiable Intent published openly |
| x402 | Created by Coinbase; x402 Foundation (Linux Foundation, operational since July 2026) | HTTP-native payment | Production (v2) | Open spec, open governance |
| Web Bot Auth | Cloudflare, Google authors; IETF working group | Agent identity | IETF working-group draft | Open standard in progress |
Other specifications exist. One example is the Machine Payments Protocol (MPP), launched by Stripe and Tempo in March 2026 for session-based machine payments. This wiki covers the ones most often cited in merchant and payments discussions.
How they fit together
A typical agent purchase in 2026 might go like this:
- The shopping agent finds products through an MCP server or a UCP catalog endpoint, or from a merchant product feed. See product data.
- Its HTTP requests to the merchant carry a Web Bot Auth signature, so the merchant’s CDN or bot-management tool can recognize a registered agent.
- The agent opens a checkout session using ACP or UCP, and the merchant returns totals, tax and shipping options.
- The user approves the purchase, or approved limits in advance. AP2 mandates or a network’s intent record capture that approval in a verifiable form.
- The payment uses a scoped credential: a PSP token, a Visa or Mastercard agentic token, or an x402 stablecoin payment for machine-priced resources.
- The merchant authorizes the payment through its usual processor and sends order updates back to the agent.
The layers are designed to stack. UCP lists AP2 as a payment extension and MCP and A2A as transports. ACP added an MCP binding in its April 2026 release. Visa’s Intelligent Commerce Connect accepts payments arriving through TAP, MPP, ACP and UCP. AP2 has an x402 extension for stablecoin settlement.
How to choose
The right set depends on your role. The playbooks go into more detail.
| If you are… | Start with | Then consider |
|---|---|---|
| A merchant on a major platform (Shopify, Salesforce, BigCommerce and others) | Your platform’s built-in ACP/UCP support and product-feed settings | Bot-management rules that recognize signed agents |
| A merchant with custom checkout | UCP and/or ACP endpoints; your PSP’s agentic token support | Web Bot Auth verification, AP2 mandate handling |
| An agent developer | MCP for tools; UCP and ACP clients for checkout | Web Bot Auth signing, network agent registration |
| A payments provider | Network agentic tokens, AP2, PSP token schemes | x402 and MPP for machine payments |
| An API or content business charging per request | x402 | Web Bot Auth for identity |
Practical points:
- Support more than one checkout protocol where it’s cheap to. Platforms and PSPs often handle both ACP and UCP behind one integration, so many merchants never have to pick.
- Protocols don’t guarantee distribution. Which AI surfaces show your products depends on each surface’s own programs and eligibility rules. In March 2026, OpenAI ended in-chat Instant Checkout and now hands buyers off to retailer sites or retailer apps inside ChatGPT, though ACP itself stayed in use. Google continues to offer in-assistant checkout through UCP.
- Treat identity and authorization separately. A valid agent signature proves which agent is calling. It does not prove the user approved the purchase. See agent identity and fraud.
- Watch governance. MCP, A2A, x402 and AP2 now sit with neutral bodies. ACP and UCP are governed by their founders and councils. That matters for long-term roadmaps.
Sources
- Agentic Commerce Protocol repository — GitHub
- Under the Hood: Universal Commerce Protocol (UCP) — Google Developers Blog
- UCP Announcements — ucp.dev
- Google donates Agent Payments Protocol to FIDO Alliance — Google
- The 2026-07-28 Specification — Model Context Protocol Blog
- A year of open collaboration: Celebrating the anniversary of A2A — Google Open Source Blog
- Linux Foundation announces operational launch of x402 Foundation — Linux Foundation
- Web Bot Auth working group documents — IETF Datatracker
- Securing agentic commerce: helping AI Agents transact with Visa and Mastercard — Cloudflare
- Visa launches Intelligent Commerce Connect — The Paypers
- OpenAI shifts checkout plans in its agentic commerce strategy — Digital Commerce 360
- Why Stripe’s Machine Payments Protocol signals a turning point for micropayments — Forrester