API eMandate authorisation can return an error if the supplied details are incorrect, if the customer denies authorisation, or for technical reasons. You'll be notified instantly. Most error types can be easily rectified.
Note that eMandate authorisation errors are different to mandate failures.
eMandate authorisation in ONMAGS (NPCI's Online Mandate Approval Gateway System) can return errors due to various reasons. Click here to see a full list of reasons.
API eMandate authorisation can return an error on the destination bank website if that bank denies the mandate authorisation or has a technical issue. If the error is a technical issue, you may report it to LotusPay Support, we will report it to NPCI, and NPCI will report it to the destination bank and ask them to fix it.
Errors broadly fall into two types: entitled validations and technical errors.
Entitled validations: If the error is a rightful validation by the destination bank (e.g. invalid frequency ADHO for L001 category code, e.g. no such account, e.g. customer not maintaining minimum balance) then there is no further consideration - the bank is entitled to deny authorisation. Here are some of the main validations:
- AP04 Account inoperative. Customer's bank account is inactive or dormant.
- AP05 No such account. The bank account number is wrong.
- AP11 Authentication failed. The input account number does not match with the net-banking login or debit card, or the login details are incorrect.
- AP15 Not maintaining required balance. Customer is not maintaining minimum required/average balance, or there are insufficient funds to cover the destination bank's mandate registration fee.
- AP18 Not allowed for CC account. Customer's bank account is not eligible for eMandate (e.g. some types of business account and jointly-held accounts).
- AP23 Rejected as per customer confirmation. Customer declined to authorise the eMandate on the bank's website.
- AP27 Invalid frequency. The destination bank is entitled to deny ADHO frequency when used with L001 category code.
Technical errors: If the error is temporary server issue, the customer can retry with the same source authorisation link. If the error is a code problem, the bank has to fix it. Some of the main errors are:
- AP28 - Mandate registration failed. This is a generic error used by banks to indicate no other applicable error code or the bank has not mapped the various error codes.
- 474 - Bank returned error XML. This is a generic error given by NPCI to indicate that the bank did not give a valid response structure/format.
- 475 - Invalid bank response received. This is a generic error given by NPCI to indicate that the bank did not give a valid response code.
When an eMandate authorisation error occurs, LotusPay informs you via webhook if you have provided a webhook URL. You can also view the error in the LotusPay dashboard on the source page.
Depending on your integration method, your customer can reuse the same eMandate link or you can create a new one for them.
The success rate of API eMandate authorisation is a function of multiple factors, including:
- Intent - whether the customer fully intended to complete the check-out. Customers may simply abandon the checkout by closing the browser.
- Internet connectivity - whether the customer had a stable internet connection. Customers may loose internet connectivity during the checkout.
- Technical error - whether the destination bank website is functioning correctly. Sometimes they may be having a temporary technical issue.
- Entitled validations - whether the destination bank website is correctly declining the authorisation due to an invalid attempt e.g. wrong account number.