When transferring a tokenized fund to a new wallet, the receiving side usually must complete whitelist verification, while the sending side depends on the product rules and transfer method.
Both sides do not always need to be whitelisted at the same time, but the receiving address being on the whitelist is basically a hard requirement. Whether the sender needs to be whitelisted depends on whether you are doing an "in-account transfer" or a "cross-chain transfer".
Why the receiving side (new wallet) must pass whitelisting
Shares of tokenized money market funds are legally treated as securities-type products in most cases and face strict transfer restrictions. The fund contract has built-in transfer restrictions. When an address is not on the whitelist, the transfer() function at the contract level will directly revert and stop shares from moving into the new address.
This is why your share transfer to a new wallet may fail or stay pending. The contract checks whether the receiving address is on the "allowed holder list"—if not, it rejects the transfer. This has nothing to do with whether the receiving side holds a crypto wallet. It is a compliance check at the smart contract level, not a wallet compatibility issue.
Does the sender need whitelisting?
It depends on the transfer scenario:
Case A: Transfer within the same fund protocol (such as transferring inside the fund's official app) Some products allow direct transfers between KYC-verified accounts. As long as the sender's address has completed whitelist verification, no extra verification is usually required before the transfer. But the receiving address still needs to be on the whitelist, otherwise the transfer will be rejected.
Case B: Cross-chain transfer (such as moving shares to another chain via a bridge) A cross-chain transfer involves two addresses: one on the source chain and one on the target chain. Some products may require both the sender address and the target address to complete verification, because the "ownership" of the shares changes on both chains. In this case, the sender may also need to complete whitelisting before starting the cross-chain operation.
How to complete whitelist verification for a new wallet
To receive shares, a new wallet needs to complete the whitelist verification process first, instead of receiving a transfer directly. You need to have the new wallet address pass the fund issuer's KYC/AML review. This usually requires identity information and relevant compliance documents. Then the fund team will add that address to the allowed list. This address must be verified by the receiving side themselves; the sender cannot do it for them.
Common reasons for failure
The most common issue is that the sender directly transfers shares to a new wallet, but the new wallet address has never been added to the fund's whitelist. The contract rejects the transfer at the contract level, so the on-chain transaction may succeed but the shares do not arrive—the balance stays at the sender's address. Another reason is that the sender did not confirm the new wallet's KYC status before making an in-protocol transfer, causing the transfer to be rejected by the contract.
Next steps
Before starting a transfer, ask the new wallet address to complete KYC verification and address registration with the fund issuer first. Confirm that the address is already on the official whitelist, then start the share transfer. If you are using a platform's "in-account transfer" feature, contact fund customer service first to confirm the sender's whitelist requirements and the receiver's verification status.
