Agent payment protocols, explained

AI agents are already spending real money. The open question is whose rails they will spend it on — and in the last few weeks that question has turned into an all-out protocol war between crypto natives, Google, Meta, Stripe, and the card networks.

#Why agents can't just use a credit card

Two problems make the existing payment system a bad fit for machines.

The first is size. Most agent payments are tiny — fractions of a cent for an API call, a data lookup, a few seconds of compute. Card networks charge a fixed fee plus a percentage on every transaction, which makes a $0.003 payment economically impossible. Stablecoins settle the same payment for a fraction of a cent, which is why 87% of x402 payments are worth $0.10 or less and still make sense.

The second is identity. A merchant's website cannot tell a legitimate shopping agent from a malicious bot. In September 2026, Amazon blocked Meta's personal shopping agent from its platform outright — the clearest sign yet that agents need a standard way to prove who they are and what they are allowed to do, instead of scraping websites like bots.

Every protocol below is an attempt to solve one or both of these problems. They are not all competing for the same layer.

#The contenders

#x402 — the crypto-native rail

x402 started at Coinbase and is built around the web's long-dormant HTTP 402 "Payment Required" status code. A server answers a request with a price; the agent pays in stablecoins (usually USDC) and retries with proof of payment. No accounts, no subscriptions, no checkout page.

It is the only contender with serious live volume: 138.5 million payments by Q3 2026, according to Chainalysis. In July 2026 the protocol moved to a foundation under the Linux Foundation, with 40 members including Visa, Mastercard, Stripe and Google — a sign the incumbents are hedging rather than fighting it.

#AP2 — Google's signed permission slips

Google's Agent Payments Protocol (AP2) tackles the identity problem with mandates: cryptographically signed instructions that prove a human authorized an agent to spend, within set limits, anchored to FIDO credentials. Where x402 is a way to pay, AP2 is a way to prove you were allowed to. Revolut's account-to-account payment work has been folded into AP2, and Revolut is rebuilding parts of its own network around agent payments.

#ACP — OpenAI and Stripe's in-chat checkout

The Agentic Commerce Protocol (ACP), co-developed by OpenAI and Stripe, lets agents complete purchases inside a chat interface, routing payment through existing card infrastructure. Its bet is distribution: if people shop inside chatbots, the checkout that lives there wins by default.

#PAP — Meta and Sierra's identity layer

The newest entrant. On October 6, 2026, Sierra and Meta announced the Personal Agent Protocol (PAP), an OAuth-based standard for how agents authenticate with businesses — checking inventory, booking, buying — with a founding coalition that includes Stripe, Shopify, Walmart, Rocket and Genesys. PAP is deliberately thin: identity and authorization only, no payment rail of its own. A v0.1 specification is expected by the end of October 2026.

#Visa and Mastercard — the network incumbents

The card networks are playing at their own layer. Mastercard's Agent Pay issues Agentic Tokens that operate inside its network rules; Visa's Trusted Agent Protocol, part of its Intelligent Commerce initiative, uses partners like Cloudflare to verify that an agent is genuine before a merchant lets it in. Their advantage is the one they have always had: merchants already accept them everywhere.

#UCP — Google's full journey

Google's Universal Commerce Protocol (UCP), announced in January 2026 and expanded at Google I/O, covers the whole commerce journey — discovery, purchase, post-purchase — rather than just the payment moment. It is less a rival to the others than a frame the others can sit inside.

#The real split: three layers, not one winner

Read the announcements together and a pattern emerges. The "war" is really three separate contests:

• Settlement — how value actually moves. Stablecoins via x402 versus card rails via ACP and the networks. The Chainalysis data says machines overwhelmingly prefer the crypto rail for small payments today.
• Authorization — how an agent proves a human said yes. AP2's signed mandates versus PAP's OAuth versus Visa's verification.
• Surface — where the buying happens. Chatbots (ACP), search and Android (UCP), merchant sites (PAP).

A single stack will probably mix layers from different camps — an agent identified via PAP, authorized by an AP2 mandate, settling over x402 is entirely plausible.

#What to watch

• The PAP v0.1 spec, due by the end of October 2026 — the first concrete test of whether the coalition ships or stalls.
• Merchant behaviour. Amazon blocking agents made the problem public; watch whether large retailers adopt a protocol or keep building walls.
• Whether the volume follows the standards. x402's 138.5 million payments happened before most of these protocols existed. Standards bodies move slower than usage.

#Key terms

Agentic commerce

Buying and selling carried out by AI agents on behalf of people or businesses, with little or no human involvement in each transaction.

x402

An open protocol, started by Coinbase and now governed by a Linux Foundation project, that lets software pay for web resources with stablecoins using the HTTP 402 status code.

Mandate

A signed, verifiable instruction proving a human authorized an agent to spend, and within what limits. Central to Google's AP2.

Stablecoin

A cryptocurrency designed to hold a steady value, usually pegged to the US dollar. USDC is the most common settlement coin for agent payments.

Agentic token

A payment credential issued to an AI agent rather than a person, with rules and limits attached. Central to Mastercard's Agent Pay.