HTX’s terms reportedly listed Russia as a restricted jurisdiction by September 2026, before the October 23 media coverage. The UK designated HTX operator Huobi Global S.A. in May, followed by
Cryptocurrency exchange HTX’s restrictions on Russian customers appear to have been in place since September 2026, following months of direct sanctions pressure on the platform’s operating entity.
The United Kingdom designated Huobi Global S.A. in May, while the European Union introduced additional measures in July targeting cryptocurrency-related financial activity connected to Russia.
By September, HTX’s user agreement reportedly included Russia among its prohibited jurisdictions. The provision gives the exchange authority to restrict access, suspend withdrawals and terminate accounts.
The policy attracted wider attention after Russian business outlet RBC reported the restriction on October 23.
For customers, the outstanding issue is operational rather than contractual. Russia is listed as restricted, but HTX has not publicly established a universal withdrawal deadline or clarified how the provision applies to every existing account.
HTX’s regulatory exposure provides important context for the change in its customer eligibility rules.
On May 26, 2026, the UK designated Huobi Global S.A., the Panama-registered entity associated with HTX, under its Russia sanctions framework.
The official UK sanctions notice identifies the company and lists HTX and HTX Exchange among its trading identities.
The designation imposes restrictions on persons subject to UK sanctions law, including applicable asset-freeze obligations.
The European Union subsequently adopted Council Decision (CFSP) 2026/1849 on July 23.
The legislation expanded Russia-related restrictions involving cryptocurrency services and third-country platforms. Its provisions address financial channels that could facilitate activity prohibited under the EU sanctions regime.
These measures are legally distinct from HTX’s decision to restrict Russian customers.
A government sanction against an exchange and an exchange’s prohibition on customers from a particular jurisdiction operate through different legal mechanisms.
Nevertheless, the sequence is relevant. By the time Russia appeared in HTX’s restricted-jurisdiction terms, the platform had already encountered direct restrictions from major Western jurisdictions.
There is no verified HTX statement establishing that those sanctions caused the September policy change.
HTX’s Platform User Agreement identifies prohibited jurisdictions in Section 1.2.
The restrictions apply to individuals residing in or physically located in Russia, as well as businesses registered or primarily operating there.
This means the eligibility criteria extend beyond citizenship.
A customer with Russian citizenship who permanently resides elsewhere may face different contractual considerations from a non-Russian citizen physically located inside Russia. The exchange’s own eligibility assessment remains decisive.
Under the agreement, HTX may restrict access to its products, suspend withdrawals or terminate accounts that do not meet its requirements.
The September 19 date was identified in a HashTelegraph review of the agreement.
However, that date has not been independently authenticated against an archived copy of the agreement for this article. It should therefore be treated as a reported document date, not proof of when the restriction became operational for every account.
The available information does not establish whether HTX has implemented simultaneous account restrictions, allowed a transition period or issued separate notices to affected customers.
HTX’s policy has emerged alongside separate restrictions introduced by Bitget and MEXC.
Bitget added Russia, Belarus and Kazakhstan to its prohibited-jurisdiction list in October.
According to The Moscow Times, the exchange stopped affected users from opening new positions on October 18 and instructed them to close positions and withdraw assets by October 21.
MEXC announced its withdrawal from Russia and Belarus on October 20.
In its official customer notice, MEXC said affected users would receive individual notifications specifying the required steps and deadlines.
The exchange also stated that customers who had not received such a notice were not affected by that particular change.
The policies therefore differ in how account restrictions are communicated and implemented.
Exchange Access Monitor Russia Restrictions: HTX vs. Bitget vs. MEXC A comparison of reported restrictions and withdrawal procedures as of October 24, 2026. HTXTimeline Unconfirmed
Policy status Russia listed as restricted in terms reportedly dating to September 2026. Withdrawal arrangements No universal account-closure or withdrawal deadline publicly confirmed. BitgetDeadline Reported
Policy status Russia added to prohibited jurisdictions in October 2026. Withdrawal arrangements October 21 deadline reported for affected customers to close positions and withdraw assets. MEXCIndividual Notices
Policy status Market exit from Russia and Belarus announced October 20, 2026. Withdrawal arrangements Affected customers receive account-specific notifications with procedures and deadlines. Sources: HTX agreement reviews, Bitget reporting and MEXC’s official announcement. Individual account restrictions may differ.For traders holding assets on centralized exchanges, the difference is financially significant.
An exchange can disable new trading activity while temporarily preserving withdrawal functionality. Another may require users to complete additional verification before funds can be released.
Neither arrangement should be assumed to apply automatically to HTX.
The consequences of sanctions can extend beyond whether an exchange accepts customers from a particular country.
Cryptocurrency platforms rely on external infrastructure, including banking partners, liquidity providers, payment processors and other exchanges.
Restrictions affecting one platform can influence how those counterparties handle transactions associated with it.
Bitget, for example, published an August compliance notice identifying HTX among entities subject to enhanced transaction controls.
The notice warned that transactions directly or indirectly connected to listed entities could face additional review or rejection.
This creates a practical risk for customers moving assets between centralized platforms.
A withdrawal may be technically possible on the originating exchange but encounter compliance checks at the receiving institution.
The issue is particularly relevant for transfers involving sanctioned entities, where blockchain transaction histories can be used to identify prior exposure.
However, restrictions on an exchange do not mean every customer or every transaction involving that platform is automatically subject to the same legal prohibition.
The applicable jurisdiction, counterparty, transaction history and specific sanctions provisions determine the relevant obligations.
HTX’s published contractual restrictions do not provide enough information to determine the withdrawal status of every Russian-linked account.
Customers should check their account notifications and the official HTX support channels for instructions specific to their circumstances.
Customers should also be cautious about unsolicited messages claiming to provide special withdrawal procedures.
MEXC has specifically warned users about impersonation attempts involving requests for passwords, recovery phrases or payments through unofficial channels.
Using a VPN does not change contractual residency requirements and should not be treated as a reliable way to restore account eligibility.
No live HTX account testing was conducted for this article, and current withdrawal availability for individual Russian customers has not been independently established.
The next material development would be a formal HTX notice specifying how the Russian jurisdiction restriction applies to existing accounts, including withdrawal access and any transition arrangements.
Until then, customers should distinguish between being contractually ineligible to use an exchange and having an account that is already operationally restricted.
The post HTX Russia Restrictions Follow UK and EU Sanctions Pressure appeared first on ETHNews.
