Evaluation
Qualified walkthrough
Used before a quote exists. The buyer reviews the product surface, rails, compliance assumptions, implementation model, and fit.
Demo context + evaluation notes
Commercial logic before approved price points.
Mozaca is pre-launch, so this page explains how pricing will be scoped instead of publishing unapproved rates. Buyers can still understand the commercial drivers before requesting a walkthrough.
Three stages before a final quote.
This keeps the site useful without inventing rate cards. Each stage produces a clearer operating view, then the approved commercial terms are inserted once leadership, legal, and engineering sign off.
Pilot
Scoped operating brief
Used when the team can name the region, rails, user type, expected volume, compliance owner, and launch goals.
Pilot scope + commercial assumptions
Production
Approved commercial proposal
Used only after senior review, partner dependencies, legal posture, support model, and implementation responsibilities are clear.
Final fees + operating terms
What determines commercial scope.
These are the variables the pricing model is designed around. They can be reviewed now; the actual fees should wait until the product, rails, compliance path, and implementation scope are real.
01
Product surface
Fedha, Hazina, Zent, embedded API, white-label flow, hosted console, or custom implementation.
02
Access model
Guided walkthrough, sandbox review, pilot, implementation build, or production environment.
03
Usage shape
Wallets, accounts, transfers, approvals, webhooks, reports, active customers, and operator seats.
04
Rail dependencies
Mobile money, banks, cards, FX, settlement partners, transaction monitoring, payment partners, and pass-through costs.
05
Compliance work
KYC, KYB, monitoring, sanctions checks, exception review, evidence exports, and regulator-facing packs.
06
Implementation scope
Data mapping, API integration, sandbox support, launch controls, training, support, and handoff.
Product-specific pricing logic.
Fedha
Wallet access + active wallets + movement events + rail costs
Cross-border or approved digital-asset corridors remain gated by partner, licensing, monitoring, and settlement review.
Hazina
Treasury console/API access + accounts + approvals + reconciliation volume
Cards, FX, yield, and accounting integrations are priced only after partner and control scope is approved.
Zent
Institutional access + policy workflows + provider integrations + reporting
Provider, venue, transaction monitoring, Travel Rule where applicable, and asset-operation costs depend on approved providers and jurisdiction.
Custom
Scoped implementation + platform modules + specialist engineering
Custom work is quoted as a written brief, with deliverables and ownership reviewed before commercial approval.
What must be approved before real pricing goes live.
This is the honest pre-launch state: the page prepares buyers for commercial review, while final numbers and contract terms wait for internal approval.
Request commercial scope- 01The senior team approves the product surface, delivery model, and positioning.
- 02Legal and compliance review the regulated claims, rails, and jurisdiction assumptions.
- 03Engineering approves API shape, environment model, implementation effort, and support responsibilities.
- 04Commercial ownership separates Mozaca fees from rail, partner, compliance, and pass-through costs.
- 05The final proposal is issued only after the buyer context is specific enough to price responsibly.
No public rate card is shown here. Final commercial terms are added only after product, rail, compliance, implementation, and support assumptions are approved.