An AI agent may need to buy a search result, call a paid software tool or obtain a piece of data while completing a task. Each purchase could cost only a fraction of a cent. The payment system has to make that exchange economical and allow software to complete it without stopping for a person to enter card details.
This is where advocates of stablecoins see a practical opening. Their case rests on the size and frequency of the payments, the ability to settle them through software, and the difficulty of making a conventional checkout fit the process. The counterargument is that payment protection and established billing relationships still have value.
Cloudflare’s Monetization Gateway, opened in closed beta on 30 September, provides a current example. It allows suppliers to charge for digital resources through the x402 protocol, with payments settled in USDC on Base. USDC is designed to track the US dollar. Cloudflare’s documentation says both buyers and sellers in the beta must be based in the United States.
The gateway puts payment within the web request process. Software requests a resource, receives the payment requirements, signs an authorisation and retries the request. The gateway verifies and settles the payment before the buyer receives the resource. There is no redirect to a separate checkout page.
For Jose Lejin P J, an IEEE Senior Member who designs production AI agents and cybersecurity controls, this is a payment mechanism suited to software buying small amounts of access when it needs them. He identifies paid APIs and tool calls as natural uses. APIs let software request a service or information from another system.
“Stablecoins win when the payment has to be made by software, for a tiny amount, at the moment of the request,” says the engineer.
His argument concerns the economics of charging individually for very small requests. A service might be useful enough for an agent to purchase, yet too inexpensive to justify a separate card transaction. A protocol that combines the request and the payment could allow a supplier to sell that service by use.
That does not mean the underlying service cannot be paid for through conventional systems. A subscription or consolidated usage bill can also cover many small requests. The difference is whether the buyer needs an existing billing relationship or can obtain a resource through a single paid interaction.
Johannes Gugl, co-founder and chief product officer of Cropr Finance, sees an advantage in the direct transfer of blockchain-based currencies. An agent could pay a few cents for an API call and settle the transaction at the time of use. He argues that the multiple steps and intermediaries involved in card payments make them more complicated to incorporate into an agent.
Cards versus Agents
However, Gugl also identifies reasons why businesses may prefer cards, particularly when acceptance and protection matter more than immediate settlement.
“Cards still hold two big advantages. They are accepted almost everywhere, and they come with strong security measures like fraud screening and chargebacks. For many payments, that protection matters more than speed,” says Gugl.
This is an important qualification. A payment system suitable for a small digital purchase may offer a different balance of benefits from one used for a larger transaction, a recurring subscription or a service whose delivery could be disputed. The ability to move money quickly answers only part of the buyer’s problem.
Serhii Nikolaichuk, founder of The Capital Index, similarly locates the strongest case for stablecoins in small purchases of digital resources. He describes a market in which software pays for an API call, a dataset, a page or a tool. In that setting, settlement can occur as part of the task rather than through a checkout designed for a human customer.
He points to the ability to make payments at any hour and to apply spending rules through the wallet. Those controls require deliberate implementation: using a stablecoin does not itself give an agent an appropriate budget or decide which suppliers it may pay.
Friction in Traditional Payments
Nikolaichuk is also clear that the features of conventional payments deserve weight in the comparison.
“Chargebacks, fraud protection and consumer law are features, not friction,” says Nikolaichuk.
The engineer makes a similar distinction between small requests made by software and purchases where a person may need their money back. He sees cards and bank transfers as better suited to larger amounts or transactions with human involvement. For an ordinary software subscription, he considers a card the more practical option.
The three contributions therefore support a case for choosing payment systems according to the transaction. Stablecoins appear well suited to immediate purchases of small digital resources. Cards retain advantages where merchant acceptance, fraud screening and established dispute processes are priorities.
There is also a difference between a refund and a reversal. A supplier can return a stablecoin payment, but the original transfer does not automatically include a card-style chargeback process. Nikolaichuk argues that recovery mechanisms must be designed into the service, whether through escrow, refunds or records that establish what was purchased.
For now, the Cloudflare beta provides a bounded implementation of this approach. Its US eligibility rules also show that the broader ambition of software paying across borders should be distinguished from the reach of an individual product available today.
The commercial opportunity is to let an agent buy a useful resource at the moment it needs it, at a price that makes sense for both parties. Whether stablecoins are the best way to do that will depend on the cost of the payment, the existing supplier relationship and the protection the buyer needs. Gugl’s qualification is central: for many purchases, protection will matter more than speed.
News sources
Cloudflare, Monetization Gateway documentation, updated 30 September 2026. https://developers.cloudflare.com/monetization-gateway/
Cloudflare, Monetization Gateway beta announcement, 30 September 2026. https://blog.cloudflare.com/monetization-gateway-beta/

