Available in🇮🇳 India
UPI Autopay allows businesses to set up recurring mandates on a customer’s UPI id, enabling automatic debits at a defined frequency without requiring the customer to approve each payment manually. This is ideal for subscriptions, loan repayments, SIP investments and other recurring payment use cases.
Recommended IntegrationWe strongly recommend using the UPI Intent flow for mandate registration. Intent provides a seamless native app experience where customers are redirected to their preferred UPI app to approve the mandate. For iOS users, you may continue to use the UPI Collect flow as a fallback. Some merchant categories are also exempted from the Collect deprecation. For the limits by merchant category, refer to UPI Transaction Limits.
Use Cases
Razorpay supports UPI Autopay across a range of industries. Subscription and recurring-service businesses (OTT, SaaS, meal delivery) set up monthly or custom-frequency mandates. Lending businesses collect EMI repayments, with irrevocable mandates available (see Industry Specific Autopay). Mutual fund distributors and investment platforms collect SIPs with extended mandate limits and AFA exemptions (see Mandate Limits and AFA). Insurance companies collect premiums on a monthly, quarterly or yearly basis.How UPI Autopay Is Set Up
UPI Autopay works in three stages:- Mandate Registration: This is the journey where the customer sets up the subscription for the first time. At Razorpay, it involves three steps:
- Create a Customer - You receive a
customer_idthat uniquely identifies the customer. - Create an Order - You send the
customer_idalong with token details (amount, frequency, expiry) to give context to the token. You receive anorder_id. - Create an Authorisation Payment - You send the
order_idandcustomer_id. This performs the first debit authorisation on the customer. If the first debit fails, the registration fails. On success, you receive apayment_id. You receive thetoken_idthrough thetoken.confirmedwebhook or by using the Fetch Token APIs, and use it for all future debits.
- Create a Customer - You receive a
- Subsequent Debits: On the scheduled dates, you create an order and then create a payment using the
token_id. The debit runs against the registered token without requiring customer intervention (subject to AFA limits). - Token Management: You can fetch, cancel or delete tokens through Razorpay APIs at any point during the token lifecycle.
Mandate Limits and AFA
UPI Autopay mandates are subject to limits defined by NPCI. These limits vary by industry category (MCC). Additional Factor of Authentication (AFA) is required by the RBI for subsequent debits above certain thresholds. When AFA is required, the customer receives a notification on their UPI app and must enter their UPI PIN to approve the payment. Refer to the limits by MCC table for the maximum mandate amount and the AFA-free limit for each MCC. The minimum mandate registration amount across all categories is ₹1.Handy Tips
- For regular industries, any subsequent debit above ₹15,000 requires the customer to approve the transaction via UPI PIN.
- For lending and investment categories (MCCs 6211, 6300, 7322, 6529, 5960), AFA is not required for debits up to ₹1,00,000. This exemption helps investment platforms process SIP amounts and lenders process EMIs without requiring customer intervention.
- If the subsequent debit amount exceeds the mandate’s
max_amount, the payment will fail.
Industry Specific Autopay
Razorpay supports customised Autopay configurations for specific industries. These features are available on request.- Third-Party Validation (TPV)
- Irrevocable Mandates
For investment and lending merchants, Razorpay supports Third-Party Validation (TPV) on UPI Autopay. TPV ensures that the customer’s bank account is validated against a pre-approved list before the mandate is registered. This adds a layer of security by confirming that the payment source matches the expected account.Know more about UPI Autopay with TPV.
Integration Steps
To integrate UPI Autopay using the S2S (server-to-server) flow, follow these steps:- Initiate Mandate Registration - Create a customer, create an order with mandate details and create an authorisation payment.
- Fetch and Manage Tokens - Retrieve the
token_idby fetching it or waiting for thetoken.confirmedwebhook, check token states, and cancel or delete tokens as needed. - Create Subsequent Payments - Create orders and charge the customer on a recurring basis using the
token_id. - Webhooks - Set up webhook listeners to receive real-time notifications for mandate and payment events. Integrating with webhooks is strongly recommended as it is the most efficient method for tracking payment and token status changes.