Skip to main content
POST
Review a same-currency payment to another Numero business

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
Maximum string length: 128

Body

application/json
sourceWalletId
integer<int64>
required
recipientWalletId
string
required

Recipient public Numero wallet ID

amount
number
required
Required range: 0.01 <= x <= 100000000Must be a multiple of 0.01
narration
string
Maximum string length: 500

Response

200 - application/json

Reviewed wallet payment under data; no funds moved

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

data
any
required

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

error
object | null
required
meta
object
required