Visa 10.1 — EMV Liability Shift Counterfeit Fraud
Visa 10.1: the cardholder says a counterfeit copy of their card was used
By Byron Kiriibwa · Updated
Checked by three automated reviewers (facts against the playbook, search, and our rules), then approved by the author on .
Visa 10.1 means the cardholder says they didn't make an in-person purchase and that a counterfeit copy of their card was used. It turns on how the card was read: whether its chip was read at a chip-reading terminal, not swiped or keyed, and whether the approval request carried the chip's full data. Swiped or keyed, accept.
What decides a Visa 10.1
- How the card was read, not who held it
- Visa lets the issuer raise 10.1 only for a chip card reported counterfeit, when the sale didn't take place at a chip-reading device or the chip's full data didn't go with the approval. Arguing the customer looked like the cardholder misses the question; the entry mode on the record answers it.
- The chip's full data in the approval request
- A chip-initiated sale authorized online can still fall under 10.1 if the approval request was sent without the chip's full data. Visa's listed response asks you to show both: that the card was chip-read, and that the full chip data was sent.
- When the chip read failed and you swiped instead
- If the reader couldn't read the chip and the card was then swiped or keyed, the record shows no chip read, and this is a dispute to accept. The safer habit is to ask for another card rather than fall back to the stripe or the keypad.
The bank's test
The bank checks:
- Was the card read by its chip at a chip-reading terminal, not swiped or keyed?
- Did the approval request carry the chip's full data?
- Has the payment already been refunded, or does the cardholder no longer dispute it?
Evidence that answers it
“Where it goes” uses the names Stripe's and Square's APIs give each piece of evidence, which are the names Upheld uses in your packet. Nothing is sent without your approval; where Upheld can't send it for you, you submit it yourself. In Stripe's Dashboard, choose the matching type for each file or text field. In Square's, add it when Square asks you to “upload any additional evidence specific to your service type”.
| Evidence | When it counts | How to show it | Where it goes | For |
|---|---|---|---|---|
| Card reader or processor record (chip, PIN, imprint) | Showing the chip read (entry mode) and the authorization. | The terminal's receipt or the processor's transaction record, showing the entry mode, the verification result, the terminal ID, and the authorization code. Point to the lines that show how the card was read and how the cardholder was verified. | Stripe: Uncategorized fileSquare: Authorization documentation | Every seller |
| Receipt or invoice | Showing the sale: what was bought and the amount. | The receipt or invoice sent to the customer. | Stripe: ReceiptSquare: Receipt | Every seller |
| Refund or credit already issued | If the payment was already refunded. | Refund date, amount, and reference. | Stripe: Uncategorized fileSquare: Generic evidence | Every seller |
| Messages with the customer | If the cardholder has withdrawn the dispute. | The relevant messages only, dated, with the key lines highlighted or quoted in the response. | Stripe: Customer communicationSquare: Cardholder communication | Every seller |
What doesn't help
- 3D Secure, address checks, or delivery proof. They answer online fraud, not a card-present sale.
- A signature on its own. A counterfeit card can be signed for; the question is whether the chip was read.
Visa's rules for 10.1
- Visa lets the issuer raise 10.1 only when all of these hold: the sale was card-present with a card reported counterfeit; it qualifies for the EMV liability shift; the card is a chip card; and either the sale didn't take place at a chip-reading device, or a chip-initiated sale authorized online was sent without the full chip data. Source: Visa, Dispute Management Guidelines for Visa Merchants (June 2024), Condition 10.1; read 2026-10-15.
- Visa's listed responses: the sale took place at a chip terminal (show it was chip-read and the full chip data was sent); a credit or reversal was already processed; the cardholder no longer disputes it. If the sale wasn't at a chip terminal, Visa says to accept.
- Visa's current rules keep the credit and withdrawal responses: at pre-arbitration the acquirer may show a credit or reversal the issuer didn't address, that the dispute is invalid, or that the cardholder no longer disputes the transaction. Source: Visa, Visa Core Rules and Visa Product and Service Rules (24 October 2026), section 11.8.2.6, Table 11-14; read 2026-11-03.
- The bank's test and the evidence list were checked against Visa Core Rules and Visa Product and Service Rules (24 October 2026), section 11.8.2, on 2026-10-29.
Common mistakes with Visa 10.1
- Sending a receipt that doesn't show the entry mode.
- Arguing the customer looked like the cardholder. The question is how the card was read.
Should you fight it?
Fight it when your card-reader provider's record shows the chip was read at a chip terminal and the sale was approved with the chip's full data. A till receipt without the entry mode can't show that, so ask the provider for the transaction record before you decide. A credit or reversal already processed, or the cardholder's message withdrawing the dispute, is also one of Visa's listed responses, and needs no chip record. Accept it when any of these is true:
- The card was swiped or keyed, or the terminal can't read chips.
- There is no record of how the card was read, and the card-reader provider can't supply one.
If you accept, don't refund as well: once it's a chargeback the money has already gone back to the customer, so a refund would pay them twice.
A dispute counts against your account whether you win or lose. To see the chance of winning at which fighting pays on your amount, try the fight-or-accept calculator; to compare what you keep with each tool, the fee calculator.
How to prevent the next one
- Use a chip-reading card reader for every in-person sale.
- Don't fall back to swiping or keying when a chip read fails; ask for another card.
- Keep the card-reader provider's transaction records.
Deadlines and fees
| Platform | Deadline | Fees |
|---|---|---|
| Stripe (US)Checked 2026-10-21 | Respond by the due date on the dispute in your Stripe Dashboard. It's usually 7 to 21 days, depending on the card network. | $15 when the dispute arrives, which isn't returned. $15 more when you respond, returned only if you win in full.Stripe's Smart Disputes waives the $15 response fee and takes 30% of the disputed amount when you win. |
| SquareChecked 2026-10-21 | Seven days from Square's first email about the dispute. | No fees for dispute management on chargebacks: Square covers the fee for disputes you challenge together. |
| Shopify Payments (US)Checked 2026-10-21 | Respond by the evidence due date in your Shopify admin. It's usually 7 to 21 days. | $15 per chargeback, returned if you win. |
A worked example (made up)
You sell handmade ceramics online and at a weekend market, where you take cards on a chip-reading card reader. On Saturday, August 9, a customer buys a $180 serving bowl at your stall: they insert the card, the reader reads the chip, and the payment is approved online. In September the cardholder files a 10.1 dispute saying they didn't make the purchase and their card had been counterfeited.
The response would attach:
- Exhibit A: the card-reader provider's transaction record for the August 9 sale, showing the entry mode as chip.
- Exhibit B: the provider's authorization record for the same sale: approved online, the authorization code, and the chip data sent with the approval request.
- Exhibit C: the receipt for the sale: the date and time, the $180 serving bowl, and the card ending.
A sample response letter (made up)
For the example above. It's laid out the way Upheld drafts a response: one part for each thing the bank checks, strongest evidence first, each pointing to its exhibit. Yours should state only what your own records show.
We contest this dispute, Visa reason code 10.1, for $180.00 charged on August 9 for a ceramic serving bowl bought in person at our market stall. The card was read by its chip, and the sale was approved with the chip's full data.
The card was read by its chip at a chip-reading terminal. Our card-reader provider's transaction record shows the entry mode as chip, not swiped or keyed (Exhibit A), for the sale on the August 9 receipt (Exhibit C).
The approval request carried the chip's full data. The provider's authorization record shows the sale was authorized online, with its authorization code and the chip data sent in the request (Exhibit B).
The card at our stall was read by its chip, and the approval request the issuer answered carried the chip's full data. We ask that the dispute be decided in our favor.
Questions people ask
What does Visa reason code 10.1 mean?
It's Visa's code for EMV liability shift counterfeit fraud: the cardholder says they didn't make an in-person purchase and that a counterfeit copy of their card was used.
The customer signed the receipt. Is that enough to win a 10.1?
No. A counterfeit card can be signed for, so a signature on its own doesn't help. What answers a 10.1 is the record of how the card was read: the chip entry mode, and the approval sent with the chip's full data.
Our till receipt doesn't show the entry mode. What do we send for a 10.1?
Ask your card-reader provider for the transaction record; sending a receipt that doesn't show the entry mode is a common mistake on this code. If there's no record of how the card was read and the provider can't supply one, accept.
Can a 10.1 come from an online order?
Visa lets the issuer raise 10.1 only for a card-present sale with a card reported counterfeit, so a shipped online order isn't one. For an online purchase the cardholder says they didn't make, see our Visa 10.4 guide.
Draft yours free
Answer a few questions and get a draft, an evidence checklist and an honest read on whether to fight. Free account, no card.
Not sure what your notice says? Decode it first.