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.
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 presented as a company site, but each product has concrete application and infrastructure work behind it: product screens, local app surfaces, service boundaries, operating workflows, and review paths that can be demonstrated during a walkthrough.
Fedha
Customer web, mobile app, admin, merchant ops, BI, developer surface, and financial services.
- Customer money appCustomer web and mobile surfaces now show wallet balances, source-wallet transfer review, transaction success states, profile/security flows, and bank-grade dashboard styling.
- Operator visibilityAdmin, merchant-operations, BI, and developer surfaces are structured around users, transactions, money movement, merchant activity, reporting, and support workflows.
- Financial services backboneLedger, transaction orchestration, settlement, KYC, notifications, policy packs, customer 360, merchant service, and reconciliation services sit behind the app surfaces.
Hazina
Customer, admin, merchant, reporting, mobile, service, and deployment surfaces.
- Business finance surfacesCustomer, admin, merchant, and reporting workspaces exist locally for account visibility, finance operations, merchant workflows, and management reporting.
- Mobile operating pathCustomer, merchant, and organization mobile apps are part of the local build, keeping daily account actions close to the same logic used by the web surfaces.
- Service architectureAccounts, payments, bill pay, savings, loans, accounting, audit, budget, fraud, customer, ledger, and finance services support the digital banking, lending, and treasury platform.
Zent
Customer, client-admin, compliance, developer, operations, mobile, digital-asset, and observability surfaces.
- Digital-asset product surfacesCustomer, client-admin, compliance, developer, and Mozaca-ops workspaces exist locally to demonstrate asset movement, provider assumptions, compliance queues, and operational review.
- Mobile customer experienceNative Android and React Native customer-app paths are part of the build, so wallet journeys can be reviewed beyond a desktop-only prototype.
- Institutional backendCustody, wallet, ledger, payment, on-ramp, off-ramp, FX, KYC, notification, audit, reporting, policy, and observability services support the governed asset-operations model.
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 Hazina — and every Mozaca product — is a product engine that defines accounts, savings, lending, and wallet tiers as configuration on a real-time ledger. Change the config, launch the product.
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