Casino Report by Pending Bet

Source route: /reports/casino/report-by-pending-bet

Use this report when casino or game-related bets remain unresolved and operators need a controlled follow-up workflow.

What This Report Is For #

This page is not the same as the normal bet report.

Use it when you need to:

• isolate pending bet records
• review stake and provisional winning values before escalation
• inspect player balances around a pending bet
• export the unresolved queue for audit or incident follow-up
• mark an old enough pending bet as lost when your role allows it

Permissions #

The page is protected by manage_pending_bet_by_report.

That permission is important for two reasons:

• it is required to open the route
• it also controls whether the Loss Bet action appears in the table

Filters #

The source filter sidebar supports:

• date and time range
• player ID
• transaction ID
• bet ID
• game type: All, Live Casino, Casino, Sports
• currency

Use narrow filters when investigating one unresolved transaction, and broader date windows when checking queue health.

Table And Totals #

The report exposes row-level fields such as:

• date
• player ID
• bet ID
• currency
• state
• game ID and game name
• provider
• transaction ID
• round ID
• category
• before balance
• bonus balance before
• bet
• win
• after balance
• bonus balance after
• username

The list also appends a footer row that summarizes:

• total stake
• total winning

Bet State Reading #

The state badge can show these source-backed values:

• Pending
• Won
• Lost
• CashOut
• Rollbacked

This lets operators compare truly pending items against already resolved rows in the same output shape.

Export #

The report supports CSV and XLSX export.

Exported fields keep the main pending-bet context, including balances, provider, transaction identifiers, and state labels.

Player Cross-Check #

Player ID is clickable in the table.

That action opens the player detail sidebar so the operator can quickly cross-check the player record without leaving the report.

Loss Bet Action #

When the user has permission, the table can show a Loss Bet button.

Important source-backed rule:

• the action is disabled until at least 15 minutes have passed since the row createdAt time

This means newly created pending bets cannot be forced into a lost state immediately.

When To Use This Page #

• when an unresolved bet queue must be reviewed
• when finance or operations needs to inspect balances around a pending outcome
• when an aged pending bet may need a controlled manual lost decision

Best Practice #

• verify transaction ID, round ID, and player context before using Loss Bet
• use the normal bet report first for broad analysis, then use this page for unresolved-item handling
• export the filtered set before taking high-impact manual actions if audit trace is important