The audit log is a record of the requests made within your tenant. It is a valuable tool for monitoring activity, investigating discrepancies, and demonstrating compliance, capturing who did what and when across the platform. Audit entries are produced automatically as services handle requests.

You can review the audit log under “Audit Logs” in the console. Recorded activity includes, but is not limited to:

• Payment activity: transaction creation, authorization, capture, void, and refund events, including failures.
• Configuration changes: updates to business units, payment orchestrators, API keys, and webhooks.
• Communications: notifications sent on your behalf.

Each entry records the event type, the tenant and trace identifiers, the acting user or API key, and an event-specific payload. The same event catalog drives webhooks, so you can have these events delivered to your own systems in real time as well.

Viewing History

Query the audit history through the API. Results are returned newest-first with cursor-based pagination, and can be narrowed by trace id, user, and date range with GET /v1/audit-log/history. There is also an “Audit Log” section in the tenant console.

Supported query parameters include trace_id, user_name, start_date, end_date, and limit, along with the last_created_at and last_id cursors for paging through large result sets.