#Recur (Recurring mandates)
PREREQUISITES
🌟 UPI mandates overview ↗#What is a recurring mandate ?
A recurring mandate is a mandate that that can be executed / debited multiple times as per the recurrence pattern configured / agreed upon during mandate creation.
#What can I do with a recurring mandate ?
Recurring mandates help merchants seamless collect money multiple times with a single setup.
- Create subscriptions for your streaming services & SAAS businesses
- Automate memberships to your physical venues with automatic payments
- Power daily savings/investment related features for your customers
#How it works
The first step to collect a payment via a recurring mandate is for the merchant to create a recurring mandate. There are 2 ways in which a recurring mandate can be created:
Intent based : Intent based mandates are always initiated by user through merchant app or by scanning a QR code.
Collect based Collect based mandates are initated by merchant by taking user's VPA as an input and creating a request.
These are the list of steps involved in collecting a payment from a customer using a recurring mandate in intent flow.
Step 1 - create a recurring mandate
- Merchant sends recurring mandate details to UPI Setu and receives a unique recurring mandate creation intent link / qr to send to their Customer
- Customer clicks recurring mandate creation intent link, chooses preferred UPI app / scans the qr on preferred UPI app and enters mPIN to initiate recurring mandate creation.
- UPI Setu triggers a webhook notification on recurring mandate creation initiation which the merchant can use to update recurring mandate status at their end.
- Once the mandate is LIVE, UPI Setu triggers another webhook notification which the merchant can use to mark mandate status as LIVE at their end.
Step 2 - send a pre debit notification
In every recurrence cycle, Merchant triggers a pre debit notification via UPI Setu 48 - 72 Hrs before debit / execution to let the Customer get notified about the upcoming debit.
No merchant intervention is needed for recurring pre debit notifications and executions if auto pre debit notification and auto execution are configured while creating a recurring mandate.
Step 3 - trigger mandate execution
- 48 - 72 Hrs after the pre debit notification is successful, Merchant triggers mandate execution via UPI Setu.
- Customer receives a collect request notification on their UPI app, clicks on the notification and enters mPIN to authorise the payment.
No merchant intervention is needed for recurring pre debit notifications and executions if auto pre debit notification and auto execution are configured while creating a recurring mandate.
Step 4 - check payment status
Merchant can use check payment status API to check payment statuses associated to the mandate
Other operations that can be performed on a recurring mandate once it is LIVE
- Updating a recurring mandate
- Revoking a recurring mandate
- Pausing a recurring mandate
- Unpausing a paused recurring mandate