What is 3-D Secure — and why it's not extra friction but a transfer of liability

Everyone treats 3-D Secure as an annoying speed bump on the way to checkout. One more screen, one more SMS code, and some people drop off.
Now the surprising part. 3DS isn't really about protecting your customer. They're protected anyway: if the payment wasn't theirs, their bank gives the money back. 3DS settles a different question — whose loss it is. And by default, the loss is yours.
What the customer sees
You submit a payment, and the bank that issued the card decides whether to ask for confirmation or wave it through. If it asks, the person sees a familiar screen: a code from a message, a password, or a fingerprint in their banking app.
They may recognize it as Visa Secure, Mastercard Identity Check or American Express SafeKey — the same thing under different brand names.
Important: that screen is drawn by the bank, not by you. You don't choose the code and you never see it. Conceptually it's a second factor, only issued by the bank rather than by you, and tied to one specific payment.
Who pays if the card turns out to be stolen
This is the whole point, and it's worth spelling out.
Without 3DS: the customer tells their bank "that wasn't me", the bank opens a dispute, and the money plus a non-refundable fee leave your balance. You try to prove the product was delivered — and usually lose, because you can't prove the cardholder was the one who paid.
With 3DS passed: the liability shift rule kicks in. Stripe's own definition says it plainly — 3DS protects businesses from liability for fraudulent card payments. The bank verified the identity, so the bank carries the loss.
There's a second, less known effect. Card networks send early warnings about suspicious payments, and by Stripe's estimate 80% of those turn into a dispute if you do nothing. But when a payment is covered by liability shift, the provider automatically attaches the 3DS data as evidence, and the dispute stops being an automatic loss.
How the dispute itself works and why it's expensive: what is a chargeback.
When 3DS is mandatory, and when it's your call
There's a regulation called SCA — strong customer authentication. It's been in force since September 14, 2019 as part of the European PSD2 directive in the European Economic Area, with similar rules in the UK, India, Japan and Australia.
For payments that fall under it, 3DS isn't optional: without confirmation the bank simply declines.
Elsewhere it's optional — a tool you switch on yourself to cut fraud. A sensible setup for a beginner: not for everyone, but by rules — large amounts, cards from another country, suspiciously repeated attempts.
What it costs you
Honestly: conversion. Every extra screen loses people — someone doesn't get the SMS, someone forgets the password, someone just closes the tab.
That's why the rules include exemptions: small amounts, recurring subscription charges, trusted merchants can go through without a prompt. Payment providers can request those exemptions automatically.
And there's a reverse effect people forget: in countries where 3DS is supported, it lowers decline rates. The bank sees a verified identity and is happier to approve a payment it would otherwise treat as risky.
What 3DS demands from your code
Here lives the most common technical mistake, and it's not about security — it's that the payment stops being a single step.
It used to be simple: send card details, get success or decline. With 3DS there's a third outcome: "action required". At that moment the payment is neither paid nor declined — it hangs, waiting for the person to finish confirmation with their bank.
What follows from that:
- your frontend must be able to show that step — open the bank's window and wait for the return. Hosted checkout pages and official components do this for you; a hand-rolled form doesn't;
- you can't decide the final status from what came back to the browser. People close the tab right after confirming. The only reliable source of truth is a notification to your server;
- hence the classic bug: money charged, order never created. The frontend didn't wait and the server wasn't listening.
The symptom that gives it away: payments sitting in "action required" for months while customers insist they paid.
Why does my subscription charge fail with "authentication required"?
Because the customer isn't on your site at that moment and the bank wants confirmation. A recurring charge runs with nobody there to ask. The fix is saving the card with consent for future charges at first checkout — then later charges go through as trusted. More on failures like this: why my payment is declined.
Can I just turn 3DS on for everything and forget it?
Technically yes, and fraud will nearly vanish. So will a slice of revenue, lost to friction. For a first product it's smarter to enable it by rules, watch the numbers for a month, and decide from data.
Do I need this if I only sell in one country?
Check your country's regulation first. If it mandates confirmation, the question is settled. If not, the guide is simple: the bigger your average order and the easier your product is to resell, the sooner it's worth turning on.
Haven't set up payments yet? Start with how to take your first payment.
The AI Architect 2027 course: step by step from computer basics to your own app and first customers. 543 short lessons on your phone.





