> For the complete documentation index, see [llms.txt](https://docs.hub88.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hub88.io/api-changelog/may-2026/thrilltech-sdk-update-community-payouts-supported-via-wallet-api.md).

# ThrillTech SDK Update: Community Payouts Supported via Wallet API

**Effective from:** 14 May 2026

***

{% hint style="info" %}
This applies to operators with an active who either use or wish to use the [ThrillTech Jackpot SDK](/developer-docs/operator-sdks/thrilltech-jackpots-sdk.md).
{% endhint %}

[ThrillTech Jackpots SDK](/developer-docs/operator-sdks/thrilltech-jackpots-sdk.md) now support **community payout** events — where a single triggering bet distributes jackpot credits to many eligible players at once. Hub88 handles the full orchestration of these batch transactions on ThrillTech's behalf, delivering each credit to your Wallet API automatically.

### **What's new?**

#### **Community payouts via your existing Wallet API**

No new endpoint required. Community payout credits arrive as standard `win` transactions on your existing Wallet API — the same endpoint you already use for supplier wins. The only difference is the `meta` block, which flags the transaction and gives you everything you need for reconciliation.

{% code overflow="wrap" lineNumbers="true" %}

```json
{
  "meta": {
    "is_community_payout": true,
    "batch_transaction_id": "b8f4a5e2-9c3d-4f1a-8e7b-2a1c5d9f3e8b",
    "source_id": "thrilltech_jackpot_main",
    "source_variant": "Mega",
    "jackpot_amount": 50000,
    "reference_bet": {
      "round_id": "round_abc123",
      "reference_bet_uuid": "bet_7f3e9a2c-1b4d-4e5f-9a8c-6d2e1f3b4c5a"
    }
  }
}
```

{% endcode %}

Use `meta.is_community_payout: true` as your primary flag to identify these transactions. The `batch_transaction_id` groups all credits from the same jackpot event, and `reference_bet` links the payout back to the round that triggered it.

This update provides:

* **Zero integration lift** as the community payouts land on your existing endpoint with no changes required on your side.
* **Clean reconciliation** as the integration groups all credits from the same jackpot fire using `batch_transaction_id`, and trace the trigger back to a specific player round via `reference_bet`.
* **Optional custom handling.** You can branch on `is_community_payout` to apply separate ledger tagging, player notifications, or accounting categorisation if your platform supports it.
* **Fully backward compatible**, as the existing win transaction handling is unchanged.

{% hint style="success" icon="book-open-lines" %}
**Read the full documentation** [**here**](/developer-docs/operator-sdks/thrilltech-jackpots-sdk.md) **and see the community payouts feature** [**here**](/developer-docs/operator-sdks/thrilltech-jackpots-sdk.md#community-payouts-batch-transactions)**.**
{% endhint %}

If you require any further assistance, contact your Hub88 account manager or our technical support team.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.hub88.io/api-changelog/may-2026/thrilltech-sdk-update-community-payouts-supported-via-wallet-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.