Step 1: define the product, applicant and target markets
Describe the service precisely. Conducting a draw, selling third-party tickets, providing ticket-intermediary services, offering instant games and accepting wagers on lottery outcomes should not be treated as one interchangeable legal model. State who contracts with customers, receives money, supplies the product, fulfils prizes and handles complaints.
List the intended markets separately from the place of incorporation or licensing. An authorisation in one jurisdiction is not evidence of unrestricted permission to offer every product elsewhere. The lottery business launch guide helps organise the commercial brief; specialist advice must establish the applicable legal route and restrictions.
White label and turnkey do not settle the licensing question
The white-label versus turnkey comparison concerns operating and implementation responsibilities. It should not be read as proof that a supplier’s licence covers a proposed brand, entity, market or product. Require the exact contracting and authorisation arrangements to be evidenced. This article does not claim that WhiteLotto holds a relevant licence, supplies a sublicence or guarantees regulatory acceptance.
Step 2: build the authority-specific requirements matrix
Use the authority’s current forms, checklist, guidance and any direct instructions received through an authorised process. Give every item a requirement reference, owner, evidence location, version, status and dependency. Track certification, translation, issue dates and validity where required; do not assume that every authority wants the same format or document age.
The following matrix is an editorial preparation aid, not a universal regulator checklist.
| Dossier workstream | Preparation question | Evidence to organise where required | Consistency check |
|---|---|---|---|
| Corporate and control | Which entity applies and who owns or controls it? | Corporate records, ownership chart, governance and relevant agreements | Names, percentages and control rights match across the pack |
| People | Who needs a declaration, assessment or individual approval? | Identity, professional history and requested personal disclosures | Roles and histories match forms and corporate records |
| Funding and forecasts | Where does investment come from and how will the business operate financially? | Funding trail, agreements, supporting records and explained forecasts | Investment, ownership and business-plan assumptions reconcile |
| Product and operations | What exactly will customers receive? | Rules, contracts, customer journey, prize process and complaint arrangements | The narrative matches the actual planned service |
| Technology and suppliers | Which systems and outsourced functions support the service? | Architecture, data and funds flows, supplier scope and required testing evidence | Policies do not promise unavailable platform functions |
| Compliance and customer protection | Which obligations and controls apply to this model? | Tailored policies, responsible owners, workflows and operating evidence | Requirements, contracts, configuration and staff responsibilities align |
Step 3: prepare corporate, personal and funding evidence securely
Keep the ownership and control picture current, including intermediate entities and relevant contractual rights. Confirm the population of directors, owners, controllers and key functions with the responsible specialists. The governance and UBO checklist helps organise these records without determining legal disclosure thresholds.
For funding, distinguish the broader origin of a person’s wealth from the source and route of a particular investment. Build a coherent trail rather than a collection of unexplained bank statements. Label unresolved evidence and assumptions. Personal declarations and financial documents belong in a controlled repository with appropriate access, retention and lawful transfer arrangements, not in unrestricted project email.
Step 4: connect the operating narrative to technical reality
Describe payment collection, ledger records, refunds, prize fulfilment and withdrawals according to the actual product. Use the lottery payment-stack guide to identify handoffs and records. Explain outsourced functions and who retains decision authority, incident ownership and evidence access.
Technical requirements may depend on the product and selected framework. Do not assert that one RNG certificate covers every lottery model or that every application requires the same laboratory test. Ask the responsible specialist to establish the required scope and accepted evidence. The security and uptime checklist helps frame supplier questions, but it is not a certification.
Tailor policies to what the system and staff can actually do. A copied policy describing controls that the platform cannot perform is a substantive inconsistency. Record any pre-launch configuration, staff appointment or third-party dependency still needed before the stated control becomes operational.
Step 5: reconcile the whole dossier before submission
Review horizontally across documents. Legal names, ownership, role titles, products, domains, market assumptions, forecasts and money flows should agree in forms, plans, policies and contracts. Assign suitable specialists to the legal, financial, technical and compliance sections, and give one coordinator responsibility for version consistency.
Create a question log with the exact authority request, owner, evidence, draft response, specialist input and approved answer. Preserve the submitted version instead of overwriting it with the next working draft. Define who may communicate with the authority or make representations for the applicant. The applicant and relevant professionals remain responsible for their declarations and regulated acts.
Scenario: a new investor joins during preparation
Do not update only the ownership chart. Identify every affected declaration, funding statement, governance document, forecast and agreement. Establish whether the change creates another official step or personal assessment, then resolve the relevant dependencies before relying on the changed pack. Retain the original snapshot, the reason for change and the approved replacement.
Step 6: use the current authorised process, then manage follow-up
Immediately before a submission, confirm the official channel is available and the instructions still apply. A historic portal link is not proof that documents can currently be submitted through it. For a specific regional discussion, consult the dated Curaçao lottery-operator preparation guide and the authority’s latest notices rather than reusing old process assumptions.
The authorised applicant representative should approve the exact file set and any disclosed open assumptions. Retain transmission evidence and official acknowledgements. Track subsequent questions and changes against that snapshot. A receipt proves delivery, not completeness, acceptance or approval.
Step 7: separate approval from launch readiness
If an authorisation is granted, read the actual scope, conditions and any remaining dependencies before release. Align live products, entities, domains, public disclosures, contracts and controls with what is permitted. Banking, payment acceptance, technical readiness and target-market permission are separate questions; none should be inferred solely from a licence document.
Assign ongoing obligations and change screening to named owners. Do not wait for renewal to discover that a new brand, supplier, shareholder or product required assessment. A launch gate should include the relevant legal, contractual, operational and technical evidence, not only a working website.
Application readiness checklist
- Confirm the product, applicant, entity roles and market restrictions.
- Build the matrix from current official requirements.
- Reconcile ownership, personal declarations and funding.
- Make policies match the planned system and operating teams.
- Resolve required testing, suppliers and appointments.
- Run completeness and cross-document consistency checks.
- Approve a submission snapshot and keep evidence of delivery.
- Define the post-approval launch and ongoing-obligations gates.
Frequently asked questions
Does one licence cover every lottery type and market?
Do not assume it does. Permission depends on the exact entity, activities, licence scope and relevant market rules. Have qualified advisers establish the position for the proposed service.
Can a small raffle avoid a full licence application?
Some regimes distinguish types of fundraising or non-commercial arrangements, but their conditions cannot be generalised. Obtain advice for the specific event, sales channel and market before relying on an exemption or registration route.
How much will approval cost and how long will it take?
Use current official schedules and scoped professional proposals for the selected route. This guide does not quote fees, taxes or fixed processing times; document preparation and third-party readiness can create separate dependencies.
Source history and scope
The UK Gambling Commission operating-licence guidance illustrates an authority’s attention to identity, ownership, finances, integrity and competence; it does not establish another jurisdiction’s requirements. The Curaçao Gaming Authority’s online-gaming regulation page is regional primary context, not proof that a particular lottery model qualifies.
This is editorial preparation, not an independent qualified legal review or a WhiteLotto licence, certification, sublicensing or approval guarantee. Use the legal, tax and audit specialist guide to scope the professional work separately.
Discuss the platform evidence for your application
Bring the confirmed model and requirements matrix to WhiteLotto to discuss implementation scope, integrations and evidence the platform workstream can supply. Keep jurisdiction advice, applicant declarations and official submissions with the appropriate authorised parties.
Discuss lottery platform implementation
Wojciech Lysak is Managing Director of White Lotto and a senior iGaming B2B expert with nearly 20 years of experience. He specializes in white label online lottery platforms, turnkey solutions, gaming systems, and scalable B2B solutions for operators across global markets.
A recognized industry leader and visionary, he actively participates in major iGaming events worldwide and has led the creation of multiple successful platforms and projects across the gaming sector.
If you’re interested in starting your own online business in the iGaming sector, Wojciech will help you take your first steps on the path to success. LinkedIn