Chargebee

Connect Chargebee with a read-only API key and a webhook URL that carries a secret.

RevGlance reads Chargebee's API v2: paid invoices, credit notes and subscriptions. Sites on Product Catalog 2.0 and on the older catalog both work.

Connect

In Chargebee, open Settings › Configure Chargebee › API Keys and add a read-only key for all of your site's data.
Copy the key (it starts with live_) and note your site name: acme for acme.chargebee.com.
Fill in the site and the key, then choose Connect Chargebee.

Field	Looks like
Site	`acme (from acme.chargebee.com)`
API keyStored encrypted	`live_…`

Chargebee does not sign its webhooks, so the secret travels with the URL.

In RevGlance, open Settings › Sources, open the Chargebee source's menu and choose Webhook. Save a long random secret under Signing secret.
Copy the webhook URL and add ?token= and your secret to the end.
In Chargebee, open Settings › Configure Chargebee › Webhooks and add a webhook with that address. Instead of ?token=, you can turn on basic authentication and use the secret as its password.

Paid invoices, before tax.
Refundable credit notes as refunds, less tax in the same share as the credit note.
Subscriptions, for MRR, plans, trials and cancellations, with the cancel reason code you set up in Chargebee.

Chargebee reports no gateway fees, so fees show as zero.

Paid invoices count before tax.
Refunds come from refundable credit notes, less tax in the same share as the credit note.
Chargebee reports no gateway fees, so fees show as zero.
MRR is the plan and add-on items, less coupons on the whole invoice that keep applying. One-off charges are left out.
Non-renewing subscriptions keep counting until their term ends. Paused ones count as churn. The cancel reason code you set up in Chargebee shows as the reason.
A payment that could not be collected counts as a failed charge. It moves no money.
A chargeback only counts when a refundable credit note records it.