Illustration of Cloudflare Wallet: Paying New Players with X402 Stablecoin

On August 4th, Cloudflare announced the launch of Wallets. Opening the announcement, the first thing you can do is very simple: claim a handle for your future wallet, which is basically choosing a name.

The easily overlooked part of the announcement is another short sentence. When it comes to actually setting up and using the wallet to purchase APIs and content, Cloudflare only says "Soon." While users can claim a handle, it doesn't mean the user already has a stablecoin card that can be freely swiped. This time gap is precisely where this product is most worthy of a closer look.

Don't Mistake the Handle for a Wallet Just Yet

Figure 1 places several of Cloudflare's recent payment product lines together, where the order is more important than the names. According to Cloudflare's Wallets announcement, what was delivered on August 4th was the handle. Recharge, payment, and the Virtual Wallet used by agents via API keys are still mentioned in the subsequent product description.

This timeline already has two pieces of the puzzle in place. As per the announcement by Cloudflare and Stripe Projects, Stripe Projects allow agents to sign up for a Cloudflare account, purchase subscriptions or domains on behalf of users, and is currently in open beta. As per the Monetization Gateway announcement, the merchant-side gateway for payments via x402 is still on a waiting list.

All three happen to involve agents and payments but are not on the same layer. Stripe Projects offer a card-on-file path that is already available for trial use. Monetization Gateway is aimed at resource partners looking to receive payments. Wallets aim to supplement the payer's identity, balance, and authorization rules. Looking at them side by side, Cloudflare's delivery this time resembles more of a payer's account page rather than an already operational cashing network.

Data on x402 Doesn't Equate to Cloudflare's Report Card

According to the snapshot displayed on the x402 website on August 5th, covering the past 30 days, the network recorded 75.41 million transactions with a transaction volume of $24.24 million. When divided, the average transaction is approximately $0.32. This order of magnitude closely resembles small, frequent payments like API calls and content access, rather than a large single order.

However, Figure 2 holds another layer of boundary. The official website does not disclose how much of these transactions come from Cloudflare, how many are initiated by AI agents, nor does it provide the enabled account, merchant, or transaction volume of the Wallet. It proves that there are already cars on this x402 protocol road, but it cannot be inferred how many cars are sporting a Cloudflare Wallet license plate.

This distinction will directly change the interpretation of the news. x402 is an open process that initiates a payment request using HTTP 402, not a settlement network exclusive to Cloudflare. Public snapshots can demonstrate observable activity on the protocol, but they cannot be considered as the adoption rate of the Cloudflare Wallet, much less replace statistics on the scale of agent-initiated consumption.

The Reality of a One-Cent Call, At Least with More Than One Wallet

Cloudflare's Paying MCP tool example sets a one-time call at $0.01, which is just a documentation sample and not a market average. It does break down micropayments very specifically, with the server first returning 402, the agent signing the payment, the settlement coordination facilitator then verifying and settling, and only then does the server return the result.

In the current developer path, the key is still held by the developer. According to the Agents SDK payment example, the confirmation callback can be set to automatic, but the example also requires a private key and the use of the test network and test USDC. Setting the agent to automatically make payments does not mean handing over the responsibility of spending, the key, and the limit altogether to a mature wallet.

The Wallet's roadmap is currently stuck at this buyer side step. Cloudflare plans to separate the Account Wallet used by the account holder from the Virtual Wallet operated by the agent with an API key, and introduce limits, whitelists, and single transaction caps. It is more like a corporate card with approval rules, where merchants still have to provide goods, and the facilitator still has to complete settlements. These rules have not yet been made available for configuration, and the planned security fence cannot be described as a current feature.

Three Agent Payment Paths, Sharing Only Two Words

Figure 4 breaks down three easily conflated paths into credential, risk control, and status. Stripe Projects hand over the payment token to the service side, with the original credit card information not given to the agent. The default limit is $100 per service side per month, and according to Cloudflare's announcement, it is still in open beta. This limit belongs to Stripe's card swipe business and cannot be translated into a Wallet's limit.

The x402 developer payment, on the other hand, is another starting point. The developer holds the private key and can set up pay-as-you-go access for API or MCP tools. Currently, only the handle for the Wallet has been opened up, while stablecoin balance, limits, and whitelisting have not yet been provided with a practical configuration entry point. As for which stablecoins will be supported, which blockchain will be used, where it can be used, as well as details on KYC, custody, and fees, Cloudflare has not yet disclosed.