On this page
- How it works
- Frictionless vs challenge
- SCA exemptions
- Liability shift
- 3DS2 vs 3DS1
- Versions
- Regulatory landscape
- Europe (EEA + UK)
- Asia-Pacific
- United States
- Mastercard TLID — mandatory from October 2026
- Conversion impact
- Challenge method mix (Stripe Sessions 2026, platform data)
- Data Only flows (Stripe Sessions 2026, platform data)
- Network fee incentives (as-of October 2026)
- Stripe Authorization Boost (retries)
- Merchant optimization benchmarks
- 2026 platform developments
- Stripe — Endive API (2026-09-30)
- Adyen — Authenticate upgrade (2026-09-22)
- EMVCo — "next evolution" announcement (2026-01-30)
- Agentic commerce edge cases
- Key terms
- Benchmarks (as-of 2026-10-25)
- What practitioners report
3D Secure 2 (3DS2)
3D Secure 2 (3DS2)
3D Secure 2 (EMV 3-D Secure, or 3DS2) is the current card authentication protocol for card-not-present (CNP) payments. Maintained by EMVCo and required by Strong Customer Authentication (SCA / PSD2) for in-scope European payments, it authenticates cardholders in real time using a rich device and behavioural data exchange — enabling most transactions to complete without any visible cardholder interaction while preserving fraud liability shift to the issuer.
How it works
3DS2 routes through four components:
| Component | Operator | Role |
|---|---|---|
| 3DS Server (Requestor) | Merchant / PSP / orchestrator | Packages and sends the authentication request |
| Directory Server (DS) | Card scheme (Visa, Mastercard, Amex, etc.) | Routes the request to the correct issuer ACS based on card BIN |
| Access Control Server (ACS) | Issuer (or issuer's vendor) | Applies the risk model; returns frictionless approval, challenge request, or rejection |
| 3DS SDK | Merchant / PSP | Native iOS/Android library replacing iframe for in-app authentication |
Per Gr4vy's June 2026 merchant guide, the protocol sends 100–150+ data elements per transaction — roughly 10× more than 3DS1 — across device data, behavioural signals, account history, order details, and merchant identifiers (category codes, acquirer BIN).
Data element count is inconsistently cited. Checkout.com and some Gr4vy sections state "more than 100." Netcetera, M2P Fintech, Freenance (fact-checked 2026-09-04), and other Gr4vy sections state "over 150." Discrepancy likely reflects different specification versions (2.2 vs 2.3) or counting methodology. The EMVCo spec is the authoritative source; the field count was not confirmed from EMVCo's own publications in this run. [Gr4vy: https://gr4vy.com/posts/what-is-3d-secure-3ds2-a-complete-merchant-guide-for-2026/]
Frictionless vs challenge
The ACS evaluates submitted data and chooses one of two paths:
Frictionless Flow (3DS2): The ACS authenticates the cardholder without any visible step, using passive risk assessment. Authentication values — ECI plus CAVV/AAV — are returned silently and the merchant gains liability shift for fraud-related chargebacks. Per the PCI Proxy blog, risk factors include device consistency (seen before?), behavioural signals (unusual time/merchant/amount), address matching, account history (account age, prior 90-day transactions), and velocity metrics. [PCI Proxy: https://www.pci-proxy.com/blog-posts/3ds-frictionless-vs-challenge-flow]
Challenge Flow (3DS2): When data is insufficient for frictionless approval, the ACS requests visible cardholder verification. In 3DS2 this renders in an iframe or native SDK — not a full-page redirect — using OTP via SMS or email, in-app push, biometrics, or security questions. Challenge abandonment is a key conversion risk. [PCI Proxy: https://www.pci-proxy.com/blog-posts/3ds-frictionless-vs-challenge-flow]
Frictionless rate benchmarks vary widely and conflict across sources. Ravelin's Global Payments Report 2026 (updated 2026-05-22, measured data) found a global frictionless rate of 58% (62% EU; 54% NA) and stated frictionless approval fell in 76% of countries year-on-year. Freenance (fact-checked 2026-09-04) claims "about 70–80%" without attribution. PCI Proxy cites "commonly cited" 80–85% for merchants sending complete data, also unsourced. Stripe's Japan data (post-mandate April 2025) showed approximately 60% frictionless. Yuno (September 2026, vendor) benchmarks 85%+ as "well-tuned" and 70%+ as "not over-challenging." These figures likely reflect different markets (SCA-mandatory vs optional), transaction mixes, and reference years. [Ravelin: https://www.ravelin.com/blog/ravelin-warns-peak-season-sales-at-risk-as-frictionless-payment-approvals-decline] vs [Freenance: https://freenance.io/fintech/psd2-strong-customer-authentication-eu-2026-sca-3ds-2-explained-exemptions-tra-30-euro-guide/]
SCA exemptions
Under PSD2, merchants and acquirers can request exemptions that skip 3DS entirely. Gr4vy's June 2026 guide (corroborated by Freenance against PSD2 RTS Article 18) lists the main types:
| Exemption | Condition |
|---|---|
| Transaction Risk Analysis (TRA) | Acquirer fraud rate <0.13% → up to €100; <0.06% → up to €250; <0.01% → up to €500 |
| Low Value Transaction (LVT) | Under €30; max 5 consecutive LVT or €100 cumulative since last full SCA |
| Merchant-Initiated Transaction (MIT) | Original CIT was SCA-authenticated; subsequent recurring/COF txns may be exempt |
| Delegated Authentication | Authentication handled by PSP, wallet provider, or merchant |
Ravelin's report (updated 2026-05-22) found 78% of merchants attempt to reduce friction by requesting SCA exemptions — but reported issuers are increasingly rejecting exemption requests as their risk expectations tighten (as-of 2026-05-22). [Ravelin: https://www.ravelin.com/blog/ravelin-warns-peak-season-sales-at-risk-as-frictionless-payment-approvals-decline]
Liability shift
Stripe's documentation (actively maintained, 2026) states successful 3DS authentication does not guarantee liability shift — card network rules and the dispute conditions determine the actual outcome — but successful authentication makes fraud disputes eligible for liability transfer from merchant to issuer. Liability shift does not apply for: non-fraud disputes, unenrolled cards, technical failures, or transactions where 3DS is bypassed via exemption. Liability shift may occur even when the issuer's 3DS provider is down (unenrolled/unavailable scenario), shifting liability to the issuer. [Stripe: https://docs.stripe.com/payments/3d-secure/authentication-flow]
3DS2 vs 3DS1
| Dimension | 3DS1 | 3DS2 |
|---|---|---|
| Launched | 1999 (Verified by Visa) | 2017+ (EMVCo specification) |
| Data elements | ~8–15 | 100–150+ |
| Default flow | Challenge (always visible) | Frictionless (no cardholder interaction) |
| Mobile | Full-page redirect | Native iOS/Android SDK |
| Challenge methods | Static password | OTP, biometrics, in-app push, OOB |
| Soft decline support | No | Yes |
| MIT recurring support | Poor | Yes (with COF/MIT flags) |
| Sunset | October 2022 (all major schemes) | Current standard |
All major card schemes sunset 3DS1 by 15 October 2022. Visa removed fraud liability protection for 3DS1-authenticated transactions; Mastercard penalized acquirers who used 3DS1 on 3DS2-ready merchants and doubled 3DS1 authentication fees. [Checkout.com, 2022-08-08: https://www.checkout.com/resources/blog/the-sunsetting-of-3ds1-and-how-businesses-can-prepare]
Versions
| Version | Key additions | Status |
|---|---|---|
| EMV 3DS 2.1 | First commercial version | Deprecated |
| EMV 3DS 2.2 | Exemptions (TRA), delegated authentication, decoupled authentication | Widely deployed |
| EMV 3DS 2.3 / 2.3.1 | FIDO WebAuthn / SPC, automated OOB transitions, device binding, split-SDK for IoT, enhanced recurring data | Growing; Stripe supports 2.3.0 and 2.3.1 |
3DS 2.3 release year is disputed across sources. The Stripe changelog (2026-01-28 — primary feed source) states "EMVCo published the 3DS 2.3.0 specification in 2021 and the 3DS 2.3.1 specification in 2023." Gr4vy's June 2026 guide states "3DS 2.3 was released in 2023 and 2.3.1 in 2024." Checkout.com says 3DS 2.3 was "first introduced in 2021." The Stripe changelog is the highest-reliability source available. EMVCo publication dates not confirmed directly from EMVCo's own site in this run. [Stripe: https://docs.stripe.com/changelog/clover/2026-01-28/3d-secure-version-support]
"First certified to 3DS 2.3.1" is claimed by both Checkout.com and Netcetera. These may be in different certification categories (3DS Server vs ACS provider) or reflect different timing windows — they cannot both be unconditionally true.
Regulatory landscape
Europe (EEA + UK)
SCA under PSD2 has been fully enforced in Europe since 2022. 3DS2 is the primary SCA mechanism for CNP transactions. Payment Services Directive 3 (PSD3) and the Payment Services Regulation were in late-stage trilogue as of mid-2026, with adoption expected H2 2026 and application ~18 months after publication; PSD3 would maintain and potentially refine the SCA framework and recognise behavioural biometrics as an inherence factor. (Gr4vy June 2026; Freenance September 2026 — regulatory status volatile as-of 2026-10-25.)
Mastercard's Identity Check compliance deadline for EEA acquirers was October 2025 per Gr4vy's June 2026 guide.
Asia-Pacific
Visa and Mastercard set April 2026 as an enforcement and fine-escalation milestone for APAC issuers and acquirers (Gr4vy June 2026 — not independently confirmed against primary scheme sources). India, Japan, Singapore, and Australia have aligned with global 3DS2 standards. Japan mandated EMV 3DS from March 2025 (M2P Fintech, vendor source).
United States
The US does not mandate SCA. 3DS2 is used selectively, driven by individual network rules and fraud pressure rather than regulation. This creates market dynamics where low ecosystem usage reduces issuer investment in the challenge UX, affecting conversion differently from regulated markets. [Gr4vy: https://gr4vy.com/posts/what-is-3d-secure-3ds2-a-complete-merchant-guide-for-2026/]
Mastercard TLID — mandatory from October 2026
From 23 October 2026, merchants must include the Mastercard Transaction Link Identifier (TLID) — a 22-character unique ID returned in the Mastercard authorization response — in every economically related Merchant-Initiated Transaction (MIT) (subscriptions, instalments, unscheduled COF). Formal compliance: 1 December 2026; non-compliance fees: January 2027. Merchants using Adyen Tokenization are handled automatically; merchants managing their own token vaults must implement TLID capture. Visa, Amex, and Discover had not announced equivalent identifiers as of mid-2026. (Adyen Help 2026-03-09; Gr4vy TLID Guide 2026-06-11 — as-of 2026-06-11.)
Conversion impact
The Stripe Sessions 2026 conference talk "The truth about 3DS and conversion" (Amandeep Batra, Head of Payments Performance EMEA; Cip Blujdea, PM Payment Intelligence — Stripe, 2026) provides the richest measured data available. All figures are Stripe platform data and should be treated as vendor-reported.
- US 2024 experiment: Adding 3DS caused overall conversion to fall from 87% to 82% (−5pp). Stripe attributes this to issuers treating a 3DS request as a risk signal and declining authenticated transactions more often — not to the challenge step itself.
- Japan post-mandate (April 2025): Conversion on 3DS transactions held at approximately 93%; dispute rates fell by more than 50%; approximately 60% of 3DS requests went through frictionlessly.
- Stripe's framing: "3DS itself works; poor outcomes in optional markets stem from low ecosystem usage, which reduces issuer investment in the checkout experience."
Challenge method mix (Stripe Sessions 2026, platform data)
- France (mature PSD2 market): ~80% biometrics; ~6% OTP
- US: >50% SMS OTP; ~24% biometrics
Data Only flows (Stripe Sessions 2026, platform data)
Data Only submits a 3DS2 authentication request to the issuer without requesting authentication — sharing device data to improve authorization decisions without a challenge or liability shift.
- Data Only applied to all US transactions indiscriminately: −17 basis points conversion
- Data Only applied to EU transactions over €250: +3.2% conversion uplift
- Effect is strongly market- and segment-dependent.
Network fee incentives (as-of October 2026)
Stripe Sessions 2026 reported: Visa raised its fee for non-authenticated transactions to 7.5 basis points; Mastercard scheduled to follow October 2026. This creates financial incentive to authenticate even in non-SCA markets.
Stripe Authorization Boost (retries)
Stripe's Authorization Boost (retry soft declines) produced a reported +90 basis point conversion uplift in the US. Approximately 1 in 5 completed checkouts is declined by the issuer on the first attempt (Stripe Sessions 2026, platform data).
Merchant optimization benchmarks
All vendor-sourced; treat as directional only.
- Gr4vy (June 2026): well- vs poorly-implemented 3DS2 can differ by 5–15pp authorization rate on affected volume; 3DS2 overall conversion impact estimated under 1–2% vs 5–15% for 3DS1 (figures unsourced within article)
- Gr4vy: frictionless rates of 90%+ described as achievable for well-implemented stacks
- Yuno (September 2026): frictionless <70% on domestic low-risk returning-customer transactions = over-challenging; >85% = well-tuned orchestration
- Decta (August 2025): EU merchants may see 2–3.5% conversion drop from poor 3DS; US merchants up to 15%; avg auth latency >37 seconds (citing Ravelin) contributes to drop-off
Frictionless optimization benchmarks conflict without primary data. Gr4vy claims 90%+ achievable; Yuno sets well-tuned at 85%+. Ravelin measured a global average of 58% (as-of 2026-05-22). Stripe's Japan post-mandate data showed ~60% frictionless. US optional-market data diverges materially from European SCA-mandate markets. Apply benchmarks only within their stated market context.
2026 platform developments
Stripe — Endive API (2026-09-30)
Three related additions to Stripe's Endive API version (2026-09-30), all breaking changes for integrations that branch on three_d_secure.result:
Standalone 3DS API: Merchants can now authenticate a card using 3DS independently of a Stripe payment — for flows where payment creation/processing are handled outside Stripe. Exposes create, submit, retrieve, list, and cancel endpoints under the ThreeDSecure.Authentication resource. [Stripe: https://docs.stripe.com/changelog/2026-09-30/standalone-3ds-api]
data_share_only result enum: New value in three_d_secure.result (alongside attempt_acknowledged, authenticated, challenge_only, exempted, failed, not_supported, processing_error). Indicates Stripe shared device data with the issuer for improved authorization without requesting authentication — no challenge, no liability shift. Breaking change for any code that switches on three_d_secure.result. [Stripe: https://docs.stripe.com/changelog/2026-09-30/3ds-data-share-only]
ECI and exemption fields (added 2026-03-25): The three_d_secure.electronic_commerce_indicator field (ECI value returned by issuer) and three_d_secure.exemption_indicator (exemption type requested, e.g. low_value, transaction_risk_analysis) were added to expose raw protocol-level signals for downstream decisioning. [Stripe: https://docs.stripe.com/changelog/2026-03-25/3ds-eci-exemption-fields]
3DS 2.3.0 and 2.3.1 support (added 2026-01-28): Stripe now supports both EMV 3DS 2.3.0 (EMVCo published 2021) and 2.3.1 (EMVCo published 2023), enabling FIDO WebAuthn / Secure Payment Confirmation, device binding, and enhanced recurring-transaction data fields. [Stripe: https://docs.stripe.com/changelog/clover/2026-01-28/3d-secure-version-support]
Adyen — Authenticate upgrade (2026-09-22)
Adyen launched a major ML-driven upgrade to its Authenticate module, replacing static rule-based authentication with continuous model retraining on network-level signals. Vendor-reported outcomes: +11% authentication rate for Too Good To Go, +12% for Just Eat Takeaway. Adyen claims global frictionless improvement through better risk calibration across their shared merchant network. [Adyen: https://www.adyen.com/press-and-media/adyen-launches-authenticate-upgrade — as-of 2026-09-22]
[!unverified] Adyen's authentication rate uplift figures (+11%, +12%) are vendor-reported for named merchants. Independent verification not available.
EMVCo — "next evolution" announcement (2026-01-30)
EMVCo published an announcement titled "The Next Evolution of EMV 3DS" on 2026-01-30, describing work on further specification updates and forming an agentic commerce task force to address the protocol assumptions that break in AI-agent payment flows. [EMVCo: https://www.emvco.com/emv-technologies/3-d-secure/]
Agentic commerce edge cases
The 3DS2 protocol was designed with a human cardholder assumed to be present and able to respond to authentication steps in real time. Agentic Commerce — AI agents executing purchases autonomously — creates protocol edge cases:
- Out-of-band (OOB) challenge flows (e.g. push notifications to the cardholder's banking app) assume a human can approve; an agent cannot.
- Decoupled authentication (introduced in 3DS 2.2) allows the authentication to complete asynchronously, potentially compatible with agentic flows — but requires explicit prior agreement with the card issuer. Not yet widely deployed.
- Biometric challenge methods require the human cardholder physically present on the device.
- EMVCo formed an agentic payments task force (announced 2026-01-30) to address protocol evolution for AI-initiated transactions. No specification changes had been published as of 2026-10-25. [EMVCo: https://www.emvco.com/emv-technologies/3-d-secure/]
Key terms
| Term | Meaning |
|---|---|
| 3DS Server (Requestor) | Merchant- or PSP-side component that initiates the 3DS2 authentication request |
| ACS | Access Control Server (ACS) — issuer-side component that runs the risk model and responds |
| CAVV / AAV | Cardholder Authentication Verification Value / Accountholder Authentication Value — cryptographic proof of authentication returned by ACS |
| ECI | Electronic Commerce Indicator (ECI) — protocol field indicating authentication outcome degree |
| Frictionless | Authentication completing with no visible cardholder interaction |
| Challenge | Authentication requiring visible cardholder action (OTP, biometrics, push) |
| Liability shift | Transfer of fraud-dispute liability from merchant to card issuer on successful authentication |
| TRA | Transaction Risk Analysis (TRA) — fraud-rate-based SCA exemption tiers |
| LVT | Low Value Transaction — SCA exemption for CNP transactions under €30 |
| MIT | Merchant-Initiated Transaction (MIT) — recurring/COF transaction initiated without cardholder present |
| TLID | Transaction Link Identifier — Mastercard's 22-char ID linking related MIT transactions |
| OOB | Out-of-band — challenge delivered via external channel (banking app push, email) |
| Decoupled auth | 3DS 2.2+ feature allowing async authentication, not requiring cardholder to be present at purchase moment |
| data_share_only | Stripe's new three_d_secure.result value for Data Only flows (no auth, no liability shift) |
Benchmarks (as-of 2026-10-25)
| Metric | Value | Source | Market | Date |
|---|---|---|---|---|
| Global frictionless rate | 58% | Ravelin Global Payments Report 2026 | Global | as-of 2026-05-22 |
| EU frictionless rate | 62% | Ravelin 2026 | Europe | as-of 2026-05-22 |
| NA frictionless rate | 54% | Ravelin 2026 | North America | as-of 2026-05-22 |
| Japan post-mandate frictionless | ~60% | Stripe Sessions 2026 | Japan | 2025 post-mandate |
| Japan post-mandate conversion | ~93% | Stripe Sessions 2026 | Japan | 2025 post-mandate |
| Japan dispute rate reduction | >−50% | Stripe Sessions 2026 | Japan | 2025 post-mandate |
| US 3DS experiment conversion delta | −5pp (87%→82%) | Stripe Sessions 2026 | US | 2024 |
| EU Data Only >€250 conversion uplift | +3.2% | Stripe Sessions 2026 | Europe | 2026 |
| US Data Only indiscriminate | −17bp | Stripe Sessions 2026 | US | 2026 |
| Stripe Authorization Boost uplift | +90bp | Stripe Sessions 2026 | US | 2026 |
| Visa non-auth fee | 7.5bp | Stripe Sessions 2026 | Global | as-of October 2026 |
| Merchants requesting SCA exemptions | 78% | Ravelin 2026 | Europe | as-of 2026-05-22 |
| TRA exemption limit tier 1 | €100 (fraud rate <0.13%) | PSD2 RTS Art. 18 / Gr4vy 2026 | EEA | Regulation |
| TRA exemption limit tier 2 | €250 (fraud rate <0.06%) | PSD2 RTS Art. 18 / Gr4vy 2026 | EEA | Regulation |
| TRA exemption limit tier 3 | €500 (fraud rate <0.01%) | PSD2 RTS Art. 18 / Gr4vy 2026 | EEA | Regulation |
| TLID compliance deadline | 1 December 2026 | Adyen Help 2026-03-09 | Global Mastercard | as-of 2026-06-11 |
What practitioners report
No Reddit data was available for this run (Reddit MCP unavailable). The following practitioner-orientation points are drawn from web sources:
- Gr4vy's June 2026 guide positions 3DS2 orchestration (intelligent exemption routing, multi-PSP retry logic) as the primary merchant lever after basic implementation is in place. Well-implemented stacks achieve frictionless rates of 90%+ according to Gr4vy (vendor claim, unverified). [Gr4vy: https://gr4vy.com/posts/what-is-3d-secure-3ds2-a-complete-merchant-guide-for-2026/]
- Stripe's Sessions 2026 data is notable: in the US (non-mandatory), 3DS degraded conversion, while in Japan (mandatory), it improved authorization and reduced disputes. Conversion impact is fundamentally a function of issuer investment, which is driven by mandate pressure.
- Ravelin's measured data (2026-05-22) found frictionless approval fell in 76% of countries year-on-year — merchants relying on frictionless are facing headwinds even with optimal data submission.
- The Mastercard TLID requirement (effective October 2026) is an immediate operational action item for any merchant running subscriptions or COF payments on Mastercard via a self-managed token vault.