Failed MRR
sum of unpaid subscription invoices
Start with subscription revenue Stripe attempted to collect but did not collect.
Payment recovery metric
For SaaS teams, a failed Stripe payment should not move straight into churn reporting. Track it as MRR at risk first, then recover it with the right email, retry, update link, or founder review.
Formula
sum of unpaid subscription invoices
Start with subscription revenue Stripe attempted to collect but did not collect.
failed MRR x expected recovery rate
Estimate the portion that can still be recovered through retries, update links, emails, or manual escalation.
failed MRR - recovered MRR
Only unresolved revenue should become involuntary churn once the recovery window ends.
Examples
These examples use public benchmark assumptions and are directional, not a guarantee. Your real number depends on failure mix, billing interval, card age, customer geography, and retry setup.
$10k MRR SaaS
5.1%
$510
$316
Small leaks become meaningful once they repeat every month.
$25k MRR SaaS
5.8%
$1,450
$899
At this stage, payment recovery deserves weekly review.
$80k MRR SaaS
6.4%
$5,120
$3,174
High-value failures should trigger founder or operator review.
A failed invoice can be recovered, unresolved, escalated, or lost. Reporting all four states keeps payment failure from polluting product churn analysis.
Failed MRR by Stripe decline code
Recovered MRR by recovery step
Open delinquent MRR still inside the dunning window
Final involuntary churn after recovery ends
High-value accounts awaiting founder escalation
Recovery action
Expired cards need update links. Insufficient funds need timing. Bank blocks need clear context. Authentication failures need a confirmation path. Dunlo turns those states into recovery workflows around Stripe.
View email templatesMRR at risk is recurring revenue attached to failed, unpaid, or unresolved subscription payments that may become churn if the payment is not recovered.
Add the monthly recurring value of failed Stripe invoices or failed subscription payments that remain unresolved. Then separate recovered revenue from final churn once the dunning window ends.
No. MRR at risk is a temporary recovery state. Churned MRR is the unresolved amount that remains after retries, customer emails, update links, and escalation fail.
Decline codes show the right recovery path. Expired cards need update links, insufficient funds need timing, bank blocks need clear explanation, and high-value failures may need founder review.
Estimate how much failed payment revenue may turn into churn.
Open guideUse the public benchmark to estimate failed MRR by SaaS stage.
Open guideCopy customer-safe email templates for common Stripe failure reasons.
Open guideFree during beta
Connect Stripe, group failures by reason, and track recovered revenue before at-risk MRR becomes final churn.