Is my billing data safe?

Yes. We only read data — we cannot modify your billing, create charges, or access card numbers. All supported platforms (Stripe, Polar, Paddle) support restricted read-only keys. Your key is used only during the scan and is never stored or logged.

Which billing platforms do you support?

We support Stripe, Polar.sh, and Paddle. Select your platform on the scan page and we'll guide you through creating an API key. Each platform gets a tailored scan covering the leak types it supports.

What permissions does the API key need?

Read access for: Customers, Subscriptions, Invoices, Products, Prices, Coupons, and Payment Methods (exact names vary by platform). We provide step-by-step instructions on the scan page. It takes about 60 seconds to create.

How long does the scan take?

Under 90 seconds for most accounts. Larger accounts (1,000+ customers) may take up to 3 minutes. You'll see real-time progress as we scan each category.

What exactly do you scan for?

We run 10 automated checks: (1) Expired coupons still discounting, (2) Legacy pricing below current rates, (3) Forever discounts with no end date, (4) Stuck subscriptions stuck in bad states, (5) Expiring cards within 90 days, (6) Uncollected revenue with open invoices, (7) Missing payment methods on active subscriptions, (8) Unbilled overages — quantity mismatches and usage exceeding plan limits, (9) Expired trials — subscriptions stuck in trialing status, (10) Duplicate subscriptions — customers charged twice after failed upgrades.

What do I do with the report?

Open the report. See the leak. See the dollar amount. See the one-sentence fix. Click the link — it takes you straight to that customer in your billing dashboard. Fix it. That money hits your account next billing cycle.

What if you don't find any leaks?

Then your billing is clean. You get a perfect health score and some peace of mind. The free scan costs you nothing either way. If you're on a paid plan and we find less than $1,000/mo, you pay nothing.

What happens when a Stripe coupon expires?

When a Stripe coupon's redeem_by date passes, the coupon stops accepting new redemptions — but existing subscriptions keep the discount indefinitely. Stripe does not auto-remove expired coupons from active subscriptions. RevReclaim scans for these zombie discounts and shows you exactly which subscriptions are affected and how much they're costing you.

Is this the same as chargeback recovery?

No. Chargeback tools handle disputed payments. We find revenue you earned but aren't collecting: expired discounts still running, subscriptions stuck in failed states, cards about to expire, and outdated pricing that was never updated. Different problem, different fix.

Can I cancel the monthly plan anytime?

Yes. No contracts, no lock-in. Cancel anytime from your dashboard. Your data is deleted within 30 days of cancellation.

Is this worth it if I have fewer than 50 customers?

Probably not. Revenue leaks compound with scale. If you have 10 customers, you probably know each one by name. RevReclaim is built for the stage where your billing account has grown past what one person can monitor — typically 100+ customers, $30K+ MRR.

Why should I trust you with my billing data?

Fair question. We designed RevReclaim to work with restricted, read-only API keys scoped to specific resources. We only perform read operations, never modify your data, never see card numbers, and never store the key after the scan.

The SaaS Billing Health Checklist: 15 Leaks Hiding in Your Stripe Account

A billing leak is revenue that a SaaS company has earned but is not collecting due to billing configuration errors, expired payment methods, or system-level issues in Stripe, Paddle, or Polar. The average SaaS founder loses $2,500 per month to billing blind spots. This 15-point checklist covers the most common leaks across five categories: failed payment recovery, stuck subscriptions, pricing integrity, payment method health, and subscription lifecycle. RevReclaim checks all 15 items automatically in 60 seconds at revreclaim.com/scan.

How Do You Score Your SaaS Billing Health?

Go through each item one by one. For every "no" answer, you've found a potential revenue leak. At the end, tally your score to get your Billing Health Score.

12-15 checks passed: Your billing is healthy. Nice work.
8-11 checks passed: You have moderate leaks. Worth fixing.
Below 8: You're losing serious money. Act now.

Or skip the manual work — run a free automated scan that checks all 15 in 60 seconds.

Failed Payment Recovery

1. You have dunning emails enabled and configured

When a customer's card fails, does your billing platform automatically email them? Stripe's default dunning is basic — three retries over a few weeks, then cancellation. Most founders never customize this.

What to check: Go to Stripe Dashboard → Settings → Subscriptions and emails → Manage failed payments. Is Smart Retries enabled? Are customer emails turned on?

The leak: Without proper dunning, a single failed $99/mo subscription means $1,188/year lost — from just one customer. See our complete guide to Stripe Smart Retries and dunning configuration.

2. You're monitoring failed payment rates weekly

If you don't check, you don't know. Failed payments typically run between 4-8% of charges for SaaS businesses. If yours is above 8%, something is wrong.

What to check: Stripe Dashboard → Payments → filter by "Failed". What's your rate over the last 30 days?

The leak: A 10% failure rate on $30K MRR means $3,000/month in charges that didn't go through. Even recovering half of those is $1,500/month back in your pocket.

3. You follow up on "past due" subscriptions within 48 hours

Stripe marks subscriptions as "past_due" when a payment fails but the subscription hasn't been canceled yet. This is your recovery window.

What to check: Stripe Dashboard → Subscriptions → filter by "Past due". How many are sitting there right now?

The leak: Every day a past-due subscription sits untouched, the chance of recovery drops. After 30 days, recovery rates fall below 15%.

Stuck Subscriptions

4. You have zero active subscriptions with no successful payment in 60+ days

These are "stuck subscriptions" — technically active in your system, but the customer hasn't actually paid in months. They inflate your MRR and hide the real number.

What to check: Export your subscription list. Filter for subscriptions where the last successful payment was more than 60 days ago. Any results?

The leak: If you have 5 stuck subscriptions at $49/mo each, your reported MRR is $245/mo higher than reality. That's $2,940/year in phantom revenue affecting your decisions.

5. You audit canceled-but-active subscriptions monthly

Sometimes a customer cancels through your app, but the Stripe subscription doesn't properly terminate. Or a webhook fails. The customer thinks they've canceled, you think they're still paying — but the charge keeps failing silently.

What to check: Cross-reference your app's user status with Stripe's subscription status. Any mismatches?

The leak: These mismatches create support headaches, chargebacks, and lost trust. One chargeback costs you the transaction amount plus a $15 dispute fee.

Pricing and Plan Integrity

6. No customers are on discontinued or legacy pricing tiers

You raised prices 6 months ago, but 30% of your customers are still on the old plan. That's fine if intentional — but do you even know which customers are grandfathered?

What to check: List all active Price IDs in Stripe. Are any attached to Products that you've since updated or archived?

The leak: If you raised prices from $29 to $49/mo and 50 customers are still on $29, that's $1,000/month you're leaving on the table — $12,000/year.

7. All active coupons have an expiration date

Open-ended coupons are a ticking time bomb. A 20% discount you ran during Black Friday 2024 might still be applied to new sign-ups if you forgot to set an expiration.

What to check: Stripe Dashboard → Products → Coupons. Look for any coupon where "Redemption deadline" is empty or "Duration" is set to "forever".

The leak: An expired promotion still giving 20% off on a $99/mo plan costs you $237.60 per customer per year. Multiply by every customer who found that coupon code.

8. No customer is receiving a larger discount than intended

Stacked coupons, manually applied discounts, and promotional pricing can compound in unexpected ways. A customer might be getting 40% off when you intended 20%.

What to check: Export subscriptions with discounts. Sort by discount percentage. Anything above your maximum intended discount?

The leak: Even 5 customers with an accidental extra 20% discount on a $99 plan costs you $1,188/year.

Payment Method Health

9. Less than 5% of active subscriptions have expired payment methods

Credit cards expire. If a customer's card expires in March and their next charge is in April, that charge will fail unless they've updated their card.

What to check: Stripe Dashboard → Customers. Export and check the card expiration dates against upcoming renewal dates.

The leak: Each expired card is a failed payment waiting to happen. If 20 customers have cards expiring next month and your average plan is $79/mo, that's $1,580 at risk.

10. You send proactive card expiration reminders

Don't wait for the charge to fail. Email customers 30 days before their card expires so they can update it proactively.

What to check: Do you have any automated email or in-app notification for upcoming card expirations? Most founders don't.

The leak: Proactive reminders recover 60-70% of expiring cards before they fail. Without them, you rely on dunning after the fact — which only recovers 30-40%.

Subscription Lifecycle

11. You're tracking involuntary churn separately from voluntary churn

Involuntary churn (failed payments) and voluntary churn (customer cancels) require completely different strategies. If you're lumping them together, you're flying blind.

What to check: Can you pull a report showing churn broken down by reason? Do you know what percentage of your churn is payment failures vs. deliberate cancellations?

The leak: Involuntary churn is typically 20-40% of total churn for SaaS businesses. It's also the easiest to fix. If you don't measure it, you can't improve it. See why Stripe subscriptions get cancelled for the full breakdown of voluntary vs. involuntary churn, and SaaS churn vs revenue leakage for a framework on which to fix first.

12. Trial-to-paid conversion is tracked and above 15%

If you offer a free trial, what percentage convert to paid? The SaaS average is 15-25%. Below 15% and you likely have a billing configuration issue (not just a product issue).

What to check: Count the number of trial subscriptions that became paid in the last 90 days vs. total trials started.

The leak: If 100 trials start per month and you convert at 10% instead of 20%, that's 10 lost customers/month. At $49/mo, that's $490/month in missed revenue — $5,880/year.

13. No subscriptions are stuck in "incomplete" or "incomplete_expired" status

Stripe creates subscriptions in "incomplete" status when the initial payment requires further action (like 3D Secure). If the customer never completes it, it stays stuck.

What to check: Stripe Dashboard → Subscriptions → filter by "Incomplete". How many are sitting there?

The leak: Each incomplete subscription is a customer who wanted to pay but couldn't complete the process. These are the easiest recoveries — a simple email can bring them back.

Data Integrity

14. Your MRR calculation matches Stripe's actual collected revenue

Many founders calculate MRR by summing up active subscription prices. But this ignores failed payments, discounts, and prorations. Your real MRR is only what you actually collect.

What to check: Compare your calculated MRR (sum of subscription prices) vs. actual revenue received in the last 30 days. Is there a gap?

The leak: A 10% gap between reported and actual MRR on a $50K business means $5,000/month in revenue you think you have but don't. This affects fundraising, hiring, and every financial decision you make.

15. Webhook failures are monitored and alerts are configured

Stripe webhooks are how your app knows about payment events. If a webhook fails and isn't retried, your app and Stripe get out of sync — leading to customers who paid but don't have access, or customers with access who haven't paid.

What to check: Stripe Dashboard → Developers → Webhooks. Check the failure rate. Is it above 1%?

The leak: Webhook sync issues cause support tickets, incorrect access, and revenue discrepancies that compound over time.

What Is a Good SaaS Billing Health Score?

Count your "yes" answers:

| Score | Grade | What It Means | |-------|-------|---------------| | 13-15 | A | Your billing is tight. Minor optimizations possible. | | 10-12 | B | A few leaks to patch. Probably losing $500-1,500/mo. | | 7-9 | C | Significant leaks. Likely losing $1,500-3,000/mo. | | 4-6 | D | Major revenue leakage. Losing $3,000-5,000/mo. | | 0-3 | F | Critical. You need a billing audit immediately. |

How Can You Automate a SaaS Billing Audit?

Going through 15 checks manually takes hours. Exporting data, cross-referencing subscriptions, checking coupon expirations — it's tedious but important work.

Or you can let RevReclaim do it in 60 seconds.

RevReclaim scans your Stripe, Paddle, or Polar account and checks all 15 of these items automatically. You get a billing health score, a breakdown of every leak found, and actionable steps to fix each one.

RevReclaim is free to use, takes 90 seconds, and uses read-only access — billing data never leaves the customer's account.

Run your free billing health scan now →

Frequently Asked Questions

What is a billing leak in SaaS?

A billing leak is revenue that a SaaS company has earned but is not collecting. Common causes include failed payments without proper dunning, expired coupons still giving discounts, stuck subscriptions inflating MRR, and customers on legacy pricing tiers. The average SaaS billing account leaks 8.4% of revenue to billing blind spots.

How much revenue do SaaS companies lose to billing leaks?

The average SaaS company loses $2,500 per month to billing blind spots. For companies in the $10K-$30K MRR range, leakage can reach 9.3% of revenue. RevReclaim scans billing accounts to identify exact dollar amounts lost to each type of leak.

What is a billing health score?

A billing health score is a 0-100 rating of how well a SaaS company's billing system is configured to collect revenue. A score of 90-100 (Grade A) means billing is well-optimized. A score below 50 (Grade D or F) indicates critical leaks that need immediate attention. The average SaaS billing account scores 56 out of 100.

How long does a billing audit take?

A manual billing audit using this 15-point checklist takes 2-4 hours. RevReclaim automates all 15 checks and delivers results in 60-90 seconds using a read-only API key from Stripe, Paddle, or Polar. The automated scan includes exact dollar amounts for every leak found.