Reference · built on requestConnectorPayments, billing & fraud

Chargebee

Customers, subscriptions, invoices, payments, and usage from Chargebee, with events delivered by webhook.

Request accessPricing ↗

About

Chargebee is a subscription billing platform. It records customers, subscriptions, invoices, credit notes, payments, and usage, and exposes them through a REST API served at your site's own host, https://{site}.chargebee.com/api/v2/. Every change of note is written as an event, and webhooks deliver those events to your endpoint.

Through Fibric an operator watches events such as payment_failed and dunning_updated, then proposes the next billing step for your approval. It leaves a receipt: what changed, why, and how to undo it.

This is a reference listing. It documents what Fibric would read from Chargebee and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Subscriptions and their status: future, in_trial, active, non_renewing, paused, cancelled, transferred
  • Invoices, credit notes, and payments as Chargebee generates and settles them
  • Events such as subscription_created, invoice_generated, payment_succeeded, payment_failed, and dunning_updated, delivered by webhook
  • Usage records for usage-based billing
  • Customers, with resource_version on each event to sequence changes that arrive out of order

Proposed actions

  • Target capability: propose pausing, resuming, or cancelling a subscription through the Subscriptions API
  • Target capability: propose a change to a subscription's term end
  • Target capability: propose reactivating a cancelled subscription

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Step in when dunning stalls

    dunning_updated events show where each invoice sits in Chargebee's retry sequence. The operator proposes the next customer contact and records who was reached and when.

    With Dunning Cadence

  • Retry a failed payment on a better day

    On payment_failed, the operator reads the invoice and the payment method on file, then proposes a retry time or a pause for your approval.

    With Payment Retry

  • Flag renewals with rising usage

    Usage records and subscription terms are read together. Accounts near a plan ceiling get a drafted renewal note for a person to send.

    With Usage Upsell

  • Watch for quiet churn

    Subscriptions moving to non_renewing or cancelled are grouped by plan and reason so a person can act before the term ends.

    With Churn Watch

Requirements

  • A Chargebee site and a Full-Access or Read-Only API key created by an admin
  • Webhooks configured in Chargebee to POST events to your endpoint, with basic authentication on the endpoint
  • A test site for validation before the live site, since the keys are separate
Authentication
An API key from the Chargebee admin console, sent as the HTTP Basic username with an empty password; keys differ between test and live sites.

Limits

  • List endpoints return 10 records by default and at most 100 per page, with next_offset paging
  • Webhook calls that fail are retried with increasing delays for up to 2 days, then dropped
  • Events can arrive out of order; the connector relies on resource_version to sequence them
  • A 429 response signals throttling; the reference publishes no request thresholds

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Chargebee ↗

Questions and answers

Does Chargebee send webhooks?
Yes. Configure webhooks in Chargebee and events trigger HTTP POST calls with JSON bodies. Failed calls are retried with increasing delays for up to 2 days. Chargebee suggests tracking event IDs to detect duplicates and using resource_version to order them.
Which API key type should the connector use?
The least permissive that fits. Chargebee offers Full-Access, Read-Only, and Publishable keys. Read-only sensing needs a Read-Only key. Proposed writes need a Full-Access key, which you approve and rotate on your own schedule.
Is there a cap on subscriptions per customer?
Yes. The Subscriptions reference states a maximum of 900 subscriptions per customer.
Ask about Chargebee

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with Chargebee through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy