Skip to content

Chargebee webhooks: events, test cards and local testing

Chargebee sends webhooks for subscription, customer, invoice, payment, order, quote, and credit note events. Capture them on a free webhooks.cc endpoint to see exactly what Chargebee sends, then replay deliveries or forward them to your local handler.

Start free:
or sign up with email

No credit card · 50 requests/day free · or get a guest URL without an account

Prefer a walkthrough? Read the local webhook testing guide.

Common Chargebee webhook events

Every Chargebee webhook is an event object with id, occurred_at, source, api_version, event_type, and a content object holding the resources it is about (the subscription, customer, invoice or transaction). These are the events most billing integrations subscribe to.

event_typeWhen Chargebee sends it
subscription_createdA new subscription is created
subscription_activatedA subscription moves from trial to active
subscription_renewedA subscription renews from its current term
subscription_renewal_reminder3 days before each subscription renews
subscription_changedA subscription's recurring items change
subscription_cancellation_scheduledA subscription is set to cancel at the end of its term
subscription_cancelledA subscription is cancelled
subscription_reactivatedA cancelled subscription becomes active or in trial again
customer_createdA customer is created
customer_changedA customer's details or payment method role change
invoice_generatedAn invoice is created (except one created as pending)
invoice_updatedA finalized invoice changes, for example voided or paid
payment_succeededA payment is collected
payment_failedA payment collection fails
payment_refundedA payment is refunded

Source: Chargebee event types.

Chargebee Test Gateway cards

The Chargebee Test Gateway is available on your test site only. Use any valid future expiry date and any 3 or 4 digit CVV.

CardNumber
Visa (succeeds, 3DS not enrolled)4111 1111 1111 1111
Mastercard (succeeds)5555 5555 5555 4444
American Express (succeeds)3782 822463 10005
Discover (succeeds)6011 1111 1111 1117
Insufficient funds (charge declined)4005 5192 0000 0004
Verification failure (card not stored)4119 8627 6033 8320

Source: Chargebee Test Gateway docs.

How to test Chargebee webhooks

  1. 1

    Create a webhook endpoint

    Sign in free with GitHub, Google, or email to create a persistent endpoint, or grab an instant guest URL at webhooks.cc without an account.

  2. 2

    Point Chargebee at your URL

    Paste the endpoint URL into Chargebee: Settings → Configure Chargebee → API Keys and Webhooks → Webhooks.

  3. 3

    Inspect what arrives

    Each delivery appears live in the dashboard with method, headers, body, query parameters, and source IP.

  4. 4

    Forward to localhost or assert in CI

    Run whk tunnel <port> to forward webhooks to a local server, or use the TypeScript, Python or Go SDK to wait for and assert on deliveries in tests.

Chargebee webhook authentication

Auth headerauthorization
AlgorithmBasic auth
Verification in webhooks.ccCapture deliveries to inspect raw signature material

Chargebee does not sign payloads. Protect the URL with optional HTTP Basic auth, and confirm each event by fetching it again through the Events API.

New to signature verification? Read the webhook signature verification guide.

Everything in one place

  • Live dashboard: see deliveries the moment they arrive
  • Forward to localhost with whk tunnel
  • Replay any captured request to any URL
  • Mock responses with custom status, headers, and body
  • Forward to your servers, Slack or Discord
  • TypeScript, Python and Go SDKs for CI assertions
  • MCP server for AI coding agents

Chargebee webhook questions

More providers

Browse all 68 providers

Your Chargebee webhook URL is seconds away

Sign up free, create an endpoint, and point Chargebee at it.

or sign up with email

No credit card · or try without an account