v1
latestOpenAPI 3.0.02026-07-24270120.1 KBMandate Status Check
Request body
Merchant account ID. Size-12
Aggregator ID. Required if the original transaction was initiated from Aggregator. Size-12
Transaction reference number. Same as original transaction number. Size-12
Hash Value. Size-64
Response
Response code indicating success/failure of the transaction status request 000 / 0000 – Success P9506 - Mandate Expired (for this responseCode merchant needs to update the mandate status as MANDATE_EXPIED at merchant side. And no need to send Notification and Execute API onwards) Any other value indicates status request failure / original transaction not found. For status of the original txn always check errorCode and errorDescription
Size-3
Description of failure. Ignore for Success response. Size-45
Merchant account ID. Echo of request field
Merchant Aggregator ID. Echo of request field
Merchant transaction reference number. Echo of request field
The reason code for failure 0000 - Success U1000 - Pending Anything Else is Rejected
Size-255
Description for failure. Size-255
The unique reference number generated by the Payment Gateway. Only in case of Execute Mandate. Size-24
Authorization date time. Only in case of Execute Mandate Format: YYYYMMDDHHMMSS
Example: 2023111912121
The authorization/payment ID generated by the authorization system. Only in case of Execute Mandate. Size-24
The payment sub instrument type. Only in case of Execute Mandate. Size-64
RRN received from the bank. Size-64
Type of the request. Possible values: CREATE_MANDATE PAUSE_MANDATE REVOKE_MANDATE EXECUTE_MANDATE RESUME_MANDATE NOTIFICATION_MANDATE
Unique Mandate Number. If the mandate is created successfully, then it will be populated. Size-50
QR generated for mandate creation. If the QR is created successfully, then it will be populated. Size-512
Hash Value. Size-64
Unique Mandate ID. If the mandate is created successfully, then it will be populated. Size-50
Echo of request field