Cloudflare Launches Cloudflare Wallets and cloudflare.pay: Stablecoin Wallets and Permanent IDs for AI Agent Shopping, with Spending Guardrails
Cloudflare announced Cloudflare Wallets and cloudflare.pay on August 4, 2026, giving AI agents a stablecoin wallet and a permanent web-address ID. How the two-tier wallet and spending guardrails work with x402, and what it means for e-commerce.
Key Takeaways
- On August 4, 2026, Cloudflare announced Cloudflare Wallets, a stablecoin wallet for AI agents, and cloudflare.pay, a permanent ID that proves who an agent acts for. Handle reservations opened the same day, and full functionality including funding and withdrawals will roll out over the coming months
- The system delegates spending authority from a human-controlled Account Wallet to per-agent Virtual Wallets, a two-tier design with guardrails such as spending caps, maximum transaction sizes, merchant allowlists, and anomaly detection. Paired with the sell-side Monetization Gateway, it fills in the buy side of the x402 economy
- For e-commerce operators, infrastructure to verify the identity and funding of visiting agents is falling into place. At the same time, stores left off a user's merchant allowlist are structurally excluded from agent-driven sales, which makes agent-readable product data and agent-facing endpoints the first step in preparation
Cloudflare Hands AI Agents a Wallet and an ID
The new service makes it easier for consumers to equip AI agents with tools that let them spend and identify themselves to merchants' agents.
fortune.comOn August 4, 2026 (US time), CDN giant Cloudflare announced a set of services built to support purchases that AI agents make on their owners' behalf. There are two pillars. Cloudflare Wallets is a programmable wallet that stores stablecoins and delegates spending authority to agents. cloudflare.pay is a permanent ID that tells merchants whose agent has come calling. Alongside them, Cloudflare is preparing a set of AI tools that lets merchants respond to inquiries and purchase requests from customer agents.
What became usable on announcement day is reserving a handle (the name of your wallet) on cloudflare.pay. Full functionality, including funding by bank transfer, withdrawal to fiat, and issuing Virtual Wallets to agents, will open "in the coming months" according to the press release. Fees and the specific stablecoins supported remain undisclosed at this point.
Co-founder and CEO Matthew Prince framed the intent this way.
When an agent shows up at your door, you need to know who sent it. Cloudflare can give agents a face, a link to the human or organization that owns them, so that trust, accountability, and real commerce can follow.
How the Two-Tier Wallet and Spending Guardrails Work
At the center of the design is a two-tier structure that separates the human's wallet from the agent's. The holder of a Cloudflare account starts with an Account Wallet that handles adding funds, withdrawing them, and managing delegation. According to Fortune, funds arrive by bank transfer and are converted into dollar-pegged stablecoins for holding, and eligible users will also have the option of funding directly with stablecoins.
From there, each individual agent gets a Virtual Wallet. The agent accesses its virtual wallet through an API key and can spend only within the permissions it has been granted. No human needs to press an approval button for every transaction, yet spending is not unlimited either. Instead of inserting an approval flow each time, the idea is to embed the permission design into the wallet itself.
The safeguards against runaway behavior are layered. There is a spending cap for the wallet as a whole, a maximum size per transaction, a merchant allowlist that narrows where purchases can happen, and recurring budgets such as 100 dollars a week for AI inference. Unexpected spending patterns are caught by anomaly detection and routed to human review. Fortune characterized the design as a safeguard against rogue agents going on spending sprees.
The other pillar, cloudflare.pay, gives agents a permanent identity in the form of a web address. A handle such as "research.example.cloudflare.pay" is tied to a Cloudflare account, and a merchant's systems can machine-read that ID to confirm which person or organization an agent represents. An option to operate pseudonymously remains for users who prefer not to reveal their name.
Agents that decline to identify themselves are not shut out immediately. Cloudflare envisions treating unverified agents the way it treats VPN traffic, subjecting them to additional verification. The new ID stacks on top of Web Bot Auth, the bot authentication mechanism the company has been pushing toward standardization, and its keypair registration.
Authentication, a Monetization Gateway, and Now the Buy Side
This launch reads less like a standalone product and more like the finishing move in an agent-economy blueprint Cloudflare has been assembling in stages. In July 2025 the company introduced Pay Per Crawl, charging AI crawlers for access, and it has driven standardization of Web Bot Auth, which verifies an agent's identity with cryptographic signatures. In July 2026 it announced the Monetization Gateway, which lets customers charge per use for web pages, datasets, APIs, and MCP tools behind Cloudflare.
The sell side had its tooling. What was missing was the buy side. If the Monetization Gateway is the merchant's cash register, Cloudflare Wallets is the buyer's purse. Connecting the two is x402, the open protocol that embeds payments into HTTP, and the result is a two-sided market where agents pay small amounts per request for information and APIs, completed end to end on Cloudflare's network. x402 was developed by Coinbase and championed by Cloudflare and Stripe, and standardization now proceeds under a Linux Foundation body with more than 25 participating companies including Visa and Mastercard.
Behind all this is a structural shift in web traffic. Chief strategy officer Stephanie Cohen told Fortune that roughly 57% of web traffic today consists of bots, and said the company has been building toward a future in which "every interaction on the internet is a chance for commerce." Subscription models for humans assumed bundled sales of articles and features, but bots do not mind carrying out dozens or hundreds of individual transactions. The bet is that selling information and data piecemeal, for cents at a time, becomes viable when the counterparty is an agent holding stablecoins.
MoonPay Got There First, Card Networks Are Moving, and the Numbers to Discount
Cloudflare is not the first to offer wallets for agents. About a week earlier, in late July, crypto payments firm MoonPay unveiled PayBox, a decentralized AI wallet aimed at nontechnical consumers using Claude and ChatGPT. Visa and Mastercard are also hurrying to retool their payment rails for agent-driven purchasing. What sets Cloudflare apart is the entry point: it comes to the same market from its position controlling the pathways of traffic through its CDN and bot management.
At the same time, there are signals that real demand remains small. An Artemis Analytics assessment from March 2026, cited by Forkast, found that 95% of x402 protocol volume was signaling without an underlying sale, with actual commercial exchange hovering around 28,000 dollars per day. The same article points to a June 2026 consumer survey in which only 14% of consumers said they trust AI to execute purchases without verification. PYMNTS research likewise found nearly half of consumers citing fraud and identity issues as concerns, with only 5% reporting no concerns at all.
Cohen herself does not expect ordinary consumers to lead the first act. The first wave will be developers and AI companies buying data, and a second wave of consumer-driven delegated purchasing will require easy-to-use shopping agents plus maturing regulation and fraud controls. Even with ID, wallet, and billing in place, there is a lag before the actors who use them daily arrive in numbers.
What This Means for E-Commerce Operators
For e-commerce operators, there are two changes worth reading out of this announcement.
First, verifying the identity of a visiting agent becomes a realistic option. Until now, operators had few means of telling whether a bot was a customer's legitimate proxy or a malicious scraper, and tended to face a binary choice between blanket blocking and doing nothing. Combine a permanent ID with proof of funds, and a third option appears: let through the agents that identify themselves and pay their way. Given that fraud and impersonation top consumer worries, being able to deal only with identifiable agents becomes a precondition for accepting agent-mediated transactions at all.
Second, the allowlist itself. If users can restrict where their agents shop, then stores that are not on the list are structurally cut off from agent-driven sales. The criteria and application process for getting listed are undisclosed for now, but preparing product data that agents can read correctly, along with agent-facing endpoints such as APIs and MCP, is groundwork that pays off whichever way the mechanics land.
Selling is also on the table. With the Monetization Gateway and Wallets both in place, charging outside agents per use for product information or inventory data has entered territory a merchant can test without a major payments-infrastructure investment. If the near-term buyers are developers and AI companies, the first things to sell are likely structured product data and search APIs rather than the products themselves.
Conclusion
Authentication with Web Bot Auth, billing with the Monetization Gateway, and now a wallet and ID with Wallets and cloudflare.pay. Cloudflare has been filling in the parts an agent economy needs, one by one, and has now sketched nearly the full blueprint for putting both sellers and buyers on its own network. Much remains undisclosed, from fees to supported currencies, and real x402 demand is still in its early ramp. Even so, the framework where only agents with a verifiable owner spend within defined limits is a plausible foundation for transactions in the agent era. The next few months, starting with handle reservations, and the behavior of the developer demand that forms the first wave, will be the test of this design.
