Operators see problems before customers do
The work arrives as queues with the clock visible: KYC reviews pending, reconciliation breaks open, approvals waiting, breakers and providers watched on the engineering side. Error triage dedupes the alert stream — 142 occurrences of one signature become a single row to acknowledge and resolve — so noise never buries the real incident.
- [ 01 ]KYC review, reconciliation breaks, and approvals as counted queues
- [ 02 ]Breakers and provider health on the engineering side
- [ 03 ]Error triage that correlates the stream — resolve once, not 142 times
Discipline by default
Every privileged action — a freeze, a credit, a retire — opens a dialog that states its blast radius and demands a written reason, and the reason lands in an immutable audit log. Production actions make the operator type PROD before the button enables. Email and phone stay masked until revealed on purpose, and money metrics sit behind a financial role.
- [ 01 ]Reason-required dialogs on every privileged action
- [ 02 ]Immutable audit log — who did what, and why, in writing
- [ 03 ]Masked PII with reveal-on-purpose; money metrics gated by role
- [ 04 ]Credits above the threshold wait for a second operator's approval
From a queue to a customer in one click
The users list is the entry point; User 360 is the destination: balance, lifetime flow, cards, devices, KYC tier, and 184 transactions for one customer on a single screen. Every money row drills down — a €120.00 transfer opens to show both ledger legs posted, double-entry and balanced, with sender and receiver one click away.
The team is managed in the same place
Operators, invites, and roles live in the console itself — superadmin, ops, compliance, engineer, support, auditor — with each operator's recent actions on their record. Role changes route through a reason dialog, and nobody can change their own role or deactivate themselves; a second superadmin must.