Table of Contents
Mastercard Agent Pay for Machines is now open to developers: on Tuesday, 20 October 2026, Mastercard opened Early Access to the service, which lets AI agents pay for digital services on a business's behalf inside a pre-approved budget, and showed it running live at Cloudflare Connect, according to Mastercard's announcement.
The service builds on x402, the open protocol that lets a website or API answer a request with "402 Payment Required". In the demo, Coinbase Developer Platform funded the agent's wallet, Base provided onchain settlement, and BVNK settled both sides in fiat or stablecoins through Mastercard's Global Money Platform, per Mastercard. Decrypt, The Block and PYMNTS reported the launch on Tuesday evening, Central European time.
Below: what Mastercard actually opened, how a voucher payment moves from an HTTP 402 response to a stablecoin settlement, how the model differs from plain x402, and what is still missing before a business can run it in production.
Key Takeaways
- Mastercard opened Agent Pay for Machines Early Access on 20 October 2026, with buyer and seller APIs, a toolkit, a sandbox and documentation (Mastercard).
- Agents pay with digitally signed vouchers inside a business-set budget; vouchers are checked offchain and can be combined and redeemed later (Decrypt).
- The demo used Coinbase Developer Platform wallets, Base for onchain settlement and BVNK to settle in fiat or stablecoins (CoinMarketCap).
- Cloudflare's Monetization Gateway, the seller side in the demo, settles x402 payments on Base in USDC (Cloudflare).
- Pricing, supported stablecoins, dispute rules and a general availability date are not in the announcement (Mastercard).
What Mastercard opened on 20 October
Mastercard first launched Agent Pay for Machines on 10 June 2026 with more than 30 named supporters, including Adyen, BVNK, Checkout.com, Cloudflare, Coinbase, Stripe and Tempo, per its June release. Tuesday's step moves it from a partner programme to something outside developers can build against. The confirmed facts:
- Access: Agent Pay for Machines Early Access, with the first version of the buyer-side and seller-side APIs, a toolkit, a sandbox and developer documentation (Mastercard).
- Pilots completed first: end-to-end pilots with Cloudflare, Ant International, AIsa, Base, BVNK, Coinbase and Hype (Mastercard).
- Protocol: builds on x402, with Mastercard positioned as a common trust layer across agent platforms, wallets, payment providers and merchants (Mastercard).
- Venue: demonstrated at Cloudflare Connect by Mastercard chief product officer Jorn Lambert (Decrypt).
- Status: still early access. Mastercard says the roadmap will be shaped by customer and partner feedback (Mastercard).
One reporting difference is worth flagging. Decrypt lists the pilot partners as Cloudflare, Ant International, AWS, BVNK and Coinbase. Mastercard's own announcement names AIsa, Base and Hype instead of AWS and mentions Amazon Bedrock AgentCore only as an example agent platform. This article follows Mastercard's list.
How a Mastercard Agent Pay for Machines payment works
Mastercard sums up the model as "Authorize once. Transact many times. Guarantee payment now. Settle later." The flow from the announcement, step by step:
| Step | What happens | Onchain? |
|---|---|---|
| 1. Mandate | A business gives an agent a task and a spending limit (Mastercard) | No |
| 2. Discovery | The agent finds registered Agent Pay for Machines providers and proposes a plan; the business approves the funding | No |
| 3. 402 response | A paid service answers with "402 Payment Required", the x402 signal that payment is needed (x402) | No |
| 4. Voucher | The agent signs a payment voucher, a promise to pay within its approved limit; the seller verifies it and delivers | No, offchain at machine speed |
| 5. Redemption | Sellers combine vouchers and redeem them later | Settlement leg |
| 6. Settlement | In the demo, Base carried onchain settlement and BVNK settled both sides in fiat or stablecoins (CoinMarketCap) | Yes, on Base in the demo |
The demo made the model concrete. Marketing agency Hype gave an agent a budget to plan a protein bar campaign; the agent bought social media research from AIsa and eight campaign images through Cloudflare AI Gateway. That came to nine payments to two independent merchants under one approved budget, with no separate accounts, API keys or invoices, per Mastercard. AIsa is the pay-per-call API marketplace that Tether Capital backed this month, covered in Stablecoin Insider's Tether AIsa analysis.
Where the stablecoins sit
Mastercard's announcement uses the word stablecoin once, but the plumbing behind the demo is stablecoin plumbing. Coinbase Developer Platform supplied the wallet that funded the agent, Base provided the settlement network, and BVNK acted as the agent wallet, using the Global Money Platform to handle payment and settlement "in fiat or stablecoins" so sellers get paid in their preferred currency, token or rail (Mastercard).
The seller side is more specific. Cloudflare's Monetization Gateway, which returned the 402 responses in the demo, handles verification and settlement through Coinbase's x402 facilitator, and its payments settle on Base in USDC, per Cloudflare's beta announcement from 30 September. The gateway uses x402 version 2 with PAYMENT-REQUIRED and PAYMENT-SIGNATURE headers, per Cloudflare's developer docs, and is a closed beta for eligible US-based sellers and buyers. Stablecoin Insider covered the gateway when Cloudflare opened its waitlist in July.
Mastercard has not said which stablecoin settled the demo payments, so the USDC detail is Cloudflare's general product rule, not a Mastercard disclosure. What the structure shows is the division of labour: x402 and a USDC wallet on the buyer side, Mastercard's voucher and guarantee in the middle, and BVNK converting to whatever the seller wants to receive. Stablecoin Insider's guide to the Mastercard Global Money Platform explains that conversion layer.
Agent Pay for Machines vs plain x402
Plain x402 was designed for direct, per-request payment: an agent pays a service from its own wallet, and a facilitator verifies and settles each payment onchain, per Coinbase's x402 documentation. Mastercard keeps the 402 handshake but changes what happens after it. Ledger Insights describes the result as batch settlement with Mastercard inserted into the flow, adding a credential registry and a guarantee, per its analysis.
| Plain x402 | Mastercard Agent Pay for Machines | |
|---|---|---|
| Payment signal | HTTP 402 with payment requirements (x402) | Same 402 signal (Mastercard) |
| What the agent sends | A signed payment authorization, settled per request | A signed voucher, a promise to pay within an approved limit |
| Settlement timing | Per request, onchain | Vouchers combined and redeemed later, in batches |
| Payment guarantee | Finality comes from the onchain settlement itself | Mastercard says payment is guaranteed now and settled later |
| Funding source | The agent's own stablecoin wallet | Wallet funding via Coinbase in the demo; fiat or stablecoins through BVNK |
| What the seller receives | The asset named in the 402 response, often USDC | Preferred currency, token or rail |
| Who sits in the middle | A facilitator such as Coinbase's | Mastercard as trust layer, plus BVNK and the facilitator |
The trade-off is clear. Plain x402 is open and settles each payment as it happens, but every seller must accept a specific token on a specific chain. Mastercard's version adds an intermediary and a delay, in return for spending limits, a promise of payment and a way for a business that funds agents from a bank account to pay sellers who want stablecoins, or the reverse. Stablecoin Insider's x402 vs AP2 vs ACK-Pay comparison covers the other agent payment protocols Mastercard is competing with.
Why machine payments lean on stablecoins
The economics explain why Mastercard built on a crypto protocol at all. More than 138 million x402 transactions had taken place on Base by mid-2026, and over 87% of x402 payments fell between a hundredth of a cent and ten cents, per Chainalysis. Payments that small rarely make sense on card rails, where fixed per-transaction costs can exceed the payment.
Circle described the split to Chainalysis as card rails for consumer-prompted agent payments and stablecoin rails for machine-to-machine settlements too small for card economics, per the same Chainalysis report. Agent Pay for Machines is Mastercard's attempt to sit across that line: it already supports settlement across cards, accounts and stablecoins, per the June release, and batching vouchers is one way to make tiny payments cheap enough to settle.
Named downsides
- No pricing. Neither buyer nor seller fees have been published, so cost against plain x402 cannot be compared.
- Settlement opacity. Redemption frequency, chains and stablecoins beyond the Base demo are unstated.
- Counterparty in the middle. Batching means sellers deliver on a promise and wait for settlement, which plain x402 avoids.
- Early access only. A sandbox and first-version APIs are not a production service level.
- Geography unclear. Cloudflare's gateway is limited to eligible US-based sellers and buyers during its beta.
- Vendor concentration. Mastercard, its BVNK unit and the Global Money Platform would sit on both sides of the payment.
Who should test it now, and who should wait
Test now: API and data sellers already behind Cloudflare's Monetization Gateway, agent platforms whose business customers want a hard spending cap per task, and payment providers in the BVNK or Coinbase orbit that want to accept agent payments without asking every buyer to hold USDC.
Wait: crypto-native agents that already pay per request in USDC and gain little from a guarantee, and any business outside the United States until Mastercard says where Early Access applies. For the risk side, Mastercard's separate Stablecoin Security screening service, launched a day earlier, shows how the company plans to wrap stablecoin payments in its fraud and sanctions tooling.
Agent Pay for Machines settles through BVNK and the Global Money Platform. Stablecoin Insider's guide explains what that account and payout layer offers and which businesses it fits.
FAQ
What is Mastercard Agent Pay for Machines?
A Mastercard service that lets AI agents pay for digital services such as AI models, data, computing power and APIs on behalf of businesses, within approved budgets and permissions. It builds on the x402 protocol (Mastercard).
Is Agent Pay for Machines live?
It is in Early Access as of 20 October 2026. Developers can use first-version buyer and seller APIs, a toolkit, a sandbox and documentation; Mastercard has not given a general availability date (Mastercard).
Does Agent Pay for Machines use stablecoins?
It can. In the demo, Base provided onchain settlement and BVNK settled in fiat or stablecoins (Mastercard). Cloudflare's Monetization Gateway, the seller side in the demo, settles x402 payments in USDC on Base (Cloudflare).
How is it different from plain x402?
Plain x402 settles each payment per request through a facilitator (Coinbase). Mastercard's version uses signed vouchers that sellers combine and redeem later, with Mastercard acting as a trust layer that guarantees payment (Ledger Insights).
How much does Agent Pay for Machines cost?
Mastercard has not published pricing for buyers or sellers; the Early Access announcement lists APIs, a toolkit, a sandbox and documentation but no fees (Mastercard).
What to watch next: published fees, a list of settlement chains and stablecoins beyond Base, dispute and chargeback rules for vouchers, and the first sellers outside the pilot group. Background on the protocol layer is in Stablecoin Insider's agent payment protocol comparison.
This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; it is not financial advice, and no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy or sell any asset or token. Product scope, partners and availability are as described by Mastercard on 20 October 2026 and can change; check Mastercard's developer documentation and take legal advice before letting software spend on a business's behalf. Nothing here is a solicitation to buy or sell.
