Resources

Chargebee Dunning: The Complete Guide

If you bill on Chargebee, you already have dunning — the question is whether it's a system or a set of settings. Chargebee Billing ships a real native stack: configurable payment retries, a smart-retry option that reacts to gateway errors, dunning emails, and an ML retry engine (Revive) in its payments layer. What it doesn't run is the full recovery playbook: a decline-code-specific schedule as the organizing system, follow-up beyond email under your brand, cancel deflection included in the same product, and one recovery view across every platform you bill on. This guide explains exactly where Chargebee's native dunning stops, what a dedicated recovery layer adds, and how to decide whether the gap is worth paying for in your account.

What "Chargebee dunning" actually is, out of the box

Dunning is everything that happens after a subscription payment fails: retrying the charge, telling the customer, getting a working card on file, and deciding when to stop. In Chargebee, those jobs are split across three native pieces:

• Dunning for online payments — Chargebee's built-in dunning retries the failed payment on the intervals you configure and sends dunning emails alongside. You decide what happens at the end of the sequence — for example, whether the subscription is cancelled or left in its current status after the final attempt.
• Smart Retry — instead of fixed intervals, Chargebee's smart retry logic retries at dynamic intervals based on the type of gateway transaction error, and treats hard and soft declines differently.
• Revive — Chargebee's ML-powered retry product in its payments layer. Chargebee describes Revive as reading 200+ signals per failed payment to time each retry — aligning attempts to customer funding cycles and issuer behavior, and switching gateways where that helps.

Around those sit two prevention features worth naming: automatic card updates before expiry (how those network services actually work is its own subject — see our guide to card updater services), and backup payment methods — both reduce the number of failures that ever reach dunning. And one adjacent product matters for the full picture: cancel flows in Chargebee live in Chargebee Retention, a separate product priced per cancel-flow session ($250/month including 50 sessions, then $3 per session) — not in Billing's dunning stack.

Where native Chargebee dunning stops

None of the above is a criticism of the machinery. It's a description of its shape — and the shape has edges:

• The retry is the system. Chargebee's native logic is organized around retrying well — error-aware timing in Smart Retry, ML timing in Revive. But a failed payment is not always a timing problem. A replaced card, a closed account, a customer who never saw the email: those need a different play per decline cause, run as one coordinated sequence of retries and messages. Native dunning treats outreach as a notification attached to retries; a recovery system treats the retry and the outreach as one plan driven by the decline code.
• Email is the only native channel. Chargebee's dunning communication is email — configurable, decoupled from the retry count, and brandable, but email. There is no native SMS or voice step in the sequence for the customer who never opens it.
• Cancel deflection is a different product, priced per session. The subscriber who clicks cancel while a payment problem is unresolved meets Chargebee Retention — separate purchase, separate pricing model, session math. Dunning and deflection are two halves of the same retention problem; in Chargebee's catalog they are two products.
• It only sees Chargebee. If you also bill anywhere else — a Stripe product line, a Shopify storefront — Chargebee's recovery view ends at Chargebee's border, and so does its reporting.
• Attribution is retry-centric. Native reporting tells you what the retry engine recovered. It is not built to separate "recovered by anyone's efforts while a system was active" from "recovered because of a specific message or attempt" — the split you need to judge any recovery tool honestly, including this one.

What a dedicated recovery layer adds on Chargebee

Swipe Again connects to Chargebee and runs the recovery system as one sequence, coordinated with Chargebee's native retries so the same customer is never worked by two competing schedules:

• A decline-code playbook, not a retry setting. Each failure is routed by its code: up to six attempts over roughly sixteen days for the declines that clear with timing (payday-aware for insufficient funds), a dedicated day 1 / 3 / 7 cadence for expired cards, and no blind retries at all for hard declines like lost or stolen cards — those go straight to asking the customer for a new card.
• Outreach beyond email. Branded email you control per day of the sequence, SMS on day 1 and day 7, and voice calls reserved for high-value accounts — every message carrying a secure, hosted card-update page under your brand.
• Cancel deflection in the same product. Reason-matched save offers — discount, pause, downgrade — presented at the cancel moment and executed on the subscription automatically. No second product, no per-session pricing.
• Backfill on connect. Connecting pulls in your last 90 days of failed payments automatically, so recovery starts on the backlog already sitting in your account, not just tomorrow's failures.
• One dashboard across platforms. If Chargebee is one of several places you bill, every recovered dollar lands in the same view, attributed to the attempt or message that won it.

One decision has to be made explicitly before any of this runs: which system owns retries. Layering a second retry schedule over Chargebee's without coordination is how customers get double-charged attempts and contradictory emails. Our engine coordinates with the native schedule rather than stacking on it — the same rule we'd tell you to apply to any tool you evaluate here, including ours. The general discipline is in our dunning management guide.

What it costs, and what the pricing models do at scale

Chargebee's native dunning is bundled with your Billing plan; Revive sits in their payments offering; Retention is the per-session product priced above. Swipe Again is one flat price — $179/month, or $1,799/year — with dunning and cancel deflection in the same plan and no percentage of recovered revenue, ever. The full breakdown is on the pricing page. The model difference matters more than the entry number: per-session and percentage pricing both scale with your problem, while a flat fee stays where it started. Run any model at 3× your current failure volume before you sign — the math is worked through in our best dunning software comparison.

And the flat fee carries the guarantee: recover $179 in your first 30 days, guaranteed — or Swipe Again is free the next 30 days. Recovered revenue means every failed payment collected while Swipe Again is active, from any recovery source, as defined in Section 3 of our Terms. How we count: how Swipe Again counts recovered revenue

Frequently asked questions

Should I turn off Chargebee's native dunning?

You don't have to choose on day one. Swipe Again coordinates with Chargebee's native retries so schedules never collide; many merchants simplify to one schedule once they've seen the attribution. What you should never do is run two uncoordinated retry engines on the same failure.

Does Swipe Again replace Chargebee Billing?

No. Chargebee remains your billing system of record — subscriptions, invoices, and charges stay there. Swipe Again is the recovery layer that works the failures Chargebee surfaces: retries, outreach, card updates, and cancel deflection.

How is this different from Chargebee Revive?

Revive is a retry-timing engine: it decides when to re-attempt the card. Swipe Again runs the whole recovery system around the retry — the decline-code playbook, the email/SMS/voice outreach, the card-update flow, and cancel deflection — and reports total recovered versus directly recovered, separately. They answer different questions: "when should this charge be retried?" versus "what does it take to get this subscriber paying again?"

What about Chargebee Retention?

Retention is Chargebee's cancel-flow product, priced per session. If cancel flows are your only gap and you're committed to the Chargebee stack, it's the native option. Swipe Again includes cancel deflection in the same flat price as dunning — the comparison that matters is total cost of both halves, not either sticker alone.

The short version

Chargebee's native dunning is a capable retry stack. It is not a recovery system: the play doesn't reorganize around the decline code, outreach stops at email, cancel deflection is a separate per-session product, and the view ends at Chargebee's border. If your unrecovered gap is bigger than $179 a month, a dedicated layer closes it — and a 14-day trial on your own backlog will prove it one way or the other. For the full recovery playbook — the four levers, the sequence, and how to measure what worked — see our complete guide to recovering failed payments.

Related reading: Stripe Billing vs Chargebee