Evaluation
Qualified walkthrough
Before any quote, your team reviews the product surface, rails, compliance assumptions, implementation model, and fit.
Demo context + evaluation notes
Fedha, Hazina and Zent are live — new products on the way. Build with us →
Every deployment is priced around its product scope, markets, rails, controls, implementation, and support. Here is what drives the price, how billing is structured, and how a quote comes together.
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.
Evaluation
Before any quote, your team reviews the product surface, rails, compliance assumptions, implementation model, and fit.
Demo context + evaluation notes
Pilot
Once you can name the region, rails, user type, expected volume, compliance owner, and launch goals, we scope a pilot around them.
Pilot scope + commercial assumptions
Production
Issued once partner dependencies, legal posture, support model, and implementation responsibilities are agreed.
Final fees + operating terms
These are the variables every quote is built from. The more of them you can share up front, the more precise your first proposal will be.
01
Fedha, Hazina, Zent, embedded API, white-label flow, hosted console, or custom implementation.
02
Guided walkthrough, sandbox review, pilot, implementation build, or production environment.
03
Wallets, accounts, transfers, approvals, webhooks, reports, active customers, and operator seats.
04
Mobile money, banks, cards, FX, settlement partners, transaction monitoring, payment partners, and pass-through costs.
05
KYC, KYB, monitoring, sanctions checks, exception review, evidence exports, and regulator-facing packs.
06
Data mapping, API integration, sandbox support, launch controls, training, support, and handoff.
Wallet access + active wallets + movement events + rail costs
Cross-border or approved digital-asset corridors remain gated by partner, licensing, monitoring, and settlement review.
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.
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.
Scoped implementation + platform modules + specialist engineering
Custom work is quoted as a written brief, with deliverables and ownership reviewed before commercial approval.
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
One product, one market, controlled volume.
Fixed pilot fee + metered movement
02
Live in production, scaling volume across markets.
Platform fee + per active wallet + per transaction
03
Multi-product, multi-entity, custom rails.
Committed platform + volume tiers + pass-through at cost
Pricing a regulated product responsibly takes specifics. These are the points we settle with you before final numbers and contract terms are issued.
Request commercial scopeEvery proposal separates the Mozaca platform fee from rail, FX, and compliance-vendor costs, which are passed through at cost. Share your market, rails, and expected volume for a scoped quote.
A useful commercial conversation separates the product, implementation, provider dependencies, and the support needed to operate it.
Identify the products, workspaces, channels, client boundaries, roles, and market-specific settings.
A defined platform scopeList the provider connections, data migration, custom workflows, testing, and launch activities.
Visible delivery assumptionsClarify ongoing support, environments, provider fees, rail charges, verification services, and responsibilities.
An understandable operating cost modelThe number of products, markets, channels, integrations, and operating requirements changes the delivery scope. A scoped proposal is intended to make those assumptions explicit.
Share your first product, target market, user groups, expected activity, required rails, existing providers, integration needs, and desired support model.