Identity
Who can act
Customers, businesses, operators, signers, roles, and approval rights.
The operating layer behind Mozaca products.
A clearer platform view for buyers evaluating how Fedha, Hazina, Zent, and custom product surfaces become real financial operations: identity, ledger state, partner rails, compliance workflows, APIs, digital-asset operations, and deployment.
Buyer platform map
One model for every product surface
Ledger
What changed
Balances, events, receipts, reconciliations, and exportable state.
Rails
Where value moves
Banking partners, payment routes, mobile money, APIs, and asset rails.
Controls
Why it is trusted
Policy, compliance state, counterparty checks, evidence, and review logs.
01
Product surface
02
Partner rails
03
Control model
04
Evidence pack
Eight engines that compose into every product surface.
Mozaca markets capabilities, not features. Each engine is a reusable piece of financial infrastructure that products consume — and that partners can compose independently when they need to build their own.
01Engine
Identity & Access Engine
Customers, businesses, operators, devices, roles, and approval authority.
KYC/KYB identity, organization membership, branch and unit scope, authentication, device binding, sessions, and service credentials establish who can act.
Identity, membership, roles, devices, sessions
02Engine
Ledger Engine
Event-sourced double-entry ledger with continuous reconciliation.
Every wallet movement, partner-rail event, and approval is written as an immutable event. Reconciliation runs continuously instead of at month-end, with exportable proofs for audit and accounting.
Events, balances, reconciliation, exports
03Engine
Wallet & Account Engine
Customer, business, merchant, agent, and asset accounts over one governed model.
Provisioning, aliases, holds, limits, account status, cards, statements, and customer-facing available balance stay connected to the authoritative ledger.
Accounts, holds, limits, cards, statements
04Engine
Payment Engine
Routing across mobile money, bank, card, and approved partner rails.
Route selection chooses the rail by destination, currency, asset, fee, and risk — with settlement state visible before submission and webhook-led updates after.
Routing, settlement, fees, webhooks
05Engine
Digital Asset Engine
Approved digital-asset movement aligned with regulated operators.
Approved digital-asset rails, provider policy, transaction monitoring, Travel Rule workflows where applicable, and counterparty controls — designed to be operated under approved partner and licensing paths.
Provider policy, monitoring, evidence
06Engine
Credit Engine
Underwriting, limits, and policy controls for embedded credit.
Partner-led credit and BNPL with policy-driven limits, repayment scheduling, exception handling, and evidence packs aligned with the same ledger and compliance layer.
Limits, repayments, exceptions, audit
07Engine
Policy & Approval Engine
Centralized authorization, limits, maker-checker, and device-bound decisions.
Roles, unit scope, transaction limits, approval matrices, dynamic OPA policy, signed mobile decisions, and versioned policy bundles decide who may act before value moves.
RBAC, OPA, approvals, signed decisions
08Engine
Compliance, Audit & Reconciliation Engine
KYC/KYB, AML, monitoring, immutable evidence, and financial matching.
Screening, risk rules, case queues, SAR workflows, append-only audit, retention, legal holds, rail reconciliation, and regulator-ready exports operate as product flows.
AML, cases, audit, legal hold, reconciliation
The product reaches the user on the channel the market requires.
Channel availability is configured per client and launch scope. The matrix reflects implemented product paths and keeps partner-dependent coverage explicit.
| Channel | Fedha | Hazina | Zent |
|---|---|---|---|
| Customer web | Included | Included | Included |
| Native customer mobile | Included | Included | Included · KMP |
| Business / operator mobile | Included | Included | Configurable |
| USSD | Customer · agent · organization | Included | Included |
| Merchant / agent operations | Core product | Included | Corridor-dependent |
| Admin / compliance portals | Included | Included | Client · ops · compliance |
| Developer APIs / webhooks | Included | Included | Included · sandbox & SDKs |
Six layers that make the products operable.
The benchmark infrastructure companies do not sell isolated screens. They sell a control plane. Mozaca makes the same operating model visible: what runs underneath each product, how controls apply, and which evidence supports the workflow.
Identity and access
Customer, business, operator, signer, and role state mapped before money or assets move.
KYC/KYB, roles, approval limits
Ledger and balances
Fiat, treasury, and approved asset balances represented through auditable event state.
Receipts, reconciliation, exports
Rail orchestration
Mobile money, bank, payment provider, partner API, and approved asset routes selected by use case.
Routing, fees, settlement status
Asset operations and controls
Wallet, policy, provider, counterparty, and signer assumptions defined explicitly for each product path.
Provider model, role policy, evidence
Compliance workflows
Sanctions, transaction monitoring, jurisdiction, and counterparty review are treated as product flows.
Risk state, exceptions, review logs
APIs and operations
Developer APIs and operator consoles share the same underlying events and reporting model.
REST, webhooks, dashboards
Product paths map to the same control plane.
Fedha
White-label · Mobile money
Client-informed platform
Branded mobile money deployment
Operator channel rollout
Pilot market hardening
Hazina
White-label · Digital banking
Partner access
White-label banking platform
API plus console
Business treasury workspace
Zent
White-label · Stablecoins
Qualified access
Branded corridor platform
API and developer workspace
Compliance and operations console
The operating model, scoped before you commit.
Deployment model, buyer path, operating surfaces, and control posture — made explicit up front, so a production launch carries no surprises for the team that has to run it.
Deployment models
White-label, embedded API, hosted console, pilot
Buyer paths
Product walkthrough, sandbox review, partner scoping
Operating surfaces
Customer app, operator console, API, webhooks
Control posture
Identity, policy, ledger, evidence, compliance review
Interoperability
Speaks the rails others route around.
Most infrastructure vendors don’t publish ISO 20022 support, and few name national-switch interoperability. Mozaca is designed to interconnect — with the open standards and the native Kenyan rails a local operator expects on day one.
Mojaloop / FSPIOP
Compatibility with the open interoperability standard behind national switches (TIPS, Higala-style deployments).
ISO 20022
The messaging standard banks and switches are migrating to — designed in, not bolted on later.
Pesalink
Kenyan bank interconnect, migrating from ISO 8583 to ISO 20022 — a first-class rail, not an afterthought.
M-Pesa · Till / PayBill / B2C
Native mobile-money interconnect for collections and payouts across the dominant local rail.
Bank rails & RTGS
Partner-led bank settlement and real-time gross settlement where the corridor requires it.
Card networks
Card acceptance and issuing through approved network and processor partners.
Interoperability targets are designed into the platform; live support per rail and standard is confirmed through partner, switch, and regulator review for each market.
Product library
Launch from a template, not a blank page.
Each template is a configurable product defined on the product engine — wallets, savings, lending, treasury, remittance, and stablecoin payout — so a launch is configuration, not a rebuild.
Customer wallet
Balances, transfers, funding, statements.
Savings & goals
Interest accrual, goal buckets, lock-ins.
Group lending / chama
Contributions, group limits, payouts.
BNPL & credit
Origination, limits, repayments, scoring.
Merchant acquiring
Tills, paybills, links, settlement.
Agent network
Hierarchy, float, commissions, cash-in/out.
Business treasury
Multi-entity accounts, maker-checker, reconcile.
Remittance corridor
Collect, convert, payout, reconcile.
Stablecoin payout
On/off-ramp, corridors, hash-chained audit.
Templates are configured per client brand, market, and licence path. Availability of a given template depends on the product and market scope.
A staged path from review to operating scope.
Review
Review product screens, delivery models, supported surfaces, and trust assumptions.
Qualify
Share region, rails, volume, entity type, access path, and compliance context.
Sandbox review
Map API shape, webhook events, operator roles, and product-specific rail constraints.
Pilot scope
Define launch corridor, responsibilities, monitoring, reporting, and acceptance criteria.
Start with a product demo, then request the access path that matches your region, rails, volume, and control requirements.