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 should be inserted after senior approval.

Public now

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

Inserted later

Approved OpenAPI artifacts, environment 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 accounts, approvals, payment batches, reconciliation, and exports.

Shared core

Ledger events

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

Shared core

Compliance state

Expose KYC, KYB, sanctions, transaction monitoring, Travel Rule where applicable, limits, 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"
  }
}

Each product has a different integration path.

Fedha

White-label · Mobile money

Partner environment

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

Business · Treasury

Partner access

Primary users

CFO teams, fintech operators, marketplace finance teams

Regions

Configured per licensed partner, banking rail, and corridor

Rails

Local accounts, mobile money, ACH, SEPA, wire/SWIFT partners

Integration surfaces

Treasury console, payment APIs, approval events, accounting exports

Product demo

Zent

White-label · Digital assets

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.