Submitted physical mandates and eSign eMandates are responded to with a reason code. The reason code can be a rejection.
API eMandates, once authorised by the customer, do not get rejected because they create instant active mandates. However, before submission the customer may face API eMandate authorisation errors.
Mandate rejection is only applicable to physical mandates and eSign eMandates.
Click here to see the full list of NACH Debit mandate response reason codes.
Physical mandates, if rejected, are generally rejected due to signature mismatch or invalid mandate data. This can be resolved by submitting a new source with a suitable correction.
eSign eMandates, if rejected, are generally rejected due to Aadhaar not present in the bank account or invalid mandate data. This can be resolved by asking the customer to add their Aadhaar to their bank account, then submitting a new source.
Physical mandates and eSign eMandates that are in Acknowledged status for 10 working days or more are assumed to be 'TAT EXPIRED' i.e. The destination bank has failed to respond within the turn-around time stipulated by NPCI. It is generally not possible to resolve such cases. The best recourse is to create a new mandate request.