Failed payment recovery for Chargebee
By Travis Steffen · Co-Founder, GTMReviewed by Calum EwingUpdated 3 min readSummarize with AI
Quick answer
Chargebee runs smart dunning — it retries a failed card on a configurable schedule and sends a sequence of dunning emails linking to a hosted payment page. But the comms are email-only, and when the dunning cycle ends the subscription just cancels. Dunning alone recovers ~20%; a human team gets 60–85%+. Revatto re-attempts the charge through Chargebee's API on AI-timed retries and runs email + SMS + human outreach on top, done for you. You pay 20% of the first recovered payment, $0 setup, $0 monthly, cancel anytime.
The gap Chargebee leaves open
What Chargebee recovers on its own
- Chargebee's smart dunning retries a failed payment on a configurable schedule — you set the number of attempts and the days between them.
- Automated dunning emails notify the customer of the failure and link them to a hosted page to update their card.
- At the end of the dunning cycle, Chargebee can cancel, pause, or move the subscription to a non-renewing state per your configured rules.
stops at
adds- Chargebee stops at: Chargebee's recovery comms are email-only — dunning emails, but no SMS and no phone outreach.Revatto adds: Email + SMS + a human recovery specialist, all sending under your brand.
- Chargebee stops at: Chargebee's retry schedule is a fixed cadence you set once — it doesn't adapt the timing to each decline.Revatto adds: AI-timed retries plus cross-client learning from millions of recovered payments.
- Chargebee stops at: When the dunning cycle ends, Chargebee makes no further attempts — the subscription cancels or pauses, with no win-back.Revatto adds: Recovery continues past Chargebee's last attempt, with human follow-up that actually reconnects the card.
- Chargebee stops at: Dunning emails alone leave most failed payments unrecovered.Revatto adds: Revatto re-attempts the charge through Chargebee's API on a recovery-optimized cadence and layers human outreach on the declines a retry can't clear.
How Revatto recovers failed Chargebee payments
- 1Detect the failure instantlyRevatto ingests Chargebee's payment_failed event the moment a charge fails — no polling, no delay.
- 2Diagnose the declineRevatto reads Chargebee's error code (e.g. insufficient_funds, do_not_honor, card_expired) to tell a soft retry-now from a hard needs-the-customer.
- 3Re-attempt intelligentlyWhere a retry can clear it, Revatto triggers an AI-timed re-attempt of the charge through Chargebee's API instead of waiting on the fixed dunning cadence.
- 4Reach the customerWhere a retry won't clear it, email + SMS + a human recovery specialist reach the cardholder under your brand to update the card.
- 5Stop on successWhen Chargebee reports the payment succeeded, Revatto ends the sequence automatically — no double-charge, no stray outreach.
How a Chargebee decline maps across stacks
A do-not-honor decline on Chargebee — ISO 05 (a generic issuer decline Chargebee surfaces as do_not_honor). Recovery looks the same across every stack Revatto runs on — here is how the same issuer decision is named on each.
ProcessorCodeWhat it’s called
ISO 8583
Code05
CalledDo Not Honor
Codedo_not_honor
CalledDo not honor
Code2000
CalledDo Not Honorgeneric issuer decline
Code5
CalledDo not honorresponseReasonCode 5
Code201
CalledDo not honor
Codedo_not_honor
CalledDo not honor
Codecall_issuer
CalledCall issuer
Code05
CalledDo not honorISO 8583 adapterCode 05 (refer to issuer)
CodeDO_NOT_HONOR
CalledDo not honor
Codedo_not_honor
CalledDo not honornormalized — no processor-specific code (free-text categorized)
Codedo_not_honor
CalledDo not honornormalized — matched by substring rule, no processor-specific code
See what Revatto would recover from Chargebee
Failed payments recovered automatically — no engineering, no manual chasing. We do the work; you keep the revenue.
Frequently asked questions
No — it works on top of it. Chargebee's smart dunning handles the scheduled retries and emails; Revatto adds the channels Chargebee doesn't (SMS and human outreach), re-attempts the charge on AI-timed retries through Chargebee's API, and continues recovery past Chargebee's final dunning attempt.
Yes. Chargebee exposes a full billing API, so Revatto can trigger a re-attempt of the charge on a recovery-optimized schedule, not just send a reminder email.
No. Chargebee's dunning notifications are email-only. SMS and phone follow-up are exactly what Revatto adds.
Chargebee makes no further attempts and cancels, pauses, or moves the subscription to a non-renewing state per your settings. Revatto keeps recovering past that point with human follow-up to reconnect the card.