Mandates

Recurring collections facilitate collections from customers, individuals, or businesses at pre-defined or regular intervals. These are typically called Mandates.

What are the use cases of Recurring Collections?

Some use cases of recurring collections are.

• EMIs: Lenders collecting repayments against a loan/credit line
• Premiums: Insurers or businesses collecting payments toward premium
• Subscriptions: Platforms collecting regular payments towards services
• Savings: Platforms facilitating savings from customers at regular intervals
• Investments: Platforms facilitating investments into various assets

How Decentro Powers Recurring Collections?

Decentro powers recurring collections through 2 key modules.

• ENACH: This is the NPCI-powered bank account-based mandate platform. The NACH stack is designed for larger ticket sizes and higher flexibility.
• UPI Auto-pay: This is the NPCI-powered UPI-based platform. The UPI stack is designed for smaller ticket sizes and seamless registration.

ENACH

ENACH is a digital mandate platform built by NPCI on the NACH framework designed to handle recurring payments like EMIs, payables, premiums, etc.

ENACH has 2 phases.

• Registration: this registers the mandate using the debit card or netbanking details of the customer
• Execution: this debits the amount from the customer's bank account against which the mandate is registered.

This set of APIs will help you enable auto collections on configured frequency from your consumers.

Note: ENACH supports registration and presentation up to 10,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

Supported Banks

This API can be used to fetch the updated list of Banks and Methods supported by NPCI for E-NACH. Using this API, you can check if your customer's bank supports API-based E-mandates.

Here is the list of supported banks and their specific bank code.

Link to Supported Banks

Mandate Registration

This API helps to enable a path (pageLink) so that your consumer can register a recurring payment with Debit Card or Netbanking as a mode of payment. The response of this API is a link that will redirect the customer to NPCI.

Link to Mandate Registration

Mandate Registration Callback

Once the customer approves or rejects the mandate, Decentro triggers a callback to a pre-configured endpoint with the mandate details.

Link to Enach registration Callback

Mandate Status

This API is used to check the real-time status of the mandate registration request initiated with Decentro.

Link to Mandate Status

Mandate Execution

This API will allow you to initiate an auto-debit for a particular mandate referencing the mandate ID from the time of registration.

The mandate needs to be registered before being presented. Else, Decentro rejects the mandate for execution.

Link to Mandate Execution

Mandate Execution Callback

Once a debit is triggered against an active mandate, Decentro triggers a callback to a pre-configured endpoint with the execution details in case of Success or Failure.

Link to Enach Execution Callback

UPI AutoPay

UPI Auto-pay is a digital mandate platform built by NPCI on the UPI framework designed to handle recurring payments like EMIs, payables, premiums, subscriptions, etc.

This set of APIs will help you enable auto collections on configured frequency from your customers.

UPI Autopay has 2 phases.

• Registration: this registers the mandate using a VPA handle of the customer by authorizing through their regular UPI PIN.
• Execution: this debits the amount from the customer's bank account linked to the VPA against which the mandate is registered.

Mandate Registration

This API is used to register a UPI based mandate by passing the VPA. Once successful, the customer needs to go to the PSP app and approve the same using the PIN.

Intent flow - This API also supports intent-based flow for mandate registration. In this flow, instead of switching between the PSP app and the platform's application, the user is redirected directly to the PSP app with the help of deep links. This helps in reducing user drop-off at the platform's end and provides a frictionless auto-payment setup on UPI Autopay. To use this flow, pass generate_mandate_uri = 1 in the request body.

Link to Create Mandate

Registration Callback

Once the customer approves or rejects the mandate, Decentro triggers a callback to a pre-configured endpoint with the mandate details.

Link to UPI Auto-Pay Registration Callback

Mandate Status

This API can be used to get the registration status of the mandate. This is a fallback option if in case the platform hasn't subscribed to the callback.

Link to Get Mandate Status

Pre-Debit Notification

This API is used to trigger a pre-debit notification to a mandate already registered. This needs to be triggered at least 48 hours before the actual debit as per NPCI guidelines.

Link to Pre Debit Notification

Mandate Execution

This API will allow you to initiate an auto-debit for a particular mandate referencing the mandate ID from the time of registration.

If the execution amount is greater than 15,000 INR, the customer will need to enter their UPI PIN on the PSP app to approve the request.

Link to Execute Mandate

Mandate Execution Status

This API can be used to get the Execution status of the mandate. This is a fallback option in case the platform hasn't subscribed to the Execution callback.

Link to Get Mandate Execution Status

Execution Callback

Once a debit is triggered against an active mandate, Decentro triggers a callback to a pre-configured endpoint with the execution details in case of Success or Failure.

Link to UPI Auto-Pay Execution Callback

📘

Note

Please note that most of the leading banks which have UPI enabled support UPI auto-pay. Also, all the leading PSPs like PhonePe, Paytm, GPay, and Amazon Pay now support UPI auto-pay as well.