Chargebee integration

Chargebee dunning and failed payment recovery

Chargebee has built-in dunning settings for retries and reminder emails. Revnio adds decline-aware collection attempts, multi-channel outreach and recovery reporting on top, using your Chargebee site’s API key and webhooks.

What Chargebee does on its own

Chargebee’s dunning settings let you schedule retry attempts for failed invoices and send dunning emails between them. What is available depends on your Chargebee plan and gateway.

Common gaps teams run into:

  • Reminders are email-based; there is no WhatsApp (or, soon, SMS) escalation for customers who don’t read billing emails.
  • Every customer gets the same schedule, regardless of plan value or why the payment failed.
  • It is hard to see how much revenue dunning actually brought back, and through which message.

What Revnio adds

Revnio receives Chargebee events (failed and successful payments, invoices, subscriptions, card changes and card-expiry events) and opens a recovery case for every failed payment.

  • Collection attempts timed by decline reason and customer value, using Chargebee’s collect-payment API.
  • Branded recovery emails with a secure link to update the card or pay the outstanding invoice now.
  • WhatsApp (Pro plan) follow-ups when the email link isn’t clicked. SMS is coming soon.
  • Pre-dunning alerts when Chargebee reports a card is about to expire.
  • Recovered revenue, recovery rate and per-channel results in one dashboard.

How the connection works

You connect with your Chargebee site name and an API key. Revnio stores the key encrypted and imports your customers, subscriptions and invoices.

For real-time events, you add a webhook in Chargebee pointing at the URL Revnio gives you, with the HTTP Basic auth username and password shown in Revnio. Revnio rejects any webhook that doesn’t carry those credentials, so nobody else can post fake events to your account.

Set up Chargebee in Revnio

  1. In Chargebee, create an API key (Settings → Configure Chargebee → API keys).
  2. In Revnio, go to Settings → Integrations → Chargebee and enter your site name and the key.
  3. Copy the webhook URL and Basic auth credentials from Revnio into a new Chargebee webhook.
  4. Let the initial sync finish, review the recovery schedule and turn on automations.

Frequently asked questions

Should I keep Chargebee’s own dunning switched on?

Avoid running two retry schedules on the same invoice. A common setup is to let Revnio handle retries and customer messages and keep Chargebee’s end-of-dunning action (for example, cancelling the subscription) as your backstop.

Why does Revnio need Basic auth on the Chargebee webhook?

Chargebee webhooks are authenticated with HTTP Basic auth. Revnio generates a password per connection and refuses events without it, so only your Chargebee site can trigger recovery actions.

Which Chargebee events does Revnio use?

Payment failed and succeeded, invoice generated and updated, subscription created, changed and cancelled, customer and card updates, and card expiring or expired.

Can customers pay the failed invoice immediately?

Yes. The recovery page gives customers a “Pay now” option that collects the outstanding invoice, as well as a way to update their card.

Start recovering failed Chargebee payments

Connect Chargebee in a few minutes and let Revnio handle retries and follow-ups. 14-day free trial.

Start 14-day free trial See pricing

Related