What is the most common card decline code?

Code 05 (Do Not Honor) is the most frequently returned decline code across the card payment industry. It is a generic catch-all response from the issuing bank and can represent a variety of underlying reasons, including insufficient funds, risk assessment failures, spending limits, or issuer-side blocks. Code 51 (Insufficient Funds) is the most common decline with a specific, identifiable cause.

What is the difference between a soft decline and a hard decline?

A soft decline indicates a temporary or recoverable issue — such as insufficient funds (51), a system error (96), or an issuer timeout (91). These transactions may succeed if retried after a delay. A hard decline indicates a permanent or unrecoverable issue — such as a stolen card (43), expired card (54), or invalid card number (14). Hard declines should never be retried with the same card details.

Can I retry a declined transaction?

Only soft declines should be retried, and card networks enforce strict retry rules. Visa and Mastercard generally allow retries after 24-48 hours for soft declines, with a maximum number of retries per billing cycle (typically 15 for Visa, 10 for Mastercard). Hard declines should never be retried — doing so can result in network fines, increased processing fees, and damage to your merchant reputation.

How can merchants reduce card decline rates?

Key strategies include: implementing account updater services to automatically refresh expired card credentials, using network tokenization for higher approval rates, implementing 3D Secure (3DS) for authenticated transactions, building smart retry logic with appropriate delays for soft declines, using clear billing descriptors to reduce false fraud flags, offering multiple payment methods, and monitoring decline rate metrics by code to identify systemic issues.

What is a healthy decline rate for merchants?

A healthy overall decline rate for card-not-present (online) merchants is typically between 5% and 10%. Rates below 5% indicate strong payment optimization. Rates between 10% and 15% warrant investigation — you may have issues with card freshness, fraud filter sensitivity, or customer demographics. Rates above 15% are concerning and likely indicate a systemic problem that requires immediate attention from your payment operations team.

What should I do if my card keeps getting declined?

First, verify the basics: check your card has not expired, your billing address matches what your bank has on file, and you have sufficient funds or credit available. If those are correct, contact your bank directly — the decline may be caused by a fraud alert, spending limit, or account restriction that only your issuer can resolve. If your bank confirms everything is fine, try using a different card or payment method.

What is the most common card decline code?

Code 05 (Do Not Honor) is the most frequently returned decline code across the card payment industry. It is a generic catch-all response from the issuing bank and can represent a variety of underlying reasons, including insufficient funds, risk assessment failures, spending limits, or issuer-side blocks. Code 51 (Insufficient Funds) is the most common decline with a specific, identifiable cause.

What is the difference between a soft decline and a hard decline?

A soft decline indicates a temporary or recoverable issue — such as insufficient funds (51), a system error (96), or an issuer timeout (91). These transactions may succeed if retried after a delay. A hard decline indicates a permanent or unrecoverable issue — such as a stolen card (43), expired card (54), or invalid card number (14). Hard declines should never be retried with the same card details.

Can I retry a declined transaction?

Only soft declines should be retried, and card networks enforce strict retry rules. Visa and Mastercard generally allow retries after 24-48 hours for soft declines, with a maximum number of retries per billing cycle (typically 15 for Visa, 10 for Mastercard). Hard declines should never be retried — doing so can result in network fines, increased processing fees, and damage to your merchant reputation.

How can merchants reduce card decline rates?

Key strategies include: implementing account updater services to automatically refresh expired card credentials, using network tokenization for higher approval rates, implementing 3D Secure (3DS) for authenticated transactions, building smart retry logic with appropriate delays for soft declines, using clear billing descriptors to reduce false fraud flags, offering multiple payment methods, and monitoring decline rate metrics by code to identify systemic issues.

What is a healthy decline rate for merchants?

A healthy overall decline rate for card-not-present (online) merchants is typically between 5% and 10%. Rates below 5% indicate strong payment optimization. Rates between 10% and 15% warrant investigation — you may have issues with card freshness, fraud filter sensitivity, or customer demographics. Rates above 15% are concerning and likely indicate a systemic problem that requires immediate attention from your payment operations team.

What should I do if my card keeps getting declined?

First, verify the basics: check your card has not expired, your billing address matches what your bank has on file, and you have sufficient funds or credit available. If those are correct, contact your bank directly — the decline may be caused by a fraud alert, spending limit, or account restriction that only your issuer can resolve. If your bank confirms everything is fine, try using a different card or payment method.

Card Decline Codes

Look up any ISO 8583 decline response code — what it means, whether you can retry it, and how to resolve it.

Common 05 · Do Not Honor 51 · Insufficient Funds 54 · Expired Card 14 · Invalid Card Number 61 · Exceeds Withdrawal Limit

Response codes

Soft declines

Hard declines

Code reference

of 34 codes

Code Description Category Retry

No decline codes match your search

Fundamentals

What Is a Card Decline Code?

A decline code (also called a response code or authorization code) is a standardized identifier returned by a card-issuing bank when it refuses to approve a payment transaction. These codes are part of the ISO 8583 financial messaging standard — the protocol that governs how authorization requests and responses are formatted and exchanged between payment terminals, acquirers, card networks, and issuers worldwide.

When a merchant submits a card payment for authorization, the issuing bank evaluates the request against dozens of criteria — available balance, card status, fraud risk, spending limits, geographic rules, and more. If the bank decides not to approve the transaction, it returns a two-character (or alphanumeric) response code that identifies the specific reason for the refusal.

Decline codes serve two critical purposes: they help merchants determine whether to retry the transaction, request an alternative payment method, or investigate a potential fraud attempt; and they help cardholders understand what went wrong so they can take corrective action (e.g., adding funds, contacting their bank, or using a different card).

How It Works

How Card Authorization Works

Every card payment goes through a real-time authorization process that typically completes in under two seconds. Understanding this flow is essential for interpreting decline codes correctly:

Cardholder initiates payment

The cardholder presents their card (physically or digitally) and the merchant's terminal, gateway, or checkout page captures the card data, transaction amount, currency, and merchant identifiers.

Acquirer receives and forwards the request

The merchant's acquiring bank (or payment processor) receives the authorization request and routes it through the appropriate card network — Visa, Mastercard, American Express, or Discover — based on the card's BIN.

Issuer evaluates the transaction

The card-issuing bank runs the transaction through its authorization engine — checking available balance, card status (active, frozen, expired), fraud scoring models, velocity limits, geographic rules, merchant category restrictions, and 3D Secure authentication status.

Response code returned

The issuer sends back a response through the network to the acquirer and merchant. If approved, the response includes an authorization code. If declined, it includes a decline code identifying the reason — such as "51" for insufficient funds or "14" for an invalid card number.

Merchants lose an estimated 5-10% of revenue to false or recoverable declines

A substantial portion of soft declines can be recovered through smart retry logic, account updater services, and network tokenization. Understanding the difference between soft and hard declines is the foundation for improving your authorization rate.

Key Distinction

Soft Declines vs. Hard Declines

The most important classification for decline codes is whether the decline is recoverable (soft) or permanent (hard). This determines whether retrying the transaction is appropriate.

Soft Declines

Temporary issues that may resolve on their own or after the cardholder takes action. Retrying after an appropriate delay is acceptable.

Common examples:

01 Refer to Issuer 02 Refer to Issuer (Special) 05 Do Not Honor 06 Error 10 Partial Approval 19 Re-enter Transaction

Retry guidance

Wait 24-48 hours before retrying. Visa allows up to 15 retries and Mastercard up to 10 retries per billing cycle for soft declines. Implement exponential backoff.

Hard Declines

Permanent issues that will not resolve with time. The transaction should not be retried with the same card details.

Common examples:

04 Pick Up Card 07 Pick Up Card (Special) 12 Invalid Transaction 13 Invalid Amount 14 Invalid Card Number 15 Invalid Issuer

Retry guidance

Do not retry. Retrying hard declines wastes processing costs, triggers network penalties, and can result in the merchant being flagged for excessive retry activity.

Root Causes

Common Causes of Card Declines

Understanding the most frequent reasons behind card declines helps merchants design better payment flows and cardholders resolve issues faster.

Insufficient funds or credit

The single most identifiable cause of card declines. The cardholder's available balance (after accounting for holds and pending transactions) is lower than the transaction amount. Represented by code 51.

Issuer risk assessment and fraud detection

Issuers run every transaction through fraud scoring models. Unusual patterns — unfamiliar merchants, geographic anomalies, atypical amounts, or rapid successive transactions — can trigger a decline even when funds are available. Often returned as code 05 or 59.

Incorrect card data

Typos in the card number (code 14), wrong expiry date (code 54), or mistyped CVV (code N7) are common causes, especially in card-not-present environments where data is manually entered.

Card restrictions and spending limits

Issuers impose daily spending limits, per-transaction caps, velocity limits (number of transactions per time period), and restrictions on specific merchant categories or geographic regions. Codes 61, 65, and 57.

Lost, stolen, or compromised cards

Cards reported as lost (code 41) or stolen (code 43) are permanently blocked. These are hard declines with no possibility of retry. The issuer may also request the card be confiscated (code 04).

System and network errors

Temporary failures in the processing chain — issuer system downtime (code 91), network malfunctions (code 96), or format errors (code 30). These are soft declines that typically resolve on retry.

For Businesses

How to Reduce Card Decline Rates

A strategic approach to decline management can recover significant revenue. These are the most effective techniques used by high-performing payment operations teams.

Implement account updater services

Card networks (Visa Account Updater, Mastercard Automatic Billing Updater) provide services that automatically update stored card credentials when a card is replaced or renewed. This prevents declines caused by expired or reissued cards in recurring billing scenarios — one of the largest sources of preventable hard declines.

Use network tokenization

Network tokens (Visa Token Service, Mastercard Digital Enablement Service) replace card PANs with network-issued tokens that automatically update when the underlying card changes. Tokenized transactions consistently see higher approval rates than raw PAN transactions because issuers trust the token lifecycle management.

Build intelligent retry logic

Classify declines as soft or hard, and only retry soft declines. Use exponential backoff (e.g., retry after 1 day, then 3 days, then 7 days). Respect card network retry limits — Visa allows 15 retries over 30 days for soft declines, Mastercard allows 10. Never retry hard declines.

Implement 3D Secure authentication

3D Secure (3DS2) authentication shifts fraud liability from the merchant to the issuer and signals to the issuer that the cardholder has been verified. This significantly reduces false fraud declines (code 05, 59) and improves approval rates for cross-border transactions.

Monitor decline rates by code

Track your decline rate broken down by response code, not just in aggregate. A spike in code 14 (invalid card number) might indicate a checkout UX problem. A spike in code 05 might mean your fraud filters need tuning. A spike in code 54 means you need an account updater.

Optimize your billing descriptor

Unclear billing descriptors cause cardholders to not recognize charges, leading them to report fraud or request blocks — which increases your decline rate and chargeback rate. Use a clear, recognizable business name and include a customer service phone number.

Decline Rate Benchmarks

Under 5% Excellent

5-10% Healthy

10-15% Needs attention

Above 15% Critical — investigate immediately

Benchmarks are for card-not-present (online) merchants. Card-present merchants typically see lower decline rates. Rates vary by industry, geography, and customer demographics.

Free tools

More tools for payment teams

Free utilities built on the same data that powers Fyatu's card issuing platform. No sign-up, no rate limits.

All tools

FAQ