Metric Definition
Dunning recovery rate
Track from
Payment retry success rate
Payment retry success rate is the percentage of failed payments that are later recovered through automated retry attempts. It measures how effectively your dunning process turns a declined charge into collected revenue. A strong retry success rate protects recurring revenue that would otherwise be lost to involuntary churn.
8 min read
What is payment retry success rate?
Payment retry success rate is the percentage of failed payments that are later recovered through automated retry attempts. When a subscription charge is declined, most billing systems do not give up immediately. They retry the charge over the following days, often alongside email reminders asking the customer to update their card. The retry success rate tells you how many of those declined charges eventually go through.
The metric matters because most payment failures are not deliberate cancellations. A card expires, a bank flags a transaction, or a temporary hold blocks the charge. These customers still want the product. If the retry sequence recovers the payment within a few days, the customer never notices and the revenue is preserved. If it fails, the subscription lapses and the revenue is lost to involuntary churn.
Think of it as the safety net under your recurring revenue. A business that recovers 70 out of every 100 failed payments keeps far more revenue than one that recovers 40, even with an identical underlying decline rate. Because the customers were never trying to leave, recovered revenue is some of the cheapest revenue you can earn. It carries no acquisition cost and protects MRR that you have already won.
Retry success rate measures recovery, not the underlying failure rate. A business can have a high retry success rate and still lose significant revenue if too many payments fail in the first place. Track the failure rate and the recovery rate together, because improving one does not fix the other.
How to calculate payment retry success rate
The calculation divides the number of failed payments you recovered by the number you attempted to retry, then multiplies by 100. If 1,000 charges failed in a month and your retry sequence eventually collected 620 of them, your retry success rate is 62 percent. The simplicity of the headline number hides several decisions about what counts and over what window.
- 1
Total failed payments retried
The count of declined charges that entered the retry sequence in the period. Exclude failures you chose not to retry, such as fraud blocks or accounts already flagged for cancellation, so the denominator reflects genuine recovery opportunities.
- 2
Recovered failed payments
The count of those charges that succeeded on a later attempt, whether through an automatic retry or a customer updating their card after a dunning email. A payment counts as recovered once, even if it took several attempts.
- 3
Recovery window
The number of days you allow for recovery before declaring the payment lost, often 14 to 21 days. A longer window inflates the rate because slow recoveries are counted, so report the window alongside the number.
- 4
Recovered revenue
The pounds value of the recovered charges, not just the count. Recovering many small charges while losing a few large ones can hide real revenue damage, so track the value as well as the rate.
Counting a payment as recovered only once matters more than it sounds. A single failed charge might trigger three retry attempts and two emails before it succeeds. If you count each successful attempt rather than each recovered charge, the rate becomes meaningless. Pin the metric to the charge, not the attempt, and the number stays comparable month over month.
Payment retry success rate in a metric tree
A metric tree decomposes retry success rate into the levers that actually move it, which turns a single billing number into a set of owned, fixable problems. Recovery is not one process. It is retry timing, the dunning messages that prompt customers to act, and the card data quality that determines whether a retry can ever succeed.
The first level splits recovery into automatic recovery and customer-prompted recovery. Automatic recovery depends on retry timing and the number of attempts, because a card declined for insufficient funds on the first of the month often clears after payday. Customer-prompted recovery depends on the dunning emails landing, being opened, and leading to a card update. Underneath both sits card data quality, where account updater services and expiry reminders quietly raise the ceiling on what any retry can achieve.
This structure lets you diagnose a falling recovery rate precisely. If automatic recovery is weak, the retry schedule is mistimed. If customer-prompted recovery is weak, the dunning emails are not reaching inboxes or not persuading anyone to act. Each branch points to a different team and a different fix.
Metric tree insight
Decline reason is the branch most teams ignore. Insufficient funds declines often recover on their own with the right retry timing, while hard bank declines almost never do. Retrying both on the same schedule wastes attempts on lost causes and mistimes the ones you could win. Segment the retry logic by decline reason and the recovery rate climbs without any new tooling.
Payment retry success rate benchmarks
Retry success rate benchmarks depend heavily on billing model, customer base, and how aggressively the retry sequence is tuned. Consumer subscriptions on credit cards tend to recover better than business subscriptions on corporate cards, which carry stricter controls. Use the ranges below as a starting point, then compare against your own decline reason mix.
| Retry success rate | Assessment | What it usually means |
|---|---|---|
| Below 30 percent | Underperforming | Retries are mistimed or dunning emails are not landing. Most recoverable payments are being lost, which inflates involuntary churn well beyond what the decline rate alone would cause. |
| 30 to 50 percent | Developing | A basic retry sequence is running but it is not tuned. Common gaps are too few attempts, no decline-reason segmentation, and weak card update prompts. |
| 50 to 70 percent | Healthy | Smart retry timing and working dunning emails are in place. The remaining losses are mostly hard declines and customers who genuinely lapse. |
| Above 70 percent | Best in class | Retry routing, account updater coverage, and well-timed reminders are all working together. Recovery is close to the practical ceiling set by hard declines. |
A high recovery rate does not mean the job is done. If involuntary churn is still eroding your churn rate, the issue may be upstream in the volume of failures rather than the recovery of them. Reducing the number of payments that fail in the first place, through card expiry reminders and account updater services, often beats squeezing another few points out of the retry sequence.
How to improve payment retry success rate
Improving retry success rate is rarely about retrying more often. It is about retrying at the right moment, for the right reason, while making it easy for customers to fix the underlying card problem. The biggest gains usually come from segmenting the retry logic and tightening the dunning sequence.
Time retries intelligently
Stop retrying on a fixed daily schedule. Insufficient funds declines recover best a few days after the failure, often around payday, while soft declines may clear within hours. Use smart retry timing that learns the optimal moment per card network and decline reason.
Tighten the dunning sequence
Make sure dunning emails reach the inbox, not the spam folder, and lead with a clear card update link. Test subject lines and cadence the same way you would a marketing campaign. A customer who updates their card voluntarily recovers revenue a retry alone never could.
Keep card data fresh
Use account updater services so expired or reissued cards are refreshed automatically before they fail. Send expiry reminders ahead of time. Better card data raises the ceiling on what every retry attempt can achieve.
Segment by decline reason
Treat a temporary bank hold differently from a permanently closed account. Retry recoverable declines persistently and stop wasting attempts on hard declines that will never clear. Routing by decline reason lifts the success rate without adding cost.
The metric tree approach starts by finding the branch with the largest gap between current and achievable performance. If automatic recovery is strong but customer-prompted recovery is weak, the fix lives in the dunning emails, not the retry schedule. If both are weak for expired card declines specifically, the fix is account updater coverage upstream.
KPI Tree lets you connect each branch of the recovery tree to the team that owns it and the action that moves it. Billing owns retry timing and routing. Lifecycle marketing owns the dunning emails. Finance owns the account updater coverage. With RACI ownership on every node, the accountable owner is pushed an alert the moment recovery dips, and the verified impact loop checks whether the change they shipped actually lifted the rate rather than assuming it did.
Common mistakes when tracking payment retry success rate
- 1
Counting attempts instead of charges
A single failed charge can take several attempts to recover. Counting each successful attempt rather than each recovered charge inflates the rate and breaks month-over-month comparison. Pin the metric to the charge.
- 2
Ignoring the recovery window
A retry that succeeds on day 20 is counted very differently from one that succeeds on day 3 if your window is open-ended. Fix the recovery window, report it alongside the rate, and keep it consistent.
- 3
Tracking the rate without the revenue
Recovering 70 percent of charges while losing your largest accounts looks healthy by count and damaging by value. Always pair the recovery rate with the pounds of revenue recovered and lost.
- 4
Retrying every decline the same way
Hard declines and soft declines behave nothing alike. Applying one retry schedule to both wastes attempts on lost causes and mistimes the recoverable ones. Segment by decline reason.
- 5
Treating recovery as the whole problem
A great retry success rate cannot save you if the failure rate is climbing. Reducing the number of payments that fail in the first place often protects more revenue than squeezing the recovery rate higher.
Related metrics
Churn Rate
Customer Churn Rate
SaaS Metrics
Metric Definition
Churn Rate = (Customers Lost During Period / Customers at Start of Period) × 100
Churn rate measures the percentage of customers or subscribers who stop using a product or service during a given time period. It is the most direct indicator of whether a business is delivering enough ongoing value to retain its customer base, and it has a compounding effect on growth, revenue, and customer lifetime value.
Net Revenue Retention
NRR
SaaS Metrics
Metric Definition
NRR = ((Beginning MRR + Expansion MRR - Contraction MRR - Churned MRR) / Beginning MRR) x 100
Net revenue retention (NRR) measures the percentage of recurring revenue retained from existing customers over a given period, including expansion, contraction, and churn. An NRR above 100% means existing customers are generating more revenue over time, creating a compounding growth engine that does not depend on new acquisition.
Monthly Recurring Revenue
MRR
SaaS Metrics
Metric Definition
MRR = Sum of Monthly Recurring Subscription Revenue from All Active Customers
Monthly recurring revenue (MRR) is the predictable, normalised revenue a subscription business earns each month. It is the single most important metric for understanding the health and trajectory of a SaaS company because it captures new sales, expansion, contraction, and churn in one number.
Customer Lifetime Value
CLV / LTV
SaaS Metrics
Metric Definition
CLV = Average Revenue Per User × Gross Margin × Average Customer Lifespan
Customer lifetime value (CLV) is the total revenue a business can expect from a single customer account over the entire duration of their relationship. It quantifies the long-term financial worth of acquiring and retaining a customer, making it one of the most important metrics for sustainable growth.
Churn rate analysis: formulas, benchmarks and fixes
Metric Definition
Improving payment retry success directly cuts involuntary churn, so this deep dive shows you how to decompose and fix the churn this recovery rate feeds into.
Metric trees for finance teams
Metric Definition
This guide shows finance teams how to place dunning recovery alongside the revenue and retention metrics it influences within a single metric tree.
Build a recovery tree that stops involuntary churn
Model payment retry success rate as a metric tree that connects retry timing, dunning, and card data quality to the teams who own each lever, with an alert to the accountable owner the moment recovery slips.
