Skip to content
IAM Insights

Explainers · Glossary

AP2

Agent Payment Protocol

Google's open protocol for letting AI agents make payments on a person's behalf with signed proof of what they approved.

reference →

In our briefings

The claim each of the newest briefings on AP2 would have you leave with.

  1. Verifiable Intent chains three layers of signed SD-JWT credentials, tokens whose fields can be shown selectively. The issuer, a bank or payment network, binds the user's key for about a year (L1). The user signs mandates for the agent (L2): final values for an immediate purchase or, in autonomous mode, constraints plus the agent's key for a recommended 24 hours to 30 days. In autonomous mode the agent then signs a payment mandate for the network and a checkout mandate for the merchant, each valid about five minutes (L3a, L3b). The specification says "Layer 3 credentials MUST NOT contain a `cnf` claim in the payload (terminal delegation)", so the agent's credential names no next key and the agent cannot pass its authority to another agent. A verifier checks the agent's final values against the user's constraints, but only the ones disclosed to it, and it skips the allowlist check when no allowlist was disclosed. Eight constraint types are defined (merchants, line items, payees, amount range, budget, recurrence, agent recurrence, reference). Budget and the two recurrence limits need the payment network to keep a running count.

    Verifiable Intent stops an AI agent from passing its buying authority on, and v0.1 has no protocol to revoke itBI-FIND-2026-0477

  2. Section 6 of EMVCo's framework presents Verifiable Intent v0.1 as one realisation of its three layers and sends reviewers to "the authoritative repository maintained by FIDO" for the current text, which it says continues to evolve. Verifiable Intent is a chain of SD-JWT verifiable credentials. A payment credential provider signs the first, and the named candidate is EMVCo's own Card Digital Payment Credential (DPC). The consumer signs the second through a wallet. In autonomous mode that layer carries the agent's key, and the agent signs a third layer of two credentials, a closed Payment Mandate and a closed checkout mandate, each bound by hash to Layer 2 and both tied to the hash of a merchant-signed checkout; in immediate mode the chain stops at the consumer's layer. Selective disclosure keeps the two apart: the merchant receives the checkout mandate, the payment system the Payment Mandate, and neither can reconstruct disclosures it was not given. A verifier in permissive mode may skip a constraint type it does not recognise, though the framework says security-critical verifiers should treat one as a failure. Section 1.2.2 declares credential-format primitives such as SD-JWT structures out of scope, and section 6.7 then specifies SD-JWT VC as Verifiable Intent's format. We read the consumer and agent layers as the open and closed mandates of Google's AP2, which the framework's text does not name.

    EMVCo's agent card-payment draft binds no one yet and points to a spec FIDO maintains for proof of consentBI-FIND-2026-0440

  3. The FIDO Alliance, the body behind passkeys, has taken on authentication and commerce for AI agents. Megan Shamas, its chief marketing officer, says FIDO "received two spec contributions", Google's Agent Payments Protocol (AP2) and Mastercard's Verifiable Intent, and is now working them into a specification to put out into the market. OpenAI, in her words, "has joined us at the board level", and the working groups FIDO has "just launched" have drawn "an enormous amount of interest"; she reads the contributions and the board seat as the industry agreeing the work belongs at FIDO. She gives no date beyond "very soon, I hope". Her list of what an agent purchase must keep is approval and consent, auditability, privacy and the ability to revoke, and in the interview she does not describe how a FIDO credential would provide them. Meanwhile she has been asking people to "please hang on, please don't move too fast on this until we can do this properly."

    FIDO's marketing chief calls agent identity 'not a thing' and asks the industry to hang on for a standardBI-FIND-2026-0246

›Cited in 35 briefings

Every briefing that discusses this term, newest first.

  1. Verifiable Intent stops an AI agent from passing its buying authority on, and v0.1 has no protocol to revoke it

    Article · · Verifiable Intent (GitHub, agent-intent/verifiable-intent) · Verifiable Intent Working Group · Apr 18, 2026

  2. EMVCo's agent card-payment draft binds no one yet and points to a spec FIDO maintains for proof of consent

    Article · · EMVCo · Aug 27, 2026

  3. FIDO's marketing chief calls agent identity 'not a thing' and asks the industry to hang on for a standard

    Podcast · · Authentic Talks - An HID Podcast · What FIDO Alliance Sees Next: Passkeys, AI Agents, and the Future of Identity? · Jun 23, 2026

  4. Google's AP2 v0.2 ties an agent's purchase to the merchant's own signed checkout by hash

    Article · · ap2-protocol.org · Google · Apr 28, 2026

  5. A new STIR draft would let a number's holder require AI agents calling from it to say so

    Draft · · IETF Datatracker · Jon Peterson, TransUnion · Nov 2, 2026

  6. Sello has the services an AI agent calls sign its receipts; the agent can't fake them, but it can go around them

    Paper · · arXiv · Juan Figuera · Jun 2, 2026

  7. Agent-audit draft now admits a call on the principal and the current agent, as RFC 8693 requires

    Draft · · IETF Datatracker · Shameer Thaha et al. · Oct 19, 2026

  8. OAuth adopts Delegate SD-JWT, which traces each hand-off to the issuer but never checks that authority narrowed

    Draft · · IETF Datatracker · Gareth Oliver et al. · Apr 22, 2026

  9. Delegation receipts for AI agents, revision 15: holding a copy of a receipt no longer lets you extend the chain

    Draft · · IETF Datatracker · Ryan Nelson, Authproof · Oct 22, 2026

  10. Agents and MCP servers get broad standing access because it is quick or easy, three voices say, and three vendors now pitch a gateway in front of MCP

    Field signals · · 9 voices from the field · Sep 2025 to Oct 2026

  11. At OWASP, one poisoned memory entry made a demo agent send a Q4 report to an attacker server

    Video · · OWASP Foundation · Recorded Jun 2026 · Uploaded October 21, 2026

  12. x402 saw about $1 million in agent payments in 30 days; Apify's founder says agents still buy through API keys

    Video · · AI Engineer · Uploaded October 18, 2026

  13. ChainIT's design has the payment rail rebuild each payment's hash before money moves; the paper reports no test

    Paper · · arXiv · Jeremy Blackburn et al. · Oct 16, 2026

  14. Nothing carries a person's limits on an agent through to the moment it acts, Yossif's problem statement argues

    Draft · · IETF Datatracker · Mohamad Khalil Yossif · Jul 22, 2026

  15. Schrock's receipts prove a named key approved one exact agent action, and the draft lists at length what they cannot prove

    Draft · · IETF Datatracker · Iman Schrock, EMILIA Protocol · Sep 12, 2026

  16. Before an agent pays or changes data, Schrock's last check treats it as untrusted and keeps the record itself

    Draft · · IETF Datatracker · Iman Schrock, EMILIA Protocol · Sep 26, 2026

  17. Three Thales researchers want the card issuer, not the agent platform, to hold an agent's spending limits

    Paper · · arXiv · Kaushal et al. · Sep 23, 2026

  18. Hardt's AAuth Budgets caps what an agent may spend at each resource, and hides the person's real limit from it

    Draft · · IETF Datatracker · Dick Hardt · Sep 28, 2026

  19. x402 v2 can take payment before delivering, with no identity beyond a wallet address and no way to dispute it

    Article · · x402 Foundation (GitHub) · x402 Foundation · Aug 31, 2026

  20. FIDO's agent authentication group is led by Google, OpenAI and a pharmacy chain; card networks lead payments

    Article · · FIDO Alliance · FIDO Alliance · Apr 28, 2026

  21. Google's AP2 lets a verifier trust a credential issuer or the agent's provider, with no trust list or revocation

    Article · · ap2-protocol.org · Google · Apr 28, 2026

  22. OAuth handles an agent in one company, working while you watch. The OpenID paper says that is where it stops.

    Article · · OpenID Foundation · Tobin South et al. · Oct 2025

  23. In May 2026 Blackhawk's technology chief said Google's AP2 means little to merchants without a credential store

    Podcast · · So What About AI Agents · Agentic Commerce - Who's side is agent on? EP 60 - with Nik Sathe - Blackhawk Network (BHN) · Jun 10, 2026

  24. Agent payment protocols prove an agent may pay; a Toronto paper adds a step to check the job was done

    Paper · · arXiv · Adrian de Valois-Franklin et al. · Jun 7, 2026

  25. A proposed consent log for A2A and MCP records the terms an agent accepted, but the agent fills it in itself

    Paper · · arXiv · Ravi Kiran Kadaboina · Apr 16, 2026

  26. Most agent-payment protocols leave the agent's own reasoning out of scope, a survey of 142 works finds

    Paper · · arXiv · Qian'ang Mao et al. · Apr 15, 2026

  27. AITH claims 4.7 million agent checks a second, but the test simulated its post-quantum signatures

    Paper · · arXiv · Zhaoliang Chen · Apr 9, 2026

  28. Google DeepMind wants agent authority to narrow at every hand-off, and misreads MCP's scopes on the way

    Paper · · arXiv · Nenad Tomašev et al. · Feb 12, 2026

  29. eBay researchers say AP2 does not make a payment mandate single-use, so they built a gateway that does

    Paper · · arXiv · Qianlong Lan et al. · Feb 6, 2026

  30. A January design paper argued AP2 and x402 move money before anyone checks the work, and proposed escrow

    Paper · · arXiv · Mehul Goenka et al. · Jan 30, 2026

  31. CORAL's public agent server rejected forged messages but let a wrong key open the session stream

    Paper · · arXiv · Yedidel Louck et al. · Nov 5, 2025

  32. OpenAI and Stripe's agent checkout stores a card for one capped purchase, and no one issues the caller's token

    Article · · Agentic Commerce Protocol (GitHub) · OpenAI et al. · Sep 29, 2025

  33. PayPal says it backs Google's AP2 and will process payments for Google's products

    Article · · Digital Transactions · Peter Lucas · Sep 18, 2025

  34. In x402 a wallet signature is the whole payment: no agent identity, no delegation, no refund once money moves

    Article · · x402.org (Coinbase Developer Platform) · Erik Reppel et al. · Aug 16, 2025

  35. OpenID4VP 1.0 makes verifiers re-check what a wallet returns, and cannot show a holder acting for someone else

    Article · · OpenID Foundation · Oliver Terbu et al. · Jul 9, 2025

Related terms

What appears alongside AP2 in the same briefings.

x402GoogleFIDO AllianceAgentic Commerce ProtocolVerifiable IntentUniversal Commerce ProtocolStripeMastercard