Every business has lived this moment: the card declines, the customer says "that's impossible, I just used it," and everyone stands there while the line grows. The terminal offers no help — just a code and a cryptic phrase like "Do Not Honor."
Here's the thing: the decline is almost never about you or your terminal. It's a message from the customer's bank, and once you know how to read it, the awkward moment gets a lot shorter. Here are the most common decline reasons in plain English — plus what to say and when a retry is worth it.
First, understand who's saying no
When a card declines, your terminal is just the messenger. The transaction traveled to the customer's bank, and the bank said no. Your processor can't override it, and neither can you. That matters at the counter: the useful next step is almost always on the customer's side of the conversation — their card, their bank, their phone.
The common codes, decoded
"Do Not Honor" (code 05)
The most common and least specific decline — the bank refused without saying why. Often it's a fraud-model hiccup: unusual location, unusual amount, too many transactions in a row. What to say: "Your bank declined it without a reason — a tap on your banking app or a quick call usually clears it." A second attempt a minute later sometimes works; a third rarely does.
Insufficient funds (code 51)
Exactly what it sounds like. Customers are often genuinely unaware. Offer to split the payment across two cards or take a smaller deposit — it saves the sale and the customer's dignity.
Expired card (code 54)
Simple fix — ask for a newer card. If you bill this customer on file, it's a nudge to enable automatic card updates, as covered in our recurring payments guide.
Suspected fraud (codes 59, 63)
The bank's fraud system flagged the transaction. The customer needs to verify with their bank — many banking apps let them approve the merchant instantly and retry on the spot.
Invalid number or CVC (codes 14, 82)
Almost always a typo on keyed-in transactions. Re-enter carefully — or better, send a payment link and let the customer type their own details.
Pickup card / stolen (codes 04, 41, 43)
The card is reported lost or stolen. Don't attempt it again, and don't play detective — just ask for another form of payment.
When retrying helps — and when it hurts
One retry after a soft decline like Do Not Honor is reasonable, especially if the customer has just approved the charge in their banking app. Hammering the same card five times is not — repeated attempts look like fraud probing to the bank's systems, can temporarily lock the customer's card, and on some pricing setups each attempt costs you an authorization fee.
A better second move: try a different method. Tap instead of swipe, a mobile wallet instead of the physical card — a different entry mode sometimes passes a check the first attempt failed, for the reasons covered in our guide to how acceptance method changes the transaction.
If declines are happening a lot
The occasional decline is normal. A pattern isn't. If your decline rate jumps, look for a common thread: keyed-in transactions missing ZIP codes, a terminal misconfiguration after an update, or — for card-on-file businesses — a stale vault full of expired cards.
We watch decline patterns for our merchants and flag the fixable ones. If declines feel more frequent than they should be, reach out or call 718-702-0186 and we'll pull your numbers and find the thread.