PHOENIX MFB

Infrastructure

The rails under the account.

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

Four services, one ledger.

Every service writes to the same double-entry ledger, so there is no reconciliation step between them.

Accounts

Issue current, sub- and virtual accounts to your own users under the Phoenix licence.

Payments

NIP inbound and outbound, bulk payouts and card acquiring, settled the same day.

Ledger

A double-entry ledger you can query per account and per cycle, exportable for audit.

Webhooks

Signed, replayable events for every state change, delivered at least once.

Operations

Run like a bank, not a side project.

These rails carry regulated money, so the operational commitments are published rather than promised.

Published uptime

99.98% across the trailing twelve months, reported per service.

T+0 settlement

Funds settle the same day, into the balance the console reads from.

Named support

An engineer on call, and an escalation path that ends at a person.

API uptime, trailing 12 months
99.98%
Settled in the last 24 hours
₦412M
Standard settlement cycle
T+0
Median time to live account
3 days

Compliance

Regulated first, fast second.

Phoenix holds the licence, the settlement account and the audit trail. You get the rails without inheriting the paperwork.

CBN licensed

Operating under a Central Bank of Nigeria licence.

NDIC insured

Customer deposits are insured to the statutory limit.

Audited ledger

Double-entry ledger, exportable for every reporting cycle.

PCI DSS L1

Card data handled inside a Level 1 certified environment.

Ready to move money faster?

Tell us your volumes and we will map the rails to them.