Why Do Card Payments Get Declined?

Every card authorisation comes back with a response code. An approval means the issuing bank has reserved the funds; a decline means the issuer, the network or the gateway has refused the transaction. Declines are a normal part of card processing, and the response code (or the decline category your payment provider maps it to) tells you whether the failure is worth retrying.

The most important distinction is between soft declines, which are temporary and may succeed on a later attempt, and hard declines, which are final and should never be retried on the same card.

What Are the Common Decline Categories?

• Insufficient funds – the account balance or credit limit cannot cover the amount. Very common on debit cards, especially just before month-end salary dates. Widely returned as response code 51.
• Do not honour – a general refusal by the issuer without a specific reason, often driven by the issuer's internal risk rules. Widely returned as response code 05.
• Expired card – the card's expiry date has passed. The customer needs a replacement card, which their bank has usually already issued.
• Suspected fraud – the issuer's fraud systems flagged the transaction, or the card has been reported lost or stolen. These declines are final and must not be retried.
• Incorrect details – the card number, expiry date or CVV entered at checkout is wrong. The fix is simply for the customer to re-enter the details carefully.
• 3D Secure failure – the cardholder failed or abandoned the authentication challenge (for example, never approved the prompt in their banking app), so the payment stopped before authorisation. See What Is 3D Secure?.
• Restricted card or transaction not permitted – the card is blocked for this type of transaction, for example online or international payments disabled on the customer's banking app, common on South African cards.

Soft Declines vs Hard Declines

Retrying hard declines wastes attempts, irritates issuers and can get a merchant flagged for excessive reattempts, as the card schemes monitor and penalise abusive retry behaviour.

How Should Merchants Handle Declines?

• Show the customer a helpful message. "Insufficient funds" and "incorrect card details" have obvious customer fixes; a generic "payment failed" causes abandonment.
• Let the customer retry or switch cards immediately at checkout for soft declines and detail errors.
• Check the customer's app settings. Many South African banks (Capitec, FNB, Standard Bank and others) let customers toggle online and international payments per card. A "transaction not permitted" decline is often solved in the banking app in seconds.
• Schedule smart retries for subscriptions. For recurring billing, retry soft declines on a schedule, for example around common salary dates, and stop after a few attempts. See Dunning and Payment Recovery.
• Keep saved card details fresh. Expired-card failures on stored cards can be reduced with account updater services and network tokens. See Backup Cards and Account Updaters.
• Never treat a decline as a payment. Only release goods on an approval confirmed by your payment provider, ideally via webhook.

Do Declines Cost the Merchant Money?

A declined authorisation does not move money, but declines still carry cost: lost sales, checkout abandonment and, for recurring merchants, involuntary churn. Improving approval rates through 3D Secure, tokenisation and sensible retry logic is usually one of the highest-value optimisations available to an online business. See Card Tokenisation and Network Tokens.

Related Topics

• Card payments hub
• What Happens During an Online Card Payment?
• Recurring Card Payments: CIT and MIT
• 3D Secure and Fraud Prevention