Visa 10.2 - EMV Liability Shift (Non-Counterfeit)
TL;DR
- A real card got used by the wrong person, and your terminal didn't read the chip.
- 10.1 is a cloned card and 10.2 is a real one, but the evidence is identical.
- Cardholder filing window: 120 days. Your response window: 30 days.
- Prove the chip was read and you win. Chip plus PIN and it isn't close.
- No chip read, no defense. Your terminal logs decide this, not your story.
Someone used a lost, stolen, or never-received card at your counter and the chip didn't get read. Visa moves the loss to whoever skipped EMV.
When This Code Applies
- Lost or stolen card used at POS
- Card never received by cardholder (intercepted)
- Genuine card, unauthorized transaction
- Chip not read (swipe fallback)
Conditions for Valid Dispute
Issuer Must Verify
- Card is genuine (not counterfeit)
- Cardholder didn't authorize the transaction
- Card has an EMV chip
- Chip wasn't read in the transaction
Transaction Must Be
- Card-present
- Processed without reading chip
- At EMV-capable or non-EMV terminal
Time Frames
| Scenario | Window |
|---|---|
| Cardholder files | 120 days from transaction date |
| You respond | 30 days from the dispute |
Liability Shift Rules
Merchant Liable When
- Terminal didn't read chip
- EMV fallback without proper procedure
- Staff accepted swipe without chip attempt
Issuer Liable When
- Chip was read successfully
- Proper authentication occurred
- PIN verified (if PIN-preferring card)
Difference from 10.1
| Aspect | 10.1 | 10.2 |
|---|---|---|
| Card type | Counterfeit | Genuine |
| Fraud source | Cloned card | Lost/stolen card |
| Key evidence | Chip vs swipe | Chip vs swipe |
Representment Options
1. Chip Was Read
Evidence required:
- EMV transaction log
- Cryptogram data
- Terminal certification
2. PIN Verified
Evidence required:
- PIN entry confirmation
- Terminal PIN pad log
- Correct PIN on first attempt
3. Cardholder Present
Evidence required:
- CCTV footage
- ID verification records
- Signature match
Prevention Strategies
Use the chip every time. If the card has one and your terminal reads it, a swipe is a loss waiting to happen. Turn on PIN preference if your terminals support it. That's the strongest defense this code allows.
Train staff on one rule: chip first, always. If a customer pushes hard for a swipe, that's information. Log every fallback and the reason for it.
Win Rate Expectations
| Defense Type | Expected Win Rate |
|---|---|
| Chip + PIN verified | 85-95% |
| Chip read only | 70-85% |
| No chip read | Under 25% |
Common Mistakes
- Swipe without a chip attempt - Liability shifts immediately
- No PIN verification - You gave up a layer
- Staff overriding chip prompts - Creates the liability
- Missing terminal logs - Can't prove the chip was used
Related Codes
- 10.1 - EMV Liability Shift Counterfeit
- 10.3 - Other Fraud Card Present
- 10.4 - Card Not Present Fraud
Next Steps
Got this chargeback?
- Pull terminal logs → Chip read? PIN entered?
- Check CCTV → Can you identify who used the card?
- Gather evidence → Representment Workflow
- Respond within 30 days
Prevent future 10.2 chargebacks:
- Chip and PIN whenever the terminal offers it
- Put a camera on the POS
- Review EMV requirements
See Also
- EMV & Contactless - Chip and NFC setup
- Card-Present Fraud - Lost and stolen card patterns
- Terminal Security - Tampering and skimmer checks
- Terminal Operations - Day-to-day POS handling