The internet was built for humans. Every system that governs how websites identify visitors, process payments and manage access assumes, at its foundation, that a person is on the other end of the interaction. That assumption is breaking down. AI agents are increasingly browsing, signing up, purchasing and transacting on behalf of users — and the infrastructure designed for human behaviour is struggling to keep pace. Cloudflare's answer is Cloudflare Wallets and cloudflare.id: an identity and payment system built specifically for the agent-driven internet that is already arriving.
Key Points
Online businesses currently have limited tools to distinguish a legitimate AI assistant acting on a real customer's behalf from an automated system designed to abuse free trials, scrape data or commit fraud. Traditional bot detection relies on IP addresses, browser signatures and behavioural patterns — signals that do not reliably reveal whether an agent was authorised by a genuine user or deployed by an attacker.
The result is a binary and imperfect choice. Block aggressive automated traffic and risk turning away legitimate customer agents. Leave systems open and expose the platform to abuse at scale. Neither option is sustainable as AI agent traffic grows from a minority of internet activity toward something approaching parity with human-driven browsing.
Cloudflare's identity system addresses the root of the problem. Each Cloudflare account receives a unique web address that functions as a verified identifier — a cloudflare.id. Users can then extend that identity to individual agents they deploy, allowing any business on the receiving end to see who authorised a request before deciding whether to grant access or complete a transaction. Users can remain pseudonymous to the wider web while still being verifiable to specific merchants and services.
"When an agent shows up at your door, you need to know who sent it," said Matthew Prince, Co-Founder and CEO of Cloudflare. "Cloudflare can give agents a face — a link to the human or organisation that owns them — so that trust, accountability, and real commerce can follow."
The payment architecture mirrors how enterprises already manage distributed financial authority — but applies those controls to software agents rather than employees.
At the top level sits an Account Wallet, which can receive, hold and manage stablecoins funded through bank transfer. This is the master funding source for an account's agent activity. Below it, users can create Virtual Wallets assigned to specific agents. Each Virtual Wallet operates under rules set by the account owner — a spending cap that limits total outlay, an approved merchant list that restricts which services the agent can transact with and a maximum transaction size that prevents any single purchase from exceeding a defined threshold.
The stablecoin-based structure is a deliberate architectural choice. Rather than relying on card payment rails — which introduce chargebacks, fraud exposure and merchant processing costs — or direct account-to-account transfers for each purchase, Cloudflare has built a programmable money layer specifically designed for machine-to-machine transactions. Stablecoins settle instantly, are programmable at the smart contract level and eliminate the friction of card authorisation flows that were never designed for automated agent commerce.
The system integrates with Cloudflare's existing Monetisation Gateway, which allows online sellers to accept payments from software agents. Together, the identity and wallet infrastructure creates both sides of an agent-based commercial transaction: verified identity for merchants, and controlled payment capability for agent owners.
Cloudflare's move into agent identity and payment infrastructure is strategically significant in ways that extend well beyond the immediate product launch.
Cloudflare already sits in a uniquely powerful position in internet infrastructure — its network sits between the open internet and a significant portion of the world's websites, handling DNS, DDoS protection, CDN delivery and security for millions of domains. Adding identity and payment verification to that stack means Cloudflare could become the de facto trust layer for agent-to-merchant transactions at internet scale.
That positioning is not accidental. If cloudflare.id becomes the standard by which merchants verify agent identity — the way SSL certificates became the standard for website security — Cloudflare gains a structural role in every commercial transaction conducted by an AI agent across the web. The network effects of that position would be enormous and very difficult for competitors to replicate.
The decision to build on stablecoins rather than traditional payment rails is a statement about where Cloudflare believes the future of machine-to-machine payments lies. Card rails have significant friction for automated transactions — authorisation flows, chargeback exposure and interchange fees all add cost and complexity that make them poorly suited to the volume and speed of agent commerce at scale.
Stablecoins, by contrast, are programmable, instant and cheap to transact. They can carry spend rules in the transaction itself. They settle without intermediaries. For a payment system designed to handle millions of agent micro-transactions across the web, they are a more elegant foundation than anything card networks currently offer.
The risk is adoption. Stablecoin infrastructure requires merchants to accept stablecoin payments and users to fund wallets with digital assets — neither of which is frictionless today. Cloudflare's existing merchant relationships through its Monetisation Gateway give it a distribution advantage, but widespread adoption will depend on how quickly the friction of stablecoin on-ramping can be reduced for mainstream users.
No major competitor currently offers a comparable combination of agent identity verification and programmable payment controls at internet infrastructure scale. Stripe, Adyen and other payment processors have agent payment capabilities on their roadmaps, but none has the identity infrastructure layer that Cloudflare is building through cloudflare.id. Browser makers and operating system providers could theoretically build agent identity systems, but they lack Cloudflare's position between agents and merchants at the network layer.
The most significant competitive pressure may come from AI platform providers themselves — OpenAI, Anthropic and Google are all building agent frameworks and could theoretically build payment and identity layers into those frameworks directly. But that would require each AI provider to independently build merchant relationships and payment infrastructure, a significant undertaking that Cloudflare has already started.
The near-term roadmap — fund deposits, withdrawals and Virtual Wallet issuance — establishes the basic financial plumbing. The medium-term opportunity is considerably larger. If agent commerce grows as expected, Cloudflare Wallets could evolve into a programmable financial operating system for the agentic web — handling not just payment authorisation but spend analytics, agent budget management, merchant verification and potentially regulatory compliance reporting for agent-initiated transactions.
The longer-term question is whether cloudflare.id becomes an open standard or remains proprietary Cloudflare infrastructure. An open standard would accelerate adoption across the industry but reduce Cloudflare's competitive moat. A proprietary system would deepen lock-in but may slow adoption if merchants and agent frameworks resist dependence on a single provider's identity layer.
Either way, Cloudflare has moved first in a space that will matter enormously as AI agents become the primary way many users interact with the commercial web. First-mover advantage in identity and payment infrastructure tends to be durable — the switching costs of migrating to a different trust layer once one is established are significant. That is the strategic logic behind the launch, and it is a sound one.
Sources
Cloudflare Wallets and cloudflare.id product announcement, August 2026. Matthew Prince, Co-Founder and CEO of Cloudflare, statement on agent identity and commerce, 2026. Cloudflare Monetisation Gateway product documentation. Industry analysis of AI agent commerce trends and infrastructure requirements, 2026.
Mac users are being targeted by fake Cloudflare CAPTCHA pages that trick them into running commands which install the Infiniti Stealer malware. The malware quietly steals crypto wallets, browser passwords, and other sensitive data without any visible signs.
AnaisWho is using x402 for development, and why is its adoption accelerating?
JinseFinanceCompared to the x402 vs. MPP debate, what truly matters is Cloudflare's decision on who to partner with for co-construction.
JinseFinanceWhen the "decentralized" revolution you tout can't function because a company's configuration file is too large, who is really in control?
JinseFinanceA faulty Cloudflare configuration file caused a major outage that briefly took down many popular websites and apps. The issue spread quickly because so many services rely on Cloudflare to manage their traffic.
AnaisCloudflare plans to launch the US dollar stablecoin NET Dollar, targeting AI intelligent payments.
JinseFinanceThe removal of its iOS and Chrome Extension wallets from the market is scheduled for November 1, 2023, although customers will still be able to access their wallets until October 1.
Coinlive Due to Cloudflare's outage, many users trying to access certain websites will receive a "500 Internal Server Error" notification.
CointelegraphWallet.app is launching the next stage in its EU-based, fully compliant crypto custody wallet, exchange and payment platform that will ...
Bitcoinist“Cloudflare is going to participate in the research and development of the core infrastructure that helps keep Ethereum secure, fast, as well as energy-efficient for everyone,” the firm stated.
Cointelegraph