Gateway Activity Logs

View and troubleshoot API communication between Chargebee and your payment gateways.

Gateway Activity Logs provide detailed visibility into API interactions between Chargebee and integrated payment gateways. You can use this feature to view, search, and troubleshoot gateway requests and responses directly from Chargebee Billing.

Overview

When Chargebee processes payments, refunds, or other gateway operations, it communicates with payment gateways through API calls. Gateway Activity Logs capture these interactions, including:

• Request headers and body
• Response headers and body
• Status codes and timing information
• Related transaction and customer context

This visibility helps you:

• Debug payment failures
• Understand gateway behavior
• Audit payment processing
• Troubleshoot integration issues

Gateway Activity index page

To view all gateway logs across your Chargebee Billing site, go to Logs > Gateway Activity in the left navigation pane.

List view columns

Select any row to view detailed information about that API call.

Filtering and searching

Use the search bar for full-text search across logs, or apply filters to narrow the results.

Filters

You can filter gateway activity logs using the following criteria:

• Operation Type: Profile, Payment Method, Payment, Refund, Authorize, Void, Capture
• Trace ID: Shared ID for all gateway API calls triggered by a single Chargebee request
• Status Code: HTTP response status
• Gateway: Payment gateway
• Source: Chargebee source used for the operation that triggered this gateway API call (see Sources in Gateway Activity Logs)
• Source Action: Chargebee API or job name
• HTTP Method: GET, POST, PUT, DELETE, PATCH
• URL: Gateway API endpoint
• Invocation Time: Date range (between, before, after)
• Payment Method: Card, Direct Debit, PayPal, Apple Pay, Google Pay, UPI, and similar methods
• Customer ID, Transaction ID, Invoice ID, Payment Intent ID, Payment Attempt ID, Payment Method ID, Gateway Account ID: Related resource IDs

Sources in Gateway Activity Logs

Source indicates which Chargebee source (such as API or Hosted Page) was used for the operation that triggered this gateway API call.

The labels below match the Source filter values on the Gateway Activity index page.

Gateway Activity details page

The Gateway Activity details page provides information about a single gateway API call.

Request information

The following fields are displayed at the top of the details page:

• URL: Complete gateway API endpoint URL
• Method: HTTP method used (GET, POST, PUT, DELETE)
• Status: HTTP response status code
• Invocation Time: Exact timestamp of the API call
• Duration: Time taken for the API call to complete (in milliseconds)
• Trace ID: Shared ID for all gateway API calls triggered by a single Chargebee request (for example, one payment or refund)
• Source: Chargebee source used for the operation that triggered this gateway API call (see Sources in Gateway Activity Logs)
• Source Action: Name of the Chargebee API or job that initiated this API call
• Operation: Type of operation (for example, Payment, Refund, or Capture)
• Gateway: Payment gateway name
• Payment Method: Payment method used (for example, Card or ACH)

Request and response data

The following sections display the complete request and response data exchanged with the gateway:

• Request Headers: All HTTP headers sent to the gateway. Sensitive headers such as authorization tokens are never stored.
• Request Body: The complete JSON request body sent to the gateway. Raw payment method information and sensitive secrets (such as card numbers, CVVs, or API keys) are masked before being stored and are never visible in the logs.
• Response Headers: HTTP headers returned by the gateway in the response.
• Response Body: The complete JSON response from the gateway, including transaction status, gateway-specific response codes, and error messages. Sensitive information is never stored—values shown as *** were stored that way.

Related resources

When available, the right sidebar displays links to related resources such as transactions, payment intents, and customers, along with their associated logs.

View logs from Transactions and Payment Intents

View Gateway Activity Logs directly from Transactions and Payment Intent details pages.

Transaction details page

In the Gateway section of any transaction, click View Request/Response Logs to see all gateway API calls made during that transaction.

Payment Intent details page

Under each Payment Attempt, click View Request/Response Logs to see gateway API calls made during that specific attempt.

Security and data handling

Chargebee never stores sensitive information in Gateway Activity Logs. Sensitive data such as credit card numbers, CVV codes, and authentication tokens are replaced with *** before being stored. If you see *** in the logs, that is exactly what was stored—the actual sensitive values are never persisted.

This supports compliance with PCI DSS and other security standards.

Summary

Gateway Activity Logs give engineering and support teams visibility into each gateway API call Chargebee makes. From the dedicated logs interface—and from payment attempts and transactions—you can inspect sanitized request and response bodies, headers, and per-call latency. Use Trace ID to follow multi-step gateway flows for a single Chargebee request, and use search and filters to isolate issues. Sensitive values are masked before storage. Logs are retained for 30 days.

Frequently Asked Questions (FAQs)

1. How long are gateway activity logs retained?

Gateway activity logs are retained for 30 days.

2. Which gateways are supported?

Gateway activity logs are available for all payment gateways integrated with Chargebee.

3. Why are some values showing as ***?

Chargebee masks sensitive data before storing logs. Values shown as *** indicate masked data and do not represent actual stored credentials or payment details.

4. What does the Trace ID help with?

A single Chargebee request (such as a payment or refund) can trigger multiple API calls to the gateway. All of those gateway calls share the same Trace ID. Use it to view the full set of gateway requests for that Chargebee operation.