The user said in a Sept. 6 Trustpilot review that they attempted to send 10 USDT over the TRC20 network to lolz.market on Aug. 28. According to the complaint, the withdrawal was declined and funds elsewhere in the Bybit account subsequently became unavailable.
The customer said the restriction was not limited to the attempted transfer. Roughly 1,000 USDT held elsewhere in the account was allegedly locked under a suspicious-activity review.
The user also claimed that Bybit had not requested supporting documents or provided a timetable for completing the review. Bybit responded publicly to the complaint on Sept. 6, saying the case was being escalated directly to its compliance team.
The allegations have not been independently verified, and there is no public indication from Bybit that the lolz.market destination itself caused the restriction. The company’s public response confirms that the case is being escalated but does not disclose what triggered the compliance review or whether the account will remain restricted.
The case is notable because of the disparity between the size of the attempted transaction and the amount allegedly rendered inaccessible. A 10 USDT transfer is a relatively small transaction, while the customer’s account reportedly contained around 1,000 USDT that could no longer be used.
That does not necessarily mean Bybit’s compliance system judged the 10 USDT transaction itself to be suspicious. Cryptocurrency exchanges routinely use automated transaction-monitoring systems that can assess wallet addresses, transaction history, counterparties and broader account activity. A small transfer can therefore potentially trigger a review if the destination or surrounding activity generates a risk signal.
Bybit’s terms and compliance framework give the exchange broad powers to restrict transactions and accounts where it suspects violations of applicable laws, sanctions, fraud, money laundering or other prohibited activity. Such controls are a standard part of operating a large centralized exchange.
The wider customer-support record makes the latest complaint worth watching rather than dismissing as an isolated technical problem. Bybit’s Trustpilot page contains numerous recent complaints involving payments, customer service and account restrictions, although those reviews do not establish that the cases share a common cause.
Other recent user complaints have also described funds becoming unavailable during reviews. One Aug. 29 complaint, for example, alleged that nearly 20,000 USDT had been frozen for weeks following a TRC20 transaction and remained under review after documents were submitted. That is a separate allegation and should not be treated as evidence that the two cases are connected.
For the latest case, the key unanswered question is what Bybit’s compliance team identified in connection with the 10 USDT transfer.
The Compliance Question Is Bigger Than the 10 USDT
The interesting part of this complaint is not really the 10 USDT. It is the possibility that a very small outbound payment can become the trigger for a much broader account review.
From an exchange’s perspective, that approach is understandable. Blockchain transactions are permanent, and a destination address associated with illicit activity can create risk regardless of how much money a customer is attempting to send. Screening the counterparty before allowing the transaction to proceed is therefore an important part of an exchange’s anti-money-laundering controls.
The problem is what happens after the alarm goes off.
There is a major difference between rejecting a questionable 10 USDT withdrawal and making a customer’s unrelated funds unavailable. The latter creates a much bigger customer-service issue because the user may have legitimate assets that are not directly connected to the transaction being reviewed.
This is where transparency becomes important.
An exchange does not necessarily need to disclose the exact reason for a compliance flag. Doing so could interfere with investigations or reveal information about its monitoring systems. But customers still need some indication of what is happening, whether additional information is required and whether there is an expected review process.
The complaint specifically alleges that none of those answers were provided.
That makes Bybit’s public response potentially more significant than the original complaint. The exchange has acknowledged the case and said it is being escalated to compliance, creating an opportunity to determine whether the restriction was caused by the destination address, the customer’s account history, a blockchain-risk signal or something else entirely.
There is also a useful editorial distinction here. Customer reviews can show that something happened from a user’s perspective, but they cannot establish why an exchange acted. Even multiple similar complaints would not prove that a particular wallet, marketplace or transaction type is being systematically blocked.
What would turn this from a customer complaint into a stronger story would be evidence showing a repeatable pattern: other Bybit users reporting restrictions after transfers to the same marketplace, screenshots showing the precise compliance message, or a response from Bybit explaining its treatment of the destination.
The lolz.market angle is therefore worth investigating, but it should not yet be presented as evidence that Bybit has blacklisted the marketplace.
For now, the strongest story is narrower: a customer says a failed 10 USDT transfer was followed by a wider freeze, and Bybit has escalated the case to compliance.
If the exchange ultimately explains that the destination generated a risk alert, the episode could offer a useful glimpse into how centralized exchanges are increasingly applying blockchain-risk screening to ordinary customer payments — and how far those controls can extend once an account is flagged.
That question is particularly relevant as users increasingly turn to self-custody when concerns about centralized platforms and access to funds arise.
The case also sits within a broader shift toward stricter regulatory expectations for MiCA-compliant crypto businesses, where transaction monitoring and customer-protection controls are becoming increasingly important parts of operating a regulated exchange.