Identify who contracts with the player
Start with the entity that accepts stakes, holds customer funds and owes winnings. Then identify the companies providing the platform, games, hosting and other services. Map each role to the relevant application or existing permission.
Confirm the territorial reach of the proposed authorization explicitly. Do not assume a single reference to Tanzania settles every jurisdictional question, including a proposed activity involving Zanzibar.
Make the implementation brief reflect the license class
| Workstream | Evidence to obtain before committing |
|---|---|
| Operator | Entity, license category, permitted activity and conditions |
| Supplier | Applicable provider status and contracted service scope |
| Payments | Merchant identity, settlement account and funds responsibilities |
| Catalog | Games and delivery configuration covered by the project |
These are procurement checks, not a substitute for the Board's current application requirements. Obtain the current fee schedule for the exact category and separate authority charges from company setup, supplier and operating costs.
Scope the appropriate project
Send SuperBluOrange the proposed entity roles and product, together with existing permissions. We can define the platform and integration work once the scope of the required permissions is clear. A provider's technical capability alone does not close the operator's application or ongoing obligations.
Last source review: October 17, 2026. Recheck applicable rules before committing.