Skip to main content
Available in🇮🇳 India
You should perform the following steps to create and charge your customer subsequent payments:
  1. Create an order to charge the customer
  2. Create a recurring payment

3.1. Create an Order to Charge the Customer

You have to create a new order every time you want to charge your customers. This order is different from the one created when you created the authorisation transaction. Use the below endpoint to create an order: POST /orders

Request Parameters

integer
required
Amount in currency subunits. For cards, the minimum value is 100 (₹1).
string
required
The 3-letter ISO currency code for the payment. Currently, we only support INR.
string
A user-entered unique identifier for the order. For example, Receipt No. 1. This parameter should be mapped to the order_id sent by Razorpay.
object
Details of the pre-debit notification. This object is optional. You should use it only if you want to control pre-debit notifications and debits. If you do not pass this object, we will automatically try to debit 25 hours after the pre-debit notification is delivered.
Watch Out!We will not attempt any retry if the debit fails for tokens with the notification object in the created order. You should manually retry the debit attempt.
string
required
The token_id generated when the customer successfully completes the authorisation payment. Different payment instruments for the same customer have different token_id.
integer
UNIX timestamp post which the debit is supposed to happen. Defaults to 25 hours after the pre-debit notification is delivered.
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”.
boolean
required
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.
object
required
Details of the bank account of the customer.
integer
required
The bank account number of the customer. For example, 123456789012345.
string
required
The name of the bank account holder.
string
required
The IFSC of the bank. For example, HDFC0000053.
object
Details of the pre-debit notification. You should use it only if you want to control pre-debit notifications and debits. If you do not pass this object, we will automatically try to debit 25 hours after the pre-debit notification is delivered.
Watch Out!We will not attempt any retry if the debit fails for tokens with the notification object in the created order. You should manually retry the debit attempt.
string
required
The token_id generated when the customer successfully completes the authorisation payment. Different payment instruments for the same customer have different token_id.
integer
UNIX timestamp post which the debit is supposed to happen. Defaults to 25 hours after the pre-debit notification is delivered.

3.2. Create a Recurring Payment

Once you have generated an order_id, use it with the token_id to create a payment and charge the customer. The following endpoint creates a payment to charge the customer. POST /payments/create/recurring
UPI Payments
  • We recommend sending a pre-debit notification to the customer 24 hours before the debit date.
  • For UPI, it may take between 24-36 hours for the subsequent payment to reflect on your Dashboard.
  • This is because of the failure of pre-debit notification and/or any retries that we attempt for the payment.
  • Do not create another subsequent payment until you get the status of the previous one.
UPI Payments
  • The subsequent payment may fail if there is late authorisation of an earlier payment.
  • For UPI, do not create subsequent payments on the last day of the cycle. This will cause the payment to fail.

Request Parameters

string
required
The customer’s email address. For example, gaurav.kumar@example.com.
integer
required
The customer’s phone number. For example, 9876543210.
string
required
3-letter ISO currency code for the payment. Currently, only INR is allowed.
integer
required
The amount you want to charge your customer. This should be the same as the order amount.
string
required
The unique identifier of the order created. For example, order_1Aa00000000002.
string
required
The unique identifier of the customer you want to charge. For example, cust_1Aa00000000002.
string
required
The token_id generated when the customer successfully completes the authorisation payment. Different payment instruments for the same customer have different token_id.
boolean
required
Determines whether recurring payment is enabled or not.
  • true: Recurring payment is enabled.
  • false: Recurring payment is not enabled.
string
A user-entered description for the payment. For example, Creating recurring payment for Gaurav Kumar
object
Key-value pair you can use to store additional information about the entity. Maximum of 15 key-value pairs, 256 characters each. For example, "note_key": "Beam me up Scotty”.
Last modified on November 19, 2026