What this page shows
This page shows the casino aggregator registry as a paginated operator table. Each row represents one upstream game aggregator connection and the status stored for that connection.
When to use it
- confirm whether an aggregator is active
- find the stored aggregator id and readable name
- activate or deactivate an existing aggregator after confirmation
How to read it
The table is intentionally small and status-focused:
IDis the stored aggregator identifierAggregatorshows the readable name and a visual initialStatusshows whether the connection is activeActionsopens the activation or deactivation confirmationRowscontrols how many aggregators are requested per page
How status changes work
Clicking the action icon does not update the row immediately. It opens a confirmation modal. The modal title and button change depending on the current state: active rows ask for deactivation, inactive rows ask for activation.
When the operator confirms, the page sends the selected aggregator id and the next status to the shared status update flow. The modal closes immediately and the list refreshes through the aggregator list request. Cancel or closing the modal leaves the row unchanged.
Known caveats
- This page is a control registry, not a diagnostics page. It does not explain why an upstream integration is failing.
- There is no visible search or status filter on the verified page. Pagination is the only list narrowing control.
- The current page does not show a dedicated success toast after a status update. Operators should rely on the refreshed row status after confirmation.
- Deactivating an aggregator can affect downstream provider and game visibility because several catalog reads require active aggregators.