Cloudflare Wallets: your next buyer has a .pay handle

Cloudflare spent the last year building the side of agentic commerce where you charge the robots. On August 4 it shipped the other side: Cloudflare Wallets and cloudflare.pay, which give AI agents a stable identity and a funded wallet they can spend from. If you sell anything online, the practical question is no longer whether agents will check out on your site. It's whether you can tell which human is behind the one that just did.

What actually happened

Cloudflare announced Wallets and cloudflare.pay on August 4. Two pieces:

Identity. Every Cloudflare account gets a unique web address that functions as a stable ID, and you can extend that identity down to individual agents. A research agent might live at research.example.cloudflare.pay. When that agent hits a merchant, the merchant can see which organization authorized it — not just another unattributed user-agent string.

Money. The Account Wallet can receive, hold, and manage stablecoins. From it you issue Virtual Wallets to specific agents, with guardrails set at issuance: a spending cap, an approved merchant list, and a maximum single-transaction size the agent can't exceed on its own. Per Fortune, funding runs through bank transfer converted into dollar-pegged stablecoins, and users can stay pseudonymous behind the handle.

Handle reservation opened August 4. Full wallet functionality — onramping, offramping, issuing Virtual Wallets — is slated for "the coming months." No pricing was disclosed.

Cloudflare is explicit that this pairs with its Monetization Gateway to complete a two-sided market: agents that can pay, merchants that can charge. Chief Strategy Officer Stephanie Cohen framed the bet around bots already making up the majority of web traffic.

Why agentic commerce matters for your business

Here's the part worth acting on: identity is arriving before money does.

Handles are reservable today. Funded wallets are months out. That gap is your window. When agent traffic starts carrying a verifiable handle, your storefront either reads it and decides what to do, or it doesn't and treats every agent as anonymous — which means you either block real buyers or let unattributed software transact.

That's a decision your checkout is making right now, by default, badly.

Three things to sort out before wallets go live:

1. Can your stack see agent identity at all? If your bot rules end at "block or allow," you have no third option for allow, attributed, with limits. That's the option that matters.
2. What's your policy when the buyer is software? Different return terms? A transaction ceiling? Decide it deliberately, not in an incident.
3. Don't build on one vendor's handle. cloudflare.pay is a Cloudflare namespace. Mastercard, Visa, and Stripe all have competing agent-identity plays. Treat "which agent is this" as a field in your own order record, populated by whichever scheme shows up — not as a Cloudflare integration.

The recurring failure in agentic commerce isn't picking wrong. It's wiring the vendor's proprietary shape directly into your order flow and discovering the switching cost later. We've said the same about agent payment rails and agents with bank accounts.

Sources: Cloudflare, Fortune.