API eMandate rejection

API eMandate authorisation returns a rejection reason code when the destination bank denies authorisation.

API eMandate authorisation in ONMAGS (NPCI's Online Mandate Approval Gateway System) can return rejection reasons.

Note that rejection reasons are different to technical errors.

See API eMandate checkout flow to learn more about the end-to-end redirection and when a customer would see a rejection reason or technical error.

Here is the full list of NPCI destination bank rejection reason codes and duplicate request allowance

Scenario 1: Accepted = true

This is the desired outcome. The destination bank has confirmed to NPCI that the customer successfully authorised the eMandate request, and LotusPay received the response.

Source moves to submitted status and the URL will be blocked from further use.

Scenario 2: Accepted = false

This means the request crossed the NPCI ONMAGS gateway but the mandate request was rejected by the destination bank.

Source remains in pending status, and the response contains the rejection details.

MndtAccptResp (meaning Mandate Accept Response) with Accptd = false, and an alphanumeric reason code beginning with the letters 'AP'. The format is 'APxx' where xx is a number.

These rejection reason codes represent entitled validations by the destination bank (e.g. invalid frequency ADHO for L001 category code, no such account, customer not maintaining minimum balance etc.). These appear in the ReasonCodes worksheet in the above Google Sheet.

There is usually no further consideration - the bank is entitled to deny authorisation. They have rejected the mandate request with a reason.

Typical codes are:

• 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.

• AP28 - Mandate registration failed. This is a generic rejection code used by banks to indicate no other applicable rejection code or the bank has not mapped the various rejection codes. For example, destination bank HDFC Bank returns AP28 rejection for start date being a past date, for frequency ADHO with category code L001, and if mode of operation of account is not singly.

Duplicate request validation by NPCI

Please see this article for important information on duplicate request validation by NPCI ONMAGS.