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.

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.

Mastercard has opened developer early access to Agent Pay for Machines, offering buyer- and seller-side APIs, software development kits and sandbox environments. The service remains in pilot, is not commercially available and has no announced date for a general production release. At Cloudflare Connect 2026, Mastercard Chief Product Officer Jorn Lambert demonstrated an AI agent running on Amazon Bedrock AgentCore making nine payments across two merchants under a single budget approved by marketing firm Hype. The agent paid for social media research from AIsa and eight image generations through Cloudflare AI Gateway without separate accounts or API keys. Built on the open x402 standard, Mastercard’s system uses off-chain, cryptographically signed vouchers that providers can redeem in batches. Coinbase Developer Platform provides wallet infrastructure, Base handles on-chain settlement, and BVNK processes fiat and stablecoin settlements through the Mastercard Global Money Platform. The early-access rollout gives developers a way to test the model, not a commercially available payment service.

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.

AI agents can select products and initiate payments without a buyer present at checkout, forcing merchants and payment providers to verify delegated authority rather than a single approval. Google’s Agent Payments Protocol (AP2) uses signed mandates to record spending limits and connect instructions to a specific cart. Stripe and OpenAI’s Agentic Commerce Protocol and Shared Payment Tokens, alongside Mastercard’s Agentic Token framework, support checkout with restricted credentials. Visa’s Trusted Agent Protocol helps merchants identify agents, while Coinbase’s x402 enables stablecoin payments through web requests, including small API charges. These tools address different risks: signatures document permission, tokens limit payment use, and records can support disputes. But compliance with a spending cap cannot prove an agent chose what its user intended. Google transferred AP2 stewardship to the FIDO Alliance in April 2026, yet consumer deployment remains early. Merchants still face integration challenges, while liability and chargeback treatment for agent errors remain unsettled.