Paddle subscription management with a revenue leak audit
Paddle runs checkout, tax and payments for your subscriptions, and it shows you each subscription on its own. What it does not give you is one number for the revenue that slips away across all of them: past due subscriptions that never come back, customers on prices you retired long ago, discounts that keep renewing, and cancellations right after a failed payment. RevenueLeak connects to Paddle Billing with an API key used for read requests only, measures each leak in dollars per month and lists the accounts to fix first.
What we read from Paddle Billing
The audit reads the records that describe what each customer should pay, what was billed and what was collected. Every read goes through the official Paddle API.
| Paddle record | What the audit uses it for |
|---|---|
| Subscriptions | Status, items, billing cycle, next billed date, scheduled changes, cancellations |
| Transactions | Billed amounts, collection result, past due and completed states, payment attempts |
| Products and prices | Your current price list, compared with the price each subscriber pays |
| Discounts | Amount, how many billing periods they apply to, which subscriptions carry them |
| Adjustments | Refunds and credits, grouped by customer, product and reason |
| Customers | Country and currency for timing and reporting, no card numbers |
- The first audit reads up to 24 months of history.
- Card data stays with Paddle. We never receive a card number.
Past due subscriptions in dollars
When a renewal payment fails, Paddle keeps trying to collect and the subscription sits in a past due state until it is paid or canceled under your settings. That built-in recovery stays exactly as it is. RevenueLeak reads every past due period and every attempt, then shows what the recovery left behind: subscriptions that ended canceled after a failed payment, amounts still open, and accounts that never received a request to update their payment method. For example, if 2,400 USD of monthly subscriptions moved from past due to canceled in a quarter, the report shows that figure per month and ranks the accounts by value. When you switch on the recovery email rule, each of those customers gets a plain email with a link to the payment method update flow Paddle provides. How the timing and wording work is described on failed payment recovery and dunning software.
Which leak categories apply to Paddle
Eight of the nine categories apply to Paddle Billing. Only the e-commerce checkout category belongs to stores.
- Failed renewals that ended past due or canceled without a full recovery sequence.
- Cards that expire in the next 30, 60 and 90 days, where Paddle exposes the expiry, with a pre-expiry request through the card updater.
- Subscribers on legacy prices below your current Paddle price list.
- Plan changes and quantity changes where the prorated difference was not billed.
- Subscriptions with a 100 percent discount that are still active.
- Discounts set to recur with no end on large subscriptions.
- Refund and credit adjustments, repeat refunders and their reasons.
- Cancellations after a failed payment, flagged as save candidates.
The method for each category is on the billing leakage page.
What we read and what we never touch
Paddle is the merchant of record, so it owns checkout, tax and the payment itself. RevenueLeak stays out of all three.
- We never change prices, products, tax settings or checkout.
- We never cancel, pause or edit a subscription during the audit.
- We never send email in your name until you verify a sending domain and switch a rule on.
- We never ask for your Paddle login. You create the API key yourself and can revoke it at any time.
The full permission model, retention and encryption are on the revenue assurance software page.
Connecting Paddle in a few minutes
You create an API key in your Paddle dashboard and paste it into RevenueLeak. The key is used for read requests only, and the first audit starts as soon as the connection is saved. Sandbox and live accounts are separate in Paddle, so connect the live account to see real revenue. A company that runs Paddle for one product and Stripe for another connects both and gets one combined report, as long as the plan has the connected accounts for it. Every platform we support is listed on billing integrations, and the Stripe side is on stripe smart retries.
Plans for Paddle accounts
| Plan | MRR up to | Connected accounts | Audit | Emails per month | Price |
|---|---|---|---|---|---|
| Starter | 10,000 USD | 1 | Monthly | 300 | 24 USD per month billed yearly, or 49 USD monthly |
| Growth | 100,000 USD | 2 | Weekly | 3,000 | 149 USD per month billed yearly, or 299 USD monthly |
| Scale | 1,000,000 USD | 5 | Daily | 20,000 | 399 USD per month billed yearly, or 799 USD monthly |
| Enterprise | above 1,000,000 USD | 20 | Daily | 100,000 | 999 USD per month billed yearly, or 1,999 USD monthly |
MRR in other currencies is converted to USD for the plan band. Full details are on revenue optimization software.
Paddle subscription management questions
No. Paddle keeps collecting past due payments as it does today. We measure what is left unpaid and add emails only where they are missing.
No. The audit only reads. Nothing in your subscriptions, prices or checkout is edited.
Yes. Amounts are reported in the original currency and converted to USD for the monthly leak total.
Yes, on plans with two or more connected accounts, starting with Growth.
Yes. The estimate on the home page runs in your browser without an account. The full audit and recovery are part of the paid plans.