Visa Reason Code 10.1: EMV Liability Shift — Counterfeit Transaction

What Visa Reason Code 10.1 Means

Visa reason code 10.1 is titled EMV Liability Shift — Counterfeit Transaction. It sits in Visa's Fraud category and applies exclusively to card-present transactions. When this code is filed, the cardholder's issuer is asserting that a counterfeit copy of the cardholder's chip card was used at your terminal — and that your failure to properly read the EMV chip is why the fraud succeeded.

The EMV liability shift, which Visa implemented in 2015, transferred responsibility for counterfeit card fraud from issuers to merchants who had not upgraded to chip-capable terminals. If the transaction was swiped on a magnetic stripe instead of processed via chip read, and the card turns out to be counterfeit, you bear the loss. The logic: a chip read would have detected the counterfeit and declined the transaction.

Cross-Network Equivalent Codes

Common Trigger Scenarios

• Magnetic stripe swipe on a chip card. The most common trigger. A chip-enabled card was swiped instead of dipped — whether because the terminal lacked a chip reader or the clerk swiped out of habit. If the card was counterfeit, liability falls on the merchant.
• Fallback processing. The chip reader malfunctioned or showed an error, so the transaction fell back to a magnetic stripe swipe. Legitimate in some cases, but it removes EMV protection and transfers liability for any resulting counterfeit fraud.
• Terminal not yet EMV-upgraded. Merchants still running legacy mag-stripe-only terminals after the 2015 liability shift deadline are fully exposed to 10.1 chargebacks on every counterfeit transaction.
• Manual key entry. The transaction was manually keyed rather than chip-read, removing all EMV authentication. Even if a chip card was physically present, manual entry forfeits the EMV liability protection.
• Skimming at the point of sale. A criminal installed a skimmer at your terminal, capturing card data used to create counterfeit cards. While you are a victim too, Visa still holds the non-chip-reading merchant liable for the resulting chargebacks.

Key Deadlines & Timeframes

Evidence You Will Need

Your defense hinges on proving the chip was read — not swiped. Pull authorization records before doing anything else.

• EMV authorization data from your processor showing the transaction included chip data (Application Identifier, Cryptogram, and Service Code beginning with 2 or 6 confirming chip-capable card)
• Terminal capability code from the transaction record showing your terminal was chip-capable and that chip read was attempted and successful
• Transaction receipt showing "CHIP READ" or equivalent confirmation rather than "SWIPE" or "MANUAL ENTRY"
• POS system logs confirming no fallback to magnetic stripe occurred for this transaction
• Signed sales receipt with cardholder signature, if applicable (less determinative than chip data but useful supplemental evidence)
• Security camera footage if available, showing cardholder physically present and card inserted into terminal

How Merchants Lose This Dispute

• Confusing "we have an EMV terminal" with "chip was used." The terminal's capability does not matter — what matters is whether chip data was captured for this specific transaction. Merchants frequently respond with terminal certification documents instead of transaction-level EMV data, which proves nothing about how the card was processed.
• Submitting a receipt showing "swipe" or "fallback." If your receipt says the card was swiped, you have confirmed liability rather than rebutted it. Do not submit evidence that acknowledges magnetic stripe processing without a compelling explanation.
• Missing the deadline while waiting for processor records. Authorization records take time to retrieve. Start the process immediately upon receiving the chargeback notification — do not wait until day 25 to request records from your processor.
• Attempting to fight when liability clearly shifted. If the transaction was genuinely swiped or processed in fallback, the dispute is effectively unwinnable. Accepting the chargeback and correcting your terminal configuration is a better use of resources than a losing representment.

Response Framework Overview

1. Assert chip processing occurred. Open by stating the transaction was processed via EMV chip read, not magnetic stripe, and that you have authorization data to confirm this.
2. Present EMV authorization records. Lead with the specific transaction data: Application Identifier (AID), Authorization Response Cryptogram (ARQC), and terminal verification results that confirm chip interaction.
3. Confirm terminal capability. Include documentation of your terminal's EMV certification status and software version at the time of the transaction.
4. Attach the transaction receipt. Show the receipt confirms chip read, not swipe or manual entry.
5. Reference the authorization approval. The issuer approved this transaction — note that the authorization was granted and that your terminal performed correctly.

Prevention Tips

• Disable magnetic stripe fallback on your terminals. If your terminal allows chip-capable cards to fall back to swipe when the chip fails, disable it. Require customers to use a different card if the chip fails after multiple attempts. This eliminates the primary liability exposure.
• Monitor fallback transaction rates. Your processor or acquirer can provide reports on fallback percentage. Rates above 1-2% suggest a hardware problem — get terminals repaired or replaced before a fraud wave hits.
• Ensure all staff insert rather than swipe. Retraining is cheap; chargebacks are not. Even one swiped transaction on a counterfeit card creates full liability. Build chip-first protocols into staff onboarding.
• Keep terminal firmware current. Outdated EMV software can cause false chip read failures that trigger fallback. Schedule regular firmware update checks with your terminal vendor.

Frequently Asked Questions

Why did I get a 10.1 chargeback if I have an EMV terminal?

Having an EMV terminal is not enough — it must have been used for the specific transaction in dispute. If the card was swiped instead of dipped (even if the terminal supports chip), or if your terminal was in fallback mode, liability shifts back to you as the merchant. The critical question is whether chip data was captured for that specific transaction.

What is fallback processing and why does it trigger 10.1?

Fallback processing occurs when a chip card is swiped because the chip reader failed or was unavailable. When this happens on a counterfeit card, liability falls on the merchant who accepted the swipe rather than requiring a chip read. Excessive fallback rates can also trigger Visa compliance programs.

Can I win a 10.1 chargeback if I processed the chip correctly?

Yes. If you can demonstrate that the chip was read and approved — not swiped, not manually keyed — and that EMV authorization data exists for the transaction, you have strong grounds to fight the dispute. Your processor can usually pull the authorization data showing the chip read occurred.

How long does a cardholder have to file a 10.1 dispute?

Visa allows cardholders up to 120 days from the transaction date to file a 10.1 chargeback. Your response window after receiving the dispute notification is 30 days from acquirer receipt, though your processor may impose a shorter deadline.

Related Codes & Resources