3. Create Subsequent Payments
Create and charge subsequent payments using Razorpay APIs after the customer's selected payment method is authorised.
Given below are the 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.
The following endpoint creates an order.
curl -u [YOUR_KEY_ID]:[YOUR_KEY_SECRET] \-X POST https://api.razorpay.com/v1/orders \-H "Content-Type: application/json" \-d '{"amount": 1000,"currency": "INR","merchant_id": "D2eavTHExqy97j","customer_id": "cust_N8fv8Nftx5hato","customer_details": {"name": "Gaurav Kumar","email": "gaurav.kumar@example.com","contact": "9000090000","shipping_address": {"line1": "Mantri apartment","line2": "Koramangala","city": "Bengaluru","country": "IND","state": "Karnataka","zipcode": "560032","latitude": "123123","longitude": "1231231"},"insights": {"order_count": "22","chargeback_count": "4","tier": "gold","booking_channel": "agent","has_account": true,"registered_at": 1234567890}},"receipt": "Receipt No. 1","notes": {"notes_key_1": "Tea, Earl Grey, Hot","notes_key_2": "Tea, Earl Grey... decaf."}}'
{"amount": 1000,"amount_due": 1000,"amount_paid": 0,"attempts": 0,"created_at": 1707389202,"currency": "INR","entity": "order","id": "order_NYMDbygGb1DuDd","notes": {"notes_key_1": "Tea, Earl Grey, Hot","notes_key_2": "Tea, Earl Grey... decaf."},"offer_id": null,"receipt": "Receipt No. 1","status": "created"}
amount
mandatory
integer Amount in currency subunits. For cards, the amount should be 100 (RM 1).
currency
mandatory
string The 3-letter ISO currency code for the payment. Currently, we only support INR.
merchant_id
mandatory
string This is the Razorpay merchant ID for your Razorpay account. You can find this by logging in to the Dashboard and clicking the user icon in the top right corner.
customer_id
mandatory
string The unique identifier of the customer. For example, cust_4xbQrmEoA5WJ01.
customer_details
mandatory
object This contains details about the customer details of the order.
name
mandatory
string Customer's name.
- Character length: Between 5 and 50 characters.
- Allowed characters: Uppercase letters (A-Z), lowercase letters (a-z), and spaces (not at the beginning).
- Not allowed characters: Numbers, special characters (e.g., @, ", ,, ., etc.), Unicode characters, emojis, and non-Latin scripts or regional languages.
- Prohibited names: Names must be meaningful and contextually appropriate.
- Avoid using repetitive patterns (e.g., aaa, xyz, kkk kk).
- Names like litri litri, Hfg Gh, or husi husi are not permitted.
- Curse words or offensive names are not prohibited.
- Example:
Gaurav Kumar.
optional
string The customer's email address. A maximum length of 64 characters for the username. For example, in "
contact
optional
string The customer's phone number. A maximum length of 15 characters including country code. For example, +919000090000.
shipping_address
mandatory
object This contains the shipping address of the order.
line1
mandatory
string Address Line 1 of the address.
- Character length: Must be between 3 and 100 characters.
- Allowed characters: Uppercase letters (A-Z), lowercase letters (a-z), numbers (0-9), spaces, and special characters (*&/-()#_+[]:'".,.).
- Not allowed characters: Regional languages.
line2
mandatory
string Address Line 2 of the address.
- Character length: Must be between 3 and 100 characters.
- Allowed characters: Uppercase letters (A-Z), lowercase letters (a-z), numbers (0-9), spaces, and special characters (*&/-()#_+[]:'".,.).
- Not allowed characters: Regional languages.
city
mandatory
string Name of the city. Must be between 3 and 50 characters in length and can only include uppercase (A-Z) and lowercase (a-z) English letters, and spaces.
country
mandatory
string ISO3 country code of the billing address. Only IND is allowed.
state
mandatory
string Name of the state. It must be between 3 and 50 characters extended and can only include uppercase (A-Z) and lowercase (a-z) English letters and spaces. Please send the full name of the state, for example, Madhya Pradesh.
zipcode
mandatory
string The ZIP code must consist of 6-digit numeric characters. Only valid Indian ZIP codes will be accepted. Refer to the
latitude
optional
float Latitude of the position expressed in decimal degrees (WSG 84), for example, 6.244203. A positive value denotes the northern hemisphere or the equator, and a negative value denotes the southern hemisphere. The number of digits to represent the precision of the coordinate.
longitude
optional
float Longitude of the position expressed in decimal degrees (WSG 84), for example, -75.581211. A positive value denotes east longitude or the prime meridian, and a negative value denotes west longitude. The number of digits to represent the precision of the coordinate.
insights
optional
json object Additional details of the customer, including past transaction data.
order_count
optional
integer Total orders placed by the account so far on the business platform. For example, 22.
chargeback_count
optional
integer Total chargeback received for the customer account on the business platform. For example, 4.
tier
optional
string Your company's passenger classification, such as with a frequent flyer program. In this case, you might use values such as:
standardgoldplatinum
booking_channel
optional
string To share if the user is an agent, corporate, or individual. Possible values:
agentcorporateindividual
has_account
optional
boolean To denote if the buyer is on guest checkout or has logged into the account. Possible values:
- 1: If the user is logged into the account.
0: If the user is on guest
registered_at
optional
integer UNIX timestamp when the customer account was created. For example, 1234567890.
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 Curlec.
notes
optional
object Key-value pair you can use to store additional information about the entity. Maximum 15 key-value pairs, 256 characters each. For example, "note_key": "Beam me up Scotty”.
amount
integer Amount in currency subunits. For cards, the amount should be 100 (RM 1).
amount_due
integer The amount that the customer has yet to pay.
amount_paid
integer The amount that has been paid.
attempts
integer The number of payment attempts, successful and failed, that have been made against this order.
created_at
integer The Unix timestamp at which the order was created.
currency
string The 3-letter ISO currency code for the payment. Currently, we only support INR.
entity
string Name of the entity. Here, it is order.
id
string A unique identifier of the order created. For example order_1Aa00000000002.
notes
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”.
receipt
string A user-entered unique identifier of the order. For example, Receipt No. 1. You should map this parameter to the order_id sent by Razorpay Curlec.
status
string The status of the order.
You can create a payment against the order_id after you create an order.
Once you have generated an order_id, use it to create a payment and charge the customer. The following endpoint creates a payment to charge the customer.
curl -u [YOUR_KEY_ID]:[YOUR_KEY_SECRET] \-X POST https://api.razorpay.com/v1/payments/create/recurring \-H "Content-Type: application/json" \-d '{"amount": 1000,"currency": "INR","order_id": "order_NYMptG6ChGaFgj","email": "gaurav.kumar@example.com","contact": "9000090000","customer_id": "cust_N8fv8Nftx5hato","token": "token_NZveVUfP5fn0fq","recurring": "1","notes": {"invoice_number": "IRS1245","goods_description": "Digital Lamp"}}'
{"razorpay_payment_id" : "pay_1Aa00000000001"}
UPI Payments
- We recommend sending a pre-debit notification to the customer 48 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.
- For UPI, do not create subsequent payments on the last day of the cycle. This will cause the payment to fail.
- Pre-Debit Notification (PDN) Failure Handling: If the pre-debit notification fails to reach the customer, either due to a PDN initiation error or a delivery failure. Razorpay automatically retries the notification request. If the notification remains undelivered after 3 attempts, the payment is marked as failed with the following details:
- Error Description: Unable to Notify the Customer.
- Error Reason: pre_debit_notification_failed.
amount
mandatory
integer The amount associated with the payment in smallest unit of the supported currency. For example, 2000 means ₹20. Must match the amount in
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 in
mandatory
string The customer's email address. For example, gaurav.kumar@example.com.
contact
mandatory
string The customer's contact number. For example, 9000090000.
customer_id
mandatory
string Unique identifier of the customer, obtained from the response of Customer API.
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
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.
notes
mandatory
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”.
invoice_number
mandatory
string Invoice number of the generated invoice. Ensure that each payment has a unique invoice number, with a length of fewer than 40 characters.
goods_description
optional
string Description of the goods. For example, Digital Lamp.
Given below is a list of possible errors you may face while creating a Recurring Payment.
- Description: The payment failed as the amount does not match the amount provided at the time of mandate creation.
- Next Steps: Pass the transaction amount less than or equal to the mandate amount.
- Description: Payment was unsuccessful as it was declined by your bank. Any amount deducted will be refunded within 5-7 working days.
- Next Steps: Retry after some time.
- Description: Payment processing failed due to error at bank or wallet gateway
- Next Steps: Retry after some time.
- Description: Payment was unsuccessful due to a temporary issue at your bank. Any amount deducted will be refunded within 5-7 working days.
- Next Steps: Retry after some time.
- Description: Payment was unsuccessful due to a temporary issue. Any amount deducted will be refunded within 5-7 working days.
- Next Steps: Retry after some time.
- Description: Day of debit does not match the debit execution rule for the payer. Please ensure execution day matches the execution rule.
- Next Steps: Please ensure execution day matches execution rule.
- Description: Payment processing failed due to error at bank or wallet gateway.
- Next Steps: Retry after some time.
- Description: Payer account linked to the customer's VPA has changed. Please request the customer to either change it to the bank account used during mandate registration or register a new mandate for them.
- Next Steps: Please request the customer to either change it to the bank account used during mandate registration or register a new mandate for them.
- Description: Payment was unsuccessful due to a temporary issue. If amount got deducted, it will be refunded within 5-7 working days.
- Next Steps: Retry after 1 hour.
Is this integration guide useful?