Integration surfaces for convergent finance.

Explore how Mozaca products expose wallet, treasury, digital-asset operations, ledger, compliance, and webhook surfaces across controlled-access environments.

Representative docs before live credentials.

The developer surface is built to make the integration model rich and reviewable. Final credentials, exact schemas, SDK packages, and environment URLs are issued after access approval.

Public now

Representative API shapes, event examples, product integration paths, and sandbox-access expectations.

Issued after approval

Approved OpenAPI artifacts, sandbox and production URLs, credentials, SDK packages, webhook secrets, and production runbooks.

Review purpose

Give senior stakeholders and technical buyers enough structure to approve layout, content model, and infrastructure direction.

Four areas to evaluate, in the order you'll touch them.

Documentation first, API guide next, SDK requirements when the operating model is clear, and sandbox once the approved access path is ready for controlled testing.

01Guide

Documentation

Concept guides, integration patterns, environment setup, idempotency, and error handling. Read before you build.

Read the docs

02Guide

API Reference

Resource shapes for wallets, transfers, ledger, treasury, asset operations, webhooks, and launch gates.

Review API guide

03Scoped

SDKs

Typed SDK requirements are scoped around auth, retries, pagination, idempotency, and webhook signing.

Discuss SDK needs

04By request

Sandbox

Non-production environment with seed data, simulated rails, and replayable webhooks. Issued after qualification.

Request sandbox

What engineering teams can integrate.

The public site does not expose live credentials. It should still make the implementation shape clear enough for technical buyers and senior reviewers to qualify fit.

Fedha

Wallet APIs

Create wallets, read balances, initiate transfers, and receive settlement events.

Hazina

Treasury APIs

Configure digital accounts, savings and lending products, business approvals, payment batches, AML decisions, reconciliation, and exports.

Shared core

Ledger events

Trace derived balances, journal entries, matching state, receipts, and exception queues.

Shared core

Policy and compliance state

Expose KYC/KYB, AML, sanctions, dynamic authorization, approvals, transaction monitoring, Travel Rule where applicable, review, and evidence outcomes.

Zent

Asset controls

Map signer roles, policy limits, risk state, and evidence-backed transfer approvals.

All products

Webhooks

Subscribe to transaction, approval, ledger, policy, and reconciliation lifecycle events.

API and event examples for integration planning.

These examples are representative of the surface we discuss in sandbox review. Final payloads, signatures, credentials, and environment hosts depend on product, rail, region, compliance scope, and partner approvals.

Transfer request

Example

POST /v1/transfers
{
  "source": "wallet_kes_184250",
  "destination": {
    "type": "mobile_money",
    "network": "partner_mobile_money",
    "phone": "+2547..."
  },
  "amount": "2500.00",
  "currency": "KES",
  "metadata": {
    "customer_ref": "pilot-user-184"
  }
}

Settlement webhook

Example

{
  "id": "evt_01HZX7",
  "type": "transfer.settled",
  "product": "fedha",
  "created_at": "2026-05-25T09:24:18Z",
  "data": {
    "transfer_id": "tr_9K42",
    "status": "settled",
    "rail": "partner_mobile_money",
    "ledger_state": "matched"
  }
}

Try it

Run a request against the sandbox shape.

Representative payloads and responses — the same surface we walk through in sandbox review. Signatures, hosts, and credentials are issued to qualified teams.

POST /v1/transfers

{
  "amount": 25000,
  "currency": "KES",
  "source": "wallet_kes_sample_001",
  "destination": "wallet_kes_settlement_001",
  "rail": "mpesa"
}

Response

// Run a request to see the response

Your first wallet in a few lines.

Install the SDK for your language, authenticate with a sandbox key, and create a wallet. The same ergonomics back every product — swap the resource, keep the shape.

Create a wallet

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 label. Your test key and SDK package access are issued with sandbox access.

Seeded test data to build against.

The sandbox ships with seeded customers, wallets, and rails so you can run the full lifecycle before touching production. Representative values are shown here; your live test credentials are issued with sandbox access.

Sandbox base URLhttps://sandbox.api.mozacalabs.com/v1

Example secret keyMOZACA_SANDBOX_KEY

Example customercus_sample_001

Example walletwallet_kes_sample_001

Example MSISDN (mobile money)+254708000000

Example webhook secretMOZACA_WEBHOOK_SIGNING_SECRET

Developer surface updates.

A dated log of controlled-access developer-surface changes, tagged so technical buyers can tell additive from breaking at a glance. Versioned API releases begin at general availability.

2026-06-18Added

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.

2026-05-30Security

Signed-webhook scheme defined

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

2026-05-12Changed

Idempotency keys required on writes

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

2026-04-24Docs

Quickstart and SDK guidance

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

Each product has a different integration 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

Technical buyers can now review the intended shape of authentication, wallets, treasury, transfers, webhooks, environments, and idempotency before requesting sandbox access.

Read the docs

How sandbox review works.

1. Request access

Submit product, company, region, rails, and launch timeline through the demo request flow.

2. Fit review

We route the request to walkthrough, sandbox review, pilot scoping, or partner diligence.

3. Integration plan

Qualified teams receive API surface, event model, sample flows, and implementation milestones.