Liability shift

On this page 8

A liability shift is the card network rule that transfers financial responsibility for fraud chargebacks from the merchant to the card issuer when a transaction was processed with a qualifying security method, most often 3-D Secure authentication for online payments. E-commerce merchants treat it as one of the central incentives in payment security, because it turns an investment in authentication into direct protection against card-not-present fraud losses.

The rule exists because card networks want each party to adopt stronger controls. The party that skips the stronger control carries the loss: if the merchant authenticates the cardholder and the issuer approves, the issuer absorbs a later fraud dispute; if the merchant does not authenticate, the merchant keeps the risk.

How the liability shift works in card-not-present payments

In a card-not-present transaction, the liability shift is triggered by the authentication result that travels with the authorization request. During EMV 3-D Secure (3DS), the issuer’s access control server evaluates the cardholder, either silently through the frictionless flow or with a challenge such as a one-time code or a banking app approval.

The outcome is encoded in an Electronic Commerce Indicator (ECI) and a cryptographic authentication value (CAVV for Visa, AAV for Mastercard). When the acquirer forwards these values and the issuer approves, a later dispute coded as fraud is normally rejected at the network level or cannot be raised against the merchant at all.

The following table summarizes the most common authentication outcomes and their usual effect on fraud liability. Exact rules differ by card network, region and rule version, so merchants confirm them with their acquirer.

OutcomeVisa ECIMastercard ECIUsual fraud liability
Fully authenticated0502Issuer
Attempted authentication0601Usually issuer, with regional exceptions
Not authenticated0700Merchant
Authentication failed or rejectedNot to be authorizedNot to be authorizedMerchant if processed anyway
Typical authentication outcomes and fraud liability

What the liability shift covers and what it excludes

The liability shift covers fraud-coded disputes only, which means claims that the cardholder did not authorize the purchase. It does not protect against service disputes such as goods not received, goods not as described, canceled subscriptions or processing errors, which follow their own chargeback rules and evidence requirements.

This distinction matters for friendly fraud, where a genuine cardholder disputes a real purchase. If the cardholder files the dispute as unauthorized, an authenticated transaction is usually protected; if the same cardholder reframes it as non-delivery, the merchant must still win through chargeback representment with shipping and usage evidence.

Dispute categoryExample claimProtected by liability shift
Fraud, card absentCardholder denies making the purchaseYes, if authenticated
Goods not receivedParcel never arrivedNo
Not as describedItem was counterfeitNo
Recurring cancellationSubscription ended before renewalNo
Processing errorSame order charged twiceNo
Dispute categories and liability shift protection

Exemptions, exclusions and who carries the risk

Under the European PSD2 strong customer authentication rules, many transactions can skip a challenge through an exemption. The general principle is that the party requesting the exemption keeps the liability. If the merchant or acquirer flags a transaction risk analysis or low-value exemption, the merchant usually retains fraud liability even though the payment was smooth.

Several transaction types fall outside 3DS entirely and therefore never carry a shift. Merchant-initiated transactions, such as subscription renewals and delayed charges, rely on the original authenticated setup, and data-only 3DS shares device data with the issuer without producing a liability-bearing authentication value.

FlowTypical useFraud liability
Challenge or frictionless 3DSStandard checkoutIssuer
Issuer-applied exemptionIssuer chooses not to challengeIssuer
Acquirer or merchant exemptionLow-risk or low-value ordersMerchant
Merchant-initiated transactionRenewals, split shipmentsMerchant
Data-only 3DSData sharing without authenticationMerchant
No 3DSMarkets without mandatesMerchant
Who usually bears fraud liability by flow

The liability shift is a contractual allocation of loss, not a fraud control in itself. Controls such as fraud screening, the address verification service, CVV checks and velocity checks reduce the probability of fraud, while the shift decides who pays when fraud still happens.

For this reason, mature merchants combine both layers. A fraud risk scoring engine decides which orders deserve authentication, which can be exempted and which should be declined, and 3DS then provides loss protection on the orders that pass through it. Address and CVV matches improve approval decisions but do not shift liability on their own.

Card-present payments have a parallel concept: the EMV chip liability shift, under which the party with the less secure technology, such as a magnetic stripe terminal accepting a chip card, bears counterfeit fraud losses.

Using the liability shift in checkout strategy

Authentication is not free. Every challenge adds checkout friction, and some issuers still produce timeouts or failed challenges that end in abandoned carts. Merchants therefore treat the shift as an optimization problem: authenticate where the expected fraud cost exceeds the expected conversion loss, and request exemptions where it does not.

The decision table below shows a common approach. Thresholds depend on margin, product resale value and the merchant’s fraud-to-sales ratio.

SituationRecommended approachReason
High-value, resellable goodsAlways request 3DSFraud loss would exceed margin
Low-value digital ordersExemption with screeningFriction costs more than fraud
New customer, risky signals3DS with challenge preferenceShifts liability on doubtful orders
Trusted returning customerFrictionless 3DS or exemptionKeeps checkout fast
Subscription setupAuthenticate the first paymentSupports later merchant-initiated charges
Decision table for authentication strategy

Common misconceptions and failure modes

Most failed protection claims come from technical or rule details, not from fraud itself. Teams that review their dispute outcomes usually find the following patterns:

  • Assuming every 3DS attempt shifts liability, although failed, rejected or data-only results do not.
  • Losing authentication data between the 3DS server and the authorization request, so the issuer never receives the ECI and authentication value.
  • Authorizing a different amount or too long after authentication, which can invalidate the protection.
  • Expecting protection against service disputes, which remain the merchant’s responsibility.
  • Ignoring network monitoring programs, since merchants with excessive fraud levels can lose the shift for fraud disputes.

A plain-language summary

When a stolen card is used online, someone must pay the money back to the real cardholder. Normally that is the shop. A liability shift means the bank that issued the card pays instead, as long as the shop asked the bank to check the buyer first, for example with a code sent to the phone.

Think of it like a landlord who agrees to cover burglary damage only if the tenant locks the door. If the shop does the extra check, the bank carries the fraud risk. If the shop skips it, the risk stays with the shop. The deal only covers stolen cards, not complaints about late or wrong deliveries.

An example from practice

An online electronics retailer selling laptops and phones notices that fraud chargebacks have reached 0.6 percent of card sales, mostly on orders above 500 euros shipped to new addresses. Its payment team routes every order through a risk score and sends all orders above 250 euros, plus any risky smaller order, through EMV 3-D Secure, while low-risk accessories under 30 euros use the low-value exemption.

Within three months, most high-value orders authenticate frictionlessly and only about one in five sees a challenge. When a batch of fraudulent laptop orders later turns into disputes, the authenticated ones are blocked as issuer liability, and the retailer pays only for the small exempted orders. Net fraud losses fall by more than half while conversion drops by less than one percentage point.