1.1 Using Razorpay APIs
To create an authorisation transaction using the Razorpay APIs, you need to:1.1.1 Create a Customer
Razorpay links recurring tokens to customers via a unique identifier. You can generate the unique identifier for a customer using the Customer API. You can create customers with basic details such asemail and contact and use them for various Razorpay offerings. Know more about Customers.
You can create a customer using the below endpoint.
/customers
Curl
Request Parameters
name mandatory
: string The customer’s name. For example, Gaurav Kumar.
email 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 Razorpayorder_id that is associated with the authorisation transaction. The following endpoint creates an order.
/orders
Sample Code
Curl
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 authorisation transaction. 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.
notesoptional
: 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 authorization such as max amount, frequency and expiry information.
max_amount optional
: integer The maximum amount that can be debited in a single charge.
MCC | Category | Min Value | Max Value
6211 | Financial Services | 100 (₹1) | 20000000 (₹2,00,000)
6300 | Financial Services | 100 (₹1) | 20000000 (₹2,00,000)
7322 | Financial Services | 100 (₹1) | 20000000 (₹2,00,000)
6529 | Financial Services | 100 (₹1) | 20000000 (₹2,00,000)
5960 | Services | 100 (₹1) | 20000000 (₹2,00,000)
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 authorisation transaction must expire. Defaults to 10 years.
frequency mandatory
: string The frequency at which you can charge your customer. Possible values:
weeklymonthlyquarterlyyearlyas_presented
recurring_value optional
: integer Determines the exact date or range of dates for recurring debits. Possible values are:
- 1-7 for
weeklyfrequency - 1-31 for
monthlyfrequency - 1-31 for
quarterlyfrequency - 1-31 for
yearlyfrequency and is not applicable for theas_presentedfrequency.
1.1.3 Create an Authorisation Payment
Once an order is created, your next step is to create a payment. Use the below endpoint to create a payment with payment methodupi.
/payments/create
Sample Code
Request
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
: Details of the expiry of the UPI link
flow mandatory
: string Specify the type of the UPI payment flow.
Possible values are:
intent(default)collect: Deprecated effective 28 February 2026. Applicable only for exempted businesses.
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 for more details.razorpay_payment_id
: string Unique reference for the payment created. For example, pay_EAm09NKReXi2e0.
Next Steps by Platform
Use the link returned in the response as a deeplink to redirect the customer to their preferred UPI app to complete the mandate registration. UPI Intent is not supported on Desktop Web. Convert the link returned in the response into a QR code and display it on your checkout UI for the customer to scan with their preferred UPI app.1.2 Using a Registration Link
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 Tips
₹1.
1.2.1 Create a Registration Link
The following endpoint creates a registration link. /subscription_registration/auth_linksSample Code
Curl
Request Parameters
customer
: object Details of the customer to whom the registration link is sent.
name mandatory
: string Customer’s name.
email mandatory
: string Customer’s email address.
contactmandatory
: 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 authorisation transaction.
method mandatory
: string The payment method used to make authorisation transaction. Here, it is card.
max_amount mandatory
: integer Use to set the maximum amount (in paise) per debit request.
MCC | Category | Min Value | Max Value
6211 | Financial Services | 100 (₹1) | 20000000 (₹2,00,000)
6300 | Financial Services | 100 (₹1) | 20000000 (₹2,00,000)
7322 | Financial Services | 100 (₹1) | 20000000 (₹2,00,000)
6529 | Financial Services | 100 (₹1) | 20000000 (₹2,00,000)
5960 | Services | 100 (₹1) | 20000000 (₹2,00,000)
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:
dailyweeklyfortnightlybimonthlymonthlyquarterlyhalf_yearlyyearlyas_presented
recurring_value optional
: integer Determines the exact date or range of dates for recurring debits. Possible values are:
- 1-7 for
weeklyfrequency - 1-31 for
fortnightlyfrequency - 1-31 for
bimonthlyfrequency - 1-31 for
monthlyfrequency - 1-31 for
quarterlyfrequency - 1-31 for
half_yearlyfrequency - 1-31 for
yearlyfrequency and is not applicable for theas_presentedfrequency.
1.2.2 Send/Resend Notifications
The following endpoint sends/resends notifications with the short URL to the customer: /invoices/:id/notify_by/:mediumSample Code
Curl
Response
Path Parameters
idmandatory
: 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:
smsemail
1.2.3 Cancel a Registration Link
The following endpoint cancels a registration link. /invoices/:id/cancelHandy Tips
issued state.
Sample Code
Curl
Response
Path Parameter
id mandatory
: string The unique identifier for the invoice linked to the registration link that you want to cancel. For example, inv_1Aa00000000001.