Your customer didn't cancel. Their payment failed. Imagine a SaaS with $20,000 MRR: customers are subscribing, retention looks healthy, and recurring revenue is growing. Then several renewal payments fail because of expired cards, insufficient funds or authentication requirements, leaving $1,200 unpaid. Does that mean $1,200 of MRR has been lost? Not necessarily. Some payments may be recovered automatically, others require customer action, and a portion could eventually become involuntary churn. A failed payment, an unpaid invoice and a canceled subscription are three different events. Understanding how they connect is essential for managing SaaS revenue.
4 things to check in Stripe today
Smart Retries is turned on (Dashboard → Revenue recovery → Retries).
Failed-payment emails to customers are turned on, with a link to update their card.
Someone follows up personally on high-value accounts that stay unpaid.
01
What is a failed payment in Stripe?
A failed payment occurs when Stripe attempts to collect money from a customer but the payment does not succeed. For subscription businesses, this often happens when Stripe charges a saved payment method for a recurring invoice.
A customer subscribes for $99 per month. Their first three payments succeed. On the fourth renewal, their bank declines the transaction and the invoice remains unpaid. The customer has not necessarily requested cancellation, and the subscription may still be eligible for payment recovery.
Stripe records the failed attempt and, depending on configuration and the failure reason, can initiate a recovery process. A failed payment is a collection event; churn is a subscription or recurring-revenue event. They are connected, but not interchangeable.
The cause matters because not every failure can be resolved in the same way.
Insufficient funds: the bank account or available card balance cannot cover the transaction. This can be temporary; a later attempt may succeed when funds become available.
Expired or outdated cards: a replaced or expired card can interrupt billing even when the customer wants to stay. Card account updater services help in some eligible cases, but cannot correct every outdated card.
Bank declines: issuer authorization rules, transaction restrictions or risk checks can block payment. Some declines are temporary; certain hard declines cannot be resolved by repeatedly submitting the same payment method.
Authentication required: payments such as those requiring 3D Secure may need customer action. Retrying without resolving authentication may not collect the payment.
Missing or incorrectly configured payment methods: a saved card on the customer account is not necessarily the method selected for the subscription. Check failure reasons and subscription payment settings together.
Tip
Not all failed payments require the same recovery action. Distinguish temporary failures from cases that need a suitable payment method or customer authentication.
03
A practical example: $20K MRR and $1,200 in failed payments
Consider 200 customers paying $100 per month: 200 × $100 = $20,000 MRR. All subscriptions are billed monthly, without discounts, taxes, upgrades, downgrades or cancellations. In April, the business issues $20,000 in subscription invoices.
April billing activity after the initial payment attempts
April billing activity
Amount
Subscription invoices issued
$20,000
Successfully collected
$18,800
Failed and unpaid
$1,200
Initial collection rate
94%
$18,800 ÷ $20,000 × 100 = 94% initially collected
Twelve customers have failed payments, creating a $1,200 collection gap. MRR has not automatically fallen to $18,800. If the affected subscriptions remain eligible under the chosen MRR methodology, their recurring value may still count during recovery.
Investigate two different questions: how much of the $1,200 can be collected, and how many subscriptions might ultimately be lost if recovery fails. Those questions require different metrics.
04
What happens after a Stripe payment fails?
Stripe Billing supports recovery workflows for failed recurring payments. The sequence depends on the payment method, failure type and account configuration.
Payment attempt fails: Stripe attempts to collect a recurring invoice. For an eligible failed attempt, it generates invoice.payment_failed.
The subscription enters recovery: an established subscription's failed renewal can make it past_due. This does not necessarily mean it has been canceled.
Stripe attempts recovery: depending on settings, it may retry, notify the customer or ask them to update payment information. Not every failure qualifies for an automatic retry.
Payment is recovered or remains unresolved: payment reduces the collection gap. Otherwise, configured recovery rules and other applicable invoices determine the eventual status. Stripe can leave the subscription past_due, mark it unpaid or cancel it; other eligible configurations may apply.
Watch out
A first payment on a new subscription behaves differently from a renewal. A new automatically charged subscription requiring immediate payment may remain incomplete until payment succeeds, rather than enter the usual renewal recovery process. Separate these populations when measuring failure rates and involuntary churn.
05
How Stripe Smart Retries work
A payment that failed today may succeed later, especially after a temporary failure. Stripe Billing's Smart Retries uses machine learning and payment-related signals to choose retry times intended to improve the likelihood of success, within configured limits.
You can configure the retry count and recovery period, or use custom retry schedules. Automatic retries should not be the entire recovery strategy: some customers must intervene before payment can succeed.
For certain hard decline codes, Stripe cannot execute another charge on the same payment method until a new or suitable one is provided. This includes some lost or stolen cards, revoked authorizations and authentication requirements. A scheduled retry is therefore not always an executed payment attempt.
If a customer's card has expired, retrying it may not solve the problem. The customer needs to update their payment details. Stripe can send automated failure notifications with a hosted payment update link or a configured customer management experience.
This lets customers resolve some payment problems without individual outreach from your team. A recovery message should be clear, actionable and proportionate to the situation.
Not every failure needs an urgent cancellation warning. Telling a customer their subscription has already been canceled when it is merely past_due creates unnecessary confusion. Resolve billing friction while maintaining customer trust.
What happened?
What does the customer need to do?
Where can they securely update their payment information?
07
What happens when payments are recovered?
Return to the $1,200 in initially failed payments. Over the following days, some succeed through retries and others after customers update their payment methods.
Recovery outcomes for the initially failed payments
Recovery activity
Amount
Initially failed
$1,200
Recovered through retries
$650
Recovered after customer action
$350
Still unpaid
$200
Total recovered
$1,000
($650 + $350) ÷ $1,200 × 100 ≈ 83.3% recovery by value
The business has recovered $1,000, or 83.3% of the initially failed amount. Its remaining collection gap is $200. The recovery rate uses the same failed-payment cohort for its numerator and denominator.
08
Recovered payments are not automatically New MRR
For the April invoice cohort, the subsequent $1,000 recovery improves collections to $19,800, assuming no other changes.
Suppose a customer's $100 renewal fails but the subscription remains eligible for MRR. Stripe collects it three days later. The business has recovered $100 in cash, not necessarily generated $100 of New MRR: the subscription's recurring value may have counted both before and after the failed attempt.
Recovering an invoice and acquiring a new subscription are different economic events. Confusing them overstates recurring revenue growth.
Involuntary churn occurs when a customer loses a subscription because of a payment or billing issue, rather than deliberately choosing to cancel.
Customer A no longer needs the software and cancels: voluntary churn. Customer B wants to stay, but their renewal fails, recovery is unsuccessful and the subscription is eventually canceled because payment remains unresolved: a typical involuntary churn scenario.
A failure does not establish involuntary churn at the instant it occurs. Status, termination reason, timing and the chosen MRR methodology matter. A subscription may remain past_due during recovery and later become unpaid or canceled, depending on configuration. Under certain methodologies, an unpaid or canceled subscription may stop contributing to MRR.
Track the failure, recovery outcome and subscription status separately. Do not classify every invoice.payment_failed event as churn; distinguish temporarily unpaid revenue from recurring revenue actually lost.
10
Five metrics every SaaS founder should monitor
Monitoring is more useful when it goes beyond counting declined charges. Separate these five measures and define their reporting scope.
Initial payment failure rate: initially failed payment value ÷ total eligible attempted payment value × 100. Here, $1,200 ÷ $20,000 = 6%. You can also measure by transaction count, using consistent exclusions and denominators.
Payment recovery rate: recovered value from a defined failed-payment cohort ÷ initially failed value in that cohort × 100. Here, $1,000 ÷ $1,200 ≈ 83.3%. A three-day recovery rate is not directly comparable with a 30-day rate; use consistent windows and allow cohorts to mature.
Outstanding failed-payment value: the amount still unpaid in a defined invoice population. A $100 invoice that fails three times does not automatically represent $300 owed. Do not sum failed attempts as separate invoices.
Involuntary churnMRR: recurring value lost when subscriptions cease qualifying because of payment-related issues. Four $100 monthly subscriptions canceled after unsuccessful recovery may represent $400 under a cancellation-based methodology. This is not automatically equal to unpaid invoice amounts, especially for annual billing, taxes, discounts and adjustments.
Time to recovery: how long collection takes. Customers recovered after 1, 4 and 9 days illustrate different collection delays. Define whether measurement starts at the first failed attempt and ends when the invoice is successfully paid; use it to assess process improvements.
11
How to monitor failed payments using Stripe
The Stripe Dashboard is a practical starting point. Depending on configuration and reporting scope, Revenue Recovery analytics can show failed payment volume, failure rates, recovered volume, recovery rates and methods, decline reasons and customers in recovery.
Three Stripe objects, three related questions
Stripe object
What it helps you understand
Subscription
What it helps you understandSubscription lifecycle, status and recurring plan information
Invoice
What it helps you understandAmount billed, amount remaining, payment status and collection attempts
PaymentIntent
What it helps you understandPayment execution, authentication requirements and payment failures
Stripe's built-in recovery analytics use their own eligibility and reporting definitions. For example, the revenue recovery overview focuses on recurring subscription payments and excludes certain initial payments after trials. Match those definitions before reconciling your own invoice or payment metrics.
An Invoice identifies what the customer owes; a PaymentIntent tracks payment execution; a Subscription describes the recurring billing relationship. Advanced reporting may also require payment allocations, credit notes, payment methods and refunds.
12
Monitor the important Stripe events
Webhooks provide event-driven updates that help keep reporting synchronized. These events describe related but different changes.
Events used in payment recovery reporting
Event
Typical purpose
invoice.payment_failed
Typical purposeDetect a failed invoice payment attempt
invoice.payment_action_required
Typical purposeDetect a payment that needs customer authentication (e.g. 3D Secure)
invoice.paid
Typical purposeIdentify when an invoice has been paid
invoice.updated
Typical purposeMonitor invoice changes and certain retry scheduling updates
customer.subscription.updated
Typical purposeMonitor subscription status changes
customer.subscription.deleted
Typical purposeDetect subscription cancellations
Do not assume events arrive exactly once or in chronological order. Verify signatures, handle duplicate deliveries and use the object's current state when appropriate.
Counting invoice.payment_failed events without deduplicating invoices can significantly overstate failed revenue. One invoice can generate multiple failure events during recovery. An invoice marked paid also needs payment-origin context when measuring actual collections, rather than treating every status transition as new cash.
Build a report around eligible subscription renewal invoices that first failed in April, rather than isolated failure counts. In this example, every failed invoice is worth $100: 12 initially fail and 10 are recovered.
April's initially failed renewal invoice cohort
Metric
April cohort
Initially failed invoices
12
Initial failed value
$1,200
Recovered invoices
10
Recovered value
$1,000
Remaining unpaid value
$200
Recovery rate by value
83.3%
Median time to recovery
3 days
Break the cohort down by failure reason, recovery method, plan, customer segment, invoice value and subscription status after the recovery window. A strong overall rate can conceal weaker recovery among annual subscribers or high-value accounts.
A cohort-based approach avoids mixing newly failed invoices with recoveries from earlier periods. The median recovery time shown is illustrative, not derived from these aggregate amounts; calculate your actual median from the real payment dates.
14
What should SaaS founders actually do?
The objective is to improve collection outcomes, not simply count failures. Four situations call for different investigations.
Match the investigation to the signal
Situation
What to investigate
Initial failure rate rises from 4% to 8%
What to investigatePayment methods, decline reasons, countries and customer segments; payment mix, customer behavior and billing configuration
Failures are stable, but recovery deteriorates
What to investigateRetry settings, payment update flows, notifications and non-retryable decline reasons
Collections recover, but payment-related cancellations increase
What to investigateRecovery definitions, cancellation timing and customers lost despite partial or delayed collections
A few high-value accounts remain unpaid
What to investigateCustomer relationships and failure reasons; consider personalized follow-up instead of automated emails alone
Strong payment recovery and strong subscription retention are related, but not identical. A growing share of non-retryable failures requires different action from temporary declines. The right response depends on why payment failed and on the customer relationship.
15
Bringing recurring revenue and payment recovery together
Stripe provides subscription, invoice, payment and recovery information. As a SaaS grows, founders may want to connect those billing events with broader recurring revenue performance.
FlowMRR helps Stripe-powered SaaS businesses monitor recurring revenue metrics, subscription movements, failed payments and recovery activity in one analytics environment. The objective is not to replace Stripe's payment recovery capabilities, but to understand recurring revenue performance alongside collection activity.
A failed payment is a warning, not necessarily a lost customer
Failed subscription payments are a normal operational challenge. They do not always mean customers are dissatisfied or planning to cancel.
A reliable monitoring process keeps these five things separate:
Payments that failed.
Amounts still awaiting collection.
Payments successfully recovered.
Subscriptions that remain active or recoverable.
Recurring revenue actually lost because of unresolved payment issues.
MRR tells you the size of the recurring business; payment recovery helps protect the cash collection behind it. Both matter, but they are not the same metric.
Follow failed payments through to their recovery outcome. Keep collection activity separate from subscription status and recurring revenue movements.
Free forever up to $10,000 MRR. Every feature included.
Questions
What happens when a Stripe subscription payment fails?+
Stripe records the failed attempt and may start recovery depending on payment method, failure reason, subscription state and account settings. A failed renewal on an established subscription may result in past_due. Retries and customer notifications can help resolve eligible failures.
Does a failed Stripe payment automatically cancel a subscription?+
No. A failed renewal does not necessarily cancel it immediately. Stripe can retry eligible payments and apply configured recovery rules before the subscription is canceled, marked unpaid or left past due.
Does a failed Stripe payment reduce MRR?+
Not necessarily. A failed payment and a reduction in MRR are different events. Depending on status and the chosen MRR methodology, the subscription may continue contributing during recovery.
What are Stripe Smart Retries?+
Smart Retries is a Stripe Billing recovery feature that uses payment-related signals to select retry times for eligible failed payments. It operates within the configured retry policy and cannot automatically resolve every decline.
What is involuntary churn in SaaS?+
Involuntary churn is a subscription lost because of a payment or billing issue, rather than a deliberate cancellation decision. Failed payments can cause it when recovery fails and the subscription no longer qualifies as recurring revenue.
How do you calculate a payment recovery rate?+
For a defined failed-payment cohort, divide recovered failed-payment value by initially failed-payment value and multiply by 100. Recovering $1,000 from $1,200 gives approximately 83.3%. Use a consistent scope and recovery observation period.
Can Stripe automatically recover failed payments?+
Yes. Stripe Billing supports recovery through Smart Retries, customer notifications and payment method updates. Recovery depends on the failure reason, eligible method and account configuration, and is not guaranteed.
Is recovered revenue the same as New MRR?+
No. Recovering an unpaid recurring invoice does not automatically create New MRR. If its subscription was already included in MRR, collecting the invoice improves cash collection without necessarily changing the recurring base.
