AI agents are starting to spend money. They book travel, buy products, pay for API calls and data, and in some cases pay other agents for work. Doing that safely needs new payment plumbing: ways to prove an agent is authorized, to give it a credential that cannot be abused, to check out with merchants and to settle tiny machine-to-machine payments that cards were never built for. In 2026 the card networks, the big payment companies and crypto infrastructure providers all shipped answers.
This list ranks the ten agent payment platforms and protocols that matter most going into 2027, for merchants, fintech teams and developers building agents that transact. Details come from company announcements and documentation through early November 2026. For the wider picture, start with our guide on what agentic commerce is.
| Platform | Layer | Best For | Known For |
| Stripe | Checkout and settlement | Merchants and developers | Agentic Commerce Protocol, agent tokens and x402 support |
| Coinbase | Machine payments | Paying for APIs and data | Created x402 and runs Agent.market |
| Visa Intelligent Commerce | Card credentials and identity | Card-based agent purchases | Agent tokens and the Trusted Agent Protocol |
| Mastercard Agent Pay | Card credentials and identity | Bank-issued agent payments | Agentic Tokens and Verifiable Intent |
| Google AP2 | Authorization | Proving what a user approved | Signed mandates across payment methods |
| PayPal | Wallet and checkout | Consumer agent shopping | Agentic commerce with AP2 support |
| Cloudflare | Edge payments | Charging agents for content and APIs | x402 at the network edge and Pay per Crawl |
| Skyfire | Agent identity and payments | Know Your Agent checks | Verified agent identity with a USDC ledger |
| Crossmint | Wallets and cards for agents | Developers building buying agents | Agent wallets and payment rails in one API |
| Circle | Stablecoin settlement | USDC-based agent payments | The settlement asset behind most x402 traffic |
Stripe sits at more layers of agent payments than anyone else. With OpenAI it created the Agentic Commerce Protocol, an open standard for agent-initiated checkout that issues single-purpose tokens so an agent can pay a merchant without seeing the buyer’s card. It integrated x402 for USDC payments on Base in February 2026, and with Tempo it launched the Machine Payments Protocol for session-based machine payments.
For merchants already on Stripe, accepting agent purchases is largely a configuration change, which makes it the default starting point for most businesses.
Coinbase introduced x402 in May 2025, reviving the HTTP 402 Payment Required status code so agents can pay for resources in stablecoins inside a normal web request. It contributed the protocol to the x402 Foundation at the Linux Foundation in 2026, launched Agent.market as a directory of services agents can buy, and since July 2026 lets all Coinbase Business customers accept USDC directly from agents.
It is the strongest choice for API providers, data sellers and developers whose agents need to pay small amounts, often, with no accounts or contracts.
Visa Intelligent Commerce turns a customer’s card into an agent-specific token with spending controls, so an agent can pay without exposing the real card number. Its Trusted Agent Protocol, developed with Cloudflare, helps merchants recognize legitimate agents and tell them apart from bots, and Visa has aligned its approach with the Agentic Commerce Protocol and x402.
Visa reported live agent purchases with dozens of European issuers in 2026 and rolled its Agentic Ready program out across regions. It is the natural route for card-based agent shopping.
Mastercard Agent Pay uses Agentic Tokens scoped to a user, an agent and a session, carrying the same fraud protections as a normal card payment. Mastercard says it enabled all US cardholders for agent-initiated payments, completed live agent payments with banks in Europe and Australia, and launched in the UAE as its first market outside the US.
Its Verifiable Intent work focuses on proving what the cardholder actually approved. It suits banks and large merchants that want agent payments on familiar card rails.
Google’s Agent Payments Protocol is an authorization standard rather than a payment network. It uses cryptographically signed mandates to record a user’s intent and the exact cart they approved, so merchants and payment providers can trust that an agent was allowed to spend. It works across cards, bank transfers and crypto, including an x402 extension built with Coinbase.
More than 60 companies backed AP2 at launch, and in 2026 Google released a version supporting purchases where the user is not present and handed the protocol to the FIDO Alliance. It is a layer to adopt alongside a payment provider, not instead of one.
PayPal is building agentic commerce on top of its consumer wallet and merchant network, and it is a launch partner for Google’s AP2 and a supporter of the Agentic Commerce Protocol. For shoppers, that means agents can complete purchases using a familiar PayPal account and its buyer protections.
It is a strong option for merchants whose customers already prefer PayPal at checkout and who want agent purchases to flow through the same account.
Cloudflare co-founded the x402 Foundation and supports x402 in its Agents SDK, so developers can build agents that pay and services that charge without extra infrastructure. Its Pay per Crawl feature lets publishers charge AI crawlers for access, and it developed the Trusted Agent Protocol with Visa.
For publishers and API businesses already behind Cloudflare, it is one of the simplest ways to start getting paid by agents.
Skyfire combines agent identity verification, often called Know Your Agent, with a payments ledger in USDC. Merchants and APIs can check that an agent is verified and tied to a responsible owner before accepting its payment or request.
It suits services that want to sell to agents but need assurance about who is behind them, a gap the card networks are only starting to fill.
Crossmint gives developers APIs to equip agents with wallets and payment methods, supporting stablecoins and traditional rails, along with tooling across the main agent payment protocols. Its guides comparing ACP, AP2, x402 and MPP are widely referenced.
It is a practical choice for teams building agents that need to buy things across many merchants without stitching together several providers.
Circle issues USDC, the stablecoin that settles most x402 payments, and it is a member of the x402 Foundation. Its wallet and payments APIs let businesses hold, send and receive USDC programmatically, which is the foundation many agent payment systems are built on.
It is less a checkout product than a settlement layer, but any team taking stablecoin payments from agents will touch it.
Consumer agents buying products from merchants mostly use card networks, Stripe, PayPal and AP2-style approvals. Agents paying for APIs, data and compute use x402, Coinbase, Cloudflare and stablecoins. Many businesses will need both.
Look for signed mandates, scoped tokens and verified agent identity, so you can prove what the user approved and limit what an agent can spend. Our guide on how to accept payments from AI agents covers the checks merchants should run.
Card-based agent payments inherit chargebacks and fraud protections. Stablecoin payments settle in seconds and are final, so refund policies have to be handled by the merchant.
The easiest path is usually your current processor. Stripe, PayPal and card network programs let many merchants accept agent payments without changing processors, while x402 is simple to add to APIs.
If you already accept crypto, our lists of crypto payment gateways for ecommerce and crypto payment APIs for developers cover providers that can extend to agent payments.
Stripe leads this list because it spans agent checkout, tokens and machine payments in one toolkit, with Coinbase close behind as the force behind x402. Visa and Mastercard bring agent payments onto the card rails most consumers trust, Google’s AP2 supplies the authorization layer, and PayPal, Cloudflare, Skyfire, Crossmint and Circle each solve a specific part of the problem. The protocols are complementary: expect agents to use mandates to prove approval, tokens or stablecoins to pay, and different rails for shopping and for machine-to-machine services.