Description -
- Your organization will provide us a Call-back URL with the following configurations.
- The Call-back URL should be of Method Type POST and Content-type should be application/JSON.
- The Call-back URL should have the request and response formats as provided for your reference.
Request Body Parameters
FIELD | DESCRIPTION | DATA TYPE | MANDATORY/NOT MANDATORY |
statusDesc | Final transaction status description from bank. | String | Mandatory |
createdDate | date of creation | String | Mandatory |
updatedDate | date of update | String | Mandatory |
productCode | specific product code. E.g.- "PAYOUT" | String | Mandatory |
txnType | Type of transaction performed, E.g.-"WALLET2CASHOUT _IMPS" | String | Mandatory |
txnAmount | Transaction amount. E.g.- "100000" | String | Mandatory |
rrn | Unique rrn from bank. | String | Mandatory |
txnId | Transaction id(unique for each transaction performed). E.g.- "371412641292288" | String | Mandatory |
Status | Final transaction status from bank. Maximum length- 20. E.g.- "FAILED" | String | Mandatory |
customeridentIfication | Unique customer identification number of customer. E.g.- "50200042591926" | String | Mandatory |
username | Specific user name. E.g.- "isutest" | String | Mandatory |
clientRefId | Client Reference id. E.g.- "7GX00312876899" | String | Mandatory |
param_b | To be used as per client’s need. | AlphanumericString | Not Mandatory |
Param_c | To be used as per client’s need. | AlphanumericString | Not Mandatory |
Mode of Pay: IMPS
Request Body JSON
Sample Response Body
Parameters | Values |
statusCode | This field displays the actual final status of a transaction. (Possible status code – 0, -5) |
statusDesc | This field displays the actual status of a transaction. (Possible status - SUCCESS,FAILED) |
Success :
Inprogress :
FAILED:
Status Codes
Code | Significance | Description |
SUCCESS | 0 | Transaction is Successful |
FAILED | -5 | Successfully Credited. |
INPROGRESS | -5 | Transaction is in Progress. |