Glossary
Audit log
An audit log is the record of actions, as opposed to the payment journal's record of payments: who logged in, who changed a routing flow, who corrected a payment's status by hand and why, who approved a payout, who issued or revoked a key, who changed a merchant's limits or fees, with the time, the user, the before and after values and the reason. It is what an auditor, an acquirer or a regulator reads to see that the controls the business describes are the controls it runs.
What makes it trustworthy
Entries are written by the system at the moment of the action, not typed by people afterwards; they cannot be edited or deleted by the users whose actions they record; they carry enough context to reconstruct the change; and they are kept as long as the records they explain. Access to the log is itself logged.
What it is used for
Investigating a wrong payout or a changed status; proving separation of duties; showing an acquirer that merchant limits were set and changed by authorised people; answering a regulator’s question about a decision months later; and noticing patterns, such as a user who edits statuses at unusual hours.
On the platform
Tranzify records every action in the back office and the merchant cabinet, including manual status changes with their reason, routing activations, payout approvals, key and user changes, with the user and the time, and keeps the records with the journal; the payment trace shows the manual actions that touched a payment in their place.
Updated: 2026-11-08