Operator guideENtransactionsfailed-depositgridtriage

Transactions / Failed Deposit

Triage grid for failed deposit rows, their provider reasons, and the error-group classification used for later analysis.

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 surface shows

Transactions / Failed Deposit is the queue for deposit attempts that did not complete successfully.

Technically this page is a failed-deposit-focused presentation of the shared banking transaction query. The FE initializes the shared get-transactions request with status='3' and then renders failed-reason and error-group columns on top of that response.

Operators use it to:

  • inspect failed rows
  • compare provider and method context
  • see normalized failed reasons
  • see the assigned error group
  • open raw provider details when available

How to read it

The most important columns are:

  • Transaction Status
  • Failed Reason
  • Error Group
  • Action

This page is best for operational triage. It is not the place where groups are edited. Group maintenance lives on the separate error-groups surface.

Filters that change the list

  • Search player
  • Currency
  • Type
  • Search by tag
  • Date start
  • Date end

Tag chips can also write directly into the filter form.

Common questions

What is the difference between Failed Reason and Error Group?

Failed Reason is the row-level reason shown for the transaction. On Carouseller rows the frontend prefers processor messages from moreDetails; otherwise it falls back to the generic banking error description. Error Group is the normalized grouping bucket joined from failed-deposit error-reason tables.

Where do I edit Error Groups?

On the dedicated Failed Deposit Error Groups surface, not in this list.

Why is there only a More Info action?

Because this list is mainly for investigation and classification visibility. The mutation workflow for groups lives on the separate group-management page.

Known caveats

  • Transaction Status is rendered from the transactions.carouseller.statuses resource when moreDetails.status_id is present.
  • Failed Reason and Error Group come from different places: provider payload or raw banking error text for the reason, normalized failed-deposit tables for the group.

Verification status

  • status: verified_backend
  • last verified: 2026-04-18
  • note: shared banking query reuse, default failed status, failed-reason joins, and error-group linkage are confirmed against FE and backend SQL
Operator actions

Screen actions

action

Apply Filters

Re-runs the failed-deposit queue with the current search and date filters.

action

Download CSV

Exports the current failed-deposit result set.

Operator actions

Row actions

action

More Info

Opens the shared transaction detail modal when provider payload details are present.

action

Filter by Tag

Clicking a tag chip writes that tag into the filter field and resubmits the list.

Grid columns

Columns

field

ID

field

Email

field

Full Name

field

Amount

Data Type
amount
field

Transaction Status

FE renders `statusId - status - description` when the Carouseller status resource contains the current `status_id`.

Note
FE renders `statusId - status - description` when the Carouseller status resource contains the current `status_id`.
field

Payment provider

field

Method

field

Failed Reason

Carouseller rows prefer provider payload messages; other rows fall back to the generic banking error description.

Note
Carouseller rows prefer provider payload messages; other rows fall back to the generic banking error description.
field

Error Group

Joined from `failed_deposit_error_reasons` -> `failed_deposit_error_groups`.

Note
Joined from `failed_deposit_error_reasons` -> `failed_deposit_error_groups`.
field

Currency

field

Date

field

User Tags

field

Action

Filter dictionary

Filters

field

Search player

Type
text
field

Currency

Type
select
field

Type

Type
select
field

Search by tag

Type
text
field

Date start

Type
date
field

Date end

Type
date
Operational notes

Notes

item

The failed-deposit list reuses the banking transactions endpoint with a failed-deposit-focused presentation.

item

The FE sets `status='3'` by default and then renders failed-deposit-specific columns on top of the shared banking payload.

item

Error-group editing is handled on a separate route.

Related references

Related pages

pageTransactions / Banking

Filterable banking transaction dashboard with weekly summary cards, backend stats charts, CSV export, and a detailed ledger-style table.

pageTransactions / Casino

Game transaction dashboard with real-time list mode, monthly analytics mode, filterable table, and a dedicated transaction detail route.

pageTransactions / Casino Transaction Detail

Read-only detail page for a single casino transaction identified by `casinoTransactionId`.

pageTransactions / Failed Deposit Error Groups

Configuration surface for creating, editing, importing, exporting, and assigning failed-deposit error groups and their reasons.

pageTransactions / KYC

Action-heavy KYC document queue exposed under the transactions area for document review, verification, re-request, download, and third-party checks.

pageTransactions / Shared Detail Modals

Reusable read-only transaction payload modals for banking-style rows on banking, withdrawals, and failed-deposit surfaces.