Skip to main content

Status Enquiry

Initiate the request to get the status of any transaction, being initiated. It is mandatory to implement status enquiry because in cases when there is no response through callback or return URL due to any exceptions or network error. Status API can help to get the final status of the transaction.

Endpoint

Endpoint
{baseUrl}/pgui/services/paymentServices/transactionStatus
S No.Parameter NameData TypeMandatory
1APP_IDNumericYes
2TXN_IDNumericNo
3ORDER_IDAlphaNumericYes
4CURRENCY_CODENumericYes
5AMOUNTNumericYes
6HASHAlphaNumericYes
caution
  • Request must be as JSON based REST API (HTTP POST).
  • AMOUNT must not be in decimal.
  • HASH generation mechanism is shared in document (Appendix.pdf).
  • ORDER_ID must be the one Merchant used while initiating the transaction.
  • CURRENCY_CODE must be the one Merchant used while initiating the transaction.
  • TXN_ID must be the one Merchant received in response.
  • It is recommended to check the combination of status and response code received in response. Response Code: (000) + Status: (Captured) = Successfully Captured
info

PLEASE DO NOT RELY ON ANY OTHER RESPONSE THAN RESPONSE_CODE + STATUS. ALL OTHER MESSAGES MAY CHANGE. ONLY RESPONSE_CODE = 000 + STATUS = ‘Captured’ = SUCCESSFUL TRANSACTION. REST ANY OF THE COMBINATIONS LIKE RESPONSE_CODE =000 + STATUS = Enrolled/PENDING DOES NOT MEAN ITS SUCCESS.

Response Sample

Example
[
{
"RESPONSE_CODE": "000",
"APP_ID": "1000221129001154",
"TXN_ID": "1010240710073757",
"MOP_TYPE": "MC",
"CARD_MASK": "510000******0511",
"ACQ_ID": "1001230116215646",
"ACQUIRER_RESPONSE": "SUCCESS",
"CURRENCY_CODE": "840",
"HASH": "35B74A0BD06C3FF06B05A2077D90ACEAAF2DCFA1EC96455B4814568CB48D1DBA5DF3CAD6D9B1674E5329D0C363349E54A4EF8484CFACE600FC406177DD489196",
"PAYMENT_TYPE": "CC",
"STATUS": "Captured",
"CREATE_DATE": "2022-04-14 01:34:55",
"ORDER_ID": "SIGN1673886404099",
"AMOUNT": "4000",
"RESPONSE_MESSAGE": "SUCCESS",
"AMOUNT_DECIMAL": "40.00"
},
{
"API_RESPONSE": "000"
}
]