Chip Fallback: Who Pays When the Chip Won't Read

A chip fallback transaction is what happens when the chip won't read and the terminal falls back to the magnetic stripe. The rules treat it as a legitimate way to take a payment, but liability swings entirely on three conditions. Get all three right and a counterfeit loss belongs to the issuer. Miss any one and it belongs to your acquirer, which in practice means you.

Those three conditions are short, specific, and almost entirely about what your terminal sends rather than what your staff do.

What counts as fallback#

The card is a chip card, the chip-reading device can't complete a chip transaction, and the sale goes through on the stripe instead. That's fallback. It's a card-present mechanism and it has no card-absent equivalent.

It exists because chips and readers fail, and refusing every sale where the chip is dirty would cost more than the fraud. The rules accommodate it, on conditions.

The three conditions that put liability on the issuer#

A transaction accepted as a fallback transaction is the liability of the issuer if all of the following apply (ID# 0001835):

• The transaction is authorized by the issuer or the issuer's agent
• Appropriate values identifying the transaction as a fallback transaction are included within the related authorization message
• Correct acceptance procedures are followed

All three. Not two of three.

The middle one is the one that gets missed, and it's invisible at the counter. Your terminal has to tell the issuer, inside the authorization message, that this was a fallback. If it sends a plain magnetic-stripe authorization with no fallback indicator, the sale may well approve and look completely normal, and the liability has already moved.

Miss one and it lands on your acquirer#

The mirror rule spells out the failure case. Transactions accepted as fallback transactions are the liability of the acquirer if both (ID# 0001839):

• The card is a chip card containing a Visa or Visa Electron Smart Payment Application, or an EMV and VIS-Compliant Plus application, and
• Either the transaction is not authorized by the issuer or the issuer's agent, or it is authorized and the appropriate values identifying it as a fallback transaction are not included in the authorization message

So two ways to lose it. Complete the sale without an online authorization, or get the authorization but fail to flag it as fallback.

Acquirer liability is not merchant liability in the rules, but your merchant agreement is what decides where it actually settles, and it very rarely settles with the bank.

Correct fallback also protects you elsewhere#

There's a second reason to get this right. The counterfeit liability rule says counterfeit card transactions in a card-present environment are the acquirer's liability when the transaction doesn't take place at a chip-reading device and is not a fallback transaction completed following correct acceptance procedures.

Read the negative carefully. A properly executed fallback is carved out of that rule. An improperly executed one isn't, so a bad fallback can expose you under two separate provisions at once.

What "correct acceptance procedures" includes#

The rules don't gather this into one list, but they do give a concrete piece of it. In the neighbouring liability provision, correct acceptance procedures are described as including obtaining online approval for transaction amounts over the applicable maximum authorized floor limit.

So the floor limit rules and the fallback rules meet here. Above your floor limit, an offline completion isn't a correct acceptance procedure, and a fallback completed that way fails the third condition before anyone looks at the message format.

Fallback is already banned in places#

Worth knowing how the direction of travel looks, because the US is currently an outlier.

In the Canada Region, an issuer or its agent must send a decline response to authorization requests for all domestic chip fallback transactions. In the LAC Region, the same applies to all domestic and intraregional chip fallback transactions, except in Puerto Rico and the US Virgin Islands (ID# 0029999).

In the Europe Region (United Kingdom), an unattended acceptance terminal must not process fallback transactions at all.

None of that binds a US merchant today. It does mean fallback is a shrinking mechanism rather than a stable one, and that a card issued in Canada may simply decline on the stripe no matter what your terminal does.

What your terminal has to be capable of#

For unattended terminals there's a hardware condition: such a device may support fallback transactions only if it has an integrated chip and magnetic-stripe reader.

The same acceptance device requirements table carries two neighbours worth knowing if you run unattended point of sale equipment. The device must support "No CVM required" for contact and signature for contactless, and it must require PIN or consumer device cardholder verification for quasi-cash transactions.

What to actually check#

This is a terminal configuration question, not a training question, and it's answerable in one conversation.

• Ask your processor whether your terminals send the fallback indicator. Specifically whether the authorization message identifies a fallback, not whether the terminal supports fallback. Those are different questions and only one of them moves liability.
• Confirm nothing completes offline above your floor limit. That breaks the third condition regardless of everything else.
• Look at your fallback rate. A reader that fails often enough to generate routine fallbacks is a hardware problem generating an ongoing liability exposure, and replacing it is cheaper than one disputed high-value sale.
• Don't let staff reach for the stripe first. A swipe that was never a chip attempt isn't fallback at all. It's a non-chip transaction at a chip-capable merchant, which is the worst position under the liability shift.

Source: Visa Core Rules and Visa Product and Service Rules, 18 April 2026.