Your Retry Strategy Won’t Optimize Itself

Transaction declines are inevitable for subscription merchants. You expect them every renewal date and plan accordingly with a well-designed retry strategy. To help customers retain access to your products or services, you design rules around which transactions to try again, after how many days, and up to X number of times. If you can’t recover a transaction, the customer unfortunately churns and you move on. That’s just the way it is. 

What this common story is missing is something far less common: actually analyzing the data to determine if your retry strategy is working, or if small changes could help you retain and delight some of those would-be churned subscribers. Too few subscription merchants segment their retry data—down to the card type, card product, or even BIN-level—to really understand what retries pay off for which customers.

There's a meaningful difference between having a retry strategy and having an optimized one. Automation typically handles the first part, while the optimization piece requires you to look at the right metrics regularly and make deliberate decisions based on what you find. When merchants skip that step, their retry logic runs in the background, quietly recovering some revenue and burning the rest on transactions that were never going to convert.

If that sounds familiar, here's where to start.

The Metrics That Tell the Story

Before you can optimize your retry performance, you need to know which numbers actually matter. Here are a few core metrics that should be on your radar:

• Retry success rate - The percentage of retried transactions that eventually succeeded. This is an important retry performance number, but it doesn’t tell you the whole story. For example, a retry success rate of 20% might sound great, but can be misleading; if it took fifty attempts to recover each transaction, you may have spent more in fees and penalties than the recovered transactions were ever worth.

• Deduped approval rate - Your overall approval rate (successful transactions / attempted transactions), calculated by removing the unsuccessful retry attempts of the exact same transaction from the denominator. The gap between your deduped and regular approval rate tells you how much retries contribute to your business. A large gap means retries are doing significant heavy lifting in your overall performance, which is useful context for any downstream decisions about retry investment.

• Approval rate contribution by attempt - How much your deduped approval rate increases with each transaction retry attempt. Think about this in terms of recovered transactions; you start with 100 transactions, of which only 75 are approved initially. Your first retry recovers 10 more, giving you an approval rate contribution of 10% (10 recovered transactions / 100 unique transactions). Calculate this for each subsequent retry to determine where additional retries stop paying off.

• Average attempts per recovered transaction - As the name indicates, this one tells you how hard you're working to recover a single transaction. If this number is high, it may mean your strategy is working too hard on transactions that aren't worth the effort.

The Retry Effectiveness Curve

Across subscription businesses of all sizes, retry success rates tend to drop off sharply after the first few attempts. Based on the billions of transaction events ingested into the Pagos ecosystem from our roster of enterprise clients, first retry attempts have an average approval rate of 25-35%. The second retry catches a smaller slice, and by the fifth or sixth attempt, your recovery figures fizzle out.

Beyond just success rates, the retry effectiveness curve captures whether the revenue recovered at each attempt justifies the cost of getting there. That calculation looks different for different business models and customer segments. When AOV is low, processing costs can outstrip recovered revenue by the fourth retry; when AOV is high, the math may favor pushing further, as a handful of recovered transactions can offset the cost of many failed attempts.

The problem is that most merchants don't know where their specific retry effectiveness curve flattens. They set a maximum retry count (e.g. 10 attempts) based on intuition or industry convention, and never reassess that strategy. Without visibility into the metrics above, they can’t tell exactly when that strategy costs more than it’s worth and starts actively cutting into revenue figures. Visibility into approval rate contribution by attempt alone would show them that attempts 7-10 are recovering a fraction of a percent of transactions while accumulating real costs.

Digging Deeper into Your Data

Beyond the retry metrics we’ve already discussed, there are several other data points you should be regularly monitoring. These take a little more work, but visualizing these trends in your historical transaction data can meaningfully sharpen your retry strategy:

• Retry success rate by initial decline code - Not all declines are equally retryable. Soft declines like insufficient_funds or do_not_honor can have meaningful retry success rates, but hard declines caused by closed accounts, invalid card numbers, or fraud blocks will likely never succeed. In fact, even trying them again can trigger penalty fees. By identifying your retry success rate by decline code, you can build rules that exclude the hopeless transactions and focus your retry budget where it's most likely to pay off.

• Processor and card type patterns - Your retry success rate may vary meaningfully by the processor you're routing through or the type of card involved. Prepaid cards, for instance, tend to have lower retry success rates and aren’t worth pursuing. Debit cards, on the other hand, tend to perform better after payday cycles and are worth a well-timed retry attempt. 

• Customer and order-level tracking - Payment methods may change during a subscription recovery cycle, like when a customer’s stored card fails and they return with a new card entirely. That counts as a recovered subscription, but it won't show up in your retry data unless you're linking attempts by customer ID or subscription ID. Tagging retry attempts with this metadata gives you a complete picture of recovery, even those customers retained through any combination of retries, outreach, and payment method updates. Without this, you're likely undercounting your true recovery rate and missing the full story of what's working.

The Cost Side of the Equation

We won't go deep on the math here, as our post on finding the retry ROI sweet spot covers that in detail, but it's worth a quick reference. You need visibility into your retry volume and attempt counts to determine your risk of crossing retry penalty thresholds. Both Visa and Mastercard have rules limiting how many times you can retry the same transaction before fees kick in. Those fees are small per transaction, but at subscription scale they compound fast. Keeping a close eye on the data can help you stay out of penalty territory.

The Work That Doesn't Do Itself

A retry strategy that runs without oversight is a strategy that optimizes for nothing. It may be recovering revenue, but is it wasting money on attempts that will never succeed? Are you bumping against penalty thresholds? You’ll never know if you’re not monitoring your data.

The first obstacle for most merchants is data access. If you're processing through multiple processors, your retry data is fragmented across separate reporting environments with different decline code taxonomies and no unified view of what happened. Pagos Insights solves that by connecting to all your processors via no-code data connections and normalizing everything into a single dataset. Using identifiers like customer ID, subscription ID, and your custom retry metadata, you can track a subscription's full retry sequence across processors, segmented by attempt, decline code, card type, and more. You can event export the clean data for external analysis.

We're also building a dedicated Retry Performance dashboard (coming soon!) that’ll surface this in a purpose-built view, so you can perform the retry analysis of your dreams.

The data and the metrics you need exist within your own payments data. With Pagos Insights, you can finally see it. Contact us today to get started.