Authentication
Backend-held keys, scopes, and idempotency headers.
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.
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.
Start
Getting started
GuideUnderstand Mozaca's product-factory model, shared engines, Fedha, Hazina, Zent, access review, base URLs, and the path from product walkthrough to sandbox integration.
Read docsSandbox and OpenAPI
GuideWhat qualified teams receive after sandbox review: approved OpenAPI artifacts, sample data, webhook replay, SDK expectations, and launch-gate evidence.
Read docsAuthentication
ReferenceAuthenticate Mozaca API requests with backend-held access keys, scoped roles, and environment-specific permissions.
Read docsCore APIs
Wallets
SandboxUse wallet APIs to create Fedha customer wallets, read balances, configure client funding routes, and expose receipt-ready transfer state.
Read docsTreasury
SandboxUse treasury APIs to model business accounts, approval policies, payment batches, vendor movement, reconciliation, and exports.
Read docsLedger and reconciliation
ReferenceDesign balances, journal entries, reconciliation matching, exception queues, receipts, statements, and export-ready evidence.
Read docsZent corridor operations
SandboxModel Zent digital finance corridor workflows with provider visibility, mobile-money payout state, customer controls, and evidence exports.
Read docsOperations
Compliance controls
ReferenceMap KYC, KYB, sanctions, transaction monitoring, Travel Rule where applicable, jurisdiction-specific requirements, and regulator-ready evidence.
Read docsTransfers
ReferenceCreate transfer instructions, track lifecycle state, make retries safe, and expose settlement evidence to product and operations teams.
Read docsWebhooks
ReferenceReceive event updates for transfers, approvals, ledger state, policy changes, and reconciliation without polling.
Read docsYOUR 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. ↗
Start with the environment
Establish the product, client context, access path, credential scope, and sandbox assumptions.
A clear environment boundaryFollow a complete movement
Read the request, authorization, payment state, webhook, and ledger implications as one journey.
An end-to-end integration modelPrepare recovery and support
Agree duplicate handling, error interpretation, reconciliation, incident ownership, and escalation context.
A production review checklistWhich 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.
KEEP EXPLORING