--- title: "Mastercard's agent payments just demoed through Cloudflare, but Coinbase keeps the fee" description: "Mastercard opened Agent Pay for Machines at Cloudflare Connect with nine live agent payments, eight through Cloudflare's AI Gateway. The vouchers clear on Coinbase rails under a card-network brand, while Cloudflare still books the traffic, not the fee." publisher: "The Inference" section: "Money" published: 2026-10-21T15:23:50.967Z modified: 2026-10-21T15:23:50.967Z canonical: https://theinference.org/article/mastercard-s-agent-payments-just-demoed-through-cloudflare-but-coinbase-keeps-the-fee language: en keywords: "Payments, AI Agents, Cloudflare, Mastercard, Stablecoins" --- # Mastercard's agent payments just demoed through Cloudflare, but Coinbase keeps the fee > Mastercard opened Agent Pay for Machines at Cloudflare Connect with nine live agent payments, eight through Cloudflare's AI Gateway. The vouchers clear on Coinbase rails under a card-network brand, while Cloudflare still books the traffic, not the fee. At [Cloudflare](https://theinference.org/markets/companies/cloudflare) Connect in San Francisco this week, [Mastercard](https://theinference.org/markets/companies/mastercard)'s chief product officer [Jorn Lambert](https://theinference.org/markets/people/jorn-lambert) let an AI agent shop: nine payments, two independent merchants, one pre-approved budget, zero accounts, zero API keys, zero invoices. The agent, running on [Amazon](https://theinference.org/markets/companies/amazon) Bedrock for the marketing agency Hype, bought social media research from AIsa, a research vendor, then generated eight campaign images through Cloudflare's AI Gateway. Eight of the nine payments ran through Cloudflare's own product. Mastercard opened early-access APIs, SDKs and a sandbox the same day, the first release beyond the June pilot cohort of Cloudflare, [Coinbase](https://theinference.org/markets/companies/coinbase), Ant International, BVNK, Base, AIsa and Hype [1][2]. ## The payment does not run on Cloudflare's infrastructure When the agent hits a paid endpoint, the service [returns HTTP's long-dormant "402 Payment Required" code and the agent answers with a digitally signed voucher](https://decrypt.co/381373/mastercard-opens-up-ai-agent-payments-with-early-access-and-live-demo), an off-chain promise to pay within its budget [2]. That voucher is [verified by Coinbase's facilitator, with settlement following later on Base or Solana](https://www.techtimes.com/articles/329316/20261021/mastercard-opens-developer-apis-ai-agent-payments-built-x402-protocol.htm) [1]. The rails carrying it belong to BVNK, the stablecoin firm Mastercard bought in August for $1.8 billion including $300 million contingent consideration [1]. Coinbase's platform has already processed more than 100 million x402 payments, and the protocol now sits under Linux Foundation governance with more than 40 members including Visa, [Stripe](https://theinference.org/markets/companies/stripe), Google and AWS [1]. Visa's rival Trusted Agent Protocol is built on Cloudflare's Web Bot Auth [1]. So the standard itself is contested turf: Cloudflare hosts the agents, authenticates them and, in this demo, sells to them, while the payment fee accrues to Coinbase's rails under a card-network brand. ## The merchant side needs the machines to pay Cloudflare [counts 10 million developers, up from 7.4 million a quarter earlier](https://thenextweb.com/news/cloudflare-developers-10-million-ai-agents-workers), and says daily agent requests on its network grew more than 1,700% in a year, with more than half of its traffic now not human [3]. The release gave no revenue figure and no paying-developer count [3]. Mastercard, for its part, has offered no timeline for commercial availability [1]. Two things decide whether this becomes Cloudflare's revenue rather than its goodwill: whether the next Cloudflare print discloses paying developers or agent revenue for the first time, and whether Mastercard names a general-availability date for AP4M. [Our Oct. 20 piece](https://theinference.org/article/cloudflare-s-bouncer-now-runs-the-bank-for-ai-agents) covered the 15% stock fall and the insider sales; what has changed since is the payment side. Until then the machine half of the traffic has to start paying, and when it does, someone else keeps the fee. ## Takeaway Mastercard's live agent-payment demo at Cloudflare Connect shows the traffic is Cloudflare's but the fee is Coinbase's: until Cloudflare discloses paying developers or agent revenue and Mastercard names a GA date for AP4M, the machine half of the internet stays unpaid. ## Sources 1. [Tech Times, Mastercard Opens Developer APIs for AI Agent Payments Built on x402 Protocol, 21 October 2026](https://www.techtimes.com/articles/329316/20261021/mastercard-opens-developer-apis-ai-agent-payments-built-x402-protocol.htm) 2. [Decrypt, Mastercard Opens Up AI Agent Payments With Early Access and Live Demo, 21 October 2026](https://decrypt.co/381373/mastercard-opens-up-ai-agent-payments-with-early-access-and-live-demo) 3. [The Next Web, Cloudflare passes 10 million developers, up 35% in a quarter, 21 October 2026](https://thenextweb.com/news/cloudflare-developers-10-million-ai-agents-workers) --- Mastercard's agent payments just demoed through Cloudflare, but Coinbase keeps the fee — The Inference. Canonical: https://theinference.org/article/mastercard-s-agent-payments-just-demoed-through-cloudflare-but-coinbase-keeps-the-fee