Chargebee
Chargebee subscription state, MRR, and plan details appear on the matching Strkr account. CS teams catch downgrades early; RevOps builds expansion workflows on the signal.
Everything Chargebee does inside Strkr.
- Subscription status on the account
- MRR + plan details surfaced
- Payment-failed alerts into Flows
- Expansion and churn triggers
Native code, not a shim.
OAuth where available
Chargebee will ship with a native OAuth flow when it lands. No pasted credentials for admins to rotate manually.
KMS-encrypted tokens
Access and refresh tokens are envelope-encrypted at rest using a dedicated customer-managed KMS key. Decryption only happens in Lambda memory during an active API call; plaintext tokens never land in a log.
Shared by the workspace
A workspace admin connects Chargebee once; every teammate uses the shared connection without re-authenticating.
Disconnect at any time
Admins or users can disconnect Chargebee from inside Strkr. Stored tokens are deleted and the provider's revocation endpoint is called within 24 hours.
Chargebee is on the roadmap.
We ship integrations as first-class native code, which takes a little longer than a Zapier shim. If Chargebee is a dealbreaker for your evaluation, reply to the welcome email after you start a trial and we'll flag it to the roadmap.