Payment Protocols · 6 min read · 5 November 2026

AP2 mandates explained: proving a human approved an agent purchase

Intent, cart and payment mandates are signed credentials. They let a merchant prove the charge matched what the user authorised, and give you evidence in a dispute.

The gap AP2 fills

When an agent pays, the merchant needs evidence that a real person wanted this purchase. Card networks and issuers have no way to see the conversation that led to the charge, so disputes and fraud claims become guesswork. AP2 makes that evidence a cryptographic object that travels with the payment.

Intent mandate

The intent mandate records what the user asked for in their own words, signed by the user's side. It is deliberately loose: "a pair of running shoes under $120" is enough. It is the answer to "did the human want this at all".

Cart mandate

The cart mandate is the receipt before the receipt: the exact items, quantities, prices and merchant, signed before payment is authorised. If the checkout page later changes the amount or the seller, the signed cart no longer matches and the mismatch is provable.

Payment mandate

The payment mandate is what the agent shows the merchant or payment network: a signed statement that this specific cart was approved by this specific user. It works across cards, banks and crypto, so the same proof survives whichever rail settles the money.

What it does not do

A signed mandate does not stop a model from being manipulated into signing the wrong thing, and it does not replace spending limits. Treat mandates as the audit trail that tells you what happened, and keep policy checks and human confirmation as the controls that stop it happening.