It clearly shows a pattern of deliberate delay rather than a genuine KYC standard.
Your issue actually falls outside standard KYC procedures, as you deposited funds outside of established protocols. Most services tend to view special cases like yours as complicated, especially when the recoverable amount doesn't seem to justify the effort from their perspective; though they should still cooperate with the recovery process even if it means explicitly stating the associated costs.
Thanks for taking the time to gather those links and stats. Looking at the Trustpilot feedback and earlier threads, it's pretty clear this isn't just an isolated glitch, but a widespread issue with how non-standard deposits and KYC/video requests are handled.
I definitely should have looked deeper into their recent track record before depositing. That said, since the funds are already stuck, I’ll keep this thread updated with exact timelines and proof.
If senior support or compliance decides to review my case and resolve it properly, I’ll document that here as well. Until then, hopefully this thread serves as a clear heads-up for anyone else searching for recent feedback on HTX.
Sorry, I actually meant to quote a Slow death`s post with links
It clearly shows a pattern of deliberate delay rather than a genuine KYC standard.
Your issue actually falls outside standard KYC procedures, as you deposited funds outside of established protocols. Most services tend to view special cases like yours as complicated, especially when the recoverable amount doesn't seem to justify the effort from their perspective; though they should still cooperate with the recovery process even if it means explicitly stating the associated costs.
I disagree that a non-standard deposit justifies a total breakdown in compliance.
Even if a manual recovery requires extra effort, a major exchange should either provide a clear protocol/fee for manual processing or explicitly declare its technical limitations.
Demanding a 1.2 GB screen recording, putting the user through complex video-KYC, and then silently marking the ticket as [REJECT] with "no response from user" isn't a "technical complexity"—it's a deliberate lack of transparency. If they have recovery fees, they should state them instead of running users in circles.
In May, the UK introduced sanctions against Huoba, later adopted by the EU. The result is that all coins connected to HTX are automatically marked as dirty, which significantly increases (freezing) the risk of using such funds.
I am interested in the motives of a person to send a centralised stablecoin to such an exchange today and whether such a person is aware of the risks. Even if HTX has no wrong intentions and has the best will to process all transactions, there is a third party that can stop the funds there.
Valid point regarding the AML risk scoring and recent UK/EU sanctions.
In my case, this was a specific transaction context, and I certainly didn't anticipate HTX’s internal automated flag loop. However, the core issue isn't even a third-party issuer freeze (like Tether blacklisting an address).
The issue is HTX’s own compliance handling: accepting the deposit, demanding exhaustive video-KYC (1.2 GB), and then silently defaulting to a [REJECT] status with incorrect labels like "user didn't respond".
If a deposit is rejected due to sanction-related AML scoring or third-party restrictions, an exchange should explicitly state that reason or issue a formal return protocol, rather than running users in bureaucratic circles.