What Are Credit Card Decline Codes?

A credit card decline code is the short code an issuer or network returns at authorization to explain why a charge failed, and the guide covers the most common codes across Visa, Mastercard, Amex, and Discover plus what to do about each.

‍A credit card decline code is the short code a card issuer or network sends back when it won't authorize a transaction, naming why the charge failed. Your processor passes that code to you in the authorization response, and each network numbers those reasons differently.

Decline codes apply only at authorization, before a charge settles. That makes them a separate thing from the chargeback reason codes on a charge that already settled and then got disputed.

Common credit card decline codes and what they mean

Most declines come from an empty account, a decline the issuer won't explain, a fraud flag, a wrong security code or account number, or an expired card. Code 51, the most-searched of them, means "Not sufficient funds."

Sort the codes by reason. The reason tells you what to do next. Here are the codes Visa publishes, in Visa's own wording, for the reasons you'll hit most:

CodeWhat Visa says it meansWhat it tells you
51Not sufficient fundsThe card works, the money isn't there right now
05Do not honorRefused, with the reason withheld from you
59Suspected fraudThe issuer flagged this charge, not the card details
54Expired card or expiration date is missingYour stored card data is stale
14Invalid account number (no such number)The number is wrong or was mistyped
N7Decline for CVV2 failureThe security code didn't match
04, 41, 43Pick up card, lost card pick up, and stolen card pick upThe issuer wants that card out of use

Mastercard, Amex, and Discover number their own responses separately, and the numbers don't always line up. Pull the exact mapping for those networks from your processor's response reference.

Many two-digit codes overlap, because the networks build on the same messaging standard.

A few codes tell you nothing useful. Code 05 and referral responses hide the issuer's reason, and nothing you change at checkout will reveal it.

Those declines need the cardholder to call their own bank.

Why decline codes matter for chargeback risk

Retrying without fixing the cause, and never telling the customer why their card failed, is how a routine failed authorization becomes a dispute. What you do after the decline creates the risk.

Think about what the cardholder sees:

  • Several declined attempts land on their account over a few days.
  • One charge finally goes through, and nothing you sent explains it.
  • A billing descriptor they don't recognize sits next to the amount.

So they call their bank and say they didn't authorize it. That's friendly fraud, and it starts with a customer who can't place the charge.

The same confusion produces disputes after settlement too, just later in the timeline.

One informed retry doesn't carry this risk. Fix the real cause, tell the customer what you're charging, and the second attempt stays routine.

How merchants should respond to a decline

Read the code first, because whether it's a soft or hard decline decides everything you do next. A soft decline is a temporary no, so the charge can clear on one retry after you fix the cause. A hard decline means stop and ask for a different card.

A closed account or a stolen-card flag returns the same answer on attempt ten as on attempt one. Our soft decline vs. hard decline entry has the code-by-code breakdown.

Here's what each common decline calls for:

  • Not sufficient funds: wait a few days, then retry once.
  • Security code failure: ask the customer to re-enter the CVV, then retry.
  • A mismatch on address verification (AVS) means they should confirm the billing ZIP with their bank.
  • Expired or invalid card: request updated card details at checkout.
  • On suspected fraud or a pick-up code, stop retrying and ask for another payment method.
  • Do not honor: ask the customer to call their issuer first.

When you can't tell which category a code falls into, treat it as hard.

Guess the other way and you keep retrying a card that will never clear, which issuers treat as abuse. Email the customer on every failed attempt, naming what failed and what you'll do next.

A mishandled decline can still turn into a dispute, and our chargeback alerts catch those.

If a dispute does land, look up what the chargeback reason code actually requires in our reason code lookup tool.

FAQ

What does "generic decline" mean on a credit card?

It's the catch-all label for an unexplained refusal, and it usually arrives as the "do not honor" code. The issuer's real reason never reaches you or your processor.

Can a credit card decline after it was already approved?

Yes. An approval is an authorization, not a completed payment, so it can still fail at capture or expire before you settle.

What is a "no ding" decline?

A "no ding" decline is a refusal the issuer doesn't score against the card or the cardholder. The term shows up mostly in account-verification and prepaid contexts.

Will my bank tell me exactly why a card declined?

Usually yes, if you call them. An issuer explains the refusal to its own cardholder but withholds it from the merchant, so only the call gets an answer.

立即降低您的争议率

加入800多家企业,使用退单自动防止拒付——设置只需不到2分钟。