Skip to main content
POST
Niobi Unified Payments

Integration Quick Reference

List of Supported Countries

Coming Soon

List of Supported Kenyan Banks

List of Supported Nigerian Banks

Special Disbursement Flows

Some payout corridors require custom nested payload shapes (such as Kenya Paybill, Till Number, and PesaLink) or additional mandatory compliance details (such as Cameroon CEMAC sender identity). For complete architectural walkthroughs and country rules, see:
payment_method_type: "pay bill"Disburse directly to an M-Pesa Paybill business number with an associated account reference.Documentation & Guides:

Body

application/json

Signed request envelope. All root fields except params are authentication fields.

client_id
string
required

Your Client ID from the Niobi Dashboard under Workspace > Integrations.

Example:

"K1PoY1WYricSpXh6Wm24twnk6ecPJOWrHGsqiKJr"

params
object
required
salt
string
required

A unique random string you generate per request. Must be the same value used when generating the signature.

Example:

"justrandomstring"

sender
string
required

The exact title of your integration as registered in the Dashboard. Case-sensitive.

Example:

"John.co"

timestamp
integer
required

Unix timestamp in seconds at the time of signing. Must match the value used to generate the signature.

Example:

1709363033

signature
string
required

SHA-256 signature computed from this payload. Generate via the Signature endpoint or your own backend.

Example:

"2193d01d50d4bd5da234ac0e0add5d4ccb40907a1b1ab27a12d2c1d88a5d5807"

Response

Payment process initiated successfully.

success
boolean
Example:

true

message
string

Describes the result of initiating the payout. Exact wording may vary depending on the payment processor or channel.

Example:

"Payment process initiated successfully."

data
object
status_code
string
Example:

"000000"