Payments endpoint
Last updated: April 29, 2022
The payments endpoint allows you to search for all payments within parameters you specify.
Note
The payments endpoint is not available in the sandbox environment.
Tip
If you're not familiar with creating API requests, you might want to take a look at our Postman guide.
Information
No payments from before February 7th, 2019 at 00.00.00 UTC will appear when using the payments endpoint. To view payments from before this time, please contact our Support team.
Use the details below to set up your request. To set the timeframe of your request, replace {start-date-time} and {end-date-time} with your desired start and end dates in ISO format (yyyy-mm-ddThh:mm:ss). Please note that the time zone for the request will be UTC.
get
https://api.checkout.com/reporting/payments
You can filter the data in the payments endpoint by using the parameters below:
| Filter | Parameter |
|---|---|
Date-Time |
|
Payment ID |
|
Reference |
|
You can also limit results.
If the payments endpoint returns a response, then the request was successful. Below, you can find an example response from the payments endpoint, in addition to a list of the fields that will be shown.
Information
By default, the payments endpoint returns up to 200 payments per page of results. You can change this limit if you'd like.
The payments endpoint is designed to present your payments as clearly as possible. Depending on your parameters, you may receive a large response. If you’re looking for data even more quickly, try amending the parameters in the request. Regardless of the parameters in your request, the payments endpoint’s response can be split into four sections, each of which is outlined below.
This section displays all payment information in accordance with your chosen parameters. The table below shows the full list of parameters displayed, and how to decipher them.
| Parameter | Description |
|---|---|
| The unique payment ID. Previously, this was called transaction_id. |
| The currency of the payment when processed by the cardholder. |
| The currency of the payment when paid out to you. |
| The date on which the payment was initiated. |
| The name of the channel where the payment was initiated. |
| An optional ID used for tracking payments. Previously, this was called track_id. |
| The payment method. For example, Visa or Mastercard. |
| The card type. For example, credit or debit card. |
| The card category. For example, consumer or commercial. |
| The country of the issuing bank. |
| The country of the merchant bank. |
| An optional, user-defined ID that identifies the business. |
This section outlines all the actions — authorization, void, capture, refund, retrieval, and chargeback — which have been administered to a payment. The table below outlines and explains the parameters of the report.
| Parameter | Description |
|---|---|
| The type of action. For example, authorization, capture, refund, chargeback, chargeback reversal, or payment-related fee. |
| The unique ID associated with an action (referred to as a charge ID in the Hub). |
| The date on which the action occurred. |
| The response code of the action (payment request). |
| Further information about the response code. |
The amounts summary shows the amounts corresponding with a particular action. The table below shows the full list of these parameters and their explanations.
| Parameter | Description |
|---|---|
| Describes an amount/fee associated with an action. For example, a gateway fee, capture fee and capture amount would all be associated with the capture action. |
| Specifies an associated date with a specific amount (some external fees are returned after the associated action). |
| The associated amount in the processing currency (if applicable). Numerical values up to 8 decimal places are provided in the response. |
| The associated amount in the payout currency. Numerical values up to 8 decimal places are provided in the response. |
Information
If you're looking for the outcome of a particular chargeback, please allow up to 60 days from the date the evidence was provided.
You might have noticed several links at the bottom of the response from the payments endpoint. Let’s take a look at each one.
This link allows you to focus on a particular payment that has been included in the response. As you can see, the final component of the link is pay_sv6ikhu36mgepkm3l22pztvywa, which corresponds to the payment ID for that particular payment in the response.
This link lets you move to the next page of results. Results are paginated at a payment level. By default, a page contains 200 results — though you can change this limit if you'd like.
This link provides the URL associated with the current request.
In addition to the JSON format described above, you can download a CSV report containing the data from the payments endpoint. To do this, follow the steps below.
In the URL for the payments endpoint, add /download after /payments. An example of this can be found below:
If you are using Postman or an equivalent application, rather than sending the GET request, use the Send and Download functionality for the GET request to download the CSV report.
Information
Using /download will return a CSV containing all your payments unlike a standard request, which is paginated.
Tip
You can also get a CSV report by amending the Headers section of the request to accept a value of text/csv. Note that this will contain the same paginated results as the JSON.
In your CSV file, a single payment is uniquely identified by an ID in the first column of the table and will be made of multiple rows, each of them reflecting a fee or an amount applied to a different action within the payment lifecycle.
Regardless of the parameters in your request, the payments endpoint’s CSV file will have the same overall structure and columns titles which can be split into three sections.
This section displays all payment and card attributes in accordance with your chosen parameters.
This section outlines all the actions — authorization, void, capture, refund and chargeback — which have been administered to a payment.
This section provides details of the associated amounts to an action in both the processing and the payout currencies.
Responses from the payments endpoint can be large, depending on the number of payments you process and the parameters you have chosen. By default, each page includes 200 results.
To limit your results, add limit= followed by a number of your choice (up to 500) at the end of the URL.
For example:
Information
You can only limit results for JSON responses. A CSV will always contain all possible results.