3DS2, PSD2, and strong customer authentication
The first version of 3D Secure asked for a password on almost every payment, opened pop-ups, and worked poorly on mobile. Many buyers abandoned checkout. The current version, 3DS2, was built to fix that.
What changes with 3DS2
- Decisions based on data. The bank receives much more payment context (device, history, amount, address) and assesses risk in milliseconds.
- Two possible paths. If risk is low, it approves without asking the buyer anything—the frictionless flow. If something looks unusual, it asks for verification—the challenge flow.
- Modern verification. The challenge is completed in the bank’s app, with fingerprint, face recognition, or an SMS code, without leaving the checkout page.
Why it is mandatory in Europe
The European PSD2 directive requires strong customer authentication (SCA) for online payments. The buyer must confirm their identity using two of these three factors:
- Something they know: a PIN or password.
- Something they have: their phone or card.
- Something they are: fingerprint or face.
3D Secure is how that requirement is met for card payments. If a payment that requires SCA does not go through 3DS, the buyer’s bank may decline it outright.
When authentication is not required
Regulation allows exemptions so low-risk payments are not blocked. The most common ones:
| Exemption | What it means |
|---|---|
| Low value | Payments under €30, subject to cumulative amount and transaction limits |
| Low risk (TRA) | The gateway assesses transaction risk and requests an exemption when it is low |
| Recurring payments | Fixed instalments to the same merchant: the first is authenticated, later ones may not be |
| Merchant-initiated (MIT) | Charges on a stored card that the merchant triggers as agreed with the customer |
| Trusted merchant | The buyer whitelists the merchant with their bank |
| Out of scope | Cards issued outside the European Economic Area and mail order / telephone (MOTO) payments |
Important: requesting an exemption does not guarantee it. The issuing bank always has the final say and may still require authentication.
What your business gains with 3D Secure
- Fewer fraud chargebacks—and you are not left holding the bill. When a payment is authenticated with 3DS, liability for a fraud chargeback (“I did not make this purchase”) shifts from the merchant to the issuing bank. That is liability shift. If the cardholder disputes fraud, the bank cannot charge the amount back to you.
- Fewer declines. Under PSD2, many banks reject European payments that arrive without authentication. Using 3DS helps you avoid losing legitimate sales to an automatic “no”.
- More buyer confidence. Seeing verification from their own bank reassures customers, especially on first purchase or high-value payments.
- A checkout that stays almost invisible. With 3DS2, most low-risk transactions are approved without the buyer doing anything. Friction is reserved for payments that genuinely need it.
- Less internal overhead. Every chargeback avoided is time you do not spend gathering evidence, responding to disputes, and reconciling refunds.
Note: liability shift covers fraud chargebacks. It does not cover disputes for other reasons—such as “product not received”, “service not as described”, or duplicate charges. For those, clear cancellation policies and proof of each sale still matter.
Frequently asked questions
Does 3D Secure make me lose sales?
With the old version, sometimes yes. With 3DS2, most payments are approved frictionlessly and challenges finish in seconds on mobile. Today you are more likely to lose a sale by not using 3DS (and having the bank decline it) than by using it.
Do I need to do something technical to turn it on?
No. Authentication is handled by the payment gateway. Your site, payment link, or virtual terminal only shows verification when the bank asks for it.
What if the buyer fails verification?
The payment does not complete and nothing is charged. The buyer can try again or use another card.
Does it apply to all cards?
Major brands: Visa, Mastercard, American Express, and other compatible schemes. It is not mandatory for non-European cards, but using it still adds protection.
What about Apple Pay or Google Pay?
These methods already include their own authentication (fingerprint, face, or device PIN), so they meet strong authentication without an extra step.
Can an authenticated payment still become a chargeback?
Yes—but if the reason is fraud, liability sits with the issuing bank, not your business. For other reasons (product not received, service not provided), the dispute follows the usual process.
3D Secure at Avirato Payments
At Avirato Payments, 3D Secure 2 is built into all online payments: website, payment links, and virtual terminal. Nothing to configure on your side.
- Authentication when it is needed. Our platform sends the bank the data required so most transactions are approved frictionlessly.
- Exemptions handled for you. We request applicable exemptions (low value, low risk, recurring) so customers take as few steps as possible.
- Protection against fraud chargebacks. Authenticated payments benefit from liability shift to the issuing bank.
- Real support. If you receive a dispute, our team helps you prepare your response.
Want to know how 3D Secure affects your payments or review your current setup? Get in touch and we will go through it with you.