Skip to main content
Every balance change on an account is a transaction: deposits, withdrawals, trades, fees, and transfers. Use the feed to show a customer their activity, to drive your own ledger, to reconcile against balances, and to feed reporting. Each transaction lists the entries behind it, so you can see exactly which account and asset moved, in which direction.

What’s available

The transaction model

A transaction has three parts:
  1. What happened: a transactionType and a status.
  2. When: createdAt, and endedAt once the transaction reaches a final state.
  3. Whose balances moved: a list of entries (the subaccounts field), each naming an accountId, an assetType, an amount, a balanceType, and a direction (CREDIT for funds in, DEBIT for funds out). balanceType is AVAILABLE for a settled movement, HOLD for an amount set aside for an in-flight debit, or PENDING for a credit not yet settled. Only AVAILABLE entries change the TOTAL balance.
One transaction can carry several entries. A trade debits one asset and credits another. An order allocated across accounts touches each of them. Summing the entries per account and asset is how you reconcile the feed against balances.

Transaction types

Statuses

endedAt is set when the transaction reaches POSTED or CANCELED, and absent while it’s PENDING. On-chain deposits and withdrawals also carry transactionHash, the blockchain transaction hash, once settled.

Integration steps

Step 1: List transactions

GET /v4/accounts/{accountId}/transactions Returns the account’s transactions, most recent first. Page with limit and after.
A withdrawal carries the transactionId of its WITHDRAWAL transaction, and a deposit attribution is keyed by its DEPOSIT transaction ID. Pass either as transactionIds to pull the matching entry. For a daily, file-based reconciliation of positions and activity, see Reconciliation files.
For an ongoing sync, poll with startDate set to your last sync point and re-check PENDING transactions until they reach POSTED or CANCELED. A transaction’s status and endedAt change after it first appears.

Step 2: Allocate funding

Under construction. GET and POST /v4/accounts/{accountId}/transactions/allocations are in the reference for allocating pre-funded USD between a funding account and customer accounts, but they return mocked data only today. This section will be updated when the endpoints are available for testing.