Public
Marketing website
Static public site, product pages, legal pages, insights, and resource surfaces for pre-launch review.
Pre-launch status for controlled access.
A clear view of Mozaca's public review surfaces, controlled-access environment model, product operating posture, and approval gates before real movement across rails.
How Mozaca exposes availability.
Public surfaces are open for evaluation. Sandbox, pilot, and production environments remain gated until senior, technical, compliance, and partner assumptions are approved.
Ready
Contact flow
Demo and diligence requests route through the public contact surface for qualification.
Guide
Developer docs
Representative API shapes, event models, environments, compliance controls, and launch gates.
Pre-launch
API environments
Sandbox, pilot, and production environments are issued only after internal approval and qualified operating review.
Current product posture.
Fedha
White-label · Mobile money
Fedha is structured for regulated mobile money deployments: a branded platform that can launch customer wallets, merchant acceptance, agent networks, settlement operations, admin workflows, and developer integration without rebuilding the operating backbone for every client.
Customer money app
Customer web and mobile surfaces now show wallet balances, source-wallet transfer review, transaction success states, profile/security flows, and bank-grade dashboard styling.
Operator visibility
Admin, merchant-operations, BI, and developer surfaces are structured around users, transactions, money movement, merchant activity, reporting, and support workflows.
Financial services backbone
Ledger, transaction orchestration, settlement, KYC, notifications, policy packs, customer 360, merchant service, and reconciliation services sit behind the app surfaces.
Hazina
Business · Treasury
Hazina is structured as a global treasury control plane: multi-entity accounts, maker-checker approvals, batch payouts, inbound references, reconciliation, audit trails, accounting exports, and partner-rail orchestration over one operational ledger.
Business finance surfaces
Customer, admin, merchant, and reporting workspaces exist locally for account visibility, finance operations, merchant workflows, and management reporting.
Mobile operating path
Customer, 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 architecture
Accounts, payments, bill pay, savings, loans, accounting, audit, budget, fraud, customer, ledger, and finance services support the treasury operating model.
Zent
White-label · Digital assets
Zent is structured as a per-client digital-asset operations platform: branded wallets, approved asset corridors, payout paths, customer and operator workspaces, API access, webhook delivery, compliance review, and evidence-backed reporting under one client-aware operating model.
Digital-asset product surfaces
Customer, client-admin, compliance, developer, and Mozaca-ops workspaces exist locally to demonstrate asset movement, provider assumptions, compliance queues, and operational review.
Mobile customer experience
Native and React Native customer-app paths are part of the build, so digital-asset wallet journeys can be reviewed beyond a desktop-only prototype.
Institutional backend
Custody, wallet, ledger, payment, on-ramp, off-ramp, FX, KYC, notification, audit, reporting, policy, and observability services support the governed asset-operations model.
Controls before pilot or production movement.
Ledger and reconciliation
Core engine
Double-entry, event-led balance and matching logic powers wallet, treasury, and settlement evidence.
Identity and compliance
Control engine
KYC, KYB, sanctions, transaction monitoring, Travel Rule where applicable, and review paths are configured by product, entity, and jurisdiction.
Local and bank rails
Partner review
Rail availability is mapped by partner approval, corridor, operating entity, and settlement model before launch.
Digital-asset rails
Licensed path review
Fedha and Zent digital-asset flows must clear licensed-path review, transaction monitoring, and partner controls before launch.
Sandbox credentials
Issued after approval
Qualified teams receive environment details only after the product, region, volume, rails, and compliance model are approved.
Controlled pilots should use environment-specific monitoring, incident contacts, operating windows, and agreed service levels once approved.