Batch Operations
Create Recurring Payments using the batch upload feature from the Razorpay Dashboard.
You can
and in bulk using the batch feature available from the Dashboard. You can check the status of the bulk action in the respective batch reports.The following table lists the various states of a batch file:
You can create registration links in bulk using the Batch Upload feature.
The following table lists the fields required to create a registration link:
After a batch file is processed, you can download the batch report from the Dashboard. Click the batch_id to view details of how many rows were uploaded, how many rows were processed successfully and how many rows failed.
Click Download Report to download the report. This report has the following additional fields that give you information about the authorisation link or the reason for failure.
Status
The status of the authorisation link. Possible values:
successfailed
authorization_link_id
The unique identifier for the authorisation link. For example, inv_E7vb0PqKa4VpBc.
authorization_link
The short URL for the authorisation link. For example, https://rzp.io/i/Abcd5.
link_status
The status of the authorisation link. For example, issued.
created_at
Timestamp, in Unix format, when the authorisation link was created. For example, 1580134092.
Error Code
The error code for the failure. For example, BAD_REQUEST_ERROR.
Error Description
The reason for the error. For example:
Bank code provided is invalid.expire_by should be at least 15 minutes after current timeThe ifsc code field is required.
Once you have the list of tokens you can either:
- .
- .
The following table lists the fields required to charge a token:
token
mandatory
The unique identifier for the token. For example, token_1Aa00000000001.
customer_id
mandatory
The unique identifier of the customer. For example, cust_1Aa00000000001.
receipt
optional
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.
description
optional
A user-entered description for the payment. For example, 12 p.m. Meals.
notes[custom 1]
optional
Key-value pair that can be used to store additional information about the entity. You can add up to 5 custom notes in the following format:
- notes[portfolio id]
- notes[transaction id]
Once a batch file is processed, you can download the processed file from the Dashboard. Click the batch_id to view details of how many rows were uploaded, how many rows were processed successfully and how many rows failed.
Click Download Report to download the processed file. This file has the following additional fields that give you information about the authorization link or the reason for failure.
order_id
The unique identifier linked to the order for the payment. For example, order_E16Yt72tHs34li.
payment_id
The unique identifier for the payment. For example, pay_E16YtBnEk38fAm.
Error Code
The error code for the failure. For example, BAD_REQUEST_ERROR.
Error Description
The reason for the error. For example, Payment amount exceeds the maximum amount allowed.
Was this page helpful?