Skip to main content
GET
Use this endpoint to fetch a list of all the payments received by a Linked Account. For this, you should send the Linked Account id in the X-Razorpay-Account API request header, as shown in the Curl example.

Response Parameters

string
Unique identifier of the payment.
string
Indicates the type of entity.
string
The payment amount represented in the smallest unit of the currency passed. For example, for an amount of ₹200.35, the value of this field should be 20035.
string
The currency in which the payment is made. We support only INR for Route transactions.
string
The status of the payment. Possible values:
  • created
  • authorized
  • captured
  • refunded
  • failed
string
The payment method used for making the payment. Here, it will be transfer.
string
Unique identifier of the order associated with the payment.
string
Description of the payment, if any.
string
The refund status of the payment. Possible values include:
  • null
  • partial
  • full
integer
The amount refunded in the smallest unit of the currency passed. For example, if the amount_refunded is 100, then it translates to 100 paise, that is ₹1. Only INR is supported.
boolean
Indicates whether the payment has been captured. Possible values:
  • true: Payment has been captured.
  • false: Payment has not been captured.
string
Customer email address used for the payment.
string
Customer contact number used for the payment.
integer
Fee (including GST) charged by Razorpay.
integer
GST charged for the payment.
string
Code for the error that occurred during payment. For example, BAD_GATEWAY_ERROR.
string
Description of the error that occurred during payment.
json object
Set of key-value pairs that can be associated with an entity. These pairs can be useful for storing additional information about the entity. A maximum of 15 key-value pairs, each of 256 characters (maximum), are supported.
integer
Timestamp, in Unix, on which the payment was created.

Errors

Code: 4xxThis error occurs when there is a mismatch between the API credentials passed in the API call and the API credentials generated on the Dashboard.Solution: Make sure the API Keys are active and entered correctly. Also, there should not be any whitespaces before or after the keys.
Code: 400This error occurs when the Linked Account is invalid or does not belong to the requested merchant.Solution: Ensure the Linked Account is valid and belongs to the requested merchant.