Why auditability matters
An immutable record of system activity lets you:
- Preserve the integrity of data across all touchpoints.
- Support internal and external audits with a verifiable trail.
- Increase transparency and reduce the risk of undetected fraud.
- Meet the record-keeping requirements of regulatory frameworks.
What Midaz records
Audit data lives inside the Midaz platform, alongside the data it describes — there is no separate audit product to install.
- Audit events capture each recorded action: what happened, who performed it (the actor), the outcome, and when, together with a request identifier that ties the event back to the originating call.
- Transaction audit logs capture ledger activity. When audit logging is enabled, each operation in a transaction is recorded to the audit log for downstream retention and processing.
How audit records behave
- Append-only and immutable: audit records are only ever added, never updated or deleted, so the historical trail cannot be rewritten.
- Metadata, not secrets: records capture the metadata of an action, not its sensitive payload. Credentials, keys, and similar secrets are never written to an audit record.
Querying audit records
Audit events are read through the Midaz API, scoped to an Organization. You can filter by action, actor, outcome, and time range, and page through large result sets — enough to reconstruct the sequence of actions for a period, or to investigate a specific actor or outcome.
For more information about auditability in Midaz, contact us.