Credit Card Decline Codes: The Complete Merchant Guide

When a payment fails, the decline code attached to it is your best clue to what went wrong — and whether the sale can still be saved. A declined card is frustrating and sometimes embarrassing for the customer, and on the merchant side every vague "card declined" message means potential lost revenue and an abandoned cart.

This guide covers the full list of credit card decline codes (and debit card codes), the difference between hard and soft declines, gateway codes like card_declined and generic_decline, virtual terminal declines, and Certegy check decline codes — plus practical steps to reduce decline rates.

What Are Credit Card Decline Codes?

Credit card decline codes — also called response codes or credit card error codes — are the numeric or alphanumeric messages an issuing bank, card network, or payment processor returns when a transaction can't be authorized. When you run a card, the issuer evaluates the transaction in real time, checking available funds, card status, fraud risk, and account restrictions. If anything fails that check, the system sends back a code identifying the reason.

Credit and debit cards use largely the same response-code system, which is why a list of debit card declined codes looks nearly identical to a credit card list — debit simply adds PIN- and limit-related codes on top.

Common Reasons for Declined Transactions

• Insufficient Funds:

One of the most straightforward declines occurs when a cardholder doesn't have enough money or credit available to cover the purchase. This often triggers a code such as 51 (Insufficient Funds).

• Card Information Errors:

Inputting incorrect card details (such as the CVV code or expiration date) can lead to declines. Typographical errors, outdated card numbers, or expired cards will cause the transaction to fail.

• Suspicious Activity or Fraud Alerts:

If the issuing bank suspects that a transaction isn't in line with the cardholder's typical spending patterns — perhaps due to an unusual geographic location or a very large purchase — it may block the sale. These declines are often tied to codes that indicate suspected fraud or restricted card usage.

• Technical or Connectivity Issues:

Sometimes the problem isn't with the cardholder's account at all. Network errors, processor downtime, or terminal malfunctions can all result in declined transactions. These codes typically encourage a retry or request an alternative payment method.

• Merchant Account Setup Issues:

If a merchant's payment gateway or processor settings aren't configured correctly — or if the merchant account is on hold — transactions may fail. These errors often point the merchant toward contacting their processor or support team.

Hard Declines vs. Soft Declines

Before you troubleshoot a specific code, identify which category it belongs to:

• Hard declines are permanent. The issuer is blocking the card outright — it's expired, closed, invalid, or reported lost, stolen, or fraudulent. Retrying a hard decline won't work and can flag your account for excessive reattempts. Examples: codes 04, 07, 14, 41, 43, 54.
• Soft declines are temporary. The issuer might approve the same card later — the account may lack funds right now, a spending limit was hit, or the issuer's system is down. Examples: codes 05, 51, 61, 65, 91, 96. Smart, limited retries and updated card data recover many soft declines.

The distinction drives your response: retry soft declines strategically; never retry hard declines.

The Complete List of Credit Card Decline Codes

Card networks share a largely standardized set of two-digit response codes. These are the codes merchants encounter most, with each code's meaning, its hard or soft classification, and the action to take:

• 01 – Refer to issuer (soft): Have the customer call their bank, then retry.
• 02 – Refer to issuer, special condition (soft): Same as code 01.
• 03 – Invalid merchant (setup issue): Your merchant account or category code is misconfigured — contact your processor.
• 04 – Pick up card (hard): Do not retry; request another payment method.
• 05 – Do not honor (soft): The most common generic decline; the customer must contact their bank.
• 06 – General error (soft): Retry once; escalate to your processor if it repeats.
• 07 – Pick up card, special condition (hard): Suspected fraud — do not retry.
• 12 – Invalid transaction (hard): The transaction type isn't allowed for this card or terminal.
• 13 – Invalid amount (soft): Re-enter the correct amount.
• 14 – Invalid card number (hard): The number doesn't match a real account — re-key it carefully.
• 15 – No such issuer (hard): The first digits don't match any issuer; check for typos.
• 19 – Re-enter transaction (soft): A processing glitch — retry.
• 41 – Lost card (hard): Do not retry; treat as potential fraud.
• 43 – Stolen card (hard): Do not retry; treat as potential fraud.
• 51 – Insufficient funds (soft): Ask for another card or retry after limits reset.
• 54 – Expired card (hard): Request updated card details.
• 55 – Incorrect PIN (soft): The customer re-enters the PIN (debit).
• 57 – Transaction not permitted to cardholder (hard): The issuer restricts this transaction type for the card.
• 58 – Transaction not permitted to terminal (setup issue): Your account isn't approved for this transaction type — call your processor.
• 59 – Suspected fraud (hard): Do not retry.
• 61 – Exceeds withdrawal limit (soft): Retry after limits reset, or split the payment.
• 62 – Restricted card (hard): The card can't be used for this purchase or region.
• 63 – Security violation (hard): Do not retry.
• 65 – Activity limit exceeded (soft): Retry later.
• 75 – PIN tries exceeded (hard): The customer must contact their bank.
• 78 – Invalid or nonexistent account (hard): Do not retry.
• 85 – No reason to decline: Returned on account verifications; not a true decline.
• 91 – Issuer or switch inoperative (soft): The issuer's system is down — retry later.
• 93 – Transaction cannot be completed (hard): A legal or violation flag; do not retry.
• 96 – System malfunction (soft): Retry later.

What Does "Generic Decline" Mean?

A generic decline — often surfaced as code 05 ("Do Not Honor") or the gateway code generic_decline — means the issuing bank refused the transaction without disclosing a specific reason. Banks intentionally keep these vague for security. The only reliable fix is for the cardholder to call the number on the back of their card; the merchant-side move is to offer an alternative payment method before the customer leaves checkout.

Debit Card Declined Codes

Debit cards return the same core response codes listed above, plus a few debit-specific ones: 55 (incorrect PIN), 75 (PIN tries exceeded), 61 (exceeds withdrawal limit), and 65 (activity limit exceeded). Because debit transactions pull from real balances and enforce daily spending caps, codes 51 and 61 appear more often than on credit cards. The fixes are the same: verify the entry, then ask the customer to check their balance or daily limit.

Visa, Mastercard, Discover, and Amex Decline Codes

• Visa and Mastercard decline codes both draw from the standardized two-digit set above. Labels vary slightly between networks and processors, but 05, 14, 51, and 54 mean the same thing everywhere.
• Discover declined? Discover uses closely equivalent response codes. Treat a generic Discover decline like an 05: the cardholder contacts Discover, and you offer a backup payment method.
• American Express maintains its own expanded code set, but most gateways normalize Amex responses into the same categories — invalid number, insufficient funds, do not honor, and suspected fraud.

Gateway and API Decline Codes: card_declined and More

If you sell online, you may never see a raw two-digit code. Payment gateways and APIs translate network responses into text codes such as:

• card_declined — a catch-all wrapper; check the accompanying decline or network code for the true reason
• generic_decline — the issuer declined without a specific reason (equivalent to code 05)
• insufficient_funds — equivalent to code 51
• expired_card — equivalent to code 54
• incorrect_cvc and AVS failures — the security details didn't match the issuer's records

When you see card_declined in your gateway logs, don't stop there — the sub-code determines whether the decline is hard or soft, and therefore whether a retry or a customer-side fix is the right response.

Virtual Terminal Decline Codes

Virtual terminal transactions are keyed-in, card-not-present payments — and issuers score them as higher risk than swiped, dipped, or tapped transactions. That means more frequent declines, typically:

• 05 (Do Not Honor) triggered by issuer risk models on keyed entries
• 14 / 15 from simple typos in a hand-keyed card number
• AVS and CVV mismatch declines when the billing address or security code doesn't match the issuer's records
• 57 / 58 when the card or your merchant account isn't configured for card-not-present or MOTO transactions

To reduce virtual terminal declines: always collect and submit AVS (billing ZIP) and CVV data, read card numbers back before submitting, retry once after re-keying, and confirm your merchant account is coded for keyed and MOTO acceptance.

Certegy Check Decline Codes: Code 1, Code 2, and Score-Based Declines

If you accept paper checks or check-by-phone payments, authorizations often run through Certegy, a check-verification service with its own decline codes:

• Certegy decline Code 1 generally means Certegy has negative information on file — most often unpaid returned checks connected to the account or ID.
• A Certegy Code 2 decline is a score-based decline: there's no negative history on file, but Certegy's real-time risk model flagged the check as statistically risky based on factors like check number, amount, location, and transaction velocity.
• Code 3 typically means Certegy couldn't verify the identity or account information provided.

Customers declined by score can request a free file disclosure from Certegy under the Fair Credit Reporting Act. On the merchant side, the practical move is to offer an alternative payment method on the spot — a card or ACH payment processing — so a verification decline doesn't cost you the sale.

What Is a Real-Time Score Decline?

Score-based declines aren't unique to checks. Card issuers and processors score every transaction in real time, and a "declined by score" result means the risk model — not the account balance — stopped the payment. These declines are more common in industries that fraud models treat as elevated risk. If score declines are a recurring pattern for your business, the underlying problem is often classification: a properly underwritten high-risk merchant account aligns your processing setup with your actual risk profile, which can reduce false-positive declines.

How Merchants Can Reduce Decline Rates

• Keep payment data current. Use account-updater services, prompt customers to refresh expiring cards, and keep gateway and terminal software up to date.
• Retry intelligently. Reattempt soft declines (51, 61, 65, 91, 96) on a spaced schedule; never retry hard declines (04, 07, 41, 43, 54).
• Communicate at checkout. Replace a dead-end "declined" message with clear guidance: verify the details, try another card, or use a different payment method.
• Offer backup payment options. Digital wallets and ACH give customers a second path to complete the purchase when a card fails.
• Monitor your decline codes. Recurring 03 or 58 codes point to account configuration problems; spikes in 05 or score-based declines point to risk-model friction worth escalating to your processor.
• Balance your fraud filters. Overly strict filters decline legitimate customers; loose ones invite fraud and the chargebacks that follow. Review AVS/CVV rules and velocity limits quarterly.

Turn Decline Codes into Recovered Revenue

Decline codes aren't just error messages — they're a diagnostic map of where your checkout is leaking sales. Read them, categorize them as hard or soft, fix the setup issues they expose, and give customers an immediate alternative path to pay. And if your business sees persistent score-based or "do not honor" declines because of your industry, PayKings can match you with acquiring banks that understand your risk profile — which can help more legitimate transactions get approved the first time.