The customer taps and the terminal asks for a PIN: why, and what to say

A customer taps their card, the terminal refuses contactless and asks them to insert and enter a PIN. The customer looks worried, the employee doesn't know what to say, and the line gets longer.

Nothing is broken, and nothing was declined. This behaviour is normal and intended. You just need to be able to explain it in one sentence.

Your terminal isn't the one deciding

This is the most important point and the most commonly misunderstood. Contactless limits are not a setting on your terminal, not a choice your business makes, and not a parameter your provider controls.

They are set by the payment network and by the financial institution that issued the customer's card. Your terminal simply applies what the card tells it. You cannot raise them, and neither can anyone at your provider.

Two limits, not one

The first is the per-transaction limit: the most a single sale can be in contactless mode. That is the one everyone knows about, and it has been raised over the years.

The second is the cumulative limit, and it is almost always the one causing the scene at the counter. It is the total a card can spend contactless before a chip-and-PIN transaction is required. According to Interac, that cumulative limit is set by each individual bank or credit union, so it varies from one customer to the next.

When the cumulative ceiling is reached, the customer has to insert the card and enter their PIN. That transaction resets the counter, and contactless works again afterward. It is a security measure: it limits what a lost card can spend before somebody proves who they are.

A customer whose card asks for a PIN does not have a balance problem. They have simply hit the cumulative ceiling their institution set.

Phones and watches behave differently

When a customer pays with a phone or a watch, the device asks them to authenticate before the exchange: a passcode, a pattern, a fingerprint or a face scan. Their identity has therefore already been verified on the device by the time it talks to your terminal.

That is why a mobile payment doesn't behave like a tapped plastic card, and why a customer can tell you, correctly, that "it always goes through" with their phone.

What staff should say, and what not to do

Wording matters. "Your card was declined" is untrue and embarrasses the customer in front of everyone. "The terminal is asking for your PIN on this one, please insert your card" is accurate and implies nothing.

Three habits to avoid:

• Tapping the card repeatedly. If the terminal wants the chip, it will keep wanting the chip.
• Splitting a sale into several smaller transactions to stay under the limit. Networks take a dim view of it, it multiplies your fixed per-transaction costs, and it weakens your position if the sale is ever disputed.
• Keying the card number in to work around it. A keyed-in transaction is treated as card-not-present: it costs more and exposes you to more risk.

What is genuinely in your control

You don't control the limits, but you do control three things that make a real difference to service speed.

Terminal placement, first. A device angled toward the customer and within easy reach cuts down on missed taps. Contactless requires the card to stay in front of the reader until the beep.

A PIN privacy shield, second, when the terminal is fixed on the counter: it stops customers hesitating to enter their code in public.

And training, above all. One sentence learned by heart turns an awkward moment into a three-second formality.

To do this week: at your next shift meeting, give your team the exact sentence to use when the terminal asks for a PIN. It is the smallest training there is, and one of the highest-return.