Skip to main content
GET
/
v1
/
transactions
/
requery
/
{sessionId}
Confirm a transaction's status by sessionId
curl --request GET \
  --url https://api.nomba.com/v1/transactions/requery/{sessionId} \
  --header 'Authorization: Bearer <token>' \
  --header 'accountId: <accountid>'
{
  "code": "00",
  "description": "Success",
  "data": {
    "id": "POS-WITHDRAW-DFC05-693cd007-cd1e-4ea6-8b79-5f5c4d7a83ea",
    "status": "SUCCESS",
    "amount": 4000,
    "source": "pos",
    "type": "withdrawal",
    "gatewayMessage": "SUCCESS",
    "timeCreated": "2026-03-08T19:26:34.657000Z",
    "fixedCharge": 0,
    "customerBillerId": "539983 **** **** 5118",
    "posTid": "2KUD4AKB",
    "terminalId": "2KUD4AKB",
    "providerTerminalId": "2KUD4AKB",
    "rrn": "230908202632",
    "posSerialNumber": "91230309116826",
    "posTerminalLabel": "KEB MUSA ABUBAKAR",
    "stan": "556734",
    "paymentVendorReference": "2KUD4AKB230908202632",
    "userId": "dfc05ca1-4e75-41dd-8e41-2d362d565893",
    "posRrn": "230908202632",
    "merchantTxRef": "c90d-4b25-ad0f"
  }
}

Documentation Index

Fetch the complete documentation index at: https://developer.nomba.com/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

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<uuid>
required

The parent accountId of the business.

Example:

"890022ce-bae0-45c1-9b9d-ee7872e6ca27"

Path Parameters

​
sessionId
string
required

SessionId

Response

OK - your request was successful.

​
code
string
required

Response Code

Example:

"00"

​
description
string
required

Response description

Example:

"Success"

​
data
object
required