LotusPay

NACH Debit migration through Corporate Portability

Pro Merchants can migrate their entire mandate and debit transaction process to LotusPay.

NPCI NACH Circular 230 allows merchants to port their existing mandates from an aggregator's common utility code to a merchant's own utility code.

NPCI NACH Circular 145 allows registered NACH participants to port their NACH Utility Code to one or more sponsor banks.

Merchants can benefit from these rules by fully or partially migrating their NACH Debit process to LotusPay. Get in touch with us at support@lotuspay.comlink icon to get started.

If the merchant wants to continue with its existing sponsor bank and utility code, and if LotusPay has an integration with that sponsor bank, then no migration is required - the merchant can get started with a simple authority letter.

Depending on your requirement, you may consider one or more of the following types of corporate portability.

Adding utility code to an additional sponsor bank

This means you have an existing utility code mapped to a sponsor bank, and now you want to use that utility code with a new or additional sponsor bank. This is useful if you want to route NACH mandates and transactions through a new or additional sponsor bank.

  1. Merchant submits authority letter and NPCI application form to LotusPay.

  2. LotusPay submits these to NPCI via the new sponsor bank.

  3. NPCI maps this utility code to the new sponsor bank. The utility code can also remain mapped to the original sponsor bank.

  4. LotusPay creates an NACH Profile for the merchant, reflecting NPCI's mapping of utility code and sponsor bank.

  5. Merchant can now manage its NACH Debit process in LotusPay using this new NACH Profile.

This process usually takes one week.

Porting mandates with same utility code

This means you have existing mandates with your own utility code that were registered outside LotusPay and now you want to manage them in LotusPay. This is useful if you want to consolidate your NACH process in LotusPay.

  1. Merchant submits the complete mandate data to LotusPay. LotusPay imports these external mandateslink icon. If it's a new sponsor bank, the sponsor bank also imports the mandate data.

  2. Merchant can now manage the imported external mandates in LotusPay, and transact on those mandates.

This process usually takes two weeks.

Porting mandates with change in utility code

This means you have mandates registered with someone else's utility code (e.g. an aggregator) and now you want to change the utility code in those mandates to your own utility code. This is useful if you were earlier using an aggregator's utility code and now you want complete control over your mandates.

  1. Merchant submits a list of Unique Mandate Reference Numbers (UMRNs), a request letter, and a no objection certificate from the owner of the utility code.

  2. LotusPay submits these to NPCI via the sponsor bank.

  3. NPCI updates the utility code in these mandates. This can take up to 20 days, as there is a cooling-off period.

  4. Merchant submits the complete mandate data to LotusPay. LotusPay imports these external mandateslink icon. Sponsor bank does likewise.

  5. Merchant can now manage the imported external mandates in LotusPay, and transact on those mandates.

This process usually takes four weeks.

NPCI responds with the a spreadsheet stating the porting status of each mandate UMRN. The possible error codes are:

ERROR_CODE ERROR_DESCRPTION

T002 Mandatory field missing
T010 Fields exceeds
B006 Invalid UMRN for corporate
B009 Mandate in intermediate state
T006 Invalid UMRN number
B011 Invalid UMRN for corporate
T011 Invalid corporate
T015 Corporate and Participant Mapping not found

Porting out from LotusPay utility code and continuing with our services

This means you have mandates registered with LotusPay's aggregator utility code NACH00000000005549 and now you want to change the utility code in those mandates to your own utility code. This is useful if you were earlier using our utility code and now you want complete control over your mandates. You want to continue using our software.

  1. LotusPay provides merchant with a list of active mandate Unique Mandate Reference Numbers (UMRNs) and a no objection certificate.

  2. LotusPay or the merchant submits these to the sponsor bank.

  3. NPCI updates the utility code in these mandates. This can take up to 20 days, as there is a cooling-off period.

  4. LotusPay updates the mandates after receiving confirmation that NPCI has updated the mandates.

  5. Merchant can continue to manage the ported mandates in LotusPay, and transact on those mandates.

This process usually takes four weeks.

Porting out from LotusPay utility code and not continuing with our services

This means you have mandates registered with LotusPay's aggregator utility code NACH00000000005549 and now you want to change the utility code in those mandates to your own utility code. This is useful if you were earlier using our utility code and now you want complete control over your mandates. You want to stop using our software.

  1. LotusPay provides merchant with a list of active mandate Unique Mandate Reference Numbers (UMRNs) and a no objection certificate. We'll also give you the complete data as your new sponsor bank and/or service provider will need it. Our role ends here (we are not involved in any subsequent steps).

  2. Your new service provider submits these to their sponsor bank or your sponsor bank.

  3. NPCI updates the utility code in these mandates. This can take up to 20 days, as there is a cooling-off period.

  4. Merchant submits the complete mandate data to the new sponsor bank or service provider. They import this mandate data into their mandate management system.

  5. Merchant can now manage the ported mandates in the new service provider or sponsor bank.

This process usually takes four weeks.

Last updated 1 year ago