Recurly dunning, with the leaks it leaves behind in dollars
Recurly dunning campaigns retry past due invoices and send reminders on the schedule you configure. When a campaign ends, the invoice is either paid or the subscription is closed, and the remaining revenue rarely gets a second look. RevenueLeak connects to Recurly with an API key used for read requests only, shows in dollars per month how much leaves through failed payments, legacy prices, open-ended coupons and missed proration, and adds recovery only after your campaign stops.
What we read from Recurly
The audit reads what each account should pay and what was collected. Every read goes through the official Recurly API.
| Recurly record | What the audit uses it for |
|---|---|
| Accounts | Status, country for retry timing, billing info with card expiry, never the full card number |
| Subscriptions | Plan, add-ons, quantity, state, renewal date, expiration reason |
| Invoices | Charge and credit invoices, past due, paid and failed states, dunning state |
| Transactions | Each payment attempt, its result and the decline reason |
| Plans and add-ons | Your current price list, compared with the price each account pays |
| Coupons and redemptions | Discount size, duration and which accounts still redeem them |
| Credits and refunds | Refund patterns, credits after downgrades, repeat refunders |
- The first audit reads up to 24 months of history.
- Card numbers stay with your payment gateway and never reach us.
After the dunning campaign ends
A Recurly dunning campaign has a fixed number of steps and an end action. When it ends unpaid, the subscription usually expires and the account leaves without a word, even when the customer only had a card problem. RevenueLeak reads every invoice that went past due, every attempt and its decline reason, and shows three figures for the period: revenue recovered by the campaign, revenue lost when the campaign ended, and revenue still open.
- Hard declines such as an expired or stolen card get a card update email with a secure payment update page instead of another retry.
- Soft declines can get one more attempt near the next likely payday after the campaign ends, if you switch that rule on.
- Steps already covered by a Recurly dunning email stay off on our side, so one invoice never produces two emails.
For example, if 2,000 USD of monthly subscriptions expired at the end of dunning in a month and a quarter of those accounts had a soft decline, the report shows 500 USD per month as the part most likely to come back and ranks those accounts. Timing by decline code is described on failed payment recovery, and the sequence design is on dunning software.
Leak categories on a Recurly site
Eight of the nine categories apply to Recurly. Abandoned e-commerce checkouts belong to stores.
- Failed renewals that expired at the end of dunning.
- Cards that expire in the next 30, 60 and 90 days, covered early by the card updater.
- Accounts on legacy plan prices below your current list.
- Plan 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.
- Refunds, credits and disputes near the response deadline.
- Cancellations and expirations after a failed payment, flagged as save candidates through the reduce churn workflow.
The method for each category is on the billing leakage page.
What we read and what we never touch
The audit only reads. RevenueLeak never edits plans, coupons, invoices, accounts or your dunning campaigns. A retry rule needs permission for that one action, and the app asks for it only when you switch the rule on. Recovery emails go from your verified sending domain and count inside the monthly email limit of your plan. The full permission model, retention and encryption are on revenue assurance software.
Connecting Recurly
You create a dedicated API key in your Recurly site settings and paste it into RevenueLeak with your site subdomain. RevenueLeak calls it with read requests only, and the first audit starts as soon as the connection is saved. Keep the key for RevenueLeak alone, so you can revoke it at any time without touching other tools, and the connection stops on the next request. Each Recurly site counts as one connected billing account. Teams comparing setups across platforms can look at chargebee dunning and the full list on billing integrations.
Plans for Recurly 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.
Recurly dunning questions
No. They keep running as configured. We read the outcome and add steps only after a campaign ends unpaid.
No. The audit only reads. A retry runs only after you switch on that rule and grant permission for it.
No. If a Recurly dunning email already covers a step, our email for that step stays off.
Yes. Amounts are reported in the original currency and converted to USD for the monthly leak total.
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.