Chargebee dunning, measured and completed
Chargebee dunning retries failed invoices and emails customers on the schedule you set, and then it stops. What happens after the last step decides whether the revenue comes back. RevenueLeak connects to Chargebee with a read-only API key, measures in dollars per month how much ends the dunning schedule unpaid, finds the leaks dunning never looks at, such as legacy prices and open-ended coupons, and adds recovery only where your schedule ends.
What we read from Chargebee
The audit reads the records that describe what each customer should pay and what was collected. Every read goes through the official Chargebee API.
| Chargebee record | What the audit uses it for |
|---|---|
| Subscriptions | Status, plan and item prices, quantity, billing period, cancellation reason |
| Invoices | Amount due, paid, not paid and voided states, dunning status |
| Transactions | Each payment attempt, its result and the reason returned by the gateway |
| Plans, addons and item prices | Your current price list, compared with the price each customer pays |
| Coupons | Discount size, duration type and which subscriptions still carry them |
| Credit notes and refunds | Refund patterns, credits issued after downgrades, repeat refunders |
| Customers and payment sources | Card expiry month and year, never the full card number |
- The first audit reads up to 24 months of history.
- Card numbers stay with your payment gateway and never reach us.
What happens after the dunning schedule ends
When the last dunning attempt fails, Chargebee applies the action you configured: the subscription is canceled, paused, or left active with an unpaid invoice. Each choice leaks in a different way. A canceled subscription is lost revenue. An active subscription with an unpaid invoice is service delivered without payment. A paused one may never be resumed. The audit reads every invoice that finished dunning unpaid and sorts it into those three outcomes, with the dollar value per month for each.
- Hard declines such as an expired or lost card get a card update email with a secure payment update page, not another retry.
- Soft declines that ended the schedule can get one more attempt near the next likely payday, if you switch that rule on.
- When Chargebee already sends a dunning email for a step, our email for that step stays off, so customers never get two messages about one invoice.
For example, if 1,800 USD of monthly subscriptions finished dunning unpaid last month and half of that came from soft declines, the report shows 900 USD per month as the part with the best chance of coming back. The decline code logic is on failed payment recovery, and the email sequence design is on dunning software.
Leak categories on a Chargebee site
Eight of the nine leak categories apply to a Chargebee site. Abandoned e-commerce checkouts belong to stores.
- Failed renewals that ended dunning unpaid, canceled or paused.
- Cards that expire in the next 30, 60 and 90 days, handled early by the card updater.
- Customers on legacy item prices below your current price list.
- Upgrades and quantity changes where the prorated charge was not invoiced.
- Subscriptions with a 100 percent coupon that are still active.
- Coupons with a forever duration on large accounts.
- Credit notes, refunds and disputes near the response deadline.
- Cancellations after a failed payment, which are save candidates.
How each category is measured and priced is on the billing leakage page.
What we read and what we never touch
The audit reads. It never edits plans, item prices, coupons, invoices or subscriptions, and it never changes your dunning settings. A recovery rule that retries a charge needs permission for that one action, and RevenueLeak asks for it only when you switch the rule on. Recovery emails go out from your verified sending domain and count inside the monthly email limit of your plan. Permissions, retention and encryption are described on revenue assurance software.
Connecting Chargebee with a read-only key
Chargebee lets you create API keys with read-only access. You create one in your Chargebee site settings, paste it into RevenueLeak together with your site name, and the first audit starts as soon as the connection is saved. Test sites and live sites are separate in Chargebee, so connect the live site to see real revenue. You can delete the key at any time, and the connection stops on the next request. Each Chargebee site counts as one connected billing account. Other platforms are listed on billing integrations, and companies moving between platforms often compare this page with recurly dunning.
Plans for Chargebee sites
| Plan | MRR up to | Connected sites | 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 |
Full plan details are on revenue optimization software.
Chargebee dunning questions
No. Your dunning schedule keeps running as it is. We read its results and add steps only after it ends.
No. The audit uses a read-only key. A retry runs only after you switch on that rule and grant permission for it.
No. If Chargebee already sends an email for a step, our email for that step stays off.
Yes. Growth connects 2 sites, Scale 5 and Enterprise 20, with one combined report.
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.