transfers:read
List transactions
Filter by customer
| Field | Description |
|---|---|
kind | swap (Stablecoin convert on Solana) or payment_route (Crypto to crypto cross-chain collection) |
customerId / customerName | Linked counterparty |
status | Settlement status |
amount | Human-readable amount string |
destination | Wallet or route destination |
receipt | Settlement metadata — signatures, route IDs, amounts, and user-safe failure messages |
receipt.origin and receipt.destination summarise what was sent and received (chain name, token symbol, amount, USD value). Present these as human-readable strings in your UI — do not expose raw chainId blobs to end users.
For swap rows, use top-level amount / destination plus receipt.swapTxSignature, receipt.payoutTxSignature, and receipt.errorMessage when failed.
For failed swaps, receipt.errorMessage is a user-safe explanation (no raw Solana logs). Payment-route deposits may include receipt.failReason with the same treatment.
| createdAt | ISO timestamp |
Returns up to 200 most recent events, swaps and deposits merged by time.
Sync behaviour
Listing transactions triggers a deposit sync for your org’s payment routes before returning results. For explicit sync on one route, usePOST /v1/payment-routes/{id}/deposits/sync.
Reconciliation pattern
- Poll
GET /v1/transactionson a schedule, or filter bycustomerIdper counterparty - Match
id+kindto your internal payment records - Use
receiptfor on-chain proof (transaction signatures, route IDs)
API reference
List transactions
GET /transactions