PlayCity opens tender for software to block gambling access for Ukraine’s military personnel

Ukraine’s gambling regulator, PlayCity, has opened a tender for software that would automate restrictions on gambling access for military personnel. For PSPs and operators, the interesting part is not the policy headline but the plumbing: the system is meant to verify eligibility through state registers without handing commercial operators sensitive military-status data.

1. PlayCity announced the tender on August 24, 2026, according to its official website. The software is intended to create the technical link needed for automatic checks under a government-approved restriction on members of the armed forces.
2. The planned module is expected to connect the Register of Persons Restricted from Access to Gambling with the relevant state register covering military personnel. PlayCity says this is one of the technical steps required before automatic verification can begin.
3. The data exchange layer will run through Trembita, Ukraine’s national interoperability system for exchanging information between public-sector information systems and state registers. In practice, that means operators would receive only the answer they need — whether access must be restricted — rather than direct access to the underlying military records.
4. That design matters because military status is sensitive information. A limited-result model reduces unnecessary disclosure while still allowing the legal restriction to be enforced, which is the sort of architecture compliance teams and PSPs tend to prefer when they are asked to build around restricted categories.
5. The timetable is tied to Cabinet of Ministers Resolution No. 804, adopted on June 17, 2026. Ukrainian legislation records the resolution as partially effective, and the current regulatory framework cites December 24, 2026 as the deadline for the required interaction and testing stage between PlayCity and the Ministry of Defence.

For high-risk operators, the key takeaway is that Ukraine is moving from a paper restriction to an automated control model. That usually means new integration requirements, more attention to data minimization, and fewer excuses for manual workarounds once the registers start talking to each other.