Library · Chargebacks · How to run this
3-D Secure
3-D Secure (EMV 3DS2) is authentication at checkout. Visa brands it Visa Secure; Mastercard brands it Identity Check. A successful authenticated transaction can shift fraud liability to the issuer on qualifying chargebacks. It does not fire when a dispute is filed. It is not an alert network.
Pair: 3-D Secure.
It does not win consumer disputes: not received, not as described, cancelled recurring. Failed or attempted 3DS is not a liability shift. Keep AVS/CVV.
Cost shape: per-attempt or per-auth fee from the gateway/acquirer, plus conversion loss on challenged auths. The tax is often the drop, not the fee. There is no public network retail price.
Enrollment is per MID. A retry onto a MID that is not 3DS-enrolled can undo the shift. Whether the conversion tax is smaller than the fraud dollars 3DS actually moved is a different job: Place 3DS only when the tax pays.
Not RDR, Ethoca, CDRN, or Order Insight.
Procedure
- Enroll 3DS on the MID that will authenticate.
- Place it in the cascade on purpose (amount, BIN, risk) — that is orchestration.
- Measure conversion drop separately from CB fraud drop.
- Keep AVS/CVV. 3DS is not a substitute.
Failure modes
- Turning on 3DS on one MID and retrying declines onto a MID that is not enrolled.
- Expecting 3DS to win ‘not received’ or ‘not as described.’
- Counting attempted/failed 3DS as a liability shift.
Worked example
None on this page yet. When one lands it will be a real case: what broke, the number, and what changed. Not a composite.
Glossary
- 3DS2
- EMV 3-D Secure 2 (Visa Secure / Mastercard Identity Check). Successful authentication can shift liability to the issuer on qualifying fraud chargebacks. It does not apply to consumer disputes.
Work with us — We run this job on your accounts. Services
FAQ
- Does 3DS win not-received or not-as-described?
- No. Liability shift is for qualifying fraud codes after successful authentication. Consumer disputes are a different family.
- Is a 3DS attempt enough?
- No. Failed or attempted 3DS is not a liability shift. A retry onto a MID that is not enrolled can undo the shift.