Skip to main content
Use the card-transactions resource to build a user’s card activity history. Each item represents one card-payment lifecycle, not one card-network event. The same item changes as an authorization clears, reverses, is cancelled, or is declined.
The Partner API exposes card transactions separately from deposits and withdrawals. See Manage money movements to build a combined account activity view.

​
List transactions for an account

Call GET /card-transactions with the required account_id query parameter. Results are ordered newest first.
cURL
You can restrict the results by lifecycle creation time with created_at_start and created_at_end. Send both values as RFC 3339 timestamps.
cURL
While pagination.has_next is true, pass pagination.next_page_cursor as page_cursor in the next request. A cursor belongs to this endpoint and filter set; don’t reuse it for deposits, withdrawals, or different filters.

​
Read the latest lifecycle state

Store each transaction’s id. Call GET /card-transactions/{card_transaction_id} when you need its latest status and amounts. The public statuses are:
Don’t treat the first response as final. Use updated_at and the current status; the amount can also change when clearing data arrives.

​
Interpret transaction amounts

Every transaction contains a required billing amount and may contain a merchant amount:
Amounts are base-10 integer strings in the currency’s smallest unit. Use decimals to display them: "1230" with 2 decimals is 12.30. Use a decimal or big-integer library, never floating-point arithmetic.
Don’t substitute amounts.billing when amounts.merchant is null. They answer different questions and can use different currencies.
direction describes the account effect: debit removes money and credit returns money.

​
Display merchant and decline details

The merchant object contains card-network data when available: name, city, country, and category_code. The entire object or any field can be null, so design a fallback display using description without assuming a merchant name exists. decline_reason is present only when status is declined. See Card decline reasons for guidance on user-facing messages.

​
Check ownership

Your partner token can read transactions for every account in your organization. Before listing or displaying transactions, check that the account_id belongs to the user making the request. Apply the same check when a user opens a transaction by card_transaction_id.

​
Next step

Build account activity

Combine card transactions, deposits, and withdrawals in your application.