Image Credit: Shutterstock
Key Takeaways
- Bitget is applying enhanced compliance review in three phases from August 7 through August 23, covering 16 platforms including HTX, EXMO, and Rapira.
- The August 23 phase overlaps with Binance’s separate restrictions on HTX, though neither exchange has confirmed a shared source for the lists.
- Bitget places responsibility on users to verify their transactions aren’t linked directly or indirectly to the flagged entities.
Bitget is rolling out enhanced compliance controls on transactions tied to 16 crypto platforms, according to a support notice the exchange published this month. The restrictions apply in three phases running from August 7 through August 23 and cover entities including HTX, EXMO, and Rapira.
What Bitget’s Notice Says
Bitget said it will apply additional controls to transactions involving the listed entities from their respective effective dates. The notice states that attempted transactions involving the entities, whether direct or indirect, may face enhanced compliance review or rejection. Accounts connected to the flagged transactions could face restrictions while a review is pending.
The exchange said the relevant activity could also breach its terms of use, which may lead to account termination. Bitget advised users sending or receiving digital assets to verify that the transaction source, originating address, destination address, and any intermediary service provider are not connected to the listed entities.
The notice frames this as an ongoing obligation rather than a one-time check, since new entities could be added in future phases.
The Three-Phase Rollout
The first phase took effect August 7 and covers Aban Tether Exchange and Shelbit General Trading. The second phase began August 13 and adds A7 Africa, A7 Nigeria, and PilotFinance. Bitget’s notice describes this rollout as a continuation of controls the exchange has applied to sanctioned entities in prior months, rather than a single response to one new designation.
The third and largest phase takes effect August 23 and covers 11 entities: ABCeX, Aifory Pro, BitPapa, EXMO, Exnode and Exnode Pay, HTX, Monease, NoOnecrypto, Rapira, Tradex, and WhiteBird. Bitget did not specify a single triggering action for this phase, and the entities span multiple jurisdictions.
How This Compares to Other Exchange Actions
The August 23 list overlaps with a separate restriction Binance placed on 11 platforms, a group that also includes HTX.
Bitget’s notice does not name the specific sanctioning authority behind each entry, and it is unclear whether the overlap reflects a shared set of sanctions designations or independent decisions by each exchange. Neither exchange has confirmed publicly whether the two lists were compiled from the same source.
Earlier restrictions from Bitget and other exchanges have followed U.S. Treasury sanctions targeting crypto platforms accused of helping evade restrictions, including prior Treasury actions against Iran-linked exchanges.
Whether the August 23 additions stem from the same Treasury action, a separate European Union measure, or a combination of designations has not been confirmed directly by Bitget and has not been confirmed by a named regulatory source.
What Users Need to Check
Bitget’s guidance instructs users to take responsibility for verifying their own transactions. The exchange said it will not simply block deposits or withdrawals tied to the listed names, but will also scrutinize indirect exposure through intermediary wallets or service providers.
That distinction matters for anyone routing funds through multiple platforms before reaching Bitget. A transaction that never touches HTX or EXMO directly could still trigger review if an intermediary address has processed funds connected to one of the listed entities.
Bitget’s notice indicates that users with existing balances on any of the 16 platforms, or with recent transaction history involving them, are likely to be affected first by the new checks.
Bitget said its support team will assist users whose accounts or transactions are affected during the review process. The notice does not specify a review timeline or an appeals process beyond directing users to support, leaving open how long an affected account might remain restricted while compliance staff examine a transaction’s history.
Bitget’s notice does not address whether users holding balances on the affected platforms themselves, rather than transacting with them through Bitget, face any separate obligation. The guidance is limited to transaction screening on Bitget’s own platform.
