What Is x402? The Protocol Making Internet Payments Native

The Internet Was Always Supposed to Have Payments

When the internet was being built, its architects knew that payments would eventually need to be native to the web. They even reserved a place for it. HTTP status code 402 — “Payment Required” — was set aside in the original HTTP specification, alongside familiar codes like 404 (Not Found) and 200 (OK). But unlike those other codes, 402 was never activated. The technology simply didn't exist.

“HTTP 402, payment required, reserved for future use. Back when the internet was being built into what it is now, they knew that we would need to do payments on the internet, and they wanted to make payments native to the internet, but the technology just didn't exist at the time.”

— Erik Reppel, Head of Engineering, Coinbase Developer Platform

Mark Andreessen spent time trying to make payments native to the internet back in the Netscape days, but the right technology wasn't there. The problem has persisted since the 1980s. What we got instead were workarounds — typing in card numbers, subscription models, advertising. The internet evolved entire business models around the absence of native payments.

x402 is Coinbase's third attempt to activate that reserved status code. Brian Armstrong tried in 2015. Balaji Srinivasan tried in 2016. Now, with the convergence of modern blockchains, stablecoins, and AI, the moment has finally arrived.

Why Now? The AI Catalyst

What changed is twofold: blockchains like Base and Solana have driven gas fees low enough to make cent-level transactions viable, and AI has fundamentally altered how the internet works.

More people are browsing the web through chat interfaces — ChatGPT, Claude, and their equivalents — instead of going directly to websites. This disrupts the advertising model that funds most of the internet. If a human isn't seeing an ad, the merchant has no reason to pay for ad placement, and the website doesn't make money.

“AI really is this complete alteration in how the internet works, and it introduces this new economic actor that has all these second order effects on how businesses are run.”

— Erik Reppel, Head of Engineering, Coinbase Developer Platform

LLMs scraped the internet to train on content, generating enormous value — but content publishers largely aren't being compensated. Some large institutions are making retroactive deals, but that requires major BD effort. If you can just pay 50 cents for the content, that's what Erik calls “micro business development.”

Agents don't have the same limitations as humans. They don't need to browse, click, and type in credit card information. They want something native, API-based, and HTTP-based so they can move as fast as they can.

“Maybe it's the first time that agents will come first — sooner than humans — because they really need this right away.”

— Bam Azizi, CEO & Founder, Mesh

How x402 Actually Works

The setup for a merchant is remarkably simple. All you need is a place for funds to settle — a self-custodial wallet, a Coinbase account, or any place that can receive crypto. The x402 standard handles the rest: how to receive payment, the user journey on both sides, and the optional “facilitator” component that means a merchant doesn't need to interact with the blockchain at all.

“Typically, I see companies start to be able to accept x402 payments in under an hour. It really is that easy to start accepting payments with x402.”

— Erik Reppel, Head of Engineering, Coinbase Developer Platform

The flow works like this: a client (human or agent) requests a resource. The server responds with HTTP 402 and a payment requirement. The client pays with stablecoins. The server verifies and delivers the resource. The entire cycle — request, payment, delivery — happens programmatically.

Facilitators: Like a PSP, but Different

A facilitator in x402 is analogous to a traditional payment service provider (PSP) — it abstracts away the complexity of dealing with the underlying network, just like a PSP abstracts Visa or Mastercard. But there's a critical difference.

“Facilitators aren't in flow of funds, and they're not at any point a custodian of funds on your behalf, and so they don't need money transmitter licenses. Anyone can operate a facilitator, because functionally, all you're doing is abstracting the complexity of interacting with blockchains and providing gas sponsorship.”

— Erik Reppel, Head of Engineering, Coinbase Developer Platform

This is a structural advantage. Because facilitators never touch the funds, the regulatory burden is dramatically lower. The money moves directly from buyer to seller on the blockchain, with the facilitator only handling the technical complexity.

Use Cases: APIs First, Content Second

The most active use case today isn't content paywalls — it's API access. When you use ChatGPT or Claude, they're useful because they know things, but limited in what they can do unless you connect external services. x402 changes that equation: if your chat interface has a wallet, anything that accepts x402 payments is now accessible.

“API usage has been even more than content access. What x402 unlocks is, if your chat interface has a wallet, anything that it knows about that can accept x402 payments, it can now do.”

— Erik Reppel, Head of Engineering, Coinbase Developer Platform

Consider research: an LLM can summarize what's available from a web search, but there are news articles and APIs with social media influence data behind paywalls. With x402, your agent can pay for that premium data, giving you a richer, more robust output. One-time API access — without signing up for a subscription — is where the highest-value transactions are happening.

Another example: you want to generate a video using a model like Sora, but you don't want a $20/month subscription. You can pay $1 to generate a single video. That transaction is uneconomical with credit card fees, but with x402, you receive the full dollar. It becomes an economically viable micro-purchase.

Cloudflare and Pay-Per-Crawl

One of the most significant partnerships is with Cloudflare. Historically, website operators had two options for bots: block them or allow them. There was no economic reason to let bots access content. Cloudflare's “pay per crawl” adds a third option — bots and agents can pay to access content.

“Cloudflare is going to be moving their pay per crawl infrastructure to leverage the x402 standard. If we all align on one standard as an industry, you get interoperability. You don't have to download a browser for each website that you visit. You download one browser and it works on any website.”

— Erik Reppel, Head of Engineering, Coinbase Developer Platform

Cloudflare sees roughly 20% of the internet's traffic. If pay-per-crawl becomes a common standard, the volume could be substantial — and it's driven entirely by the agentic need to access diverse resources at scale.

Conversational vs. Autonomous Commerce

Erik breaks agentic commerce into two buckets. Conversational commerce is where you're talking to an AI but you're in the loop for the final purchase. Autonomous commerce is where the agent acts and pays without human approval.

“Maybe you want ChatGPT to book you a vacation. It might pay for access to localized weather data, engage a service to plan the itinerary, and pay a small amount to make that itinerary. It's doing autonomous commerce to pay for access to those pieces of information. Then at the last mile, it brings the itinerary to you and the hotel and flight it wants to book, and you're in the loop for that last larger purchase.”

— Erik Reppel, Head of Engineering, Coinbase Developer Platform

The vision is that AI becomes substantially better because it can pay to access more capabilities. You give agents a budget to accomplish a task, and they spend it autonomously on the small stuff while bringing larger decisions to you.

Refunds, Not Chargebacks

A common question is how x402 handles disputes. The answer reflects a philosophical difference from traditional card payments.

“I like to say that stablecoins support refunds, but not chargebacks.”

— Erik Reppel, Head of Engineering, Coinbase Developer Platform

The mental model is cash, not credit. For thousands of years, commerce worked without chargebacks. If you handed someone $5, that was the end of the transaction. Stablecoins work the same way — settlement is final, but merchants can issue refunds. Market risk and reputational risk keep companies accountable.

For larger purchases, chargebacks may be necessary. That's where x402's extension system comes in. The v2 of the standard introduces extensions — optional components that can be added to transactions on a case-by-case basis. Not every one-cent transaction needs chargeback infrastructure, but a $500 purchase might.

Schemes and Escrow: Beyond Simple Payments

x402 uses a concept called a scheme to define how money logically moves. Today, the supported scheme is called “exact” — the equivalent of handing someone a dollar bill. But more complex schemes are being developed.

“There's a scheme being developed that would allow for you to escrow a dollar and then do all these requests, and then for the merchant to pull out of escrow as they have the proof points for you and as you consume the API credits that you're functionally purchasing.”

— Erik Reppel, Head of Engineering, Coinbase Developer Platform

This escrow scheme is critical for nano-payments. Many APIs are priced at $1 per million requests — even crypto can't handle transactions that small individually. The solution is to escrow a dollar upfront and draw down against it as the API is consumed. In theory, any logical way money can be transmitted — escrow, streaming payouts, dynamic pricing — can be represented in x402 via the scheme mechanism.

How x402 Relates to Other Standards

The agentic commerce space has a growing list of standards: Google's A2P (Agent-to-Agent Protocol), Stripe's ACP (Agentic Commerce Protocol), MCP (Model Context Protocol), and x402. A natural concern is fragmentation. But these standards are complementary, not competing.

“x402 is kind of internet native transfer of value. A2P is very much used within the agent-to-agent space — it's really an extension of Google's A2A framework. ACP is really meant for conversational commerce, e-commerce analogous. You can actually use x402 as a transport mechanism within ACP as well.”

— Erik Reppel, Head of Engineering, Coinbase Developer Platform

The analogy is the early web: HTTP didn't exist in isolation. It worked alongside HTML, CSS, JavaScript, FTP, and SMTP. Similarly, x402 handles value transfer, A2P handles agent communication, ACP handles e-commerce workflows, and MCP handles model context. They're the new generation of standards for the agentic web.

x402 is already a first-class payment mechanism within A2P. If two agents want to exchange value in stablecoins, they communicate how value is going to be exchanged with A2P and then perform the transfer with x402.

The Path to Neutrality

One important question: is this just a Coinbase product? The answer is no — and the team is actively working to ensure that.

“The web works because you have neutral technologies that are uncontroversial. No one says ‘I shouldn't use HTTP because Google contributes a ton to the HTTP protocol.’ We're moving x402 into a foundation, because we want to create the most level playing field possible.”

— Erik Reppel, Head of Engineering, Coinbase Developer Platform

From the start, x402 has been designed to work with any blockchain and any token. There are already at least 10 different blockchains that support x402 transactions — some EVM, some not. The standard supports any token that implements EIP-3009 for gasless transfers, with a proposal coming to unlock all ERC-20 tokens as well.

The foundation is being set up to maximize both neutrality and the ability to advance the standard without getting bogged down in process. Learn more at x402.org.

An Idea Whose Time Has Come

x402 had six months of steady 30% week-over-week compounding growth before usage hockey-sticked. When asked what caused the explosion in interest, Erik's answer was disarming.

“I think it's an idea whose time has come. It's one of those brain worms that you can't stop thinking about once you realize what the implications are.”

— Erik Reppel, Head of Engineering, Coinbase Developer Platform

The implications are significant. The internet reserved a spot for native payments 40 years ago. Blockchains have made the transaction costs viable. AI has created the economic urgency. And x402 is a simple, open standard that connects these forces — under an hour to integrate, no MTL required for facilitators, and designed from day one to be as neutral as the web itself.

Whether it's an AI agent paying for a premium API, a bot paying to crawl a website, or a user paying a dollar to generate a video instead of committing to a monthly subscription, x402 is activating the payment layer the internet was always meant to have.