ReferenceUpdated May 28, 2026
Environment types
Mozaca separates public guide, sandbox, pilot, and production environments so teams can evaluate product shape before real money or regulated data is involved.
| Environment | Purpose | Data |
|---|---|---|
| Guide | Public documentation and UI examples | Illustrative only |
| Sandbox | API shape, test events, integration review | Test data |
| Pilot | Scoped launch corridor and partner validation | Controlled client data |
| Production | Approved live operation | Live data |
Launch checklist
Production access requires more than working API calls. The operating path must be reviewed across controls, partner dependencies, monitoring, and evidence.
- Entity and product scope accepted.
- Regions, rails, and counterparties reviewed.
- Identity, compliance, and approval policies configured.
- Webhook delivery and reconciliation tested.
- Operational owner, escalation path, and launch monitoring confirmed.
Change control
Changes to production rails, signer policy, high-risk workflows, and webhook destinations require controlled rollout and documented approval.
Related docs
Getting startedUnderstand Mozaca's representative integration model for Fedha, Zent, Hazina, access review, base URLs, and the path from product walkthrough to sandbox integration.AuthenticationAuthenticate Mozaca API requests with backend-held access keys, scoped roles, and environment-specific permissions.WebhooksReceive event updates for transfers, approvals, ledger state, policy changes, and reconciliation without polling.