All Categories Web Documentation Integration - Admin

Integration - Admin

DIGIO - NACH


With the integration of the NACH APIs, you can automate the payment frequency. The amount will be automatically debited at a particular frequency from the Customer account after completion of the Mandate through API.

Here you can integrate all the APIs provided by DIGIO so that the mandate can be created digitally, which will reduce the cost of paper, and time, and also the payment will be done smoothly. The recurring payment cycle will be initiated with the help of NACH API.

Glossary


  1. Penny Drop API - This will verify the customer's bank account number and IFSC Code this API will validate the Bank account.

  2. Fuzzy API - This is used to verify the customer name, in the bank account

  3. Mandate - It indicates an authorized authority to handle and verify the processes. Mandate mode might vary for each bank. This is verified using the IFSC code or by Destination Bank ID.

  4. API Mandate - This helps to create mandate by verifying the debit card and net banking details.

  5. eSign Mandate - This mandate helps to verify the customer using Aadhaar. Here two methods can be used, OTP or Biometric.

  6. Physical NACH Mandate - Here a physical document will be used as a mandate, which will be scanned and uploaded for further verification.

  7. UPI Mandate - This mandate helps to verify customer using UPI.

Enable Digio API in Toolyt


Step 1: Click on 'Admin Configuration' from the profile tab.

Step 2: Click on 'Integration' which is under 'Apps and Automation' category.

image.png

Step 3: Select (tick) 'Digio'.

Step 4: Once enabled click on the 'setting' icon in Digio.

image.png

Step 5: Fill in the digio credentials (client id will be available in the digio dashboard) and click on 'save' button.

image.png

Step 6: Now click on 'service' tab and enable the Digio services based on your use case and click on 'update' button.

image.png

Configuring NACH


Step 1: Click on 'Admin Configuration' from the profile tab.

Step 2: Click on 'Add-Ons' which is under 'Apps and Automation' category.

image.png

Step 3: Select (tick) 'NACH' and click on 'settings' icon.

image.png

Step 4.1: Select the 'Management Category' from the dropdown, so that purpose for using digio can be set. In this case we are selecting 'Loan installment payment'.

image.png

Step 4.2: Now select the 'Frequency' by which you want debit the payment.

image.png

Step 4.3: The 'Corporate config id', corporate config id upi', corporate account number' and 'corporate account number upi' will be available in the digio dashboard.

image.png

Step 4.4: Now select the mandates that needs to be enabled. For ex: API mandate, eSign mandate, UPI mandate, Physical mandate and click on 'Save' button.

image.png

Setting up NACH in forms


Here we are going to set up a form where the NACH element must be enabled so that payment collection could be processed. Here we will learn to map all every element in NACH to the required form fields.

Since we are going to discuss about forms, you can click here to read more about form module.

Note: NACH will only be available in single entry forms.

Step 1: Click on 'Admin Configuration' from the profile tab.

Step 2: Click on 'Forms' under the 'Manage' category.

image.png

Step 3: Either create a form by clicking on 'manage' or select an existing form where NACH must be included.

Step 4: Click on 'Manage form properties' icon near to the form.

image.png

Step 5: Now click on 'Elements' then drag and drop 'NACH' to 'Default elements'.

image.png

NACH element properties


This is in follow up with the NACH element which we drag and drop in forms. Here we shall discuss in detail about each properties. There are basically four properties, they are Access Restriction, Element settings and Delete.

  1. Access Restriction

    This helps you to set up restriction on elements for different designations based on the stages. Here you can opt whether the element must remain hidden or visible.

    Step 1: Click on the 'eye' icon image.png near to the element.

    Step 2: Select the 'designation' and 'stage' from the dropdown.

    Step 3: Select whether to 'view or hide' the element in that stage.

    Step 4: Click on 'save' button.

  2. Element settings

    This setting helps you to map NACH elements to different form elements. Mapping is a very crucial step in NACH, without proper mapping NACH button will not be shown in the form from (manager/user view) or the required values won't be shown, thereby the trigger cannot be initiated.

    Step 1: Click on the 'settings' icon near to the element.

    Step 2: Under the 'details' tab, enter the name for the element.

    Step 3: Under the 'labels' tab, you can set the name based on your regional language.

    For mapping, follow below mentioned steps:

    Step 4.1: Select the 'NACH fields' from the dropdown to whom the form field element must be linked.

    image.png

    Step 4.2: Under the 'select form' dropdown either choose 'select from lead/customer' profile' or choose 'select form forms'.

    image.png

    Step 4.2.1: If 'select from lead/customer profile' is selected choose the field element

    image.png

    Step 4.2.2: If select from forms' is selected choose the respective form and the form field element.

    image.png

    Step 5: Now click on 'save' button.

    image.png

Note: When the NACH fields are successfully mapped, a green tick comes near to the field.

image.png

Note: You can verify the NACH fields linked just selecting the respective NACH field it from the dropdown.

image.png

NACH Fields


There are 14 field elements in NACH. Each elements serves a strong purpose for mandate creation.

  • Customer Identifier: This NACH parameter is used to send the URL for NACH creation to the customer using a mail or phone number.

  • Maximum Amount: This indicates the maximum amount that can be debited in a single transaction.

  • First Collection Date: This indicates the date from which the mandate needs to be registered.

  • Final Collection Date: This indicates the final date of the mandate. Once it breaches the mandate will be expired, hence transaction cannot be fulfilled.

  • Customer Name: Name of the customer on who's behalf mandate will be created.

  • Customer Account Number: Account number on who's name the mandate is created.

  • Destination Bank ID: This is the IFSC code of destination bank. This helps in verifying which all mandates exist for the destination bank.

  • Destination Bank Name

  • Customer Account Type: This indicates the customer's account type such as savings, current etc.

  • Customer Ref Number: It is unique customer number maintained by the corporate. It can be Toolyt ID, Loan account number, customer number etc.

  • Scheme Ref Number: This additional customer number maintained by the corporates.

  • Debit Amount: The amount which needs to be debited from the customer's account in a single transaction.

  • Debit Settlement Date: The date on which the amount needs to be debited form the customers account in during each transaction.

  • Payment Count: Number of times the payment needs to be done.

Was this article helpful?