Let's Discuss x402, the Ghosts of Internet Past, and M-M Transactions
Cloudflare’s NET Dollar: money for robots and more...
Hello all.
Welcome and welcome back.
This is a bonus edition because I haven’t finished writing my ledger/bank issue yet, so enjoy.
On September 25th, 2025, Cloudflare announced NET Dollar. What is the NET Dollar? Cloudflare describes it as a fully USD-collateralized stablecoin, designed for agentic payments and transactions between AI systems without human involvement. In plain speak: money for robots.
AI’s impact on everything from newsrooms to TikTok has been thoroughly dissected, but the payments angle hasn’t received enough attention. As AI systems begin to act on their own (buying data, querying APIs, paying other agents), the rails they’ll need are not the ones we humans use. Cloudflare is offering one answer to the question: what rails do autonomous agents use as we set them loose on the internet?
Cloudflare
For the less familiar: Cloudflare has long been an integral part of the internet’s infrastructure. It accelerates sites, protects against attacks, caches content, and quietly keeps a lot of the web running. If the internet were a city, Cloudflare would be a big chunk of the roads, power lines, and streetlights. It’s fitting that Cloudflare, of all companies, is trying to make money from the web itself.
Cloudflare doesn’t exist in a vacuum. The last couple of years have been a parade of “corporate stablecoins.” Those are attractive capital products, and you’ll continue to see more of them, aimed at captive user bases for retention, float economics, and ecosystem control. Yet Cloudflare’s move feels different. Rather than competing directly in consumer payments, they’re carving out a niche: payments between machines.
They’re also calling out a marked shift in how the internet is monetized. For decades, online business models ran on ads and attention, an inheritance from the days of the Ad Man. Cloudflare’s pitch: monetize usage itself via tiny, native, programmatic payments.
The Ghost of Internet Past (HTTP 402: Payment Required)
Before we dive into the 402 protocol itself, as a refresher: HTTP is the application protocol of the web, the request-response language your browser uses to communicate with servers.
When HTTP was first drafted in the early 1990s, its architects reserved a status code for future use that no one used: 402 – Payment Required. It was meant for a future web where sites could natively charge small amounts for access, digital cash at the protocol layer. That web never arrived. Instead, we duct-taped credit cards, PayPal, and ad networks onto a system with no native money primitive. The foresight to reserve 402 was impressive; the follow-through just took three decades.
That missing primitive, the lack of built-in payments, has been referred to as the internet’s original sin by some, including Marc Andreessen.
So when Cloudflare references x402, they’re not just being cute; they’re reviving that ghost. Use the long-dormant 402 idea as a protocol-level payment signal: a machine (our AI agent) requests a resource; the server responds, “Sure, 402: pay the toll troll first.” It’s the internet finally cashing the check it wrote in the ‘90s.
So why don’t we use existing rails?
If it’s just “making a payment,” can’t agents call Stripe or a bank API? Not really. Agents have different requirements for payment rails than the rails we humans typically transact with:
True autonomy
No humans in the loop: no logins, no cardholders, no “Approve” taps, no OTPs. The payment must be programmatic and self-authenticating.
Instant (or near-instant) settlement
If an agent needs data in real-time, it can’t wait for T+1/T+2 or the typical length of settlement delays. Cloudflare frames NET Dollar for real-time/near-instant transactions.
Finality
No chargebacks, no disputes, no appends. That model makes sense for humans who make mistakes, but it breaks tiny machine-driven transactions. Think on-chain finality: once sent, it’s done.
Micropayments that actually work
For small transactions, fee overheads on card rails can erode the economic upside for payments (consider how many basis points a merchant loses on a card transaction). If you remove the human-centric fee stack and chargeback risk, pay-per-use becomes a viable model.
How does an M-M (machine-to-machine) payment work?
A simplified loop:
An AI agent requests a resource (API endpoint, tiny dataset).
The server returns a 402 Payment Required response, along with metadata including price, asset (e.g., NET Dollar), and destination.
The agent signs a payment payload (a digital IOU from its wallet/facilitator) and retries with the signed proof attached.
The server validates via a facilitator, such as Coinbase or a similar node, which abstracts wallets and chain plumbing. If valid, the server fulfills the request; the facilitator settles NET Dollar on the appropriate chain in the background.
To the developer, it feels like normal HTTP, except that money is embedded within the protocol. The result is effectively stateless payment: no sessions, OAuth, or human login loops, just autonomous agents exchanging verified value.
Or, for simplicity:
Agent A (payer) → Server / Merchant (resource provider) → Facilitator (e.g., Coinbase, PayAI) → Payment Asset (NET Dollar) → Settlement Layer (Layer 2 blockchain) → Facilitator (confirmation) → Merchant / Agent B (payee)
Or even simpler:
Agent A (payer) → Facilitator → NET Dollar → Settlement Layer → Facilitator → Merchant / Agent B (payee)
And if we want to compare traditional financial rails to this:
Traditional rails: Customer → Merchant → Acquirer → Network → Issuer
Agentic rails: Agent → Facilitator → NET Dollar → Settlement Layer → Facilitator → Merchant
The Actors Involved:
x402 — protocol/signaling for payments in HTTP workflows.
Agents — autonomous software acting on behalf of users/firms (Agent A = payer, Agent B = payee/service).
Merchant/Service — the API/data provider receiving funds.
Payment asset — could be NET Dollar, a 1:1 USD-backed stablecoin.
Settlement layer — likely a layer-2 blockchain
Facilitator — an intermediary (could be Coinbase) for custody, validation, and chain interaction, so developers can just use APIs.
The Broader Context
If you squint, this is the sequel to last week’s breakdown of card rails, acquirers, PSPs, and bps. Those rails were built for humans swiping plastic. This rail is being constructed for machines exchanging packets of info at sub-second speeds, with cryptographic finality, and without dispute windows for all sizes of transactions.
Yes, it’s still early days for this, but it’s incredibly fascinating. And there’s a lot we still don’t know:
Which chain/L2? Cloudflare describes NET Dollar as “global and interoperable,” but no public technical specification is yet available.
Issuer/redeemer + reserves? Details TBD beyond “fully collateralized 1:1 USD.”
Regulation. How will regulators treat a stablecoin issued by an infrastructure company?
Jurisdictions. Stablecoins and cross-border transactions = a patchwork of laws and licensing.
Fees/spreads. What do facilitators charge for tiny payments?
Abuse. How do you rate-limit or reputation-score agents when they can be spun up infinitely?
Closing Thoughts
That’s it for today’s machine-to-machine payments bonus. It’s easy to dismiss this as “oh, just another stablecoin.” Still, if it succeeds, it could have a significant impact on how the internet generates revenue and how we interact with e-commerce. And interestingly (to me at least), this is an area where AI could be better without us (payments with no human in the loop), which might also simultaneously make our lives easier.
Anyway, that’s all for today.
Next time, back to our regularly scheduled programming: how banks actually store money and what real-time ledgers look like when you peel off the UI.
Until then, thanks for reading.
Bye.
Sources:
Cloudflare (2025) Cloudflare Introduces NET Dollar to Support a New Business Model for the AI-Driven Internet. [Press release] 25 September. Available at: https://www.cloudflare.com
NET Dollar (2025) NET Dollar™ — A 1:1 USD-backed stablecoin built for agentic commerce. [Product/FAQ]. Available at: https://netdollar.cloudflare.com
CoinDesk (2025) Cloudflare Unveils U.S. Dollar Stablecoin for AI-Powered Internet Economy. 25 September. Available at: https://www.coindesk.com
The Defiant (2025) Cloudflare to Launch “NET Dollar” Stablecoin. September. Available at: https://thedefiant.io
MDN Web Docs (n.d.) 402 Payment Required. Available at: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/402
Cloudflare (2025) Cloudflare and Coinbase Will Launch x402 Foundation. [Press release index] 23–26 September. Available at: https://www.cloudflare.com
Ledger Insights (2025) Cloudflare to launch NET stablecoin for AI agentic payments. 26 September. Available at: https://www.ledgerinsights.com
Economy of Bits / Stratechery (n.d.) The Internet’s Original Sin. [Substack essay series]. Available at: https://economyofbits.substack.com
The Stablecoin Podcast (n.d.) [Audio podcast]. Available at: https://www.thestablecoinpodcast.com