Payment Decline Codes: What They Mean and How Businesses Should Respond

Payment decline codes are short numeric or text messages that explain why a card transaction did not go through. They are returned by payment processor or card issuer during authorization and help understand what went wrong: insufficient funds, incorrect card number, problems with card network, or something else. In this material, we will break down what credit card decline codes mean, how hard decline differs from soft decline, and what merchants should do to minimize declines.

Samuel  D’Souza
Samuel D’Souza·Marketing Lead
Updated: August 20, 2026
8 minutes to read
payment decline codes

What are payment decline codes?

Payment decline codes are response messages that are returned during authorization or processing. They can come from issuing bank, card network, or payment processor. Each code points to a specific reason why transaction decline occurred.

It is important to understand: decline codes may differ across different providers. Traditional decline codes exist, but their interpretation may differ. Therefore, you should not rely on universal tables as the final truth. Always check the documentation of your payment gateway or payment processor.

Card decline codes help businesses understand what exactly went wrong: a problem with card details, lack of available credit, suspicion of fraud, or something else. Error codes are not a verdict, but a hint where to look next. Response code gives direction for the next actions.

How a card payment decline happens

To understand what decline code is, you need to understand how card transaction works. Everything starts with checkout. The client enters credit card number, card expiration date, and CVV. Payment gateway sends authorization request. The request goes through acquiring bank and card network, such as Visa or Mastercard, to issuing bank — the bank that issued the card.

The issuing bank checks: whether there is available credit or money, whether the card is not blocked, whether there is suspicious activity. If everything is fine — approve. If not — decline. Card issuer returns decline reason and decline code.

The code returns through the same chain back: issuer → card network → acquirer → payment processor → payment gateway → your dashboard and checkout. It is exactly on this path that decline occurs and the code appears.

Payment gateway plays a key role in routing requests and processing card payments.

Ready to Accept Online Payments?

Hard decline vs soft decline

This is one of the most important differences for business. Hard decline and soft decline require a different approach.

Hard decline means that transaction should not be repeated without changes. This is a permanent decline. Examples: expired card, incorrect card number, card is blocked, credit limit exceeded. Hard decline occurs when the problem is not solved by retrying. If you see hard decline, repeat attempts will not help — they will only create extra requests and irritate the client. The client needs either to enter correct card details or use different card.

Soft decline is a temporary decline. It may be caused by technical problems on the issuer side, temporary unavailability of card network, or suspicious activity that requires additional confirmation. Soft decline can be retried after some time. The client can simply try again. Retry logic for soft decline works, but carefully: no more than 1–2 attempts, and with a pause between them.

Decline occurs for different reasons, and credit card decline codes will help determine what you are dealing with. Hard decline occurs usually for reasons that are not fixed by retrying. Soft decline may be resolved automatically. Decline reason is the main thing to look at.

Why payment declines happen

Insufficient funds or credit limit

The client exceeded the limit or there is no money on the account. Enough funds or available credit is the main condition for a successful transaction.

Card is expired

Card expiration date has passed.

Incorrect card data

Error in card number, CVV, or billing address.

Suspicion of fraud

Fraud protection was triggered. Card is suspected in fraud.

Unsupported card type or card network

Unsupported card network or card network associated with a region that you do not accept. Major card networks, such as Visa and Mastercard, have their own rules.

Country or MCC restrictions

Transaction decline because of geographic or category restrictions.

Technical problems on the issuer side

Issuing bank has declined because of a failure.

Authentication error

The client did not pass verification.

Common payment decline codes and what they mean

Codes 05, 12 and 14: generic or invalid transaction details

Decline code 05 is “Do not honor”. This is a general issuer decline. It can mean anything: from insufficient funds to suspicion of fraud. Decline code 12 is “Invalid transaction”. Incorrect format or transaction parameters. Decline code 14 is “Invalid card number”. Card number does not exist or was entered with an error.

What to do: check card number, billing details, amount, and currency. If everything is correct, ask the client to use different card or another payment method. Issuer decline often requires client intervention — they need to call the bank.

Card declines can occur because of typos. Incorrect card number is one of the most frequent reasons. Decline reason 14 almost always means that credit card number doesn't exist or does not match the format.

Codes 51, 54 and 57: funds, expiry and transaction restrictions

Decline code 51 is “Insufficient funds”. There is not enough money on the card or available credit is exhausted. Credit card over the limit is also a frequent reason. Decline code 54 is “Expired card”. Card expiration date has passed. The client needs to update card details. Decline code 57 is “Transaction not permitted”. Card issuer does not allow this type of transaction. There may be a restriction by country, by MCC code, or by operation type.

What to do: for 51 — the client must top up the account or use another card. For 54 — update card information in the system. For 57 — the client must contact the bank and clarify why the operation is prohibited. Credit limit and available credit are what the client controls, and you do not.

Decline code 51 is one of the most frequent card decline codes. Expired card is another common reason for declines. Transaction not permitted may be connected with security settings on the issuer side.

Codes 82 and 91: verification or issuer availability issues

Decline code 82 is a card verification error, CVV. The client entered the security code incorrectly. Decline code 91 is “Issuer unavailable”. The client’s bank is not responding. This is a technical problem on the issuer side.

What to do: for 82 — the client must check CVV and enter it again. For 91 — wait and try later. Card verification and authentication are key security elements. Issuer decline 91 is a temporary problem. Retry logic is appropriate here.

Decline code 82 is often called CVV decline. Card issuer cannot process the request at the moment.

payment decline codes

What merchants should do when a payment is declined

Read the response code

Look at decline code and decline reason in dashboard. Do not ignore it.

Determine hard vs soft decline

If hard decline — do not retry. If soft — you can try again after some time.

Do not retry blindly

Blind repeat attempts are a bad practice. They increase the load on payment processor and irritate the client. Retry logic must be thought through.

Show the client a clear message

On checkout, write what went wrong. Do not show the code — show a human wording: “Insufficient funds” or “Incorrect CVV”.

Ask the client to correct the data or use another card

Different card or alternative payment method often solves the problem. Card to complete the transaction must be valid.

Offer alternative payment methods

If the card does not go through — offer bank transfer, digital wallet, or other methods.

Log failed-payment reason

Keep records of declines. This will help analyze reasons and improve checkout.

Escalate problems to processor or issuer

If the problem repeats and is not solved — contact payment processor support.

How to reduce payment decline rates

Clean card data

Use validation on checkout: check card number, card expiration date, CVV. This reduces input errors.

Clear billing fields

Make sure the client enters the address correctly. Card verification through AVS, Address Verification System, reduces the risk of declines.

Tokenization and saved cards

Tokenization allows storing card information securely. Account updater automatically updates card data when card expiration date changes.

Smart retries for soft declines

Set up retry logic: for soft decline, automatic repeat attempts after an hour or a day.

Local and alternative methods

If the card does not go through, offer alternative payment method — bank transfer, digital wallet, local payment methods. This reduces dependence on cards.

Routing and acquirer strategy

Use payment gateway with intelligent routing. If one acquirer does not work — try another. Credit networks may have different rules.

Fraud rules tuned

Configure fraud protection so that it does not block real transactions. False positives are one of the frequent reasons for declines.

Monitoring by decline reason

Track decline codes in dashboard. Analyze which reasons dominate and work with them.

How decline codes help payment operations and reporting

Decline code is not just a number. It is data. And it must be used.

Reporting dashboard must show not only the number of declines, but also their distribution by reasons. This helps understand where the bottlenecks are.

Response code analytics allows seeing: whether this is a problem of a specific issuer, a temporary failure of card network, or a system error on the payment processor side.

Data on declines helps improve fraud protection: if there are many false positives — reconfigure the rules. If there are many declines by 51 — perhaps your audience is solvent, but credit limits are low.

Segmentation by method, country, card type, BIN, device gives deep understanding. For example, declines by card network may point to problems with a specific processor.

Decline codes are your compass in the world of payment operations. They help not to guess, but to act based on facts. Codes occur with different frequency depending on the region.

payment decline codes

Frequently Asked Questions