What’s available
The transaction model
A transaction has three parts:- What happened: a
transactionTypeand astatus. - When:
createdAt, andendedAtonce the transaction reaches a final state. - Whose balances moved: a list of entries (the
subaccountsfield), each naming anaccountId, anassetType, anamount, abalanceType, and adirection(CREDITfor funds in,DEBITfor funds out).balanceTypeisAVAILABLEfor a settled movement,HOLDfor an amount set aside for an in-flight debit, orPENDINGfor a credit not yet settled. OnlyAVAILABLEentries change theTOTALbalance.
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.
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.