LogoLogo
Knowledge BaseDeveloper DocsProduct NewsChangelogStatusHub88 home
Hub88 Knowledge Base
Hub88 Knowledge Base
  • 👋Welcome to Hub88
  • HubConnect
    • 🤝HubConnect Overview
    • HubConnect Operator Zone
    • Getting Started
    • Customer Support
    • Due Diligence
    • HubConnect Supplier Zone
    • Data Insights
    • General Information
  • Operator BackOffice
    • 💡Operator Backoffice Overview
    • Dashboards
    • Reports
    • Invoices
    • Transactions Management
      • Flagged Activity
      • Handling Big Wins
      • Transactions Use Cases
    • Rewards and Campaigns
    • User Mapping
    • Game Management
    • Glossary
Powered by GitBook
LogoLogo

Hub88

  • HubWallet
  • HubMarket
  • Suppliers

Hub88

  • News
  • Status
  • Privacy Policy

Contact

  • sales@hub88.io

Follow us

  • LinkedIn
  • Telegram

Copyright © 2025. All Rights Reserved.

On this page
  • What Is Flagged?
  • Using the Flagged Activity View
  • Available Statuses
  • Creating a Support Case
  • Shared Visibility and Collaboration
  • Data Retention
  • FAQ

Was this helpful?

  1. Operator BackOffice
  2. Transactions Management

Flagged Activity

PreviousTransactions ManagementNextHandling Big Wins

Last updated 28 days ago

Was this helpful?

The Flagged Activity area in the provides a way to quickly identify and investigate suspicious or problematic gameplay activity. This view simplifies issue resolution by automatically surfacing transactions that meet predefined risk criteria— system response failures or unusually large wins.


What Is Flagged?

Transactions are flagged automatically by the system based on two criteria:

1. Operator Response Failures

Transactions that have both:

  • Status: declined

  • Error code: RS_ERROR_UNKNOWN

These often indicate a failure in the operator’s system response to a round transaction and may require follow-up.

2. Big Wins

Transactions where both:

  • Win amount exceeds €40,000, and

  • The bet-to-win ratio is higher than 350x

These may trigger additional internal review, particularly around bonus abuse or jackpot verification.


Using the Flagged Activity View

  • Review all flagged transactions (filters can be applied as needed)

  • Update investigation status of one or multiple transactions

Available Statuses

Operators can track investigation progress using one of three statuses:

  • FLAGGED (default) – Automatically assigned when the transaction is flagged

  • INVESTIGATING – Set when the issue is actively under review

  • RESOLVED – Used when investigation is complete

Note: Changing a status to RESOLVED doesn't remove the transaction from the view. It remains accessible for reference and auditing purposes.

Creating a Support Case


Shared Visibility and Collaboration

The Flagged Activity area supports cross-user visibility. All users within the Operator's account see the same investigation statuses, enabling teams to avoid duplication and maintain investigation continuity.

All changes made will automatically reflect for all users under the same account.


Data Retention

  • Flagged transactions are retained for 30 days after the flag was applied.

  • If a previously declined transaction is retried and succeeds, the flag is removed, and the transaction will no longer appear in the Flagged Activity view.


FAQ

2. Are investigation statuses visible in the main Transactions page? No. These statuses are only available and visible within the Flagged Activity area.

3. Is the transaction data consistent between both views? Yes. Apart from the investigation statuses, the transaction data is identical.

The layout is identical to the standard but is automatically filtered to show only flagged entries. From this view, you can:

Similarly to the , you can create customer support cases directly from the Actions menu at the end of each transaction's row. You can create support requests for both and cases. Once you click the selected ticket creation, you'll be directed to HubConnect, where you can finalize the case creation with some data already prefilled.

1. Can I customise the Big Win threshold? Not at this time. Thresholds are fixed based on system-wide configuration. This may evolve based on operator demand and data insights. Read more about .

All Transactions view
All Transactions view
"Big Wins"
“Stuck round / missing transaction”
Handling Big Wins
Operator Backoffice
Flagged Activity Under Transactions Management
Creating a Support Case from Flagged Activity