Skip to content

Transactions list & filters

TL;DR - The transactions page is the unified view across every customer in your fintech. Filter by status, type, customer, recipient, network, or date range; search free-text; export.

What you see

Column What it shows
Created Timestamp the transaction was initiated.
Customer Which of your customers the transaction belongs to.
Type What kind of transaction - see the type table below.
Reference Human-readable code (e.g. PO-XXXXXXXX for payouts).
Recipient Bank or wallet name, where applicable.
Amount Signed - outflows are negative, inflows positive.
Status Lifecycle state - see Status reference.

The table is display-only in v1 - rows are not clickable to a detail modal. Use the filter and search row to narrow what's shown, and the export buttons to pull a more detailed offline view.

Transaction types

Type What triggered it
deposit_fiat Customer wired funds into their fiat virtual account (top-up).
deposit_crypto Customer wired USD into a crypto VA - auto-converted and forwarded on-chain (on-ramp).
payout_fiat A fiat payout you initiated.
payout_crypto A crypto-to-fiat payout.
crypto_conversion Internal conversion leg of a crypto-to-fiat or on-ramp flow.
fee A fee line item.

Statuses

Common terminal states: completed, failed, returned, expired, canceled.

In-flight: created, pending, processing.

Manual: action_required, under_review.

The full list with explanations is in Status reference.

Filters

The filter bar at the top of the table:

  • Customer - pick a single customer to scope the list.
  • Status - multi-select chips.
  • Type - multi-select chips.
  • Recipient - searchable picker.
  • Network - for crypto-related rows: polygon, solana, tron, ethereum, arbitrum, base.
  • Date range - from / to.
  • Search - free text across reference, recipient, memo, invoice number.

Cross-customer view vs scoped view

  • Transactions in the left navigation = unified across every customer.
  • Customer dashboard → recent transactions = scoped to one customer.

Click View all on a customer dashboard to jump to the unified page with the customer filter pre-applied.

What happens behind the scenes

UI action Endpoint
Cross-customer list GET /api/v1/transactions
Scoped to one customer GET /api/v1/organizations/{orgId}/transactions
Single transaction detail GET /api/v1/transactions/{id}

All filters map to query parameters: status, type, recipientId, network, fromDate, toDate, q, page, limit.

What's next