Your institution
The bank, telco, SACCO, e-money issuer, or licensed fintech deploying Mozaca holds the regulatory license and owns the customer relationship. You are the regulated operator; the accounts are yours.
You hold the license. Mozaca is the technology.
The cleanest way to de-risk a regulated launch is to keep the license and the customer relationship with the operator, and let the software carry the controls and the evidence. Here is how that split works — and why a Kenya-first, CBK-aware posture matters.
A clean line between licence and technology.
Buyers de-risk faster when the responsibility split is explicit. Mozaca states it plainly.
The technology & the controls
Wallets, ledger, payment routing, and the compliance stack — KYC/KYB, sanctions screening, transaction monitoring, maker-checker, and audit evidence — delivered as software you operate under your brand.
Compliance by design
Because controls ship as configured product flows rather than bolt-ons, your team launches on rails that already assume regulator review — instead of building the control plane from scratch.
Built for the market it launches in.
Several pan-African and global entrants operate in Kenya without a local licence. A platform designed around the home market's regulator and rails starts from trust the others have to earn.
CBK-aware posture
The operating model is designed around Central Bank of Kenya expectations for the licence path a client operates under — not retrofitted to them.
Data residency & ODPC
Per-client isolation and data-residency options are designed with the Office of the Data Protection Commissioner regime in mind — a control local buyers ask for and offshore vendors struggle to offer.
Native interconnect
Pesalink, M-Pesa Till / PayBill, and bank rails are treated as first-class rails, not an afterthought — the interconnect a Kenyan operator expects on day one.
The licence stays local
The client holds the Kenyan licence and the customer relationship; Mozaca provides the software and evidence. Home-turf credibility, without importing someone else's regulatory perimeter.
Controls that ship as features, not fine print.
The compliance stack is part of the product surface — configured per client market and partner path, and visible to the teams who operate it.
KYC tiers
Identity verification with tiered limits, step-up, and re-verification enforced before movement is enabled.
KYB & beneficial owners
Entity onboarding captures directors, owners, operating purpose, and ongoing monitoring state.
Sanctions & PEP screening
Names and counterparties screened against sanctions and PEP lists at onboarding and on transaction.
Transaction monitoring
Rule- and risk-based monitoring with case queues, escalation, and disposition tracking.
Maker-checker & RBAC
Role-bound approvals, limits, and duties-segregation on every sensitive action, with approval history.
Travel Rule (where applicable)
Originator/beneficiary information handling on approved digital-asset corridors, per the client's jurisdiction.
Case management
Compliance and operations teams work KYC, sanctions, and monitoring cases from a shared console.
Audit chain & signed exports
Every meaningful state change is hash-chained and correlated, and packaged into audit-ready exports.
Regulated flows, product by product.
Each product is explicit about its licence path and the controls around it, without over-claiming approval that belongs to a client or partner.
Fedha · mobile money
Designed for the mobile-money / e-money licence path: the operator holds the licence, and Fedha provides wallets, agent and merchant operations, settlement, and the KYC / limits / monitoring / audit controls around them. Any approved digital-asset movement is gated by licensed-path review.
Hazina · digital banking & treasury
Partner-bank and payment-rail led. KYB, beneficial-owner capture, sanctions screening, maker-checker approvals, continuous reconciliation, and audit evidence are configured per client scope, with the licensed bank or partner holding the underlying accounts.
Zent · stablecoins
Institutional digital-asset workflows designed around approved custody, KYC/KYB, sanctions and transaction monitoring, Travel Rule where applicable, and licensed liquidity/settlement partners — with Mozaca providing the policy, ledger, settlement, and evidence layers.
Mozaca is a technology provider, not a bank and not the licensed entity. We do not hold customer funds or issue licences. Exact licences, regulated entities, partner banks, custodians, and corridor approvals are confirmed with the client during signed scoping and diligence. This page describes operating posture and is not legal advice.
Need the licensing model, control mapping, and per-market posture for vendor onboarding? Request the compliance and licensing pack.
Related → Trust & security · Ledger & reconciliation