Does Visa reason code 10.1 apply to online transactions?

No. Code 10.1 is strictly a card-present dispute tied to the EMV liability shift. Card-not-present fraud claims come through as 10.4 instead. If you received a 10.1 on an ecommerce transaction, that is a filing error worth challenging with your acquirer.

Can I win a 10.1 chargeback if my terminal was EMV-enabled?

Yes, and this is the main winnable scenario. If your authorization records show the transaction was processed as a genuine chip read on a certified EMV terminal, the liability shift never triggers and the dispute should be reversed. Submit the POS entry mode data and terminal certification as evidence.

Who is liable when a counterfeit card is swiped instead of dipped?

The merchant, in almost all cases. The EMV liability shift moved counterfeit losses to whichever party lacked chip capability. If the card had a chip and your terminal processed it as a swipe or key entry, the issuer can charge the transaction back under 10.1 with strong odds of keeping it.

Visa · Fraud

Reason code 10.1: EMV Liability Shift Counterfeit Fraud

The cardholder claims a counterfeit chip card was used at a merchant terminal that was not EMV-enabled, so liability for the fraudulent transaction shifts to the merchant. It arises solely in card-present acceptance, where a chip card was processed by magnetic stripe or key entry instead of a chip read. Under the EMV liability shift rules, the party with the weaker technology eats the loss.

Issuer filing window

120 days from the transaction processing date

Merchant response window

typically 20-30 days to respond, depending on the acquirer

Why 10.1 chargebacks happen

A counterfeit card cloned from stolen magnetic stripe data was swiped at a terminal that does not support chip processing.
The merchant's EMV terminal was broken or misconfigured, forcing staff to fall back to magnetic stripe swipes on chip cards.
Staff manually keyed in the card number from a counterfeit card instead of inserting the chip.
The point-of-sale software was never certified for EMV even though the hardware physically supports chip reads.
A fraudster deliberately targeted the business after learning its terminals still accept swiped chip cards.

How to fight a 10.1 chargeback

Pull the authorization record and confirm whether the transaction was actually processed as a chip read; if the POS entry mode shows chip data was read and validated, the liability shift does not apply and you should submit that evidence.
Provide terminal certification records showing the device was EMV-compliant and functioning on the transaction date.
Submit proof that the card presented was not a chip card at all, such as the service code from the authorization message, since the liability shift only covers chip cards processed by lesser means.
Check for a duplicate dispute under another 10.x code on the same transaction, because Visa only permits one fraud dispute per transaction.
If the transaction was a fallback approved by the issuer with full chip data transmitted, include the authorization log showing the issuer approved it with that knowledge.

How to prevent 10.1 chargebacks

Deploy certified EMV chip terminals at every point of sale and retire any swipe-only hardware.
Train staff to always attempt a chip insert first and to treat repeated fallback swipes on chip cards as a fraud red flag.
Keep terminal firmware and kernel certifications current so chip reads do not silently fail into fallback mode.
Monitor your fallback transaction rate; a spike usually means either broken hardware or an active counterfeit card operation targeting your store.
Require additional verification, such as ID checks where permitted, on high-value keyed or swiped transactions.

High-risk merchant angle

A pure ecommerce operation should never receive a 10.1, since the code exists for card-present acceptance; where it reaches high-risk operators is hybrid models such as retail CBD or vape locations running alongside an online store. Counterfeit fraud at a terminal still generates TC40 fraud reports, and while Visa's current monitoring under VAMP (the Visa Acquirer Monitoring Program, which replaced the old Visa Fraud Monitoring Program in April 2025) builds its headline ratio on card-not-present activity, those reports still sit in the risk file your acquirer weighs across the whole relationship. If you operate card-present MIDs under the same legal entity as your online MIDs, keep the fraud reporting separated and the terminals EMV-certified so a POS problem does not contaminate your ecommerce underwriting file.

Frequently asked questions

Does Visa reason code 10.1 apply to online transactions?: No. Code 10.1 is strictly a card-present dispute tied to the EMV liability shift. Card-not-present fraud claims come through as 10.4 instead. If you received a 10.1 on an ecommerce transaction, that is a filing error worth challenging with your acquirer.
Can I win a 10.1 chargeback if my terminal was EMV-enabled?: Yes, and this is the main winnable scenario. If your authorization records show the transaction was processed as a genuine chip read on a certified EMV terminal, the liability shift never triggers and the dispute should be reversed. Submit the POS entry mode data and terminal certification as evidence.
Who is liable when a counterfeit card is swiped instead of dipped?: The merchant, in almost all cases. The EMV liability shift moved counterfeit losses to whichever party lacked chip capability. If the card had a chip and your terminal processed it as a swipe or key entry, the issuer can charge the transaction back under 10.1 with strong odds of keeping it.

Related Visa codes