Recently, a Binance user accidentally sent 11,000 USDT to the wrong person, leaving many people wondering: If the UID was checked, how did the funds still end up with a stranger?
The main reason is that Binance has multiple independent account systems.
Many users assume that Binance is a unified platform and that UIDs are valid across the entire platform. That is not the case.
Besides the international platform, there are Binance US, Binance TR in Turkey, and Binance TH in Thailand. Each holds the relevant local operating licenses and is run by a different, independent legal entity.
There are just two words behind the decision to separate accounts: compliance.
The regulatory frameworks for crypto assets in the United States, Turkey, and Thailand differ greatly. Licensing requirements, KYC standards, anti-money laundering rules, user data storage, custody of funds, and connections to local banks are all managed separately. Regulatory requirements call for segregation, so platforms must build separate, isolated account, fund, and user systems.
There’s a critical vulnerability here that’s very easy to overlook: UID numbers are unique only within the current site.
For example, a user on the Thailand site has UID 123456. That same number could easily be assigned to a completely unrelated user on the main site.
If you get the UID of someone on another regional site and initiate an internal transfer on the main site, the system won’t recognize that it’s a cross-site transfer. It will send the assets straight to the account of a stranger on the main site with the same UID.
That’s exactly what caused this mistaken transfer.
In response to this incident, the platform took action: Yijie personally reimbursed the user for their loss, and the product was updated with transfer risk alerts and improved confirmation steps.
To be objective, crypto transfers have a harsh reality: once most transfers are confirmed on-chain, there’s no way to reverse them—unlike bank transfers, which can be stopped.
That’s why risk checks and confirmation beforehand are the only lines of defense.
Here are a few practical tips to avoid mistakes:
First, for internal transfers, don’t rely on the UID alone. Check the nickname and profile picture too, and confirm large transfers a second time using a screenshot.
Second, if the platform lets you add friends, choose the recipient from your friends list to avoid errors from manually entering a UID.
Third, don’t use UID-based internal transfers between regional sites. Ask for an on-chain deposit address instead. On-chain addresses are unique across the network, so there won’t be any duplicates. For large transfers, always send a small test amount first, and transfer the rest only after confirming it arrived.
Fourth, don’t transfer funds when you’re not in the right state of mind. Staying up late, feeling rushed, or being emotionally unsettled are all times when mistakes are more likely.
To reiterate: this multi-account isolation model is an architectural design adopted by overseas exchanges to meet the regulatory requirements of different regions. It’s a product of compliance, but it also creates the risk of UID conflicts.

