Cloudflare Wallets and cloudflare.pay Give AI Agents IDs and Budgets

What Cloudflare actually announced

On August 4, Cloudflare announced two connected products for software agents that shop and pay on behalf of people. The first is an identity service called cloudflare.pay. The second is a wallet system that holds money for an agent to spend.21 The identity piece gives each user a permanent web address that agents can read. A user can attach that address to their agents so merchants know who sent them, or choose to stay pseudonymous.21 The wallet piece uses stablecoins. A bank transfer is converted into a dollar-pegged token, and the user then lets an agent spend from that balance.21

The wallets come in two tiers. An Account Wallet is the human-controlled store of funds and handles deposits, withdrawals and stablecoin balances. Each agent can then get its own Virtual Wallet, which draws from the Account Wallet.22 Owners can set an overall spending cap, a list of approved sellers and a maximum amount per transaction for each Virtual Wallet. Unusually fast or unexpected spending can be flagged for a person to review.22 Handles look like research.example.cloudflare.pay. They are built on Web Bot Auth, Cloudflare's existing system that identifies automated traffic using cryptographic keypairs.23

CEO Matthew Prince presented the launch as a question of accountability. He said that when an agent arrives at a business, the business needs to know who sent it, and that Cloudflare can link the agent to the person or organization that owns it.25

Announced is not the same as live

The coverage diverges most on how much of this exists today. Fortune's headline said Cloudflare had "launched" a wallet for AI shopping.21 Most other outlets point out that only one part worked on launch day: reserving a cloudflare.pay handle. Funding, withdrawals and issuing Virtual Wallets were promised "in the coming months."25 Six weeks later, one developer found that a reserved handle still only showed the name and offered a notification for when Wallets became available. Cloudflare's own documentation said a reserved handle could not yet send, receive or hold funds.19

One line in Fortune's later reporting adds to the confusion. It described cloudflare.pay as an August rollout that "lets" agents prove they act for a user and spend from a linked wallet.4 The stronger reading is that August delivered a design plus a name-reservation drive, not a working purchase flow. That gap matters for anyone planning around the product.

The seller side moved first

The more concrete progress is on the merchant side. On September 30, Cloudflare opened a closed beta of its Monetization Gateway, which lets domain owners charge agents for websites, APIs, MCP tools and datasets.11 It uses the HTTP 402 "Payment Required" status code, so payment happens inside the request itself, with no checkout page.11 Payments are verified and settled through Coinbase's x402 Facilitator, in USDC on the Base blockchain.11 Prices can range from $0.001 to $100 per request.20

The first customers are a useful guide to what "agentic commerce" means right now. Cloudflare's own AI Gateway lets U.S. customers pay for model inference per request. Ceramic.ai sells web searches without requiring an API key. Stocktwits sells per-request market sentiment signals. API2PDF charges for document generation.112 API2PDF reported that its old rule, requiring a credit card after the first month, caused more than half of potential customers to drop off. That figure shows the kind of sign-up friction the system is designed to remove.10

The beta is limited to eligible U.S. buyers and sellers.17 Cloudflare product manager Rohin Lohe said the company plans to add features and users through the rest of the year and aims for wide availability by early 2027.4 Several outlets describe Wallets and the Monetization Gateway as two halves of one market, buyers on one side and sellers on the other, both running on Cloudflare's network.22

"Shopping" is mostly machines buying from machines

The headlines talk about AI shopping, but the transactions now being enabled are mostly not consumer purchases. All four launch customers sell data, search or computing to software, not goods to households.2 The broader x402 market looks the same. One newsletter analysis cites roughly 75.4 million transactions worth about $24.2 million over a 30-day window, an average of around 32 cents each. The same analysis notes that growth has disappointed people hoping for agent-driven commerce.8 An academic study it cites found an average payment of $0.27 across 143 million settlements, with 28.5% of transactions worth less than one cent.8

The best way to read Cloudflare's move is as infrastructure for micropayments between software, which may later expand into consumer shopping. Even practitioners who back the model admit demand is thin. A Search Engine Journal contributor got Claude Code to pay a cent per page on his site, but all of his payments used test tokens with no real value, and he controlled both the buying and selling agents.19

Optional identity: a deliberate trade-off

Analysts disagree about whether this design solves the trust problem. Andrew O'Connor of PSE Consulting said that giving agents a lasting identity and a secure way to pay removes one of the biggest barriers to adoption. He added that merchants need to know an agent is authenticated and acting within the permissions a consumer has granted.15 Other coverage points out that identity is optional. An agent can hold a funded Virtual Wallet and transact without ever saying who it works for, so Cloudflare's accountability pitch only covers agents that choose to identify themselves. Sellers can also still accept anonymous x402 payments from unidentified wallets.23

This looks like a deliberate choice. Making identity mandatory would add back the sign-up friction the products are meant to remove, so Cloudflare chose broad adoption over gatekeeping. The decision about requiring identity then falls to merchants, who will decide when to demand it. It also leaves a gap that banks are trying to fill. Lead Bank has proposed a legal status called the "Authorized Financial Agent," with mandatory credentials, signed spending mandates, assigned liability and oversight. The analysis notes that x402 has none of these protections unless it is wrapped in another protocol.8 That same analysis also notes that Lead sells its own agent payment products, so its proposed rules may favor banks like itself.8

Another point of dispute is how new the identity layer really is. One analysis argues that agent identity did not start in August 2026. Cloudflare proposed Web Bot Auth in May 2025, and Visa, Mastercard and American Express were building on it by October 2025. On this view, the new parts are payments and readable handles.27 That account fits Cloudflare's own description of the handles as a layer on top of Web Bot Auth.23

Plenty of competitors, one shared standard

Cloudflare is entering a crowded field. Visa has its Trusted Agent Protocol, Mastercard has Agent Pay, and Google has published the Agent Payments Protocol (AP2).15 Crypto payments firm MoonPay launched a consumer AI wallet called PayBox a week before Cloudflare's announcement.21 Stripe and OpenAI's Agentic Commerce Protocol, and the Universal Commerce Protocol backed by Google, Shopify and major retailers, compete for the checkout layer.7

The main counterweight to fragmentation is the x402 Foundation. It began operating under the Linux Foundation on July 14 with 40 members, including Visa, Mastercard, Google, AWS, Stripe and Cloudflare.19 It plans to support payment types from cards to stablecoins.7 O'Connor warns that competing protocols could produce trust models that don't work with each other, slowing progress just as interest grows.15 Banks and card networks may be taking a hedged approach. Cloudflare is among the launch supporters of Mastercard's Agent Pay for Machines.7 At the same time, card networks belong to the foundation that governs the stablecoin-based protocol Cloudflare is building on.26

Why it matters

Cloudflare's position is a strong one. One analysis says it sits in front of about a quarter of the web. If machine payments ran through Cloudflare rather than through checkout providers like Stripe, the analysis puts the prize at around $200 billion.8 Cloudflare's existing reach lets it offer agents both a payment method and a verified identity at the point where their requests already arrive. That is a real structural advantage that card networks, which sit further away from web traffic, cannot easily copy.

The unresolved problems are governance and demand. No major jurisdiction has settled who is liable when an agent's transaction goes wrong or the agent is compromised.15 Developers also have practical problems to solve: per-call spending caps don't stop large total costs over a long task, and retrying a failed paid request can mean paying twice.20 The products show where Cloudflare thinks agent payments are going. The next test is whether real agents start spending real money once the wallets go live.