What the liability shift actually covers
The card networks introduced the EMV liability shift to encourage adoption of chip technology. In broad terms, when a counterfeit card is used and the terminal was capable of reading the chip but the transaction was instead completed by swiping the magnetic stripe, liability for that specific counterfeit-fraud loss can shift toward whichever party — merchant or issuer — had the lesser chip capability at the point of sale.
This is a network rule about how counterfeit-card losses are typically allocated. It is not a guarantee that a merchant will avoid a dispute, and it does not apply to every type of chargeback — lost or stolen card disputes, card-not-present fraud and non-fraud disputes (like a service complaint) are handled under different rules entirely.
Chip vs magstripe fallback
When a chip fails to read, many terminals allow a magstripe swipe as a fallback so the sale can still be completed. That fallback path is exactly the scenario the liability shift is meant to address: if the card had a working chip and the terminal could read it, but the transaction was swiped instead, the merchant may bear more of the counterfeit-fraud risk on that transaction.
Keeping terminal software current and training staff to attempt the chip or tap read first, rather than defaulting to a swipe, is a reasonable operational habit under these rules.
Contactless, mobile wallets and PIN debit
Contactless tap payments and mobile wallets (such as phone- or watch-based payments) generally use chip-equivalent cryptographic data and are treated similarly to a chip transaction under network rules. PIN debit transactions have their own separate network rules and liability framework, distinct from the general EMV credit liability shift.
None of this changes how a transaction should be handled operationally — accept the tap or chip read the terminal presents, and let the device and network handle the underlying verification.
What this means if you still key or swipe often
Some businesses still see a meaningful share of keyed transactions — phone orders, mail orders, or manually entered sales when a chip read fails repeatedly. Keyed and card-not-present transactions sit outside the EMV liability shift altogether and are governed by different fraud and dispute rules, which is why AVS, CVV and other card-not-present controls matter separately.
If a countertop terminal is aging or a device is not reading chips reliably, that is worth addressing directly, since repeated fallback to swiping increases exposure specifically for counterfeit-card scenarios.
Practical steps for merchants
The liability shift is a background rule, not a daily checklist item, but a few habits keep a business aligned with it.
Keep hardware current
Confirm your terminals are EMV- and contactless-capable and that firmware updates are applied.
Don't default to swipe
Train staff to attempt chip or tap first and treat repeated fallback failures as a hardware issue to fix.
Separate card-not-present risk
Recognize that phone, invoice and online sales need their own fraud controls, since the liability shift does not apply to them.
Review terminal age periodically
Older devices may lack current contactless or authentication capability; hardware options can be reviewed as part of a periodic account review.
Frequently asked questions
What is the EMV liability shift?
It is a card-network rule describing how liability for certain counterfeit-card fraud losses is generally allocated between a merchant and card issuer, based on whether chip technology was used or available at the point of sale.
Does accepting chip cards guarantee I won't lose a dispute?
No. The liability shift addresses counterfeit-card fraud specifically and is one factor among several in how a related dispute may be evaluated. It does not cover other dispute types and does not guarantee any outcome.
Are tap and mobile wallet payments treated like chip payments?
Generally yes, since they use similar chip-based cryptographic verification, though PIN debit transactions follow their own separate network rules.
What happens if the chip reader fails and we swipe instead?
If a counterfeit card is later swiped as a fallback when the terminal could have read the chip, the merchant may bear more of the counterfeit-fraud liability for that transaction under network rules.
Does the liability shift apply to phone or online orders?
No. Card-not-present transactions are governed by separate fraud and dispute rules, which is why controls like AVS, CVV and authentication matter for those channels specifically.
How do I know if my terminals are current?
A processor or POS provider can review your current hardware and firmware. BSV Solution can assess your equipment as part of a broader account review.
Want a second opinion on your setup?
Tell us how you take payments today and a BSV Solution specialist will walk through the options with you. Eligibility and processor selection are reviewed individually, subject to underwriting approval.