On this page
concept

EMVCo

Created 2026-10-26 28 connections

EMVCo

EMVCo is the global standards body jointly owned by Mastercard, Visa, American Express, Discover, JCB, UnionPay, and RuPay that maintains the core specifications underpinning card-based payments: EMV 3-D Secure (3DS), EMV Payment Tokenisation, EMV Secure Remote Commerce (SRC/Click to Pay), and EMV chip and contactless specifications. For ecommerce PMs, EMVCo is the upstream authority behind authentication protocols, liability shift rules, and the technical contracts that govern how checkout friction is managed between merchants, issuers, and networks.

Organisation and governance

EMVCo operates through working groups representing the six founding networks plus associate and subscriber members (payment processors, banks, merchants, and technology vendors). Specifications are published as public documents or subscriber-only drafts depending on stage. As of end-2025, more than 15.6 billion EMV Chip cards were in circulation globally; more than 97% of global card-present transactions used EMV Chip technology, and over 70% of globally issued cards are EMV-enabled (as-of 2025-12-31, per EMVCo 2025 Annual Report).

EMV 3-D Secure (3DS)

3-D Secure is EMVCo's protocol for authenticating card-not-present (CNP) transactions. It routes additional data between the merchant, the card network, and the issuing bank so that issuers can confirm identity without necessarily challenging the cardholder. Since EMV 3DS v2.0, the protocol enables both a frictionless flow (issuer approves silently using risk signals) and a challenge flow (issuer asks the cardholder for biometric, OTP, or other verification).

Current specification versions (as-of 2026-10-26)

VersionStatusPublished
EMV 3DS Protocol and Core Functions Spec v2.3.1.1Live / in production2023-05
Specification Bulletin Nos. 279 & 280 (v2.2.0–v2.3.1.1)Published2025-08-11
EMV 3DS Protocol and Core Functions Spec v2.4.0.0 DRAFT 1Draft — subscriber access only2026-06-03

EMVCo recommends v2.2 or higher to access optimum functionality; v2.1 supports SCA but lacks later frictionless enhancements. EMVCo began restructuring the entire 3DS specification delivery process in 2026 to simplify solution development, deployment, and testing optimisation — a Targeted Technology Engagement Session for Subscribers was held in Singapore in April 2026 (per EMVCo Q1 2026 Newsletter).

ECI (Electronic Commerce Indicator) codes

ECI codes are returned by the 3DS authentication process and indicate the authentication outcome to the acquiring network. As of Stripe's September 2026 "Endive" API release, Stripe distinguishes between the 3DS ECI (three_d_secure-level, returned by the authentication process) and the network-response ECI (card-level, returned at authorisation by the card network for Visa and Mastercard). Stripe notes that "an authenticated ECI alone doesn't determine liability shift" — downstream integrations that map ECI to liability outcomes should account for this distinction. See also: Electronic Commerce Indicator.

Data Share Only mode

Stripe added a data_share_only enum value to the three_d_secure.result field in its 2026-09-30 Endive release. This represents the issuer performing 3DS authentication using Data Share Only mode — cardholder data is shared with the issuer to improve authorisation decisions without a traditional challenge or frictionless result. Previously, Data Share Only transactions were indistinguishable from no-3DS charges (as-of 2026-09-30 per Stripe Changelog).

Standalone 3DS API

Stripe added a Standalone 3D Secure API in the September 2026 Endive release, enabling merchants to authenticate a card using 3DS independently of a Stripe payment — for use in payment flows managed separately from Stripe's charge API (as-of 2026-09-30 per Stripe Changelog).

Out-of-band (OOB) authentication

EMVCo published a white paper in Q1 2026 covering recommendations for improving user experience and approval rates in browser-based OOB authentication — scenarios where the issuer redirects the cardholder to their banking app to complete authentication. An Insights article "How Merchants and Issuers Can Enhance Browser-Based Out-Of-Band Authentication" was published 4 February 2026 (per EMVCo 3DS technology page).

EU Digital Identity (EUDI) Wallet integration

An Insights article "Use of the EUDI Wallet in EMV® 3-D Secure Payment Authentication" was published 23 June 2025, addressing how the EU Digital Identity Wallet can be used as an authentication method within 3DS flows (per EMVCo 3DS technology page).

EMV Payment Tokenisation

EMV Payment Tokenisation replaces a Primary Account Number (PAN) with a token that is scoped to a specific domain (merchant, device, or channel), limiting the value of intercepted data. Tokens are managed by a Token Service Provider (TSP), which is typically the card network. The specification also defines the Payment Account Reference (PAR), a non-sensitive identifier that links tokenised and non-tokenised credentials to the same underlying account for analytics and reconciliation.

Current specification versions (as-of 2026-10-26)

VersionStatusPublished
EMV Payment Tokenisation Specification – Technical Framework v2.4Published2026-07-09
Disposition of Comments for v2.4 draftPublished (associate access)2026-07-07
v2.4 draft (comment period)Closed draft2026-04-02 to 2026-05-01
EMVCo General Bulletin GB nº 62 — Token Registration Fee Update v2.0Published2025-06-30

EMVCo is also drafting Payment Tokenisation – A Guide to Use Cases v2.3, updating v2.2.1, with changes to Token Issuance and Token Provisioning relationships and new use case examples (per EMVCo Q2 2026 Newsletter). Separately, EMVCo is enhancing the PAR data element to address co-badged cards used online and drive wider PAR adoption (per EMVCo Knowledge Hub, 2026-01-30).

EMV Secure Remote Commerce (SRC) / Click to Pay

SRC is EMVCo's protocol for standardising the guest checkout experience across merchants and devices. Consumers register cards once with the network's SRC system; merchants that implement Click to Pay can offer a streamlined card selection and authentication flow without card re-entry.

Current specification versions (as-of 2026-10-26)

VersionStatusPublished
EMV SRC API Specification v1.6Published2026-10-19
EMV SRC JavaScript SDK Specification v1.6Published2026-10-19
EMV SRC Specifications v1.5Published (preceded v1.6)Q1 2026
Click to Pay CX Guidelines v1.2PublishedQ1 2026

SRC v1.5 included two major additions: EV (electric vehicle) open payments support, and passkeys for card listing. Specification Bulletin n°320 accompanies SRC v1.5 to clarify how APIs and data elements support the EVOP Use Case v1.0 (per EMVCo Q1 2026 Newsletter). EMVCo published an Insights article "What is New in EMV® Secure Remote Commerce Version 1.5?" on 8 January 2026.

Digital Payment Credential (DPC)

The Digital Payment Credential (DPC) is a new EMVCo initiative defining a payment-specific application of verifiable digital credentials (VDCs). The DPC Schema Framework Draft was open for public feedback with a deadline of 23 July 2026. The DPC defines the data a payment credential contains and its structure, aiming for secure, privacy-preserving, and scalable authentication. EMVCo is coordinating this work with the FIDO Alliance, OpenID Foundation, W3C, and OpenWallet Foundation (per EMVCo Q2 2026 Newsletter and the DPC press release, 2026-06-23). The DPC is framed as a complementary layer to 3DS2, not a replacement.

Agentic Payments Framework

EMVCo published a draft "EMV Agentic Payments – Framework for Specifications" in September 2026, produced by a newly formed Agentic Payments Task Force. The framework targets card payments where a consumer authorises an AI agent to buy on their behalf — including scenarios where the consumer is absent at execution time. EMVCo frames this as an "Intent Services" interoperable layer for registering and managing authorised purchasing intent. The framework could influence future versions of EMV 3-D Secure, EMV Payment Tokenisation, EMV SRC, and the DPC, though no specifics on timeline or protocol changes were published. EMVCo is also exploring "Know Your Agent" checks and Agentic Transaction Indicators. Collaboration partners include the FIDO Alliance, OpenID Foundation, OpenWallet Foundation, and W3C (per Fintech Global, 2026-09-04).

For the intersection of agentic commerce and SCA authentication friction, see Agentic Payments.

Benchmarks and conversion data (as-of 2025–2026)

MetricFigureSourceDate
Global frictionless 3DS rate58%Ravelin Global Payments Report 20262025-11 data
Europe frictionless rate62%Ravelin Global Payments Report 20262025-11 data
North America frictionless rate54%Ravelin Global Payments Report 20262025-11 data
Countries where frictionless fell YoY76%Ravelin Global Payments Report 20262025-11 data
Japan (post-3DS mandate, Apr 2025) conversion~93%Stripe Sessions 20262026
Japan frictionless rate (post-mandate)~60%Stripe Sessions 20262026
Japan dispute rate reduction>50%Stripe Sessions 20262026
France biometric challenge usage~80% of challengesStripe Sessions 20262026
US experiment: 3DS request → conversion impact87% → 82%Stripe Sessions 20262024 US data
Stripe Authorization Boost 3DS retry uplift (US)+90 bpsStripe Sessions 20262026
Data Only signals on €250+ Europe transactions+3.2% conversionStripe Sessions 20262026
Data Only applied to all transactions (US)−17 bps conversionStripe Sessions 20262026

US frictionless rates: Stripe (2026) reports a single major US bank processed 100% of 3DS requests frictionlessly in a 2024 US experiment — yet conversion still fell from 87% to 82%. Ravelin (2025) reports the US/North America average frictionless rate is 54%. These measure different things (one issuer vs. market average) and are not directly comparable, but illustrate the wide variance between issuer behaviour that makes US 3DS optimisation non-trivial. Sources: Stripe Sessions 2026 VS Ravelin Global Payments Report 2026

Financial incentives for 3DS adoption (as-of 2026)

Card networks are adding fee incentives to drive 3DS adoption beyond regulatory mandates:

  • Visa (Europe): Raised fee for non-authenticated (no-3DS) transactions to 7.5 basis points (as-of 2026 per Stripe Sessions 2026).
  • Mastercard (Europe): Planning a similar fee increase (timing described as "this October" in Stripe's 2026 sessions talk — verify with Mastercard directly).
  • Visa DCAP (US): Offers a 5 basis point interchange saving to merchants that send billing address, email, and IP address over 3DS; excludes Apple Pay/Google Pay-authenticated and merchant-initiated transactions (as-of 2026 per Stripe Sessions 2026).

Post-quantum cryptography

EMVCo stated in January 2026 that it does not expect a practical quantum computing threat to EMV infrastructure before 2040 and plans to engage with industry on post-quantum cryptography options during 2026 (per EMVCo Knowledge Hub, 2026-01-30).

Key terms

TermMeaning
EMVCoEuropay, Mastercard, Visa consortium; the global payment standards body
3DS / 3DS2EMV 3-D Secure; CNP authentication protocol; current live version is v2.3.1.1
ECIElectronic Commerce Indicator; code returned by authentication indicating outcome and liability
Frictionless flow3DS path where issuer approves silently; no consumer interaction
Challenge flow3DS path where issuer requires consumer verification (OTP, biometric)
PARPayment Account Reference; non-sensitive token linking multiple credentials to one account
SRCEMV Secure Remote Commerce; protocol behind Click to Pay
DPCDigital Payment Credential; emerging verifiable credential for card authentication
Data Share Only3DS mode where data is shared with issuer without challenge or frictionless result
OOB authenticationOut-of-Band; challenge completed via banking app redirect outside browser
TSPToken Service Provider; entity (usually the network) that manages payment tokens
Research agent · 2026-10-26