EMV Liability Shift
- Chip liability isn't one rule. Each network's code has its own tests on the card, terminal, region, transaction data and exclusions. They allocate a loss between the issuer and your acquirer (the bank behind your processor). What reaches you depends on your acceptance agreement
- Counterfeit and lost, stolen or never-received claims are separate, with separate tests. Whether a PIN was used doesn't settle the second one alone
- Contactless and mobile wallets have their own conditions. Don't assume they match a chip dip
- US dates: ordinary point of sale from October 2015. ATM dates differ, 21 October 2016 on Mastercard and 1 October 2017 on Visa. Fuel and other regions have their own. On older hardware, check your terminal's certification status
A chip read failed, or an in-person sale came back as a counterfeit-fraud dispute? First check whether the chip was actually read, on a certified terminal with chip turned on, and whether the chip data reached the authorization and clearing records. EMV rules can move counterfeit fraud liability from the issuer to your acquirer when a chip card wasn't processed as a chip. That's the liability shift. Every condition below matters.
How Liability Shift Works
The Basic Idea
On eligible counterfeit fraud, responsibility can follow whoever didn't support the chip. That's a starting point, not the test. The network's card, terminal, region, required authorization and clearing data, and exclusions all apply (Visa rules, 24 October 2026, sections 4.1.17.45 and 11.8.2, pp. 254-255 and 692-696; Mastercard's guide, 13 May 2025, 4870, pp. 495-512).
| Terminal | Card | Where a counterfeit claim starts (issuer = the customer's bank) |
|---|---|---|
| Chip processed, required data sent | Chip | With the issuer |
| Chip terminal, chip data missing | Chip | It can land on your acquirer, then you. Check the code |
| No chip terminal | Chip | It can land on your acquirer, then you. Check the code |
| Any | No chip (mag-stripe) | This chip code doesn't apply. Other fraud rules can |
What your acquirer charges you after that depends on your acceptance agreement.
The US Dates
These are scheme and region milestones, not a guarantee that a later sale qualifies.
| Network | US ordinary point of sale | US ATM |
|---|---|---|
| Visa | October 2015 | 1 October 2017 |
| Mastercard | 1 October 2015 | 21 October 2016 (guide, pp. 695-698) |
Automated fuel dispensers and other regions have separate dates.
Chip authentication makes a card harder to copy (EMVCo). That's the reason for the shift, not a ranking of fraud by channel.
What "Chip Terminal" Really Means
Having a terminal with a chip slot isn't enough. For the protection to hold:
Requirements
| Requirement | Why It Matters |
|---|---|
| EMV-capable terminal | Hardware must support chip |
| EMV enabled | Chip must be activated, not disabled |
| EMV certification | Terminal must be certified and deployed through your acquirer or processor |
| Chip processed on the transaction | Dip or tap, with the required data in authorization and clearing. Contactless has its own conditions |
Common Mistakes
| Mistake | Result |
|---|---|
| Chip terminal but EMV not enabled | You can lose a counterfeit claim |
| Swiping a chip card outside proper fallback | You can lose a counterfeit claim |
| Fallback to swipe after a real chip failure | Proper technical fallback can be excluded. See fallback |
| Keying a card when the chip could work | You can lose a counterfeit claim. Qualifying keyed fallback has its own requirements |
Transaction Types and Liability
Chip Dip (Contact EMV)
- Card inserted into chip slot
- The chip creates a one-time code for each payment
- Counterfeit responsibility can stay with the issuer when the required data is sent and the code's tests are met
Contactless (Tap)
- Card or device tapped on terminal
- Uses EMV technology
- Check the network's contactless and verification conditions. They aren't always the same as a chip dip
- Includes Apple Pay, Google Pay (tokenized)
Swipe (Mag-Stripe)
- Magnetic stripe read
- On a chip card, a counterfeit claim can stand, unless it's proper technical fallback
- Acceptable for non-chip cards
Keyed (Manual Entry)
- Numbers typed manually
- No chip or swipe
- No chip read to rely on. Qualifying keyed fallback can be excluded from Mastercard 4870, under its requirements
- Measure your own keyed fraud and losses against other entry methods
Fallback Transactions
When chip fails and you fall back to swipe:
What Can Cause Fallback
- A dirty or damaged chip
- A terminal chip reader problem
- A card chip fault
- A fraud attempt, such as a manipulated card
Measure fallback and losses by entry method on your own transactions. Don't assume which of these you've got.
What Makes Fallback Proper
It isn't a count of how many times it happened. The network looks at whether there was a real chip-processing failure, the required entry, terminal and card data, and the authorization and clearing coding and approval conditions. Proper fallback can be excluded from a counterfeit claim, including qualifying keyed fallback under Mastercard's requirements. A recorded fault alone isn't the whole test (Mastercard's guide, pp. 496 and 509, and the 4870 remedies; Visa rules, section 4.1.17.47, p. 255, and Table 11-11, p. 694).
A terminal that keeps falling back is a problem to investigate, whatever happens on one sale.
Fallback Best Practices
- Always attempt chip first
- Re-insert chip if first attempt fails
- Clean the chip reader as the device maker instructs
- Request different card if repeated failure
- Document fallback reasons, and check your provider codes the fallback correctly
Reason Codes for Liability Shift Disputes
Visa
| Code | Name | When Used |
|---|---|---|
| 10.1 | EMV Liability Shift (Counterfeit) | An eligible counterfeit chip-card transaction whose full chip data didn't reach online authorization or offline clearing, under the regional terminal and data tests. Proper fallback is excluded |
| 10.2 | EMV Liability Shift (Non-Counterfeit) | A lost, stolen or never-received chip-and-PIN card, used where the terminal couldn't handle chip and PIN properly. Contactless and fallback sales are excluded, and so are US domestic sales |
Mastercard
| Code | Name | When Used |
|---|---|---|
| 4870 | Chip Liability Shift: Counterfeit | A counterfeit on a validly issued chip card, at a terminal that couldn't read chips or with the required chip data missing. Proper technical fallback is excluded. Europe's non-ATM Maestro use has its own route |
| 4871 | Chip Liability Shift: Lost/Stolen | A lost, stolen or never-received chip card or qualifying device, under its card, terminal and verification tests and participating geography. Proper contactless and device verification cases are excluded |
Amex
| Code | Name | When Used |
|---|---|---|
| F30 | EMV Counterfeit | A counterfeit chip card accepted in a qualifying lower-technology case, not every counterfeit |
| F31 | EMV Lost/Stolen/NRI | A lost, stolen or never-received chip-and-PIN card, used with lower technology or without adequate PIN support, with issuer, merchant and acquirer all in designated countries after their effective dates. Properly identified fallback, contactless and digital-wallet sales are excluded |
Conditions and responses are in Amex's rules, effective 24 October 2026, Tables 9-30 and 9-31, pp. 126-129.
Discover
Use the code on your notice. Providers can show newer four-digit Discover codes from 17 April 2026 (Braintree's evidence guide). Older notices can use UA codes: one provider's list labels UA05 Chip Counterfeit Transaction and UA06 Chip and PIN Transaction (Moneris's guide, pp. 172-176). Those are a provider's labels, not Discover's current list.
Fighting EMV Liability Chargebacks
What Can Support a Response
Get the actual card, terminal, entry-mode, authorization and clearing records for the remedy you're claiming. A receipt, certificate or log supports that. It isn't an automatic win (Mastercard's guide, 4870 pp. 504-509, 4871 pp. 533-540; Visa rules, sections 11.8.2 and 11.8.3).
| Scenario | What to gather |
|---|---|
| Chip was actually used | Chip data in the authorization and clearing records, with the receipt as support |
| Terminal is certified | Certification documents, as support. They don't show how this sale ran |
| Card wasn't chip-enabled | The card's record. A BIN lookup alone doesn't prove this card's chip or service code |
| Technical malfunction documented | Terminal logs, plus the fallback coding in authorization and first presentment |
When a Response Is Harder
| Scenario | Why |
|---|---|
| Swiped a chip card, outside proper fallback | The chip was available and wasn't used |
| Keyed a card without a qualifying fallback | No chip data to show |
| EMV not enabled | A configuration issue on your side |
| Frequent fallback | The count doesn't decide a case, but it can point to a terminal problem |
Evidence to Collect
| Evidence | Purpose |
|---|---|
| Transaction receipt | Supports the entry method (chip/swipe/keyed) |
| Terminal certification docs | Supports EMV capability |
| Terminal batch report | Shows transaction details |
| Chip data (ARQC/TC) | Shows the chip was read, if it's in the required messages. Ask your processor for the chip data on the transaction |
Contactless and Mobile Wallet Liability
Mobile Wallets (Apple Pay, Google Pay)
| Factor | What to check |
|---|---|
| Tokenized | Token represents card, not actual number. That isn't a blanket network protection |
| Device authentication | A biometric or PIN on the device, with exceptions. Apple's Express Mode can use an eligible payment or transit card without authenticating each payment |
| Liability | Check the actual verification result, region and fraud condition |
Contactless Cards
| Factor | What to check |
|---|---|
| EMV contactless | Uses chip technology wirelessly |
| Liability shift | Depends on the code. Visa 10.2 excludes contactless in its stated tests, and Mastercard has its own verification and contactless exclusions (Visa rules, Table 11-17, pp. 698-699; Mastercard's guide, pp. 526-527) |
Special Cases
Card-Present but Keyed
Sometimes you have the card but can't dip/swipe:
- Damaged chip and mag-stripe
- Reader malfunction
Liability: Don't assume. In-person manual entry needs its actual processing classification and any qualifying technical-fallback conditions. Otherwise a keyed sale has no chip read to rely on. A phone order is card-not-present, even if the customer has the card in hand.
Best practice: If chip and swipe both fail, request different payment method or decline transaction.
Hotel and Rental Pre-Authorization
| Scenario | What applies |
|---|---|
| Initial auth (check-in) | Eligibility is checked on that transaction |
| Incremental auth | Has its own eligibility. May not be card-present |
| Final capture or a delayed charge | Has its own linked-transaction and processing conditions |
Hotels and rentals have special rules allowing delayed and incremental charges. An earlier chip read doesn't cover them automatically. Visa's delayed-charge exclusion has its own conditions, and Mastercard's later-charge remedies need their own data (Visa rules, Table 11-17, p. 699; Mastercard's guide, pp. 526-540).
Recurring Transactions
| Scenario | What applies |
|---|---|
| Initial chip transaction | Eligibility is checked on that transaction |
| Subsequent recurring | MIT (merchant-initiated) rules apply |
| Stored credential | Has its own conditions, not just the original capture method |
Don't assume the first chip read protects later charges on the saved card. Charges you start later, without the customer there, follow their own rules. Ask your processor: "Which later charges on a saved card are protected, against which fraud claims, under my account terms?"
Terminal Compliance
EMV Certification Process
| Step | Description |
|---|---|
| 1. L1 | Mechanical and electrical interface testing |
| 2. L2 | The terminal's EMV kernel and application logic |
| 3. L3 | End-to-end integration with payment-system requirements (EMVCo) |
| 4. Deployment | Your processor or acquirer's process for activating it in production |
Maintaining Compliance
| Action | Frequency |
|---|---|
| Firmware updates | As released |
| Certification renewals | Per network requirements |
| Security patches | Immediately |
| Reader cleaning | As the device maker instructs |
Terminal Inspection Checklist
- Chip slot clean and unobstructed
- No overlays on chip slot or PIN pad
- Tamper-evident seals intact
- Firmware current
- EMV enabled (not bypassed)
Regional and Network Variations
Visa
- US ordinary point of sale: October 2015. US ATM: 1 October 2017
- Gas stations extended to April 2021
- Regional eligibility and exclusions are in section 11.8.2, pp. 692-696
Mastercard
- US ordinary point of sale: 1 October 2015. US ATM: 21 October 2016
- Check its domestic and interregional tables, pp. 695-698, for your region and MCC
American Express
- Liability shift effective October 2015
- SafeKey is an online authentication product, separate from chip at a terminal
- Conditions and responses are in its rules, Tables 9-30 and 9-31, pp. 126-127
Discover
- ProtectBuy for authentication
- Use the code on your notice, and ask your acquirer for the current chip rules
Future: Tap-to-Phone
Emerging technology allows phones to act as terminals:
| Factor | Status |
|---|---|
| Technology | Phone accepts contactless payments |
| Certification | Network programs exist (Visa Tap to Phone, etc.) |
| Liability shift | Being on a phone doesn't decide it. It turns on the solution's certification, the transaction data and the network's condition |
| Security | Software-based security model |
Scale Callout
| Volume | Focus |
|---|---|
| Under $50k/mo CP | Check your terminals are EMV-enabled. Don't overthink. |
| $50k-$250k/mo CP | Monitor fallback rates. Clean readers regularly. |
| $250k-$1M/mo CP | Track liability shift chargebacks. Investigate patterns. |
| Over $1M/mo CP | Dedicated terminal management. Regular certification audits. |
Where This Breaks
-
Assuming chip = protected. Terminal certified, EMV enabled, chip actually processed, required data sent, and the code's tests met. Check them all.
-
Ignoring fallback rates. High fallback rates signal terminal issues and potential liability gaps. Monitor and fix.
-
Keyed transactions for "convenience." A keyed sale has no chip read to rely on. Cut them back.
Next Steps
Understanding liability shift?
- Card-Present Fraud: CP fraud types and prevention
- EMV & Contactless: Operational guide for chip payments
- Card-Present Terminal Decisions: Terminal selection
Fighting EMV chargebacks?
- Chargeback Lifecycle: Understand dispute timelines
- Compelling Evidence: Build your defense
- Representment: Response strategies
Optimizing terminal operations?
- Terminal Operations: Managing terminal fleet
- Terminal Security: Physical security controls
- Digital Wallets: Contactless wallet benefits
Related Pages
- Prevent Fraud: The fraud hub
- Card-Present Fraud: CP fraud types and prevention
- Card-Present Terminal Decisions: Choosing terminals
- Terminal Operations: Managing terminal fleet