1.1. Using Razorpay APIs
To create an authorisation transaction using the Razorpay APIs, you need to:1
[Fetch Payment Methods](#111-fetch-payment-methods).
2
[Create a Customer](#112-create-a-customer).
3
[Create an Order](#113-create-an-order).
4
[Create Authorisation Payment using Razorpay APIs](#113-create-an-a...
1.1.1. Fetch Payment Methods
Use the below endpoint to fetch a list of banks Razorpay supports for different payment methods. /methods1.1.2. 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.3. 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
Given below is the sample code to authenticate emandate with Aadhaar. Aadhaar authentication type is enabled by default for your Razorpay account.
Curl
Response
Curl
Response
Curl
Response
Authorisation transaction + auto-charge first payment
Request Parameters
amount mandatory
: integer Amount in currency subunits. For emandate, the amount should be 0.
currency mandatory
: string The 3-letter ISO currency code for the payment. Currently, we only support INR.
payment_capture mandatory
: boolean Determines whether the payment status should be changed to captured automatically or not. Possible values:
true: Payments are captured automatically.false: Payments are not captured automatically. You can manually capture payments using the Manually Capture Payments API.
method mandatory
: string The authorisation method. Here, it is emandate.
customer_id mandatory
: string The unique identifier of the customer to be charged. For example, cust_D0cs04OIpPPU1F.
receipt optional
: string A user-entered unique identifier of the order. For example, rcptid #1. You should map this parameter to the order_id sent by Razorpay.
notesoptional
: json 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 authorisation such as max amount and bank account information.
auth_type optional
: string Emandate type used to make the authorisation payment. Possible values:
netbankingdebitcardaadhaar
max_amount optional
: integer The maximum amount in paise a customer can be charged in a transaction. Know about the maximum and default values.
expire_at optional
: integer The Unix timestamp to indicate till when you can use the token (authorisation on the payment method) to charge the customer subsequent payments. Defaults to 40 years. The maximum value you can set is 40 years from the current date. Any value beyond this will throw an error.
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”.
bank_account
: Customer’s bank account details that should be pre-filled on the checkout.
account_number optional
: string Customer’s bank account number.
account_type optional
: string Customer’s bank account type. Possible values:
savings(default)current
ifsc_code optional
: string Customer’s bank IFSC. For example UTIB0000001.
beneficiary_name optional
: string Name of the beneficiary. For example, Gaurav Kumar.
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 methodnetbanking.
/payments/create/json
Request
Request Parameters
amount mandatory
: integer Amount in currency subunits. For netbanking, the amount has to be 0 (₹0).
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 using in Step 1.1.2.
customer_id mandatory
: string The unique identifier of the customer to be charged. For example, cust_K39wXdBlhqNk0B.
recurring mandatory
: boolean Possible values:
true: Recurring payment is enabled.false: Recurring payment is not enabled.
auth_type optional
: string Emandate type used to make the authorisation payment. Possible values:
netbankingdebitcardaadhaar
email mandatory
: string The customer’s email address. For example, gaurav.kumar@example.com.
contact mandatory
: string The customer’s contact number. For example, 8888888888.
method mandatory
: string The payment method selected by the customer. Here, the value must be emandate.
bank mandatory
: string The customer’s bank name. The bank code used here should match the bank details used in Step 1.1.2. Use the Method API to check the bank code.
account_number
: string Customer’s bank account number.
account_type
: string Customer’s bank account type. Possible values:
savings(default)current
ifsc_code
: string Customer’s bank IFSC. For example HDFC0000001.
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. The value here is redirect - Use this URL to redirect customer to the bank page.
url
: string URL to be used for the action indicated.
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
0.
1.2.1. Create a Registration Link
The following endpoint creates a registration link. /subscription_registration/auth_linksRequest
Curl
Response
Request
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 payment.
method mandatory
: string The authorization method. Here, it is emandate.
auth_type optional
: string Possible values:
netbankingdebitcardaadhaar
max_amount optional
: integer The maximum amount, in paise, a customer can be charged in a transaction. Know about maximum and default values.
expire_at optional
: integer The Unix timestamp indicates till when you can use the token (authorization on the payment method) to charge the customer their subsequent payments. Defaults to 40 years. The maximum value you can set is 40 years from the current date. Any value beyond this will throw an error.
bank_account
: The customer’s bank account details.
beneficiary_name optional
: string Name on the beneficiary. For example Gaurav Kumar.
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.