Which Part of the Receiving Destination Does the Withdrawal Form Reject?

Treat an address-format error as a stop sign. It can mean the address belongs to another asset, another network, an unsupported legacy or new format, or simply the wrong form field. It can also be syntactically valid while the selected exchange route does not support it. Reopen the receiving wallet or exchange and rebuild the complete destination instead of modifying characters or trying random converters.

Use the Destination Packet Validator

A complete withdrawal destination has three validation layers.

• Syntax layer — characters, length, checksum and address-family rules
• Platform layer — the sending exchange supports this format and network
• Route layer — the receiver supports the exact asset, network, memo and amount

Recreate the destination from the receiving side

Open the intended wallet or exchange, choose the asset and network, and use its Receive or Deposit screen. Copy the full address and any memo or tag. Do not copy from transaction history, a search result, an old email or a different coin’s deposit page.

Cause 1 — the address was entered in the wrong field

Kraken currently lists entering a withdrawal address in the Description field as a cause of Invalid Address errors. Labels and address-book names belong in their own field. Recheck every form label before diagnosing the blockchain format.

Cause 2 — wrong asset family

A DOGE address commonly begins with D, while an XRP address commonly begins with r and an EVM address begins with 0x. Prefixes can identify obvious mismatches, but they are not a universal safety check. Use the receiver’s selected asset as the authority.

Cause 3 — right asset, unsupported address type

Bitcoin can use formats beginning with 1, 3, bc1 or bc1p, but a particular platform can support only a subset at a given time. Kraken documents supported and unsupported types and notes that new formats may not yet be accepted. The receiving wallet can be valid while the sender is not ready for that address family.

Cause 4 — old or deprecated format

An older address format can remain recognizable but be rejected after platform changes. Generate a fresh address from the current receiving application. Do not use an online converter unless the official platform documents the conversion and the resulting destination is independently verified.

Cause 5 — same-looking EVM address, wrong selected network

Ethereum, Base, Arbitrum and BNB Smart Chain can display the same 0x account text. The form can accept the syntax while the route remains incompatible, or it can reject the address because the selected asset is available only on another network. Match the chain on both sides.

Cause 6 — USDT network mismatch

Kraken currently lists USDT ERC-20 addresses with a 0x prefix and TRC-20 addresses beginning with T or represented in hexadecimal form. A TRON address is not an Ethereum address merely because both can receive USDT. The token ticker does not identify the chain.

Cause 7 — missing memo or tag is usually a separate field problem

XRP, XLM and other custodial deposit routes can require an account identifier in addition to the address. Do not append the memo to the address string unless the receiving service explicitly provides a combined format. A valid address without the required routing value is still incomplete.

Cause 8 — URI or QR content was pasted instead of the address

A QR code can contain a scheme, amount or parameters such as bitcoin: or ethereum:. Some withdrawal forms accept only the bare address. Compare the decoded content with the text shown by the receiver and copy the address field directly.

Whitespace and invisible characters

Copying from formatted text can add spaces or line breaks. Paste into a plain-text field locally, remove only surrounding whitespace and compare the full string again. Never delete internal characters to make the form accept it.

Contract addresses and smart-account destinations

Some services reject contract addresses or require a compatible deposit method. A 0x contract is syntactically valid but may not support the asset or transfer mechanism used by the exchange. Confirm with the receiver before selecting another address.

Worked Bitcoin format case

A wallet generates a bc1p Taproot address, while the exchange’s current withdrawal page supports 1, 3 and bc1 but not bc1p. The user generates a supported receiving address from the same trusted wallet rather than changing the Taproot string.

Worked USDT case

The exchange withdrawal is set to USDT TRC-20, but the pasted destination begins with 0x and came from an Ethereum deposit page. The error is not a typo. The user either selects the receiver’s supported TRON deposit route or abandons the transfer.

Do not force acceptance with a random address

Changing the network, choosing another coin or pasting an address from a different wallet can remove the warning while creating a more dangerous route. The destination must belong to the intended user and support the selected asset.

When support is appropriate

Contact the sending exchange when its current documentation says the address type is supported but the form rejects it. Include the asset, network, address type, masked destination, error text and screenshot of the receiver’s deposit page. Do not include private keys.

The successful end state

The form should accept a destination generated by the receiver, and the user should be able to reproduce the asset, network, complete address, memo and minimum from the receiving page. Acceptance alone does not prove the later transfer will be credited.

Address-format sources — July 30, 2026

Current Kraken and wallet documentation illustrates how address support is platform-specific. Always use the live sender and receiver interfaces.

• Kraken supported withdrawal address formats: https://support.kraken.com/gb/articles/360001474826-supported-address-formats-for-cryptocurrency-withdrawal
• Coinbase destination tag and memo requirements: https://help.coinbase.com/en/coinbase/trading-and-funding/sending-or-receiving-cryptocurrency/destination-tag-memo-faq
• Coinbase supported-deposit warning: https://help.coinbase.com/en-gb/coinbase/trading-and-funding/sending-or-receiving-cryptocurrency/unsupported-crypto-deposits
• MetaMask EVM address-format explanation: https://support.metamask.io/more-web3/learn/the-ethereum-address-format-and-why-it-matters-when-using-metamask/
• Bitcoin address information: https://bitcoin.org/en/you-need-to-know

FAQ