Pillar 05 · Partner offering via KoraStratum
A bank-grade stack for Tier-2 / 3 banks ready to leave BankOne.
Kora CBA + Kora Digital Banking + Kora IDV + Kora Compliance, delivered as one bundle through Orokii. Cloud-native. NIBSS, Interswitch, and BVN in production. BankOne migration mirror to de-risk the cutover. Reference deployment at FMFB.
Where the market is
Global cores under-serve African banks. African cores under-serve cloud-native expectations.
Established
BankOne and Finacle dominate Nigerian banking. Fiserv DNA, Jack Henry, FIS, Mambu, Thought Machine sell into larger banks worldwide. Most need heavy customization to fit African rails.
Underserved
Tier-2 / 3 Nigerian banks and MFBs that want cloud-native economics, NIBSS / Interswitch / BVN built in, eFASS regulatory mapping, and Islamic banking — without the global-vendor procurement cycle.
Where we sit
A single-vendor stack for Tier-2 / 3 banks in Nigeria and West Africa. BankOne migration mirror to de-risk the cutover. Bundled identity and compliance instead of four separate vendors.
What's included
Core, channels, identity, and compliance — one stack.
Kora CBA — core banking
Multi-tenant, microservices core banking in Go. General ledger, customer management, account lifecycle, transaction posting, loans, cards, treasury, trade finance, wealth, USSD, agent banking, bill-pay. 33+ services in production at FMFB.
Production · 3.5/5 maturity
Kora Digital Banking (web + mobile)
Customer-facing web (React Native Web + Express backend) and Flutter mobile app. Auth, transfers (NIBSS, Interswitch, NIP), bills, loans, savings, KYC via Kora IDV. App Store and Play submission-ready.
Production at FMFB · web 3/5, mobile 3.5/5
Kora IDV onboarding
Document OCR, MRZ, NFC chip read across 127 countries. BVN verification. Active + passive liveness. Identity is bundled, not a separate vendor selection.
Production
Kora Compliance built-in
Sanctions, PEP, adverse media screening with strong African PEP depth. Transaction monitoring. Case management. CBN-aware reporting.
Production · service-to-service auth hardening in progress
BankOne migration mirror
A transaction-mirror layer that runs Kora CBA in parallel with an existing BankOne deployment. Cutover happens once parity is proven. Reduces migration risk relative to a flag-day replacement.
Production at FMFB
Local rail and regulator integration
NIBSS, Interswitch, NIP, BVN, eFASS regulatory mapping, CBN compliance routes. Nigerian Islamic banking module in beta.
Production for core rails, beta for Islamic
Full product documentation lives at korastratum.com. Orokii handles the integration and migration relationship.
Who we work with
Three buyer shapes. All Nigerian or West African. All licensed.
Nigerian Tier-2 / 3 commercial banks
Currently on BankOne or Finacle, looking to migrate to a cloud-native core that is materially cheaper to operate and has African regulatory hooks built in. The migration mirror is the de-risking lever.
Microfinance banks
MFBs needing a unified stack — core, digital banking, compliance, identity — without integrating four vendors. FMFB is the reference deployment.
Neobank operators in West Africa
Greenfield neobanks in Nigeria, Ghana, or Kenya. Kora CBA + Digital Banking is a single-vendor full stack with the African rails the global cores skip.
How we work together
You operate the bank. We deliver and migrate the stack.
You bring
- Your banking license and regulatory standing
- Your existing customer base and operational footprint
- Your decision on migration strategy (greenfield vs BankOne mirror vs phased)
- Hosting: self-host on your cloud or accept KoraStratum-hosted
- Local NIBSS / Interswitch / BVN credentials and bank routing
We bring
- The Kora CBA + Digital Banking + IDV + Compliance stack via KoraStratum
- Migration delivery — BankOne mirror setup, parity validation, cutover playbook
- Six years of MTO operational experience translated into the operational shape
- Orokii as the single delivery partner for the full bundle
- Reference deployment at FMFB for proof and runbook patterns
Commercial model
Migration + license + operations. Long-cycle, high-value engagement.
Delivery / migration
$500k – $2M
one-time, depending on bank size and migration shape
BankOne mirror setup, parity validation, customer data migration, channel cutover, regulator reporting validation, runbook handoff.
Product license
Per-bank
annual · paid to KoraStratum
Sized to the bank's account count, transaction volume, and module mix. Materially below incumbent global-core pricing.
Ongoing operations
$10k – $40k
per month · DevOps support
Patch delivery, incident response, on-call coverage, observability tooling, quarterly review.
Realistic plan: 1–2 deals per year, high revenue per deal. This is a long-cycle sale (6–18 months) and we are honest about that.
Frequently asked
What partners ask before signing.
Is this realistic for a US community bank?
No. The stack does not yet have FedNow, NACHA file generation in the CBA itself, FDIC reporting, or US BSA/AML modules. We do not pitch it to US community banks or credit unions; we tell those buyers up front that we are the wrong vendor.
How long does a real migration take?
Realistic: 6–12 months for a Tier-2 / 3 Nigerian bank using the BankOne mirror approach. Greenfield neobanks in West Africa expect 6–9 months for the first market. Both timelines assume the customer-side resourcing is real.
What about the integration story between CBA, Digital Banking, IDV, and Compliance?
The four products talk to each other today but unevenly. Web frontends call CBA via api.korastratum.com; mobile is mid-cutover from a legacy Express middleware to CBA-direct; CEngine integration is hardening service-to-service auth. We are candid that integration plumbing is the live engineering work — not vapor, not complete.
Is Orokii or KoraStratum the licensed party?
Neither. The bank — the customer — is the licensed party in every jurisdiction. KoraStratum licenses the software; Orokii delivers the integration. The bank operates under its own license at all times.
Can we start with just Kora IDV or Kora Compliance and add CBA later?
Yes. The compliance + identity pillar (Pillar 4) is the standalone path. CBA + Digital Banking is the bundled path for banks doing a full core migration. Many customers start with IDV alone and expand later; that is a sensible path.
How do procurement and licensing work?
KoraStratum licenses the products directly to the bank — Orokii is the delivery partner under a cross-sell agreement. One commercial relationship per side, two contracts in total. Discussed in the scoping call.
Ready to evaluate?
A 60-minute scoping call covers your current core, migration appetite, regulatory standing, and realistic timeline. We will tell you whether the fit is real before either side commits engineering time.