Skip to main content
POST

Endpoint

Authentication

string
required
Bearer token with your API key. Must have Perform Operations permission.
string
required
Must be application/json

Path Parameters

string
required
The unique identifier of the merchant. Must match the merchant ID associated with the API key.

Request Body

Cash-Out Operation

string
required
Must be "cash-out"
string
required
Amount to withdraw (e.g., “20000.00”)
string
required
Distributor short code to withdraw to
string
Optional reference note or description for the operation

Pay Merchant Operation

string
required
Must be "pay-merchant"
string
required
Amount to pay (e.g., “15000.00”)
string
required
Destination merchant’s short code
string
Optional reference note or description for the operation

Pay Individual Operation

string
required
Must be "pay-individual"
string
required
Amount to pay (e.g., “3000.00”)
string
required
Recipient’s phone number in international format (e.g., “+234 8123456781”)
string
Optional reference note or description for the operation

Response

string
Unique identifier for the created operation

Maker-Checker Workflow

Operations created via API follow the maker-checker approval pattern. The operation is created in a pending state and requires approval by a checker before execution.
After creating an operation:
  1. Operation is saved with status pending
  2. A checker with appropriate permissions must approve it via the web interface
  3. Once approved, the operation is executed on the blockchain
  4. The operation status changes to completed or failed

Get Balance

Check merchant balance before creating operations

Get Operations

Query operation history and status