3D-Secure lets the issuer verify the cardholder at checkout, and a successful authentication can move liability for fraud-coded disputes to the issuer. It does not cover item not received or not as described claims, and exemption-based approvals don’t earn the shift. This one-pager shows where the protection ends and how to step up only where risk warrants it.
What’s inside:
- How EMV 3DS works, from order and device data to a frictionless approval or a challenge
- A reason-code table showing which Visa and Mastercard disputes shift liability and which stay with you
- The conversion tradeoff: why challenging too broadly costs sales and too narrowly leaves exposure
- Four ways to get more from 3DS: a fuller risk picture, step-up only where needed, testing before you change, and coverage for what 3DS leaves out
- Three questions to ask your team about which orders go to 3DS, abandonment by issuer, and chargebacks outside the shift
