Skip to content
Public surfaces operational

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

Mozaca docs

Representative developer and operator documentation for wallets, treasury, transfers, webhooks, ledger events, compliance controls, and controlled-access environments.

GuideUpdated May 28, 2026

Evaluation-ready integration docs.

The docs make Mozaca's intended integration model clear for technical buyers and reviewers: API shape, environments, ledger events, compliance controls, webhooks, and operational handoff. Final credentials and approved schemas belong in the private sandbox packet after review.

Authentication

Backend-held keys, scopes, and idempotency headers.

API reference

Wallet, treasury, transfer, ledger, and asset-operation examples.

Webhooks

Events, signatures, retries, and delivery expectations.

Compliance

KYC, KYB, sanctions, transaction monitoring, and launch evidence.

YOUR INTEGRATION READING PATHTHE DETAILS THAT MATTER

Understand the contract before the code.

Work through the access model, financial state, and event boundaries before connecting a production workflow.

PRODUCT EXPERIENCEIllustrative data
Built around the workflow.Designed for the operator. ↗
01

Start with the environment

Establish the product, client context, access path, credential scope, and sandbox assumptions.

A clear environment boundary
02

Follow a complete movement

Read the request, authorization, payment state, webhook, and ledger implications as one journey.

An end-to-end integration model
03

Prepare recovery and support

Agree duplicate handling, error interpretation, reconciliation, incident ownership, and escalation context.

A production review checklist
Which contract should our implementation use?

Use the contract and environment confirmed for your product and deployment. Public guidance supports evaluation and should be checked against the agreed implementation scope.

Where do we discuss an integration gap?

Bring the expected request, response, state transition, and downstream system behavior to a technical review. A concrete flow is more useful than a general feature list.