Skip to main content
POST
Pay out from a wallet to a bank account πŸ”’

Authorizations

X-Numero-Api-Key
string
header
required

Your business API key (live_key_...). Issued on approval; managed in Dashboard β†’ Settings β†’ Developer.

X-Numero-Signature
string
header
required

Base64(HMAC-SHA256(publicApiKey, input)) over the raw request body (POST) or canonicalized query string (signed GET). Also send X-Numero-Signature-Version: v2. Required on money-movement / state-changing endpoints (marked πŸ”’).

The HMAC key is your Public Key as raw UTF-8 bytes β€” a SECRET despite the name, and a different value from the X-Numero-Api-Key authentication header. Signing with the API key will never produce a valid signature.

Headers

Idempotency-Key
string
required

A unique string you generate per logical operation. Replaying the same key returns the original result rather than moving money twice; reusing it with a different body is a conflict.

Path Parameters

walletReference
string
required

The wallet's reference, as returned when the wallet was created.

Body

application/json
amount
number<double>
required

Major units (naira

destinationAccountNumber
string
required
destinationBankCode
string
required

Bank code from GET /business/banks.

destinationAccountName
string

Optional. Supply the name returned by name enquiry.

narrative
string

Response

The payout

Canonical response envelope for the public surface. data on success, error on failure.

data
object
required

Endpoint payload on success (object or array); null on failure.

error
object | null
required
meta
object
required