Refunds Dashboard
Order cancellations are an unfortunate reality for any business. Customers may cancel an order, return part of the order, or the full order. Merchants may not have the resources to fulfill the order and must cancel it. Therefore, it is imperative for merchants collecting payment online can refund the payment to the merchant.
Types of Refunds
Refunds can be classified into two types:
- Partial refund: Where the refund amount is less than the payment amount. This means the merchant is refunding only part of the payment done by the customer. This happens when only part of the order is canceled.
Ex. Customer purchases two products from merchant or value Rs. 500 and Rs. 7000. Customer pays a total of Rs. 7,500 to the merchant via online payment. Now the customer returns product 1 of value Rs. 500. Now, the merchant only must return Rs. 500 to the customer (instead of the transaction amount of Rs. 7,500). - Instant refund: If the instant refund is enabled for you, the refunds are completed within 5 minutes of the refund request.
- Full refund: Where the refund amount is equal to the payment amount. This means that the merchant is refunding the entire payment done by the customer for a transaction. This happens when either merchant or customer cancels the entire order.
Ex. Customer purchases two products from merchant or value Rs. 500 and Rs. 7000. Customer pays a total of Rs. 7,500 to the merchant via online payment. Now the customer returns both the product. Now, the merchant must return Rs. 7,500 to the customer.
Understanding Refunds
How to get a Refund from various PayU India products
PayU offers refunds for payments made using PayU India products: PayU Offers, PayU Partners, Split Settlements, etc. Generally, you need to initiate a refund request using any of the following methods:
- Cancel Refund Transaction API: For more information, refer to Refund Transaction API.
- PayU Dashboard: For more information, refer to Refunds Dashboard.
How long does it take to get a refund?
Refunds will take between 5-21 days for the refund amount to reflect in your customer’s bank account. In the case of Net Banking transactions, certain government banks may take some more days. You will be communicated over email with the status (successful or failed) once the request for a refund is processed.
How does Chargeback differ from Refunds?
A chargeback is raised by the customer to the issuing bank for many reasons like a fraud transaction, unsatisfactory product or service delivery, etc. In refunds, it is initiated by you (merchants) after your customer requests for a refund or a transaction has failed for the customer.
Initiate a Refund using Dashboard
You can issue refunds easily with PayU Dashboard.
To initiate the refund using Dashboard:
- Login to the Merchant Dashboard.
- Navigate to Track > Transactions.
- Click the transaction ID to view the transaction details.
The transaction details are displayed for the transaction.

- Click Send Refund at the top-right corner of the page.
The Refund Payment pop-up page is displayed.

- Enter the amount to be refunded in the Refund Payment field.
- Click Send Full Refund if the full amount is refunded or Send Partial Refund or partial amount is refunded.
Note: Refund amount will be reflected in customer’s bank account in 5-6 working days.
Upload Bulk Refunds using Dashboard
Understanding Upload Bulk Refunds
Bulk refunds let merchants initiate multiple refund requests at after uploading a file through the PayU Dashboard. PayU processes the uploaded file row by row: each row represents one refund request and can be accepted for processing or rejected if it does not meet the file requirements. A batch output file provides the processing result for each row, helping merchants review refund outcomes.
Use this format to prepare the merchant-level file for a bulk refund upload. The file contains six columns: the first two columns are mandatory, followed by optional and Closed Loop Wallet-only conditional fields.
Every file you upload containing refund information on Dashboard is known as a batch. After a batch is uploaded successfully, it is picked up for processing within 60 mins. After a batch is picked for processing the status against that batch gets updated. A batch file can be in either of these states:
- UPLOADED: This is the initial state of the file when it is uploaded. Once you upload a file, it stays ‘uploaded’ and gets picked up for processing within 60 mins.
- QUEUED: This state indicates that the file is read and refunds are queued in the system for processing.
- PROCESSING: This state indicates that the batch file is getting processed.
- COMPLETED: This is the final state of the file. It indicates that all the rows in the batch file were processed, either successfully or unsuccessfully. Merchants can download the batch output file from the dashboard to check the status of each refund.
After a batch crosses the Uploaded stage, the Download Output option gets enabled for that batch. You can then download the output file for the batch to check the refund status when required.
Supported file types
Bulk refund uploads support .xls, .xlsx, and .csv files.
File requirements
- The first two columns,
transactionidandamount, are mandatory. - Do not change the first two column headers.
- Include all six columns in the file, in the order shown below. Leave fields that do not apply blank.
- Use a unique filename for each upload.
Merchant-level fields
The following fields are defined at the merchant level:
| Field name | Description | Requirement |
|---|---|---|
transactionid | Unique PayU Transaction ID (PayU ID) for which the refund is processed. | Mandatory |
amount | Refund amount. | Mandatory |
remarks | Additional information or notes for reference and future tracking. | Optional |
reference_id | Merchant's unique refund reference ID for merchant-side tracking and reconciliation. | Optional |
refund_type | Applicable only to Closed Loop Wallet merchants; other merchants may leave blank. Supported value: wallet. | Conditional: Closed Loop Wallet only |
customer_phone | Customer's registered mobile number. Required only for Closed Loop Wallet refund processing; other merchants may leave blank. Supported value: a 10-digit phone number. | Conditional: Closed Loop Wallet only |
The first two fields, transactionid and amount, are mandatory for every merchant. The remarks and reference_id fields are optional. The refund_type and customer_phone fields are conditional: use them for Closed Loop Wallet refunds and leave them blank for other merchants. For Closed Loop Wallet refunds, set refund_type to wallet and provide the customer's registered 10-digit mobile number in customer_phone.
Examples
The following examples show the six-column order. They are illustrative rows only.
Standard refund row
For a non-Closed Loop Wallet refund, the two conditional fields are blank:
transactionid,amount,remarks,reference_id,refund_type,customer_phone
PayUTxn12345,500.00,Customer return,MER-REF-1001,,Closed Loop Wallet refund row
For a Closed Loop Wallet refund, provide wallet and the customer's registered 10-digit phone number:
transactionid,amount,remarks,reference_id,refund_type,customer_phone
PayUWallet67890,250.00,Wallet refund,MER-REF-1002,wallet,9876543210Procedure
To initiate refunds using bulk upload:
- Log on to PayU Merchant Dashboard and select Transactions.

- Select the Batch Refunds tab.

A list of batches uploaded in the past is displayed on this page. The batches can be filtered based on the date of upload and batch status.
-
Click Upload Batch Refund to upload a batch of refunds.
The Batch Upload pop-up page is displayed with instructions to upload the file.

- Use the Download sample file option to download the Excel file template that can be used for including the refund information:
- Update the following columns of the Excel. For more information, refer to Understanding Bulk Upload.
- transactionid
- amount
- remarks
- reference_id
- refund_type
- customer_phone
- Save the file.
- Update the following columns of the Excel. For more information, refer to Understanding Bulk Upload.
Notes:
- The first two columns,
transactionidandamount, are mandatory.- Do not change the first two column headers.
- Include all six columns in the file, in the order shown below. Leave fields that do not apply blank.
- Use a unique filename for each upload.

-
Browse for the desired file from your system and click Upload.
A message is displayed after the file is successfully uploaded.

- Click Submit.
A ‘success’ message is displayed with the number of total records uploaded for processing.

After the batch is uploaded, the status is displayed as Uploaded under the Batch Refunds tab.

-
Click the batch ID to open the batch details page.
All refunds uploaded within that batch, their details along with present status are displayed on this page.
A refund can be in any of these states:
- IN PROGRESS: When the refund is initiated and is being processed.
- REQUESTED: When the refund is sent to the bank for offline processing. In such cases, it takes 5-7 business days for the credit to reflect into the customer’s account.
- SUCCESS: When the refund is successfully processed
- FAILURE: When the refund failed while processing with the PG. The merchant can download the output file to see the failure reason.
- REJECTED: When the refund got rejected during initiation due to some validation failures. The merchant can download the output file to see the failure reason.
Track Refunds on Dashboard
The Refunds tab of the _Transactions_page summarizes all the refunds for the selected date range. You can view the detailed transaction records and the option to export the transaction records for the selected period.
To view the refunds for a preferred interval:
-
Login to the Merchant Dashboard. For more information, refer to Log in to Dashboard.
-
Navigate to Track > Transactions and then select the Refunds tab.
The Refunds tab of the Transactions page is displayed.

- Below the Transactions Overview, click the drop-down for calendar view
- Select the option Today to view the summary of transactions triggered for the day.
Updated 8 days ago
