3. Create Subsequent Payments
Create and charge subsequent payments using Razorpay APIs after the customer's selected payment method is successfully authorised.
Create and charge subsequent payments using Razorpay APIs after the customer's selected payment method is successfully authorised.
You should perform the following steps to create and charge your customer subsequent payments:
- Create an order to charge the customer
- Create a recurring payment
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.
The following endpoint creates an order.
curl -X POST https://api.razorpay.com/v1/orders \-u [YOUR_PARTNER_KEY_ID]:[YOUR_PARTNER_KEY_SECRET]\-H "X-Razorpay-Account: acc_KBrJAIEqre5ucn" \-H "Content-Type: application/json" \-d '{"amount":1000,"currency":"INR","payment_capture": true,"receipt":"Receipt No. 1","notes": {"notes_key_1":"Tea, Earl Grey, Hot","notes_key_2":"Tea, Earl Grey... decaf."}}'
amount
mandatory
integer Amount in currency subunits. For cards, the minimum value is 100 (₹1).
currency
mandatory
string The 3-letter ISO currency code for the payment. Currently, we only support INR.
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.
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 tha payment status should be changed to captured automatically or not. Possible values:
true: Payments are captured automatically.false: Payments are not captured automatically.
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.
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.
method
string The payment method used. Here, it is card.
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.
- 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. For UPI, do not create subsequent payments on the last day of the cycle. This will cause the payment to fail.
curl -X POST https://api.razorpay.com/v1/payments/create/recurring \-u [YOUR_PARTNER_KEY_ID]:[YOUR_PARTNER_KEY_SECRET]\-H "X-Razorpay-Account: acc_KBrJAIEqre5ucn" \-H "Content-Type: application/json" \-d '{"email": "gaurav.kumar@example.com","contact": "9876543210","amount": 71000,"currency": "INR","order_id": "order_KhUvbWvROaN5cu","customer_id": "cust_KhOZydVZbcThjW","token": "token_KhT8dzSCFruvfj","recurring": "1","description": "Creating recurring payment for Kay Say","notes": {"note_key 1": "i dare you","note_key 2": "i double dare you"}}'
mandatory
string The customer's email address. For example,
contact
mandatory
integer 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 order amount.
currency
mandatory
string 3-letter ISO currency code for the payment. Currently, only INR is allowed.
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
Was this page helpful?