Cloudflare began the first stage of its programmable wallet rollout on Aug. 4, allowing customers to claim unique wallet handles for future stablecoin payments by artificial intelligence agents.
Summary
- Cloudflare users can claim wallet handles now, while stablecoin funding and payment functions remain forthcoming.
- Account Wallets will hold funds, while Virtual Wallets let authorized agents make controlled purchases online.
- Owners can cap allowances, approve merchants, limit transaction sizes, and require human overrides when needed.
- x402 processed 75.41 million transactions and $24.24 million in volume during the last thirty days.
- Cloudflare has not disclosed supported stablecoins, networks, custody partners, fees, or full launch timing yet.
The official Cloudflare announcement said users can reserve a handle tied to their Cloudflare account through cloudflare.pay. However, the company said the ability to fund wallets and use them to purchase APIs, data and online content will arrive “soon.” It did not provide a launch date.
The distinction means Cloudflare has opened the identity layer of the product rather than a fully functioning payment service. Customers cannot yet assume that the stablecoin storage, withdrawal or automated spending features described by the company are broadly available.
Cloudflare Wallets begin with handles, not payments
Cloudflare plans to offer two wallet types. Account Wallets will be controlled by individual or organizational customers. Users will be able to add funds, withdraw balances and delegate spending authority to wallets operated by their AI agents.
Virtual Wallets will operate through API keys. An agent will use the wallet to purchase services within permissions established by the Account Wallet owner. Cloudflare listed APIs, Model Context Protocol tools, data, AI inference and online content as potential purchases.
The company is also building a human readable identity system around the wallets. A business could assign an agent an address such as research.example.cloudflare.pay, allowing merchants to associate the software with a particular organization. Declaring that identity will remain optional. Merchants will decide whether to serve unidentified agents or give priority to known ones.
Cloudflare compared the system with the way the Domain Name System links readable website names to less readable internet addresses. The wallet handle will be connected to an agent’s cryptographic key rather than replace the underlying verification process.
Spending controls aim to limit autonomous agent risks
Cloudflare said Account Wallet owners will be able to set allowances, approved merchant lists and maximum transaction sizes. These controls are intended to let agents test low cost services without requesting human approval for every purchase.
A company could, for example, give each employee’s agent a weekly budget for AI inference. When a wallet reaches its limit, the agent could request a manual override from an authorized administrator. Unexpectedly fast spending could also trigger a review before the owner increases the budget or adds more funds.
Cloudflare presented these limits as protection against overspending. However, it has not published technical documentation explaining how lost API keys, compromised agents, disputed payments or unauthorized purchases will be handled.
The company has previously worked with Visa and Mastercard on systems that help merchants distinguish approved shopping agents from malicious bots. Visa’s Trusted Agent Protocol and Mastercard’s Agent Pay use Cloudflare’s Web Bot Auth system to verify cryptographic signatures and confirm whether an agent intends to browse or complete a payment.
x402 connects agent wallets with paid online resources
The wallets form the buyer side of Cloudflare’s planned agent commerce system. Its Monetization Gateway will provide the seller side by allowing website owners and developers to charge for pages, datasets, APIs and MCP tools.
As crypto.news previously reported, Cloudflare opened the Monetization Gateway waitlist in July. Customers will be able to set fixed or variable prices and require payment before Cloudflare passes a request to their server.
Payments will use x402, an open protocol that attaches payment instructions to standard HTTP requests. When an agent requests a paid resource, the server returns an HTTP 402 “Payment Required” response containing the price and settlement instructions. The agent pays and resubmits the request with payment proof.
Coinbase introduced x402 in 2025 and later formed the x402 Foundation with Cloudflare. The foundation aims to maintain the system as a neutral standard rather than a protocol controlled by one company or blockchain.
The x402 website reported 75.41 million transactions, $24.24 million in volume, 94,060 buyers and 22,000 sellers over the latest 30 day period at the time of reporting. Those figures are live protocol metrics and may change as new activity is recorded.
In related coverage, crypto.news reported that Amazon Bedrock AgentCore integrated x402 payments, allowing agents to purchase services using USDC. That rollout shows Cloudflare is entering a growing market that already includes cloud providers, payment companies and blockchain developers.
Full wallet access depends on compliance and funding support
Cloudflare said it will initially offer conventional funding and withdrawal methods in supported locations. Eligible customers will also be able to fund their wallets directly with stablecoins. The company has not identified the first countries or regions included in that rollout.
It also has not disclosed which stablecoins or blockchains the wallets will support. The announcement did not name a custodian, banking partner, onramp provider or entity responsible for identity and compliance checks. Pricing, transaction fees and withdrawal limits also remain unknown.
These details will determine how widely companies can deploy the product. Wallet services involving stablecoin custody and fiat conversion can face different regulatory requirements across U.S. states and international markets.
The next verified update should clarify when Cloudflare customers can fund Account Wallets, create Virtual Wallets and complete live x402 purchases. Until then, users can claim wallet handles, but the core stablecoin payment features remain a planned service rather than a completed general release.
Be the first to comment