Upload Recurring Transactions in Bulk
After you register for recurring payments in bulk, you can upload the recurring transactions in bulk as described in this section.
Schedule Recurring Debits (new):You can now schedule recurring debits for future date by passing the
debit_datefield as another column in the YYYY-MM-DD format in the bulk upload file. You should enable this feature to schedule recurring debits. Contact your key account manager to get it enabled.
Prerequisites
- Download the sample file as in the below procedure (Step 1 to 4) and update it to include the data to be uploaded.
- Ensure that all mandatory fields in the file are filled with the correct details. The columns in the CSV file for upload are described in the following table (Expandable Text):
Description of Columns in the CSV file for uploading transactions in bulk
| Column Name | Field Type (Mandatory/ Optional) | Character Limit | Description |
|---|---|---|---|
| authpayuid | Mandatory | 20 | The authpayuid for the recurring transaction. |
| amount | Mandatory | 15 | The amount to be debited for the recurring transaction. |
| txnid | Mandatory | 50 | The transaction Id of the transaction. |
| Optional | 50 | The email ID of the customer. | |
| phone | Optional | 50 | The mobile number of the customer. |
| udf 1 | Optional | 255 | The user defined field information. |
| udf 2 | Optional | 255 | The user defined field information. |
| udf 3 | Optional | 255 | The user defined field information. |
| udf 4 | Optional | 255 | The user defined field information. |
| debit_date | Optional | 10 | The date on which you want this transaction to be charged. Format: YYYY-MM-DD. If left blank, the transaction will be processed immediately as usual. |
- Ensure that your bulk upload files are in the CSV format, as this is the only supported file type.
- Each batch can contain up to 1,00,000 records (approximately), which is the maximum number of records processed in a single batch.
- You can schedule a transaction for a future T+1 date or any date up to 3 month in advance.
- You cannot schedule a transaction for a date more than 3 month from today — such rows will be rejected/marked as failed with an appropriate error.
- If you don't provide a debit date, the transaction is processed right away.
Procedure
To upload recurring transactions using PayU Dashboard:
- Login to the Merchant Dashboard. For more information, refer to Log in to Dashboard.
- Navigate to Subscriptions.
- Click Bulk Upload at the top-right corner.
- Select any of the following file type you want to upload and click Continue.
- Recurring: This should be used for Enach mandates
- Recurring + Pre-Debit: This should be used for Cards and UPI mandates

Select the file type
- Click the Download button to download the sample file for registration or mandate.

Download the sample file
- You can either:
- Click Choose file and select the file containing all the mandates that need to be debited.
- Drag and drop the file in the dedicated area.
The file should follow the format outlined in the provided sample file. Refer to the Prerequisites section for more details.
- Click Upload to upload the file.
After uploading the file, the system will automatically check for discrepancies. If there’s an issue, an error message will appear on the screen as shown below.

After your file is successfully uploaded, a message similar to the following screenshot is displayed.
- Click Ok, Got it.
Sample Response When debit_date is Enabled
debit_date is EnabledYou will receive the following data in the response.
| Column Name | Value |
|---|---|
authpayuid | 30300810212 |
amount | 1.000000000000000000 |
transactionId | sample123497 |
status | Debit Scheduled |
pg_response | Info Response: Invoice Created Successfully |
payuid | {{PAYU_ID}} |
scheduled_debit_date | 06/10/26 19:26 |
scheduled_predebit_date | 05/10/26 23:16 |
predebit_executed_at | 05/10/26 23:16 |
recurring_executed_at | - |
previousstatus | - |
last_updated_at | 05/10/26 23:16 |
errorcode | - |
debit_date Validations Scenarios
debit_date Validations Scenarios| Error Code | PG Response | Scenario |
|---|---|---|
ERR_104 | Invalid debit_date format. Please provide the date in yyyy-MM-dd format. | Wrong format (e.g. 07/10/26, 07-10-2026) |
ERR_105 | Invalid debit_date. Debit date cannot be more than 3 months from today. | Date correctly formatted but more than 3 months from today |
ERR_106 | debit_date is not enabled | Feature not enabled for the merchant |
ERR_107 | Scheduled debit date must be at least 25 hours from now. Please choose a later date. | The provided debit date does not give enough time to complete the pre-debit notification before the scheduled debit. Standard Card / UPI requires the debit date to be at least 25 hours from the time of upload |
ERR_107 | Scheduled debit date must be at least 37 hours from now. Please choose a later date. | The provided debit date does not give enough time to complete the pre-debit notification before the scheduled debit. AMEX requires the debit date to be at least 37 hours from the time of upload |
ERR_108 | debit_date is in the past | The provided debit date is before today's date |
Updated 1 day ago
