Cloudflare launched Cloudflare Wallets and cloudflare.pay on August 4, 2026, giving AI agents a way to hold funds and an optional identity handle. Two wallet tiers control spending: a human-owned Account Wallet and an agent-owned Virtual Wallet capped by an allowance, merchant allow-list, and per-transaction limit. Declaring an agent’s identity is optional, not required, which means Cloudflare’s own pitch about trust and accountability only applies to agents that choose to use it. This is the third piece of infrastructure Cloudflare has built for agentic commerce in under a year, and each one has chosen frictionless reach over mandatory gatekeeping.
Introducing Cloudflare Wallets. They will allow you to store stablecoins, purchase services, and receive funds across the web. https://t.co/ucAaoKMs4Q
— Cloudflare (@Cloudflare) August 4, 2026
An AI agent trying to sign up for a new API today runs into a wall built for humans. It hits a login page it can’t reasonably navigate, has no way to add a payment method without a person stepping in, and if it does get that far, still needs someone to generate an API key on its behalf. The task was to try the API, compare it against three others, and pick the best one. Instead, it gets kicked back to a human, and the whole point of using an agent evaporates.
What Cloudflare actually built
Cloudflare’s answer, announced August 4, is a two part fix: Cloudflare Wallets and a companion identity system called cloudflare.pay. Handle reservation opened the same day. Full wallet functionality, including funding, spending, and issuing wallets to individual agents, is expected in the coming months. The pitch is straightforward: give agents a stable identity and a native way to pay, and the onboarding wall disappears.
Account Wallets hold the money, Virtual Wallets spend it
The mechanics split into two wallet types. An Account Wallet belongs to a human and holds stablecoins, with its owner deciding how much to release. A Virtual Wallet belongs to an agent, funded from that Account Wallet, and spends against three guardrails set by the human:
- a total allowance
- an approved merchant list
- a hard per transaction ceiling
An agent that hits its limit doesn’t get to override it. It can request a manual override from a human authorized to make changes to the Account Wallet. This is the part of the design doing the actual risk control work: cap the number, and the worst case an agent can do to your account is bounded by that number.
Identity is optional, and that’s the part worth sitting with
The identity half of the system works differently, and this is where the design gets more interesting than the wallet mechanics. Declaring an agent’s identity through cloudflare.pay is not required. An agent can hold a funded Virtual Wallet, transact with merchants, and never say which human or organization it belongs to. Cloudflare’s own framing for why identity matters at all, in CEO Matthew Prince’s words, is that giving an agent a public face is what lets
“trust, accountability, and real commerce can follow.”
That’s a real design choice, not an oversight, and it lines up with what Cloudflare says the whole product exists to fix: friction. A mandatory identity requirement would recreate exactly the kind of gate the company built this system to remove, one more piece of information an agent has to supply before it can transact. Optional identity keeps onboarding frictionless for every agent, including ones that never intend to identify themselves. Cloudflare gets the low friction adoption it wants. The accountability layer it’s selling only shows up for agents that opt in.
The third piece Cloudflare has built this year, and each one chose reach over gatekeeping
This isn’t Cloudflare’s first move into agent facing infrastructure, and the pattern holds. In October 2025, the company built the Trusted Agent Protocol with Visa, Mastercard, and American Express. That system, too, works on an opt in basis: it lets merchants recognize agents that choose to authenticate, it doesn’t require it. Earlier this month, Monetization Gateway gave sellers a way to charge for APIs and content per request, with no identity check built into the payment itself. Mastercard has also been building infrastructure for AI-to-AI payments, reflecting a broader industry push toward autonomous commerce.
Wallets is the third piece, and it repeats the same choice: sellers can charge, card network partners can optionally verify, and now agents can optionally identify themselves while they pay. Read against that sequence, the identity system isn’t an isolated design decision. It’s Cloudflare consistently picking frictionless reach over mandatory gatekeeping, three times in less than a year.
What merchants are actually left holding
Go back to the agent at the login wall. With a funded Virtual Wallet, it clears that wall in one request, no human, no manual payment step. But the merchant on the other end still doesn’t automatically know whose agent it is. Similar questions around agent identity and authorization are also being explored in blockchain infrastructure, including Sui’s Seal MPC framework.
That information exists, sitting in cloudflare.pay, available if the agent chooses to share it. Whether merchants come to require that disclosure as a condition of the sale, the way some already require a business license or a verified email, is the next real decision point in this system, and it’s one Cloudflare hasn’t made for them.
FAQ
What’s the difference between an Account Wallet and a Virtual Wallet?
An Account Wallet is controlled by a human and holds funds. A Virtual Wallet belongs to an individual agent, is funded from an Account Wallet, and spends within limits set by the Account Wallet’s owner.
Do agents have to declare their identity?
No. Declaring identity through cloudflare.pay is optional. An agent can transact using a Virtual Wallet without identifying which human or organization it belongs to.
When does full wallet access launch?
Handle reservation opened August 4, 2026. Full functionality, including funding, spending, and issuing Virtual Wallets, is expected in the coming months, with no specific date announced yet.
AI Disclosure: Cryip uses AI-assisted tools to help refine language — correcting spelling and grammar and simplifying complex terms for readability.
We do this to make crypto topics easier to understand for readers at all experience levels. AI does not draft facts, sources, or conclusions. Every article is reviewed and approved by a human editor before publication. Read our full AI Use & Content Policy.
