Every few months the agent ecosystem invents a new "X vs Y" that isn't one. Last autumn it was A2A vs MCP — two protocols treated as rivals that were never solving the same problem. The agent-payments space is now running the identical play. Search "AP2 vs x402" and you get bracket-style showdowns ranking protocols head to head, as if a developer had to pick a winner. The framing is wrong, and it's wrong in a way that will cost you an integration if you believe it.
AP2, x402, and ACP are not three answers to one question. They answer three different questions, and a single agentic purchase can pass through all three.
Three layers, not three rivals
AP2 — the authorization layer. Google's Agent Payments Protocol, announced in September 2025, does not move money. It standardizes permission. The core object is a Mandate: a digitally signed credential that records a human told an agent it could spend — on what, under what conditions, up to what limit. An intent mandate captures "buy me running shoes under $150"; a cart mandate locks the specific cart the agent assembled. The problem AP2 attacks is the one that actually keeps agentic commerce out of production: when an autonomous process spends your money, who can prove it was allowed to, and what happens at the chargeback. AP2 is the audit trail, not the rail.
x402 — the settlement layer. Coinbase's x402 revives the HTTP status code that shipped dead in 1997: 402 Payment Required. A server answers a request with 402 and a header describing its price; the client returns a signed stablecoin payload in a second header; a facilitator verifies and settles the payment onchain, then the server fulfills the request. No account, no subscription, no prior billing relationship — any client, human or agent, pays per call with one extra header. On an L2 like Base the fee is around a cent. This is the piece built for the genuinely new behavior: an agent paying for one API response, one dataset, one inference, the moment it needs it.
AP2 proves the agent was allowed to spend. x402 actually moves the money. ACP runs the store. None of them does the other two's job.
ACP — the commerce layer. The Agentic Commerce Protocol, co-developed by OpenAI and Stripe and now maintained jointly, is what powers Instant Checkout inside ChatGPT. It standardizes the shopping part: product discovery, cart management, fulfillment options, and completing a checkout session — the four steps from "show me options" to "order confirmed." Its center of gravity is the existing card economy: a merchant already on Stripe can switch on agentic checkout in roughly a line of code, and the money settles over the same rails it always did.
Where the seam actually is
Read each protocol's own documentation and the rivalry dissolves. AP2's docs explicitly describe x402 as complementary — AP2 handles authorization, x402 handles a payment method — and Google shipped an A2A x402 extension, built with Coinbase, precisely to wire its authorization layer to crypto settlement. Stripe, having co-authored ACP, also added x402 support for USDC on Base in early 2026. The vendors are not fighting over one box on an architecture diagram; they are stacking boxes.
So the useful question is not "which protocol wins" but "which layer is my problem at."
- If you are a merchant who wants to be buyable when a shopper asks their assistant to order something, your problem is at the commerce layer: ACP, and you may never touch the other two.
- If you are building an API or service that agents pay for per call — metered data, a tool, an inference endpoint — your problem is at the settlement layer: x402, which lets a stranger's agent pay without ever signing up.
- If your concern is governance — letting an agent spend within bounds you can prove and revoke — your problem is at the authorization layer: AP2, sitting on top of whatever rail settles underneath.
The one non-obvious thing
The instinct to pick a single "agent payments protocol" is a hangover from the card era, where one integration — your processor — covered authorization, the network, and settlement in one relationship. Agentic payments are pulling those concerns back apart into separately addressable layers, the way the early web pulled transport, naming, and content apart. That's why the receipt and the authorization are becoming first-class artifacts instead of byproducts of a checkout button.
The maturity gap is real and worth pricing in: by late April 2026 x402 reported on the order of 69,000 active agents and 165 million transactions, while AP2 still has comparatively few production implementations. But adoption curves are not the architecture. The architecture is three layers, and the right answer for most teams is not one protocol — it's knowing which layer you're standing on, and leaving room for the other two above and below you.
