Page body
What this surface shows
Transactions / Withdrawals is the operator queue for customer withdrawal requests.
This page is action-heavy. It is not only a history table. Operators use it to:
- filter and review withdrawal requests
- open provider request/response payloads
- move
APPROVE_REQUESTEDrows back toPENDING - approve or reject postponed payouts when permissions allow
How to read it
The grid combines identity, provider, amount, status, payout method, balances, timestamps, and tags.
Important columns are:
StatusActionProvider ReqProvider Resp
Provider Req opens the postponed request payload from postponedResumeParams. Provider Resp opens the shared response payload from moreDetails.
Filters that change the queue
- Search player
- Search provider
- Status
- Search by tag
- Date start
- Date end
Tag chips inside the grid can also push a tag into the filter form and re-run the list.
Common questions
What does To Pending do?
It is a status-change action shown only for rows currently in APPROVE_REQUESTED. The backend change is restricted to APPROVE_REQUESTED -> PENDING, sets postponed=true, and clears any stored postponedResumeParams.
Why do some rows show extra approve/reject icons and others do not?
Because those icons only appear for postponed rows and are also permission-gated.
What do Approve Withdrawal and Reject Withdrawal actually call?
They do not mutate the row in-browser. CRM calls resume-payout or reject-payout on gs-admin-backend, and the backend helper forwards the request to the configured user-backend payout endpoints.
Why are there two different modal types?
Because one modal shows the shared transaction provider payload, while the postponed modal shows the postponement payload and reason.
Known caveats
- Some row actions are permission-dependent (
Approve,Reject). - The page mixes status workflow actions with read-only payload inspection actions.
- “No tags” and tag chip behavior are part of the operator workflow because tags are searchable from the row itself.
Verification status
- status:
verified_backend - last verified:
2026-04-18 - note: list query, status-change restriction, postponed payload fields, and payout mutation routes are confirmed against FE and backend services