Cloudflare rolled out Cloudflare Wallets during its Agents Week, giving AI agents a stablecoin balance and a cloudflare.pay handle to use when purchasing APIs, data, and content. Only the handle reservation feature works today, with funding and payment functionality described as coming in the months ahead. The sole working feature has already triggered complaints about impersonation and fraud, raising questions about whether the platform can protect brand owners before real money changes hands.
The payment system runs on x402, a protocol that repurposes the HTTP 402 Payment Required status code for machine-native micropayments. Coinbase created it, and the Linux Foundation now hosts it with roughly 40 members including Cloudflare, Stripe, Visa, Mastercard, Google, and Amazon Web Services. Cloudflare's network spans 337 cities and reaches approximately one in five websites, according to the company. Each account holder receives an Account Wallet and can create separate Virtual Wallets per agent, funded from the main account and controlled by three limits the owner sets: an allowance, an allow-list of approved merchants, and a maximum transaction size.
On Hacker News, commenter merek discovered his company name and several variations already taken, asking "Without domain validation, what is this user's intention other than fraud/impersonation?" He noted he already faces an impersonator running a website under his brand and confusing customers. Commenter nikolay contrasted the rollout with how Meta handled reserved usernames, giving advance notice and an equal start, and concluded "What Cloudflare did is basically push me not to use their offering, because I couldn't get my username."
The control model Cloudflare ships describes a budget rather than a policy, according to the report. An allowance is a running total, an allow-list is a set membership test, and a maximum transaction size is a per-request bound—each evaluates the current payment against a fixed limit, and none expresses a relationship between payments. Rules that platform teams tend to want do express relationships: an agent may only pay a vendor it has already checked against an approved catalog, it may not pay two vendors for the same thing within an hour, or it must obtain approval before a first purchase from a new merchant. Each requires reasoning about the sequence rather than the current request. Concurrency raises a related issue, since agents issue actions in parallel, so several payments can be checked against an allowance that none of them has yet reduced, and each passes a ceiling their sum exceeds.
For teams evaluating agent payments, the questions are narrow: where does the spending policy live, at the wallet or in the application? What happens when several agent actions run in parallel against one budget? And whether a provider ships limits or a language, because that determines how much has to be built in-house. The report concludes that x402 is a working rail and the question of who governs it is settled, but what an agent can spend across a sequence of payments is not. The username controversy and the control model both point to the same tension: a platform can scale fast or it can protect participants, but doing both at once requires design choices Cloudflare hasn't yet made public.