Bitcoin and Ethereum do not share a deposit lane. A BTC to ETH exchange delivers a different native asset on a different network. It should finish with ETH that your Ethereum wallet can use, rather than an ERC-20 token representing Bitcoin.
The hand-off deserves a little attention even if the design deserves a little less. Verify the Bitcoin deposit instructions produced for this exchange, keep your exchange reference, and check that the receiving wallet is set to Ethereum. Those checks are more useful than an impressive-looking conversion number copied from yesterday.
01/Native ETH is the target
Select ETH on Ethereum in the receiving picker. WETH is a separate token, and wrapped Bitcoin is a different result entirely. A familiar 0x address format does not tell you which network a service accepts. Confirm Ethereum support on the receiving wallet or exchange account before relying on that address.
02/Bitcoin deposits have their own fee decision
Your Bitcoin wallet chooses or estimates a miner fee for the source transaction. The time until a deposit is observed depends partly on that transaction reaching the network and meeting the route’s requirements. A higher-level swap estimate is not a guarantee about a transaction your wallet has not yet broadcast.
03/Give a refund somewhere useful to go
If you provide a refund destination, it must be compatible with the source asset and the provider’s flow. For a Bitcoin source, check the requested Bitcoin refund details. Do not automatically reuse the Ethereum destination as a Bitcoin refund address. If you send from a custodial platform, make sure it can handle the return path described by the provider.