Operational Consoles & Workflows
A set of internal web consoles supports the day-to-day operation of the platform. Access to each console is restricted by role, with segregation of duties enforced between teams.
Consoles
| Console | Purpose |
|---|---|
| Operations console | Real-time monitoring of transaction flow, partner health, corridor performance, and wallet balances. Used by the operations team to triage issues as they occur. |
| Compliance console | KYC review queues, transaction monitoring alerts, case management, SAR/STR workflow, and sanctions hit adjudication. |
| Risk console | User risk tier review, limit overrides (within policy), and behavioural alert management. |
| Customer support console | User profile lookup, transaction history review, secure communication, dispute initiation, and step-up verification tools. No PAN or sensitive authentication data is exposed. |
| Finance console | Settlement, reconciliation, fee configuration, partner invoicing, and regulatory reporting. |
| Admin console | System-level configuration, reference data (countries, currencies, corridors), and user administration for internal staff. Restricted to a small number of administrators with enhanced controls. |
Key Operational Workflows
- Onboarding a new user. KYC capture → automated verification → (if required) manual review in the Compliance console → account activation.
- Dispute handling. User raises dispute in-app → ticket created in the Customer Support console → evidence gathered → partner-specific dispute workflow executed (card network, banking partner, or remittance partner).
- New corridor launch. Corridor configured in the Admin console → partner integration tested in staging → compliance sign-off → progressive rollout with monitoring.
- Daily reconciliation. Automated jobs reconcile the Ledger service against partner statements; breaks are escalated to the Finance console for investigation.