Payment Radar
3D Secure 2.0 Reduces Checkout Friction and Maintains Liability Shift for Merchants
Reducing checkout friction directly improves conversion rates and customer satisfaction. Shifting liability for fraud chargebacks protects merchant revenue. The ability to authenticate in the background reduces operational costs associated with manual fraud reviews.
Payment RadarOriginal source: Payments Journal · linked publisher media; native reuse rights require confirmation 
What changed
3D Secure 2 (3DS2) has replaced the high-friction, redirect-based authentication of 3DS 1.0 with a data-driven protocol that authenticates low-risk transactions in the background and performs in-app authentication for high-risk ones, while maintaining the liability shift for fraud chargebacks to the issuer. This evolution moves away from interrupting shoppers with redirects, instead using over 100 data points to assess risk silently. When a transaction is flagged as risky, the challenge occurs directly within your app or site rather than sending the customer away to a separate page. The core shift is that low-risk purchases are now authenticated without any customer interaction, streamlining the path to purchase while keeping security robust.
Why a business should care
Reducing checkout friction directly improves conversion rates and customer satisfaction. Shifting liability for fraud chargebacks protects merchant revenue. The ability to authenticate in the background reduces operational costs associated with manual fraud reviews. By leveraging these changes, you can maintain strong security without sacrificing the seamless experience customers expect online.
Who it affects
Online merchants, e-commerce businesses, and payment processors accepting card-not-present transactions. Any business processing payments where the physical card is not swiped, tapped, or inserted (online, phone, mail order) stands to benefit from this update.
What to consider doing
Update your payment gateway settings to ensure 3DS2 is enabled and configured for background authentication. Verify that your checkout flow supports in-app challenges to avoid redirects.
Uncertainty and risks
None identified at this time based on current evidence. No specific signals require immediate action beyond standard configuration checks. 3D Secure 2.0 (3DS2) has replaced the high-friction, redirect-based authentication of 3DS 1.0 with a data-driven protocol that authenticates low-risk transactions in the background and performs in-app authentication for high-risk ones, while maintaining the liability shift for fraud chargebacks to the issuer. Merchants should ensure their payment gateways and checkout flows are updated to support 3DS2. They should leverage the increased data points available for risk assessment to optimize their fraud rules, potentially reducing manual reviews for low-risk transactions while maintaining strong security for high-risk ones. Merchants should also verify that their authentication flows are configured to avoid redirects where possible to minimize friction.
Comments