Corporates can avail three different ways to registrate mandates. Although all the three processes are fully digital in nature and serve offline use-cases, they offer different turn around times. Sponsor bank as reference below is the corporate or payee’s bank (or financial institution). UMRN stands for Unique Mandate Reference Number, it is generated immediately after the mandate is registered and is used to track multiple mandate details for each customer.
| Steps | 3 Mandate Variants | ||
|---|---|---|---|
| API eNACH (Debit Card /Net Banking/Aadhaar) | PHYSICAL NACH | eSIGN eNACH | |
| 1 - Sponsor bank profile creation | Via Digio Dashboard (One time activity) | Via Digio Dashboard (One time activity) | Via Digio Dashboard (One time activity) |
| 2 - Mandate Request Creation | API/Dashboard/CSV Trigger SMS or Email to user or use Digio SDKs for authentication within your application | API/Dashboard/CSV Generate pre filled form or send user a link to download | API/Dashboard/CSV Trigger SMS or Email to user or use Digio SDKs for authentication within your application |
| 3 - User Authentication | Digio screens triggered via SDK or SMS/EMAIL Link. Users are taken to the Destination bank page via NPCI and authenticated with Debit Card or Netbanking. NPCI informs the sponsor bank at the end of the day or next day. Corporate-> NPCI-> DestinationBank | Signed Image Submission - API or Dashboard. If a link is sent to the user, signed image is uploaded on the link itself. Signed Images with NPCI XMLs are sent to the sponsor bank instantly or at a window based on a defined pattern with sponsor bank. Bank submits the ZIP (XMLs & Images) to NPCI when NPCI windows are open. Corporate-> SponsorBank-> NPCI-> DestinationBank | Digio screens triggered via SDK or SMS/EMAIL Link. User performs Aadhaar eSign Authentication ( on ESP webpage). eSigned XMLs are sent to the sponsor bank instantly or at a window based on a defined pattern with the sponsor bank. Bank submits the XMLs to NPCI when NPCI window is open. Corporate-> SponsorBank-> NPCI-> DestinationBank |
| 4- UMRN & NPCI Acknowledgement (ACK) | Generated by NPCI Instantly in authentication response. Note - it doesn’t mean final registration. NPCI->Corporate | Generated by NPCI on image receipt. Received by corporate generally by Next working day in XML/CSV format NPCI-> SponsorBank-> Corporate | Generated by NPCI on eSigned XML receipt. Received by corporate generally by Next working day in XML/CSV format NPCI->Sponsor Bank->Corporate |
| 5 - Final Registration (RES) | By Next working day NPCI-> SponsorBank-> Corporate | 7 working days DestinationBank->NPCI->SponsorBank->Corporate | 3-7 days DestinationBank-> NPCI-> SponsorBank-> Corporate |
Mandate Request Creation is common for all mandate variants. This step is required for passing Mandate meta information to Digio like - Amount, Frequency, Customer details etc. before user authentication. This step generates a unique NACH id starting with “ENA” for each mandate instance.
There are 3 ways to create Mandate Request At Digio end:
| 1 | Digio Dashboard | Create a mandate on need basis. Recommended when volumes are minor and deep integration is not required. |
| 2 | CSV Upload | Create bulk requests. Recommended when volumes are decent and deep integration is not required. |
| 3 | API Integration | Automated way with deep integration with your systems. Most recommended. |