3D Secure 2: Exemptions, Liability Shift and When to Use It illustration

3D Secure 2: When to Use It, Exemptions and Liability Shift

3D Secure 2 is the card industry’s authentication protocol for online payments, and it sits in an uncomfortable spot for merchants: it can cut fraud losses and shift liability, but it can also add friction and lose sales. Getting the balance right is a product decision as much as a risk one. This guide explains how 3D Secure 2 works, when exemptions apply, what liability shift does and does not cover, and how to decide when to trigger it.

What 3D Secure 2 does

When a customer pays online, the merchant sends the issuer a set of data about the purchase and the device, such as the amount, shipping address, account history and device information. The issuer’s risk engine then decides one of two things. In a frictionless flow, it approves the authentication silently and the customer notices nothing. In a challenge flow, the customer is asked to prove who they are, for example with a banking app approval or a one-time code. The original 3D Secure 1 redirected every customer to a separate page, and the card networks ended support for it in 2022, so the current version is the one to build for.

Why the data you send matters

Because the issuer decides based on the data it receives, thin or inconsistent data leads to more challenges. Send complete billing and shipping details, a stable customer identifier, account age and purchase history where you have them, and accurate device data. Low-quality submissions are one of the most common reasons merchants see high challenge rates and abandoned checkouts.

Exemptions and out-of-scope payments

In Europe, the PSD2 rules require strong customer authentication for many online payments, with exceptions. Typical exemptions include low-value payments up to defined limits, payments judged low risk through transaction risk analysis that depends on the provider’s fraud rates, trusted beneficiaries the customer has approved, and certain recurring payments of a fixed amount after the first one. Some payments are outside the rule entirely, including merchant-initiated charges under an earlier agreement and mail or phone orders. Our guide to merchant-initiated and customer-initiated transactions explains the labeling that makes this work.

Losing sales to declines? I help online merchants recover that revenue. Get a free Payment Performance Audit →

Exemptions have trade-offs. A payment authenticated through a full challenge can carry liability protection for fraud chargebacks, while a payment that relies on an exemption may not, so confirm the liability terms with your acquirer before you rely on one.

What liability shift means

When a transaction is fully authenticated through 3D Secure, fraud chargebacks of the relevant type generally become the issuer’s responsibility instead of the merchant’s. That is valuable, but it has limits. It typically covers fraud-coded disputes only, not claims that goods never arrived or were not as described, and the rules differ by network and situation. Do not assume 3D Secure makes chargebacks disappear.

How to decide when to trigger it

Outside regions where authentication is mandatory, you choose when to use it. A practical approach is to apply it selectively:

  • Always where regulation requires it and no exemption applies.
  • On orders your risk score marks as medium or high risk.
  • On product categories or customer segments with a history of fraud disputes.
  • Less often for known returning customers with clean history, where an exemption or frictionless flow is likely.

How to measure whether it is working

Track the frictionless rate, the challenge rate, the challenge success rate and checkout conversion for orders that went through each path, along with fraud and chargeback rates before and after. Compare against a control group where possible. The goal is not the highest authentication rate, it is the best result after counting lost sales, fraud losses and dispute costs.

Common mistakes

Applying 3D Secure to every order, sending incomplete data, ignoring mobile app flows that need the right SDK, and treating the liability shift as a guarantee are the mistakes that appear most often. Also watch your decline codes after launch, since authentication failures can look like ordinary declines in reporting. For more on reading those signals, see our guide to payment decline codes.

3D Secure 2: Key Takeaways

  • 3D Secure 2 lets issuers approve silently or challenge based on the data you send.
  • Better data means fewer challenges and less abandoned checkout.
  • Exemptions reduce friction but may not carry the same liability protection.
  • Liability shift mostly covers fraud-coded disputes, not delivery or quality claims.
  • Trigger it selectively and measure net results, not only fraud reduction.

Frequently Asked Questions

What is 3D Secure 2?

3D Secure 2 is the card industry protocol for authenticating online payments. The merchant shares purchase and device data with the issuer, which either approves silently in a frictionless flow or challenges the customer to prove identity.

Does 3D Secure 2 shift liability for chargebacks?

Fully authenticated transactions generally move liability for fraud-coded chargebacks to the issuer. It usually does not cover claims such as goods not received, and rules vary by network, so confirm the details with your acquirer.

What are common exemptions to strong customer authentication?

Under PSD2, typical exemptions include low-value payments, transactions assessed as low risk, trusted beneficiaries and certain fixed-amount recurring payments. Merchant-initiated payments and mail or phone orders are generally out of scope.

Should merchants use 3D Secure 2 on every order?

Not necessarily. Outside regions that mandate authentication, many merchants apply it selectively to riskier orders and measure the net effect on conversion, fraud and disputes.

Related Reading

About the author

Anatoli Shevtsov

Payments product leader with 20+ years in technology and 15+ years in payments, including product and engineering roles at CyberSource (Visa), Wells Fargo, Chase, NCR and SiriusXM. I work on authorization rate optimization, fraud prevention, chargebacks, network tokenization and payment orchestration, and write here about what I have learned building payment products. Certified Scrum Product Owner (CSPO).

About me · Resume · LinkedIn · Contact

Free Payment Performance Audit

Losing revenue to declined payments?

I help online merchants recover revenue lost to declines, false fraud flags and failed renewals. Tell me a little about your payment setup and I will send back the three biggest fixes I would make across authorization rate, retry logic, tokenization and routing. No cost, no obligation.

Request a free audit →

Free download

Decline Code Cheat Sheet for Merchants

The 15 most common card decline codes on one page: what each one means, whether to retry, and how to fix it.

No spam. Unsubscribe anytime. See the privacy policy.

Leave a Comment