Keep the applicant, product and evidence consistent
The application brief should identify the operator entity, proposed games, platform configuration and suppliers. If a test report concerns a different software version or game configuration, establish whether it supports the proposed deployment before treating certification as complete.
Compare the contracting entity and domain with the authority's online-operator information. A brand name alone is not enough to establish who holds the concession or what relationship a new project would have with it.
Budget the complete operating arrangement
Separate the current concession-related payments and tax assessment from platform fees, testing, payments, staffing and acquisition spending. Use current authority material for each applicable charge rather than carrying an old percentage into a new financial model.
The release plan should list the evidence needed before accepting players and name an owner for each unresolved item. Commercial readiness and regulatory completion are separate milestones.
Discuss the Colombian project with SuperBluOrange using the intended entity, product list and concession status. We can then scope the software and integration work around the actual application, rather than describe a foreign license as a shortcut into Colombia.
Last source review: October 17, 2026. Recheck applicable rules before committing.