To create an authorization transaction using the Razorpay APIs, you need to:
- .
- .
- .
Razorpay links recurring tokens to customers via a unique identifier. You can generate this identifier using the Customer API.
You can create
with basic information such asemail
and contact
and use them for various Razorpay offerings. The following endpoint creates a customer.
name
mandatory
string
The name of the customer. For example, Gaurav Kumar
.
mandatory
string
The email ID of the customer. For example, gaurav.kumar@example.com
.
contact
mandatory
string
The phone number of the customer. For example, 9876543210
.
fail_existing
optional
boolean
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:
0
: Retrieve details of the existing customer.1
(default): Throws an exception error.
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”
.
You can use the
to create a unique Razorpayorder_id
that is associated with the authorisation transaction. The following endpoint creates an order.
You can use the
API to create a unique Razorpayorder_id
that is associated with the authorisation transaction. The following endpoint creates an order.
Authorisation transaction + auto-charge first payment
You can register a customer's mandate and charge them the first recurring payment as part of the same transaction. Know more about
.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 tha 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 .
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.
notes
optional
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:
netbanking
debitcard
aadhaar
max_amount
optional
integer
The maximum amount in paise a customer can be charged in a transaction. Defaults to 9999900
(₹99,999). The maximum value you can set is 1000000000
(₹1,00,00,000)
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.
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”
.
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 value)current
ifsc_code
optional
string
Customer's bank IFSC. For example UTIB0000001
.
beneficiary_name
optional
string
Name of the beneficiary. For example, Gaurav Kumar
.
Watch Out!
The beneficiary_name
should be between 4 to 120 characters.
Once an order is created, your next step is to create a payment. Use the below endpoint to create a payment with payment method netbanking
.
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
customer_id
mandatory
string
The unique identifier of the customer to be charged. For example, cust_K39wXdBlhqNk0B
.
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.
auth_type
optional
string
Emandate type used to make the authorization payment. Possible values:
netbanking
debitcard
aadhaar
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
account_number
string
Customer's bank account number.
account_type
string
Customer's bank account type. Possible values:
savings
(default value)current
ifsc_code
string
Customer's bank IFSC. For example HDFC0000001
.
If the payment request is valid, the response contains the following fields. Refer to the
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.