3D Secure

Why it matters

3DS matters because it sits at the trade-off between fraud prevention, approval rate, checkout conversion, issuer liability, and SCA compliance for card-not-present transactions.

How it works

In practice, the merchant initiates the authentication request, transaction data is passed to the issuer through the 3DS rails, and the issuer either approves frictionlessly or requires a challenge such as a one-time code, biometric step, or other authentication method.

Risks and pitfalls

The risk is overusing challenges and damaging conversion, or underusing authentication and increasing fraud exposure. Correct 3DS analysis separates protocol support, issuer behavior, exemption logic, and merchant UX.

Regional notes

For BIST/MOEX/global commerce, 3DS should be interpreted through local issuer support, card-not-present fraud patterns, SCA-like requirements, and the merchant category’s tolerance for checkout friction.

Related terms

Primary sources