Tracer
Real-time transaction validation, answered in under 100 ms.
What it is
Tracer is Lerian's real-time control layer. It makes instant decisions (ALLOW / DENY / REVIEW) for any kind of transaction in under 100 ms, applying spend limits and business rules before the money moves.
A ledger records what happened; Tracer decides beforehand what is allowed to happen. It sits apart from the ledger: it does not read balances, it evaluates the context your system sends. Before recording a transaction in Midaz, your application calls Tracer and submits to the ledger only if the decision is ALLOW.
Capabilities
- Real-time validation answered in under 80 ms (p99).
- Rules engine built on CEL expressions: type-safe, with no code deploy.
- Dynamic spend limits per transaction, account, portfolio or segment, with automatic period reset.
- Product-agnostic: cards, transfers, Pix and crypto.
- Full audit trail with 7+ years of retention (SOX/GLBA).
- Configurable default decision (fail-open or fail-closed) when no rule matches.
When to use it
- Spend governance: evaluating transactions against internal or per-customer policies.
- Transaction validation: applying business rules before execution.
- Compliance: producing audit-ready records and guaranteeing traceability.
On the platform
Sits in front of Midaz: your application validates in Tracer and records the transaction in the ledger only if the decision is ALLOW. Tracer does not connect to Midaz and does not read balances — your application orchestrates the two.
Build with Tracer.
Talk to the people who build it — or go straight to the documentation.