Mastercard Opens Agent Pay for Machines Sandbox, Demonstrates Nine Purchases Under One Authorized Budget
Oct. 21, 2026 • Deep Dive • AI in Fintech
Mastercard opened early access to its Agent Pay for Machines developer toolkit and sandbox at Cloudflare Connect on October 20, 2026. In a live demonstration, an AI agent operated by marketing agency Hype made nine payments across Cloudflare AI Gateway and AIsa within one human-authorized budget, without separate accounts or invoices for each purchase.
The toolkit uses x402, an open protocol that lets servers request payment through an HTTP 402 response and agents fulfill the request with cryptographically signed vouchers. The trial used Coinbase Developer Platform wallet infrastructure, Base for onchain execution, and BVNK for fiat and stablecoin processing. The demonstration illustrates one approach to separating an agent’s purchasing decisions from the human authorization and payment records that govern them. Separately, Google’s Agent Payments Protocol uses signed mandates to verify human intent, while Mastercard, Visa and Ant International are working on a framework for agent identity and verification.
Mastercard opened early access to its Agent Pay for Machines developer toolkit and sandbox on October 20, 2026, offering a way for AI agents to buy digital services programmatically within spending boundaries set by a human. The launch at Cloudflare Connect included a live demonstration in which an agent made nine payments under one authorized budget.
The demonstration addresses a central question in agent-driven commerce: how can software make individual purchasing decisions without making the agent itself the final authority over spending? Mastercard’s approach lets a human define the limits while the agent carries out transactions within them. It also shows how a payment request can become part of an automated exchange between an agent and a digital service, rather than a separate manual checkout.
Nine payments under one authorization
At Cloudflare Connect, an autonomous AI agent operated by marketing agency Hype completed nine individual payments across Cloudflare AI Gateway and AIsa. The purchases stayed within a single authorized budget and did not require individual accounts or invoices for each payment. The reported demonstration shows a sequence of transactions, not merely an agent preparing a payment request for a person to approve one purchase at a time.
The early-access release is a developer toolkit and sandbox. The demonstration establishes that the participating services could be paid through that setup; it does not, on its own, establish how widely the system is in use. The distinction matters because the challenge is not simply whether an agent can initiate a payment. It is whether repeated, machine-initiated purchases can be tied to a clear authorization and recorded through payment infrastructure.
From a service request to settlement
Agent Pay for Machines uses x402, an open protocol originally incubated with Coinbase. Under x402, a server can respond to a request with the HTTP 402 “Payment Required” status code. The agent can then fulfill the payment request using a cryptographically signed voucher. In practical terms, the service can ask for payment as part of the same programmatic interaction in which the agent seeks access to it.
The trial used Coinbase Developer Platform wallet infrastructure, the Base blockchain for onchain execution, and BVNK for fiat and stablecoin payment processing. Those components served different parts of the transaction flow: wallet infrastructure supported the agent’s payment capability, Base provided an onchain execution layer, and BVNK handled payment processing. The verified account of the trial does not provide a transaction-by-transaction breakdown of which payment form was used for each of the nine purchases.
The architecture also reflects a distinction described in the International Monetary Fund’s 2026 note, How Agentic AI Will Reshape Payments. The note separates probabilistic AI intent from deterministic authorization mandates and settlement ledgers. An agent may decide which service to request, but its capacity to spend needs a verifiable mandate, and the resulting transaction needs a definite payment record. Mastercard’s demonstration illustrates that division through purchases made inside a pre-authorized budget.
Identity and authority across networks
Other payment initiatives are addressing related parts of the problem. Google has deployed its Agent Payments Protocol, or AP2, which uses cryptographically signed mandates to confirm verifiable human intent before a machine executes a payment. AP2 and x402 are distinct approaches: the verified information describes AP2’s role in proving authorization, while x402 provides a way for a server to request and an agent to fulfill payment during a service interaction.
Mastercard, Visa and Ant International have also partnered on the Know-Your-Agent interoperability framework through the Monetary Authority of Singapore’s BuildFin.ai initiative. That effort aims to harmonize agent identity and verification across networks. Knowing which agent is acting, and under what authority, is separate from delivering a payment request or settling it; each is part of making an automated transaction accountable.
For now, the Mastercard showcase demonstrates bounded purchasing across named digital services in an early-access environment. The broader work on signed mandates and interoperable agent verification indicates that payment execution alone is not the whole task. Agent-driven commerce depends on connecting an agent’s choices to identifiable authority and to payment records that can be checked after the transaction.
The Linux Foundation appointed payments veteran Michael Hursta executive director of the x402 Foundation on October 1, 2026, as payment systems designed for autonomous AI agents gained attention. Foundation members reported more than 75 million agentic payment transactions in a 30-day period in September, and Coinbase and Amazon Web Services showcased production payment rails at Sibos 2026. Reported transaction counts, however, do not establish the value or commercial character of that activity. The emerging protocols address different obstacles. Coinbase’s x402 enables per-request USDC payments through HTTP, while Google’s Agent Payments Protocol uses signed mandates to connect an agent’s purchases to a user’s authorization. Stripe and Tempo have also proposed session-based billing through the Machine Payments Protocol. These approaches respond to card fees and interactive checkout checks that can impede small, automated transactions. Card networks are developing delegated-identity tools, leaving multiple potential paths for agent payments rather than a single replacement for existing rails.
Mastercard opened developer early access for Agent Pay for Machines (AP4M) on October 20, 2026, releasing buyer- and seller-side APIs, a sandbox and developer toolkits. In a Cloudflare Connect demonstration, marketing agency Hype tested an autonomous agent making nine payments to two merchants within a single budget, without manual billing or account setup. AP4M uses HTTP 402 payment challenges, but differs from crypto-native implementations of the x402 protocol. Its agents issue digitally signed vouchers off-chain; merchants can batch and redeem them later instead of settling every request on-chain. The pilot combined agent wallet infrastructure from Coinbase Developer Platform and BVNK, settlement on Base, and Mastercard’s multi-currency fiat and stablecoin settlement platform. Circle separately expanded its managed payments service to target AI-agent traffic using USDC. Together, the developments show competing approaches to machine-to-machine payments, with different choices about settlement, funding and who manages digital assets.
Visa launched a live pilot with BILL and Billtrust at Money20/20 USA in late October 2026 to test end-to-end B2B invoice payments executed by software agents. The agents act on invoices enterprise buyers have already approved; they do not decide which supplier payments to authorize. Visa’s Trusted Agent Protocol and Agentic Directory are designed to authenticate those agents when they access supplier and merchant portals without shared credentials or manual human login. Separately, Visa has put Commercial Payment Controls into production for eligible issuers in supported regions, allowing businesses to set limits and restrictions on corporate spending. The company plans general availability of Commercial Virtual Authentication and Commercial Supplier Validation in 2027 after pilot completion. Its SESA 2.0 analytics platform has identified more than $600 billion in potentially cardable supplier spend. The pilot tests whether approved invoice payments can be executed through automated workflows while preserving buyer-defined controls.
Mastercard and Visa are advancing different approaches to AI-initiated business payments. At Cloudflare Connect, Mastercard demonstrated an agent making nine payments across multiple service providers under one authorized budget. It also opened early developer access to Agent Pay APIs, a sandbox and toolkits. Visa expanded its commercial agentic suite around a BILL and Billtrust pilot, alongside spend analytics and fraud tools. The distinction is how each approach constrains the agent. Visa’s pilot lets an agent pay invoices that buyers have already approved, using its Trusted Agent Protocol to navigate supplier-portal security without sharing underlying login credentials. Mastercard is testing controls for machine-to-machine transactions, including signed vouchers, agent verification and a score intended to estimate whether an incoming transaction was AI-initiated. Both efforts leave a consequential question for business payments: how responsibility should be assigned when an authorized agent follows its technical instructions but breaches a procurement condition.
Mastercard opened developer APIs, SDKs and a sandbox for Agent Pay for Machines (AP4M) on October 21, 2026. The tools enable autonomous AI agents on Amazon Bedrock to make multi-merchant micropayments over x402 using off-chain signed vouchers. The launch follows Coinbase Developer Platform’s report that cumulative x402 payments across Base and Solana had exceeded 100 million by October. The x402 protocol uses an HTTP 402 response to tell an agent what a service costs and how to pay. Its growing infrastructure includes a Linux Foundation-governed foundation, while alternative approaches use Lightning payments or existing processor rails. Transaction counts, however, do not establish how much genuine agent-led commerce is taking place. TRM Labs found a much smaller pool of plausible commercial trade after screening out other activity. Security questions also remain, including whether a service can receive payment without delivering its output. Developers therefore face choices about settlement, spending controls and proof of service.
CapitalOS completed a $21.9 million Series A financing round on October 21, 2026, led by LGVP. The company plans to expand its engineering team and scale the infrastructure behind its AI-driven money orchestration platform. WEX Venture Capital, Group 11, Great North Ventures, Night Capital and existing early investors also participated. Founded in 2022, CapitalOS helps vertical SaaS and AI platforms offer embedded charge cards, digital wallets and automated bill payments without maintaining in-house licensing or risk operations. Its architecture uses five specialized AI agents across underwriting, capital, compliance, risk and fraud, and support. Property management platform Guesty is an active customer, and CapitalOS reports managing transactions for more than 25,000 active cardholders across dozens of integrated platforms. CapitalOS relies on infrastructure provider Increase and its chartered partner banks rather than replacing depository institutions. The announcement did not disclose a valuation, credit warehouse partner or the identities of its current primary sponsor banks.