EN Before a crypto deposit: check network, address and memo
Contents
At a glance
Check an exchange deposit route before sending: match the asset and network, copy the required memo, review limits and confirm that the funds were credited.
Prepare a deposit record before opening the send screen
This guide is for someone transferring cryptocurrency from a wallet or another platform into their own exchange account. The goal is to check the receiving instructions before authorising a transfer, then distinguish a blockchain transaction from a credited account balance. You need access to both services and their current deposit and withdrawal screens. You do not need to share a recovery phrase, private key or password.
Open the receiving service independently through your usual app or saved address. Select the actual account and product you intend to fund: instructions for an exchange account do not automatically apply to a separate self-custody wallet. In a private note, record the asset, receiving network, deposit address, memo requirement and time of your check. Leave unknown fields visibly unresolved. This note is an editorial working aid, not a substitute for the provider's live instructions or an assurance that the platform is solvent. [1][2]
Match the asset and network at both ends
Start on the receiving side. Coinbase's receive instructions ask you to choose an asset and network before displaying the address and any required memo. Kraken similarly asks you to select the cryptocurrency and an available deposit network. Now open the sending service and compare the exact route it offers. A matching token name alone does not complete that comparison.
Write the sending network beside the receiving network. If they differ, pause; do not choose whichever option has the smallest fee. If an interface uses an unfamiliar abbreviation, resolve it through that provider's official documentation before continuing. Treat wrapped or bridged versions as a separate compatibility question. Do not infer support from a familiar logo. The practical completion criterion is an explicitly supported asset-and-network route at both ends for your account, rather than a general statement that the exchange lists the asset. [1][2][5]
Copy the address and the required memo separately
Use the receiving screen's copy controls for the address and, when displayed, its destination tag or memo. Coinbase explains that this extra identifier can allocate deposits at a shared address to the correct customer. An address can therefore be correct while the account-routing information is missing. A sender's optional-looking field does not override a receiving platform's requirement.
Paste each value into its intended field and compare it with the original, including the complete memo. Do not put the memo into a personal transaction note unless the provider explicitly identifies that field as the on-chain memo. If you scan a QR code, inspect the populated fields afterwards: Kraken specifically warns users to ensure required tags or memos are included. If the receiver requires a memo but the sender offers no suitable field, stop and ask official support which transfer method is supported. [1][3]
Read minimums, restrictions and processing conditions
Read the warnings on the selected deposit screen before choosing an amount. Record any minimum deposit, fee, account-verification condition and expected confirmation requirement shown for that particular route. Kraken's processing documentation says minimums differ between cryptocurrencies and that crediting requires blockchain confirmations. Its estimates depend on network conditions. Do not turn an estimate into a promised arrival time.
If considering a small trial transfer, first establish that the amount expected to arrive meets the receiving requirements after applicable deductions. An arbitrarily tiny transfer may be a poor test. Coinbase suggests considering a test amount, but it does not replace compatibility checks. Check the provider's status page for the specific asset or network, not only the service-wide headline. If deposits are suspended or instructions conflict, postpone the transfer. Do not work around a restriction by selecting another network without repeating the compatibility check. [3][4]
Recheck the final transfer screen
Before authorising, compare the final confirmation screen against the receiving instructions, not just against the note you copied earlier. Recheck the asset, network, full address, required memo, amount and displayed fee. A QR scan or saved recipient is convenient input, not evidence that all fields still match the intended deposit. If a field has changed, return to the receiving screen and resolve the discrepancy.
If you use a trial transfer, wait for the receiving account to credit it before deciding whether to proceed with another transfer. Recheck the instructions again for that later transfer. A successful trial shows that one transfer was credited under those conditions; it does not guarantee future availability, a larger transfer's treatment or the platform's financial condition. Keep the confirmation details privately. Avoid posting account screenshots or a complete transaction history in public support discussions. [1][3]
Work through a mismatch without sending
Consider a fictional transfer where the receiving screen offers network A, while the sending screen defaults to network B. Both screens display the same asset name. The working record should say 'network mismatch: unresolved', and the send action remains unapproved. The next step is to find a supported common route in the official interfaces, not to experiment with a live transfer. These letters describe a hypothetical example, not named networks or actual account support.
Now suppose the receiving screen also displays a memo but scanning its QR code fills only the address. Copy the memo into the dedicated field and compare the complete result. If there is no dedicated field, the example remains blocked. Only after both discrepancies are resolved should you revisit the amount, fee and deposit conditions. This deliberate stop point prevents a visually plausible address from concealing two separate unanswered questions. [1][3][5]
Verify crediting and handle a missing deposit
After sending, save the sender's transfer record and transaction hash when available. A transaction hash identifies the blockchain transaction; it is different from an internal exchange reference. Check the correct network's transaction details through the provider's linked explorer and compare the destination, asset and status. Then check the receiving account's deposit history and credited balance. Network confirmation and account crediting are different stages.
If the balance is missing, compare the recorded route with the current deposit requirements and the provider's status notice. Do not send a second payment merely to make the first appear. For an incorrect Coinbase tag or memo, its guidance says to contact support with the transaction hash; assistance may be possible, not guaranteed. Kraken also directs users with an incorrect tag or memo to support. Provide the relevant hash, network, asset, amount and time through the authenticated support channel, without sending wallet secrets. [1][3][4]
Keep a reusable checklist, not a reusable assumption
Keep a short checklist with separate results for asset compatibility, network compatibility, address, memo, deposit conditions and final credited balance. Mark each as verified, unresolved or not applicable, and record why. 'Not applicable' for a memo should come from the receiving instructions, not from the absence of a field in the sending app. Preserve the original record if you later correct a mistake, adding a dated explanation rather than overwriting what happened.
For the next deposit, reuse the checklist structure and obtain the current values again. Recheck immediately after a provider changes its supported networks, deposit interface or account restrictions. This procedure reduces avoidable routing mistakes; it cannot establish custody quality or guarantee recovery of an unsupported transfer. If a stranger offers to repair a missing deposit, verify the support request independently before sharing information or granting access. Our related articles cover support impersonation and the limits of proof of reserves. [1][3][5]
Frequently asked questions
Does the same asset name mean the network is correct?
No. Confirm the exact supported asset-and-network route at the sending and receiving services. A matching ticker alone is insufficient. [5]
Can a QR code replace checking the memo?
No. Inspect the populated fields and compare any required memo or tag with the receiving screen. [3]
Does a confirmed transaction prove my exchange balance was credited?
No. Check the receiving account's deposit history and balance separately; confirmations and account crediting are different stages. [4]
Evidence & sources
Source record: · Checked:
Record limits · Provider instructions checked on 4 November 2026. Availability and requirements depend on the account, asset and network; recheck the live deposit screen before each transfer.
- Source reported
Kraken requires a supported deposit network and checking the selected currency's deposit warnings.
Supporting excerpt: Kraken: how to deposit cryptocurrencies
Choose your network.
Kraken: how to deposit cryptocurrencies ↗ - Source reported
Coinbase displays receiving details after asset and network selection; account restrictions can require additional steps.
Supporting excerpt: Coinbase: steps to receive crypto
Select the network you want to receive on.
Coinbase: steps to receive crypto ↗ - Source reported
Coinbase says required tags or memos route deposits to the customer and incorrect values can prevent crediting.
Supporting excerpt: Coinbase: destination tags and memos
Always confirm you’ve entered the correct tag/memo when required.
Coinbase: destination tags and memos ↗ - Source reported
Kraken requires blockchain confirmations before crediting and notes that minimum deposit amounts vary.
Supporting excerpt: Kraken: cryptocurrency deposit processing times
Each cryptocurrency has a different minimum amount needed to deposit at Kraken.
Kraken: cryptocurrency deposit processing times ↗ - Source reported
Coinbase instructs users to confirm network compatibility when sending or receiving assets on multiple networks.
Supporting excerpt: Coinbase: assets on multiple networks
To avoid losing funds, always confirm that you and the recipient are using the same network.
Coinbase: assets on multiple networks ↗
Related reading
Fake exchange support: how to verify a request
Verify an exchange support request and protect your account if you shared a code, allowed remote access or sent cryptocurrency.
Read article : Fake exchange support: how to verify a request
What proof of reserves cannot tell you
A reserve snapshot can leave debt, ownership rights and later asset movements outside its scope. Read the engagement before treating a balance as evidence of safety.
Read article : What proof of reserves cannot tell you
AERO migration: why account type changes the outcome
Coinbase’s AERO/VELO migration has different rules for customer balances and Prime Vault. We compare the deadlines, conversion ratios and transfer restrictions.
Read article : AERO migration: why account type changes the outcome