Levee / Learn / Agent payments protocols compared

Agent payments protocols compared: AP2, x402, Visa and Mastercard

Protocols decide how an agent pays. None of them decide whether it should.

Short answer: AP2, x402, Visa Intelligent Commerce and Mastercard Agent Pay are ways for an AI agent to prove intent or move a payment. None of them decide how much an agent may spend or on what. That decision needs its own control, enforced outside the agent. See AI agent spend controls for how to set it up.

Why protocols are not controls

Agentic payments are moving quickly, and several groups have published ways for software to pay. They answer practical questions: how does a merchant know an agent is acting for a real person, how is a payment credential passed safely, and how does money settle. Those are plumbing questions. A different question sits on top of them: should this agent be allowed to make this purchase right now? A protocol can carry the answer, but it does not write it. Someone still has to define limits, approve them and check every payment against them.

The four approaches at a glance

ApproachMain ideaTypical railWhat it leaves open
AP2 (Agent Payments Protocol)Signed mandates that record what a user authorized an agent to doCards, bank transfers and othersHow limits are set and enforced per payment
x402Pay for a web resource with the HTTP 402 status codeStablecoins, mainlyWho approved the budget and what it may cover
Visa Intelligent CommerceAgent-ready card credentials and signals on the card networkCardsThe business rules for each agent purchase
Mastercard Agent PayTokenized agent credentials on the card networkCardsThe business rules for each agent purchase

Details change as each standard develops, so check the publisher's own documentation before building on one. The table describes the broad design of each, not a full specification.

AP2: proving what a person authorized

AP2 centres on mandates, which are signed records of what a user asked an agent to do. That makes a purchase easier to explain afterwards, because there is evidence of intent. It is closest in spirit to a spend mandate, and we compare the two in more detail in the agentic payments glossary. A signed record of intent helps with disputes. It does not by itself stop a purchase that falls outside that intent unless something checks each payment against it.

x402: paying per request

x402 revives the HTTP 402 Payment Required code so a client can pay for an API call or page and then receive it. It suits machine-to-machine usage where each request is small. The open question for a business is budget: an agent that can pay per request can also pay many times. A cap, an allowed-service list and an end date matter as much here as on a card. Our guide to AI agent spend limits covers the limits to set.

Visa and Mastercard: agents on the card networks

Both networks are working on ways to identify agent-initiated transactions and to pass tokenized credentials rather than raw card numbers. For a company, this means agent purchases can ride existing merchant acceptance. The card still needs rules. Category blocks and credit lines are blunt, as we explain in why card limits and MCC blocks are not enough.

Where spend controls fit

A spend control sits between intent and settlement. A person approves what the agent may buy. At the moment of payment, a check compares the purchase with that approval and returns approve, decline or a request for a person. The check works the same way whichever protocol carried the payment, as long as it runs where the payment is authorized and outside the agent.

  • Protocols answer who the agent is and how the payment travels.
  • Controls answer whether this purchase is allowed.
  • Records answer what was decided and why, which finance and audit teams ask for.

Treating these as three layers avoids a common mistake: assuming a standard payment protocol also gives you governance.

Choosing a protocol

  • Buying from existing online merchants usually points to card rails.
  • Paying for APIs and data per call points to x402-style flows.
  • Needing a portable proof of user intent points to a mandate-based approach such as AP2.
  • Whichever you pick, put limits, an end date and human approval for exceptions in front of it.

How Levee fits

Levee is the authorization layer for AI agent spend. Levee lets a human approve what an agent may spend, enforces it at the moment of card authorization, outside the agent, and keeps tamper-evident proof of every decision. Levee is not a payment protocol. Its mandate engine is designed to work across rails, and cards issued through Airwallex are the first live rail. Levee never holds or moves money. Authorization declines purchases outside the mandate, which bounds the damage if an agent is misled. For a comparison of products, see AI agent spend control tools compared, or visit the Levee homepage.

Frequently asked questions

What is the difference between AP2 and x402?

AP2 is an open protocol from Google for agent-led payments built around signed mandates. x402 uses the HTTP 402 status code so software can pay for a resource directly, often with stablecoins. They solve different parts of the payment flow.

Do agent payment protocols include spend controls?

They carry or prove intent and move payments. Limits on what an agent may buy, and the decision to approve or decline each purchase, still have to be defined and enforced by someone, and the protocols do not replace that.

Which protocol should I use for an AI agent?

It depends on the rail and the merchants. Card networks suit existing merchants, x402 suits pay-per-request APIs, and AP2 targets signed intent across payment types. Whatever you choose, enforce limits outside the agent.

Is Levee a payment protocol?

No. Levee is the authorization layer for AI agent spend. It decides, at the moment of card authorization, whether a purchase matches what a human approved. Cards issued through Airwallex are the first live rail, and Levee never holds or moves money.

Can a spend mandate work with these protocols?

The idea is compatible. A mandate defines what an agent may buy, and a protocol carries the payment. Levee is rail-agnostic by design, but only cards via Airwallex are live today.

Related

Levee is running a free design partner pilot for platforms putting AI agents in charge of spend.

Become a design partner

Published by Levee, 2026-11-09. Levee is the authorization layer for AI agent spend: levee.dev.