1. Initiate Mandate Registration

UPI Collect Flow Deprecated

According to NPCI guidelines, the UPI Collect flow is being deprecated for new UPI Autopay 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.

Exemptions

UPI 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 Authorization Payment API request and migrate to UPI Intent or UPI QR code to continue accepting UPI Autopay registrations. For detailed migration steps, refer to the
migration documentation
.

You can initiate mandate registration using the

Razorpay APIs

or a

Registration Link

The following state diagram depicts the mandate registration flow and token lifecycle:

UPI Autopay mandate registration and token state flow

1.1 Using Razorpay APIs

You can use APIs to set up mandate registrations on UPI Autopay inside the customer's checkout journey. To do this, you need to create customer identifiers and then initiate the checkout process. Here are the steps:

Create a Customer
- This allows Razorpay to uniquely identify the customer and store UPI Autopay tokens against the customer ID.
Create an Order
- Send the token details required to set up UPI Autopay on the customer ID.
Create an Authorisation Payment
- Initialise the authorisation journey where the actual mandate registration happens.

1.1.1 Create a Customer

Razorpay links recurring tokens to customers using a unique identifier generated through the Customer API. You can create customers with basic details such as email and contact and use them for various Razorpay offerings. Know more about

Customers

The following endpoint creates a customer.

POST

/customers

curl -u [YOUR_KEY_ID]:[YOUR_KEY_SECRET] \
-X POST https://api.razorpay.com/v1/customers \
-H "Content-Type: application/json" \
-d '{
  "name": "Gaurav Kumar",
  "email": "gaurav.kumar@example.com",
  "contact": "9123456780",
  "notes":{
    "note_key_1": "September",
    "note_key_2": "Make it so."
  }
}'

Once you create a customer, you can create an order for the mandate registration.

Request Parameters

name

mandatory

string The customer's name. For example, Gaurav Kumar.

optional

string The customer's email address. For example, gaurav.kumar@example.com.

contact

optional

string The customer's phone number. For example, 9876543210.

notes

optional

object 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.1.2 Create an Order

Use the

Orders API

to create a unique Razorpay Curlec order_id that is associated with the mandate registration. The following endpoint creates an order.

POST

/orders

Sample Code

curl -u <YOUR_KEY_ID>:<YOUR_KEY_SECRET> \
-X POST https://api.razorpay.com/v1/orders \
-H "Content-Type: application/json" \
-d '{
  "amount": 100,
  "currency": "INR",
  "customer_id": "cust_4xbQrmEoA5WJ01",
  "method": "upi",
  "token": {
    "max_amount": 200000,
    "expire_at": 2709971120,
    "frequency": "monthly"
  },
  "receipt": "Receipt No. 1",
  "notes": {
    "notes_key_1": "Tea, Earl Grey, Hot",
    "notes_key_2": "Tea, Earl Grey… decaf."
  }
}'

Handy Tips

The token.max_amount value must respect the limits defined by NPCI for your merchant category. For regular industries, the maximum is ₹99,999. For lending and investment categories (MCCs 6211, 6300, 7322, 6529, 5960), the maximum is ₹2,00,000. Refer to the

UPI Autopay overview

for the complete limits table.

Request Parameters

amount

mandatory

integer Amount, in paise.

currency

mandatory

string The 3-letter ISO currency code for the payment. Currently, we only support INR.

method

mandatory

string Payment method for the mandate registration. Here, the value should be upi.

receipt

optional

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.

notes

optional

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".

token

Details related to the mandate such as max amount, frequency and expiry information.

max_amount

optional

integer 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).

expire_at

optional

integer The Unix timestamp that indicates when the mandate must expire. Defaults to 10 years.

frequency

mandatory

string The frequency at which you can charge your customer. Possible values:

weekly
monthly
quarterly
yearly
as_presented

recurring_value

optional

integer Determines the exact date or range of dates for recurring debits. Possible values are:

1-7 for weekly frequency
1-31 for monthly frequency
1-31 for quarterly frequency
1-31 for yearly frequency and is not applicable for the as_presented frequency.

Watch Out!

If the date entered for the recurring debit is not available for a month, then the last day of the month is considered by default. For example, if the date entered is 31 and the month has only 28 days, then the date 28 is considered.

recurring_type

optional

string Determines when the recurring debit can be done. Possible values are:

on: Recurring debit happens on the exact day of every month.

Handy Tips
For creating an order with recurring_type=on, set the recurring_value parameter to the current date.
before: Recurring debit can happen any time before the specified date.
after: Recurring debit can happen any time after the specified date.

For example, if the frequency is monthly, recurring_value is 17 and recurring_type is before, recurring debit can happen between the month's 1st and 17th. Similarly, if recurring_type is after, recurring debit can only happen on or after the 17th of the month.

1.1.3 Create an Authorisation Payment

Once an order is created, your next step is to create a payment to initiate the mandate registration on the customer's UPI app. The UPI payment flow you use determines how the customer approves the mandate:

UPI Intent (recommended): The customer is redirected to their preferred UPI app (or scans a QR code on desktop) to approve the mandate. This is the default flow.
UPI Collect (deprecated): A collect request is sent to the customer's VPA (UPI ID). This flow is being deprecated for new UPI Autopay registrations effective 28 February 2026. For iOS users, you may continue to use the Collect flow as a fallback.

Use the below endpoint to create a payment with payment method upi.

POST

/payments/create/upi

Sample Code

UPI Intent

UPI Collect (Deprecated)

Before creating the collect payment, validate the customer's UPI ID using the /payments/validate/vpa endpoint.

curl -u <YOUR_KEY_ID>:<YOUR_KEY_SECRET> \
 -X POST https://api.razorpay.com/v1/payments/validate/vpa \
 -H "Content-Type: application/json" \
 -d '{
   "vpa": "gauravkumar@exampleupi"
 }'

Once the UPI ID is validated, create the authorisation payment with upi.flow set to collect.

Request Parameters

amount

mandatory

integer The amount associated with the payment in smallest unit of the supported currency. For example, 2000 means ₹20. Must match the amount in order created

previously

currency

mandatory

string The 3-letter ISO currency code for the payment. Currently, we support only INR.

order_id

mandatory

string The unique identifier of the order created in the

previous step

customer_id

mandatory

string Unique identifier of the customer, obtained from the response of

Step 1.1.1: Create a Customer

recurring

mandatory

string Determines if the payment is recurring or one-time. 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.

method

mandatory

string The payment method selected by the customer. Here, the value must be upi.

upi

object Details of the UPI payment flow.

flow

mandatory

string Specify the type of the UPI payment flow.
Possible values are:

intent (default, recommended)
collect: Deprecated effective 28 February 2026. For iOS users, you may continue to use the Collect flow as a fallback.

vpa

mandatory for

string VPA of the customer where the collect request will be sent. Applicable only to the UPI Collect flow.

expiry_time

optional

integer Period of time (in minutes) after which the collect request will expire. The default value is 5. Applicable only to the UPI Collect flow.

mandatory for

string The customer's email address. For example, gaurav.kumar@example.com.

contact

mandatory for

string The customer's contact number. For example, 9123456780.

mandatory for

string Client's browser IP address. For example, 117.217.74.98.

referer

mandatory for

string Value of referer header passed by the client's browser. For example,

https://example.com/

user_agent

mandatory for

string 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

save

optional

boolean Applicable only to the UPI Collect flow. 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.

notes

optional

json object Key-value pairs that can hold additional information about the payment.

Response Parameters

If the payment request is valid, the response contains the following fields. Refer to the

UPI Intent Flow document

or the

UPI Collect Flow document

for more details.

razorpay_payment_id

string Unique reference for the payment created. For example, pay_EAm09NKReXi2e0.

link

string Returned only for the UPI Intent flow. The UPI intent link to redirect the customer to their UPI app for mandate approval. Use this as a deeplink on mobile or convert it to a QR code for desktop.

Next Steps by Platform

For the UPI Intent flow, use the link returned in the response to take the customer to their UPI app:

Use the link returned in the response as a deeplink to redirect the customer to their preferred UPI app to complete the mandate registration.

For the UPI Collect flow, a collect request is sent to the customer's VPA. The customer must open their UPI app and approve the mandate request before it expires.

1.2 Using a Registration Link

Registration Links are an alternate way of initiating mandate registration. If you create a registration link, you need not create a customer or an order separately.

When you create a registration link, an

invoice

is automatically issued to the customer. The customer can use the invoice to complete the mandate registration.

Know how to

create Registration Links

using the Dashboard.

Handy Tips

You 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.

1.2.1 Create a Registration Link

The following endpoint creates a registration link.

POST

/subscription_registration/auth_links

Sample Code

curl -u <YOUR_KEY_ID>:<YOUR_KEY_SECRET>
-X POST https://api.razorpay.com/v1/subscription_registration/auth_links
-H "Content-Type: application/json" \
-d '{
  "customer": {
    "name": "Gaurav Kumar",
    "email": "gaurav.kumar@example.com",
    "contact": "9123456780"
  },
  "type": "link",
  "amount": "100",
  "currency": "INR",
  "description": "Registration Link for Gaurav Kumar",
  "subscription_registration": {
      "method": "upi",
      "max_amount": "500",
      "expire_at": 4102444799,
      "frequency": "monthly",
      "recurring_value": 25,
      "recurring_type": "on"
  },
  "receipt": "Receipt No. 23",
  "email_notify": true,
  "sms_notify": true,
  "expire_by": 4102444799,
  "notes":{
    "note_key 1":"Beam me up Scotty",
    "note_key 2":"Tea. Earl Gray. Hot."
  }
}'

Request Parameters

customer

object Details of the customer to whom the registration link is sent.

name

mandatory

string Customer's name.

mandatory

string Customer's email address.

contact

mandatory

integer Customer's contact number.

type

mandatory

string In this case, the value is link.

amount

mandatory

integer The payment amount in the smallest currency sub-unit.

currency

mandatory

string The 3-letter ISO currency code for the payment.

description

mandatory

string A description that appears on the hosted page.

subscription_registration

Details of the mandate registration.

method

mandatory

string The payment method used for mandate registration. Here, it is upi.

max_amount

mandatory

integer 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).

expire_at

optional

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.

frequency

mandatory

string The frequency at which you can charge your customer. Possible values:

daily
weekly
fortnightly
bimonthly
monthly
quarterly
half_yearly
yearly
as_presented

recurring_value

optional

integer Determines the exact date or range of dates for recurring debits. Possible values are:

1-7 for weekly frequency
1-31 for fortnightly frequency
1-31 for bimonthly frequency
1-31 for monthly frequency
1-31 for quarterly frequency
1-31 for half_yearly frequency
1-31 for yearly frequency and is not applicable for the as_presented frequency.

Watch Out!

recurring_type

optional

string Determines when the recurring debit can be done. Possible values are:

on: recurring debit happens on the exact day of every month.
before: recurring debit can happens any time before the specified date.
after: recurring debit can happens any time after the specified date.

sms_notify

optional

boolean Indicates if SMS notifications are to be sent by Razorpay Curlec. Possible values:

true (default): Notifications are sent by Razorpay Curlec .
false: Notifications are not sent by Razorpay Curlec.

email_notify

optional

boolean Indicates if email notifications are to be sent by Razorpay Curlec. Possible values:

true (default): Notifications are sent by Razorpay Curlec .
false: Notifications are not sent by Razorpay Curlec.

expire_by

optional

integer The Unix timestamp indicates the expiry of the registration link.

receipt

optional

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 Curlec.

notes

optional

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

Sample Code

curl -u [YOUR_KEY_ID]:[YOUR_KEY_SECRET]
 -X POST https://api.razorpay.com/v1/invoices/inv_1Aa00000000001/notify_by/sms

{
  "success": true
}

Path Parameters

mandatory

string The unique identifier of the invoice linked to the registration link for which you want to send the notification. For example, inv_1Aa00000000001.

medium

mandatory

string Determines through which medium you want to resend the notification. Possible values:

sms
email

1.2.3 Cancel a Registration Link

The following endpoint cancels a registration link.

POST

/invoices/:id/cancel

Handy Tips

You can only cancel registration link in the issued state.

Sample Code

curl -u [YOUR_KEY_ID]:[YOUR_KEY_SECRET]
 -X POST https://api.razorpay.com/v1/invoices/inv_1Aa00000000001/cancel

{
  "id": "inv_FHrfRupD2ouKIt",
  "entity": "invoice",
  "receipt": "Receipt No. 1",
  "invoice_number": "Receipt No. 1",
  "customer_id": "cust_BMB3EwbqnqZ2EI",
  "customer_details": {
      "id": "cust_BMB3EwbqnqZ2EI",
      "name": "<n>",
      "email": "nur.aisyah@example.com",
      "contact": "+60123456789",
      "gstin": null,
      "billing_address": null,
      "shipping_address": null,
      "customer_name": "<n>",
      "customer_email": "nur.aisyah@example.com",
      "customer_contact": "+60123456789"
  },
  "order_id": "order_FHrfRw4TZU5Q2L",
  "line_items": [],
  "payment_id": null,
  "status": "cancelled",
  "expire_by": 4102444799,
  "issued_at": 1595491479,
  "paid_at": null,
  "cancelled_at": 1595491488,
  "expired_at": null,
  "sms_status": "sent",
  "email_status": "sent",
  "date": 1595491479,
  "terms": null,
  "partial_payment": false,
  "gross_amount": 100,
  "tax_amount": 0,
  "taxable_amount": 0,
  "amount": 100,
  "amount_paid": 0,
  "amount_due": 100,
  "currency": "MYR",
  "currency_symbol": "RM",
  "description": "Registration Link for Nur Aisyah",
  "notes": {
      "note_key 1": "Beam me up Scotty",
      "note_key 2": "Tea. Earl Gray. Hot."
  },
  "comment": null,
  "short_url": "https://rzp.io/i/QlfexTj",
  "view_less": true,
  "billing_start": null,
  "billing_end": null,
  "type": "link",
  "group_taxes_discounts": false,
  "created_at": 1595491480,
  "idempotency_key": null
}

Path Parameter

mandatory

string The unique identifier for the invoice linked to the registration link that you want to cancel. For example, inv_1Aa00000000001.