Skip to content
Public surfaces operational

Fedha, Hazina and Zent are live — new products on the way. Build with us →

Pricing

Priced around your launch, not a generic rate card.

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.

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.

Evaluation

Qualified walkthrough

Before any quote, your team reviews the product surface, rails, compliance assumptions, implementation model, and fit.

Demo context + evaluation notes

Pilot

Scoped operating brief

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

Final commercial proposal

Issued once partner dependencies, legal posture, support model, and implementation responsibilities are agreed.

Final fees + operating terms

What determines commercial scope.

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

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 we confirm before your final quote.

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 scope
  • 01Product surface, delivery model, and launch markets are agreed.
  • 02Legal and compliance teams confirm the regulated activities, rails, and jurisdiction assumptions.
  • 03Engineering confirms the API scope, environment model, implementation effort, and support responsibilities.
  • 04Mozaca fees are separated from rail, partner, compliance, and pass-through costs.
  • 05The final proposal is issued once your context is specific enough to price accurately.

Every 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.

Request a quote
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. ↗
01

Product and configuration

Identify the products, workspaces, channels, client boundaries, roles, and market-specific settings.

A defined platform scope
02

Implementation and integration

List the provider connections, data migration, custom workflows, testing, and launch activities.

Visible delivery assumptions
03

Operations and external services

Clarify ongoing support, environments, provider fees, rail charges, verification services, and responsibilities.

An understandable operating cost model
Why 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.