Information about who is sending and receiving money has long been required to travel alongside international bank transfers. Extending that requirement to crypto changed how exchanges communicate with each other.
Where the requirement came from
Anti-money-laundering frameworks require that identifying details accompany a payment through every intermediary. The purpose is to let each institution in the chain screen the parties involved.
In banking this works because the message carrying the payment instruction has fields for exactly that data. The information and the money travel together by design.
Public blockchains carry no such fields. A transfer records addresses and amounts, and nothing about the people behind them, so the data must move on a separate channel.
Why the parallel channel is difficult
Two exchanges must agree on a protocol, verify each other's identity and exchange customer data securely before the transfer settles. None of that is provided by the underlying network.
Competing messaging standards emerged, and an exchange using one cannot automatically talk to an exchange using another. Interoperability between these systems remains incomplete.
The transfer itself settles in minutes while the data exchange may take longer. Institutions therefore hold incoming funds until the accompanying information arrives.
The problem of unhosted addresses
A transfer to a wallet controlled by an individual has no institution at the other end to receive the data. There is no counterparty to send it to.
Jurisdictions have taken different approaches, ranging from additional customer declarations to ownership verification requirements. The obligations vary considerably and are still being revised.
Some platforms respond by restricting withdrawals to addresses the customer has verified in advance. Others apply value thresholds below which the additional checks do not apply.
How thresholds change behaviour
Most frameworks apply the requirement only above a specified transfer value. Below it, reduced information is acceptable.
Thresholds create an incentive to split transfers, which supervisors address through rules on linked transactions. Monitoring systems look at patterns rather than individual amounts.
Threshold levels differ between jurisdictions, so the same transfer can be reportable at one end and not the other. Institutions generally apply the stricter of the two.
What it means for the user experience
Withdrawals now commonly ask for the name of the receiving institution or the identity of the wallet owner. That request is a compliance requirement rather than a platform preference.
Transfers between platforms in different regulatory regimes take longer than transfers within one. The delay sits in the data exchange, not the settlement.
The requirements continue to evolve as more jurisdictions bring crypto service providers into existing financial regulation. Anyone transferring across borders is subject to rules at both ends.