Guides

Credit card decline codes

A practical guide for merchants

A decline code is the issuing bank's short explanation for why a card authorization failed. Your payment gateway returns it instead of an approval so you can coach the customer, decide whether to retry, and spot fraud or configuration issues. For how authorization fits into the broader payment flow, see how credit card processing works.

This guide walks through soft vs hard declines, what to do at the register or checkout, and the patterns that signal a bigger problem, plus a searchable directory when you need to look up a specific code.

Use Decline Code Lookup Tool

Declined credit card payment at checkout

Soft declines vs hard declines

Most merchant-facing declines fall into two buckets. Knowing which you have changes the next operational step.

Soft

Often retryable

Temporary issues like insufficient funds, activity limits, or issuer timeouts. Ask the customer to try again later, use another card, or lower the amount when appropriate.

Hard

Usually stop

Problems like invalid card number, expired card, or do-not-honor with fraud/risk flags. Retrying the same data rarely helps. Collect a different card or have the customer contact their bank.

What to do when a sale declines

  1. Read the code and message. “Insufficient funds” and “do not honor” need different scripts for your customer.
  2. Decide soft vs hard. Soft: one careful retry or another payment method. Hard: do not hammer the same card.
  3. Check your filters. A spike in CVV/AVS failures may mean bad data entry, or card testing.
  4. Coach the customer clearly. Tell them whether to retry, update the card, or call their bank.
  5. Watch trends weekly. One decline is noise. A surge in a single code is a signal.

Decline patterns that signal a bigger problem

One decline is normal. These patterns usually mean something upstream needs attention.

Fraud

Sudden CVV / do-not-honor spikes

Often card testing or stolen-card traffic. Tighten velocity limits and review fraud prevention settings.

Ops

Expired card on renewals

Recurring billing needs card-updater flows and customer reminders before the renewal attempt fails.

Config

One code across many cards

Can point to gateway misconfiguration, MCC issues, or an issuer/network outage, not just “bad customers.”

Risk

Forced sales that later charge back

Pushing past hard declines can create disputes later. Declines are sometimes protecting your ratio.

Read the chargebacks guide

Common decline codes

These are the responses merchants see most often. Use this as a quick scan, then open the full directory below when you need a less common code.

CodeNameTypeWhat to do
05Do not honorHardAsk the customer to contact their bank or try another card. Review fraud filters if 05 declines spike.
14Invalid card numberHardHave the customer re-enter the number carefully or use a different card.
51Insufficient fundsSoftAsk the customer to use another payment method or retry later.
54Expired cardHardCollect an updated expiration date or a new card for recurring billing.
61Exceeds withdrawal limitSoftTry a lower amount, split payment if appropriate, or use another card.
65Activity limit exceededSoftRetry later or request another payment method; review for card testing patterns.

Responses can vary by issuer and gateway wording. If a code is missing here, use the full directory below.

Decline code lookup

Type a code or keyword to filter the directory. Messaging can vary by network and processor. When in doubt, use the full response text from your gateway log. Linked codes and names open a deeper Zen article when one is available.

Showing 48 of 48 codes

CodeName
00informational

Approved

informational

Authorization approved (not a decline). Proceed with the sale.

01soft

Refer to card issuer

soft

Issuer wants the merchant or cardholder to contact the bank. Ask the customer to call the number on the back of the card, then retry.

02soft

Refer to issuer (special)

soft

Similar to 01 with a special-condition referral. Have the customer contact their bank before retrying.

03hard

Invalid merchant

hard

Merchant ID or terminal configuration is not accepted for this transaction. Contact your processor. Often an account or MCC configuration issue.

04hard

Pick up card

hard

Issuer requests the card be retained (fraud or compromised card). Do not retry. For card-present, follow pickup procedures; online, stop the sale.

Do not honor

hard

The issuing bank declined without a more specific reason. Often related to risk rules, suspected fraud, or account restrictions. Ask the customer to contact their bank or try another card. Review fraud filters if 05 declines spike.

06soft

Error

soft

General error response from the issuer or switch. Retry once; if it continues, try another card or contact support.

07hard

Pick up card (special)

hard

Issuer requests card pickup for special conditions. Do not retry the same card.

10informational

Partial approval

informational

Issuer approved only part of the requested amount. Capture the approved amount or cancel and collect another tender for the balance.

12hard

Invalid transaction

hard

Transaction type is not allowed for this card or merchant. Verify transaction type, MCC, and card product support.

13hard

Invalid amount

hard

Amount is invalid or outside allowed limits. Check formatting, currency, and ticket size rules.

14hard

Invalid card number

hard

The card number failed validation or was entered incorrectly. Have the customer re-enter the number carefully or use a different card.

15hard

No such issuer

hard

BIN does not map to a known issuing bank. Re-check the card number; try another card.

19soft

Re-enter transaction

soft

Temporary issue; issuer asks to try again. Retry the authorization once.

21soft

No action taken

soft

Issuer did not take action on the request. Review gateway logs; retry or use another method.

30hard

Format error

hard

Message format or required field failed validation. Usually a gateway/integration bug. Escalate to technical support.

41hard

Lost card

hard

Card reported lost. Do not retry. Ask for another payment method.

43hard

Stolen card

hard

Card reported stolen. Do not retry. Treat as high fraud risk.

46hard

Closed account

hard

The account is closed. Request a different card.

51soft

Insufficient funds

soft

The account does not have enough available balance for the purchase. Ask the customer to use another payment method or retry later.

52hard

No checking account

hard

No checking account associated with the card. Use another card or payment method.

53hard

No savings account

hard

No savings account associated with the card. Use another card or payment method.

Expired card

hard

The expiration date on file is past due. Collect an updated expiration date or a new card for recurring billing.

55soft

Incorrect PIN

soft

PIN verification failed. Allow a PIN retry if card-present; otherwise use another method.

Transaction not permitted to cardholder

hard

Issuer blocks this transaction type for the cardholder. Ask the customer to enable the transaction type with their bank or use another card.

58hard

Transaction not permitted to terminal

hard

Merchant/terminal is not allowed to process this transaction type. Contact your processor about MCC, terminal, or capability settings.

59hard

Suspected fraud

hard

Issuer flagged the authorization as potentially fraudulent. Do not force the sale. Ask for another card and review fraud controls.

61soft

Exceeds withdrawal limit

soft

The transaction exceeds the cardholder's available limit or velocity rules. Try a lower amount, split payment if appropriate, or use another card.

62hard

Restricted card

hard

Card is restricted (region, product, or status). Customer should contact their bank; try another card.

63hard

Security violation

hard

Security data failed validation. Re-check AVS/CVV and card data; do not store CVV.

Activity limit exceeded

soft

Too many transactions or spend on the card in a period. Retry later or request another payment method; review for card testing patterns.

75hard

PIN tries exceeded

hard

Too many incorrect PIN attempts. Customer must unlock/reset with their bank.

76hard

Invalid / nonexistent account

hard

Account specified is invalid. Re-enter card details or use another card.

77hard

Inconsistent with original

hard

Reversal or follow-up does not match the original transaction. Escalate to gateway support with reference IDs.

78soft

Blocked / first use

soft

Card blocked pending activation or first use. Customer should activate the card with their bank, then retry.

80soft

Credit issuer unavailable

soft

Credit issuer system unavailable. Retry later or use another card.

82hard

Negative CAM / CVV failure

hard

Security code or policy check failed (wording varies by network). Confirm CVV and billing details; do not store CVV after authorization.

85informational

No reason to decline / AVS-only

informational

Often used when AVS is checked without a purchase authorization. Interpret with your gateway docs; may not mean the sale failed.

91soft

Issuer unavailable

soft

The issuing bank or network could not be reached in time. Retry once after a short wait; if persistent, ask for another card.

92soft

Unable to route

soft

Transaction could not be routed to the issuer. Retry later; if persistent, verify BIN/network support.

93hard

Violation / cannot complete

hard

Legal or network violation prevents completion. Do not retry without processor guidance.

94informational

Duplicate transmission

informational

Duplicate of a recent authorization was detected. Check whether the first attempt already approved before retrying.

96soft

System malfunction

soft

Issuer or network system error. Retry once later; escalate if widespread.

97informational

Reconciliation error

informational

Settlement/reconciliation mismatch response. Usually back-office. Contact processor support.

N7hard

CVV2 failure

hard

Visa-style CVV2 mismatch (code varies by processor display). Re-enter the security code; confirm card-not-present data.

R0hard

Stop recurring payment

hard

Cardholder requested stop on recurring charges. Cancel the subscription and confirm with the customer.

R1hard

Revocation of authorization

hard

Cardholder revoked authorization for recurring charges. Stop future billing on that credential.

R3hard

Revocation of all authorizations

hard

All authorizations for the merchant revoked by cardholder. Stop billing and obtain a new payment method intentionally.

Guide FAQ

Frequently asked questions

Common questions about decline codes, retries, and what they mean for your approval rate.

Only when the code suggests a soft decline (temporary funds issues, limits, or issuer timeouts). Hard declines and clear fraud responses should not be retried with the same card data.

Networks and gateways map issuer responses slightly differently. Treat the code plus the full response text as the source of truth for that processor.

Yes. Issuers use merchant category signals in risk models. Wrong or high-scrutiny coding can lower approval rates. Review MCC codes if declines cluster after boarding or a product change.

A decline happens before the sale is captured. A chargeback happens after settlement when the cardholder disputes the charge. Preventing bad authorizations is one of the cleanest ways to reduce later disputes.

Still have questions? Contact our support team

Need help interpreting declines?

Zen Payments helps ecommerce and high-risk merchants configure gateways, read decline patterns, and keep approval rates healthy. Call 877-715-4501 or fill out the form to get started.

Get started with Zen Payments
Fill out this form and a merchant services representative will be in touch!
Phone Number

Already filled out a form?  Login

Zen Logo
Feel free to reach out to us with questions or for general support, available 24 hours, 7 days a week!
email iconsales@zenpayments.comphone icon(877)-715-4501Partner Login
© 2026 Zen Payments | All rights reserved
By using this site, you agree to our Privacy Policy and Terms of Service.
Credit Card Decline Code Lookup - Zen Payments