Skip to content
Launch20 Oct 2026

Mastercard opens early access to Agent Pay for Machines, letting AI agents pay for digital services within set limits

Built on the open x402 protocol, the service lets businesses give AI agents a budget and lets online providers charge them per request.

Illustration: A small robot arm at a service counter handing a sealed voucher to a clerk window, a ledger with a fixed allow…

What changed

Mastercard announced Agent Pay for Machines on 20 October 2026 at Cloudflare's Connect event and opened an early-access programme for developers. The service extends Mastercard's Agent Pay to cases where an AI agent buys digital services, such as data, research or images, on behalf of a business. Mastercard sums up its view in one line: payments aren't the hard part, authority is. The design builds on x402, an open protocol in which a paid web service answers a request with an HTTP 402 Payment Required response. A business gives its agent a task and a spending limit. When the agent hits a paid service, it creates a digitally signed voucher within that limit, and the provider checks the voucher and delivers. The exchanges happen off-chain, and providers can bundle vouchers and redeem them later, so an agent needs neither open-ended spending power nor a separate billing account with each seller. The pilot involved Cloudflare, Ant International, AIsa, Base, BVNK, Coinbase and the marketing agency Hype. In one test, an agent given a campaign budget made nine payments to two sellers without separate accounts, API keys or invoices. Coinbase supplied the wallet used to fund the agent, Base handled on-chain settlement, and BVNK acted as the agent wallet, using Mastercard's Global Money Platform to settle in fiat or stablecoins. Sellers can be paid in their preferred currency, token or rail. Early access includes buyer and seller APIs, a toolkit, a sandbox and documentation. No general release date or pricing has been given. The launch is aimed at a new kind of online merchant: companies that sell digital goods by the request, such as APIs, data feeds and content. It offers them a way to charge software buyers small amounts under a card network's rules, rather than through monthly contracts or prepaid credits.

What merchants must do

If you sell APIs, data or digital content, test the seller-side API in the sandbox to see whether per-request charging fits your pricing. Decide which currencies, tokens or rails you would accept for agent payments before you join a pilot. Log the voucher and spending-limit data for each agent order so you can answer disputes later.