Skip to main content
GET
List card transactions

Authorizations

X-Auth-Client
string
header
required

Your workspace client id.

All calls must include four headers:

  • X-Auth-Client — your workspace client id
  • X-Auth-Timestamp — Unix seconds
  • X-Auth-Nonce — 16-byte random hex
  • X-Auth-Signature — hex(HMAC-SHA256( {client_id}:{timestamp}:{nonce}:{raw_body}, client_secret))

The playground computes the timestamp, nonce and signature for you.

X-Playground-Client-Secret
string
header
required

Your sandbox client secret. The playground uses it to sign the request in your browser and removes it before the request is sent. Never send your client secret as a header in your own integration.

Query Parameters

card_id
string

Only this card's transactions.

limit
integer
default:20

Page size, default 20, at most 100.

Required range: 1 <= x <= 100
after
string

Cursor from page_info.next_cursor. Alias: cursor.

cursor
string

Alias of after.

type
string

Transaction type, for example funding, withdrawal, authorization, settlement, fee.

status
string

Transaction status (pending, processing, completed, failed, reversed, declined).

currency
string

Transaction currency.

start_date
string

Start of the date range.

end_date
string

End of the date range.

period
string

Date window.

card_type
string

Card type (virtual, physical).

cardholder_name
string

Cardholder name.

last_four_digit
string

Card last four digits.

amount_min
integer<int64>

Minimum amount, micro-units.

Required range: x >= 0
amount_max
integer<int64>

Maximum amount, micro-units.

Required range: x >= 0
merchant_name
string

Merchant name.

merchant_category
string

Merchant category.

merchant_mcc
string

Merchant category code.

merchant_country
string

Merchant country.

reference
string

Transaction reference.

has_fee
boolean

Only rows with (true) or without (false) a fee.

failure_code
string

Failure code.

network
string

Card network.

initiated_from
string

Channel the transaction was initiated from.

Free-text search.

Response

OK

Successful responses are wrapped in this envelope, and so are errors a handler answers itself (request body and field validation, some not-found and conflict cases, ORG_NOT_ACTIVE): success is false and error carries a code and message. Errors raised by authentication and by the services behind a handler are a Problem instead.

success
boolean
required

true on success

timestamp
string<date-time>
required

When the response was written.

data
object

The payload; its shape is given per operation. Omitted when there is none.

error
object
message
string

Human-readable summary; omitted when empty.

metadata
object

List metadata. Page lists set page, per_page, total and total_pages; offset and cursor lists set limit, offset, has_more and next_cursor. Zero and empty fields are omitted, and metadata is absent when nothing is set.

request_id
string

Set on error envelopes: the request's correlation id (req_ followed by a UUID), the same value as the X-Correlation-ID response header. Quote it to support.