ThrillTech SDK Update: Community Payouts Supported via Wallet API
Effective from: 14 May 2026
ThrillTech Jackpots SDK 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.
{
"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"
}
}
}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 viareference_bet.Optional custom handling. You can branch on
is_community_payoutto 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.
If you require any further assistance, contact your Hub88 account manager or our technical support team.
Last updated
Was this helpful?

