Skip to content
Public surfaces operational

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

API v1 Sandbox preview

One API for every product you launch on Mozaca.

Wallets, transfers, bulk payouts, FX, ledger and compliance — the same REST resources and signed webhooks behind Fedha, Hazina, Zent and every product that follows.

  • REST & JSON
  • HMAC-signed webhooks
  • Idempotent writes
  • Simulated rails in sandbox
sandbox

Create a KES 2,500 mobile money transfer; it returns 201 and emits created, posted and settled webhooks.

Webhooks

Every movement, pushed to you.

Transfers, payouts, conversions, approvals and reconciliation each emit signed events. Failed deliveries retry with backoff, and any event can be replayed. Here is a sandbox log in motion.

Event log1,284 delivered · sandbox, demo data

Following the newest event. Select any row to inspect it.

POST https://webhooks.yourcompany.com/mozaca
Mozaca-Signature: t=1790514235,v1=54d96018c3a91f0e5b…Mozaca-Delivery: attempt 1 of 5 {  "id": "evt_01J9Q7A4XK",  "type": "transfer.settled",  "created": "2026-09-27T09:24:21Z",  "livemode": false,  "data": {    "id": "tr_01J9Q4K2VX",    "status": "settled",    "amount": "2500.00",    "currency": "KES",    "rail": "mobile_money"  }}
API reference

The API at a glance.

Predictable resources, one authentication model and the same error shape everywhere. Launch a new product on Mozaca and it speaks this API from day one.

Full API guide

Wallets

All products
  • POST/v1/walletsCreate a wallet
  • GET/v1/wallets/{id}Retrieve balance
  • GET/v1/wallets/{id}/transactionsList movements

Transfers

Fedha · Hazina
  • POST/v1/transfersSend money
  • GET/v1/transfers/{id}Track a transfer
  • POST/v1/transfers/{id}/reverseReverse

Payouts

Fedha · Hazina
  • POST/v1/payouts/batchesUpload a batch
  • POST/v1/payouts/batches/{id}/approveApprove
  • GET/v1/payouts/batches/{id}Batch status

FX & stablecoin

Hazina · Zent
  • POST/v1/fx/quotesQuote a rate
  • POST/v1/fx/conversionsConvert
  • GET/v1/corridorsCorridors & limits

Ledger

Shared core
  • GET/v1/ledger/entriesJournal entries
  • GET/v1/reconciliation/runsReconciliation runs
  • GET/v1/reconciliation/exceptionsExceptions

Compliance & webhooks

Shared core
  • GET/v1/compliance/cases/{id}Case & evidence
  • POST/v1/webhook_endpointsSubscribe
  • POST/v1/events/{id}/replayReplay an event
Try it

Send a request right here.

Pick an endpoint and press send. Responses are representative of the sandbox — hosts, signatures and credentials are issued to approved teams.

POST/v1/transfers
{  "amount": "25000.00",  "currency": "KES",  "source": "wallet_kes_sample_001",  "destination": "wallet_kes_settlement_001",  "rail": "mobile_money"}
curl -X POST https://sandbox.api.mozacalabs.com/v1/transfers \
  -H "Authorization: Bearer MOZACA_SANDBOX_KEY" \
  -H "Content-Type: application/json" \
  -d '{"amount":"25000.00","currency":"KES","source":"wallet_kes_sample_001","destination":"wallet_kes_settlement_001","rail":"mobile_money"}'
Response
// Press “Send request” to see the response
Quickstart

From key to first transfer in minutes.

  1. 1

    Install the SDK

    Or call the REST API directly — every example has a cURL twin.

  2. 2

    Authenticate

    Use your sandbox secret key. Keys are scoped per environment and role.

  3. 3

    Move money

    Create a wallet, fund it from a simulated rail, send a transfer.

  4. 4

    Listen for events

    Verify the signature on each webhook and update your records.

curl https://sandbox.api.mozacalabs.com/v1/wallets \
  -H "Authorization: Bearer MOZACA_SANDBOX_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "owner": "cus_sample_001", "currency": "KES" }'

MOZACA_SANDBOX_KEY is a placeholder. Your test key and SDK package access are issued with sandbox access.

Sandbox

Seeded data to build against.

Every sandbox ships with seeded customers, wallets and simulated rails, so you can run the full lifecycle before production. The values here are representative.

Public now
Representative API shapes, event examples, product integration paths and what sandbox access includes.
Issued with access
Approved OpenAPI files, sandbox and production hosts, credentials, SDK packages, webhook secrets and runbooks.
.env.sandboxRepresentative
# Issued with sandbox accessMOZACA_API=https://sandbox.api.mozacalabs.com/v1MOZACA_SANDBOX_KEY=MOZACA_SANDBOX_KEYMOZACA_WEBHOOK_SECRET=MOZACA_WEBHOOK_SIGNING_SECRETSAMPLE_CUSTOMER=cus_sample_001SAMPLE_WALLET=wallet_kes_sample_001SAMPLE_MSISDN=+254708000000
Integration paths

Each product, its own path.

Fedha

White-label · Mobile money

Client-informed platform
Primary users
Wallet customers, agents, merchants, operations teams, compliance/admin teams
Regions
Multi-jurisdiction by configuration; regulatory packs and rails selected per client
Rails
Mobile money, trust accounts, merchant paybills/tills, bank interfaces, and partner-approved future corridors
Integration surfaces
Customer app, web app, APIs, webhooks, statements, reports, exports
Product demo
Hazina

White-label · Digital banking

Partner access
Primary users
Retail customers, merchants, finance teams, and operator admins
Regions
Configured per licensed partner, banking rail, and corridor
Rails
Bank accounts, mobile money, card networks, and partner payout rails
Integration surfaces
Treasury console, payment APIs, approval events, accounting exports
Product demo
Zent

White-label · Stablecoins

Qualified access
Primary users
Customers, client admins, developers, Mozaca operators, compliance reviewers
Regions
Configured by client market, regulatory path, and approved provider coverage
Rails
Approved digital-asset routes, payout networks, settlement partners, payment providers
Integration surfaces
Web and mobile apps, USSD, OpenAPI, SDKs, webhooks, service APIs
Product demo
Changelog

What's new.

  1. Added

    OpenAPI 3.1 sandbox model prepared

    Wallets, transfers, ledger, and webhook resources are organized into a representative OpenAPI 3.1 model used during approved sandbox review and SDK planning.

  2. Security

    Signed-webhook scheme defined

    Webhook delivery is designed around HMAC-SHA256 signatures, per-endpoint secrets, and replay-protection timestamps for approved environments.

  3. Changed

    Idempotency keys required on writes

    All POST endpoints accept an Idempotency-Key header; retried requests return the original result instead of re-executing.

  4. Docs

    Quickstart and SDK guidance

    Node, Python, Go, and cURL examples show the intended integration ergonomics alongside the interactive API playground.

Access

How sandbox access works.

  1. 1

    Request access

    Tell us the product, company, region, rails and launch timeline.

  2. 2

    Fit review

    We route you to a walkthrough, sandbox review, pilot scoping or partner diligence.

  3. 3

    Build

    Your team gets the API surface, event model, sample flows and implementation milestones.

Request sandbox access
INTEGRATE FOR REAL-WORLD CONDITIONSTHE DETAILS THAT MATTER

Build the happy path. Plan the edges.

Financial integrations need more than a successful API response. Review the behavior around duplicate requests, delayed events, authorization, and reconciliation.

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

Requests you can safely retry

Agree how idempotency keys, request references, validation errors, and retry windows behave for each write operation.

Predictable duplicate protection
02

Events you can verify

Confirm signing, timestamps, replay protection, delivery ordering, and recovery after missed callbacks.

A documented event contract
03

State you can reconcile

Keep internal IDs, product references, provider references, and ledger identifiers connected in your integration.

A traceable reconciliation path
Are the public examples production credentials or live endpoints?

No. Public examples explain the integration model. Access, credentials, environments, and the exact product contract are reviewed through the developer onboarding process.

What should the technical team bring to a review?

Share the intended user flows, existing systems, authentication model, supported environments, expected volumes, event-handling approach, and how your team closes the financial records.