Recurly has been in the subscription billing game for over a decade, and dunning has been part of the platform for almost as long. If you're already on Recurly, you've got a working dunning engine the day you sign up. The question is whether it's pulling its weight or whether you're quietly leaving 15 to 20 points of recovery on the table.
This is an honest look at what Recurly's dunning management does well, where it stops, and how to decide between staying with the built-in tool or layering a focused solution on top.
How Recurly dunning works under the hood
Recurly's dunning system is built around three concepts: retry schedules, dunning campaigns, and decline categories.
Retry schedules define when Recurly will re-attempt a failed charge. You get granular control here. You can set different schedules for soft declines (insufficient funds, temporary holds) vs hard declines (fraud, closed account), and you can split those further by card type or payment method.
The default schedule is reasonable:
| Attempt | Days after failure | Decline type |
|---|---|---|
| 1 | 3 | Any |
| 2 | 5 | Any |
| 3 | 7 | Soft only |
| 4 | 10 | Soft only |
| End | 14 | Expire or cancel |
You can push this to as many as 8 attempts over 30 days, which is more aggressive than most. Whether that's useful depends on your customer base.
Dunning campaigns are the email side. Each campaign is a set of templates tied to a retry schedule. Recurly ships a default campaign and lets you create alternatives for different customer segments (by plan, currency, or custom attribute).
Decline categories are Recurly's way of routing different failure reasons to different flows. This is genuinely useful. A "fraud suspected" decline shouldn't trigger the same retries as an "insufficient funds" decline, and Recurly handles that split natively.
What Recurly does well for dunning
Decline categorization. The split between soft and hard declines, and the ability to configure different retry logic for each, is more sophisticated than most billing platforms. Recurly groups failure reasons into categories and lets you set rules per category.
SMS support. Unlike Chargebee and most standalone tools, Recurly actually supports SMS in its dunning campaigns. You can send text reminders as part of the sequence. This is a real differentiator at the enterprise tier.
Multi-currency and localization. If you're running subscriptions across the US, EU, UK, and APAC, Recurly handles currency, tax, and localized templates without custom work.
3DS and SCA handling. Recurly was early on Strong Customer Authentication and has solid off-session auth flows built in. For European SaaS, this saves real engineering hours.
Account Updater integration. Recurly includes Visa Account Updater and Mastercard ABU sync by default, which silently refreshes 20 to 40% of expired cards before they ever enter a dunning sequence.
Where Recurly dunning stops
Template editor feels dated. The dunning email editor is functional but not modern. You can get branded, working templates, but iterating on copy feels slower than tools built around content workflows.
SMS is capped and costs extra. While SMS is supported, it's metered separately and the pricing can add up at volume. For high-volume B2C SaaS, the unit economics of Recurly SMS don't always compete with dedicated SMS-first tools.
Analytics are platform-wide, not recovery-focused. Recurly's dashboards cover the whole subscription lifecycle. If you want a focused view of "what did my dunning sequence recover this month," you're building it yourself or relying on exports.
No A/B testing on dunning emails. You can run multiple campaigns, but Recurly doesn't natively split traffic between two templates to compare recovery rates. For teams that want to iterate fast on copy, that's friction.
Lock-in. Recurly's dunning only works if you're running Recurly as your billing platform. If you want to test different dunning without migrating billing, you can't.
Realistic recovery rates with Recurly
Based on customer reports and published benchmarks, here's what to expect:
| Setup | Expected recovery rate |
|---|---|
| Recurly defaults, no tuning | 40 to 50% |
| Recurly with customized schedules and templates | 55 to 65% |
| Recurly plus SMS enabled | 65 to 75% |
| Recurly plus a dedicated dunning tool layered on top | 70 to 80% |
The gap between "Recurly with SMS" and "Recurly plus a focused tool" is narrower than with email-only platforms. Recurly's SMS support is the reason. If you're not using Recurly SMS, you're probably at 55 to 65% and you should either turn on SMS or look at a dedicated solution.
When Recurly's built-in dunning is enough
Stay with Recurly's built-in if:
- You're already running Recurly for billing and don't want another tool
- You've enabled SMS and your recovery rate is above 65%
- You need multi-currency, multi-region, and complex subscription logic
- Your team is comfortable inside Recurly's template editor
- Compliance and enterprise audit trails matter more than iteration speed
For mid-market and enterprise SaaS with clean Recurly setups, the built-in tool is legitimately competitive. It's one of the few cases where the "use what you already have" answer holds up.
When a dedicated dunning tool wins
Look at a dedicated solution if:
- You want to iterate on copy and timing without touching billing config
- You want A/B testing on dunning templates
- You want a recovery ROI dashboard separate from billing analytics
- You're moving toward Stripe and want to evaluate dunning tools before migrating billing
- Your recovery rate is stuck below 60% despite tuning
Honest take on Recurly for dunning
Recurly is the rare billing platform where the built-in dunning is good enough that most teams don't need to replace it. The decline categorization is solid, SMS is native, and the retry logic is flexible. That's a higher bar than Chargebee or Stripe Billing set.
Where Recurly falls short is iteration speed. If your job is to squeeze every point of recovery out of your failed payments, you want a tool where testing a new template is a three-minute change, not a fifteen-minute tour through campaign settings.
Where Rekko fits
Rekko is Stripe-native, so it doesn't compete directly with Recurly for billing. But if you're evaluating whether to migrate from Recurly to Stripe, or you're running a hybrid setup, Rekko gives you the fast-iteration dunning layer that Recurly's built-in tool doesn't.
Email plus SMS sequences live in Rekko, connected directly to Stripe webhooks. Setup takes about 5 minutes. Pre-authenticated payment update links are built in. SMS is included at every tier without separate metering. You get the recovery ROI dashboard that Recurly's platform-wide analytics don't focus on.
Start your 14-day free trial, no credit card required. Or see the Recurly alternative breakdown for the side-by-side.