Skip to content

BaltBet adapts to Russia's stricter betting tax rules by October 2022

Russia's crackdown on betting taxes reshapes how BaltBet operates. Will bettors embrace the changes—or seek riskier alternatives?

The image shows an old book with a picture of a New Russia Company Limited stock certificate on it....
The image shows an old book with a picture of a New Russia Company Limited stock certificate on it. The certificate is printed on a piece of paper with text and numbers written on it, likely indicating the stock price of the company.

BaltBet adapts to Russia's stricter betting tax rules by October 2022

BaltBet, Russia’s oldest and fastest-growing bookmaker, is adjusting to new financial rules starting October 1, 2022. The company must now process all transactions through the government’s Unified Center for Processing Financial Transactions (ETSUPIS). This shift comes as part of stricter regulations on betting and tax compliance across the country. BaltBet has operated legally in Russia since 2010 under a license from the Federal Tax Service (FNS). This permit allows the bookmaker to advertise and run its business openly nationwide.

Under the updated system, BaltBet classifies players as tax agents. This means they must pay a 13% levy on net winnings—calculated as withdrawals minus deposits. The platform automatically deducts this tax, along with service fees, when processing payouts through ETSUPIS. Small-scale bettors receive some relief. Winnings below 4,000 rubles per year remain tax-free. However, those attempting to bypass taxes by using unlicensed bookmakers face legal risks and penalties. The move to ETSUPIS ensures stricter oversight of financial flows. It also simplifies tax collection by integrating payments directly into the withdrawal process.

The new rules take full effect from October 1, 2022. BaltBet’s transition to ETSUPIS aligns with broader efforts to regulate Russia’s betting industry. Bettors will now see taxes and fees deducted automatically, reducing manual reporting and potential errors.

Read also: