Skip to main content
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

Path parameters

Query parameters

Response

200 — Success

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

Code examples

cURL
Node.js (axios)

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

id
string<uuid>
required

Query Parameters

page
integer
Example:

1

limit
integer
Example:

20

Response

A list of transactions for the specified card.

success
boolean
Example:

true

statusCode
integer
Example:

200

message
string
Example:

"Data retrieved successfully"

data
object[]
pagination
object