Mastercard's Nine Payments on One Budget: How Agent Pay for Machines Works
In Mastercard's October 2026 Agent Pay for Machines demo, an agent made nine payments to two providers on one pre-approved budget. Each HTTP 402 request was answered with a signed x402 payment voucher that the provider verified before delivering and can redeem later. Vouchers can be redeemed later in batches rather than settled per request.
What Mastercard showed
On October 20, 2026, at Cloudflare Connect, Mastercard demonstrated Agent Pay for Machines and opened early access to it. The Block, Decrypt and Fintech News Singapore all reported the same demo. A marketing agency, Hype, gave an agent a protein bar campaign and a budget approved once in advance. The agent bought social media research from AIsa and generated eight campaign images through Cloudflare AI Gateway: nine payments to two independent providers, with no separate accounts, API keys or invoices.
The reported plumbing: the agent paid using x402. When a provider answered with HTTP 402 Payment Required, the agent generated a digitally signed payment voucher, which Decrypt describes as a promise to pay within its approved limit. The provider verified the voucher before delivering. Vouchers can be collected and redeemed later rather than settled one by one. Coinbase Developer Platform supplied wallet infrastructure, Base provided onchain settlement, and BVNK, which Mastercard acquired in August, handled payment and settlement in fiat or stablecoins through Mastercard's Global Money Platform.
Early access includes buyer side and seller side APIs, a toolkit and a sandbox. The Block reports Mastercard describing it as still a pilot, not commercially available. Coverage traces the product to a June 2026 announcement that covered spending controls and card, bank account and stablecoin payments.
Not the same product as Mastercard Agent Pay
Mastercard Agent Pay, announced April 29, 2025, is the consumer checkout program built on Mastercard Agentic Tokens, an extension of the tokenisation already used for contactless and card on file. Agent Pay for Machines is the machine-to-machine piece: agents paying APIs and digital services per request. The nine-payment demo is the second one.
How one budget covers nine payments
The interesting part is not the count. It is that one approval produced many payments without the budget being spent nine separate times by a human.
The voucher model explains how. Each 402 response is answered with a signed commitment, not a settled transfer. The provider checks the signature and the commitment against what it knows about the buyer's authority, delivers, and holds the voucher. Settlement happens later, potentially as one redemption covering many vouchers. That removes the per-request settlement cost and latency, which is what makes nine small purchases in a short task practical.
The pattern is not new to x402. Cloudflare proposed a deferred payment scheme for x402 in September 2025, where cryptographic trust is established at request time and financial settlement follows on card rails or stablecoins. Mastercard's version adds a network operator, its settlement platform, and a budget approved up front.
What the public reporting does not say: where the budget is enforced, how a provider learns that remaining budget is sufficient, how double redemption of a voucher is prevented, and how disputes work. None of the coverage found addresses them. Treat every answer below as analysis of the model, not a description of Mastercard's implementation.
Network budget versus session-key float
There are two ways to bound an agent that pays many times. They put the limit in different places.
A network-held budget. The buyer approves a budget with an intermediary. The agent signs vouchers; somewhere between the agent and settlement, a system checks them against the budget. The provider extends short credit between delivery and redemption, and relies on the intermediary to make good on valid vouchers.
A session-key float. The agent holds a key registered to a smart account with a cap, allowed assets and recipients, and an expiry. Each payment is a transfer the contract checks before it executes. Funds exist before the agent spends them, and an out-of-scope payment fails at signing.
The trade-offs
Who carries risk. With vouchers, the provider is exposed until redemption, and the guarantor is whoever backs the voucher. With a float, the provider is paid when the transfer lands and carries no credit risk.
Where enforcement lives. A network budget is enforced by a service. A session key cap is enforced by the account contract. Both work; the first depends on that service being correct and available, the second on the contract.
Cost per payment. Vouchers amortise settlement across many requests. A float pays each transfer individually, which on Base is cheap but not zero, and batching or channels close the gap for very high frequency.
Recourse. A network can build dispute handling into redemption. A settled stablecoin transfer is final; recourse is by agreement with the seller.
Fiat reach. Mastercard's model lets sellers receive their preferred currency or rail. A USDC float settles in USDC.
What to take from it as a builder
The agent still needs a hard local limit. A budget held by a network bounds what the network will honour. It does not stop a compromised agent from signing vouchers it should not, and every rejected voucher is a failed task. Put the cap in the key as well, so the agent cannot sign past it.
Validate the 402 response. Deferred or immediate, the agent is still reading payment terms written by the party being paid. Check asset, amount, recipient and expiry before signing anything.
Record vouchers like payments. A signed voucher is a liability the moment it leaves the agent. Log it with the request it paid for, so redemption can be reconciled against delivery.
Expect convergence. Card networks are adopting x402 and Base settlement; onchain rails are adopting deferred schemes. The open question is who enforces the budget, and that choice decides who you are trusting.
Frequently asked questions
- What is Mastercard Agent Pay for Machines?
- It is Mastercard's machine-to-machine payment product for agents buying APIs and digital services. It builds on x402: when a service returns HTTP 402, the agent signs a payment voucher within an approved limit, the provider verifies it, and vouchers are redeemed later. Mastercard opened early access on October 20, 2026, and describes it as a pilot.
- How did one budget cover nine payments in the demo?
- Hype approved a single budget, and its agent made nine payments to AIsa and Cloudflare AI Gateway by signing a voucher each time a provider asked for payment. Providers verified vouchers before delivering and can redeem them later in bulk, so the nine purchases did not need nine separate settlements or nine human approvals.
- Did the demo settle onchain?
- According to The Block and Decrypt, Coinbase Developer Platform supplied wallet infrastructure and Base provided onchain settlement, while BVNK handled payment and settlement in fiat or stablecoins through Mastercard's Global Money Platform. The interactions themselves happened off-chain as signed vouchers, with settlement deferred rather than per request.
- Is a network budget safer than a session-key float?
- Neither is strictly safer. A network budget can add dispute handling and fiat settlement but depends on an intermediary enforcing it correctly. A session-key float is enforced by the account contract before any transfer executes and leaves providers with no credit exposure, but settled payments are final. Many agents will want a local key cap either way.