Policy
before movement
Role, limit, counterparty, and rail checks are visible before a transfer is approved.
Building Financial InfrastructureFor The Next Generation Of Finance.
Bridging Web2 and Web3 across global markets — with the policy controls, evidence trails, and partner rails institutional teams need before money moves.
Rails
with partners
Banking, payment, mobile money, and approved digital-asset routes stay explicit.
Proof
for every event
Wallet state, ledger entries, webhooks, receipts, and exports are designed for review.
One core. Distinct products. Client-owned brands.
Mozaca is the factory behind the portfolio. We turn reusable financial infrastructure into configurable products, then adapt each product to a client's market without exposing another client's identity, data, or operating model.
- 01 · Shared engines
Build the financial primitives once.
Identity, ledger, wallets, payments, policy, compliance, audit, reconciliation, reporting, and developer infrastructure form the reusable Mozaca core.
- 02 · Mozaca products
Shape the core around a market problem.
Fedha packages mobile money and ecosystem operations. Hazina packages digital banking, lending, remittance, and treasury. Zent packages stablecoin-to-local-money digital finance.
- 03 · Market configuration
Select the country, rails, and rules.
Currencies, languages, KYC tiers, limits, payment providers, data residency, regulatory controls, and channel mix are configured for the launch market.
- 04 · Client deployment
Deliver it under the operator's brand.
Each client gets explicit branding, roles, integrations, policies, data boundaries, infrastructure, and operating evidence—without creating a new product fork.
A clearer path from product idea to trusted launch.
Mozaca becomes easier to evaluate when every buyer can see the same sequence: what is being built, which rails it touches, who can approve it, and what evidence proves it is ready.
01Product scope
Choose the surface
Start from the product your partner needs to understand: wallet, treasury, rail orchestration, or digital-asset operations.
02Partner context
Map the rails
Make banking partners, payment routes, mobile money, approved asset rails, and provider dependencies visible early.
03Policy model
Set the controls
Define roles, limits, approvals, counterparties, customer checks, and review thresholds before movement.
04Audit trail
Prove the launch
Show transaction state, ledger evidence, receipts, webhooks, reconciliations, and exports in one review path.
Live lifecycle
Watch the money move.
One transfer, every stage visible — from the wallet, through policy and compliance, across the rail you choose, into the ledger, and out as proof. This is the same path partners operate.
- 1InitiateWallet engine
- 2Policy & complianceCompliance engine
- 3RoutePayment engine
- 4LedgerLedger engine
- 5ProofLedger engine
Result
Run the transfer →
Ready to move KES 25,000 over M‑Pesa.
Find your fit
Start from what you’re building.
- What it is
- Your own mobile money app plus the operator tools behind it — one governed wallet and transaction core.
- Who it's for
- Telcos, banks, licensed e-money issuers, and agent-network operators.
- What you can do
- Launch branded customer wallets, agent cash-in/out, merchant tills & paybills, and settlement — under your brand.
Corridors
Money moves on real corridors.
Not “crypto, somehow.” Each corridor is a named route with a rail and a settlement time — stablecoin in, local money out, reconciled and attested. Pick one to see every leg.
USDCKES
Settles ~2 min- 1
On‑ramp
instantUSDC received on‑chain and verified
- 2
Convert
~30sUSDC → KES at a quoted, locked rate
- 3
Payout
~60sM‑Pesa B2C to the recipient wallet
- 4
Attest
instantReceipt, ledger entry, hash‑chained audit
Corridors, rails, and settlement times are configured per client, market, licence path, and approved liquidity and payout partners. Times shown are representative targets, not guarantees.
Your strategy. Your rails.
Mozaca is not a single-purpose wallet or provider-only platform. It is a modular infrastructure layer for institutions building fintech products around banking partners, payment routes, digital-asset rails, controls, and proof.
Build wallets, treasury, and money movement around reviewable rails.
Mozaca gives partners the operating layer for accounts, transfers, approvals, partner routing, reconciliation, and evidence before production launch.
Govern approved asset workflows without making Mozaca the custodian.
Asset details, route policy, approval rules, risk state, and provider dependencies are visible so institutions can review movement with confidence.
Choose the product path that matches the build.
Each module pairs a clear value proposition with the kind of operating screen a partner needs in diligence: balances, transactions, asset details, approvals, partner rail state, and evidence exports.
Request platform demo
Real build work behind the brand.
Mozaca is the factory behind a portfolio of configurable financial products. Each product has concrete application and infrastructure work behind it, while market and client deployments keep their own brands, integrations, policies, and data boundaries.
Fedha
Client-informed customer, business, agent, merchant, biller, admin, reporting, developer, mobile, POS, and USSD surfaces.
- Client-informed product coreThe reusable architecture has been exercised through a client-specific implementation while the public Fedha brand, configuration model, and client confidentiality remain separate.
- Multi-channel operating proofCustomer and business mobile, web, USSD, merchant, agent, administration, reporting, and developer workflows have implementation and UAT evidence.
- Governed financial backboneLedger, approvals, payouts, audit retention, biller operations, KYC/AML, notifications, interoperability, reconciliation, and recovery controls sit behind the product surfaces.
Hazina
Customer, admin, merchant, reporting, mobile, service, and deployment surfaces.
- Full digital-banking surfacesCustomer, admin, merchant, organization, and reporting workspaces cover accounts, payments, savings, lending, remittance, merchant operations, and treasury controls.
- Mobile operating pathCustomer, merchant, and organization mobile apps include dashboards, units, wallets, approvals, and daily account actions backed by the same service contracts as the web surfaces.
- Policy-led service architectureAccounts, payments, savings, loans, accounting, AML, OPA policy, audit, fraud, customer, ledger, and finance services support the governed platform.
Zent
Customer, client-admin, compliance, developer, operations, mobile, digital-asset, and observability surfaces.
- Expanded product surfacesCustomer, client-admin, compliance, developer, and Mozaca-ops workspaces now cover wallet movement, cards, lending, scheduled payments, provider state, regulatory review, incidents, and fleet health.
- Hardened mobile customer experienceThe Kotlin Multiplatform mobile path covers accounts, balances, send, receive, on/off-ramp, payment, request-money, history, security, responsive layouts, and UAT-focused hardening.
- Digital-finance backendCustody, wallet, card, lending, ledger, payment, on-ramp, off-ramp, FX, AML/KYC, notification, audit, reporting, dynamic policy, and observability services support the platform.
Review path
Review Mozaca in five minutes.
Company storyWhat Mozaca Labs is building and why the products fit together.Product portfolioFedha, Hazina, and Zent positioned as separate products on one platform.Platform logicWallet, ledger, payment, digital-asset, credit, and compliance engines.Status postureWhat is public, reviewable, gated, and still dependent on approvals.
Product engine
New financial products are configuration, not code.
Behind Fedha, Hazina, Zent, and future Mozaca products is a shared engine that defines accounts, savings, lending, wallet tiers, approvals, and compliance policy as configuration on a real-time ledger. Change the configuration, not the client's product core.
defined as configurationproduct.hcl
product "savings_daily" {
ledger = double_entry
currency = "KES"
interest = { rate = 0.06, accrual = "daily" }
limits = { min = 100, max = 500000 }
posting = "real_time" # no overnight batch
compliance = ["kyc_tier_1", "sanctions"]
rails = ["mpesa", "pesalink", "bank"]
}→ live product surfaces, ledger, limits & compliance — no forked codebase
Real-time double-entry — no batch
Balances post and reconcile as events arrive. There is no overnight window where the truth is unknown.
A product library, not a blank page
Wallets, savings, group lending, BNPL, and remittance ship as configurable templates — launch by editing, not rebuilding.
Per-client tenancy & residency
Deploy multi-tenant, dedicated, or hybrid — with Kenyan data-residency options offshore vendors can't match.
New products go live in days
A new account type or plan is a configuration change reviewed and shipped — not a release cycle.
The engines behind every Mozaca product.
Mozaca markets capabilities, not features. Each engine is a reusable piece of financial infrastructure that products consume: wallets, ledger state, payment routing, approved digital-asset movement, credit policy, and compliance evidence — designed to be composed by partners and operated under one control plane.
Explore the platformWho we serve.
Built on controls
Trust you can point to.
Fintech buyers don’t take claims — they take evidence. These are the controls wrapped around every transfer, and the rails Mozaca connects to under partner and regulatory review.
Double-entry ledger
Event-sourced, reconciled balances as the source of truth.
Hash-chained audit
Every meaningful state change leaves signed, correlated evidence.
KYC / KYB & sanctions
Tiered identity and screening enforced before money moves.
Maker-checker & RBAC
Role-bound approvals and limits on every sensitive action.
Per-client isolation
Brand, data, policy, and rails scoped per deployment.
Signed webhooks & exports
Reviewable receipts, webhooks, and audit-ready export packs.
Connects toMobile moneyPesalink / bank railsCard networksUSDC · USDT · cUSDCustody & liquidity partnersKYC / KYB providers