Refunds
Integrate with Refunds API using partner auth.
You can make full or partial refunds to customers. Know more about
.Refunds Can be Made Only on Captured Payments
You can initiate refunds only on those payments that are in captured state. A payment in authorized state is auto-refunded if not captured within 5 days of creation.
Given below are the sample codes to create a full refund. You should send the account_id of the sub-merchant using X-Razorpay-Account in the header. Refer to the
id
mandatory
string The unique identifier of the payment which needs to be refunded.
amount
optional
integer The amount to be refunded. Amount should be in the smallest unit of the currency in which the payment was made.
- For a partial refund, enter a value lesser than the payment amount. For example, if the payment amount is S$1,500.00 and you want to refund only S$500.00, you must pass
50000. - For full refund, enter the entire payment amount. If the
amountparameter is not passed, the entire payment amount will be refunded.
notes
optional
json object Key-value pairs used to store additional information. A maximum of 15 key-value pairs can be included.
receipt
optional
string A unique identifier provided by you for your internal reference.
id
string The unique identifier of the refund. For example, rfnd_FgRAHdNOM4ZVbO.
entity
string Indicates the type of entity. Here, it is refund.
amount
integer The amount to be refunded (in the smallest unit of currency).
For example, if the refund value is S$30.00 it will be 3000.
payment_id
string The unique identifier of the payment for which a refund is initiated. For example, pay_FgR9UMzgmKDJRi.
created_at
integer Unix timestamp at which the refund was created. For example, 1600856650.
batch_id
string This parameter is populated if the refund was created as part of a batch upload. For example, batch_00000000000001.
notes
json object Key-value store for storing your reference data. A maximum of 15 key-value pairs can be included. For example, "note_key": "Beam me up Scotty”.
receipt
string A unique identifier provided by you for your internal reference.
acquirer_data
array A dynamic array consisting of a unique reference number (either RRN, ARN or UTR) that is provided by the banking partner when a refund is processed. This reference number can be used by the customer to track the status of the refund with the bank.
Given below is the sample code for Fetch all Refunds API. Pass the account_id of the sub-merchant using X-Razorpay-Account in the header. Know more about
By default, only the last 10 refunds are returned. You can use count and skip query parameters to change that behaviour.
from
optional
integer Unix timestamp at which the refunds were created.
to
optional
integer Unix timestamp till which the refunds were created.
count
optional
integer The number of refunds to fetch. You can fetch a maximum of 100 refunds.
skip
optional
integer The number of refunds to be skipped.
id
string The unique identifier of the refund. For example, rfnd_FgRAHdNOM4ZVbO.
entity
string Indicates the type of entity. Here, it is refund.
amount
integer The amount to be refunded (in the smallest unit of currency).
For example, if the refund value is S$30.00 it will be 3000.
payment_id
string The unique identifier of the payment for which a refund is initiated. For example, pay_FgR9UMzgmKDJRi.
created_at
integer Unix timestamp at which the refund was created. For example, 1600856650.
batch_id
string This parameter is populated if the refund was created as part of a batch upload. For example, batch_00000000000001.
notes
json object Key-value store for storing your reference data. A maximum of 15 key-value pairs can be included. For example, "note_key": "Beam me up Scotty”.
receipt
string A unique identifier provided by you for your internal reference.
acquirer_data
array A dynamic array consisting of a unique reference number (either RRN, ARN or UTR) that is provided by the banking partner when a refund is processed. This reference number can be used by the customer to track the status of the refund with the bank.
Was this page helpful?