What is a Hard Decline in Card Payments?

A hard decline is a card payment refusal that's permanent. The issuer has told the merchant "no" for a reason that won't resolve itself — the card has been reported lost or stolen, the account's closed, the issuer suspects fraud, or it's a flat do-not-honour instruction. Unlike a soft decline, retrying a hard decline doesn't help. It piles up decline fees, annoys the customer, and can flag the merchant account for fraud monitoring. The right move is to stop retrying and offer an alternative payment route.

The distinction between soft and hard declines isn't just terminology. Card schemes treat them as fundamentally different signals, and the way a merchant responds to each has outsized effects on authorisation rates, fees, and even merchant-account standing. Hard declines are the ones you can't out-retry.

What Makes a Decline "Hard"

A hard decline is the issuer's way of saying the transaction shouldn't go through and isn't going to go through. The card might be physically in the customer's wallet, but as far as the issuer's authorisation system is concerned, that card is dead for new transactions. The reasons fall into a few buckets.

Fraud-related: the card has been reported stolen, the issuer's fraud team has frozen it, or the transaction pattern has tripped a model that says "this isn't the cardholder." Once that decision lands, no amount of retrying changes it. The cardholder has to talk to their bank.

Account-status-related: the card account's been closed, written off, or charged off. The plastic might still be in someone's pocket, but the account behind it doesn't exist any more.

Card-status-related: the cardholder reported the card lost or stolen, the issuer cancelled it and sent out a new one. The old number is now hot — any attempt to use it is itself a potential fraud signal.

Issuer judgment: "do not honour" is a catch-all code (05) issuers use when they don't want to give a more specific reason. Often it's a fraud suspicion they don't want to disclose, but it can also be a credit-line problem or an account flag the cardholder isn't aware of. Whatever the cause, the answer is the same: don't retry.

Common Hard Decline Codes

The ISO 8583 response codes you'll see flagged as hard by virtually every payment processor:

• 04 — Pick up card. The issuer wants the card confiscated. In a face-to-face context, the merchant is instructed to retain the card. In a CNP context, just abandon the attempt.
• 05 — Do not honour. The generic refusal. The issuer isn't disclosing the reason, but they're clear the transaction shouldn't go through.
• 07 — Pick up card, special conditions. Same as 04 but typically signals a fraud suspicion.
• 12 — Invalid transaction. The transaction itself isn't acceptable to the issuer — wrong type for the card, prohibited merchant category, etc.
• 14 — Invalid card number. The number isn't a valid card. Either it was typed incorrectly (rare for a CNP retry where the number's stored) or the card never existed / has been deactivated.
• 15 — No such issuer. The BIN doesn't route to any known issuer. Bad card data.
• 41 — Lost card. Cardholder has reported it lost. Don't retry, ask for another card.
• 43 — Stolen card. Cardholder has reported it stolen. Same response, with extra urgency on the fraud-monitoring side.
• 54 — Expired card. The card's expiry date has passed and no Card Account Updater data is available. The customer needs to provide a new card.
• 57 — Transaction not permitted to cardholder. The card isn't allowed to make this type of transaction. Permanent for this card.
• 62 — Restricted card when it surfaces as a hard variant — e.g. cards barred from certain merchant categories.
• R0 / R1 / R3 — Stop payment / revocation of authorisation. The cardholder has formally revoked recurring billing consent. Continuing to charge after this is a chargeback magnet.

The lookups aren't perfectly standardised between Visa, Mastercard, Amex, and Discover, but the soft-vs-hard classification is. Every modern payment platform maintains the mapping so the merchant doesn't have to.

Why Retrying a Hard Decline Is Actively Bad

Three things happen when a merchant keeps hammering a hard-declined card.

First, decline fees stack up. Most acquirers charge a small fee per declined authorisation attempt — typically a few pence — and on a high-volume merchant those add up fast for no upside.

Second, fraud monitoring activates. Card networks watch for the pattern of "merchant attempts payment, gets hard decline, immediately retries, gets hard decline again." Repeat that enough on cards flagged as lost or stolen and you'll find your merchant account on a watchlist or, worse, temporarily suspended for review. Visa's Account Information Inquiry programme and Mastercard's equivalent both specifically target merchants whose retry behaviour looks like card testing.

Third, the customer experience falls apart. The customer's bank may push a fraud alert to their app on the second attempt. By the third, you've turned a recoverable lost-card situation ("just give me your new card number") into a deeply uncomfortable conversation about why their bank thinks your business is suspicious.

The Right Response to a Hard Decline

Stop retrying. Move on. Offer the customer a different payment route — another card, a bank transfer, a payment link they can use later, or for recurring billing, ask the customer to update their card on file before the next charge attempt. On the customer-facing side, the message should be polite, short, and free of speculation: "That payment didn't go through. Can you try a different card, or we can send you a payment link to complete this later."

What you shouldn't do is tell the customer their card is fraudulent, blocked, or stolen — even if the code suggests it. Card issuers don't always disclose the reason, and a wrong guess is the kind of thing that ends up in a complaint or on social media. The agent's role is to acknowledge the decline and offer a route forward, not to diagnose the bank's decision.

Hard Declines on Recurring Billing

Recurring billing makes hard declines more consequential because the merchant doesn't have the customer on the phone. A hard decline on a monthly subscription charge needs to trigger an automated customer-update flow — email, SMS, in-app prompt — rather than a retry loop. Card Account Updater (Visa Account Updater, Mastercard Automatic Billing Updater) helps in cases where the issuer reissued the card, but it doesn't cover account closures, fraud freezes, or revoked-consent cases. Those need the customer back in the loop.