A customer’s card was declined. Now what?

What is actually happening in a decline

In the two seconds after a tap, the authorization request travels from your terminal through your processor to the card network and lands at the issuing bank, where risk systems score it against the account's balance, limits, patterns and fraud models. Approve, and funds go on hold. Decline, and a response code comes back describing why, in the issuer's shorthand.

The point worth internalizing: the decline is the issuer's decision about their cardholder, not a judgment about your business or a malfunction of your equipment. Your terminal is the messenger. What you control is what happens next, and that turns entirely on reading the code correctly.

Soft versus hard: the only classification that matters

Soft declines are conditions that can change. Insufficient funds: the account is real but short today, and the same charge may clear after payday. Velocity or limit exceeded: the card hit a spending ceiling that resets. Try again later: the issuer's systems hiccupped. These are retryable, on the right schedule, and for recurring billing they are recoverable revenue.

Hard declines are conditions that will not change. Stolen or lost card, account closed, card expired against a replaced number, and the severe forms of do-not-honour. Retrying a hard decline never succeeds; it just tells the issuer's systems that transactions from your merchant account push against clear refusals, which drags your approval rate down across all customers.

The generic 'do not honour' code deserves its own note: it is the issuer declining without stating a reason, and it can be either soft or hard. Treat a single occurrence as soft, offer another method, and never hammer it with repeated attempts.

The counter script: saving the sale without the awkwardness

The customer at your counter is embarrassed, sometimes unjustly: declines happen to solvent people for boring reasons, a fraud model tripped by unusual travel, a daily tap limit, a bank outage. The staff move is quiet neutrality: 'That one didn't go through, do you want to try tap instead of insert, or another card?' No diagnosis aloud, no receipt waved around, no 'insufficient funds' announced to a queue.

Offer the ladder: try again once, try another entry method, try another card, try debit. Interac debit rides different rails with its own approval logic and rescues many stalled credit moments. For big-ticket sales, a deposit now by another method with the balance by payment link later keeps the deal alive. Every one of those beats the customer leaving to 'sort it out with the bank', because a meaningful share of them never come back.

For online and subscription businesses: recovery is a system

In e-commerce the decline meets the customer alone at a checkout, and the message you display decides the outcome. 'Your card was declined, please check the details or try another card' with the form intact converts far better than an error page that dumps the cart. Never echo raw issuer codes at a customer.

For recurring billing, declines are the mechanics of involuntary churn, and the recovery stack is well understood. Classify every failure: retry soft declines on a schedule that respects paydays and backs off over the cycle; never retry hard ones. Run an account updater so cards reissued after expiry or breach refresh silently instead of failing. And send dunning messages that assume good faith, a card update link, one tap, no shame, because most failed renewals are administrative, not intentional.

Businesses that build this stack typically recover a substantial share of failed recurring revenue that would otherwise silently churn, which for a subscription operation is margin found in the couch cushions.

RapidCents recurring billing ships with the retry engine, decline classification and Account Updater integrated, and the dashboard reports authorization rate by channel so a sagging approval rate shows up as a trend you can act on rather than a mystery you discover at quarter end.