Chip fallback transactions, and who ends up paying
A fallback transaction is what happens when a chip card fails to read and the sale completes on the magnetic stripe instead. The terminal allows it deliberately, so a genuine customer with a damaged card can still pay. The catch is that a fallback sale carries the weaker protections of a stripe transaction, and fraud losses on it generally land with the merchant rather than the issuer.
A handful of fallbacks a month is normal wear. A steady stream of them is either a broken reader or somebody working your counter.
Why does a chip fail to read in the first place?
Usually dirt or damage. Chip contacts wear, cards get carried in wallets full of keys, and a reader that has eaten a year of lint reads poorly. Occasionally it is a genuinely counterfeit card whose chip does not work because it was never meant to.
That last possibility is the reason fallback exists as a monitored category rather than an ordinary one. A card that cannot present a chip is a card that cannot prove it is the real one.
What does a fallback cost the store?
Two things. It generally prices higher, because stripe transactions sit in less favourable interchange categories than chip ones. And it moves counterfeit-fraud liability, because the protection created by the EMV liability shift depends on the chip being read.
The second cost dwarfs the first and shows up rarely, which is exactly the shape of risk that stores under-manage.
How many fallbacks are too many?
Track the rate rather than the count, because the count rises with a busy week. If fallbacks are a routine part of a particular cashier's shift, or a particular terminal's day, you have a specific thing to look at rather than a general worry.
The two explanations are a dirty or failing reader and a person who has learned that swiping avoids questions. Clean the reader first — it is free, it is the more common cause, and ruling it out is the fair order in which to investigate a person.
What should a cashier do when a chip will not read?
Try the chip three times, then try a tap if the card supports it, and only then fall back to the stripe. A tap is a chip transaction over a different interface, so it keeps the protections a swipe gives up.
If the stripe is the only path left, complete the sale and look at the card: does the name match the person, does the signature panel look right, does the card feel like a card. None of that is foolproof and all of it is better than nothing, and for a large sale it is worth the four seconds.
Can you turn fallback off?
Some terminals allow it, and a small number of high-risk merchants do. The trade-off is that you will also turn away legitimate customers whose chips have simply worn out, which at a neighborhood store is a real cost with a face attached.
The middle path most stores land on is keeping fallback enabled, watching the rate, and setting a value above which a fallback needs a manager. That keeps the everyday sale frictionless and puts a second pair of eyes on the transactions that would actually hurt.
Where do you find your own fallback numbers?
On the terminal's own reports or in your processor's portal, usually under transaction entry method. If you cannot find it, ask your provider for a month of transactions broken out by entry mode — chip, contactless, stripe and keyed. That single report answers the reader question, the training question and the fraud question at once, and most providers can produce it on request.
Look at it once a quarter rather than once. Readers degrade gradually, so the number that matters is the trend rather than any single month's figure.
Frequently asked questions
Is a contactless tap a fallback?
No. Contactless transactions use the same chip and the same cryptographic exchange over a different interface, so they carry card-present protections. A tap is a good outcome when the contacts will not cooperate, not a compromise.
Does cleaning the reader really help?
More than owners expect. A cheap card-reader cleaning card run through the slot weekly costs very little and removes the most common cause of read failures. It is one of the few maintenance habits that pays for itself in avoided service calls.
Do fallback transactions get declined more often?
They can be, because some issuers scrutinise them harder precisely because of the fraud association. A decline on a fallback after the chip failed is a signal worth respecting rather than working around.
Is the store liable for every fraudulent fallback?
Liability depends on the card type, the network's rules, and the circumstances of the dispute, so "every" is too strong. What is reliably true is that a fallback puts you in a weaker position than a chip read would have, which is the reason to keep the rate low.
Should I train staff to explain the delay to customers?
Yes, and one sentence does it. "The chip is not reading, let me try it once more" is better received than silent repetition, and it stops the customer assuming the store's machine is broken.
What if a specific regular customer always falls back?
Their card is probably worn out and their bank will replace it. Telling them so is a small kindness that also removes a recurring risk from your counter, which is the rare case where those two interests point the same way.