Recurly is a serious billing platform, and its native recovery machinery deserves to be described fairly before anyone talks about gaps. It retries failed invoices, it can send dunning emails on a campaign schedule, and it keeps a coherent record of the whole attempt history against the account. A business that configures it deliberately is not neglecting recovery. The gaps this piece is about are not defects in that machinery; they are the places where a general billing platform's job reasonably ends and a subscription business's problems keep going.
The first gap is authorship. Native dunning emails are written by the platform, in the platform's voice, inside the platform's templates. Merchants can adjust them, but in practice most run close to stock, and subscribers can tell: the message that arrives about a failed payment reads like it came from a system, because it did. Response rates follow the writing. A note that sounds like the business the subscriber actually chose — its name, its colour, its way of speaking — asks for the same card update and gets a different hearing, because it does not have to spend its first lines proving it is legitimate.
The second gap is what happens around the retry rather than inside it. A billing platform schedules attempts against an invoice. It is not watching for the signals that should change the plan: a card replaced through the updater between attempts, a subscriber who replied to a dunning email with a question, an account that cancelled twenty minutes ago and must not be charged or chased again. Each of those is a small event. Together they are the difference between a schedule and a process, and they are exactly where recovered subscribers are quietly lost by systems that are, on paper, configured correctly.
The third gap is the newest and the easiest to miss: alerts that exist but were never subscribed. Platforms add account-event notifications over time — a billing-information-updated event is the classic example — and an integration built against an older event list will never hear them. The merchant's settings look complete, the receiver looks complete, and the one event that announces a customer just fixed their card passes unheard, so the recovery case sits silent instead of closing. Completeness here is not a feature; it is a maintenance obligation, on both the subscribe list and the handling list, kept equal.
A fourth consideration sits underneath the other three: who watches the watchers. Billing platforms ship changes — new decline handling, revised campaign defaults, deprecated events — on their own release cycles, and a recovery setup tuned once and never revisited drifts out of alignment a little further every quarter. The merchant rarely notices, because nothing breaks loudly; recoveries simply sag by a point or two and the sag gets attributed to the customer base. A periodic review of the whole chain, settings against handling against counting, is unglamorous work. It is also where a noticeable share of the recoverable money is hiding in accounts that believe their setup is finished.
For the Recurly-specific version of all three, a walkthrough of recovery for Recurly merchants, gap by gap covers the native campaign's real strengths, the handover settings that matter, and the event coverage a complete setup should carry — including which native retries stay on by design and why.
None of this asks a Recurly merchant to leave Recurly. The billing platform keeps doing billing. The argument is narrower: the work around the invoice — the writing, the watching, the listening for the card-update that ends the case — is a specialism, and it shows in the numbers when somebody owns it full-time.
That ownership is the offer at Swipe Again: connect Recurly once, native retries checked live before every attempt so nothing is ever charged twice, cancellation stopping recovery immediately, and one flat monthly price with no share of what gets recovered.
Top comments (0)