Visa 10.2 — EMV Liability Shift Non-Counterfeit Fraud

Visa 10.2: the cardholder says their lost or stolen card was used in person

By · Updated

Checked by three automated reviewers (facts against the playbook, search, and our rules), then approved by the author on .

Visa 10.2 means the cardholder says someone used their card in person after it was lost, stolen or never received. The terminal decides it: the bank checks whether the chip was read at a terminal that can take a PIN, whether the PIN was entered, and whether the approval carried the chip's full data. Without that, accept.

Start a free draft

What decides a Visa 10.2

A terminal that can take a PIN
Visa's first listed response is that the sale took place at an EMV PIN-compliant terminal, with documentation of that. A chip read alone isn't the whole answer here: Visa lets the issuer raise 10.2 when a chip sale took place at a device that wasn't EMV PIN-compliant.
The PIN, entered and verified
The bank asks whether the PIN was entered. The card-reader provider's transaction record shows the verification result next to the entry mode and the terminal; a receipt with only the amount and card ending shows neither, so ask the provider for the record.
Only a PIN-preferring chip card
Visa lets the issuer raise 10.2 only for a PIN-preferring chip card reported lost, stolen or not received. An online-authorized chip sale made without an online PIN can still be disputed under it if the approval request was sent without the chip's full data.

The bank's test

The bank checks:

  1. Was the card read by its chip at a chip-reading terminal, not swiped or keyed?
  2. Did the sale take place at a terminal that can take a PIN (EMV PIN-compliant), and was the PIN entered?
  3. Did the approval request carry the chip's full data?
  4. 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 for Visa 10.2, by kind of business
EvidenceWhen it countsHow to show itWhere it goesFor
Card reader or processor record (chip, PIN, imprint)Showing the chip read, the PIN verified, and the terminal.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 documentationEvery seller
Receipt or invoiceShowing the sale: what was bought and the amount.The receipt or invoice sent to the customer.Stripe: ReceiptSquare: ReceiptEvery seller
Refund or credit already issuedIf the payment was already refunded.Refund date, amount, and reference.Stripe: Uncategorized fileSquare: Generic evidenceEvery seller
Messages with the customerIf 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 communicationEvery seller

Start a free draft

What doesn't help

  • 3D Secure, address checks, or delivery proof. They answer online fraud, not a card-present sale.
  • A receipt that shows only the amount and card ending, with no entry mode or verification result.

Visa's rules for 10.2

  • Visa lets the issuer raise 10.2 only when all of these hold: the sale was card-present with a card reported lost, stolen, or not received; it qualifies for the EMV liability shift; the card is a PIN-preferring chip card; and either the sale wasn't at a chip-reading device, or a chip sale took place at a device that wasn't EMV PIN-compliant, or an online-authorized chip sale without an online PIN was sent without the full chip data. Source: Visa, Dispute Management Guidelines for Visa Merchants (June 2024), Condition 10.2; read 2026-10-15.
  • Visa's listed responses: the sale took place at an EMV PIN-compliant terminal (provide documentation of that); a credit or reversal was already processed (its amount and date); the cardholder no longer disputes it (their letter or email). If the sale wasn't at an EMV PIN-compliant 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.3.6, Table 11-20; 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.3, on 2026-10-29.

Common mistakes with Visa 10.2

  • Arguing that the sale was in person or that the card checks passed, without showing the PIN-compliant terminal and the PIN.
  • Sending only the till receipt when the card-reader provider's transaction record shows the entry mode and verification.

Should you fight it?

Fight it when the card-reader provider's record shows the chip was read and the PIN entered and verified, at a terminal that is EMV PIN-compliant, with documentation of that terminal. Saying the sale was in person, or that the card checks passed, doesn't answer it. Visa also lists a credit already processed, with its amount and date, or the cardholder's letter or email withdrawing the 10.2; either answers it without the PIN-terminal record. Accept it when any of these is true:

  • The card was swiped or keyed, or the terminal can't take a PIN.
  • There is no record of how the card was read or verified, and the card-reader provider can't supply one.
  • The seller suspects the card really was used by someone else and has nothing showing a chip-and-PIN sale.

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 card reader that reads chips and takes PINs, and let it prompt for the PIN.
  • Don't key in or swipe a chip card when the chip read fails; ask for another card.
  • Keep the card-reader provider's transaction records, which show the entry mode and verification.

Deadlines and fees

Deadlines and fees by platform
PlatformDeadlineFees
Stripe (US)Checked 2026-10-21Respond 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-21Seven 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-21Respond 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 run a mobile bike repair service and take cards on a card reader that reads chips and takes PINs. On June 14 you replace a customer's chain and brake pads at their home for $140; they insert their Visa card and enter the PIN when the reader asks, and the payment is approved. In July the cardholder files a 10.2 dispute saying their card had been stolen and they didn't make the purchase.

The response would attach:

  1. Exhibit A: the card-reader provider's transaction record for June 14: entry mode chip, PIN verified, the terminal ID and the authorization code.
  2. Exhibit B: the card-reader provider's documentation that the reader with that terminal ID is EMV PIN-compliant.
  3. Exhibit C: the provider's authorization record, showing the approval request was sent with the chip's full data.
  4. Exhibit D: the invoice and receipt for the June 14 repair: a chain and brake pads, $140, 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.2, for $140.00 charged on June 14 for a bike repair done at the customer's home. The card was at the job: its chip was read and its PIN entered at a PIN-compliant card reader.

The card was read by its chip, not swiped or keyed. Our card-reader provider's transaction record shows the entry mode as chip (Exhibit A), for the repair on our June 14 invoice and receipt (Exhibit D).

The sale took place at an EMV PIN-compliant terminal, and the PIN was entered. The same record shows the PIN verified at the terminal ID it names (Exhibit A), and the provider's documentation shows that terminal is EMV PIN-compliant (Exhibit B).

The approval request carried the chip's full data. The provider's authorization record shows the request sent with it, and the issuer's authorization code (Exhibit C).

The card's chip was read and its PIN entered and verified at a PIN-compliant reader, and the issuer approved the sale on the chip's full data. We ask that the dispute be decided in our favor.

Questions people ask

What does a Visa 10.2 dispute mean?

It's Visa's code for EMV liability shift non-counterfeit fraud: the cardholder says they didn't make an in-person purchase made with their card after it was lost, stolen or never received.

How is a 10.2 different from a counterfeit card dispute?

Visa lets the issuer raise 10.2 only for a card reported lost, stolen or not received, and only a PIN-preferring chip card; a counterfeit card is Visa 10.1, which has its own guide. A 10.2 response has to show the terminal could take a PIN, not only that the chip was read.

How do we show our card reader is EMV PIN-compliant?

Visa asks for documentation that the sale took place at an EMV PIN-compliant terminal. Ask your card-reader provider for it, along with the transaction record showing the terminal, the entry mode and the PIN verification.

Our reader can't take a PIN. Should we fight a 10.2?

No. If the sale wasn't at an EMV PIN-compliant terminal, Visa says to accept, and the same goes for a card that was swiped or keyed.

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.

Start a free draft