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 prices each deployment around product scope, market configuration, client boundaries, rails, controls, implementation, and support. Buyers can understand those commercial drivers before requesting a walkthrough.
Built for what comes next.
Three stages before a final quote.
Product deployments vary by market, rails, integrations, control model, volume, and support obligations, so pricing follows a qualified scope instead of a misleading one-size-fits-all rate card.
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
Digital banking and treasury platform + accounts + lending + 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.
How you'll be billed.
Indicative packaging so you can see the shape before a quote. The Mozaca platform fee is always separated from pass-through costs (rails, FX, compliance vendors), which are shown at cost — no hidden markup. A rate card is issued at commercial review.
01
Pilot
One product, one market, controlled volume.
- Sandbox + one production market
- Guided launch & readiness matrix
- Standard support
Fixed pilot fee + metered movement
02
Growth
Live in production, scaling volume across markets.
- Production environment
- Multi-market configuration
- Higher limits & priority support
Platform fee + per active wallet + per transaction
03
Scale
Multi-product, multi-entity, custom rails.
- Dedicated or hybrid deployment
- Data residency & named liaisons
- Custom rails & SLAs
Committed platform + volume tiers + pass-through at cost
What must be approved before real pricing goes live.
This is the honest commercial boundary: 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.
MAKE THE PROPOSAL COMPARABLETHE DETAILS THAT MATTER
Know what sits inside the scope.
A useful commercial conversation separates the product, implementation, provider dependencies, and the support needed to operate it.
PRODUCT EXPERIENCEIllustrative data
Built around the workflow.Designed for the operator. ↗
Product and configuration
Identify the products, workspaces, channels, client boundaries, roles, and market-specific settings.
A defined platform scopeImplementation and integration
List the provider connections, data migration, custom workflows, testing, and launch activities.
Visible delivery assumptionsOperations and external services
Clarify ongoing support, environments, provider fees, rail charges, verification services, and responsibilities.
An understandable operating cost modelWhy is there no universal price for every deployment?
The number of products, markets, channels, integrations, and operating requirements changes the delivery scope. A scoped proposal is intended to make those assumptions explicit.
What helps produce a useful estimate?
Share your first product, target market, user groups, expected activity, required rails, existing providers, integration needs, and desired support model.
KEEP EXPLORING