Understanding Decline Codes: A Complete Guide for Subscription Businesses
A practical reference to the 50+ decline codes your payment processor returns, organized by category with specific recovery strategies for each.
What Are Decline Codes?
When a payment fails, the issuing bank returns a decline code to the payment processor, which then passes it to the merchant. These codes are meant to explain why the transaction was rejected, but in practice, they are often cryptic, inconsistent across processors, and sometimes misleading. Understanding what each code actually means, and more importantly, what action to take in response, is critical for maximizing recovery rates.
Hard Declines: Do Not Retry
Hard declines indicate a permanent problem with the payment method. Common hard decline codes include "card stolen" (code 43), "account closed" (code 46), and "fraudulent transaction" (code 59). Retrying these payments will never succeed and can trigger fraud monitoring alerts from the card network. The correct response is immediate customer outreach requesting a new payment method, combined with a clear explanation of why the current card cannot be charged.
Soft Declines: Retry with Strategy
Soft declines represent temporary conditions that may resolve. "Insufficient funds" (code 51) is the most common, accounting for roughly 40% of all payment failures. "Issuer temporarily unavailable" (code 91) and "processing error" (code 96) indicate infrastructure issues. These failures respond well to intelligent retry timing. The key is matching the retry strategy to the specific decline code: insufficient funds benefits from payday-aware timing, while processor errors can be retried within minutes.
Card Update Declines
Expired card (code 54) and invalid card number (code 14) declines require the customer to provide updated payment details. These cannot be recovered through retries alone. However, the recovery rate for card-update declines is actually higher than for soft declines when the outreach is handled well. Customers who receive a clear, low-friction update request within 24 hours of expiration recover at rates above 60%. The window closes quickly though, dropping to under 20% after 7 days.
Building a Decline Code Taxonomy
Effective recovery starts with mapping every decline code your processor returns to one of four categories: hard decline (do not retry), soft decline (smart retry), card update needed (customer outreach), and unknown or ambiguous (conservative retry plus monitoring). LostChurn maintains a taxonomy of over 50 decline codes across 13 payment processors, automatically classifying each failure and routing it to the optimal recovery workflow. This classification alone can improve recovery rates by 30% compared to treating all failures identically.
Cross-Processor Normalization
One of the biggest challenges in decline code management is inconsistency across payment processors. Stripe uses different codes than Braintree, which differ from Adyen, which differ from PayPal. The same underlying failure, insufficient funds, might appear as code 51 from one processor, "card_declined" from another, and "Do Not Honor" from a third. Normalizing these codes into a unified taxonomy is essential for merchants using multiple processors or considering a processor migration.
Ready to recover your failed payments?
Connect your payment processor in under 2 minutes and start recovering revenue today.
Start Free Trial