On this page
- How it works
- Challenge types
- What triggers a challenge (ACS risk factors)
- Merchant challenge preference signals
- Conversion impact
- Soft decline and step-up retry
- SCA Exemptions and Liability Shift
- Regional variation
- Protocol and changelog notes
- Key terms
- Benchmarks (as-of 2026-10-24)
- Contradictions
- What practitioners report
Challenge Flow
Challenge Flow
The Challenge Flow is the active cardholder authentication path in EMV 3D Secure 2 (3DS2) transactions. When the issuer's ACS (Access Control Server) (ACS) cannot silently approve a transaction via Frictionless Flow — because the transaction exceeds its risk tolerance — it requires the cardholder to supply additional proof of identity before the payment can proceed. The two paths together define how 3D Secure 2 (3DS2) balances fraud prevention against conversion.
How it works
EMVCo describes the core distinction: in the Frictionless Flow the issuer approves without challenging the cardholder based on real-time risk assessment; in the Challenge Flow the issuer judges a transaction high-risk or requires cardholder confirmation, and the cardholder must supply additional information before the transaction can proceed (EMVCo Knowledge Hub, 2025-08-21).
The flow is controlled by the issuer's ACS, not the merchant. Stripe's documentation states: "Stripe can't guarantee your preference because the issuer determines the ultimate authentication flow" (Stripe 3DS Authentication Flow docs). The ACS returns transStatus: C when it requires a challenge; the PaymentIntent transitions to requires_action on Stripe, and the cardholder is presented with a challenge UI.
The challenge appears inline in checkout via iframe or native SDK, not as a full-page redirect. For web, Stripe states card issuers are required to support challenge content at these iframe sizes: 250×400, 390×400, 500×600, 600×400, and full screen; the sandbox attribute must not be used because some issuer implementations fail if sandboxed (Stripe 3DS Authentication Flow docs). The authentication process timeout must be at least 5 minutes to remain compliant with SCA regulation; a value under 5 minutes results in an Android error (Stripe 3DS Authentication Flow docs).
Challenge types
Four challenge UI types exist in the EMV 3DS protocol. Stripe's iOS, Android, and React Native SDKs support: Out of Band (OOB), One Time Passcode (OTP), Single Select, and Multi Select (as-of 2026-10-24; Stripe 3DS Authentication Flow docs). Adyen's native 3DS2 integration additionally surfaces: text, app single select followed by text, HTML OOB, plus edge cases such as empty CRes and CRes timeout (Adyen 3DS Authentication-Only docs, API v70, as-of 2026-10-24).
EMVCo's White Paper Phase 2 also adds WebAuthn (FIDO-based), Secure Payment Confirmation (SPC, a W3C standard built on WebAuthn), and Decoupled Authentication as distinct authentication paths (EMVCo Knowledge Hub, 2025-08-21).
Decoupled Authentication is a sub-path where authentication happens separately from the payment flow. EMVCo describes it as serving as a fallback when the primary method is unavailable and enabling merchant-initiated authentication when the cardholder is not present (e.g., MOTO, recurring payments, split shipments). The ACS uses an RReq message to return results rather than the CReq/CRes flow used in standard challenges. gr4vy notes EMV 3DS 2.3 adoption is growing but not yet universal (as-of 2026).
In terms of real-world challenge type distribution: Stripe's 2026 session data reports that in the US, over half of challenges are OTP sent by SMS and 24% use biometrics; in France, which enforces 3DS on almost all transactions, approximately 80% use some form of biometrics and 6% use OTP (volatile, as-of 2026; Stripe Sessions 2026 speaker data).
What triggers a challenge (ACS risk factors)
The ACS decides which path a transaction takes; the merchant does not control the outcome directly but controls data quality (PCI Proxy, 3DS Frictionless vs Challenge Flow). Challenge triggers documented across sources include:
- Unusual transaction amounts
- Billing/shipping address mismatches
- Unfamiliar or untrusted devices
- New customers with no transaction history (short account age, few successful transactions in past 90 days)
- High-risk merchant categories
- Incomplete, stale, or inaccurate data from the merchant (missing device fingerprints, outdated billing address, absent contact information)
- High card velocity in a short window
- IP geolocation inconsistency with billing address
(Sources: PCI Proxy; gr4vy 2026; Shuftipro 2026)
Shuftipro (2026) notes that inaccurate data — such as an outdated autofilled billing address — can satisfy a mandate's fields check while still raising the issuer's risk score, with no error surfaced to the merchant.
Sending a no-challenge request with thin or inaccurate data can make the issuer more suspicious and may trigger the very step-up the merchant wanted to avoid (Acquired.com, 3DS Challenge Preference).
EMV 3DS2 can transmit over 150 data elements to the issuer; richer data payloads produce higher frictionless rates (Yuno, 2026).
Risky or ambiguous transactions will be challenged regardless of integration quality; there is no way to bypass risk-based authentication entirely (PCI Proxy).
Merchant challenge preference signals
Merchants can signal a challenge preference via the challengeIndicator field, but the ACS is not bound. Adyen's API supports four values: noPreference, requestNoChallenge, requestChallenge, requestChallengeAsMandate; Adyen also supports a challengeCancel field to notify the ACS that authentication was cancelled (Adyen 3DS Authentication-Only docs, API v70). Stripe exposes request_three_d_secure with any (preference for frictionless) and challenge (preference for challenge); the issuer's final decision overrides the preference (Stripe 3DS Authentication Flow docs).
The 3DS Requestor Challenge Indicator 04 ("challenge requested: mandate") is used for regulated use cases where a challenge is required (Acquired.com). The most common 3DS misconfiguration is hard-coding "challenge mandated" to every transaction regardless of risk; Yuno (2026) describes setting challenge preference to "no preference" as better but suboptimal, and per-transaction dynamic policy using real-time risk scoring as the mature approach.
Conversion impact
Challenge flow is the primary source of 3D Secure 2 (3DS2) conversion loss, with abandonment estimates varying across sources:
- gr4vy (2026) cites "industry data" suggesting 10–30% of customers abandon at the challenge step
- PCI Proxy cites "industry benchmarks" at 10–15%
- Acquired.com's illustrative model assumes 18% abandonment (82% challenge completion)
(All three figures lack primary source attribution — see Contradictions)
Ravelin's 2026 3DS report found frictionless rates declined globally, with 28 of 37 countries registering declining or plateauing frictionless rates (~76%); 78% of merchants now use exemptions, up from the prior year (as-of 2026; Ravelin Global Payments Report 2026 – Authentication).
Ravelin 2026 country 3DS success rates (as-of 2026): UK 95% · Italy 93% · Netherlands 92% · France 91% · Ireland 91% · United States 88% · Germany 87% · Spain 81% · Portugal 77% · Sweden 76% · Denmark 75% · Greece 74% · Brazil 36% (Ravelin 3DS Rates 2026).
Stripe's 2026 session data (2024 US test): requesting 3DS on some transactions lowered conversion from 87% to 82%; some US issuers treat a 3DS request as a fraud signal and decline more often (as-of 2024; flagged as potentially superseded).
Japan's April 2025 mandate: conversion on 3DS transactions remained steady at ~93%; ~60% frictionless; dispute rates fell >50% (Stripe 2026 session data, speaker-reported; as-of mid-2025).
Soft decline and step-up retry
When a merchant requests frictionless and the issuer insists on a challenge, the result is a Soft Decline. Without step-up retry logic, the transaction fails and liability does not shift to the issuer (Yuno, 2026).
Worldline documents the soft decline flow as: (1) merchant requests frictionless; (2) issuer returns statusCode=2 with error code 40001139; (3) platform redirects customer to issuer for 3DS; (4) platform receives result and processes with acquirer; (5) customer redirected to merchant returnUrl.
Many integrations omit step-up retry logic because it was out of scope for the original compliance build; the absence means soft declines result in lost sales (Yuno, 2026).
Stripe's Authorization Boost re-authenticates issuer declines via 3DS retries and resubmits them; Stripe reported 90 basis points of US conversion uplift and noted about one in five checkouts is declined on the first try (Stripe Sessions 2026, as-of 2026).
SCA Exemptions and Liability Shift
Successful 3DS authentication — frictionless or challenge — moves fraud chargeback liability to the issuer. When the merchant requests an SCA exemption (TRA, low-value, etc.), liability stays with the merchant even if authentication succeeds (Acquired.com).
Transaction Risk Analysis (TRA) exemption thresholds under EBA PSD2 RTS (as-of 2026; subject to PSD3/PSR revision): acquirer fraud rate below 0.13% → transactions up to €100; below 0.06% → up to €250; below 0.01% → up to €500. TRA eligibility depends on the acquirer's fraud rate, not the merchant's alone (gr4vy, 2026; Yuno, 2026). Low-value exemption: transactions under €30, capped at 5 consecutive exemptions or €100 cumulative since the last full SCA or challenge (gr4vy, 2026).
Issuer-applied exemptions surfaced in Adyen's API (as-of 2026-10-24): lowValue, secureCorporate, trustedBeneficiary, transactionRiskAnalysis; reasons for no authentication required include: MerchantInitiatedTransaction, MOTO, POS, AcquirerNotInEEA, IssuerNotInEEA, NonFinancial (Adyen 3DS Authentication-Only docs, API v70).
Regional variation
Europe/UK: Strong Customer Authentication (SCA - PSD2) is fully enforced. Unauthenticated card-not-present transactions are generally declined unless an exemption applies. PSD3/PSR was in late-stage negotiation as-of 2026, with adoption expected in H2 2026 and application 18 months after publication (gr4vy, 2026; volatile). Visa charges 7.5 bps more on non-authenticated European transactions; Mastercard adding a similar fee (Stripe 2026 session, as-of 2026; rates volatile). EEA Mastercard Identity Check compliance deadline: October 2025; additional Mastercard tracking mandates: October 2026 (gr4vy, 2026). Ravelin 2026: 51% of British merchants want PSD2 SCA abolished in the UK.
Mastercard 3DS Data Mandate (effective 2026-07-01): Four required fields for all Mastercard Identity Check card-not-present transactions: (1) cardholder name, (2) billing address line 1, (3) at least one contact method (email, mobile, home phone, or work phone), (4) device identifier (browser IP or device ID) (Shuftipro 2026, citing Mastercard; as-of 2026-07-01).
United States: SCA is not mandated. 3DS2 used selectively for high-risk transactions. Visa's DCAP program offers ~5 bps off interchange for eligible transactions that send billing address, email, and IP over 3DS; Apple Pay, Google Pay, and merchant-initiated transactions are excluded (Stripe 2026 session; volatile, as-of 2026). Ravelin 2026: US 3DS success rate saw a "significant leap of 47%" year-on-year (methodology and metric unclear).
Asia-Pacific: Visa and Mastercard set April 2026 as the enforcement and fine-escalation milestone. India, Japan, Singapore, and Australia have aligned to global 3DS2 standards; India additionally runs its own SCA-equivalent rules through the Reserve Bank of India (gr4vy, 2026).
Protocol and changelog notes
Stripe supports 3DS up to v2.3.1; major card brands no longer support 3DS 1 (Stripe docs). Stripe changelog 2026-01-28 (API version clover): added support for importing 3DS authentication results using protocol versions 2.3.0 and 2.3.1 (as-of 2026-01-28). Stripe changelog 2026-09-30 (API version endive): added data_share_only as a new three_d_secure.result enum value; prior to this, Data Share Only authentications were indistinguishable from unauthenticated transactions (three_d_secure: null); breaking change for integrations branching on this field (as-of 2026-09-30). The same changelog also added a Standalone 3DS API and surfaced network ECI on card charges.
Authentication cryptogram validity periods (Adyen, API v70, as-of 2026-10-24): American Express = 45 days; CUP = 90 days; Mastercard = 95 days; Visa = 90 days.
EMVCo message extensions defined in the White Paper: Device Acknowledgement, Bridging, Attribute Verification, Travel Industry, Payment Token (EMVCo Knowledge Hub, 2025-08-21).
Key terms
| Term | Meaning |
|---|---|
| ACS | Access Control Server — issuer's component that decides frictionless vs challenge |
| transStatus: C | ACS response indicating challenge required |
| transStatus: Y | Authentication successful (frictionless or challenged) |
| transStatus: A | Authentication attempted but cardholder not verified |
| transStatus: N | Not authenticated / transaction denied |
| challengeIndicator | Merchant field to signal challenge preference; ACS is not bound |
| OOB | Out-of-Band — authentication via banking app push notification |
| Decoupled Authentication | Authentication performed separately from the payment flow; used for MOTO, 3RI, or as fallback |
| Soft Decline | Issuer rejects frictionless request and requires a challenge; transaction fails if no step-up retry |
| TRA | Transaction Risk Analysis — SCA exemption based on acquirer fraud rate thresholds |
| Data Share Only | 3DS mode where cardholder data is shared with the issuer without a challenge (Stripe: new enum value as-of 2026-09-30) |
| 3RI | 3DS Requestor-Initiated — merchant-initiated transactions (recurring, MOTO) |
Benchmarks (as-of 2026-10-24)
- Ravelin 2026: 28 of 37 countries have declining or plateauing frictionless rates
- Challenge abandonment: gr4vy "10–30%" · PCI Proxy "10–15%" · Acquired.com model "~18%" (all three lack primary source attribution)
- Country 3DS success rates (Ravelin 2026): UK 95% · Italy 93% · France 91% · US 88% · Germany 87% · Spain 81% · Brazil 36%
- Yuno frictionless benchmarks (vendor, no methodology): <70% = over-triggered · >85% = well-tuned
- Stripe 2026 session (US test, 2024): 3DS on some transactions — 87% → 82% conversion
- Japan post-mandate (April 2025, mid-2025 data): 3DS conversion ~93%; ~60% frictionless; disputes fell >50%
- Stripe Authorization Boost: ~90 bps US conversion uplift reported (as-of 2026; Stripe Sessions 2026)
Contradictions
What practitioners report
Reddit stream unavailable (MCP not in this session). No practitioner counter-narratives captured this run.