Engagement scope - proposed scope
Choosing a White Label Sportsbook Provider: Whose Licence, Whose Code
This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.
Scope areas for this kind of build
Typical scoping questions
Whose licence do the bets run under?
- If the answer is the provider's, you are a brand on their operation, and their terms set your margin and your exit. If it is yours, ask exactly what they will and will not help with.
What do I pay after launch, and for how long?
- A revenue share needs written terms: what it is charged on, whether it ever ends and what changes if you leave. A seller who will not put it in writing has answered already.
Who owns the source and the database?
- Ask for the repository and the player records by name. A licence to use software is not ownership, and the difference shows the first time you want to change the cashier.
What happens if we stop working together?
- Get the answer for the site, the player list and the wallet balances. On a platform you own and host, the answer is that you carry on. On a rented one, check before you sign.
Is the exchange a real order book?
- Ask to watch two customers matched against each other, a partial fill and the remainder resting on the book. If all they can show is fixed odds, there is no exchange.
How is money stored, and can a balance be rebuilt?
- Ask for the column type and for a balance derived from the ledger alone. Ours is numeric(18,8) with decimal.js, and each wallet change writes an append-only entry.
Who can void or reverse a market?
- It should be a console action with a recorded actor and IP address, never a database update. Ask to see the audit entry it leaves behind.
What is unfinished, and what needs my own accounts?
- Every platform has gaps and depends on outside contracts. Ask for both lists in writing. Ours names the data feed, casino providers, payments and notification accounts.
Proposed delivery stages and dependencies
Agree scope, prerequisites, acceptance tests and responsibilities in writing. No delivery sequence or launch duration is guaranteed by this preview.
Scope and licence check
- Before implementation or spending, establish the operator's lawful authority, eligible markets/products, licence status, payment approval and data/game provider contracts with qualified review. Record unresolved dependencies; no licence or provider access is supplied by this preview.
Brand everything
- Proposed branding can cover the agreed web/mobile/operator surfaces. Verify third-party attribution, licence duties, distribution eligibility and store rules before promising branding removal or publication.
Margins and risk desk
- If lawful and in scope, define pricing/risk settings, validation, exposure reporting and restricted staff authority, then test the agreed controls in an approved non-live environment. No working risk desk or wagering capability is verified here.
Source handover and support
- The written agreement must define the source inventory, schema/migrations, documentation, support, third-party licences, modification rights and handover. No unrestricted ownership or continuing support grant is made by this preview.
- Licensing, payment approval and provider contracts are dependencies to verify for the actual operator. No historical client deployment, week/day delivery count or typical-launch claim is established here.
Licence, Money and Player Protection: Where We Stand
Three questions matter most on a betting platform. Can money vanish, can an admin deny an action, and can an auditor rebuild what happened? The answers sit in the data model and not in a policy document.
The licence is yours, always
- We supply software, never permission to operate. Obtaining and holding a licence in each market you accept customers from is your responsibility, along with age verification, responsible-gambling provision and local advertising limits. We do not advise on any of it, and any seller who says a licence comes bundled with the code is misleading you.
No silent balance changes
- Wallet mutations run in a transaction under row-level locking, check available balance before a debit and append a ledger entry with direction, amount, balance after, source reference and description.
Exact decimal maths
- Every amount is calculated with decimal.js over numeric(18,8) columns, so fiat and crypto share one precision and any balance can be rebuilt from the ledger.
Limits that are enforced
- Deposit caps by day, week and month, daily loss limits, session time limits, self-exclusion with an end date and reality check reminders on an interval you set. These are the controls an application usually asks to see, not a promise that any regulator will accept them.
- A dedicated compliance document maps the security posture: bcrypt at cost 12, 15-minute access tokens with 7-day refresh rotation and reuse detection, TOTP two-factor, login lockout, three-tier roles on every admin route and an audit log with admin identity and IP address.
- Where that document rates an item Moderate or Configuration Required, we say so here. Input validation is Moderate because it is inline rather than schema-driven. A WAF, secrets management and monitoring are deployment hardening, and the data feed, casino games, payments and notification accounts are yours to arrange.
Illustrative regulated-operator requirements
A proposed configuration for a lawfully authorized operator, not a client engagement, approval to publish client details or evidence of an operating service.
Exchange & Sportsbook Operator
- The source proposes exchange, sportsbook and casino modules with shared wallet/operations concepts. Assess lawful eligibility, provider rights, account boundaries, limits and reconciliation separately; no module is shown as live.
- If permitted, scope shared-wallet accounting with product-specific eligibility, limits, settlement and reconciliation tests; do not assume shared access is lawful or implemented.
- Identify KYC, age/location checks, exclusion, limits and responsible-gambling requirements with qualified review. Controls need implementation and evidence; no licence readiness or legal sufficiency is certified.
- Define restricted settlement, voiding and reversal workflows with provider references, review steps and auditable records, then test them on the agreed build.
Take the checklist to every seller
Start with whose licence the bets run under. We would rather answer these questions now than after you buy.
Explore White Label Sports Betting Software
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by Bet365 or any other betting operator.
White label sports betting software describes a category of product, not any one company. Brand names appear elsewhere on this site only to describe the kind of platform being built and the terms buyers search for.
Discuss this scope by message
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.com