# Transactions Use Cases

### Reviewing transaction history

Reviewing transaction history allows you to pinpoint specific activities and identify potential discrepancies or issues.

**To review transaction history**:

1. Search for transactions by applying the required **Transaction UUID**, **User ID**, or **Round ID**.
2. Use the **Amount**, **Currency**, and **Status** columns to narrow down the data.
3. Apply filters like **Timeframe**, **Transaction Kind**, and **Supplier** to search for potential errors or inconsistencies.

***

### Monitoring bet transactions

Monitoring bet transactions allows you to track player activity and assess performance.

**To monitor bet transactions**:

1. Apply the **Transaction Kind** filter and select **Bet** to focus solely on bet transactions.
2. Set a relevant **Timeframe** (e.g., daily, weekly) to view bets placed during that period.
3. Filter by **Game** to focus on bet activity within specific games.
4. Use the **Operator**, **Brand**, or **Site** filters to view relevant bets from specific operational segments, if needed.

***

### Monitoring win transactions

Monitoring win transactions allows you to assess player performance and financial impact, either across all games or by specific game.

**To monitor win transactions**:

1. Apply the **Transaction Kind** filter and select **Win**, **Jackpot Win**, or **Bonus Win**, depending on the type of win you want to monitor.
2. Set a relevant **Timeframe** to focus on recent wins.
3. Use the **Currency** filter to track wins in specific currencies.
4. Filter by **Game** to narrow down the data to specific games you wish to track for wins.

***

### Investigating failed or rolled back transactions

Investigating failed or rolled back transactions allows you to identify and troubleshoot technical issues and maintain financial integrity.

**To investigate failed or rolled back transactions**:

1. Apply the **Transaction Kind** filter and select **Rollback** to view transactions that have been rolled back.
2. Use the **Status** filter to select **Declined** or **Retry attempts limit exceeded** to focus on failed or declined transactions.
3. Set a relevant **Timeframe** (e.g., last 24 hours) to focus on recent failed or rolled back transactions.
4. If relevant, filter by **Game** to focus on failed or rolled back transactions that occurred within specific games.

***

### Tracking free bet and free bet win transactions

Tracking freebet and freebet win transactions helps assess promotional effectiveness and player engagement.

**To track free bet and free bet win transactions**:

1. Apply the **Transaction Kind** filter and select **Freebet Bet** and **Freebet Win** to view these specific transaction types.
2. Set a relevant **Timeframe** (e.g., during a promotion or campaign) to track the usage of free bets.
3. Use the **Currency** filter to focus on transactions involving specific currencies.
4. Filter by **Status** and select **Success** to focus on successfully placed or won free bets.

***

### Supplier performance and monitoring

Supplier performance monitoring helps assess transaction volumes, wins, or issues associated with specific game providers.

**To monitor supplier performance**:

1. Apply the **Supplier** filter and select the relevant supplier to view transactions related to that provider’s games.
2. Filter by **Transaction Kind** (e.g., **Bet**, **Win**, **Rollback**) depending on the activity you wish to monitor.
3. Set a relevant **Timeframe** to focus on the supplier's performance during that period.

***

### Tracking player activity across multiple sites or brands

Tracking player activity across multiple sites or brands provides a comprehensive view of player behaviour.

**To track player activity across multiple sites or brands**:

1. Apply the **Site/Brand** filter to select a specific site or brand, isolating transactions within that segment.
2. Filter by **Transaction Kind** to focus on specific activities (e.g., **Bet**, **Win**, **Rollback**).
3. Use the **User** search to track transactions for a specific player across multiple sites or brands.

***

### Tracking performance by game

Tracking performance by game allows operators to assess the performance of specific games, including bet and win transactions, and identify potential issues.

**To track performance by game**:

1. Apply the **Game** filter to select the specific game(s) you want to monitor.
2. Filter by **Transaction Kind** (e.g., **Bet**, **Win**, **Rollback**) to capture relevant activities for that game.
3. Set a relevant **Timeframe** to track the game’s performance during that period.

***

### Reconciling transaction data with payment processors

Reconciling transaction data with payment processors ensures that financial records are aligned and that there are no discrepancies.

**To reconcile transaction data with payment processors**:

1. Filter transactions by **Supplier** and compare the data with the records provided by your payment processor.
2. Use the **Transaction Status** filter to ensure that payments are processed correctly and that no transactions are pending or failed.
3. Verify the **Amount Wagered** and **Currency** against the processor’s records to identify any discrepancies.
4. If discrepancies are found, use the **Actions** column to access round details and logs for further investigation.

***

### Investigating discrepancies in transaction data

Investigating discrepancies in transaction data helps identify mismatches in amounts, wins, or rollbacks.

**To investigate discrepancies in transaction data**:

1. Apply the **Transaction Kind** filter and select **Bet**, **Win**, **Rollback**, or other relevant transaction types to investigate discrepancies in those activities.
2. Use the **Status** filter to select **Declined**, **Rollback**, or **Retry attempts limit exceeded** to filter for discrepancies.
3. Set a relevant **Timeframe** to narrow down when discrepancies are most likely to have occurred.
4. Use the **Amount Range** filter to focus on specific transaction amounts that may involve discrepancies.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hub88.io/operator-backoffice/transactions-management/transactions-use-cases.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.