Card transactions
Cards
List Card Transactions
Retrieve transaction history for a single card with optional filtering by date range, type, and status.
GET
Card transactions
Overview
GET /cards/{id}/transactions returns the full transaction history for one card — fundings, withdrawals, merchant authorizations, settlements, refunds, and any cross-border charges. The response is paginated.
When to use it
- Render a per-card transaction view to the cardholder.
- Reconcile a card’s activity with merchant statements.
- Investigate a disputed charge.
Prerequisites
- The card must belong to your company.
Request
Headers
| Name | Required | Description |
|---|---|---|
Authorization | Yes | Bearer <access_token> |
Path parameters
| Name | Type | Description |
|---|---|---|
id | string | Card ID (UUID). |
Query parameters
| Name | Type | Default | Description |
|---|---|---|---|
page | integer | 0 | 0-indexed page number. (Note: this differs from the rest of the API, which uses 1-indexed pagination.) |
limit | integer | 50 | Items per page. Max recommended: 100. |
fromDate | string | — | ISO 8601 date or datetime. Includes transactions on/after this instant. |
toDate | string | — | ISO 8601 date or datetime. Includes transactions strictly before this instant. |
type | string | — | Filter by transaction type. See Glossary → Transaction for values. |
status | string | — | Filter by status. One of PENDING, PROCESSING, SUCCESS, FAILED. |
includeRaw | boolean | false | If true, attach the raw upstream-issuer payload to each transaction. For debugging. |
sync | boolean | true | If true (default), force-refresh from the upstream issuer. Set false to read from Cartevo’s local cache only. |
Response
200 — Success
| Field | Type | Description |
|---|---|---|
data[].id | string | Transaction ID. Use to fetch full detail or in support tickets. |
data[].category | string | Always "CARD" for this endpoint. |
data[].type | string | One of AUTHORIZATION, SETTLEMENT, FUNDING, WITHDRAWAL, TERMINATION, DECLINE, REVERSAL, REFUND, CROSS-BORDER. |
data[].status | string | One of PENDING, PROCESSING, SUCCESS, FAILED. |
data[].amount | number | Transaction amount in currency. |
data[].description | string | Human-readable description (often merchant + city for AUTHORIZATION / SETTLEMENT). |
meta | object | Standard pagination metadata. See API Conventions → Pagination. |
Pagination quirk: This endpoint uses page=0 for the first page (0-indexed), unlike the rest of the API. We are aligning this in a future release.
Error responses
| Status | Trigger |
|---|---|
404 | Card does not exist or belongs to another company. |
400 | Invalid fromDate / toDate format, or invalid type / status value. |
Code examples
cURL
Node.js (axios)
Related
- Cards Overview → Supported transaction types
GET /cards/{id}— current card balance and status.- Webhooks → Transaction events — receive these events in real time instead of polling.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.