Overview

This API allows the platform to initiate an ENACH-based registration request. The payer can then authorize the request using one of the supported modes.

• Debit Card
• Net banking

📘

Ensure to use only staging credentials & Simulation data only.

Flow

Below is the flow for using this API.

• The platform can check if the bank is supported using the Supported Banks API.
• The platform captures the mandate details like amount, frequency, timeframe, etc.
• The platform initiates a registration request by hitting the endpoints with the mandate details.
• Decentro validates if the destination bank supports the authorization mode (Debit Card/Netbanking).
• The platform receives a shortened link from Decentro if the request is successful.
• The platform renders the link on their asset (app/website), which is redirected to the NPCI page.
• The payer authorizes the request using the relevant details
  • Debit card-related details if authorization is Debit Card
  • Netbanking login and OTP (in some cases) if authorization is Netbanking
• Decentro triggers the registration status callback once the authorization is complete with the status to a pre-configured endpoint.
• Decentro also redirects the payer to the platform's page basis the redirection URL provided at the time of onboarding.
• The platform can alternatively check the registration status using the Mandate Registration Status API by passing the Decentro transaction ID received from this API response.

Note: If the link generated by Decentro is successfully initiated (opened), it remains valid for 15 minutes from the time of opening. If the payer uses the link after this time period, the registration will not be successful. This link can only be clicked once.

Registration Statuses

API Endpoints

Below are the API endpoints to be used by the platform basis the environments.

Request Parameters

Frequency

Below are the frequencies accepted by Decentro under the 'frequency' parameter in the request payload.

• Adhoc
• Daily
• Weekly
• Monthly
• Quarterly
• Semi-Annually
• Yearly
• Bi-Monthly

Amount Rule

Below are the values Decentro accepts under the 'amount_rule' parameter in the request payload.

• Fixed -> Amount to be debited from the user's bank account is fixed. Can not debit more or less than the specified amount.
• Max -> Amount to be debited from the user's bank account can be less than or equal to the specified amount.

Authentication Mode

Below are the values Decentro accepts under the 'authentication_mode' parameter in the request payload.

• Debit Card
• Net banking

Start & End Date

Below are the validations on the date parameters in the request payload.

• Start date: needs to be a current date or a date in the future
• End date: needs to be at least 1 day after the start date and can extend up to 40 years

Category Codes

Below are the purpose codes the platform will pass in the category_code parameter in the request payload.

Simulation Data

📘

OTP Validation

1. Enter any 6-digit random number to validate the OTP.
2. "111-111" use this 6-digit number to verify the wrong OTP scenario.

📘

Debit Card Validation

1. Enter a random 12-digit debit card number.
2. Enter a random 3-digit CVV.
3. Enter a random debit card expiry date.

Authentication Mode - Debit Card

Authentication Mode - Net Banking