eSign eMandate authorisation errors

eSign eMandate authorisation can return an error if the eSign Service Provider (ESP) gateway rejects the request.

Note that emandate_esign authorisation errors are different to mandate failures in physical and emandate_esign (i.e. mandate rejection after submission and acknowledgement).

See eSign eMandate checkout flow to learn more about the end-to-end redirection and when a customer would see an error.

eSign eMandate authorisation in the eSign Service Provider (ESP) gateway can return errors due to various reasons.

Typical codes are:

• 112: Aadhaar number does not have both email ID and mobile number.

• 517: Expired VID is used in input.

• 953: Exceeded Maximum OTP generation Limit. Try After some time 

• E-119: ASA\\KSA is unable to connect to UIDAI server

• E-148: Ekyc services Unavailable.

• ESP-415: Invalid OTP. No Of Retry Attempt Exhausted!!

• ESP-944: User terminated eKYC process

• ESP-945: User terminated eKYC process after OTP Generation

• ESP-946: User interface page expired

• ESP-999: Unknown Error

Handling errors

When an eSign 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 source eSign eMandate link or you can create a new one for them.

Input rejection with eSign error

If the eSign is successful, the source input is submitted to NPCI, and this automatically creates an acknowledged mandate with UMRN. In rare cases, this may not happen, and the source rolls back to pending_submission status.

• Esign Signature is tampered or corrupt: This error indicates that there was a technical fault in the eSign process. The solution is to create and submit a new source.