Ukraine’s PlayCity Launches Tender for Military Gambling Blockade Software by December 24, 2026

Ukraine’s gambling watchdog PlayCity has launched a tender for software that will block military personnel from regulated gambling sites and licensed venues. For PSPs and operators, the important part is not the headline politics but the plumbing: once the Ministry of Defense plugs this into state registers, account onboarding in Ukraine gets another mandatory screening step.

1. PlayCity is acting on a government order that requires military servicemen and women to be prohibited from gambling. The stated rationale is twofold: fears that Russian operatives are using gambling-related dependency to blackmail soldiers, and concerns that gambling problems are reducing army combat readiness.
2. The new module will be developed first, then implemented and enforced by the Ministry of Defense. It will use information from state registers through the Trembita system, which is the technical layer that lets public registers talk to each other for eligibility checks.
3. When an account is created, the system will send a request to the Register of Persons Restricted from Access to Gambling and run an automated check. If there is a match, the person will be denied access to regulated gambling websites and licensed venues.
4. The ministry wants the software solution implemented no later than December 24, 2026. It will sit on top of existing guardrails, including self-exclusion, rather than replacing them.
5. The source text also flags the obvious weak point: illegal gambling websites that target vulnerable people and problem gamblers, including military personnel. In other words, a regulated-market block only works as far as the operator stays inside the regulated market.

The practical takeaway for high-risk payment providers is straightforward: if Ukraine’s implementation goes live as described, military status becomes another data point in KYC/onboarding and risk-screening flows. That matters for operators, PSPs, and acquiring partners because it can affect account approval logic, customer exclusions, and the volume of transactions that need to be filtered before they ever reach a payment page.