Handy Tips
1.1. Using Razorpay APIs
To create an authorisation transaction using the Razorpay APIs, you need to:1
[Create a Customer](#111-create-a-customer).
2
[Create an Order](#112-create-an-order).
3
[Create Authorisation Payment using Razorpay APIs](#113-create-an-a...
1.1.1. Create a Customer
Token Sharing for Partner Auth Model
- Add the basic auth with partner credentials (client_id and client_secret).
- Add the
account_idof the sub-merchant usingX-Razorpay-Accountin the header. For example, -H “X-Razorpay-Account: acc_KBrJAIEqre5ucn”
Request
email 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”.
Response Parameters
id
: string The unique identifier of the customer. For example cust_1Aa00000000001.
entity
: string The name of the entity. Here, it is customer.
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.
notes
: 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”.
created_at
: integer A Unix timestamp, at which the customer was created.
You can create an order once you create a customer for the payment authorisation.
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
Token Sharing for Partner Auth Model
- Add the basic auth with partner credentials (client_id and client_secret).
- Add the
account_idof the sub-merchant usingX-Razorpay-Accountin the header. For example, -H “X-Razorpay-Account: acc_KBrJAIEqre5ucn”
Request
Curl
Response
Request Parameters
amount mandatory
: integer Amount in currency subunits. For cards, the amount should be 100, that is, 1.
currency mandatory
: string The 3-letter ISO currency code for the payment.
customer_id mandatory
: string The unique identifier of the customer. For example, cust_4xbQrmEoA5WJ01.
method optional
: string Payment method used to make the authorisation transaction. Here, it is card.
token
: object Details related to the authorisation such as max amount, frequency and expiry information.
max_amount mandatory
: integer The maximum amount that can be auto-debited in a single charge. The minimum value is 100, that is, 1, and the maximum value is 1500000, that is, 15000. For an amount higher than this, the cardholder should provide an Additional Factor of Authentication (AFA) as per RBI guidelines.
expire_at mandatory
: integer The Unix timestamp that indicates when the authorisation transaction must expire. The card’s expiry year is considered a default value.
frequency mandatory
: string The frequency at which you can charge your customer. Possible values:
weeklymonthlyyearlyas_presented
expire_at mandatory
: integer The Unix timestamp that indicates when the authorisation transaction must expire. The card’s expiry year is considered a default value.
frequency mandatory
: string The frequency at which you can charge your customer. Possible values:
weeklymonthlyyearlyas_presented
receipt optional
: string A user-entered unique identifier for the order. For example, Receipt No. 1. You should map this parameter to the order_id sent by Razorpay.
notesoptional
: object Key-value pair you can use to store additional information about the entity. Maximum 15 key-value pairs, 256 characters each. For example, "note_key": "Beam me up Scotty”.
Response Parameters
id
: string A unique identifier of the order created. For example order_1Aa00000000002.
entity
: string The entity that has been created. Here it is order.
amount
: integer Amount in currency subunits. For cards, the amount should be 100, that is, 1.
amount_paid
: integer The amount that has been paid.
amount_due
: integer The amount that is yet to pay.
currency
: string The 3-letter ISO currency code for the payment.
receipt
: string A user-entered unique identifier of the order. For example, Receipt No. 1. You should map this parameter to the order_id sent by Razorpay.
method
: string Payment method used to make the authorisation transaction. Here, it is card.
customer_id
: string The unique identifier of the customer. For example, cust_4xbQrmEoA5WJ01.
status
: string The status of the order.
notes
: 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”.
created_at
: integer The Unix timestamp at which the order was created.
You can create a payment against the order_id after you create an order.
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 methodcard.
Token Sharing for Partner Auth Model
- Add the basic auth with partner credentials (client_id and client_secret).
- Add the
account_idof the sub-merchant usingX-Razorpay-Accountin the header. For example, -H “X-Razorpay-Account: acc_KBrJAIEqre5ucn”
Request
Request
Handy Tips
- To process recurring transactions, customer card details will need to be secured/tokenised in accordance with the applicable laws. You will be solely responsible for obtaining informed consent from customers for the processing of emandates and such consent shall be explicit and not by way of a forced/default/automatic selection of check box, radio button etc.
- When the merchant is sharing
recurring: trueorpreferred, it is for tokenising the card as per applicable rules for recurring mandate creation. If such consent is not shared during the payment flow, then Razorpay will not tokenise the card or process the emandate/ recurring transaction.
Request Parameters
amount mandatory
: integer Amount in currency subunits. For cards, the minimum value is 100, that is, 1.
currency mandatory
: string The 3-letter ISO currency code for the payment.
order_id mandatory
: string The unique identifier of the order created in Step 1.1.2.: Create an Order.
customer_id mandatory
: string The unique identifier of the customer.
recurring mandatory
: boolean Possible values:
true: Recurring payment is enabled.false: Recurring payment is not enabled.
Handy Tips
recurring parameter also supports the value preferred. Use this when you want to support recurring payments and one-time payment in the same flow.
save mandatory
: integer Saves the customer’s card details. Possible values:
1: Saves the card details.0: Does not save the card details.
email mandatory
: string The customer’s email address.
contact mandatory
: string The customer’s contact number.
method mandatory
: string The payment method selected by the customer. Here, the value must be card.
card
: object The attributes associated with a card.
number mandatory
: integer Unformatted card number. This field is required if value of method is card. Use one of our test cards to try out the payment flow.
name mandatory
: string The name of the cardholder.
expiry_month mandatory
: integer The expiry month of the card in MM format. For example, 01 for January and 12 for December.
expiry_year mandatory
: integer Expiry year for card in the YY format. For example, 2030 will be in format 30.
cvv mandatory
: integer CVV printed on the back of the card.
Handy Tips
- CVV is not required by default for tokenised cards across all networks.
- CVV is optional for tokenised card payments. Do not pass dummy CVV values.
- To implement this change, skip passing the
cvvparameter entirely, or pass anullor empty value in the CVV field. - We recommend removing the CVV field from your checkout UI/UX for tokenised cards.
- If CVV is still collected for tokenised cards and the customer enters a CVV, pass the entered CVV value to Razorpay.
Response Parameters
If the payment request is valid, the response contains the following fields. Refer to the S2S Json V2 integration document for more details.razorpay_payment_id
: string Unique identifier of the payment. Present for all responses.
next
: array A list of action objects available to you to continue the payment process. Present when the payment requires further processing.
action
: string An indication of the next step available to you to continue the payment process. Possible values:
otp_generate- Use this URL to allow the customer to generate OTP and complete the payment on your webpage.redirect- Use this URL to redirect the customer to submit the OTP on the bank page.
url
: string URL to be used for the action indicated.
After this step, you can proceed to integrate with the Fetch Token API.
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.2.1. Create a Registration Link
The following endpoint creates a registration link. /subscription_registration/auth_linksCurl
Response
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
: object Details of the authorisation transaction.
method mandatory
: string The authorisation method. Here it is card.
max_amount mandatory
: integer The maximum amount that can be auto-debited in a single charge. The minimum value is 100 (₹1) and the maximum value is 100000000 (₹10,00,000). For an amount higher than this or the RBI limit of ₹15,000 (1500000) or ₹1,00,000 (10000000) respectively, the cardholder should provide an Additional Factor of Authentication (AFA) as per RBI guidelines.
expire_at optional
: integer The Unix timestamp till when you can use the token (authorisation on the payment method) to charge the customer subsequent payments. The card’s expiry year is considered a default value.
frequency mandatory
: string The frequency at which you can charge your customer. Possible values:
weeklymonthlyyearlyas_presented
sms_notify optional
: 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.
email_notify optional
: 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.
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.
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”.
Response Parameters
id
: string The unique identifier of the invoice.
entity
: string The entity that has been created. Here, it is invoice.
receipt
: string A user-entered unique identifier of the invoice.
invoice_number
: string Unique number you added for internal reference.
customer_id
: string The unique identifier of the customer. For example, cust_BMB3EwbqnqZ2EI.
customer_details
: object Details of the customer.
id
: string The unique identifier associated with the customer to whom the invoice has been issued.
name
: string The customer’s name.
email
: string The customer’s email address.
contact
: integer The customer’s phone number.
billing_address
: string Details of the customer’s billing address.
shipping_address
: string Details of the customer’s shipping address.
order_id
: string The unique identifier of the order associated with the invoice.
line_items
: string Details of the line item that is billed in the invoice. Maximum of 50 line items are allowed.
payment_id
: string Unique identifier of a payment made against the invoice.
status
: string The status of the invoice. Possible values:
draftissuedpartially_paidpaidcancelledexpireddeleted
expire_by
: integer The Unix timestamp at which the invoice will expire.
issued_at
: integer The Unix timestamp at which the invoice was issued to the customer.
paid_at
: integer The Unix timestamp at which the payment was made.
cancelled_at
: integer The Unix timestamp at which the invoice was cancelled.
expired_at
: integer The Unix timestamp at which the invoice expired.
sms_status
: string The delivery status of the SMS notification for the invoice sent to the customer. Possible values:
pendingsent
email_status
: string The delivery status of the email notification for the invoice sent to the customer. Possible values:
pendingsent
date
: integer Timestamp, in Unix format, that indicates the issue date of the invoice.
terms
: string Any terms to be included in the invoice. Maximum of 2048 characters.
partial_payment
: boolean Indicates whether the customer can make a partial payment on the invoice. Possible values:
true: The customer can make partial payments.false(default): The customer cannot make partial payments.
amount
: integer Amount to be paid using the invoice. Must be in the smallest unit of the currency. For example, if the amount to be received from the customer is 299.95, pass the value as 29995.
amount_paid
: integer Amount paid by the customer against the invoice.
amount_due
: integer The remaining amount to be paid by the customer for the issued invoice.
currency
: string The currency associated with the invoice.
description
: string A brief description of the invoice.
notes
: object Any custom notes added to the invoice. Maximum of 2048 characters.
short_url
: string The short URL that is generated. This is the link that can be shared with the customer to receive payments.
type
: string Here, it is invoice.
comment
: string Any comments to be added in the invoice. Maximum of 2048 characters.
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
Response Parameter
success
: boolean Indicates whether the notifications were sent successfully. Possible values:
true: The notifications were successfully sent via SMS, email or both.false: The notifications were not sent.
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.
Response Parameter
id
: string The unique identifier of the invoice.
entity
: string The entity that has been created. Here, it is invoice.
receipt
: string A user-entered unique identifier of the invoice.
invoice_number
: string Unique number you added for internal reference.
customer_id
: string The unique identifier of the customer. For example, cust_BMB3EwbqnqZ2EI.
customer_details
: object Details of the customer.
id
: string The unique identifier associated with the customer to whom the invoice has been issued.
name
: string The customer’s name.
email
: string The customer’s email address.
contact
: integer The customer’s phone number.
billing_address
: string Details of the customer’s billing address.
shipping_address
: string Details of the customer’s shipping address.
order_id
: string The unique identifier of the order associated with the invoice.
line_items
: string Details of the line item that is billed in the invoice. Maximum of 50 line items are allowed.
payment_id
: string Unique identifier of a payment made against the invoice.
status
: string The status of the invoice. Possible values:
draftissuedpartially_paidpaidcancelledexpireddeleted
expire_by
: integer The Unix timestamp at which the invoice will expire.
issued_at
: integer The Unix timestamp at which the invoice was issued to the customer.
paid_at
: integer The Unix timestamp at which the payment was made.
cancelled_at
: integer The Unix timestamp at which the invoice was cancelled.
expired_at
: integer The Unix timestamp at which the invoice expired.
sms_status
: string The delivery status of the SMS notification for the invoice sent to the customer. Possible values:
pendingsent
email_status
: string The delivery status of the email notification for the invoice sent to the customer. Possible values:
pendingsent
date
: integer Timestamp, in Unix format, that indicates the issue date of the invoice.
terms
: string Any terms to be included in the invoice. Maximum of 2048 characters.
partial_payment
: boolean Indicates whether the customer can make a partial payment on the invoice. Possible values:
true: The customer can make partial payments.false(default): The customer cannot make partial payments.
amount
: integer Amount to be paid using the invoice. Must be in the smallest unit of the currency. For example, if the amount to be received from the customer is 299.95, pass the value as 29995.
amount_paid
: integer Amount paid by the customer against the invoice.
amount_due
: integer The remaining amount to be paid by the customer for the issued invoice.
currency
: string The currency associated with the invoice.
description
: string A brief description of the invoice.
notes
: object Any custom notes added to the invoice. Maximum of 2048 characters.
short_url
: string The short URL that is generated. This is the link that can be shared with the customer to receive payments.
type
: string Here, it is invoice.
comment
: string Any comments to be added in the invoice. Maximum of 2048 characters.
After this step, you can proceed to integrate with the Fetch Token API.