POST
/
v1
/
transactions
/
accounts

Authorizations

Authorization
string
headerrequired

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

accountId
string
required

The parent accountId of the business.

Query Parameters

limit
integer

This endpoint is paginated. limit describes the size of the page you are querying

cursor
string

The cursor is used to scroll to the next page. When making the first call to list all accounts, there is no need to pass in any cursor since the API has not returned any cursor back to you. Only use cursor when the API provides it

dateFrom
string

This starting date (UTC). Sample date: 2023-01-01T00:00:00

dateTo
string

This ending date (UTC). Sample date: 2024-09-30T23:59:59

Body

application/json
transactionRef
string

Transaction ID/Reference

status
enum<string>

Transaction status

Available options:
NEW,
PENDING_PAYMENT,
PAYMENT_SUCCESSFUL,
PAYMENT_FAILED,
PENDING_BILLING,
SUCCESS,
REFUND
source
enum<string>

Transaction source

Available options:
api,
pos,
web,
android_app,
ios_app
type
enum<string>

Transaction type

Available options:
withdrawal,
purchase,
transfer,
p2p,
online_checkout,
qrt_credit,
qrt_debit
terminalId
string

Terminal ID

rrn
string

RRN (Retrieval Reference Number)

merchantTxRef
string

Merchant transaction reference

orderReference
string

Online checkout order reference

orderId
string

Online checkout order id

Response

200 - application/json
code
string
required

Response Code

description
string
required

Response description

data
object
required
Fetch transactions on the parent accountFetch a single transaction on a sub account