--- page_source: https://juspay.io/in/docs/lotuspay/web/nach-debit-flow/mandate-rejection page_title: Mandate rejection --- # Mandate rejection ## Acknowledged physical mandates and eSign eMandates are responded to with a reason code. The reason code can be a rejection. Mandate rejection after source submission is only applicable to physical mandates and eSign eMandates. For API eMandate rejection, the source has a different workflow for [errors](https://juspay.io/in/docs/lotuspay/web/nach-debit-flow/api-emandate-errors) and [rejection](https://juspay.io/in/docs/lotuspay/web/nach-debit-flow/api-emandate-rejection). **Click** **[here](https://docs.google.com/spreadsheets/d/1IqijBC8YzqbndCcLSsiP07z4bCT1wW_Yad5PNEPNHAA/edit#gid=0)** **to see the full list of NACH Debit mandate response reason codes.** LotusPay does not have any further information about the rejection reason other than what is visible to you. We have no direct contact with the destination banks as all processes happen via the clearing house and the response codes are preset. **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. Here are some of the common rejection reasons and what you can do to address them: * _M003 Drawers signature differs_ - Submit a new source with a new scan including a better signature from the customer. Ensure it accurately matches the signature on file in the destination bank. * _M008 Company for stamp required or wrong_ - Submit a new source with a new scan including the customer's company stamp on their signature. If the customer is not a company then this mandate has been wrongly rejected by the destination bank (ask the customer to ask their bank why they wrongly rejected it). * _M025 Present under proper mandate category_ - Submit a new source with the appropriate mandate category or frequency. This is usually due to ADHO frequency with L001 category code. Many destination banks reject such mandates because this combination is not permitted by NPCI (see [Mandate categories](https://juspay.io/in/docs/lotuspay/web/nach-debit-flow/mandate-categories)). * _M027 Image not clear_ - Submit a new source with a better quality image of the same paper mandate. * _M038 No such account_ - The destination bank does not recognise the bank account details you inserted in the mandate. Correct the details and create a new source. * _M056 Not maintaining required balance_ - Ask the customer to add funds to their bank account to cross the minimum balance requirement of the bank, to put the account in good standing. Then submit a new source with the same scan image. * _M060 Invalid frequency_ - This is usually due to ADHO frequency with L001 category code. Many destination banks reject such mandates because this combination is not permitted by NPCI (see [Mandate categories](https://juspay.io/in/docs/lotuspay/web/nach-debit-flow/mandate-categories)). Submit a new source, using MNTH frequency. **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. Here are some of the common rejection reasons and what you can do to address them: * _M089 Aadhaar number mismatch in X509 certificate and mandate_ - The Aadhaar number in the mandate does not match with the Aadhaar number in the digital signature. This error is defunct since 2019. * _M090 Aadhaar number mismatch in X509 certificate and bank CBS_ - The Aadhaar number in the digital signature does not match with the Aadhaar number in the bank account. Submit a new source with the correct Aadhaar number. * _M091 eSign signature is tampered or corrupt_ - The eSign signature is not valid. This is a technical error. You'll need to submit a new source. Contact Support to report this issue. * _M092 Signed content does not tally with the data mandate_ - The signed content does not match with the unsigned content. This is a technical error. You'll need to submit a new source. Contact Support to report this issue. * _M093 Aadhaar not mapped to account number_ - There is no Aadhaar number updated in the bank account. Update the Aadhaar number in the bank account and then submit a new source. ### **TAT expired** Physical mandates and eSign eMandates may receive _ncex "TAT expired"_ rejection code. This means that the mandates were in _Acknowledged_ status and the destination bank failed to respond within the turn-around time stipulated by NPCI. The best recourse is to create a new mandate request.