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.
