Standard · Transact
AP2 (Agent Payments Protocol)
Signed mandates that prove what the person approved before an agent pays.
Watching
What it is
AP2 uses signed records (mandates) for intent, cart and payment, so everyone can later see what a person approved. It works with cards, bank transfers and stablecoins.
An analogy
A signed purchase order that proves the boss agreed to the spend.
At a glance
- Owner
- Google; reported moved to the FIDO Alliance with Verifiable Intent in April 2026
- Maturity
- Watching Announced September 2025 with more than 60 partners. The move to the FIDO Alliance is reported, not confirmed from a primary page.
- Where it lives
- ap2-protocol.org
- Framework domain
- Transact: Be chosen
- What it serves
- Prove an agent’s authority to pay
Who should care
The roles this standard touches most. See all the roles on the personas page.
- Legal, risk and security. Set the policies: which agents may do what, identity, data, disclosure and liability.
- Commerce and sales. Make offers, prices, availability and checkout work for agents buying on someone’s behalf.
- Engineering and product. Build the access, data, endpoints and actions that agents use, on open standards.
How to adopt it
- 1
Do not build on it directly: your payment provider and commerce platform bring it.
- 2
Ask your provider how it handles agent mandates.
- 3
Follow the governance move before planning anything further.
The Institute’s view
Watch
Important for how agents will pay, but it reaches most organizations through their payment provider. Watch it and ask your provider about it.
Standards change fast. Last reviewed November 2026.