NACH Profiles

NACH Profile is the mapping of utility code, sponsor bank and creditor bank account.

NACH profile is the name given by LotusPay for a mapping of a sponsor bank, utility code, and (optionally) a creditor bank account. It is the basis of all NACH source, mandate and debit transaction activity.

You can view your NACH profiles in Dashboard > Settings > Company Settings.

NACH profile creation

After your sponsor bank has mapped your utility code to that sponsor bank and mapped your utility code to credit your bank account, you can email LotusPay Support to create this exact NACH profile in our system. You should mention:

a) The sponsor bank e.g. ICICI Bank.

b) The utility code (e.g. NACH00000000005549) and associated user name (e.g. LOTUSPAY SOLUTIONS PVT LTD).

c) The creditor bank account details (account holder name, account IFSC and account type, along with evidence such as bank letter, cancelled cheque or recent bank statement).

NACH profile must precisely reflect the mapping of sponsor bank and utility code done by NPCI, and must precisely reflect the mapping of utility code to a creditor bank account done by the sponsor bank. We can't create profiles that do not abide by this.

Examples

Example 1 - No NACH profile (defaults to LotusPay aggregator):

If you do not see any NACH profiles in your company settings page, it means you're using LotusPay's aggregator NACH profile by default.

Example 2 - LotusPay aggregator:

NACH00000000005549 --- ICIC --- LOTUSPAY-NODAL

This NACH profile is mapping LotusPay's aggregator utility code to sponsor bank ICICI Bank, and it is mapped to credit funds to LotusPay's nodal account within ICICI Bank.

Example 3 - Merchant LotusPay nodal:

NACH00000000009999 --- ICIC --- LOTUSPAY-NODAL

This NACH profile is mapping a merchant's utility code to sponsor bank ICICI Bank, and it is mapped to credit funds to LotusPay's nodal account within ICICI Bank.

Example 4 - Merchant:

NACH00000000009999 --- HDFC --- nil

This NACH profile is mapping a merchant's utility code to sponsor bank HDFC Bank, and it has no creditor bank account mapped to it. The merchant can use this NACH profile to register mandates in LotusPay, but not to create ACH Debit transactions. The merchant can create ACH Debit transactions directly with their sponsor bank.

Example 5 - Merchant:

NACH00000000009999 --- HDFC --- BA0082N2GDTD12

This NACH profile is mapping a merchant's utility code to sponsor bank HDFC Bank, and it is mapped to credit funds to the merchant's own bank account within HDFC Bank. This merchant can use this profile to register mandates and process ACH Debit transactions in LotusPay.

NACH profile usage in source and mandate

Source must be created on an NACH profile. If the source is submitted, the resulting mandate automatically takes the same NACH profile.

The mandate retains its original NACH profile unless we update it to another one. Pro merchant can ask us to do this in bulk by emailing LotusPay Support. If you want to change the mandate's NACH profile to one with a different sponsor bank than that which originally registered the mandate, you'll need to ensure that the new sponsor bank recognises this mandate (some sponsor banks require to import the mandate data first).

• In LotusPay API, you must specify the NACH profile on which to create the source. You do this by specifying the creditor_agent_code (sponsor bank) and creditor_utility_code. If you have multiple NACH profiles with the same creditor_agent_code and creditor_utility_code, the system will take the last updated NACH profile.

• In LotusPay imports, you must specify the NACH profile on which to create the source. You do this by specifying the creditor_agent_code (sponsor bank) and your utility code. If you have multiple NACH profiles with the same creditor_agent_code and creditor_utility_code, the system will take the last updated NACH profile.

• In LotusPay dashboard forms and plan public forms, you cannot specify the NACH profile. The source automatically takes the last updated NACH profile of your default sponsor bank. If you are using agent public forms and you have multiple NACH utility codes, the form allows you to select one.

  Note : If you have multiple nach_profiles and you do not explicitly pass one during source creation, the system will automatically pick the latest NACH profile created with the same creditor_agent_code and creditor_utility_code as a default.

If you're changing your sponsor bank, be sure to use the NACH profile of your new sponsor bank, and be sure to withdraw pending sources created with the NACH profile of your previous sponsor bank.

NACH profile usage in ACH debit transactions

You cannot create an ACH Debit if the NACH profile has no creditor bank account mapped in LotusPay. This means you're using our software only for registering mandates, and you can process your ACH Debit transactions directly with your sponsor bank. To create ACH debits in LotusPay, contact LotusPay Support to ask us to add your creditor bank account to this NACH profile (provided that you've already linked this creditor bank account in your sponsor bank).

By default, an ACH Debit transaction is created using its mandate's NACH profile. You can create the ACH Debit on a different NACH profile provided that it has a creditor bank account mapped. This is useful when you want to route debits to different sponsor banks and/or different creditor bank accounts.

• In LotusPay API, you can optionally specify the NACH profile on which to create the ACH debit. Simply add an input argument 'nach_profile' and enter the ID of the NACH profile.

• In LotusPay imports, you can optionally specify the NACH profile on which to create the ACH debit. Simply add a column 'nach_profile' and enter the ID of the NACH profile.

• In LotusPay forms, you cannot specify the NACH profile. The ACH debit automatically takes the mandate's NACH profile.

There are prerequisites for using an alternative NACH profile for an ACH debit transaction:

1. The NACH profile must be in the same merchant account, and it must be active.

2. The NACH profile must contain a creditor bank account.

3. The NACH profile utility code must match the mandate's utility code.

4. The NACH profile sponsor bank must recognise the mandate UMRN and data. Most sponsor banks validate debit inputs against mandate data. What this means is: If this is the original sponsor bank where you registered the mandate then they will recognise the UMRN, but if this is a different sponsor bank then you need to ask the bank to first import the mandate data.