Agent Will Pay

Mastercard opens Agent Pay for Machines to developers: 9 payments, 2 merchants, 1 budget

20 October 2026

What happened

At Cloudflare Connect on 20 October 2026, Mastercard opened early developer access to Agent Pay for Machines, its service for permissioned machine-to-machine payments across cards, bank accounts and stablecoins. The live demonstration was deliberately mundane: an agent working for marketing agency Hype ran a protein-bar campaign task. It used the Agent Pay for Machines Discovery Service to find providers, proposed a plan, and — once Hype approved the funding — made nine payments to two merchants (research from AIsa, eight campaign images from Cloudflare AI Gateway) out of a single approved budget. No separate accounts, API keys or invoices per provider. The agent paid over the x402 protocol with signed payment vouchers; Coinbase Developer Platform supplied the wallet infrastructure and the Base network handled on-chain settlement. Early access gives developers buyer-side and seller-side APIs, a toolkit and a sandbox.

What it means for each party in the payments chain

Issuer. The issuer’s question is the same one Mastercard framed: “Who gave the agent permission to spend? How much can it spend? What can it spend that money on? And who is it paying?” The demo answers all four with a signed voucher trail — which is why the issuer’s dispute queue will treat these payments as attributable, not anonymous.

Acquirer. The acquirer’s interest is volume: machine-to-machine payments are high-frequency and low-value, so the acquirer needs a model where the cost of processing each payment does not exceed its value. AP4M’s guaranteed settlement and pre-authorized spending limits are the answer Mastercard is offering.

Merchant. The merchant is the seller in the demo (AIsa, Cloudflare AI Gateway). The merchant’s benefit is that it gets paid without setting up a separate account for each agent buyer — the Discovery Service and the signed voucher make the agent a normal counterparty.

PSP. The PSP’s role is infrastructure: Coinbase Developer Platform supplied the wallet, Base handled on-chain settlement. The PSP is the party that converts a signed voucher into settled value — and the party that must handle the case where the voucher is valid but the settlement fails.

Card scheme. Mastercard’s role is the network and the trust framework. AP4M is the scheme’s answer to the question of how machine payments scale: permissioned access, guaranteed settlement, and a trust framework that names the five pillars (identity, intent, controls, trusted execution, intelligence) without yet pricing the loss split.

What it does not mean

Mastercard describes this as a pilot phase, not a commercial rollout: developers are being asked to test the APIs and give feedback before wider release. Agent Pay for Machines was first launched in June 2026 with 30+ participants; the October step is early access, not general availability. A September 2026 Trust Framework (five pillars: identity, intent, controls, trusted execution, intelligence) accompanies it, but the product is still being refined.

Sources