API ReferenceIntegrationsKnowledge Base

3. Create Subsequent Payments

You have to complete two 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 authorization transaction.

Use the below endpoint to create an order.

/orders

Auto-capture Payments:
To auto-capture payments, set payment_capture to 1 as shown in the example.

The payment_capture parameter defaults to 0 if not set.

Request Parameters#

amount mandatory
integer Amount in currency subunits. Minimum value is 100 (₹1 ). Maximum value depends on the max_amount for the token.
currency mandatory
string The 3-letter ISO currency code for the payment. Currently, we only support INR.
payment_capture mandatory
boolean Indicates if auto-capture is enabled for the order. In this case, the value has to be 1, that is auto-capture is enabled.
receipt optional
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.
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”.

3.2. Create a Recurring Payment#

Once you have generated an order_id, use it along with the token_id to create a payment and charge the customer.

Use the below endpoint to create a payment and charge the customer.

/payments/create/recurring

Once our system validates and successfully processes the payment request, a razorpay_payment_id is returned. In the case of some banks such as HDFC and Axis, the payment entity returned will be in the created state since the charge system of these banks are file-based and can take a few hours.

Note:
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.

Request Parameters#

email mandatory
string The customer's email address. For example, gaurav.kumar@example.com.
contact mandatory
string The customer's phone number. For example, 9876543210.
amount mandatory
integer The amount you want to charge your customer. This should be the same as the amount in the order.
currency mandatory
string 3-letter ISO currency code for the payment. Currently, only INR is allowed.
order_idmandatory
string The unique identifier of the order created. For example, order_1Aa00000000002.
customer_id mandatory
string The customer_id for the customer you want to charge. For example, cust_1Aa00000000002.
token mandatory
string The token_id generated when the customer successfully completes the authorization payment. Different payment instruments for the same customer have different token_id.
recurring mandatory
boolean Determines if recurring payment is enabled or not. Possible values:
  • 1 - Recurring is enabled.
  • 0 - Recurring is not enabled.
descriptionoptional
string A user-entered description for the payment. For example, Creating recurring payment for Gaurav Kumar.
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”.
×