Overview

This API lets the platform execute a debit request against a registered mandate for whom the pre-debit notification has been successfully initiated.

This API is an async API and the actual debit happens after the request is placed by Decentro with the bank partner.

Flow

Below is the flow for using this API.

• The platform registers a UPI-based mandate using the Create Mandate API and receives the unique decentro mandate ID in the response from Decentro and in the Get Mandate Status API or the Registration Callback.
• The platform initiates the pre-debit notification using the Pre-debit Notification API by passing the unique decentro mandate ID from Decentro.
• Decentro responds with a notification sequence ID upon successful completion of the notification.
• The platform passes the same in the request payload on the endpoints if the pre-debit notification is successful.
• Decentro triggers a Presentation Status Callback to a pre-configured endpoint once the presentation reaches a terminal stage.
• The platform can check the status of the mandate using the Mandate Presentation Status API as an alternative.

Points to Note

Decentro checks a few points before initiating the pre-debit request, most of which are fetched from the mandate registration details here.

• The debit request should be against an active mandate
• The debit request should be as per the set frequency
• The debit request should be as per the amount rule
• The debit request should be as per the set date rule
• The pre-debit notification request should be successful
• The user will receive a collect notification with expiry of 30 minutes in case presentation limit is more than the threshold limit. For most merchants, this limit is set to INR 15,000.
• The clients can retry the presentation after 1 hour from the previous presentation attempt.
• The clients can retry upto 9 times if a presentation is failed.
• This API is an async API

API Endpoints