Complex plans, add-ons, and proration all map cleanly to CashSDK entitlements. Chargebee's tax and invoicing integrations feed net and gross revenue into your analytics.
Chargebee
Connect Chargebee so subscription billing, dunning, and revenue operations map to CashSDK entitlements and one unified ledger.
Chargebee handles subscription billing, dunning, and revenue operations at scale, with deep quoting, proration, and tax integrations for teams with complex pricing. Connect it to CashSDK and RevOps keeps its billing engine while your app reads one clean entitlement model, and the revenue reconciles into a single ledger.
How it works#
1
Connect your Chargebee site
Add a Chargebee API key so CashSDK can read plans, subscriptions, and their status.
2
Map plans to entitlements
Each Chargebee plan (or item price) maps to a CashSDK product and the entitlement it unlocks.
3
Reconcile with webhooks
Subscription changes, dunning outcomes, and invoices are merged into your unified revenue ledger.
Connect Chargebee#
1
Create an API key
In Chargebee, go to Settings → Configure Chargebee → API Keys and create a read-only (or read-write, if you push changes) key. Copy it.
2
Add it to CashSDK
Open Settings → Billing → Chargebee and paste the key along with your Chargebee site name. It is stored encrypted at rest. Use a test site while you build.
3
Register the webhook
Copy the webhook URL from Settings → Billing → Chargebee and add it in Chargebee under Settings → Configure Chargebee → Webhooks. Enable the subscription and invoice events, and set the Basic-auth credentials so CashSDK can verify each request.
Map your catalog#
For each Chargebee plan, create a matching product in CashSDK and attach the entitlement it unlocks. Add-ons and tiers resolve to the same entitlement your app already checks.
Test and go live#
1
Test on a test site
Connect a Chargebee test site key and create a test subscription. Confirm the entitlement is granted and it appears under Events.
2
Switch to production
Swap in your live Chargebee site key and webhook settings. The CashSDK key does not change. It already serves both environments.