Gateway Webhook Logs
Each log records the receipt, processing, and response details of a gateway webhook, helping you monitor activity, troubleshoot issues, and verify integrations.
Overview
Webhook Logs provide a detailed record of webhook requests sent by payment gateways to Chargebee, and a centralized view of:
- Incoming gateway webhook requests
- Request metadata, headers, and payloads
- Processing status, response codes, and retry attempts
- Related Chargebee resources, when available
You can use Webhook Logs to:
- Monitor recent webhook activity
- Debug failed or delayed webhooks
- Audit system activity
This visibility is available while a webhook is being retried and after processing is complete.
Webhook logs index page
The Webhook Logs page provides a list view of all webhook events. Each row represents a single webhook request and its current status.
To view all webhook logs for your Chargebee Billing site, go to Logs > Webhooks in the left navigation pane.
List view columns
Each webhook entry includes the following fields:
| Column | Description |
|---|---|
| Received At | Timestamp when Chargebee received the webhook. |
| Gateway | Payment gateway that sent the webhook (for example, Adyen or Stripe). |
| Transaction | Related Chargebee transaction, when available. |
| Status Code | HTTP status code returned by Chargebee in response to the webhook request (for example, 200). |
| URL | Chargebee webhook endpoint URL that received the gateway request. |
| Duration | Time taken by Chargebee to process and respond to the webhook request. |
Select any row to view detailed information about that webhook request.
Filtering and searching
To help you locate specific webhook events, you can filter and search the logs. Use the search bar to search webhook logs, or apply filters to narrow the results.
Filters
You can filter webhook logs using the following criteria:
- Gateway: Payment gateway that sent the webhook
- Status Code: HTTP status code returned by Chargebee in response to the webhook request
- URL: Chargebee webhook endpoint that received the gateway request
- Received At: Date range for webhook receipt time
- Transaction ID: Related transaction ID
- Customer ID: Related customer ID
- Invoice ID: Related invoice ID
Webhook log details page
The Webhook Logs Details page shows detailed information about a single webhook request received from a gateway.
Request summary
The summary section at the top of the page displays the key details of the webhook request:
- Status: HTTP status code returned by Chargebee
- Received At: Timestamp when Chargebee received the webhook
- Gateway: Payment gateway that sent the webhook
- URL: Chargebee webhook endpoint URL that received the gateway request
Headers
The Headers section displays the HTTP headers sent by the gateway with the webhook request.
Use this section to inspect metadata such as content type, user agent, gateway-specific identifiers, and tracing information. Sensitive header values such as authentication credentials are masked before storage and are not shown in clear text in webhook logs.
Webhook payload
The Webhook Payload section displays the full request body received from the gateway.
Use this section to inspect gateway event data such as:
- Event type or code
- Payment amount and currency
- Gateway references
- Merchant references
- Success or failure indicators
- Additional gateway-specific metadata
Sensitive values are masked before storage and are not shown in clear text in the logs.
Related resources
When available, the right sidebar displays links to Chargebee resources associated with the webhook, such as:
These links let you quickly navigate from a webhook to the related entities in Chargebee.
Why use webhook logs
Use webhook logs to:
- Confirm that Chargebee received a gateway webhook
- Inspect the headers and payload associated with the request
- Review the response returned by Chargebee
- Investigate failed, delayed, or duplicate notifications
- Trace the webhook to related Chargebee resources
Security and data handling
Sensitive values such as authentication credentials, secrets, and protected payment-related fields are masked before storage and are not shown in webhook logs. If you see *** in the logs, those fields were masked; the log view does not show the original sensitive values in clear text.
Frequently asked questions
1. What do webhook logs capture?
Webhook Logs capture incoming webhook requests from payment gateways, including headers, payload, status code returned by Chargebee, and related resource links when available.
2. Why are some values shown as ***?
Chargebee masks sensitive data before storing webhook logs. Values shown as *** indicate masked data and do not represent the original values sent by the gateway.
3. Can I use webhook logs to troubleshoot gateway notification issues?
Yes. Webhook Logs help you verify whether Chargebee received the webhook, inspect the payload and headers, and review the response status returned to the gateway.
4. Which resources can be linked from a webhook log?
Depending on the webhook content, related resources can include transactions, customers, and invoices.
5. How is this different from Chargebee webhooks to my application?
Gateway webhook logs record incoming HTTP webhook requests from payment gateways to Chargebee. That is separate from Events & webhooks, where Chargebee sends subscription and billing event notifications out to a URL you configure. To configure or troubleshoot those outbound notifications, use Webhook settings together with monitoring at your configured endpoint.
6. What are the limitations of gateway webhook logs?
What you see depends on your Billing site, the gateways you use, and how those gateways send webhooks to Chargebee. Retention, search coverage, and availability can vary by configuration and product. For account-specific limits (including how long logs are kept and which gateways are supported for your site), contact Chargebee Support.
Articles & FAQs
Was this article helpful?