Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
3-D Secure is the card-scheme protocol that lets an issuer authenticate a cardholder during an online purchase, carrying risk data between merchant, acquirer, and issuer and shifting fraud liability.

What Is 3-D Secure?
3-D Secure is the messaging protocol that lets a card issuer check who is behind an online purchase before it is authorised. The name comes from its three domains: the acquirer domain where the merchant sits, the issuer domain where the cardholder’s bank sits, and the interoperability domain of scheme infrastructure that connects them. You meet it as Visa Secure, Mastercard Identity Check, or an in-app approval from your banking app.
The first version, launched by Visa around 2001, redirected the shopper to a bank-hosted page and asked for a static password. It was unpopular for good reason: the page looked like a phishing site, the password was forgotten constantly, and abandonment rates on checkout pages rose sharply wherever it was switched on.
EMVCo’s 3-D Secure 2, published from 2016 and now at version 2.3, changed the model. The merchant’s 3DS Server sends an authentication request containing up to a hundred or so data elements: device fingerprint, browser characteristics, shipping and billing address, account age, purchase history, and the amount. The issuer’s Access Control Server scores that evidence and takes one of two paths.
Version 2 also supports app-based and in-app purchases properly, carries a decoupled authentication option for delayed approval, and allows merchants to request an exemption rather than a challenge.
3-D Secure authenticates the person, not the card data. It makes stolen card numbers far harder to monetise at checkout, which pushes card-not-present fraud towards merchants with no authentication, towards account takeover of accounts that already hold a trusted card, and towards social engineering of the shopper during the challenge itself.
Successful authentication usually moves chargeback liability for fraud from the merchant to the issuer. That liability shift, not the security benefit on its own, is what persuades most finance directors to deploy it. It does nothing for friendly fraud, where the genuine cardholder disputes a purchase they made, which belongs to chargeback fraud controls instead.
Attackers adapt. Real-time phishing kits proxy the genuine 3DS challenge to the victim and relay the code within its validity window, which is why SMS one-time passcodes are being retired in favour of app-bound approval with transaction details displayed.
In the UK, strong customer authentication is law rather than a scheme preference. The Payment Services Regulations 2017 and the FCA’s SCA-RTS require two independent elements from knowledge, possession, and inherence for most electronic payments, and the FCA’s enforcement date for e-commerce card payments was 14 March 2022. 3-D Secure 2 is simply the mechanism most of the market uses to satisfy it. The rules also define exemptions that a merchant may request: low-value payments, transaction risk analysis below defined fraud rate thresholds, trusted beneficiaries, and recurring transactions of a fixed amount.
Turkey arrived at near-universal 3-D Secure earlier and by a different route. Card scheme and banking rules make the merchant or acquirer carry the loss on unauthenticated domestic e-commerce transactions, so Turkish acquirers effectively require 3-D Secure on card-not-present payments, with the Interbank Card Centre (BKM) operating the domestic switch and BDDK’s information systems rules requiring strong authentication for electronic banking. The practical difference for a UK merchant is that the Turkish market has no broad equivalent of the UK exemption framework to lean on: you should expect a challenge rate closer to the issuer’s default than to your own optimisation targets, and you should test the challenge flow on Turkish issuers specifically.
Treat the 3DS Server as part of your payment attack surface. The data you send drives the issuer’s decision, so an integration that omits the optional risk fields will produce more challenges and more abandonment than one that populates them accurately. Common failure modes are worth testing directly: a challenge window that does not render on mobile, a merchant that accepts an authentication result without verifying the cryptogram, and a fallback path that quietly processes the payment without authentication when the directory server times out.
Authentication also sits alongside, not instead of, PCI DSS obligations and your own fraud detection scoring. At Privia Security, we test payment flows end to end as part of our web application security services, including the exemption logic merchants use to keep conversion high.
No. It authenticates the cardholder at checkout, so it is effective against the use of stolen card numbers on merchants that support it. It does nothing about fraud committed from a compromised but genuine account, about friendly fraud where the real cardholder disputes a purchase, or about merchants and regions where authentication is not applied. Treat it as one control among several.
Because the issuer approved them through the frictionless flow. Version 2 sends a large set of risk signals with the authentication request, and when the issuer’s scoring is comfortable it returns an authentication result without prompting the shopper. Merchants can also request a defined exemption, such as transaction risk analysis or a low-value payment, which removes the challenge while keeping the authentication record.
The protocol is not named in law, but strong customer authentication is required by the Payment Services Regulations 2017 and the FCA’s SCA-RTS, fully enforced for e-commerce card payments from 14 March 2022. 3-D Secure 2 is the standard way the card industry meets that requirement, so in practice UK online card payments are authenticated through it unless a defined exemption applies.
A payment authenticated successfully through 3-D Secure normally shifts liability for fraud-related chargebacks from the merchant to the issuer. If you request an exemption and skip authentication, you usually keep that liability yourself. The economics are straightforward: exemptions improve conversion but move risk onto your own balance sheet, so model the trade-off against your actual fraud rate.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.