1.1 Using Razorpay APIs
You can create an authorisation transaction with the UPI Collect payment method using the following APIs: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 information such asemail and contact and use them for various Razorpay offerings. The following endpoint creates a customer.
/customers
Sample Code
Curl
Response
Request Parameters
name
: string The name of the customer. For example, Gaurav Kumar.
email
: string The email address of the customer. For example, gaurav.kumar@example.com.
contact
: string The phone number of the customer. For example, 9876543210.
fail_existing optional
: 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.
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”.
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
Success Response
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.
customer_id mandatory
: string The unique identifier of the customer. For example, cust_4xbQrmEoA5WJ01.
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 mandatory
: 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 mandatory
: integer 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.
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.1.3. Validate the VPA (UPI ID)
Use the below endpoint to validate the customer’s UPI ID. /payments/validate/vpa Sample CodeRequest
vpa mandatory
: string The UPI ID you want to validate. For example, gauravkumar@exampleupi.
1.1.4. 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/upi
Request
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 Step 1.1.2.: Create an Order.
currency mandatory
: string The 3-letter ISO currency code for the payment. Currently, we only support INR.
order_id mandatory
: string The unique identifier of the order created in Step 1.1.2.: Create an Order.
email mandatory
: string The customer’s email address. For example, gaurav.kumar@example.com.
contact mandatory
: string The customer’s contact number. For example, 9123456780.
customer_id mandatory
: string Unique identifier of the customer, obtained from the response of Step 1.1.1.: Create an Customer.
recurring mandatory
: string 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:
collect(default)intent
vpa mandatory
: string VPA of the customer where the collect request will be sent.
expiry_time mandatory
: integer Period of time (in minutes) after which the link will expire. The default value is 5.
ip mandatory
: string Client’s browser IP address. For example, 117.217.74.98.
referer mandatory
: string Value of referer header passed by the client’s browser. For example, https://example.com/
user_agent mandatory
: 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
description optional
: string Descriptive text of the payment.
save optional
: 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.
notes optional
: json object Key-value pairs that can hold additional information about the payment.
Refer to the Notes section of the API Reference Guide.
Response Parameters
If 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.
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_linksCurl
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.