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.
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_type | When Chargebee sends it |
|---|---|
| subscription_created | A new subscription is created |
| subscription_activated | A subscription moves from trial to active |
| subscription_renewed | A subscription renews from its current term |
| subscription_renewal_reminder | 3 days before each subscription renews |
| subscription_changed | A subscription's recurring items change |
| subscription_cancellation_scheduled | A subscription is set to cancel at the end of its term |
| subscription_cancelled | A subscription is cancelled |
| subscription_reactivated | A cancelled subscription becomes active or in trial again |
| customer_created | A customer is created |
| customer_changed | A customer's details or payment method role change |
| invoice_generated | An invoice is created (except one created as pending) |
| invoice_updated | A finalized invoice changes, for example voided or paid |
| payment_succeeded | A payment is collected |
| payment_failed | A payment collection fails |
| payment_refunded | A 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.
| Card | Number |
|---|---|
| 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
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
Point Chargebee at your URL
Paste the endpoint URL into Chargebee: Settings → Configure Chargebee → API Keys and Webhooks → Webhooks.
- 3
Inspect what arrives
Each delivery appears live in the dashboard with method, headers, body, query parameters, and source IP.
- 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 header | authorization |
|---|---|
| Algorithm | Basic auth |
| Verification in webhooks.cc | Capture 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
Create a free webhooks.cc endpoint and add its URL as a webhook on your Chargebee test site (Settings, Configure Chargebee, API Keys and Webhooks, Webhooks tab). Click Test Webhook on the webhook's card and pick an event, or make a test purchase with a Test Gateway card, and the delivery appears on the endpoint with its headers and body. To reach code on your machine, run whk tunnel <port> --endpoint <slug> with that endpoint's slug, and every delivery is forwarded to localhost as well as kept on the endpoint.
No. Chargebee does not sign webhook payloads. It recommends protecting the webhook URL with HTTP Basic authentication (turn on Protect webhook URL with basic authentication and set a username and password) and HTTPS, and confirming an event by fetching it again with the Retrieve an Event API call. Chargebee also publishes the IP addresses it sends webhooks from, per region, in its webhooks API docs.
Anything other than a 2xx response, or a timeout, counts as a failure. Chargebee then retries up to 7 times: 2 minutes after the failure, then 6 minutes, 30 minutes, 1 hour, 5 hours, 1 day and 2 days after each previous attempt, about 3 days and 7 hours in all. You can also resend an event by hand from Logs, Events in the Chargebee app.
Retries mean the same event can arrive more than once, and Chargebee says webhooks can arrive out of order. Store the event id you have processed (for at least 3 days and 7 hours, the retry window) and skip repeats, and compare the resource_version of the resource in the payload with the one you stored, processing the event only when it is newer.
Up to five. Chargebee calls them one after another for every event. Each Chargebee account has a test site and a live site, so set up the webhook you test with on the test site, where the Test Gateway cards work.
Create a free endpoint on webhooks.cc (sign in with GitHub, Google, or email, or use a guest endpoint without an account), then configure it as your webhook URL: Settings → Configure Chargebee → API Keys and Webhooks → Webhooks. Every delivery shows up live in the dashboard with full headers, body, and query parameters. To hit a local server, run whk tunnel <port> and the CLI forwards each webhook to localhost.
Yes. Capture one real delivery from Chargebee, then replay it to any URL from the dashboard, or run whk tunnel <port> to forward live deliveries to localhost. webhooks.cc has no built-in Chargebee sample templates, but the Send button posts any payload and headers you paste in.
Chargebee can authenticate deliveries with the authorization header (Basic auth). 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. Capture a real delivery on webhooks.cc to inspect the exact header value, then implement the check in your handler.
Yes. A free account gets you persistent endpoints, 50 requests per day, 7-day retention, and full CLI, SDK, and MCP access, with no credit card. You can also try a guest endpoint without an account: up to 25 requests for 12 hours.
More providers
Your Chargebee webhook URL is seconds away
Sign up free, create an endpoint, and point Chargebee at it.
No credit card · or try without an account