Steward
EMVCo (owned by American Express, Discover, JCB, Mastercard, UnionPay and Visa); Agentic Payments Task Force
Status
Draft; public comment period closed 2026-09-30
Latest version
EMV Agentic Payments: Framework for Specifications v1.0 DRAFT ()
Primary source
EMVCo Requests Feedback on Framework for Secure, Interoperable and Scalable Card-Based Agentic Payments (external link)

What it is

, the body that writes the EMV card standards, published “EMV Agentic Payments: Framework for Specifications” as a v1.0 draft for public feedback on 2026-09-01. Source [1, 2] EMVCo is owned by American Express, Discover, JCB, Mastercard, UnionPay and Visa, and the work runs in an Agentic Payments Task Force. Source [3, 4]

The draft centers on Intent Services, a shared layer where participants register, reference, retrieve and manage the intent a consumer has authorized, before, during and after a transaction. It targets cases where intent has to be tracked over time: recurring purchases, cumulative budgets and activity after the purchase. It describes ecosystem roles and the data needed to register intent, keep its lifecycle and state, and let authorized parties retrieve it. Source [1] The draft itself sits behind EMVCo’s terms of use, so the atlas does not list its field names.

Status

The comment period ended on 2026-09-30, and no final version was found on 2026-10-11. Source [1] says it may consider (KYA) and agentic transaction indicators in future publications, so neither is part of this draft. It also says the work may lead to changes in EMV , EMV Payment Tokenisation, EMV Secure Remote Commerce and the EMV Digital , and it names the , the OpenID Foundation, the OpenWallet Foundation and W3C as collaborators. Source [1] On 2026-10-08 OpenID Foundation experts published comments on the draft. They asked for a defined verifier role, a split between identity and delegated authority, and a threat model, and they said the comments are not an OpenID Foundation consensus view. Source [5]

How it relates to the eight

, the intent layer of Mastercard Agent Pay, is the only part of the eight that names, and EMVCo describes Intent Services as complementing VI’s cryptographic assurance. Source [1, 4] The link to AP2 is indirect: AP2’s authorization example asks for a of type com.emvco.dpc, the EMV Digital Payment Credential, which the framework says it may inform. Source [1, 6] Visa and Mastercard are among EMVCo’s owners, but the framework does not name or Pay. Source [1, 3]

Status history

Relations at a glance

How EMVCo agentic payments framework relates to each protocol
ProtocolRelationNote
Mastercard Agent PayComplementsThe framework names Mastercard's Verifiable Intent as an existing solution whose cryptographic assurance Intent Services would complement.
AP2ComplementsIndirect. AP2's example requests a credential of type com.emvco.dpc (the EMV Digital Payment Credential), a technology the framework says it may inform.

Back to the orbit

Sources

  1. EMVCo Requests Feedback on Framework for Secure, Interoperable and Scalable Card-Based Agentic Payments (external link)EMVCo. Standard, primary source. Published . Accessed .
  2. EMV Agentic Payments: Framework for Specifications v1.0 DRAFT: Comment period ends 30-Sept 2026 (external link)EMVCo. Standard, primary source. Accessed .
  3. Overview of EMVCo (external link)EMVCo. Documentation, primary source. Accessed .
  4. How EMVCo is Working to Enable Secure, Interoperable and Scalable Card-Based Agentic Payments (external link)EMVCo Knowledge Hub (Clinton Allen). Standard, primary source. Accessed .
  5. OIDF responds to EMVCo Agentic Payments framework draft (external link)OpenID Foundation. Announcement, primary source. Published . Accessed .
  6. AP2 Agent Authorization (external link)Google (google-agentic-commerce). Specification, primary source. Published . Accessed .

Source details

    Loading the index.

    Enter open Esc close ? shortcuts