---
title: "Hard Decline"
url: "https://mahouse.world/glossary/hard-decline"
type: "glossary term"
topic: "Payments performance"
author: "Ihor Vlasov"
reviewed: "2026-09-20"
published: "2026-08-10"
---

# Hard Decline

A hard decline is an issuer's refusal of a payment for a reason that will not change if the merchant tries again — the card is reported lost or stolen, the account is closed, the number is invalid, the transaction type is not permitted — as opposed to a soft decline, where the reason is temporary. The schemes prohibit retrying hard declines; the right response is to stop and, for a stored card, ask for another.

**Also known as:** Permanent decline, Do-not-retry decline, Hard decline code

## Key facts

- **Used at:** every authorisation response; the decline code tells the merchant which kind it is, and the merchant's retry logic branches on it
- **Binding:** the scheme rules — Visa and Mastercard classify decline codes into categories with retry rules; Visa's 2021 rules bar retrying category-1 declines ("do not honour" with specific sub-codes, lost/stolen, closed account, invalid card) and charge acquirers for excessive reattempts
- **Typical hard decline codes:** lost or stolen card (41, 43), closed account (46), invalid card number (14), pick-up card (04), transaction not permitted (57), expired card (54 — hard for that card, but an account updater may supply the replacement), fraud-flagged by issuer (59, 63)
- **Typical share:** 15–30% of e-commerce declines are hard; the rest are soft and recoverable
- **Parties:** the issuer (which decides and codes), the network (which classifies and polices retries), the acquirer (which is fined), and the merchant (which must handle the code correctly)

## How a hard decline works in practice

A renewal is submitted on a stored card and the issuer responds with code 41, lost card. The card has been reported; the customer has a new one. Retrying tomorrow will produce code 41 again, and after a few attempts the scheme's monitoring counts the merchant's excessive reattempts and the acquirer receives a fee per retry, which it passes on. The correct flow: stop; check the account updater or network token service, which may already hold the replacement card; if not, dunning — email the customer, prompt in the app, and update the stored credential when she responds. The subscription survives if the customer does; the card does not.

The distinction from soft declines is the whole retry design. "Insufficient funds", "issuer unavailable", "do not honour" (in most sub-codes) and "exceeds limit" may change tomorrow; "stolen", "closed", "invalid" will not. A merchant's retry engine reads the code, classifies it, and retries only the soft ones on a schedule the schemes allow; hard declines go straight to recovery by other means. Where a merchant's classification is wrong — treating "do not honour" as hard, or "stolen" as soft — it either loses recoverable revenue or pays retry penalties, and both show in the numbers.

For a fraud team a hard decline on a card in the merchant's own systems is also a signal: a stored card reported stolen may mean the account holding it was taken over.

## Example

A subscription service's retry engine treats all declines alike and retries each up to eight times over 14 days. Of its 20,000 monthly declines, 5,000 are hard; the engine attempts 40,000 retries on them, all declined. Its acquirer passes on Visa's excessive-reattempt fees — $0.10 each on the reattempts beyond the allowance — about $3,000 a month — and a warning letter. The service rebuilds the engine: hard codes go to the account updater and then to dunning; soft codes retry on a schedule tuned by code and issuer. Fees stop; recovery on soft declines rises because the retries are better timed; and the account updater supplies replacement cards for 30% of the "lost or stolen" declines, which had been churned outright before.

## Common mistakes

- Retrying hard declines, which costs fees and issuer goodwill and recovers nothing.
- Classifying decline codes by a list copied from a blog rather than from the schemes' current tables.
- Treating "expired card" as final without checking the account updater.
- No dunning path for hard declines, so a customer with a new card is lost by default.
- Ignoring hard declines on stored cards as a fraud signal.

## Related terms

- [Soft Decline](https://mahouse.world/glossary/soft-decline.md)
- [Decline Recovery](https://mahouse.world/glossary/decline-recovery.md)
- [Retry Logic](https://mahouse.world/glossary/retry-logic.md)
- [Approval Rate](https://mahouse.world/glossary/approval-rate.md)
- [Decline Rate](https://mahouse.world/glossary/decline-rate.md)
- [Chargeback Reason Code](https://mahouse.world/glossary/chargeback-reason-code.md)

— Ihor Vlasov, M&A FinTech Expert. Last reviewed 2026-09-20. https://mahouse.world/authors/ihor-vlasov