Integrations
Connect Chargebee revenue
Verify Chargebee payment and refund webhooks for one Premely site.
- Chargebee
What it is
The Chargebee connection uses a site-specific HTTPS endpoint protected by generated Basic Auth credentials.
Why use it
Use it when Chargebee is the source of truth for subscription payments and refunds that should appear in Premely revenue reporting.
Before you start
- You need owner or admin access in the Premely workspace.
- You need permission to create or edit webhooks in the Chargebee site.
- Choose Test or Live to match the Chargebee site you are connecting.
How to use it
- 1
Create the Premely endpoint
Open your site's Settings, choose Integrations, find Chargebee and choose Connect. Select the mode that matches your Chargebee site and choose Create Chargebee endpoint.
Create the site-scoped endpoint, then copy the generated Chargebee credentials before leaving the setup flow. Shown in Premely with disposable demo data; your values will differ.
- 2
Copy the generated URL and credentials
The confirmation shows Webhook URL, Username and Password. Copy all three and keep the dialog open until you have entered them in Chargebee. The password is shown only once. Use your own generated values, not the examples in this screenshot or your Chargebee login password.
Copy all three values into the matching Chargebee webhook. The password is not your Chargebee login and is shown only once. The displayed password is an invalid example. Captured from the real Premely interface using disposable local-review values. Example URLs and credentials cannot be used for a real connection.
- 3
Create the Chargebee webhook
In Chargebee, open Settings, Configure Chargebee, then API Keys and Webhooks. Select Webhooks and Add Webhook. Name it Premely revenue, paste the Premely Webhook URL, and enable Protect webhook URL with basic authentication. Enter the Username and Password generated by Premely, not your Chargebee login. Under Events to Send, select
payment_succeededandpayment_refunded, then choose Create.Chargebee: webhook setup and testing
Official Chargebee example, not a configured Premely connection. Replace the example URL, username and password with your Premely values. Change All Events to payment_succeeded and payment_refunded before creating the webhook.
- 4
Test delivery in Chargebee
On the saved webhook, open Test Webhook, select a supported payment event and choose Test URL. Review the response. Use a completed payment from the matching Chargebee test site, not an unrelated subscription event. A successful HTTP response confirms delivery, but you still need to check that Premely recorded the supported event.
- 5
Check the first verified event in Premely
Close the setup confirmation, then choose Manage on Chargebee in your site's Integrations. Check Last verified event. A timestamp confirms that a supported event arrived; Connected alone does not. If it still says Waiting for first event, check the webhook URL, generated Basic Auth credentials, event type and matching Test or Live environment.
Check for a timestamp beside Last verified event after Chargebee sends a supported payment event. This example is waiting for its first event, even though the endpoint is configured. Captured from the real Premely interface using disposable local-review values. Example URLs and credentials cannot be used for a real connection.
What to expect
Check the site and environment
Each connection sends revenue to one Premely site. A Test connection does not verify a Live connection. Keep the provider environment and the Premely mode the same throughout setup.
Currencies stay separate
Premely does not silently combine or convert different currencies. Provider revenue appears in Revenue and Revenue / Visitor only in its valid currency context.
Revenue and visitor attribution are separate
A verified payment can appear in revenue without being linked to a visitor. Premely shows the visitor link only when the payment carries matching Premely attribution data.
Duplicate deliveries do not duplicate revenue
If the provider retries the same event, Premely does not count it as another payment.
Credentials are shown once
Copy the Basic Auth password when it is created. Premely does not show the stored credential again.
Useful ways to apply this
Subscription payment reporting
Review supported Chargebee payments and refunds beside acquisition and conversion data for the selected site.