Overview

Decentro helps platforms collect payments periodically, be it daily, weekly, monthly, or even yearly, to reduce dependency on human intervention through the ENACH stack. It also helps platforms mitigate risks due to a payer defaulting on a payment, etc., and reduce dependency on the payer for transferring or approving funds transfer for each transaction.

Decentro powers both capabilities on its own RBI-approved PA Escrow account and directly on the platform's bank account as a technology partner.

Decentro's mandates stack powers the use cases below for platforms to leverage.

• EMI repayments: This allows lenders like LSPs, NBFCs, SFBs, and even banks to leverage the stack to collect EMIs from borrowers through the ENACH stack.
• Insurance premiums: This allows platforms like insurtechs, life, and general insurers to leverage the stack to collect premiums from borrowers through the ENACH stack.
• Investment use cases: This allows investment platforms like Fintechs, RIAs, and even AMCs to leverage the stack to collect EMIs from borrowers through the ENACH stack.
• Subscription use-cases: this allows platforms, like SME aggregators, B2B marketplace platforms, ECOM, and even offline platforms, to leverage the stack to collect EMIs from borrowers through the ENACH stack.

Glossary of Terms

Below are the commonly used terms/words in the context of Decentro's ENACH stack.

Flow

Decentro's mandates stack has largely 3 legs or steps in the flow.

• Mandate Registration: This step involves the payer setting up a mandate on the ENACH or UPI stack and consenting to the mandate terms like amount, tenure, frequency, etc. Note that this doesn't debit the funds from the payer's account.
• Pre-debit notification: This step involves the payee/platform letting Decentro and the payer know the presentation date and amount well before the debit date. Note that this doesn't debit the funds from the payer's account.
• Mandate Execution: This step involves the payee/platform letting Decentro know the amount to be debited on a specific date from the registered account. At this stage, the payer's bank account is debited for the amount presented for execution.

Note: ENACH supports registration and presentation up to 1,00,00,000 INR across frequencies.

📘

Note

Please note that not all commercial banks support API-based E-mandates. All the supported banks are available in the Supported Banks API. The platform can use this API to check if the customer's bank supports ENACH.

📘

Coming Soon

Aadhaar based E-mandates

Prerequisites

Below are the prerequisites expected of the platform before going live.

• The platform or the entity under the platform has a utility code registered with NPCI.
• If the platform or the entity under the platform lacks a utility code, Decentro facilitates its creation.
• The platform configures the required endpoints at its end to receive the callbacks from Decentro for registration and/or execution.

Journey

Below is the flow recommended by Decentro for leveraging up the ENACH stack.

• Decentro helps the platform receive its utility code by liaising with NPCI and its sponsor bank. This is an offline process, and Decentro configures it at its end.
• The platform shares endpoints that can be configured at Decentro's end to trigger callbacks for registration and presentation. This can be shared with Decentro at [email protected].
• The platform asks for the payer's bank account on its page/app and checks if it is supported on ENACH using the ENACH Supported Banks API.
• Alternatively, the platform can call Decentro's Mandate Registration API directly, and Decentro will respond if ENACH supports the bank.
• The platform initiates the registration flow by passing the payer's bank account details using the Mandate Registration API.
• The platform shares the link shared by Decentro with the payer on its app or website, where the payer is redirected to NPCI and completes the mandate request.
• After completing the mandate registration process, the payer is redirected to the URL the platform shares when onboarding.
• Decentro triggers the ENACH registration Callback to the platform's endpoint with the registration status once the payer has completed the steps.
• The platform can also check the registration status using the Mandate Status API using the Decentro transaction ID received from the registration API.
• The platform initiates the pre-debit notification to the payer using standard communication modes, such as SMS and/or Email, to ensure compliance with the guidelines.
• The platform initiates the debit request by triggering the Mandate Execution API, which will be passed to the destination bank for actual debit.
• The actual debit happens from the payer's bank account if the account has sufficient balance and is active or if there are no issues with it.
• Decentro triggers the ENACH Execution Callback API to the platform's configured endpoint once it receives the presentation status from its bank partner.
• The platform can also check the status of the mandate's presentation using the Get Mandate Execution Status API.

Authorization Modes

Below are the authorization modes a payer can use to approve a mandate registration request.

• Netbanking: The payer must have their netbanking credentials handy at registration. In this flow, the payer is redirected to their bank's page to enter the netbanking credentials and the OTP to complete the authorization flow.
• Debit Card Native: The payer must have their debit card details handy at registration. In this flow, the payer is redirected to their bank's page to enter the debit card details, such as the number, PIN, Expiry, and OTP, to complete the authorization flow.
• Debit Card on NPCI: The payer must have their debit card details handy at registration. In this flow, the payer enters the debit card details like number, PIN, Expiry, and OTP to complete the authorization flow on the NPCI page.
• Aadhaar: The payer must have their Aadhaar details handy at registration. In this flow, the payer enters the Aadhaar number & validates the OTP. The second OTP will be sent via bank to register the mandate.

The banks that support each of the flows are covered in the Supported Banks section.

Note: The payer's bank handles and triggers the OTP and other bank-specific authorization. Decentro or its bank partners don't have any control over the same.

Settlement Flow

Decentro settles the funds received from its bank partner (Sponsor Bank) as per the agreed business proposal. From a settlement perspective, Decentro has the capabilities below.

• Settlement to a single bank account of the platform/merchant
• Settlement to multiple bank accounts of the platform/merchants basis pre-defined logic

Transaction Limits

Decentro's ENACH platform supports transaction limits for registration/presentation, as below.

• Debit Card based non-security mandate: 1 CR
• Netbanking-based non-security mandate: 1 CR
• Aadhaar-based non-security mandate: 1 CR
• General security mandate: 1 CR

Supported Banks

The ENACH Supported Banks API can fetch the updated list of Banks and Methods NPCI supports for E-NACH. Using this API, you can check if your customer's bank supports API-based E-mandates.

Below are the banks and the authorization modes they support.

A detailed list of banks on the ENACH platform and the modes they support can be found here.

If you have any questions, please refer to ENACH FAQs. If you have any additional queries, please email us at [email protected].

Decentro's ENACH-related API reference can be found here.