Quick Definition
Recurring billing is the automatic, repeated charging of a customer's payment method at regular intervals for ongoing access to a product or service. It is the billing model that powers every SaaS company, subscription box, and membership service.
When it works, recurring billing is invisible. The customer's card is charged, the invoice is paid, and no one thinks about it. When it fails, and it will fail for 5-10% of your transactions, it becomes the single largest source of preventable revenue loss.
The baseline: Across subscription businesses, recurring billing failures account for 20-40% of all churn. Not product issues, not competitors. Billing infrastructure.
How Recurring Billing Works
The subscription billing loop
Every recurring billing cycle follows the same steps:
- Subscription created. Customer signs up, payment method stored on file.
- Billing period ends. The clock runs out on the current cycle (monthly, quarterly, annual).
- Invoice generated. Your billing system creates a new invoice with the subscription amount.
- Payment attempted. The stored card (or bank account) is automatically charged.
- Success or failure. Payment goes through, or it does not.
- Loop repeats. Next billing period starts, and the cycle continues.
Stripe Billing specifics
In Stripe's implementation, recurring billing works through the Subscription object:
- Subscription defines the plan, price, and billing interval
- Invoice is generated automatically at the start of each billing period
- PaymentIntent is created for each invoice and attempts the charge
- Webhooks fire at each step (
invoice.created,invoice.payment_succeeded,invoice.payment_failed)
Stripe handles the scheduling, invoice generation, and payment attempts automatically. Your job is to handle what happens when it fails.
The Failure Points in Recurring Billing
Recurring billing has a fundamental vulnerability: it relies on a stored payment method remaining valid and funded across every billing cycle for the entire customer lifetime.
Here are the specific points where it breaks:
Card expiration
Credit and debit cards expire every 3-5 years. For a subscription business with thousands of customers, cards are expiring every single month. Account updater services catch 60-80% of these, but the rest fail.
Insufficient funds
The customer's account does not have enough money at the exact moment the charge is attempted. This is the most common soft decline and the most recoverable.
Bank-initiated declines
Banks decline charges for reasons that have nothing to do with the card's validity:
- Unusual transaction patterns
- Spending limit exceeded
- International transaction blocks
- Fraud prevention algorithms
Card replacement
When a customer reports their card lost or stolen, the bank issues a new card with a new number. The old number on file fails immediately.
Outdated billing information
Address changes, name changes, or other profile updates that create mismatches with the bank's records.
Network and processing errors
Technical failures between the payment gateway, card network, and issuing bank. Temporary, but they still result in a failed payment.
Recurring Billing Failure Rates by Industry
Not all subscription businesses face the same failure rates:
| Industry | Average Monthly Failure Rate |
|---|---|
| B2B SaaS | 3-5% |
| B2C SaaS / Apps | 5-8% |
| Media / Streaming | 6-9% |
| E-learning | 5-7% |
| Health & Fitness | 7-10% |
| Subscription Boxes | 8-12% |
The variance comes from customer demographics, average transaction size, and payment method distribution. B2B SaaS tends to have lower failure rates because corporate cards are better maintained.
For detailed benchmarks, see Payment Recovery Benchmarks by Industry.
The Revenue Impact
The math on recurring billing failures compounds quickly.
Monthly impact
For a SaaS company with $200,000 MRR and a 6% failure rate:
| Metric | Value |
|---|---|
| Monthly revenue at risk | $12,000 |
| Recovered with no dunning (20%) | $2,400 |
| Recovered with dunning (70%) | $8,400 |
| Revenue saved by dunning | $6,000/month |
| Annual impact | $72,000 |
The compounding effect
Revenue loss from billing failures compounds because it is not just the failed payment you lose. It is:
- The current month's revenue (the immediate loss)
- All future months the customer would have paid (the LTV loss)
- Expansion revenue the customer would have generated through upgrades
- Referrals the active customer would have made
A $100/month customer with a 24-month expected lifetime represents $2,400 in lost LTV when recurring billing fails and no one follows up.
Recurring Billing Best Practices
1. Accept multiple payment methods
Do not limit customers to credit cards. Each additional payment method reduces your overall failure rate:
| Payment Method | Typical Failure Rate |
|---|---|
| Credit card | 5-10% |
| Debit card | 6-12% |
| ACH / Bank transfer | 0.5-2% |
| SEPA (Europe) | 0.5-1.5% |
| PayPal | 2-4% |
ACH and SEPA have dramatically lower failure rates because they pull directly from bank accounts, bypassing card-specific issues like expiration.
2. Implement pre-dunning
Send card expiration reminders before the card expires. Customers who update their card proactively never produce a failed payment in the first place.
See Pre-Dunning vs Dunning: Which Approach Recovers More Revenue?
3. Set up automated dunning
Every recurring billing system needs a dunning sequence that activates immediately on failure:
- Day 0: Email notification with payment update link
- Day 2: SMS reminder
- Day 3-4: Follow-up email with value reinforcement
- Day 6-7: Urgency message
- Day 10+: Final warning before cancellation
4. Configure smart retries
Not every failed payment needs the same retry schedule. Smart retries analyze the decline reason and pick optimal retry timing:
| Decline Type | Retry Strategy |
|---|---|
| Insufficient funds | Retry in 3-5 days (after payday) |
| Processing error | Retry in a few hours |
| Generic decline | Retry next day, then 3 days later |
| Expired card | Do not retry, request update |
5. Use grace periods wisely
A grace period gives customers continued access while you attempt recovery. Too short, and you cancel customers before retries can work. Too long, and customers get free access without paying.
Standard grace periods: 7-14 days for monthly, 14-30 days for annual.
6. Track billing health metrics
Monitor these recurring billing KPIs:
| Metric | Target |
|---|---|
| Authorization rate | > 95% |
| Monthly failure rate | < 5% |
| Recovery rate | > 60% |
| Involuntary churn rate | < 1% of total subscribers |
Recurring Billing and Revenue Metrics
Your recurring billing health directly drives your headline metrics:
MRR increases when billing succeeds and decreases when it fails. Every unrecovered failed payment is a direct MRR loss.
Net Revenue Retention takes a hit from involuntary churn caused by billing failures. A company with 110% NRR and 3% involuntary churn could be at 113% NRR if they recovered those payments.
Churn rate includes involuntary churn by default. If you are not separating voluntary from involuntary churn, your churn analysis is missing a major variable.
Key Takeaways
- Recurring billing powers SaaS revenue but fails 5-10% of the time.
- Card expiration, insufficient funds, and bank declines are the primary failure points.
- Failures compound. You lose the current payment, the LTV, and the expansion revenue.
- Multiple payment methods reduce risk. ACH and SEPA fail at 10-20x lower rates than cards.
- Automated dunning is non-negotiable. Manual follow-up does not scale, and every hour of delay reduces recovery odds.
Protect Your Recurring Revenue with Rekko
Rekko monitors your Stripe subscriptions and activates the moment recurring billing fails:
- Instant failed payment detection via Stripe webhooks
- Multi-channel dunning with email and SMS sequences
- Smart retry coordination that adapts to decline type
- One-click payment update via pre-authenticated links
- Revenue recovery dashboard showing exactly what you have saved