Payment Decline Codes Explained: Soft vs Hard Declines
Every failed recurring payment carries a decline code — a short string returned by the card-issuing bank or the payment processor that explains why the transaction was rejected. For subscription businesses, these codes are more than a technical detail: they are the single biggest driver of involuntary churn. When a loyal customer's card is declined, the difference between recovering that payment and losing the subscriber often comes down to understanding what the code means and choosing the right response.
Decline codes fall into two broad categories. Soft declines are temporary or retriable failures — the card network or issuer rejected the attempt, but a retry under the right conditions can still succeed. Common examples include "insufficient funds," "do not honor," and velocity or risk-related blocks. Hard declines, by contrast, indicate a permanent problem with the card or account: an expired card, an invalid card number, or a closed account. Retrying a hard decline wastes effort and can even damage your sender reputation with issuers, so the correct response is to update the card on file or prompt the customer to provide new payment details.
The mistake most subscription teams make is treating every decline the same way. A blanket retry schedule applied to both soft and hard declines will burn through retry attempts on payments that can never succeed, while under-investing in the soft declines that are genuinely recoverable. The most effective recovery programs segment decline codes by category, apply a tailored strategy to each, and use network tokenization and account updater services to keep card data current before a retry is ever attempted.
Revaly automates this entire process. The Revaly Approval Platform intercepts failed payments in real time, classifies each decline code, and applies the optimal recovery strategy — whether that means an intelligent retry with updated card data, an issuer partnership route, or a customer-facing update flow. The result is higher approval rates, more recovered revenue, and measurably less involuntary churn, all without ripping out your existing billing stack.
Understanding your decline mix is the first step toward reducing involuntary churn. When you can see which codes are driving your failures and how each one responds to recovery, you stop guessing and start recovering — turning failed payments into retained subscribers and protected revenue.