List card transactions
GET/v1/cards/transactions
Retrieves all transactions for a specific card with optional filters.
Request
Query Parameters
The ID of the card to retrieve transactions for
Filter by parent card transaction ID to group related transactions
Possible values: [PRE_AUTHORIZATION, PRE_AUTH_COMPLETION, REVERSAL_ADVICE, ONLINE_TRANSACTION, REFUND, CREDIT, BALANCE_INQUIRY, ACCOUNT_VERIFICATION]
Filter by card transaction type (PRE_AUTHORIZATION, PRE_AUTH_COMPLETION, REVERSAL_ADVICE, etc.)
Possible values: [PENDING, COMPLETED, FAILED, CANCELLED, PROCESSED]
Filter by transaction status (PENDING, COMPLETED, FAILED, CANCELLED)
Possible values: [CREDIT, DEBIT]
Filter by operation (CREDIT, DEBIT)
Filter transactions created after this date (YYYY-MM-DD)
Filter transactions created before this date (YYYY-MM-DD)
Responses
- 200
- 400
- 403
- 404
Successfully retrieved card transactions.
- application/json
- Schema
- Example (from schema)
Schema
Array [
]
data
object[]
Unique transaction ID (child ID)
Parent card transaction ID for grouping related events
Card ID (credit or debit)
Possible values: [CREDIT, DEBIT]
Type of card (CREDIT or DEBIT)
Possible values: [PRE_AUTHORIZATION, PRE_AUTH_COMPLETION, REVERSAL_ADVICE, ONLINE_TRANSACTION, REFUND, CREDIT, BALANCE_INQUIRY, ACCOUNT_VERIFICATION]
Transaction type
Possible values: [CREDIT, DEBIT]
Transaction operation (CREDIT or DEBIT)
Possible values: [PENDING, COMPLETED, FAILED, CANCELLED, PROCESSED]
Transaction status (PENDING, COMPLETED, FAILED, CANCELLED)
Transaction amount
Asset acronym
Transaction timestamp
pagination
object
{
"traceId": "string",
"message": "string",
"data": [
{
"id": "123e4567-e89b-12d3-a456-426614174000",
"parentCardTransactionId": "987fcdeb-51a2-43b8-96cd-ba321f098765",
"cardId": "987fcdeb-51a2-43b8-96cd-ba321f098765",
"cardType": "CREDIT",
"type": "PRE_AUTHORIZATION",
"operation": "DEBIT",
"status": "COMPLETED",
"amount": 100.5,
"asset": "USD",
"timestamp": "2024-07-29T15:51:28.071Z"
}
],
"pagination": {
"totalResults": 0,
"hasMoreResults": true
}
}
Invalid request payload. This can happen if required fields are missing or have invalid formats.
- application/json
- Schema
- Example (from schema)
Schema
{
"traceId": "string",
"message": "string"
}
The API key is invalid or the client does not have sufficient permissions.
- application/json
- Schema
- Example (from schema)
Schema
{
"traceId": "string",
"message": "string"
}
One of the specified resources was not found. Does not apply for empty result set.
- application/json
- Schema
- Example (from schema)
Schema
{
"traceId": "string",
"message": "string"
}