Mastercard Opens Agent Pay for Machines Early Access

Mastercard has opened early access to Agent Pay for Machines, a system meant to let AI agents pay for digital services on a business’s behalf within a budget a person approves. Announcing it on 20 October at Cloudflare Connect, the card network said developers can now get “the first version of our buyer- and seller-side APIs”, along with a toolkit, sandbox and documentation.

This is a test phase, not a launch. Mastercard has given no pricing and no date for general availability, and The Block, which reported the news, says the project “remains in a pilot stage and has not yet been made commercially available.” For developers building agents, it is a first chance to test how a card network wants machine payments to work.

In brief

Mastercard has opened early access to Agent Pay for Machines, giving developers APIs, a toolkit and a sandbox to test AI agent payments.
The system builds on the x402 protocol and lets agents pay within a set budget, with settlement in fiat or stablecoins through Coinbase, Base and BVNK in its pilot.
It is not generally available: Mastercard has given no pricing, launch date or fees.

The problem Mastercard says it is solving

Mastercard’s pitch starts from how agents now work. In its own release, it says an agent might buy data from one provider, a model from another and computing power from a third. “In other words, AI agents are becoming economic actors,” it says. “But how does an agent actually pay?”

Today, each paid service usually needs its own account, API key, prepaid credits or billing relationship, the company says, which breaks down when an agent picks services as a task unfolds. Then comes the question of control. “Who gave the agent permission to spend? How much can it spend? What can it spend that money on? And who is it paying?” Mastercard asks. Its answer: “Payments aren’t the hard part. Authority is.”

That is where x402 comes in. Agent Pay for Machines builds on the open protocol, which uses the web’s “402 Payment Required” response, “and connects it with the trust, security and reach of the Mastercard network,” the company says. A business gives an agent a job and a spending limit; when a paid service asks for money, the agent signs a digital voucher, which Mastercard describes as “a secure promise to pay within its approved limit.” The provider checks it and delivers. “These interactions happen off-chain at machine speed. Providers can combine vouchers and redeem them later,” the release says.

What the demo showed

The Cloudflare Connect demo used Hype, a marketing agency, which gave an agent a defined budget to plan a sample campaign for a protein bar launch. Running on “an agent platform such as Amazon Bedrock AgentCore”, the agent found registered providers and proposed a plan: social media research from AIsa, then campaign images through Cloudflare AI Gateway. Hype approved the funding, and the agent bought the research and eight images.

Mastercard sums it up in its release: “Nine payments. Two independent merchants. One approved budget. No separate accounts, API keys or invoices. The agent pays only for what it uses while Hype stays in control.” It has not said what the payments were worth.

The crypto plumbing sits behind the scenes. Mastercard says Coinbase Developer Platform supplied the wallet used to fund the agent, Base provided on-chain settlement, and BVNK, which The Block notes Mastercard acquired in August, acted as the agent wallet. BVNK used Mastercard’s Global Money Platform to settle both sides “in fiat or stablecoins”, so sellers can be paid in their preferred currency, token or rail.

Pilot role	Firm
Agent wallet funding	Coinbase Developer Platform
On-chain settlement	Base
Agent wallet and settlement	BVNK
Services bought	AIsa, Cloudflare

Source: Mastercard release, 20 October 2026.

From pilot to early access

Mastercard says the step follows end-to-end pilots with Cloudflare, Ant International, AIsa, Base, BVNK, Coinbase and Hype. It first announced Agent Pay for Machines in June, The Block notes, with support for spending controls and card, bank account and stablecoin payments. PYMNTS reported that it received the new release on 20 October.

The company is asking for feedback rather than promising features. “This is just the start. Our roadmap will be shaped by what customers and partners need,” it says, adding that it wants developers to test different uses. It frames the goal in three lines: “The web gave software a way to communicate. APIs gave software a way to use services. Now AI agents need a way to pay for them.”

Rivals are moving too. As TSN has reported, Visa is running a live pilot in which AI agents pay approved invoices, and AWS and Anchor Browser have let agents pay for x402-protected pages.

Our read

This is TSN’s analysis. Mastercard is betting that the hard part of agent payments is permission, not settlement, and that a card network is best placed to vouch for it. The open questions are cost and liability: who carries the loss when an agent overspends or a voucher is disputed. Until Mastercard publishes pricing and a launch date, this remains a developer sandbox rather than a product businesses can switch on.