Hard Decline

A hard decline is a refusal of a card authorization for a reason that will not change if the merchant tries again. The card may have been reported lost or stolen, the account may be closed, the card number may not exist, or the issuer may have blocked the card or the merchant. The issuing bank returns a response code that, read correctly, tells the merchant to stop and seek another way to be paid.

Like its opposite, the soft decline, "hard decline" is a working term used by merchants, acquirers and payment gateways rather than a single code in the network rules. Visa's decline categories call this group declines where the issuer "will never approve", and Mastercard flags many of them with a "do not try again" advice code. Both are subsets of the wider payment decline, and the distinction decides whether a retry is allowed at all.

Picture trying to pay a bill with a cheque from an account the bank has already closed. It does not matter how politely you ask, or how many times you hand it over: the answer will always be no. The only fix is a different account.

A hard decline is the card version of that closed account. The bank behind the card is saying, in effect, "this card cannot be used, full stop". Perhaps it was reported stolen, or it has been replaced with a new number. For the shop, the sensible response is to stop trying that card and ask the customer for another way to pay, rather than pressing the button again and again.

Response codes come from the ISO 8583 standard used for card authorization messages, with network-specific additions. Codes generally treated as hard include:

• Lost card (41) and stolen card (43). The card has been reported and blocked. These are also "pick up card" codes, telling a staffed store to keep the card if possible.
• Invalid card number (14) and no such issuer (15). The number fails validation or does not match a known bank identification number, often because of a typo or a made-up number.
• Expired card (54). The card is past its expiry date. Retrying the same details will fail, but the customer, an account updater service or a network token can supply the current details.
• Closed account or revoked authorization. The account no longer exists, or the cardholder has told the issuer to stop payments to the merchant, for example after cancelling a subscription.
• Transaction not permitted (57). The card is not allowed to be used for this kind of purchase, such as a card blocked for gambling or for cross-border spending.

Retrying a hard decline cannot succeed and loads issuer systems with pointless traffic. Repeated attempts on blocked cards are also a classic sign of card testing and other payment fraud. For both reasons the networks discourage it. Visa charges fees when merchants reattempt a transaction declined with a code in its "never approve" category, and Mastercard charges when merchants ignore merchant advice codes telling them not to try again. As of November 2026 these fees are charged to acquirers and passed on to merchants; amounts and rules change, so the current schedule should be checked with the acquirer. Merchants that keep retrying can also see more of their good transactions declined, as issuers' risk systems learn to distrust their traffic.

1. Stop automated retries. Payment systems should map hard decline codes and advice codes to "do not retry" and block further attempts on that card.
2. Tell the customer clearly but generally. At checkout, ask for another card without naming the reason; telling a shopper "your card is reported stolen" can help a fraudster and embarrass a genuine customer.
3. Update stored details. For card-on-file transactions and recurring payments, use account updater services or network tokens to pick up reissued cards, then ask the customer to update the card if that fails.
4. Review fraud signals. A cluster of lost, stolen or invalid-card declines from one IP address or device usually points to an attack, and velocity checks or rate limits should be tightened.
5. Offer alternatives. Another card, a digital wallet or a bank transfer can save the sale.

A high share of hard declines lowers a merchant's approval rate and often reflects a data problem rather than bad customers: old stored cards, poor input validation or misflagged merchant initiated transactions that issuers no longer recognise. Breaking the decline rate down into hard and soft, and by code, helps teams pick the right fix. Unlike a soft decline, a hard decline rarely needs a better retry strategy; it needs better data or a different payment method. The same thinking applies across providers, so routing a hard-declined card to a second acquirer through multi-acquirer processing will not change the issuer's answer and may itself count as an excessive retry.

• Visa
• Mastercard
• International Organization for Standardization (ISO)