Public
Marketing website
Static public site, product pages, legal pages, insights, and resource surfaces for product evaluation.
Product maturity with clear access boundaries.
A clear view of Mozaca's public surfaces, implemented product paths, client-informed work, controlled environments, and the partner and approval gates that still apply to real movement.
All public surfaces operational
Subscribe to updatesStatus API · JSON — at GA
ComponentProductionSandboxNotes
Marketing website
ProdOperational
Sandbox—
Public site, product pages, docs, and legal surfaces.Documentation
ProdOperational
Sandbox—
API guides, environment model, and integration reference.Product APIs
ProdControlled
SandboxBy approval
Product-specific wallet, ledger, payment, policy, and compliance endpoints.Sandbox environment
Prod—
SandboxBy approval
Seeded test data and credentials for qualified integrators.Webhooks
ProdControlled
SandboxBy approval
Signed delivery for settlement, ledger, and compliance events in qualified environments.Product workspaces
ProdControlled
SandboxBy approval
Customer, organization, merchant, agent, admin, developer, compliance, and operations surfaces by product scope.Component-level incident history, 90-day uptime, and a machine-readable status feed publish with the platform. Until then, environments are issued by approval — subscribe to be notified of maintenance and incidents once live.
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.
Controlled access
API environments
Product sandboxes, pilots, and client environments are separate from the public website and issued only after 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.
Client-informed product core
The 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 proof
Customer and business mobile, web, USSD, merchant, agent, administration, reporting, and developer workflows have implementation and UAT evidence.
Governed financial backbone
Ledger, approvals, payouts, audit retention, biller operations, KYC/AML, notifications, interoperability, reconciliation, and recovery controls sit behind the product surfaces.
Hazina
White-label · Digital banking
Hazina is structured as a white-label digital banking platform: customer accounts, savings, lending, remittance, merchant services, and business treasury controls share one governed core, with each deployment configured for the operator's brand, market, roles, rails, and regulatory path.
Full digital-banking surfaces
Customer, admin, merchant, organization, and reporting workspaces cover accounts, payments, savings, lending, remittance, merchant operations, and treasury controls.
Mobile operating path
Customer, 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 architecture
Accounts, payments, savings, loans, accounting, AML, OPA policy, audit, fraud, customer, ledger, and finance services support the governed platform.
Zent
White-label · Stablecoins
Zent is structured as a per-client stablecoin operations platform: branded wallets, on- and off-ramp corridors, payout paths, customer and operator workspaces, API access, webhook delivery, compliance review, and evidence-backed reporting under one client-aware operating model.
Expanded product surfaces
Customer, 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 experience
The 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 backend
Custody, wallet, card, lending, ledger, payment, on-ramp, off-ramp, FX, AML/KYC, notification, audit, reporting, dynamic policy, and observability services support the platform.
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.