Glossary
Liability shift
Liability shift is the card schemes' rule that, when a payment was authenticated through 3-D Secure, or the issuer approved it under certain exemptions, the issuer rather than the merchant bears the loss if the cardholder later disputes it as fraud. It covers fraud reason codes only: a dispute for goods not received or not as described still lands on the merchant. Where the issuer did not take part in authentication, or the attempt failed, liability stays with the merchant.
When it applies
A completed 3-D Secure authentication, frictionless or challenged, with the authentication value carried in the authorisation; some exemptions, such as issuer-approved low-risk transactions in the EU, keep the shift, while merchant-requested exemptions move liability to the merchant. Merchant-initiated transactions after an authenticated first payment inherit a protected position in most scheme rules.
What it does not do
It does not prevent the chargeback from being filed or counted in monitoring programmes; it decides who pays. It does not cover non-fraud disputes. And an authentication that failed or was abandoned is not a shift: the payment should usually not be submitted at all.
On the platform
Tranzify’s hosted checkout runs 3-D Secure where the rule or the issuer asks, passes the authentication result into the authorisation, stores it with the payment, and shows in the trace whether a disputed payment was authenticated, which is the first fact a merchant needs when a fraud chargeback arrives.
Updated: 2026-11-08