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
Six 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
Wallet Engine
Multi-rail customer and business wallets backed by one balance model.
Fiat, mobile money, bank-partner, and approved asset balances behind a single addressable wallet — with funding, transfer, conversion, and receipt state surfaced to both customer and operator.
Balances, funding, transfers, receipts
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
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
04Engine
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
05Engine
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
06Engine
Compliance Engine
KYC, KYB, sanctions, monitoring, and regulator-ready audit.
Customer identity, business onboarding, sanctions screening, transaction monitoring, and review queues — treated as first-class product flows with audit evidence on every action.
KYC/KYB, screening, monitoring, audit
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
Partner environment
Branded mobile money deployment
Operator channel rollout
Pilot market hardening
Hazina
Business · Treasury
Partner access
Hosted treasury console
API plus console
Business banking layer
Zent
White-label · Digital assets
Qualified access
Branded corridor platform
API and developer workspace
Compliance and operations console
Buyers need to know how the operating model is scoped.
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
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.