Page body
What this surface shows
Transactions / Banking is the main ledger-style view for payment and wallet-side transaction history. It combines:
- weekly summary cards
- two charts for transaction mix and trend
- a filterable table
- a shared “More Info” modal
- filter chips plus
Reset/Exportcontrols for the current query state
Use this page when the question is about deposits, withdrawals, bonus money movement, provider references, or balance impact on a banking transaction row.
How to read it
The upper part of the page is a quick snapshot. Those cards and charts come from GET /api/admin/get-banking-stats, not from the visible table query:
Weekly TransactionsWeekly Volume (EUR)Weekly Success RateWeekly Avg Value
The table below is the actual operator work surface. It is best for:
- looking up a payment transaction id
- checking amount and amount in EUR
- checking before/after balances
- checking type and status
- checking affiliate payload columns such as
Aff PIDandSub ID 2 - following tag-based investigation
Filters that change the list
The visible filters are:
- Provider
- ClickID or PID
- Affiliate PID
- Sub ID 2
- Payment Transaction ID
- Currency
- Type
- Status
- Search by tag
- From
- To
Search by tag also works by clicking chips directly in the table.
The page also exposes:
Show Filters/Hide FiltersResetExport
Common questions
Why does this page show charts as well as a table?
Because the route acts as an operational dashboard, not just a raw list. Operators can inspect weekly movement quickly before drilling into a specific row.
Are the summary cards calculated from the visible table rows?
No. The summary cards and charts come from GetBankingStatsService, while the table uses GET /api/admin/get-transactions.
What does ClickID or PID really search?
That filter matches affiliate_link_payload.click_id or affiliate_link_payload.pid on the joined affiliate-link payload. It is broader than the dedicated Affiliate PID field.
Why can I see UTC hints on Updated and Date?
Because those timestamps are explicitly labeled as UTC in the grid.
Known caveats
- The stats section uses a separate frontend helper call named
getBankingStats, but the confirmed backend owner isGetBankingStatsService. - If the trend dataset is empty, the frontend falls back to placeholder weekly points for chart continuity.
- The page exposes a “More Info” action, but it is read-only and uses the shared transaction detail modal.