Operator guideENplayerswalletbalancestab

Players / Wallet

Wallet tab inside the player workspace showing one or more player wallets, balances, and wallet metadata used during manual balance operations.

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 / Wallet is the balance tab inside the player workspace. It shows the player's current wallet set and the metadata operators usually need before running manual wallet actions.

When to use it

Use this tab when you need to:

  • confirm the active wallet and its currency
  • check real-balance, non-cash balance, and wallet card status
  • compare multiple wallets attached to the same player
  • prepare for Manage Wallet or Add Adjustment actions from the workspace header

How to read it

The tab renders one card per wallet. The active wallet is highlighted with the verified badge and ACTIVE chip. Each card focuses on:

  • current cash amount
  • non-cash amount
  • owner type and currency chips
  • wallet ownership metadata
  • creation, update, and last-transaction timing
  • whether the card is the active wallet or a secondary wallet

If more than one wallet exists, operators can expand a card with More Details to inspect the full wallet details.

Header actions tied to this tab

The tab itself is read-only, but operators normally use it as the inspection surface before opening two header-level mutation flows:

  • Manage Wallet: manual add/remove money flow for a selected wallet
  • Add Adjustment: manual bet/win adjustment flow linked to a selected wallet and game

Those actions do not mutate data inside the tab component. They open separate modals and call dedicated wallet endpoints in gs-admin-backend.

Known caveats

  • This tab is a read surface. Manual balance changes are triggered from header modals such as Manage Wallet and Add Adjustment, not from inline controls inside the tab itself.
  • The visible layout is card-based, not a grid. Search in docs should therefore use wallet terms such as wallet balance, non-cash amount, or manage wallet, not table-column wording.
  • If userWallets is empty, FE falls back to player.userWallet, so the tab can still render the primary wallet even when the multi-wallet payload is not populated.
  • The Wallet Type switch inside Manage Wallet shows Cash and a disabled Bonus option. Operators currently cannot post manual non-cash changes from this modal even though the backend service accepts NONCASH.
  • Last Transaction in the expanded card is a display convenience. FE currently reuses updatedAt and shows No transactions yet only when the timestamp is missing.
  • Add Adjustment posts a casino transaction with adjustment or marketing semantics depending on the selected game identifier, so it should be used for game-linked corrections, not for ordinary cash top-ups.

Verification status

  • status: verified_backend
  • last verified: 2026-04-18
  • note: wallet card rendering, Manage Wallet, and Add Adjustment are traced through the FE wallet tab, both modal components, use-balance, use-game-adjustment, wallet.controller.js, AddBalanceService, and AddGameAdjustmentService.
Operational notes

Notes

item

The wallet tab itself is read-only. Operators inspect balances here before using header-level wallet actions.

item

`Manage Wallet` uses `AddBalanceService`, which validates `userId`, `addAmount`, `walletType`, and `walletId`, updates cash or non-cash balance, live-updates the wallet, and optionally writes comment activity with source action `MANAGE_WALLET`.

item

`Add Adjustment` uses `AddGameAdjustmentService`, which validates `userId`, `amount`, `transactionType`, `gameId`, and `walletId`, creates a successful casino transaction, live-updates the wallet, and optionally writes comment activity with source action `ADD_ADJUSTMENT`.

item

`AddGameAdjustmentService` classifies some game identifiers such as `stream`, `bonus_payout`, `cashback`, and `rakeback_calendar` as marketing transactions instead of ordinary adjustment flows.

Related references

Related pages

pagePlayers / Banking

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

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.