Also called: Declined transaction, Card decline, Payment decline
What a decline is
A decline is a card payment request that is refused before the sale is approved. For a typical card transaction, your payment system sends an authorization request through your acquirer and the card network to the customer’s issuer. The issuer checks the account and transaction, then returns an approval or decline.
The issuer is not the only possible source. Your processor, gateway, or merchant account settings can also block a transaction. A message such as “invalid merchant” or “card type not accepted” points to a setup or routing issue, while “insufficient funds” points to the cardholder’s account.
A decline code gives you a clue, not always the complete reason. Codes can differ between networks and payment systems, so use the code description shown for that transaction rather than assuming one number has the same meaning everywhere.
A decline code is a clue, not a diagnosis. Match your next step to the code and the pattern.
What a decline means for your business
The immediate cost is a sale you did not collect. A customer at your counter might use another card, but an online shopper can leave before trying again. For recurring billing, an expired card or insufficient funds can interrupt a payment until you collect updated details or the customer resolves the account issue.
A decline is not proof of fraud. Issuers also refuse legitimate purchases because of spending limits, unusual activity, or details that do not match their records. Blocking every suspicious-looking transaction can turn a false decline into lost revenue.
Repeated retries are not a harmless way to recover a sale. Visa and Mastercard have retry rules, and excessive attempts can trigger network fees. Follow the response guidance for the specific code and avoid sending the same failed payment repeatedly.
What the decline code tells you
Some common codes identify a clear next step. Code 51 means insufficient funds, so ask the customer to use another payment method or contact their bank. Code 54 means the card is expired, so request an updated card. Code 41 indicates a lost card and Code 43 a stolen card. Do not retry those cards.
Code 05, often displayed as “do not honor,” does not explain the issuer’s specific reason. Ask the customer to contact their bank or try another payment method. Code 91 indicates the issuer or switch is unavailable, which points to a temporary connection problem rather than an expired card or a confirmed lack of funds.
Compare the response text, code, payment channel, and time of each attempt. A cluster of “invalid merchant” or “transaction not permitted” messages across different customers points to a merchant setup issue. Repeated “insufficient funds” or expired-card responses point to customer account details instead.
Where decline handling goes wrong
Treating every decline as a customer problem wastes time and can hide a processing fault. If several cards fail in the same terminal or online checkout, review your accepted card types, account status, and payment system response before asking each customer to call their bank.
Do not tell a customer that a specific fraud rule or account condition caused the refusal unless the response actually says so. The code shown to your business often provides a category, not the issuer’s full decision. A calm explanation and another payment option help the customer complete a legitimate purchase without exposing private account details.
What you can actually change
- Read the response. Record the code and message for each failed attempt. Use the displayed code guidance because meanings can differ by network or payment system.
- Fix the right problem. Ask the customer to update expired or incorrect details, contact their bank, or use another payment method. For “invalid merchant” errors across customers, investigate your account or setup.
- Limit repeat attempts. Do not retry lost or stolen cards. For other declines, follow the applicable network and processor retry guidance instead of repeatedly resubmitting the same payment.
- Track patterns. Compare decline codes by terminal, checkout, and payment channel. A sudden cluster of similar errors can reveal a configuration or routing issue.
Frequently asked questions
Does a declined transaction mean the customer has no money?
No. Insufficient funds is one possible reason, but an issuer can also decline a purchase because of suspected fraud, an account limit, incorrect details, or unusual activity. A code such as 05, “do not honor,” does not reveal the exact reason.
Should I retry a declined card payment?
Only when the code and applicable network guidance support a retry. Do not retry cards reported lost or stolen. For an expired card or incorrect details, get corrected information; repeated attempts can trigger network retry fees.
Can a decline be caused by my payment setup?
Yes. Your processor, gateway, or merchant account settings can block a payment, including when a card type is not enabled or the account is restricted. If different customers receive similar setup-related errors, review your account configuration rather than treating each as an issuer decision.