StaticinstanceThe process default, on the replica: every query here is a read, and a read landing inside the lag right after a write self-heals on the next bust.
Aggregate transaction totals grouped by (method, type, status).
Single GROUP BY query against the same UNION used by search, but skips
the outer entity / ledger / solana enrichment — aggregation only needs
(method, type, status, amount). Use this instead of paging through
search when you only need bucketed sums (e.g. the home-page money-
movement widget).
OptionalcreatedAt?: DbTimestampCriteriaOptionaldataSources?: (Filter by the producing arm; prunes the UNION exactly.
Optionalmethods?: (Optionalstatuses?: ("PENDING" | "FAILED" | "PROCESSING" | "COMPLETED" | "RETURNED" | "CANCELLED")[]Optionalsubtypes?: Pass values to include only those subtypes; pass null to exclude transactions with a subtype
How many rows the search's filters match, ignoring paging and order; see
TransactionAdminQueryService.count. Busted with the customer's listings.
Entity external ids the customer has transacted with, ordered by recency
(most recently transacted first), optionally filtered by entityType.
Uncached.
Every matching transaction, a page at a time, oldest page first.
For callers that read the whole result set (CSV and XLSX exports, the DART
reports, a statement period) rather than one page of it. Walks by keyset, so
the cost per page does not grow with how deep the walk has gone the way
search's OFFSET paging does. The cache is deliberately not in the path: a
full walk would evict every useful entry for a result nobody reads twice.
Pages rather than rows so a caller can resolve related data for a whole page in one query instead of once per row.
Payment-instrument external ids the customer has transacted with, ranked by
usage (most-used first). Skips the outer entity / ledger / solana
enrichment — ranking only needs (payment_instrument_id, method, created_at).
Uncached.
OptionalcreatedAt?: DbTimestampCriteriaOptionaldataSources?: (Filter by the producing arm; prunes the UNION exactly.
Optionallimit?: numberOptionalmethods?: (
Read-only query services to fetch normalized transactions across all products
If you need more info about a transaction, fetch it using its specific service. Transaction Service will remain generic and high-level.