Accounts
Issue current, sub- and virtual accounts to your own users under the Phoenix licence.
Infrastructure
The console is just one client of the Phoenix API. Issuing accounts, moving money, reading the ledger — anything it does, your code can do.
The stack
Every service writes to the same double-entry ledger, so there is no reconciliation step between them.
Issue current, sub- and virtual accounts to your own users under the Phoenix licence.
NIP inbound and outbound, bulk payouts and card acquiring, settled the same day.
A double-entry ledger you can query per account and per cycle, exportable for audit.
Signed, replayable events for every state change, delivered at least once.
Operations
These rails carry regulated money, so the operational commitments are published rather than promised.
99.98% across the trailing twelve months, reported per service.
Funds settle the same day, into the balance the console reads from.
An engineer on call, and an escalation path that ends at a person.
Compliance
Phoenix holds the licence, the settlement account and the audit trail. You get the rails without inheriting the paperwork.
Operating under a Central Bank of Nigeria licence.
Customer deposits are insured to the statutory limit.
Double-entry ledger, exportable for every reporting cycle.
Card data handled inside a Level 1 certified environment.
Tell us your volumes and we will map the rails to them.