Refunds
1. Introduction
When the merchant wants to return the funds to their customer, for example, if the customer returned an item, merchant can initiate a refund. Merchant can either do a full refund or a partial refund.
Important Information• The refund amount cannot be greater than the transaction amount.
• Merchant can perform multiple partial refunds, as long as the sum of partial refunds does not exceed the original transaction amount.
Understanding the various Refund Status codes:
| Refund Status | Status Code | Description |
|---|---|---|
| CANCELLED | 0699 | A transaction which has been initiated for a full refund before it was settled at BillDesk is marked as cancelled. A cancelled transaction does get processed for a refund back to the customer. |
| REFUND | 0799 | When a transaction has been partially refunded before/after settlement or a full refund after settlement is marked as refund. |
Refund of Transaction - Validity:
| Transaction Flow | Refund Applicability on Transactions with Date as |
|---|---|
| Token based Transaction | Current Date - Transaction Date <= 180 Days |
| Guest Checkout Transaction | Current Date - Transaction Date <= 90 Days |
2. Salient Features
- A single Refund API to initiate refunds across various payment methods i.e. cards/ netbanking/ wallets etc.
- Allows merchant to automate the process of initiating refunds from their system without needing operations team to do this through the dashboard
3. API Orchestration
The orchestration of the APIs/ workflow has been explained below:
Refund Use Cases:
API Reference | Description |
|---|---|
Use the API to invoke the refund workflow. The transaction amount must be less than or equal to the original transaction amount. For sample code click here. | |
Use the API to retrieve refund details based on refund id or merchant refund reference number. For sample code click here. |