Why Is My Exchange Asking for Beneficiary Information Before a Crypto Withdrawal?
If Coinbase, Kraken, or Binance asks for the recipient's name, wallet type, or a self-hosted wallet verification step before a crypto withdrawal, you are usually hitting Travel Rule checks — not losing your coins.
If your exchange suddenly asks for the recipient's full name, wallet type, exchange name, or a self-hosted wallet verification before letting you send crypto, the first reaction is usually confusion.
It feels like the platform is inventing friction right when you finally want to move funds.
In most cases, this is not a sign that your coins disappeared or that support is about to confiscate them. It is a Travel Rule compliance step.
The practical question is not whether the regulation is annoying. It is what the exchange is actually asking for, why the transfer is paused, and how to finish the withdrawal without making a preventable mistake.
Short answer
| If the exchange asks for | What it usually means | Best next step |
|---|---|---|
| Recipient or beneficiary name | The exchange must identify who is receiving the transfer | Enter the real owner of the destination wallet or exchange account |
| Wallet type: exchange vs self-hosted wallet | The platform needs to know whether you are sending to another institution or your own wallet | Choose carefully before proceeding |
| Exchange or VASP name | The destination is another regulated platform and the exchange needs counterparty details | Select the real exchange if it is listed |
| Wallet ownership verification | The exchange needs proof that you control the self-custody address | Complete the signature, self-attestation, or small deposit test exactly as requested |
| Withdrawal blocked until info is added | The transfer cannot proceed without the Travel Rule step | Finish the requested check instead of retrying blindly |
1. This is usually a Travel Rule check, not a wallet failure
The Travel Rule is a set of anti-money-laundering requirements that make exchanges collect and share certain information about crypto transfers.
Coinbase's Europe help documentation says it may need additional counterparty information when users withdraw to a non-Coinbase address or receive deposits from outside the platform. Kraken says EU and UK clients may need to confirm information about both the sender and receiver for some crypto transfers. Binance says users in covered jurisdictions may have to complete deposit or withdrawal questionnaires about the originator or beneficiary.
In plain English, the exchange is trying to answer one or both of these questions:
- Who controls the destination wallet or account?
- Is the destination your own self-custody wallet or another exchange/VASP?
That is why the prompt often appears right before the withdrawal goes through.
2. What "beneficiary information" usually means in practice
The wording sounds more complicated than it usually is.
For many retail users, the exchange is asking for some combination of:
- the recipient's full name
- the recipient's country of residence
- whether the destination is an exchange or a self-hosted wallet
- the exchange name, if you are sending to another platform
- confirmation that the wallet is yours, if you marked it as self-custody
Coinbase's UK help page says users may need to provide the recipient's wallet type, exchange name when applicable, full name, and country of residence. Coinbase Exchange's Europe documentation goes further and says self-hosted-wallet withdrawals may require wallet ownership verification through a digital signature or a small deposit verification.
Binance describes a similar process. Its Travel Rule FAQ says a withdrawal may trigger a questionnaire about the originator or beneficiary, and its address-book verification guide says self-hosted wallets may require a Satoshi Test or a declaration before future withdrawals can be pre-filled.
Kraken's EU/UK update says users may be asked to identify whether a transfer is going to a self-hosted wallet or another VASP, and to verify ownership of a private wallet in some cases.
3. Self-hosted wallet verification is the part that surprises people
This is usually the moment when users think the exchange is malfunctioning.
A self-hosted wallet verification step means the exchange wants proof that the destination address actually belongs to you.
The exact method depends on the platform:
- Coinbase documents two main options: sign a message from a compatible self-custody wallet, or complete a small deposit test by sending an exact requested amount back to Coinbase from the wallet you want to verify.
- Kraken says users may verify ownership with a digital signature, a self-certification, or a Satoshi Test depending on the case.
- Binance says self-hosted addresses may be marked as verified or declared after Travel Rule checks, and some users may need a Satoshi Test to prove control.
The important point is simple:
this step is about proving control of the destination wallet, not about moving your main balance yet.
If you are being asked to sign a message, that should be non-transactional. If you are being asked to do a small deposit test, send the exact amount requested, from the same wallet address you are trying to verify, on the correct network.
4. The biggest mistake is choosing the wrong wallet type
Many users click through too fast and misclassify the destination.
That creates unnecessary delays.
Use this rule:
| Destination | How to think about it |
|---|---|
| Your Ledger, Trezor, Tangem, MetaMask, or other self-custody wallet | Self-hosted wallet |
| Your account on another exchange | Exchange / VASP / platform |
| A wallet address controlled by another person | Usually their self-hosted wallet or their exchange account, depending on where it lives |
If you tell the exchange a destination is self-hosted when it is actually another exchange, or the reverse, the information request can fail or the transfer can be delayed.
That is also why it is smart to prepare your normal destination address before a stressful withdrawal. Our guide on should you use exchange withdrawal allowlisting? explains why pre-approved address-book entries reduce both security risk and last-minute confusion.
5. Why a hardware wallet can still trigger these questions
Users often assume a hardware wallet should bypass this whole process.
It does not.
A Ledger, Trezor, or Tangem wallet is still a self-hosted wallet for regulatory purposes. The exchange may still ask you to:
- confirm that the wallet is yours
- verify the address with a signature or test transaction
- reuse a verified address instead of generating a fresh one every time
Coinbase's small-deposit-test guidance even notes that some chains, especially Bitcoin-style wallets, may rotate addresses for privacy. That can matter because verification may apply only to the address you actually verified.
So if you complete a verification flow once, keep the confirmed address record and label it clearly.
If you are still moving funds into self-custody for the first time, pair this guide with how to move crypto from an exchange to a hardware wallet safely.
6. When the exchange is really warning you about the destination
Sometimes the beneficiary step is routine. Sometimes it is a clue that the transfer setup itself is messy.
Slow down if:
- you do not recognize the wallet type the screen is asking about
- someone else told you what answers to enter
- you are sending to an "investment platform," recovery service, or person you have never met
- the exchange asks for details you cannot verify yourself
- you are rushing because of pressure, fear, or a fake support call
That last point matters.
A scammer often wants you to feel that the exchange is the obstacle and the scammer is the helper. That is backwards. If someone is coaching you through beneficiary questions or wallet verification steps, stop and read crypto support call scam first.
7. What to do if the verification keeps failing
Do not keep guessing.
Use this checklist:
| Check | Why it matters |
|---|---|
| The wallet type you selected | Wrong classification breaks the flow before the withdrawal even starts |
| The exact wallet address | The proof step usually applies only to the specific address being verified |
| The network | A small deposit or verification transaction on the wrong chain will not solve the problem |
| The exact amount requested | Coinbase and Binance both describe exact-amount test flows, not rough estimates |
| Whether the wallet is actually yours | Some exchanges only allow first-party self-hosted wallet transfers in certain flows |
If the issue is not wallet ownership but a broader compliance review, the better next read is why is my crypto exchange asking for source of funds or source of wealth?. If the transfer is blocked for a more general reason, read why can't I withdraw crypto from an exchange?.
Who this guide is for
| Situation | Best takeaway |
|---|---|
| Your exchange suddenly asks for the recipient's name or exchange before a withdrawal | You are probably hitting Travel Rule data collection, not a random bug |
| You are sending from Coinbase, Kraken, or Binance to your own wallet | Be ready to classify the wallet correctly and prove ownership if asked |
| You are moving funds to a hardware wallet for the first time | A hardware wallet is still a self-hosted wallet, so verification prompts are normal in some regions |
| You are worried the withdrawal pause means frozen funds | It usually means the exchange needs more destination information before releasing the transfer |
Bottom line
If an exchange asks for beneficiary information, wallet type, or a self-hosted wallet verification before a crypto withdrawal, the most likely explanation is a Travel Rule compliance step.
The safest response is:
identify whether the destination is your own wallet or another platform, enter the real recipient details, complete the exact verification step requested, and avoid improvising when you are not fully sure who controls the destination.
Explore more
Guides worth reading next
Crypto Exchange Account Security Checklist: What to Lock Down Before You Buy
A practical checklist for securing a crypto exchange account before you deposit, trade, or withdraw: passkeys, 2FA, allowlists, anti-phishing codes, and device reviews.
How to Move Crypto from an Exchange to a Hardware Wallet Safely
A practical withdrawal checklist for moving crypto from Coinbase, Kraken, or another exchange to Tangem, Ledger, or Trezor without using the wrong address or network.
Should You Keep Crypto on an Exchange or Move It to a Wallet?
Decide when an exchange account is enough and when self-custody with Tangem, Ledger, or Trezor is safer.
Should You Use Exchange Withdrawal Allowlisting?
Address allowlisting can slow you down, but that delay is often the point. Here is when Coinbase, Kraken, and Binance withdrawal protections are worth the friction and how to set them up without trapping yourself.
SIM Swap Attacks on Crypto Exchange Accounts: What to Lock Down First
A practical SIM-swap prevention checklist for crypto exchange users: remove SMS-only 2FA, secure email, add backup passkeys, lock withdrawals, and know what to do if your phone service changes unexpectedly.
Why Can't I Withdraw Crypto From an Exchange? The Usual Reasons
If Coinbase, Kraken, Binance, or another exchange will not let you withdraw, the problem is usually a deposit hold, a security cooldown, an account restriction, or temporary wallet maintenance — not disappearing crypto.