3. Create Subsequent Payments

Create and charge subsequent payments using Razorpay APIs after the customer's selected payment method is successfully authorized.


You should perform the following steps to create and charge your customer subsequent payments:

You have to create a new order every time you want to charge your customers. This order is different from the one created during the authorisation transaction.

Handy Tips

You can use the notification object in the request if you want to control pre-debit notifications and recurring debits.

The following endpoint creates an order.

POST
/orders

amount

mandatory

integer Amount in currency subunits. For cards, the minimum value is 100 (₹1.00).

currency

mandatory

string The 3-letter ISO currency code for the payment. Currently, we support INR only.

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.

notification

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 after 36 hours and 5 minutes.

Handy Tips

The TAT to create a debit if you send a pre-debit notification is 36 hours and 5 minutes.

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.

token_id

mandatory

string The token_id generated when the customer successfully completes the authorisation payment. Different payment instruments for the same customer have different token_id.

payment_after

optional

integer UNIX timestamp post which the debit is supposed to happen. Defaults to 36 hours and 5 minutes after the pre-debit notification is delivered.

notes

optional

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”.

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 .

id

string A unique identifier of the order created. For example order_1Aa00000000001.

entity

string The entity that has been created. Here it is order.

amount

integer Amount in currency subunits.

amount_paid

integer The amount that has been paid.

amount_due

integer The amount that is yet to be paid.

currency

string The 3-letter ISO currency code for the payment. Currently, we only support INR.

receipt

string A user-entered unique identifier of the order. For example, rcptid #1.

notification

object Details of the pre-debit notification.

token_id

string The token_id generated when the customer successfully completes the authorisation payment. Different payment instruments for the same customer have different token_id.

payment_after

integer UNIX timestamp post which the debit is supposed to happen.

id

string the unique identifier of the notification. For example, notification_00000000000001.

status

string The status of the order.

notes

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”.

created_at

integer The Unix timestamp at which the order was created.

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
  • You will get a razorpay_payment_id, razorpay_order_id and razorpay_signature as a response after the payment request is successfully processed.
  • In the case of some banks, such as HDFC Bank and Axis Bank, the payment entity is in the created state since the charging system of these banks is file-based and can take some time.

email

mandatory

string The customer's email address. For example, gaurav.kumar@example.com.

contact

mandatory

integer The customer's phone number. For example, 9876543210.

currency

mandatory

string 3-letter ISO currency code for the payment. Currently, only INR is allowed.

amount

mandatory

integer The amount you want to charge your customer. This should be the same as the order amount.

order_id

mandatory

string The unique identifier of the order created. For example, order_1Aa00000000002.

customer_id

mandatory

string The unique identifier of the customer you want to charge. For example, cust_1Aa00000000002.

token

mandatory

string The token_id generated when the customer successfully completes the authorisation payment. Different payment instruments for the same customer have different token_id.

recurring

mandatory

boolean Determines whether recurring payment is enabled or not.

description

optional

string A user-entered description for the payment. For example, Creating recurring payment for Gaurav Kumar

notes

optional

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”.

razorpay_payment_id

string The unique identifier of the payment that is created. For example, pay_1Aa00000000001.

razorpay_order_id

string The unique identifier of the order that is created. For example, order_1Aa00000000001.

razorpay_signature

string The signature generated by the Razorpay. For example, 9ef4dffbfd84f1318f6739a3ce19f9d85851857ae648f114332d8401e0949a3d

Given below is a list of possible errors you may face while creating a Recurring Payment.

Use this endpoint to retrieve details of a particular order as per the id.

GET
/v1/orders/:id

id

mandatory

string Unique identifier of the order to be retrieved.

id

string The unique identifier of the order.

amount

integer The amount for which the order was created, in currency subunits. For example, for an amount of ₹295.00, enter 29500.

entity

string Name of the entity. Here, it is order.

amount_paid

integer The amount paid against the order.

amount_due

integer The amount pending against the order.

currency

string ISO code for the currency in which you want to accept the payment. The default length is 3 characters. Refer to the

.

receipt

string Receipt number that corresponds to this order. Can have a maximum length of 40 characters and has to be unique.

notification

object Details of the pre-debit notification. The notification object is populated in the response only if you have passed this while creating an order.

token_id

string The token_id generated when the customer successfully completes the authorisation payment. Different payment instruments for the same customer have different token_id.

payment_after

integer Unix timestamp post which the debit is supposed to happen.

id

string Unique identifier of the notification.

delivered_at

integer Indicates the unix timestamp when the notification was delivered.

status

string The status of the order. Possible values:

  • created: When you create an order it is in the created state. It stays in this state till a payment is attempted on it.
  • attempted: An order moves from created to attempted state when a payment is first attempted on it. It remains in the attempted state till one payment associated with that order is captured.
  • paid: After the successful capture of the payment, the order moves to the paid state. No further payment requests are permitted once the order moves to the paid state. The order stays in the paid state even if the payment associated with the order is refunded.

attempts

integer The number of payment attempts, successful and failed, that have been made against this order.

notes

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”.

created_at

integer Indicates the Unix timestamp when this order was created.


Was this page helpful?