Enterprise treasury
The whole group's treasury, on one screen.
One platform collects, pays out, supervises and consolidates. Your subsidiaries keep their own accounts; you keep the whole picture.
Treasury management
Treasury where the money moves.
No export, no second system, no spreadsheet to reconcile at month end. The balances you read are the ones the payments just executed against.
- Corporate hierarchy: a holding company reads its subsidiaries' activity consolidated, one row per company with the group total beneath. Each entity keeps its own position, its own limits and its own settlement account.
- A platform that scales to handle your volume needs: every service scales horizontally and independently of the others. Growth is a capacity decision, not a migration.
- Balances, statements, settlements and movements are screens in the product — not a report you have to request.
Centralisation
One platform, all your rails, all your operators.
Mobile money, dedicated-IBAN transfers and instant payment behind one API and one webhook; your attached operators under your main account.
- Each attached operator has a sub-account per rail, under your main account.
- Commission splits in the same transaction as the collection; impossible to split more than was collected.
- Limits and approvals per business and per operator, funds kept during review.
- Mass payouts from the dashboard or the API, executed row by row, with a result per row.
- Grouped requests to pay on instant payment.
Real-time supervision
Every operation is evaluated before it moves.
Controls apply at the moment the money passes, on the platform that executes it — not on an export read the next day.
- Limits per business, per rail and per direction, changed without a deployment.
- Human approval with funds kept: a flagged operation waits, it is not silently refused.
- AML thresholds evaluated on every collection: transaction reports with daily aggregates.
- Rate limiting by source; kill switch per rail.
Full traceability
Every franc has a line, and that line never moves again.
The ledger and the audit logs are never rewritten: they are appended to, and each entry is bound to the previous one.
- Double-entry ledger, never modified; corrections are compensating entries.
- SHA-256 hash chain per account: each entry commits to the previous one.
- Insert-only audit logs; every decision by a team member is attributable there.
- A payout can never exceed the balance: the reservation is atomic.
Regulatory reporting
The registers the regulator expects, produced by the system that executes.
No export to a second supervision tool: registers, reconciliations and incidents come out of the same ledger as the payments.
Register of transaction and suspicious-activity reports, validated under four eyes.
Watermarked, audited exports.
Three-way reconciliation between the ledger, the operators and the settlements.
Bank statement import in CAMT format.
72 h incident register, immutable timestamps.
Customer funds safeguarded; coverage recomputed daily, critical alert on any shortfall.
Governance
Four eyes on everything that matters.
One person prepares, another approves. The maker-checker catalogue covers suspension, tariffs, reports, disputes, KYC, withdrawals, adjustments, settlements and thresholds.
- Thresholds and limits can only be loosened under four eyes.
- Step-up validation bound to the content of the operation for every money movement.
Supervision that lives where the money passes.
Let's talk about your operators, your rails and your volumes.