Invest1 publisher2 min readPublished
Cloudflare's stablecoin gateway settles on two chains short of its product lead's throughput target
Cloudflare is now charging for web resources in stablecoins. The product director running that effort says machine payments will eventually need throughput beyond what any existing blockchain can supply.
The Investor · Invest desk

What happened
- Cloudflare launched its Monetization Gateway on July 1, 2026, letting sellers charge for web resources in USDC settled on the Base and Polygon networks.
- The gateway is built around x402, a revived version of HTTP's long-dormant 402 status code, adapted for stablecoin transactions with near-instant finality and negligible fees.
- Will Papper, who joined as Director of Product in July 2026, puts the payment layer the internet needs at 5 to 50 million transactions a second, beyond any single existing blockchain.
- Papper has pointed to Ethereum's original sharding design, splitting a database into parallel pieces, as the architectural model for scaling that payment infrastructure.
Compiled by The InvestorSomething wrong?How this is made
Why it matters
- capability Charging fractions of a cent per request becomes possible on resources Cloudflare already fronts, a price tier card minimums have always ruled out.
- constraint Base and Polygon capacity sets the ceiling on what agents can spend through the gateway.
- exposure Each payment is a USDC leg on someone else's chain, and Crypto Briefing says Circle is the direct beneficiary of the volume.
Five million payments a second, at a full cent each, comes to 50,000 dollars a second [1]. That is 4.32 billion dollars a day, or about 1.58 trillion a year [2]. The top of the range Papper cites, 50 million a second, works out near 15.8 trillion dollars a year [3]. Both figures are ceilings, because the transactions the gateway was built for are sub-cent by design [7]. Crypto Briefing does not report a fee for the gateway or any volume through it [15].
So the target describes capacity. Cloudflare shipped that capacity on rails its own product director says fall short. Papper's position, as Crypto Briefing reports it, is that no existing blockchain comes close to 5 to 50 million transactions per second on its own [6], and that machine-to-machine commerce will eventually exceed what all existing blockchains can handle combined [11]. Settlement through the gateway happens on-chain in seconds [4].
Sharding is the borrowed part. Vitalik Buterin proposed splitting the chain into parallel pieces years ago as the path to massive throughput, and the network pivoted to a rollup-centric roadmap instead [10]. At the application layer the idea is simpler than Ethereum's proposal. If no single chain clears the load, spread the requests across several and route each one to whichever chain can settle it.
Cloudflare put settlement on two chains it does not operate, and the volume accrues to them and to the issuer of the dollar being moved. Crypto Briefing writes that Circle, which issues USDC, stands to benefit directly from increased on-chain volume flowing through Base and Polygon [12], and attributes the choice of those two over Solana or Arbitrum to the best combination of speed, cost and reliability for payment workloads [13].
In my view the throughput figure is the least binding constraint in the picture. Cloudflare's advantage is position. It already sits between clients and servers for a large share of the internet, roughly 20% of global web traffic [1][14], and a payments product normally has to buy distribution of that kind. The open question is whether sellers will price per request at all. Card minimums make anything below a few cents uneconomic [8], so the sub-cent tier has no incumbent to take share from, and no measured demand either. If sellers stay with subscriptions and API keys, a rail built for 50 million payments a second sits idle at any fee.
A disclosed take rate and a count of billed requests would settle it. The gateway launched on July 1, 2026, the same month Papper joined Cloudflare [4], so any usage record is short.
What to watch
- A published fee or take rate on the Monetization Gateway; until then the throughput target cannot be converted into revenue.
- Whether Cloudflare adds settlement venues beyond Base and Polygon, or moves to a chain it controls itself.
- Whether the sharding framing becomes a shipped feature, routing one payment flow across several chains at once.