Visa Reason Code 10.1: EMV Counterfeit Fraud

What Visa reason code 10.1 means

Reason code 10.1 is a Fraud (category 10) chargeback built around the EMV liability shift. The issuer is saying three things at once: the card was a chip card, the transaction was made with a counterfeit copy of it (typically cloned magnetic-stripe data), and the merchant processed it at a terminal that did not read the chip.

Under the liability shift, whichever party has the weaker technology bears the fraud loss. If the cardholder’s bank issued a chip card and the merchant accepted a counterfeit by swiping it, the loss sits with the merchant.

Like all Visa fraud and authorization codes, 10.1 runs through the allocation workflow. There is no separate “dispute response” stage: the acquirer either accepts the liability or challenges it through pre-arbitration, and an unresolved case can go to Visa for arbitration.

Ecommerce note: 10.1 is a card-present code. An online-only store should not see it. Card-not-present fraud claims arrive as 10.4. If you do get a 10.1, look at your in-person channels first.

Common causes

• A terminal that is not EMV-capable, or a chip reader that is broken or disabled
• Staff swiping a chip card instead of inserting it, including “chip won’t read, just swipe it” habits
• Fallback transactions (chip read fails, card swiped) that don’t meet Visa’s fallback rules
• Card skimming at the point of sale, where the cloned stripe data is later used at a swipe-only terminal

Evidence that wins a 10.1 dispute

The defense is technical, not narrative. Your processor or acquirer usually evaluates the case from the transaction data itself.

1. Proof the chip was read: authorization and clearing data showing a chip-read POS entry mode. If the chip was read, the transaction is not covered by this code.
2. Proof the card was not a chip card: if the service code on the card’s magnetic stripe did not indicate a chip, the liability shift does not apply.
3. Proof the terminal was EMV-compliant and that the transaction was correctly processed for that terminal type.
4. A transaction receipt with the entry mode, terminal ID and authorization code, matching the dispute record.

Customer communication, delivery proof and prior order history rarely help here. The question is how the card was read, not who made the purchase.

How to prevent 10.1 chargebacks

• Use EMV-certified terminals everywhere you take cards in person, including event and pop-up kits.
• Train staff to always insert or tap chip cards, and not to fall back to a swipe without following your processor’s fallback procedure.
• Replace terminals whose chip readers fail repeatedly.
• Check terminals for tampering or skimming devices.

Should you fight or accept?

Fight only when the transaction data shows a chip read, or the card was not chip-enabled. Your acquirer can usually tell you quickly which one applies.

Accept when the card was swiped on a terminal that could have read the chip, or on one that couldn’t. That is exactly the situation the liability shift was designed for, and there is no compelling-evidence path that overrides it. The better spend is fixing the terminal or the process that allowed the swipe.

For how card-present fraud differs from the online fraud ecommerce merchants usually fight, see our Visa reason codes guide.