Analysts are predicting that the digital economy is growing at three times the rate of national GDPs, driven largely by AI in various ways. Some speculators think AI-enhanced workplaces could generate nearly USD $4.91 trillion by 2026. With that kind of money involved, it’s no surprise that a whole new financial ecosystem is emerging around AI.

The earliest incarnations of AI mostly resembled an accelerated version of existing workflows, essentially automating the boring stuff in order to enhance productivity and allow greater focus on more important tasks. This traditional format falls short when it comes to making and authorizing payments, however, as each transaction needs to be authorized by a human.

Human approvals are inconvenient at the best of times and become excessively restrictive when it comes to paying for things like API access. Imagine having to authorize every single API call by hand, especially when dealing with large batches of transactions that are all too common in batch processing. For an AI to be truly useful, it needs to be able to make payments on its own accord. This is where agent payment protocols (APPs) come into play.

Agent payment protocols allow agentic AI ecosystems to send and receive payments via API endpoints. APPs are simply API assets containing financial data that’s returned in a JSON object. While the idea and architecture are fairly simple, the implications are profound.

APPs have been proliferating, creating a glut of payment protocols to pick from. To help you decide which one will best suit your project, we’ve put together this side-by-side comparison of emerging agent payment protocols and how they can support agentic AI workflows.

1. Agents Payment Protocol (AP2)

The Agents Payment Protocol (AP2) is an open-source payments protocol designed to allow safe, secure, trackable financial transactions initiated by agents. While most payment protocols focus on authentication, AP2 prioritizes intent, making sure that the agent is making purchases the way that the user intends. To achieve both the trust necessary for a financial protocol as well as establishing the user’s intent, AP2 uses mandates, which are tamper-proof, cryptographically-signed digital contracts that serve as verifiable proof of the instructions provided by the user.

AP2 was created by Google in collaboration with leading financial institutions and providers like PayPal, Coinbase, and American Express in response to the rising agentic economy. The current payment system assumes there’s a human at the keyboard authorizing all purchases. AP2 authorizes agents to act on your behalf, signing an authentication agreement upfront, allowing the agent to act in your stead. This has the potential to unlock all manner of dynamic ecommerce actions, such as automating purchases based on price changes or availability.

AP2 allows three different types of mandates. The first is an intent mandate, specifying the conditions under which an agent can make a purchase. Cart mandates, which require user authentication before a purchase can be finalized. Finally, payment mandates signal an agent’s involvement with payment networks.

2. Agentic Commerce Protocol (ACP)

Agentic Commerce Protocol (ACP) is an open-source payment specification created by OpenAI and Stripe. It dictates how agents are able to interact with merchants via four RESTful endpoints: Create Checkout, Update Checkout, Complete Checkout, and Cancel Checkout. Payments are handled via SharedPaymentTokens, which are single-use tokens restricted to a particular window of time, striking a good balance between user control and AI agent autonomy.

ACP’s first major rollout was in ChatGPT’s Instant Checkout in February 2026, allowing users to make in-chat purchases from Etsy sellers. They have since dialed back the in-chat purchases in favor of a more app-based ecosystem, as of March 2026. The only downside is that ACP is meant more for situations where a human is present rather than fully autonomous agentic systems.

3. x402

x402 describes the payment protocol as “the internet’s payment protocol.” It’s an open payment protocol that enables instant payments via HTTP using the 402 standard. When a client requests a paid resource, the server returns an HTTP 402 and payment instructions, like the total amount, type of currency, or destination wallet. It doesn’t require an account, session, or even an API key.

x402 was launched in December 2025 and was designed by Coinbase, which uses it for wallet-based identity, dynamic payment recipients, and multi-chain support. It offers native support for Base, Ethereum, Polygon, Solana, Avalanche, and Sui with no processing fees other than on-chain gas. This makes x402 ideal for agent-to-agent payments. Its only downside is that x402 only uses stablecoin, so it can’t be used for transactions involving physical goods or commerce.

4. Stripe MPP

Machine Payments Protocol (MPP) is a new open standard created by Stripe and Tempo designed to allow agents to pay for API access with a single HTML request. It’s designed to simplify the API payment process, sending a 402 Payment Required response to an agent from a dedicated endpoint. The agent only has to pay the amount specified in the WWW-Authenticate: Payment header of the 402 Payment Required response, which describes the cost, expected form of currency, and accepted forms of payment. When the payment is authenticated, the agent is sent an asset containing an Authorization: Payment header, which authorizes the endpoint to deliver a 200 OK status along with the requested asset.

Being based around the 402 Payment Required status makes Stripe MPP very similar to x402, but with one key difference. x402 is only able to accept cryptocurrency payments. Stripe MPP accepts credit and debit card payments as well as cryptocurrencies, making it an obvious and much-needed evolution of the agent payment protocol. x402 also tends to get expensive very quickly, as every payment takes place on the blockchain. Stripe MPP allows users to deposit funds upfront, which can then be used to make payments using fast, lightweight vouchers. Perhaps best of all, Stripe MPP is configured very similarly to Stripe itself, so many users will already be more familiar with its format, making it less daunting for new users to get started.

5. Agent Transfer Protocol (AGTP)

Agents are not human, so they shouldn’t be forced to adhere to human standards and protocols. Agents don’t click links or browse results. Instead, they execute complex workflows using simple HTTP requests. It stands to reason that agentic AI would get its own transfer protocol.

The Agent Transfer Protocol was designed as a dedicated layer for AI agents, intended to exist between the TLS layer and the agent itself. Instead of relying on the relatively crude traditional HTTP requests used by APIs, it introduces new intent verbs specifically designed for agentic AI like QUERY, SUMMARIZE, BOOK, SCHEDULE, LEARN, DELEGATE, COLLABORATE, CONFIRM, ESCALATE, and NOTIFY. Most importantly for payments, AGTP introduces a PURCHASE command, which instructs the agent to interact with an external payment tool like a digital wallet or a financial API.

Best of all, each time a financial transaction is completed successfully via AGTP, the protocol’s trust index is updated, marking both the agent and the payment tool as trustworthy — an essential part of the agentic protocol’s ability to return trustworthy results.

AGTP’s only real drawback is that it’s not a native payment protocol in its own right, like the other APPs on our list. That said, its ability to pick reliable tools for handling financial transactions securely, paired with all its other advantages, still makes the proposed protocol an exciting development for agentic AI.

Agent Payment Protocols: When to Use Each

Agent payment protocols are an indispensable part of AI becoming truly agentic. After all, AI isn’t as useful as it could be if you have to validate every step of the process, including processing payments. As AI continues to become more autonomous, agent payment protocols are only going to increase in importance.

Each of the five APPs we’ve looked at today has its strengths as well as its shortcomings. Here’s a brief overview of when to use each:

• If you’re looking for a payment protocol for high-trust, user-governed financial environments that maintain tight control over authorization and intent, AP2 is likely to best suit your needs.
• For commerce flows involving the public, try ACP.
• x402 is a good pick for a fully autonomous native payment protocol if you’re not averse to cryptocurrency.
• Stripe MPP offers many of the same advantages while still accepting traditional financial tools.
• Finally, although AGTP isn’t a dedicated payment protocol like the other APPs on our list, it’s still worth a look, especially considering its many other advantages.