Developer Documentation

Integrate the Orchestrator

Everything you need to connect the Ocuula payment orchestrator to your application — authentication, split engine, provisioning API, webhook system, and transaction tracking.

Documentation

Getting Started

Understand the core concepts — split engine, routing rules, and provisioning models.

Read more →

Authentication

Authenticate API requests using API keys. Authorization headers, sandbox vs live environments.

Read more →

Split Engine Presets

Five presets for distributing funds — percentage, fixed, waterfall, tiered, and direct debit.

Read more →

Splits API

Trigger split executions and batch operations via the Orchestrator API.

Read more →

Transactions API

Query transaction details and track the status of split executions.

Read more →

Provisioning API

Dynamically provision merchants under your platform using the Orchestrator provisioning endpoint.

Read more →

Outbound Webhooks

Signed webhook events dispatched to your destination URL whenever a split is processed.

Read more →

Wallet API

Check your sandbox wallet balance and top up test funds programmatically.

Read more →

Rules API

Create, list, update, and delete routing rules programmatically via the Orchestrator API.

Read more →

Fees & Pricing

Volume-tiered pricing model, fee caps, and the fee preview endpoint for estimating costs.

Read more →

Validators Package

Shared Zod schemas and TypeScript types for split rules, fee calculations, Moolre APIs, and merchant provisioning.

Read more →

Escrow & Approvals

Time-locked escrow holds and multi-signature approval gates for high-value disbursements.

Read more →

USSD API

Offline field-agent payment triggers and interactive USSD session management.

Read more →

Provisioning Models

The Orchestrator supports two merchant provisioning models:

Model A — Sub-Account

The parent merchant provisions a sub-account under its own tenant and Moolre credentials. Ideal for platforms that manage payments on behalf of sub-merchants.

Shared CredentialsSame Tenant

Model B — Direct Keys

The parent creates a new tenant organization with its own Moolre credentials. Each merchant manages their own API keys and settlement wallets.

Isolated TenantOwn Credentials