The concept

3-D Secure, now in version 2, is the protocol that inserts an additional check between checkout and approval. Depending on the calculated risk, the issuing bank asks the cardholder for confirmation, through an app or a code, before authorizing.

The most important effect isn't technical, it's about liability. In a successfully authenticated transaction, the fraud dispute becomes the issuer's responsibility, not the seller's. This is what's called the liability shift.

The simpler it is for the customer to understand the offer and move forward, the shorter the distance between interest and purchase.

Russell Brunson Source: concept developed in DotCom Secrets. Paraphrased by the editorial team.

The cost is friction. Every extra step in the checkout drags down conversion, and that's why the sensible decision isn't to turn 3DS on or off for everything, but to apply it by risk tier: suspicious transactions or high-ticket ones go through authentication, the rest go straight through.

How it shows up in practice

You sell a high-value course and notice you're getting a lot of refusals. Your platform offers activating 3-D Secure, which adds a step in checkout, suspicious transactions are challenged and the buyer confirms the purchase through app or bank code. Friction increases, but fraud disappears.

Implementing for everything kills your conversion. The sensible strategy is using 3DS only in risk bands, suspicious transactions or high ticket, letting the rest convert fast. When authentication is successful, fraud responsibility passes to the issuing bank, not you.