Mastercard opened early access to Agent Pay for Machines on October 20 with buyer- and seller-side APIs, a developer toolkit, a sandbox and documentation. According to Mastercard, the release followed end-to-end pilots involving Cloudflare, Ant International, BVNK, AIsa, Base and Coinbase.
The product is built for an AI agent to make multiple purchases authorised by a user or business within an approved framework, instead of processing every purchase as a separate payment event.
Early access follows pilots with Coinbase, Base and Cloudflare
Mastercard said the new tools cover both sides of an agent-led transaction: those building purchasing agents and those receiving payments for services or goods. The company did not detail a wider commercial rollout timetable in its October announcement, but the sandbox and APIs give developers an environment in which to integrate the system.
The pilots brought together payment, wallet, blockchain and service providers. Alongside Coinbase and Base, the list included Cloudflare, Ant International, BVNK and AIsa. The mix matters because an agent payment requires more than an instruction to pay: it needs a wallet and payment path, a way for a merchant to assess a payment request, and a means of settling the resulting obligation.
Mastercard first announced Agent Pay for Machines on June 10. At that point, it described a system intended to support credentialing and permission controls, alongside settlement across cards, accounts and stablecoins. The initial announcement named more than 30 participants and supporters, according to Mastercard Investor Relations.
The Cloudflare demo tested one budget across nine purchases
The Cloudflare Connect demonstration offered a more specific example of how the workflow could operate. An AI agent made nine payments to two merchants under a single approved budget: one payment to AIsa for social-media research and eight to Cloudflare for campaign images.
That sequence is the practical issue Mastercard’s design seeks to address. A user or business can approve a budget for a task, while the agent makes the separate purchases needed to complete it. In the demonstration, research and image-generation services were supplied by different merchants, and the image work itself involved eight individual purchases.
The pilot does not establish how broadly the arrangement will be adopted by merchants or developers. It does, however, show why Mastercard is putting buyer- and seller-side tools into the early-access package: the model depends on both the agent’s payment authority and a merchant’s ability to recognise and process the payment request.
Coinbase, Base and BVNK split the wallet, settlement and payment roles
Mastercard said Coinbase Developer Platform supplied wallet infrastructure, Base provided on-chain settlement, and BVNK handled agent-wallet payment and settlement through Mastercard Global Money Platform. Mastercard also said settlement could occur in either fiat currency or stablecoins, rather than presenting the pilot as a stablecoin-only system.
x402 vouchers allow service delivery before final settlement
Coinbase-incubated x402 and digitally signed payment vouchers are used for repeat agent purchases, The Block reported. The report said merchants can verify vouchers before delivering services and batch them for later redemption rather than settle each payment individually.
In Mastercard’s Cloudflare demonstration, one approved task resulted in nine payments to two merchants.
Mastercard said its October early-access release gives developers APIs, a toolkit, sandbox and documentation after pilots involving Mastercard, Coinbase, Base, Cloudflare and other participants.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
