Get the current status and details for a mandate by customer reference number
Getting started with Digio Rest Apis
|
HTTP Basic
Send
Authorization in header containing the word Basic followed by a space and a base64 encoded string of username:password.
|
Get Mandate Details by CRN
This API is used to get the current status and details for a mandate by customer reference number
|
*
crn
string
|
|
Unique ID to identify mandates provided by Digio.
Unique ID to identify mandates provided by Digio.
➔ This depicts the current state of mandate
➔ The type for mandate which was requested
Details of bank
Email id of bank
Name of the bank
➔ Status with the bank
Time at which shared with the respective bank
Time of authentication with the bank
List of acknowledgement reports from bank
⮕ [ List of acknowledgement reports from bank ]
Unique ID for acknowledgment
UMRN received from bank
Message ID received for acknowledgement
Original Message ID against which the acknowledged is received
Mandate ID
This depicts whether the mandate was accepted or rejected
Time at which acknowledgment was received
Acknowledgment file name
If rejected, this denotes the code
Descriptive reason in case of rejection
Timestamp of acknowledgment
Timestamp of last modification of the acknowledgment
List of response reports from bank
⮕ [ List of response reports from bank ]
Unique ID for response
UMRN received from bank
Message ID received for response
Original Message ID against which the response is received
Mandate ID
This depicts whether the mandate was accepted or rejected
Time at which response was received
Response file name
If rejected, this denotes the code
Descriptive reason in case of rejection
Name of destination bank
Id of destination bank
Timestamp of response
Timestamp of last modification of the response
Details of mandate
Name of file shared with the bank
Identifier for customer, could be email or mobile number
Name of customer
Unique Reference Number identifier the customer
Unique number maintained by Corporate for the reconciliation
Mobile number of customer
Customer email number
➔ Mode of authentication used for mandate
Timestamp of mandate authentication
Denotes whether it is a recurring mandate or not
➔ In case of recurring mandate, denotes the frequency.
Date of first debit
Date of last debit
For fixed amount mandate, this denotes the amount
Maximum amount that may be collected from the customer's account
Masked account number of customer
➔ Type of bank account of customer
IFSC code of customer's bank account
Name of customer's bank
Name of sponsor's bank account
Transaction ID in reference to NPCI
Only present if a sub-user has created the schedule.
Unique ID for sub-user
Identifier for sub-user, this is generally emailID or mobile number
➔ This denotes what type of identifier was used
Sub-user's email id, if registered
Subuser's mobile number
UMRN of the mandate registered
Timestamp at which mandate was created
Last modification timestamp of the mandate
➔ Mode of mandate authentication
➔ In case of API mandate, sub auth mode type
Name of service provider
Utility code for the given corporate config
It is only applicable for API mandate and it returns true/false. If the sponsor bank supports authentication using aadhaar then it returns true, else it returns false.
It is only applicable for API mandate and it returns true/false. If the sponsor bank supports authentication using pan/custId then it returns true, else it returns false.
Failure reason if shared by NPCI after rejecting a request at NPCI gateway level
Failure reason if shared by bank post NPCI gateway acceptence
Details about the exception. Usually contains the exception id for reference.
Error code
Description of the error
Custom errors