> 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/product-news/september-2026/streamer-billing-without-the-slack-thread.md). # Streamer billing, without the Slack thread Request, approve, and exclude promotional GGR from billing — all inside HubConnect. **Released: September 22, 2026** *** When an operator runs a streamer campaign, the streamer's gameplay is funded by promotion, not real player revenue, so it shouldn't be billed as Gross Gaming Revenue (GGR). Agreeing that has always meant a private message between an operator and a supplier, with no confirmation and no shared record. **Streamer Exclusions** changes that. Operators request an exclusion directly in HubConnect Operator Zone, suppliers review and approve or reject it in HubConnect Supplier Zone, and once approved, the agreed GGR is excluded from billing automatically, from the date it was requested. {% hint style="info" %} **Find the full feature guides:** \ \ \- [For Operators Streamers Exclusions](/hubconnect-operator-zone/promotions/streamer-exclusions.md) \ \ \- [For Suppliers Streamers Exlcusions Management](/hubconnect-supplier-zone/supplier-promotions/streamers-exclusions-management.md) {% endhint %} *** ### **For operators, you can:** * **Request an exclusion yourself** \ Pick the Brand, products, games, streamer player IDs, and dates, and submit without going through Hub88 or the supplier directly. * **Track every request in one place** \ See the products, games, and GGR/bet totals tied to each streamer, by player or by product. * **Extend or shorten cover as the campaign changes** \ Shorten an end date immediately, or ask for an extension that goes back to the supplier for review. * **Never be billed for your own promotional spend slipping through** \ Once approved, the exclusion is backdated to your requested start date, not the approval date.

Control and view streamer exclusions

### **For suppliers, you can:** * **See exactly what you're being asked to exclude** \ The operator, products, games, dates, and your own Supplier User IDs, before you decide. * **Approve or reject with one click, or in bulk** \ Nothing comes off your billing without your sign-off. * **Keep your users protected** \ You only ever see your own Supplier User IDs, never the operator's underlying player IDs.

Bulk approve or reject streamer exclusion requests

*** ### **Where to find it** Streamer Exclusions is now available under **Promotions** in both HubConnect Operator Zone and HubConnect Supplier Zone. **Operators**: see the [Streamer Exclusions guide](/hubconnect-operator-zone/promotions/streamer-exclusions.md) for a full walkthrough of requesting and managing exclusions. **Suppliers**: see the [Streamer Exclusions guide](/hubconnect-supplier-zone/supplier-promotions/streamers-exclusions-management.md) for a full walkthrough of reviewing and approving requests. *** ### **Why it matters** Streamer billing agreements used to live in private messages, with no confirmation either side could point back to. Streamer Exclusions turns that into one trusted, shared record: exclusions apply from the right date automatically, and billing disputes over a slipped ID or date drop away. It's an exclusion tool, not a streamer campaign product, it covers 100% of the GGR for agreed streamer activity, and partial exclusions aren't supported. --- # 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/product-news/september-2026/streamer-billing-without-the-slack-thread.md?ask=&goal= ``` `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.