Operator guideENplayersbankingtransactionsanalytics

Players / Banking

Banking tab inside the player workspace with transaction filters, a paginated banking grid, analytics cards, CSV export, and automatic-withdrawal availability.

Reader view

Clean portal guidance

This page keeps the operator explanation, field and action descriptions, and screenshots visible without exposing repo paths, raw sidecars, or editorial-only implementation details.

Narrative content

Page body

What this tab shows

Players / Banking is the transaction workspace for a single player. It combines a filtered banking table with a separate analytics layer and an automatic-withdrawal availability snapshot.

When to use it

Use this tab when you need to:

  • review the player's deposits, withdrawals, bonus-money moves, or rollback events
  • inspect one banking row in detail
  • export the player's filtered banking history
  • see all-time transaction analytics for this player
  • check whether automatic withdrawal is currently available

How to read it

The tab has three distinct layers:

  1. Table filters for transaction type, status, currency, provider, search, and date range.
  2. Transactions table with one row per banking item plus expandable row details.
  3. Analytics and automatic-withdrawal cards that summarize wider transaction behavior.

The visible Transactions and Deep Analytics tabs inside the component are not separate routes. They are two views of the same Banking tab.

Known caveats

  • The visible table respects the selected date range and search query, but the analytics query is fetched separately with an all-time date range and no search filter. Summary cards can therefore differ from the currently visible table rows.
  • The analytics query keeps the same userId, currency, transactionType, status, and paymentProvider filters as the table, but always forces the date range to 2000-01-01 -> 2030-01-01, sets limit=1000, and clears the free-text search filter.
  • Type can be manually reclassified in-line for supported deposit or withdrawal groups. This changes classification, not the raw transaction amount.
  • The Apply button in the filter card does not submit a separate request. The filters are already bound to component state, so changing them refreshes the table and analytics without an extra apply step.
  • Automatic-withdrawal availability is a backend eligibility snapshot, not a guaranteed payout execution result.

Verification status

  • status: verified_backend
  • last verified: 2026-04-18
  • note: transaction list, type update, and automatic-withdrawal availability routes are traced from FE hooks to gs-admin-backend.
Calculation notes

Calculations

calculation

Total Deposits

Formula Text
Sum of `amount` for rows whose `transactionType` is `deposit` or `addMoney` in the analytics query.
Operator Note
This uses the separate analytics dataset, not the paginated visible table only.
Verification Status
verified_backend
calculation

Total Withdrawals

Formula Text
Sum of `amount` for rows whose `transactionType` is `withdraw` or `removeMoney` in the analytics query.
Operator Note
This is paired with Total Deposits to calculate net flow.
Verification Status
verified_backend
calculation

Net Flow

Formula Text
`totalDeposits - totalWithdrawals`
Operator Note
Positive net flow means deposits exceed withdrawals in the analytics dataset.
Verification Status
verified_backend
calculation

Success Rate

Formula Text
`(successfulRows / analyticsTransactionList.length) * 100`, where successful rows have status `SUCCESS`, `APPROVED`, or `COMMITED`.
Operator Note
This is a frontend-derived display metric based on backend statuses.
Verification Status
verified_backend
calculation

Deposit Count

Formula Text
Count of analytics rows whose `transactionType` is `deposit` or `addMoney`.
Operator Note
This count is based on the separate analytics dataset, not only the visible paginated table rows.
Verification Status
verified_backend
calculation

Withdrawal Count

Formula Text
Count of analytics rows whose `transactionType` is `withdraw` or `removeMoney`.
Operator Note
This is the count companion to `Total Withdrawals`, using the same analytics dataset.
Verification Status
verified_backend
calculation

Largest Deposit

Formula Text
Maximum `amount` among analytics rows whose `transactionType` is `deposit` or `addMoney`.
Operator Note
When there are no matching deposit rows the FE falls back to `0`.
Verification Status
verified_backend
calculation

Largest Withdrawal

Formula Text
Maximum `amount` among analytics rows whose `transactionType` is `withdraw` or `removeMoney`.
Operator Note
When there are no matching withdrawal rows the FE falls back to `0`.
Verification Status
verified_backend
calculation

Analytics Scope

Formula Text
Analytics always use `startDate=2000-01-01`, `endDate=2030-01-01`, `limit=1000`, and an empty `search` value while still passing the current `userId`, `currencyCode`, `transactionType`, `status`, and `paymentProvider`.
Operator Note
The analytics section can differ from the filtered table because it intentionally ignores the table search input and selected date range, but it still respects the non-date filters.
Verification Status
verified_backend
Grid columns

Columns

field

ID

Internal banking-row identifier.

Data Type
integer
field

Provider / PaymentID

Provider name plus provider-specific payment reference shown in the same cell.

Data Type
string
field

Type

Current transaction classification used by the admin UI and analytics.

Data Type
enum
field

Amount

Absolute amount on the banking row.

Data Type
amount
field

Balance Change

Before and after balance visualization for the selected row.

Data Type
amount
field

Bonus ID

Bonus reference when the transaction is bonus-related.

Data Type
integer
field

Payment Method

Payment method recorded on the banking row.

Data Type
string
field

Status

Current processing state of the transaction.

Data Type
enum
field

Date

Row creation timestamp.

Data Type
datetime
field

Date Updated

Latest update timestamp for the transaction.

Data Type
datetime
Filter dictionary

Filters

field

Currency

Restricts both the visible table and the analytics query to one currency code.

Type
select
field

Action Type

Limits the table to one transaction family such as deposit or withdraw.

Type
select
field

Status

Filters rows by lifecycle status such as pending, approved, rollback, or failed.

Type
select
field

Payment Provider

Restricts rows to one provider name or provider substring.

Type
text
field

Start Date

Lower date bound for the visible transaction table.

Type
date
field

End Date

Upper date bound for the visible transaction table.

Type
date
field

Search

Matches transaction ID, payment transaction ID, actionee email, provider, type, or currency on the visible table.

Type
text
Metric dictionary

Metrics

metric

Total Deposits

Sum of deposit and add-money rows used by the analytics panel.

Source Type
frontend-derived
Verification Status
verified_backend
metric

Total Withdrawals

Sum of withdraw and remove-money rows used by the analytics panel.

Source Type
frontend-derived
Verification Status
verified_backend
metric

Net Flow

Difference between total deposits and total withdrawals in the analytics panel.

Source Type
frontend-derived
Verification Status
verified_backend
metric

Success Rate

Share of analytics rows whose status is `SUCCESS`, `APPROVED`, or `COMMITED`.

Source Type
frontend-derived
Verification Status
verified_backend
metric

Deposit Count

Number of analytics rows whose transaction type is `deposit` or `addMoney`.

Source Type
frontend-derived
Verification Status
verified_backend
metric

Withdrawal Count

Number of analytics rows whose transaction type is `withdraw` or `removeMoney`.

Source Type
frontend-derived
Verification Status
verified_backend
metric

Largest Deposit

Highest single-row amount among analytics deposit and add-money rows.

Source Type
frontend-derived
Verification Status
verified_backend
metric

Largest Withdrawal

Highest single-row amount among analytics withdraw and remove-money rows.

Source Type
frontend-derived
Verification Status
verified_backend
metric

Automatic Withdrawal Max Instant Amount

Backend eligibility limit shown in the automatic-withdrawal snapshot.

Source Type
backend
Verification Status
verified_backend
Operational notes

Notes

item

The table query and analytics query call the same transaction route with different parameter scopes.

item

The analytics request keeps `userId`, `currencyCode`, `transactionType`, `status`, and `paymentProvider`, but forces a broad `2000-01-01 -> 2030-01-01` date window, `limit=1000`, and empty search.

item

Automatic-withdrawal availability is loaded separately and should be read as an eligibility snapshot.

Related references

Related pages

pagePlayers / Detail Workspace

Main player workbench at `/player/[playerId]` with tabbed sections, player-level actions, and modal-based operator workflows.

pagePlayers / Fraud Detection

Fraud-detection tab inside the player workspace with fraud risk assessment, related fraud reports, IP analysis, and identity-graph filtering.

pagePlayers / Game Report

Per-player game or provider report inside the player workspace, filtered by date option and grouped either by game or by provider.

pagePlayers / Inbox

Inbox tab inside the player workspace for reviewing sent notifications, filtering by read state or notification type, and resending or deleting messages.

pagePlayers / KPI Summary

Grouped player-level KPI snapshot inside the player workspace, covering player info, deposits, withdrawals, casino totals, bonus cost, and predictive metrics.

pagePlayers / KYC Status

KYC tab inside the player workspace for browsing user documents, checking third-party verification state, and approving, rejecting, or re-requesting documents.