Revenue recovery software that reads first and fixes on your rules
RevenueLeak works in four steps: connect, audit, fix, recover. It connects to your billing system with a restricted read-only key, measures where recurring revenue is leaking in dollars per month, gives you a ranked list of accounts to fix and recovers failed payments only after you switch a rule on.
How revenue recovery software works in four steps
Every account goes through the same sequence. Nothing is written to your billing system during the first three steps, and the fourth step only runs the rules you turn on.
| Step | What happens | Writes to billing |
|---|---|---|
| Connect | You add a restricted read-only key or authorize the app where the platform offers it | Never |
| Audit | We read invoices, subscriptions, prices, coupons, refunds and disputes and score nine leak categories | Never |
| Fix | You get a ranked list of accounts with the dollar amount and the fix for each one | Never |
| Recover | Retries, recovery emails and card update requests run for the rules you switch on | Only per rule |
Connect with a restricted read-only key
On Stripe you create a restricted key with read permission on the objects we list and nothing else, then paste it into RevenueLeak. Paddle, Chargebee and Recurly work the same way with their read-only API keys. Shopify and WooCommerce use app authorization, where the store owner approves a list of read scopes on the platform screen. You can revoke the key or the app at any moment from your billing dashboard, and the connection stops at once. Setup details for each platform sit on the stripe smart retries page and the other integration pages.
- Read permission on invoices, subscriptions, customers, prices, coupons, refunds and disputes.
- No permission to create charges, change prices or delete objects.
- One key per connected billing account, counted against your plan.
What we read and what we never touch
We read the billing records that explain revenue. We never read card numbers, because billing platforms do not expose them through the API, and we never touch your product database, your CRM or your bank.
- We read: invoices and their payment attempts with decline codes, subscription status and plan history, price lists, coupons and their duration, refunds, disputes with response deadlines, card expiry month and year, cancellation dates and reasons.
- We never touch: full card numbers, bank account details, your application data, your customers' passwords, your payout settings.
- We never change: prices, plans, coupons, refunds or subscription status. Those fixes stay with your team, with the account list in hand.
What happens in the first audit
The first audit reads up to 24 months of history, so seasonal patterns and old discounts show up. It then scores each of the nine leak categories in USD per month. For example, if 40 renewals failed last month and 25 of them were retried once and given up, that line shows the monthly value of those 25 subscriptions and the decline code behind each one. The billing leakage page shows the full structure of the audit document.
- Failed renewals without a full retry schedule.
- Cards expiring in the next 30, 60 and 90 days with no update request.
- Customers on legacy prices below the current price list.
- Upgrades and seat changes that never billed the prorated difference.
- Comped or fully discounted accounts with active usage.
- Coupons with no end date on large accounts.
- Refund patterns and disputes past their response deadline.
- Cancellations after a failed payment and save candidates.
- Abandoned checkouts and failed renewals on Shopify and WooCommerce.
Fix the list, account by account
Each category comes with a ranked list: account, amount per month, reason, suggested fix. A legacy price line tells you the current price, the old price and the difference. A forever coupon line shows when it was created and what it costs each month. Your team decides and makes the change in the billing system. You export the list to CSV on every plan and to PDF from Growth up.
Recover failed payments with rules you switch on
Recovery is the only part that writes, and it writes only what a rule allows. A retry rule asks the billing system to try the invoice again on a schedule chosen by decline code. An email rule sends recovery or card update emails from your sending domain. A page rule gives each customer a secure link to update the card. All of it is described on the failed payment recovery and dunning software pages. If built-in billing retries are already on, we measure what they leave behind and add only the missing steps.
A monthly number for the board
Every audit ends with one figure: leak in USD per month, split into the recoverable part and the part that needs a pricing or contract decision. The audit runs monthly on Starter, weekly on Growth and daily on Scale and Enterprise. See revenue optimization software for the plan limits.
Questions about how RevenueLeak works
Not by default. The connection is read-only. Retries and emails run only after you switch a rule on, and you can switch it off at any time.
It depends on history size. Most accounts see the first categories within the hour, and the full report when all history has been read.
We keep the billing records needed for the audit for as long as your account is active and delete them after you close it. Card numbers never reach us.
Yes, the estimate on the homepage is free and uses the numbers you type in. The full audit and recovery are part of the paid plans.
Yes. We read every attempt the billing system made and only add retries, emails or card update requests where a gap remains.
Yes. Starter includes one account, Growth two, Scale five and Enterprise twenty.