Smart Retry Logic for Declined Payments: The Rules That Actually Work
Payment declines are a significant source of involuntary churn, particularly for subscription models, but many temporary soft declines can be recovered with a smart retry strategy that uses data to time and shape each.
Merchant accounts, acquiring routes, and chargeback controls, matched to your risk profile.
Payment declines are a significant source of involuntary churn for any business, but they are particularly damaging for subscription models. While some declines are permanent, many are temporary soft declines that can be recovered with a smart retry strategy. A well-designed payment retry logic system can recover a substantial portion of this lost revenue, directly impacting your bottom line and customer lifetime value. It moves beyond simple, fixed-interval retries and instead uses data from decline codes, card schemes, and issuer behaviour to time and shape each attempt for the highest probability of success.
The difference between a basic retry setup and an intelligent one is the difference between blindly knocking on a locked door and knowing precisely when the owner will be home to open it. An effective strategy is not about retrying more often, but retrying smarter. This involves analysing the reason for the initial failure and adapting the subsequent attempt, sometimes by changing the timing, the amount, or even the acquiring bank used for processing.
Hard Declines vs Soft Declines: The Foundation of Retry Logic
The first rule of any payment retry logic is to know when not to retry. All card payment declines are not created equal. They fall into two main categories, and your strategy must begin by differentiating them based on the response code returned by the issuer.
Hard declines signal a permanent failure. The issuing bank has given a definitive "no" that will not change with subsequent attempts on the same card. Retrying a hard decline is not only futile, it's harmful. It increases your transaction costs, can flag your merchant account for excessive authorisations, and may even lead to penalties from card schemes like Visa and Mastercard. Common reasons for hard declines include:
05 Do Not Honour(often a catch-all, but usually treated as hard)14 Invalid Card Number41 Lost Card, Pick-Up43 Stolen Card, Pick-Up
When you receive a hard decline, the only viable next step is to contact the customer through your dunning process and ask them to provide a new payment method. The card is unusable.
Soft declines, on the other hand, signal a temporary issue. The issuing bank is indicating that the transaction could be approved at a later time or under different circumstances. These are the declines that a robust decline recovery strategy is built to solve. Common reasons for soft declines include:
51 Insufficient Funds54 Expired Card(can sometimes be retried if the customer has an updated card-on-file arrangement)61 Exceeds Withdrawal Limit65 Activity Count Limit Exceeded01 Refer to Card Issuer(often a temporary velocity check)
For these codes, a retry is not just possible, it is recommended. The key is to tailor the retry attempt based on the specific reason for the decline.
Building a Smarter Retry Schedule
A generic retry schedule, like "try again in 3 days, then 5 days, then 7 days", is better than nothing, but it leaves significant revenue on the table. An intelligent schedule is dynamic and informed by data. It considers the specific decline code and common consumer behaviour patterns associated with it.
Timing Based on Decline Codes
The reason for the decline is your most important signal for when to retry. For example, a decline for 51 Insufficient Funds has a very different optimal retry pattern than a generic system error.
- Insufficient Funds: These declines are often linked to customer paydays. The highest success rates for retrying an "Insufficient Funds" decline are typically within a day or two of common salary deposit dates, such as the 1st, 15th, or last day of the month. A smart system might try one day after the initial decline, then again around the 1st of the upcoming month.
- Issuer-Side Limits: Codes like
61 Exceeds Withdrawal Limitor65 Activity Count Limit Exceededoften relate to daily or weekly velocity controls set by the issuer. Retrying these transactions after 24-48 hours often works, as the customer's limit has had time to reset. - General Issuer Declines: Vague codes like
01 Refer to Card Issueror temporary system timeouts (e.g.,91 Issuer or Switch is Inoperative) suggest a transient issue. An immediate or short-interval retry (e.g., 15-60 minutes later) can sometimes capture these, followed by a longer interval of 24 hours if the first retry fails.
Sophisticated platforms can analyse historical data across millions of transactions to identify the optimal retry windows for specific BINs (Bank Identification Numbers). Some issuers consistently resolve certain soft declines within hours, while others take days. This level of granularity is where retry logic generates its highest returns, especially for subscription businesses that depend on recurring billing success.
Dynamic Retries: Changing More Than Just the Time
The most advanced retry strategies go beyond timing. They dynamically alter the transaction itself to increase the likelihood of approval on subsequent attempts. This requires a flexible payment infrastructure, often managed through a payment orchestration layer.
Retry with 3D Secure
Sometimes, an issuer will soft decline a transaction because their risk engine is uncertain about its legitimacy. This is common for new subscriptions, high-value orders, or transactions that deviate from the customer's typical spending pattern. Retrying the transaction while forcing a 3D Secure challenge can provide the issuer with the authentication proof it needs. The customer completes the challenge, and the transaction is approved. This technique shifts liability for fraud-related chargebacks to the issuer and satisfies requirements under regulations like PSD2 for Strong Customer Authentication (SCA) in Europe.
Retry Through a Different Acquirer
Not all acquiring banks have the same relationships with issuing banks or the same risk tolerances. An issuer in Brazil might view transactions from a UK-based acquirer with more suspicion than one from a local LATAM acquirer. If your initial transaction is declined, routing the retry attempt through a different provider in your multi-acquirer processing setup can yield an approval. This is a core function of smart payment routing, where the system automatically selects the acquirer most likely to approve a given transaction based on factors like card origin, currency, and historical performance.
Retry with Network Tokens
If you are using network tokenisation, you have another powerful tool. Unlike a standard PAN (Primary Account Number), a network token is automatically updated by the card schemes (Visa, Mastercard) when a customer's card expires or is reissued. If a recurring payment fails with an 54 Expired Card decline, a system integrated with network tokenisation can automatically retry the transaction using the updated card details linked to the token, often without any action required from the customer. This significantly reduces passive churn from outdated card credentials.
Measuring Success and Avoiding Pitfalls
Implementing a smart retry strategy requires careful monitoring to ensure it is adding value and not causing harm. The primary metric is your payment recovery rate: the percentage of revenue from failed transactions that is successfully captured through retries.
However, you must also watch for negative indicators. Card schemes have rules about excessive authorisation attempts on a single card. Visa's Stored Credential Transaction framework and Mastercard's authorization standards impose limits and potential fees for merchants who repeatedly retry declined transactions, especially hard declines. Visa's programs, for instance, can identify merchants with high rates of authorisation attempts per approved transaction and may apply penalties.
A well-configured system avoids this by:
- Never retrying hard declines.
- Capping the number of retries for any given soft decline (typically 3-4 attempts over a billing cycle).
- Using intelligent timing to maximise the effectiveness of each attempt, reducing the overall number of retries needed.
Ultimately, a smart retry system should be one component of a broader communication strategy. After a capped number of failed retry attempts, the system should trigger your dunning process, which proactively notifies the customer about the payment issue and provides them with a simple way to update their payment information. This combination of automated recovery and clear customer communication is the key to minimising involuntary churn.
Frequently asked questions
What is payment retry logic?
Payment retry logic is an automated process that attempts to re-process a failed card transaction at a later time. Instead of simply giving up after a single decline, the system uses a set of rules to decide when and how to try the payment again. The goal is to recover revenue from temporary "soft declines" like insufficient funds or temporary issuer outages.
How many times should you retry a failed payment?
There is no single answer, but a common best practice is to cap retries at 3 to 4 attempts within a billing cycle. Retrying indefinitely is counterproductive, as it increases processing costs and can violate card scheme rules against excessive authorisations. An intelligent system stops retrying after a few optimised attempts and triggers a dunning process to contact the customer.
What is the difference between a soft decline and a hard decline?
A soft decline is a temporary transaction failure. The issuer indicates the payment might be successful if tried again later (e.g., Insufficient Funds, Issuer System Down). A hard decline is a permanent failure, where the issuer has given a final refusal (e.g., Stolen Card, Invalid Card Number). You should only ever retry soft declines.
Can retrying a payment increase my costs?
Yes, each retry attempt is a transaction that incurs an authorisation fee from your payment processor or acquirer, regardless of whether it succeeds. This is why blindly retrying payments is inefficient. A smart retry strategy minimises costs by using data to time attempts for the highest chance of success, reducing the total number of attempts needed.
How does smart routing help with payment retries?
Smart routing enhances retry logic by allowing the system to retry a failed transaction through a different acquiring bank. An issuer might decline a transaction from one acquirer due to its location or risk profile but approve the same transaction from another. This is particularly effective for international businesses using a smart payment routing strategy with multiple acquirers.
Does retry logic work for high-risk merchants?
Yes, it is especially critical for high-risk merchants, who often face higher decline rates from cautious issuing banks. An intelligent retry strategy, combined with multi-acquirer routing and 3DS optimisation, can significantly improve approval rates and recover revenue that would otherwise be lost.
Related reading
This article explains how card testing attacks uniquely impact subscription businesses, detailing the mechanisms of these fraudulent activities and their severe consequences for online merchants.
Network tokens improve authorisation rates for recurring payments by providing a dynamic link to the underlying funding instrument at the card scheme level, ensuring fewer failed renewals due to outdated card details.
Account updater services like Visa Account Updater (VAU) and Mastercard Automatic Billing Updater (ABU) automatically update stored card details, preventing failed recurring payments and protecting revenue streams for.
