STATUS 402 API
Last updated
Last updated
NPCI sends the Transaction Status Request to BOU.
BOU forwards the Transaction Status Request to Biller.
Biller sends the Transaction Status Request Acknowledgement to BOU, immediately upon receiving the request.
After Biller processes the request, the resulting Transaction Status Request is sent to BOU.
Once BOU receives the Transaction Status Response, a Transaction Status Response Acknowledgement is sent to Biller.
BOU forwards the Transaction Status Response to NPCI.
On receiving the Transaction Status Response, NPCI sends Transaction Status Response to BOU.
Once BOU receives the Transaction Status Response from NPCI, they send the corresponding notification to Biller.
STATUS 402 API is used to check the status of the bill transaction
The various parameters are explained below:
[ROOT] (No parent property / element)
refId
M
String
Unique identification assigned by the initiating BBPOU to unambiguously identify the transaction which is passed on, unchanged, throughout the entire end- to-end chain, binding the Fetch and Payment messages
txn
M
String
Transaction information passed throughout the system.
txn.ts
M
String
Transmission date and time of the transaction
txn.xchange
M
String
Identification of the type of the request – transaction status (402)
txnStatusReq
M
String
Information pertaining to transaction status request
txnStatusReq.msgId
M
String
Unique identification assigned by the initiating BBPOU for chaining a request and response message
txnStatusReq.txnRefere nceId
M
String
Transaction reference number used by the Customer for referring to a Payment transaction
Expected Acknowledgement Parameters
The various parameters are explained below:
[ROOT] (No parent property / element)
reason
M
String Min Length – 1, Max Length – 100
Reason of the Status
code
M
String Fixed Length 3
Response code for a request
status
M
String Min Length – 1, Max Length – 100
Status of given request
Json Formatted Request Example
Json Formatted Response Example