List Transactions

Returns a paginated list of the customer's transaction history — covering every transaction type recorded for the customer (crypto deposits/withdrawals, buy/sell, fiat movements, bonuses, and others), not just crypto wallet activity.

Query Parameters

Field	Type	Description
`page`	`integer`	Page number, starting at 1. Default `1`.
`pageSize`	`integer`	Items per page, 1–100. Default `50`.
`CustomerId`	`string (uuid)`	Optional. If you pass a customer ID, only that customer's transactions are returned. If you leave it out, transactions for all customers are returned, and each transaction includes a `customerId` field showing who it belongs to.

Response envelope

Like List Wallets, this returns { "data": [...], "pagination": {...} } rather than the standard envelope; the request ID is in the X-Request-Id response header, not the body.

Response Fields

Field	Type	Description
`data[].id`	`string (uuid)`	Transaction identifier
`data[].txId`	`string`	Internal transaction reference code
`data[].date`	`string (date-time)`	Transaction date
`data[].accountName`	`string`	Customer's name on the transaction
`data[].name`	`string`	Wallet/product display name, or the buy/sell pair (e.g. `USDT/USD`), depending on transaction type
`data[].type`	`string`	Transaction type/subtype (e.g. `Withdraw Crypto`, `Buy`)
`data[].wallet`	`string`	Wallet or trading pair the transaction was executed against
`data[].network`	`string`	Blockchain network, for crypto transactions
`data[].address`	`string`	On-chain or bank address/account involved
`data[].amount`	`string`	Gross transaction amount, pre-formatted for display; format varies by transaction type
`data[].fee`	`number`	Fee charged
`data[].netAmount`	`number`	Net amount after fees
`data[].receivedAmount`	`number`	Amount received by the counterparty, where applicable; otherwise `null`
`data[].status`	`string`	Transaction status (e.g. `Approved`, `Pending`, `Failed`)
`data[].adminStatus`	`string`	Internal admin review status, if applicable
`data[].description`	`string`	Transaction description, if any
`data[].remarks`	`string`	Admin remarks, if any
`data[].merchantName`	`string`	Merchant name, for card/merchant transactions
`data[].isFiatOrCrypto`	`string`	Transaction subtype (`Fiat` or `Crypto`)
`data[].txSubtype`	`string`	Transaction sub-type classification, if applicable
`data[].transactionReference`	`string`	On-chain transaction reference/hash, where applicable
`data[].action`	`string`	Underlying action performed (e.g. `Consume`, `Reversal`, `Refund`)
`data[].actionType`	`string`	Action sub-classification
`data[].isWhiteListed`	`boolean`	Whether the destination address is travel-rule whitelisted
`data[].payeeId`	`string (uuid)`	Beneficiary identifier, if the transaction targeted a saved beneficiary
`data[].favouriteName`	`string`	Saved beneficiary's display name
`data[].payeeStatus`	`string`	Beneficiary verification status note, if unverified; otherwise empty
`data[].crossBoarderFee`	`number`	Cross-border fee component, if applicable
`data[].txWith`	`string`	Counter-currency involved in a buy/sell/swap
`data[].senderName`	`string`	Sender's name, for incoming bank transfers
`data[].senderBankName`	`string`	Sender's bank name, for incoming bank transfers
`data[].senderBankAccountNumber`	`string`	Sender's bank account number, for incoming bank transfers
`data[].mccCode`	`string`	Merchant category code, for card transactions
`data[].localCurrency`	`string`	Local settlement currency, if different from the transaction currency
`data[].localAmount`	`number`	Amount in the local settlement currency
`data[].note`	`string`	Additional note, if any
`data[].postSettlementAmount`	`number`	Post-settlement amount, if the transaction has settled
`data[].postSettlementDate`	`string (date-time)`	Post-settlement date, if applicable
`pagination.total`	`integer`	Total matching transactions across all pages
`pagination.limit`	`integer`	Page size used
`pagination.offset`	`integer`	Number of items skipped before this page
`pagination.hasMore`	`boolean`	Whether a further page is available

Note: this endpoint surfaces the same internal transaction record used across every product line (crypto, fiat, cards, bonuses), rather than a crypto-wallet-specific projection. Fields such as senderBankAccountNumber, mccCode, and localCurrency are only ever populated for non-crypto transaction types and will be null/absent on crypto deposit/withdrawal rows.

Request

Responses