Limited time BFCM offer for prevent 2.0
Limited time BFCM offer for prevent 2.0
Limited time BFCM offer for prevent 2.0
Limited time BFCM offer for prevent 2.0
Sep 2, 2026

EMV Liability Shift: Who Pays When a Card-Present Transaction Is Disputed?

rétrofacturation?
Ce n'est plus votre problème.

Recover 4x more chargebacks and prevent up to 90% of incoming ones, powered by AI and a global network of 20,000+ merchants.

Plus de 600 avis
Aucune carte bancaire n'est nécessaire.

En bref :

  • A liability shift moves fraud chargeback costs to the side that did not support chip security.
  • EMV disputes use reason codes such as Visa 10.1 and 10.2 and Mastercard 4870.
  • Liability depends on the actual sale and network rule, not on owning a chip reader.
  • Use acquirer records to confirm the entry method, cardholder check and chip data.
  • Fraud liability protection does not cover delivery or product-quality disputes.
Chargement du lecteur AudioNative de synthèse vocale d'Elevenlabs…

The EMV liability shift is a set of card network rules that decides who pays for some in-store fraud. It looks at the card, the terminal, how the cardholder was checked and the data sent. It does not protect every chip or contactless payment from every chargeback.

Use the rule that fits the actual sale and dispute reason. Owning a chip reader, getting an approval and qualifying for liability protection are three different things.

What Is a Liability Shift?

A liability shift moves the cost of a fraud chargeback from one party to another. Card networks use it to reward the side that supports the safer payment method.

For EMV, it works like this. If a chip card is swiped at a terminal that cannot read chips, counterfeit fraud losses can shift to the merchant’s acquirer. The acquirer usually passes them on to the merchant. In the US, this shift began on October 1, 2015, for card-present sales (Visa’s 2011 announcement).

What Is an EMV Dispute?

An EMV dispute is a fraud chargeback filed under an EMV liability shift reason code. The cardholder says they did not make an in-store purchase. The issuer then argues that the sale did not use the chip or PIN security the card supported.

Common codes are Visa 10.1 (counterfeit fraud) and 10.2 (non-counterfeit fraud), and Mastercard 4870 (chip liability shift). For how criminals target chip cards, see EMV fraud.

Assess Liability by Transaction Scenario

ScénarioWhat to establishWhat not to assume
Contact chip transactionWhether chip data and required verification were processed correctly.A chip-capable terminal proves the disputed sale was chip-read.
Contactless card or walletThe recorded entry method, authentication data, and applicable program.Every tap protects against every claim.
Technical fallbackWhy chip processing failed and how fallback was identified to the network.Every fallback has the same liability result.
Lost or stolen genuine cardThe applicable verification and non-counterfeit fraud rules.Counterfeit-card rules answer the case.
Online purchaseThe relevant remote authentication or token program.In-store chip protection automatically extends online.
Delivery or product complaintEvidence addressing fulfillment or the product description.Fraud liability protection defeats a service complaint.

The card-present fraud guide covers store operations. The counterfeit-card guide covers copied card data and terminal checks.

Read the Network Condition Before Choosing Evidence

Visa’s public merchant guide splits counterfeit EMV fraud (condition 10.1) from non-counterfeit EMV fraud (10.2). For 10.1, a merchant defense needs proof that the chip was read and the required data was sent. See the Visa merchant dispute guidelines.

Mastercard’s public guide lists exclusions and rules for technical fallback. So a blanket “swipe means the merchant always pays” rule does not hold. Ask your acquirer to check the condition and the data sent against the Mastercard chargeback guide.

Public guides explain the framework. Your acquirer should confirm the current rules for the sale’s network, region and date before you accept a liability call.

Collect Evidence About the Disputed Sale

Follow the current case and provider rules

Build an EMV evidence record for this sale

Case and payment

Case and payment numbers, disputed amount and response deadline.

Terminal and entry method

Terminal ID and the sale’s recorded entry method.

Approval and settlement

Approval and settlement records from the acquirer.

Cardholder check and chip data

How the cardholder was checked, and proof of the chip data.

Fallback and service records

Fallback flags, terminal error logs and service tickets, if any.

Completed refund or reversal

Any completed refund or reversal linked to the payment.

Ask the acquirer to explain missing or mismatched data. Do not try to rebuild it from a receipt. Keep sensitive card data out of normal support tickets. Organize the records you may share with a standard evidence structure.

Keep Chip Security Separate From Remote Authentication

EMVCo describes chip technology as one layer in a wider fraud defense, with several ways to check the cardholder. See its EMV chip explanation. Chips make counterfeit cards harder to use. They do not stop every form of payment fraud.

Online 3D Secure and wallet programs have their own rules. Review Apple Pay chargeback rules or Google Pay chargeback rules when a wallet is involved. Do not apply an in-store table to an online sale.

Fix the Processing Cause Alongside the Case

If the records show unexpected fallback or missing chip data, give the terminal or setup issue its own owner. Fixing future sales does not change the disputed one. Buying a new terminal also does not prove the old sale qualified.

Use chargeback representment when the case allows a response and the records support you. You can run supported evidence workflows with Chargeflow’s automated recovery.

Sources and scope

Source notes updated: November 12, 2026. Scope: in-store card payments. EMVCo explains the technology but does not decide a chargeback. Use the network’s regional rules and your acquirer’s case steps for liability. Keep terminal entry-mode and fallback records.

For a live case, keep the rule’s edition or effective date, the section that applies and the provider notice.

Foire aux questions

Does the EMV liability shift cover every chargeback?

No. The EMV liability shift covers certain fraud cases under card network rules. It does not settle delivery, quality, cancellation or other customer disputes.

Does technical fallback always make the merchant liable?

No. Fallback has no single liability result. Check the network, how the sale was coded, why fallback happened and the dispute rules with your acquirer.

Does an approval code prove EMV protection?

No. An approval code alone does not prove EMV protection. Check the entry method, the cardholder check, the required data and the network rule that applies.

PARTAGER CET ARTICLE

rétrofacturation?
Ce n'est plus votre problème.

Récupérez 4 fois plus d'rétrofacturation s et PRÉVENTION jusqu'à 90 % des messages entrants, grâce à l'IA et à un réseau mondial de 20 000 commerçants.

Plus de 600 avis
Aucune carte bancaire n'est nécessaire.
s'abonner

Les dernières actualités sur l'rétrofacturation, la fraude et le commerce électronique, directement dans votre boîte mail. Chaque semaine.

Inscrivez-vous dès maintenant pour ne rien manquer des dernières tendances !
En indiquant votre adresse e-mail, vous acceptez nos Conditions d'utilisation et notre Politique de confidentialité
Schéma composé de lignes pointillées et courbes formant des arcs segmentés, mis en évidence par trois repères en forme de losange bleu situés à gauche.Motif abstrait en forme de grille circulaire, avec des repères en forme de losanges bleus sur un fond moitié noir, moitié blanc.