Mastercard has opened early access to Agent Pay for Machines, a system designed to let AI agents buy digital services within budgets and permissions set by a business. The company showed the system at Cloudflare Connect on October 20, 2026, after pilot work with Cloudflare, Ant International, AIsa, Base, BVNK, Coinbase and Hype. This is an early-access developer product, not a general consumer checkout service.
What Mastercard announced
Mastercard’s October 20 announcement says Agent Pay for Machines gives software agents a way to pay for services such as data, AI models, computing power and APIs. The first buyer- and seller-side APIs, toolkit, sandbox and documentation are available through an early-access program.
The distinction matters. Mastercard is not saying that any agent can spend from any card today. A business defines the task, permissions and spending limit first. The agent then operates inside those boundaries.
How the payment flow works
When a digital service asks for payment, the service returns an HTTP 402 “Payment Required” response. The agent creates a digitally signed voucher that promises payment within its approved limit. The seller verifies the voucher, delivers the service and can redeem vouchers later.
Mastercard says these exchanges happen off-chain, while final settlement can use different rails. In the demonstration described by the company, Coinbase Developer Platform supplied wallet infrastructure, Base handled on-chain settlement and BVNK used Mastercard Global Money Platform to support payment and settlement in fiat or stablecoins.
That is a different model from giving an agent a reusable account password or unlimited spending authority. The budget and task are approved in advance, while each seller checks the signed voucher before providing the service.
What the Cloudflare demo showed
Mastercard’s example used an agent working on a sample marketing campaign. The agent bought social-media research from AIsa and generated eight campaign images through Cloudflare AI Gateway. Mastercard says the process produced nine payments to two independent merchants under one approved budget, without separate accounts, API keys or invoices for each seller.
The demo is useful because it shows the intended workflow: one authorization can cover several small service purchases as an agent completes a larger task. It does not establish general availability, merchant coverage or production performance outside the pilot.
Where x402 fits
Agent Pay for Machines builds on x402, an open protocol that lets an online service request payment through the HTTP 402 response. Mastercard adds a trust and settlement layer around that pattern, according to its announcement.
Our plain-language x402 explainer covers the underlying request-and-payment flow. The broader agentic commerce protocol tracker compares x402 with AP2, Visa Trusted Agent Protocol and other systems.
What businesses should check before trying it
Early access is the key limitation. A business evaluating the system should confirm which currencies and settlement rails are available in its region, how spending limits are enforced, how vouchers can be revoked, and which party handles disputes or a compromised agent.
The announcement describes permissions, signatures and spending limits, but it does not publish a full commercial price list or promise that every Mastercard merchant can accept these machine payments. Those details should come from the early-access documentation and agreements, not from the demo.
For now, the practical change is that developers can request access to a working buyer-and-seller toolset. The product is meant for agent-to-agent purchases of digital services, not for replacing ordinary card checkout for consumers.
