When a chip card is inserted into an EMV terminal, the chip should communicate with the device and create a secure transaction. If that process fails and the terminal allows the magnetic stripe to be swiped instead, the payment may be recorded as an EMV fallback transaction. Fallback can be legitimate, but repeated use creates risk for merchants.
A genuine chip may fail because it is damaged, dirty, or worn. A terminal reader can also malfunction. In those cases, the device normally asks the customer to insert the card more than once before offering another method. The exact sequence depends on the terminal and processor configuration. Employees should follow the prompts rather than immediately swiping a card that has a chip.
Fraudsters may exploit fallback by using counterfeit cards with intentionally damaged or nonworking chips. The magnetic stripe can contain stolen data, while the fake chip forces the terminal toward a less secure transaction path. If the purchase is later disputed as counterfeit fraud, the merchant may face greater liability because the chip was not successfully read.
Businesses should watch for unusual fallback patterns. A sudden increase may point to a damaged terminal, an employee skipping the proper process, or suspicious customer activity. Keep chip readers clean, replace failing equipment, and train staff not to override terminal prompts casually. For a high-value sale, employees should use extra caution if the card repeatedly fails and the customer pressures them to swipe it.
Contactless payment or another card may provide a safer alternative when the chip cannot be read. Merchants should also review fallback reports with their payment provider and confirm how their equipment handles failed insert attempts. One occasional fallback does not necessarily signal fraud, but a pattern deserves attention. Treating fallback as an exception, documenting the sale, and maintaining reliable terminals can reduce preventable losses while keeping legitimate customers moving.
A simple incident log can help identify the source. Record the terminal, date, employee, card-entry sequence, and transaction result without writing down sensitive card data. Several fallback events on one device may justify replacement before the reader fails during the busiest part of the day.
