Skip to main content
Available in🇮🇳 India
UPI Collect Flow DeprecatedAccording to NPCI guidelines, the UPI Collect flow is being deprecated for new UPI mandate registrations effective 28 February 2026.
  • Customers can no longer register UPI mandates by manually entering VPA/UPI id/mobile numbers.
  • Subsequent debits for existing mandates created via UPI Collect will continue to be executed without change.
ExemptionsUPI Collect will continue to be supported for:
  • MCC 6012 & 6211 (IPO and secondary market transactions).
  • iOS mobile app and mobile web transactions.
  • UPI Mandates (execute/modify/revoke operations only).
  • eRupi vouchers.
  • PACB businesses (cross-border/international payments).
Action Required
  • If you are a new Razorpay user, use UPI Intent.
  • If you are an existing Razorpay user not covered by exemptions, you must remove the UPI Collect flow parameters from your Create Authorisation Payment API request and migrate to UPI Intent or UPI QR code to continue accepting UPI mandate registrations. For detailed migration steps, refer to the migration documentation.
You can create an authorisation transaction using the Razorpay APIs or Registration Link.

1.1 Using Razorpay APIs

You can create an authorisation transaction with the UPI Collect payment method using the following APIs:
Razorpay links recurring tokens to customers using a unique identifier generated through the Customer API.You can create customers with basic information such as email and contact and use them for various Razorpay offerings. The following endpoint creates a customer.POST /customers
string
The name of the customer. For example, Gaurav Kumar.
string
The email address of the customer. For example, gaurav.kumar@example.com.
string
The phone number of the customer. For example, 9876543210.
string
The request throws an exception by default if a customer with the exact details already exists. You can pass an additional parameter fail_existing to get the existing customer’s details in the response. Possible values:
  • 1 (default): If a customer with the same details already exists, throws an error.
  • 0: If a customer with the same details already exists, fetches details of the existing customer.
object
Key-value pair that can be used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”.
Use the Orders API to create a unique Razorpay order_id that is associated with the authorisation transaction. The following endpoint creates an order.POST /orders
integer
required
Amount, in paise.
string
required
The 3-letter ISO currency code for the payment. Currently, we only support INR.
string
required
The unique identifier of the customer. For example, cust_4xbQrmEoA5WJ01.
string
required
Payment method for the authorisation transaction. Here, the value should be upi.
string
Unique identifier for the order entered by you. For example, Receipt No. 1. This parameter should be mapped to the order_id sent by Razorpay.
string
A description of the mandate that will be displayed to the customer in their UPI app. This helps the customer understand what they are subscribing to. Keep it under 50 characters and avoid special characters. For example, Monthly Pro subscription.
object
Key-value pair that can be used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”.
object
Details related to the authorization such as max amount, frequency and expiry information.
integer
required
The maximum amount that can be debited in a single charge.For other categories and MCCs, the minimum value is 100 (₹1) and maximum value is 9999900 (₹99,999).
Best PracticesSet the max_amount as close to the actual debit amount as possible. For example, if the expected debit amount is ₹99-₹299, setting the max_amount to ₹5,000 may cause the customer to drop off due to trust issues. A realistic max_amount builds customer trust while allowing flexibility for variable debits.
integer
required
The Unix timestamp that indicates when the authorisation transaction must expire. The default value is 10 years and the maximum value allowed is 30 years.
string
required
The frequency at which you can charge your customer. Possible values:
  • daily
  • weekly
  • fortnightly
  • bimonthly
  • monthly
  • quarterly
  • half_yearly
  • yearly
  • as_presented
object
required
Details of the bank account of the customer.
integer
required
The bank account number of the customer. For example, 123456789012345.
string
required
The name of the bank account holder.
string
required
The IFSC of the bank. For example, HDFC0000053.
Use the below endpoint to validate the customer’s UPI ID.POST /payments/validate/vpa
Request Parameters
string
required
The UPI ID you want to validate. For example, gauravkumar@exampleupi.
Once an order is created, your next step is to create a payment. Use the below endpoint to create a payment with payment method upi.POST /payments/create/upi
integer
required
The amount associated with the payment in smallest unit of the supported currency. For example, 2000 means ₹20. Must match the amount in Step 1.1.2.: Create an Order.
string
required
The 3-letter ISO currency code for the payment. Currently, we only support INR.
string
required
The unique identifier of the order created in Step 1.1.2.: Create an Order.
string
required
The customer’s email address. For example, gaurav.kumar@example.com.
string
required
The customer’s contact number. For example, 9123456780.
string
required
Unique identifier of the customer, obtained from the response of Step 1.1.1.: Create an Customer.
string
required
Possible values:
  • 1: Recurring payment is enabled.
  • preferred: Use this when you want to support recurring payments and one-time payment in the same flow.
string
required
The payment method selected by the customer. Here, the value must be upi.
object
Details of the expiry of the UPI link
string
required
Specify the type of the UPI payment flow.
Possible values are:
  • collect (default)
  • intent
string
required
VPA of the customer where the collect request will be sent.
integer
required
Period of time (in minutes) after which the link will expire. The default value is 5.
string
required
Client’s browser IP address. For example, 117.217.74.98.
string
required
Value of referer header passed by the client’s browser. For example, https://example.com/
string
required
Value of user_agent header passed by the client’s browser.
For example, Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.130 Safari/537.36
string
Descriptive text of the payment.
boolean
Specifies if the VPA should be stored as a token. Possible values:
  • true: Saves the VPA details.
  • false(default): Does not save the VPA details.
object
Key-value pairs that can hold additional information about the payment.
Refer to the Notes section of the API Reference Guide.
Response ParametersIf the payment request is valid, the response contains the following fields. Refer to the UPI Collect Flow document for more details.razorpay_payment_id : string Unique reference for the payment created. For example, pay_EAm09NKReXi2e0.
Registration Links are an alternate way of creating an authorisation transaction. If you create a registration link, you need not create a customer or an order. When you create a registration link, an invoice is automatically issued to the customer. The customer can use the invoice to make the Authorisation Payment. Know how to create Registration Links using the Dashboard.
Handy TipsYou can use webhooks to get notifications about successful payments against a registration link. Know more about Webhooks.
A registration link must always have the amount (in Paise) that the customer will be charged when making the authorisation payment. For UPI, the amount must be a minimum of ₹1. The following endpoint creates a registration link. POST /subscription_registration/auth_links

Request Parameters

object
Details of the customer to whom the registration link is sent.
string
required
Customer’s name.
string
required
Customer’s email address.
integer
required
Customer’s contact number.
string
required
In this case, the value is link.
integer
required
The payment amount in the smallest currency sub-unit.
string
required
The 3-letter ISO currency code for the payment.
string
required
A description that appears on the hosted page.
object
Details of the authorisation transaction.
string
required
The payment method used to make authorisation transaction. Here, it is card.
integer
required
Use to set the maximum amount (in paise) per debit request.For other categories and MCCs, the minimum value is 100 (₹1) and maximum value is 9999900 (₹99,999).
integer
The Unix timestamp till when you can use the token to charge the customer subsequent payments. The default value is 10 years and the maximum value allowed is 30 years.
string
required
The frequency at which you can charge your customer. Possible values:
  • daily
  • weekly
  • fortnightly
  • bimonthly
  • monthly
  • quarterly
  • half_yearly
  • yearly
  • as_presented
object
required
Details of the bank account of the customer.
integer
required
The bank account number of the customer. For example, 123456789012345.
string
required
The name of the bank account holder.
string
required
The IFSC of the bank. For example, HDFC0000053.
boolean
Indicates if SMS notifications are to be sent by Razorpay. Possible values:
  • true (default): Notifications are sent by Razorpay .
  • false: Notifications are not sent by Razorpay.
boolean
Indicates if email notifications are to be sent by Razorpay. Possible values:
  • true (default): Notifications are sent by Razorpay .
  • false: Notifications are not sent by Razorpay.
integer
The Unix timestamp indicates the expiry of the registration link.
string
A unique identifier entered by you for the order. For example, Receipt No. 1. You should map this parameter to the order_id sent by Razorpay.
object
This is a key-value pair that is used to store additional information about the entity. Maximum 15 key-value pairs, 256 characters (maximum) each. For example, "note_key": "Beam me up Scotty”.

1.2.2. Send/Resend Notifications

The following endpoint sends/resends notifications with the short URL to the customer: POST /invoices/:id/notify_by/:medium
Response

Path Parameters

string
required
The unique identifier of the invoice linked to the registration link for which you want to send the notification. For example, inv_1Aa00000000001.
string
required
Determines through which medium you want to resend the notification. Possible values:
  • sms
  • email
The following endpoint cancels a registration link. POST /invoices/:id/cancel
Handy TipsYou can only cancel registration link in the issued state.
Response

Path Parameter

string
required
The unique identifier for the invoice linked to the registration link that you want to cancel. For example, inv_1Aa00000000001.
Last modified on November 19, 2026