Cloudflare Introduces AI Wallet Support for x402 Payments
On August 4, Cloudflare commenced the initial phase of its programmable wallet deployment, allowing users to secure unique wallet handles for upcoming stablecoin transactions managed by AI agents.
Summary
- Cloudflare users can now reserve wallet handles, with capabilities for stablecoin funding and payments anticipated shortly.
- Account Wallets are designed to hold funds, while Virtual Wallets empower authenticated agents to make limited online purchases.
- Owners are able to set spending limits, approve merchants, restrict transaction amounts, and request human input when necessary.
- x402 has processed 75.41 million transactions totaling $24.24 million in the past month.
- Information on supported stablecoins, networks, custody partners, fees, and the complete launch timeline is still awaited from Cloudflare.
According to an official statement from Cloudflare, users can select a handle associated with their Cloudflare account via cloudflare.pay. However, functionalities for funding wallets and utilizing them for purchasing APIs, data, and online content are projected to be available “soon,” although a clear launch date has not been provided.
This clarification indicates that Cloudflare has opened up the identity layer of the product rather than delivering a fully functional payment system. Customers should not assume that the touted features for stablecoin storage, withdrawal, or automated spending are currently operational.
Cloudflare Wallets start with handles, not payments
Cloudflare plans to provide two types of wallets. Account Wallets will be managed by individual or organizational users, enabling them to deposit funds, withdraw balances, and delegate spending authority to AI agents.
Virtual Wallets will function using API keys, allowing agents to acquire services based on the permissions established by the Account Wallet holder. Potential purchases may include APIs, Model Context Protocol tools, data, AI inference, and online content.
The company is also crafting a human-readable identity framework for these wallets. For instance, a business might allocate an address like research.example.cloudflare.pay to an agent, associating the software with a specific organization. However, establishing that identity will be optional, and merchants can decide whether to cater to unidentified agents or prioritize known ones.
Cloudflare compares this system to how the Domain Name System connects user-friendly website names with less intuitive internet addresses. The wallet handle will link to an agent’s cryptographic key while maintaining the underlying verification process.
Spending controls aim to mitigate autonomous agent risks
Cloudflare highlighted that Account Wallet owners can impose spending caps, generate approved merchant lists, and limit transaction amounts, allowing agents to test low-cost services without requiring human approval for each transaction.
For instance, a company may assign a weekly budget for AI inference to each employee’s agent. When a wallet hits its limit, the agent may seek a manual override from an authorized administrator. Rapidly increasing expenditures could also trigger a review before the owner increases the budget or adds more funds.
Cloudflare has positioned these constraints as safeguards against overspending. However, it has not published technical documentation regarding how lost API keys, compromised agents, disputed payments, or unauthorized transactions will be managed.
The company has partnered with Visa and Mastercard to create systems that assist merchants in distinguishing between authorized shopping agents and malicious bots. Visa’s Trusted Agent Protocol and Mastercard’s Agent Pay utilize Cloudflare’s Web Bot Auth system to verify cryptographic signatures and determine whether an agent intends to browse or finalize a payment.
x402 links agent wallets with paid online resources
The wallets represent the consumer’s side of Cloudflare’s planned agent commerce system. Its Monetization Gateway will cater to the seller’s side, allowing web owners and developers to charge for pages, datasets, APIs, and MCP tools.
As previously mentioned by crypto.news, Cloudflare opened the waitlist for the Monetization Gateway in July. Customers will have the choice to set fixed or variable pricing and require payment prior to Cloudflare processing their requests.
Payments will utilize x402, an open protocol that adds payment instructions to standard HTTP requests. When an agent seeks a paid resource, the server responds with an HTTP 402 “Payment Required” message, which includes the price and settlement instructions. The agent will then pay and resubmit the request with proof of payment.
Coinbase introduced x402 in 2025 and subsequently formed the x402 Foundation in collaboration with Cloudflare. The foundation aims to uphold the system as a neutral standard, rather than a protocol controlled by a single company or blockchain.
The x402 website reported 75.41 million transactions resulting in $24.24 million in volume, involving 94,060 buyers and 22,000 sellers over the last 30-day period. These statistics represent current protocol metrics and may vary as new activities are logged.
In related developments, crypto.news reported that Amazon Bedrock AgentCore has integrated x402 payments, allowing agents to acquire services using USDC. This rollout underscores Cloudflare’s entry into a growing market already populated by cloud providers, payment companies, and blockchain developers.
Full wallet access hinges on compliance and funding support
Initially, Cloudflare stated it will offer standard funding and withdrawal methods in supported locations. Eligible users will also be able to fund their wallets directly with stablecoins, though the company has not disclosed which regions or countries will be included in this rollout.
Moreover, the details regarding supported stablecoins or blockchains remain undisclosed. The announcement did not specify a custodian, banking partner, onramp provider, or entity responsible for identity and compliance verifications. Further information on pricing, transaction fees, and withdrawal limits is also currently unclear.
These specifics will dictate how broadly companies can adopt the product. Wallet services involving stablecoin custody and fiat conversions can face varying regulatory requirements across U.S. states and international markets.
The next confirmed update should provide clarity on when Cloudflare customers can fund Account Wallets, create Virtual Wallets, and engage in live x402 transactions. Until then, users may reserve wallet handles, but the core stablecoin payment functionalities remain anticipated services rather than fully launched features.