Fetch Refund With ID
GET
/v1/refunds/:id
Click to copy
Use this endpoint to retrieve the refund using the id.
Is this page helpful?
1curl -u [YOUR_KEY_ID]:[YOUR_KEY_SECRET] \23-X GET https://api.razorpay.com/v1/refunds/rfnd_DfjjhJC6eDvUAi
Success
Failure
1{2"id": "rfnd_DfjjhJC6eDvUAi",3"entity": "refund",4"amount": 6000,5"currency": "MYR",6"payment_id": "pay_EpkFDYRirena0f",7"notes": {8"comment": "Issuing a normal refund"9},10"receipt": null,11"acquirer_data": {12"arn": "10000000000000"13},14"created_at": 1589521675,15"batch_id": null,16"status": "processed",17"speed_processed": "normal",18"speed_requested": "normal"19}
Path Parameters
id
*
string
Unique identifier of the refund which is to be retrieved.
Response Parameters
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 MYR 30.00, it will be 3000
.
currency
string
The currency of payment amount for which the refund is initiated.
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.
status
string
Indicates the state of the refund. Possible values:
pending
: This state indicates that Curlec is attempting to process the refund.processed
: This is the final state of the refund.failed
: A refund can attain the failed state in the following scenarios:
Refund is not possible for a payment which is more than 6 months old.
speed_requested
string
The processing mode of the refund seen in the refund response.
This attribute is seen in the refund response only if the speed
parameter is set in the refund request.
Possible value:
normal
: Indicates that the refund will be processed via the normal speed. The refund will take 5-7 working days.
speed_processed
string
This is a parameter in the response which describes the mode used to process a refund.
This attribute is seen in the refund response only if the speed
parameter is set in the refund request. Possible value:
normal
: Indicates that the refund has been processed by the payment processing partner. The refund will take 5-7 working days.
Errors
The API {key/secret} provided is invalid.
Error Status: 4xx
The API credentials passed in the API call differ from the ones generated on the Dashboard.
Solution
The requested URL was not found on the server.
Error Status: 400
Possible reasons:
- The URL is wrong or is missing something.
- A GET API is executed by POST method.
Solution
_id is not a valid id
Error Status: 400
The refund id entered is invalid.
Solution
The id provided does not exist
Error Status: 400
The refund id entered is incomplete or invalid.
Solution
Fetch Refund With ID
GET
/v1/refunds/:id
Click to copy
Use this endpoint to retrieve the refund using the id.
Is this page helpful?
Path Parameters
id
*
string
Unique identifier of the refund which is to be retrieved.
Response Parameters
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 MYR 30.00, it will be 3000
.
currency
string
The currency of payment amount for which the refund is initiated.
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.
status
string
Indicates the state of the refund. Possible values:
pending
: This state indicates that Curlec is attempting to process the refund.processed
: This is the final state of the refund.failed
: A refund can attain the failed state in the following scenarios:
Refund is not possible for a payment which is more than 6 months old.
speed_requested
string
The processing mode of the refund seen in the refund response.
This attribute is seen in the refund response only if the speed
parameter is set in the refund request.
Possible value:
normal
: Indicates that the refund will be processed via the normal speed. The refund will take 5-7 working days.
speed_processed
string
This is a parameter in the response which describes the mode used to process a refund.
This attribute is seen in the refund response only if the speed
parameter is set in the refund request. Possible value:
normal
: Indicates that the refund has been processed by the payment processing partner. The refund will take 5-7 working days.
Errors
The API {key/secret} provided is invalid.
Error Status: 4xx
The API credentials passed in the API call differ from the ones generated on the Dashboard.
Solution
The requested URL was not found on the server.
Error Status: 400
Possible reasons:
- The URL is wrong or is missing something.
- A GET API is executed by POST method.
Solution
_id is not a valid id
Error Status: 400
The refund id entered is invalid.
Solution
The id provided does not exist
Error Status: 400
The refund id entered is incomplete or invalid.
Solution
1curl -u [YOUR_KEY_ID]:[YOUR_KEY_SECRET] \23-X GET https://api.razorpay.com/v1/refunds/rfnd_DfjjhJC6eDvUAi
Success
Failure
1{2"id": "rfnd_DfjjhJC6eDvUAi",3"entity": "refund",4"amount": 6000,5"currency": "MYR",6"payment_id": "pay_EpkFDYRirena0f",7"notes": {8"comment": "Issuing a normal refund"9},10"receipt": null,11"acquirer_data": {12"arn": "10000000000000"13},14"created_at": 1589521675,15"batch_id": null,16"status": "processed",17"speed_processed": "normal",18"speed_requested": "normal"19}