Perform wallet transfer from the parent account
Transfer funds between Nomba accounts (P2P). Bypasses external processors for near-instant settlement. Returns synchronously with data.status: SUCCESS. Note: wallet transfers do not return a sessionId — use the parent account requery endpoint for status checks.
Authorizations
Nomba authenticates API calls with OAuth2 HTTP bearer tokens. There are two methods of authentication; Client-Credentials method and PKCE (Proof Key for Code Exchange) method. In each of the methods, You will get an ACCESS_TOKEN. You need to use an "Authorization" HTTP header to provide your ACCESS_TOKEN. For example: Authorization: {ACCESS_TOKEN}.
Headers
The parent accountId of the business.
"890022ce-bae0-45c1-9b9d-ee7872e6ca27"
Body
The request payload required to perform a wallet transfer.
A structure representing an object required to post a wallet transfer.
The amount to be transferred.
3500
The receiver's accountId.
"890022ce-bae0-45c1-9b9d-ee7872e6ca27"
Unique reference used to track a transaction from an external process.
This is an idempotency key and must be unique per transaction.
"UNQ_123abGGhh5546"
The payment narration
"Testing Payment"
Response
OK - your request was successful.
Response code. This reflects the HTTP status code of the response, e.g. 200 when the request completed successfully and 201 when it was accepted and is still being processed.
200, 201, 400, 401, 403, 429, 500 "200"
Response description
"Success"
Transfer data