Payment Decline
Payment Decline — Definition & Guide
A payment decline is a failed authorization in which the issuing bank refuses to approve a transaction. Declines occur for a range of reasons — insufficient funds, suspected fraud, expired card details, daily spending limits, or geographic restrictions — and are communicated back to the terminal via a numeric reason code. Visa publishes a full reference of payment response codes and decline reasons that govern how declines are classified and handled.
A payment decline means the card’s issuing bank said no to an authorization request. It does not automatically mean fraud or a bad customer — cards get declined for routine reasons like a spending limit being reached, an incorrect CVV entry, or the bank flagging an unusual purchase location. The challenge for merchants is handling the situation professionally without embarrassing the customer or revealing unnecessary detail about why the card did not go through.
Declines fall into two categories. A hard decline is permanent — the card is closed, reported stolen, or the account has been flagged in a way that will not change on retry. A soft decline is temporary — insufficient funds, a daily limit hit, or a bank hold that can often be resolved with one call to the issuer. Knowing the difference tells you whether to try again or move on.
Most processors pass decline codes back to the terminal. Code 05 (“Do Not Honor”) is the most common soft decline. Code 41 (“Lost Card”) and Code 43 (“Stolen Card”) are hard declines that should not be retried. Understanding the basic split between hard and soft declines is enough for day-to-day operations — your processor’s documentation will have the full code reference.
Here is the flow of a typical payment decline scenario:
The entire authorization cycle happens in under two seconds. The merchant never knows the specific reason beyond the code — card network rules prohibit sharing most decline details with the cardholder. The standard merchant response is simply “it did not go through” and offering an alternative payment method.
Permanent refusal. Card is stolen, closed, or flagged. Do not retry. Examples: codes 41, 43, 62.
Temporary refusal. Funds, limits, or holds. May succeed on retry or after customer contacts their bank. Example: code 05.
Most declines fall into a handful of predictable categories:
The most common decline. The cardholder’s account does not have enough available credit or funds. Ask for an alternative payment method — retrying the same card declined will not help.
A catch-all soft decline from the issuing bank. Could be a fraud flag, unusual activity, or a bank-side hold. The cardholder should call their bank to resolve. May succeed on retry after resolution.
The card number entered does not pass basic validation. Usually a keying error on manual entry. Ask the customer to recheck their card number and try again.
The card’s expiration date has passed. The cardholder needs to use their replacement card. For recurring billing, this is one of the most common reasons subscriptions fail — update stored card data proactively.
Hard declines. The card has been reported lost or stolen. Do not retry. If the card is physically present and the terminal prompts card retention, follow your processor’s guidelines.
The transaction exceeds the cardholder’s daily spending or withdrawal limit. The customer may be able to resolve this by calling their bank to raise the limit, or by splitting the transaction.
The card is restricted for certain transaction types — common with corporate cards, prepaid cards, or cards with category-specific spending controls.
A hard decline indicating the issuer wants the card retrieved. Follow your processor’s card retention procedures. Never accuse the cardholder directly.
A hard decline is permanent — the card is stolen, closed, or flagged in a way that will not change. Do not retry. A soft decline is temporary — insufficient funds, a spending limit, or a bank hold. These may succeed if retried after the customer contacts their bank.
Yes — politely. Avoid explaining the decline code or speculating about the reason. Simply say it did not go through and offer an alternative. Card network rules restrict what details merchants can share with cardholders.
Once for soft declines. Card network rules prohibit excessive retries and can result in fees for non-compliant retry practices. Never retry a hard decline — doing so can flag your merchant account for excessive retry violations.
Declines themselves do not — they are a normal part of processing. What affects account standing is an elevated chargeback ratio, which happens when customers dispute charges rather than declining at the point of sale.
Card-not-present transactions carry higher fraud risk, so issuers apply stricter scrutiny. Without a physical card and PIN, the bank relies on AVS, CVV, and behavioral signals to approve or decline. Decline rates for e-commerce are consistently higher than card-present environments.
An Unusual Decline Pattern Is Almost Always Diagnosable from Your Statement.
Send us your last processing statement. We will identify the decline-code pattern, separate true card-issuer declines from processor-side soft-declines, and show you what configuration or routing changes would recover the legitimate transactions.
Request a Free Statement ReviewNo obligation • For glossary readers comparing pricing models and processor options • Response within one business day