The Protocol Default

The argument

Agents can already pay without a checkout screen. An agent requests a resource, receives a payment prompt, authorises the transaction and the service delivers. Protocol adoption in payments follows path dependency. The standard embedded first in agent frameworks, MCP servers and startup templates becomes the layer everything else assumes, and such layers are extended far more often than they are replaced.

By March 2026 three approaches were in production. Coinbase’s x402, launched in May 2025, gates an API endpoint behind an HTTP 402 response and settles in USDC, with no accounts or merchant relationship. Google’s AP2, built on its A2A framework, adopted x402 as its on-chain settlement extension, and Coinbase and Cloudflare set up the x402 Foundation to govern the protocol. Stripe and Tempo launched the Machine Payments Protocol (MPP), supporting stablecoins, cards and fiat through Stripe’s existing payment stack.

The two leading designs encode different views of where financial trust sits. x402 is internet-native: payment as a property of HTTP, stateless and settled on chain without an intermediary in the path. MPP is network-native: agent purchases treated as commerce, with the fraud, tax, refund and reporting tools businesses already use extended to a new kind of buyer. Which becomes the default is likely to depend on where developers already are when they need to ship.

Both settle in US dollars under US governance and leave local-currency settlement optional. At scale, that optionality becomes structural for every jurisdiction outside the United States. The question surfaces early where programmable domestic payment systems already exist. India’s agent payment pilots on UPI keep a human in the consent chain, with a user-set limit for each merchant. Developers who need fully machine-to-machine payment today reach for x402 or Stripe, and each such integration sets a default. The choice that matters is whether a domestically settled, domestically governed option exists at the moment developers choose.

Key points

• Agent payment standards spread through developer defaults, and defaults are extended more often than replaced.
• x402 places payment in the web protocol layer; MPP extends an existing payment network’s controls to agents.
• Both settle in US dollars under US governance and leave local-currency settlement optional.
• Jurisdictions with programmable domestic payment systems meet the question first: is a domestic option available when developers make their choice?

Evidence and sources

• Coinbase x402 launch (May 2025) and the x402 Foundation formed with Cloudflare (September 2025)
• Google Agent Payments Protocol (AP2) and its A2A framework (September 2025)
• Stripe and Tempo, Machine Payments Protocol launch (March 2026)
• UPI agent payment pilots through Reserve Pay and UPI Circle (from September 2025)

Limits

• Adoption figures in the original, including x402 payment counts, MPP integrations and Stripe’s share of the Forbes AI 50, were company-reported at the time of writing.

Since publication

• Google contributed AP2 to the FIDO Alliance on 28 April 2026; version 0.2 adds payments where the human is not present, under signed mandates.
• x402 has been governed by the x402 Foundation under the Linux Foundation since April 2026. Independent analysis in July 2026 classed about half of reported x402 activity as artificial.

Tracked in the Agentic Payments Ecosystem Map.