Coinbase pushed x402 to neutrality, Stripe hedged MPP with it

The growing complexity of the agentic commerce space

Over the past few weeks, a lot more people have started paying attention to agentic commerce. And the more they look, the less obvious the map seems.

Last week, the market was still trying to understand Stripe and Tempo’s Machine Payments Protocol, or MPP. Then almost immediately, Stripe showed up as a founding contributor to Coinbase’s x402 Foundation. Cloudflare now supports both. Google is in the room too, while continuing to push AP2 and UCP. Visa and Mastercard have both joined the broader conversation, but clearly not because they woke up one morning wanting to champion stablecoins.

Linux Foundation is explicitly positioning x402 as a neutral, community-governed home for “payments over HTTP.” Cloudflare has placed both x402 and MPP inside its Agents SDK. Stripe has published support for both. At first glance, it looks messy. Who is competing with whom? Which protocols overlap, and which ones actually stack?

The more I look at it, the less I think this is market confusion. It looks more like the opposite. The market already understands that this will not be unified by a single protocol in one shot. What is emerging looks much more like what usually happens in internet infrastructure: different layers forming at the same time, different firms placing bets at different levels of the stack, and interoperability doing the hard work of turning fragmentation into something usable.

That is why I think many people are still reading x402 the wrong way. The real strategic story is not simply “which protocol wins.” It is who gets to define the default control plane for paid machine access on the agentic web. And the reason the key players are multi-homing is straightforward: nobody knows yet whether the durable bottleneck will sit in authorization, distribution, orchestration, or settlement.

1. Why did Coinbase hand x402 to Linux Foundation?

If x402 remained a Coinbase protocol, it would struggle to become a market default.

That is not a matter of ideology. It is a matter of standardization politics. Linux Foundation is not presenting x402 as a shiny new feature from a single company. It is presenting it as shared infrastructure: vendor-neutral, community-governed, and open to broad industry participation. Just as importantly, the x402 Foundation is still in formation. The governance framework and board are still being assembled. In other words, this move is not mainly saying, “the product is finished.” It is saying, “this protocol now needs a neutral home.”

That distinction matters more than most people think. If x402 keeps looking like a Coinbase product surface, major cloud providers, payment firms, card networks, and platforms may be technically willing to integrate it while remaining strategically hesitant. Nobody wants the future paid access layer of the internet to sit too obviously inside a single company’s orbit.

That is why moving x402 under Linux Foundation should not be read as Coinbase giving up control. It is better understood as Coinbase trying to maximize adoption. If the company wants x402 to become a serious HTTP-native baseline for paid access, it has to remove the political tax of “this is really just Coinbase’s protocol.”

People often look at foundations like this and reduce them to PR or open-source theater. In protocol wars, that is a mistake. Governance is part of the product. When a standard is still early and lacks overwhelming network effects, neutrality and trust matter almost as much as technical elegance. If x402 becomes meaningful internet plumbing, it may not be because its code is prettiest. It may be because it lowered the coordination cost faster than its alternatives.

Put differently: governance is not a side detail here. Governance is a growth engine.

2. What is Stripe doing by backing MPP and joining x402?

The player worth watching most closely in this phase is Stripe.

Its behavior looks contradictory only if you frame everything as a one-layer protocol contest. On March 18, Stripe launched MPP and presented it as an open standard for machine payments. At the same time, Stripe became a founding contributor to x402 Foundation and published support for x402-based machine payments. Cloudflare’s documentation goes even further, stating that MPP is backward-compatible with x402’s core payment flow, and that MPP clients can consume existing x402 services.