Card Decline Codes

Every card decline comes with a response code from the issuing bank. Use this guide to look up what each code means, understand why a payment was rejected, and learn the exact steps to resolve it — whether you are a cardholder or a business managing failed transactions.

What is card authorization?

Card authorization is the real-time approval process that happens every time a card is swiped, tapped, or entered online. The merchant's payment terminal sends the transaction details — card number, amount, and merchant category — to the acquiring bank, which routes the request through the card network (Visa, Mastercard, etc.) to the issuing bank. The issuer then runs a series of checks: Is the card valid and not expired? Are there sufficient funds or available credit? Does this transaction match the cardholder's typical spending patterns? If everything passes, the issuer approves the transaction and places a hold on the funds. If any check fails, the issuer sends back a decline code explaining the specific reason the transaction was rejected.

How do card decline codes work?

When a card transaction fails, the issuing bank generates a two-digit response code and sends it back through the card network to the acquiring bank, which relays it to the merchant's payment processor. This entire round trip typically happens in under two seconds. The decline code tells the merchant — and in many cases, the cardholder — exactly why the transaction was not approved. Each code corresponds to a standardized reason defined by the card networks, making it possible for businesses to programmatically categorize failures and take the right next step. Some processors also layer on their own response codes for more granular detail, but the underlying issuer codes remain the universal standard.

What is a decline code?

A decline code is a short numeric response code from the issuing bank that explains why a card transaction was not approved. Each code maps to a specific reason — insufficient funds, suspected fraud, expired card, incorrect PIN, and so on. These codes are standardized across the major card networks and are used by banks, payment processors, merchants, and finance teams worldwide. Understanding decline codes is essential for any business that accepts card payments, because they provide the data you need to diagnose payment failures, reduce lost revenue, and improve the customer experience. Not all decline codes are equal: some indicate temporary issues that can be resolved with a simple retry, while others signal permanent problems that require the cardholder to take action.

Why understanding decline codes matters for your business

Failed card payments cost businesses real money. Industry data suggests that the average online merchant loses 5–10% of revenue to payment declines, and a significant portion of those declines are recoverable. By understanding decline codes, your team can identify payment issues as they happen, categorize them correctly as soft or hard declines, and take targeted action to recover revenue. Decline codes also help you spot patterns — if you see a spike in code 51 (insufficient funds) at the end of the month, that's a billing timing issue. If code 14 (invalid card number) keeps appearing, your checkout form may have a UX problem. Monitoring your overall decline rate is a key business metric: a healthy card-not-present decline rate sits between 5–10%, and anything above 15% usually signals an underlying issue worth investigating.

Decline Code Reference

Select a code for a full breakdown and resolution steps.

Code

Meaning

05Do Not Honor— Generic bank decline 51Insufficient Funds— Not enough balance 14Invalid Card Number— Card number error 54Expired Card— Card past expiration 41Lost Card— Card reported lost 43Stolen Card— Card reported stolen 61Exceeds Withdrawal Limit— Over daily limit 62Restricted Card— Card restricted by issuer 63Security Violation— Security concern 55Incorrect PIN— Wrong PIN entered 78Card Not Activated— Card needs activation 57Transaction Not Permitted— Transaction type blocked

Soft declines vs. hard declines

Card declines fall into two categories, and the distinction determines what you should do next. Soft declines are temporary failures — insufficient funds (code 51), system errors (code 96), issuer timeouts (code 91), or do-not-honor responses (code 05) that may clear up on their own. These can often be resolved by retrying the transaction after an appropriate delay, or by the cardholder adding funds to their account. Many payment processors recommend waiting 24–48 hours before retrying a soft decline. Hard declines are permanent rejections — lost or stolen cards (codes 41, 43), expired cards (code 54), invalid card numbers (code 14), or closed accounts. Retrying a hard decline will not work and can even trigger fraud flags. These require the cardholder to use a different payment method or contact their issuing bank directly.

Common causes of card declines

Insufficient funds is by far the most frequent reason for a card decline, accounting for nearly half of all failed transactions. The second most common cause is incorrect card information entered during online checkout — a mistyped card number, wrong expiration date, or incorrect CVV. Fraud-related declines are triggered when a transaction deviates from the cardholder's normal spending patterns, such as an unusually large purchase, a transaction in a different country, or multiple rapid purchases in succession. Other common causes include expired cards that haven't been updated, cards that have been reported lost or stolen, transactions that exceed daily spending limits set by the issuer, and cards that are restricted from certain merchant categories or geographic regions.

How to manage and resolve card declines

Effective decline management starts with correctly categorizing each decline code. For soft declines, implement automated retry logic with appropriate delays — most processors recommend 24–48 hours for insufficient funds and immediate retries for timeout errors. For hard declines, notify the customer promptly with clear, specific instructions on how to update their payment method. Use account updater services to automatically refresh expired or reissued card details for recurring payments, which can recover a significant percentage of failed subscription charges without any customer action. Verify card data before submission using Address Verification Service (AVS) and CVV checks to catch errors early. Monitor your decline rate as a key metric and investigate spikes quickly. Tools like real-time transaction monitoring, pre-authorization checks, and intelligent payment routing across multiple processors can significantly reduce your overall decline rate and recover lost revenue.

How to reduce card declines proactively

The best approach to decline management is prevention. Keep card-on-file data current by using account updater services that automatically refresh card numbers and expiration dates when issuers reissue cards. Implement smart retry logic that respects the decline code — retry soft declines on an appropriate schedule but never retry hard declines. Offer multiple payment methods so customers have a fallback when one card fails. Use pre-authorization checks for high-value transactions to confirm funds before committing. Optimize your checkout flow to reduce data entry errors — auto-format card numbers, validate inputs in real time, and clearly flag incorrect fields. For subscription businesses, send proactive payment reminders before billing dates so customers can ensure their card is funded and up to date. Finally, work with your payment processor to fine-tune fraud rules — overly aggressive fraud filters are a common source of false declines that reject legitimate transactions.

Why Slash for card management?

Unlimited virtual and physical cards, organized with virtual accounts and card groups. Set granular spend controls, earn high cashback, and track expenses in real time so you always understand every payment.