Multi-tenant isolation
Institutions never share a customer file. Super-admins can still run group reports without mixing another institution's books.
Platform
OrbitMFI is one multi-tenant core for hire purchase, microfinance, savings and loans, cooperatives, and susu schemes. Isolation, Ghana payment rails, AI decisioning, and Bank of Ghana packs share the same ledger.
Multi-tenant architecture, branch isolation, and Ghana-ready controls.
Stack
Every staff click, client-portal payment, USSD collection, and API post lands on the same tenant-scoped ledger.
01
Staff portal, hire-purchase specialist desks, the white-label client portal, USSD, and a tenant-scoped REST API all post to the same ledger.
02
Origination, core banking, collections AI, hire purchase, savings/susu, payroll, and Bank of Ghana packs share one client file so nobody is duplicated.
03
Postgres with row-level security. Every table is tenant-scoped. Branch RBAC further limits what officers, tellers, and collectors can see.
04
Paystack and mobile money receipts, SMS/USSD reminders, Ghana Card KYC, credit-bureau files, and GPS watchlists post back as ledger events.
05
Dual-control disbursements, attributable audit trails, encrypted backups, and geo-redundant failover with a 99.99% uptime target.
Explore
Each item in the Platform menu loads its own page — architecture, security, Ghana controls, AI, integrations, APIs, and implementation.
Channels, application services, tenant-scoped Postgres, and geo-redundant failover.
Open ArchitectureRow-level security, branch RBAC, encryption, and attributable audit trails.
Open Security & isolationMPR packs, Ghana Card KYC, PAYE, SSNIT, and credit-bureau files from posted books.
Open Ghana & BoGCredit scores, collections ranking, fraud signals, and in-product coaching.
Open AI & decisioningPaystack, mobile money, SMS, GPS watchlists, and webhook receipts back to the ledger.
Open IntegrationsA two-to-four week go-live with migration, training, UAT, and on-call cutover.
Open ImplementationControls
Tenant isolation, dual control, and examiner-ready extracts are how the platform is built — not a later hardening project.
Institutions never share a customer file. Super-admins can still run group reports without mixing another institution's books.
Loans, hire-purchase instalments, susu receipts, and payroll journals post immediately. Month-end is a close, not a reconstruction.
Multiple availability zones, automated failover, and edge caching so branch and field staff stay productive on 3G.
Disbursements and collections carry idempotency keys so retries from MoMo or Paystack never double-post.
Teller limits, vault dual-control, and officer assignment keep cash on the same book examiners sample.
Clients see your name, colours, and logo. The operating core underneath stays OrbitMFI.
APIs
Originate a loan, post a MoMo receipt, or register a webhook without a second database. Keys are tenant-scoped. Disbursements are idempotent.
Every Platform dropdown item is a real page. Nothing here sends you to login.
Watch
Origination, collections, the client portal, and month-end — the same walkthrough your implementation lead uses.
Step 1
Capture identity, photos, and next-of-kin once. Reuse the file across loans, savings, and hire purchase.
Step 2
Price reducing-balance or flat-rate products, lock a schedule, and disburse with dual control.
Step 3
SMS, USSD, MoMo, and field queues post to the same instalment so PAR is honest.
Step 4
The client portal shows the live savings balance, loan due, and HP statement — then takes payment.
Step 5
Provisions, MPR packs, payroll, and the GL share one book examiners can sample.
Architecture, isolation, modules, and go-live timing.
Start a 14-day sandbox or talk to an architect about hire purchase, microfinance, and multi-branch cores.