Get Transactions for Cards with Filtering Options
GET/api/v1/cards/transactions
Retrieves a list of transactions for a specified card or for all cards associated with the client. The function allows filtering transactions based on the card ID.
- If 'card_id' is specified, it fetches transactions only for that card.
- If 'card_id' is not specified, it fetches transactions for all cards under the client's account. Transaction statuses include:
- 'CLEARED': Transactions that were authorized but not captured by a follow-up capture transaction. The reserved funds are released back to the wallet. For 'CLEARED' transactions, the amount is deducted as paramount in capture transactions.
- 'REVERSED': Transactions that were reversed upon an authorization reversal request. This results in the release of reserved funds back to the wallet. 'REVERSED' transactions also encompass 'CLEARED' and 'EXPIRED' statuses.
- 'EXPIRED': Transactions where the authorization expires after 7 days without a capture or reversal. The reserved funds are released back to the wallet in such cases.
Request
Query Parameters
The unique identifier of the card for which transactions are being retrieved. If not specified, transactions for all cards are retrieved.
Default value: 1970-01-01
The start date for filtering transactions, in ISO8601 format (inclusive).
The end date for filtering transactions, in ISO8601 format (inclusive).
The offset from where to start listing the transactions.
Default value: 2000
The maximum number of transactions to return.
Responses
- 200
- 422
Successful Response
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- MOD1
- MOD2
- MOD1
- MOD2
- ]
id object required
The unique identifier of the transaction.
string
string
The Bank Identification Number associated with the transaction.
card_id object
The identifier of the card involved in the transaction.
string
string
The masked number of the card for privacy.
A memo or card name associated with the card.
The current status of the card used in the transaction. 'ACTIVE' for cards that are currently in use and can be freely used for transactions, 'INACTIVE' for cards that cannot be used at the moment, and 'CLOSED' for cards that have been permanently deactivated and can no longer be used.
The email address of the card user.
The date of the transaction.
The billed amount in the transaction currency.
The currency of the billed amount.
The transaction amount.
The currency of the transaction amount.
Charge is equal Fee
The status of the transaction.
The name of the merchant where the transaction occurred.
The type of transaction. Possible types include 'AUTHORIZATION' for initial holds on funds, 'CLEARING' for the settlement of funds, 'REVERSAL' for canceling an authorization before it settles, 'REFUND' for returning funds to the cardholder, and 'ORIGINAL_CREDIT' for transactions crediting funds back to a card without a preceding debit.
If applicable, details of the previous transaction state, typically in cases of 'REVERSAL' and 'SUCCESS' transactions. It references the transaction that initially authorized the payment, usually when the state is 'PENDING AUTHORIZATION'.
The reason for transaction failure, if any.
A detailed description of the reason for the transaction's decline, if applicable.
[
{
"id": "string",
"bin": "string",
"card_id": "string",
"mask_number": "string",
"card_memo": "string",
"card_status": "string",
"card_user": "user@example.com",
"date": "string",
"billing_amount": 0,
"billing_currency": "string",
"amount": 0,
"currency": "string",
"charge": 0,
"status": "string",
"merchant_name": "string",
"type": "string",
"failure_reason": "string",
"decline_description": "string"
}
]
Validation Error
- application/json
- Schema
- Example (from schema)
Schema
- Array [
- Array [
- MOD1
- MOD2
- ]
- ]
detail object[]
loc object[]required
string
integer
{
"detail": [
{
"loc": [
"string",
0
],
"msg": "string",
"type": "string"
}
]
}