Sent crypto to the wrong network or forgot a memo?
Find which network received your crypto, check the asset and memo, and identify who can investigate. A practical guide for Canadian readers facing a missing deposit.
In this guide · 10 sections
- Check whether the transfer was sent
- Compare the asset, network and receiving instructions
- Who controls the receiving address
- When a deposit needs a memo or destination tag
- Confirmations do not settle deposit eligibility
- Prepare the evidence for the receiving provider
- What to ask before agreeing to a recovery attempt
- Do not bridge or fund an address to repair an earlier transfer
- Before your next transfer
- Frequently asked questions
Find the next check for a network or memo issue
Choose the status you observed to find the relevant next check. This guide does not inspect a transaction, connect to your account or determine whether funds can be recovered.
No personal details are needed. Do not share recovery words, passwords or banking credentials.
Browse all situations and next checks
- I do not yet know what went wrong
- Establish the record before choosing a recovery route
- Find the sending record and the receiving instructions independently.
- Compare the asset, network, destination and memo requirement.
- Do not assume that an identical address format proves the receiving service supports the transfer.
- I have not sent the transfer yet
- Resolve the receiving instructions first
- Check the receiving service’s current asset and network support for your account.
- Read whether a memo or destination tag is required for this deposit.
- If the instructions do not match the sending options, resolve that difference before sending.
- I sent on a different network from the receiving instructions
- Identify who controls the receiving address
- Save the actual network and transaction hash, plus the intended receiving instructions.
- For a provider account, ask its official support about that specific asset and network; recovery support varies.
- Do not import recovery words into a service offered by an unsolicited helper.
- The network matches, but the memo or tag is missing or wrong
- Ask the receiving service about deposit identification
- Check whether the transaction succeeded or was rejected before treating it as an unallocated deposit.
- Save the hash, amount, destination and the memo or tag actually sent.
- Compare that record with the memo instructions shown by the receiving service.
- Ask official receiving support what evidence it requires. A memo issue does not establish that a recovery is available.
- The network rejected or failed the transfer
- Separate a rejected attempt from an uncredited deposit
- Read the actual transaction result on the correct network.
- A missing required tag can be a reason for rejection on some networks; do not assume funds arrived merely because a hash exists.
- Use the explorer guide to distinguish transaction outcome from fees and account credit.
- The recipient address itself is wrong
- Distinguish a wrong recipient from a network mismatch
- Verify the complete destination against the original instructions.
- Identify whether the address belongs to a provider you can contact through an official channel.
- A support request or a new transfer cannot reverse a completed payment by itself.
- I cannot find the transaction on the explorer
- Check the network and transaction reference
- An internal withdrawal reference is not necessarily a blockchain transaction hash.
- Use the sending record to identify the network before choosing an explorer.
- Ask the sender whether the withdrawal was broadcast if the network record remains unclear.
If you sent crypto to the wrong network or forgot a required memo, stop sending further deposits. Find the transaction in your sending account, establish which network actually processed it, and compare the receiving instructions with what you submitted. The next step depends on who controls the destination address. An exchange deposit, a transfer to your own wallet and a payment to somebody else need different investigations.
A missing balance does not tell you which mistake occurred. Your transfer might be awaiting broadcast, visible on a different blockchain, unsupported by the recipient, or missing the reference needed to credit your account. Start with evidence you can read without signing anything. Do not enter recovery words into a website, connect a wallet to a stranger’s recovery service, or send another payment to demonstrate the problem.
For Canadian readers, also separate the crypto transfer from any earlier Canadian dollar funding. A bank payment into an exchange and a later withdrawal from that exchange are different events. If the missing money is still at the bank funding stage, use our guide to an Interac or crypto deposit not received in Canada. A blockchain explorer cannot settle a question about a payment that never became a crypto withdrawal.
This guide uses official documentation checked on October 21, 2026. Provider examples explain specific policies, not recommendations or promises that every asset and network is available to a Canadian account. All scenarios below are hypothetical teaching examples. No recovery, support conversation or transfer described here represents a test performed by this publication.
Check whether the transfer was sent
Check the sending record before diagnosing a wrong network. Locate the withdrawal or payment you authorized and record its status, asset, amount, selected network and transaction identifier. Keep an internal withdrawal reference separate from a blockchain transaction hash. If the provider shows only a request number, ask whether the withdrawal has been broadcast and which public transaction record belongs to it.
Write down the exact status rather than translating it into a conclusion. For your own notes, “the app shows processing” is more useful than “the blockchain is slow.” Likewise, “the sender reports completed, but I have not verified the transaction” leaves a question open that “the recipient lost it” prematurely closes. This distinction helps support investigate the stage that is actually uncertain.
Use the transaction’s own explorer link when available, checking that it names the network recorded by the sender. If you choose an explorer yourself, reach it through the network’s official documentation. A transaction made on one blockchain may not appear in a search on another. Searching Ethereum when the withdrawal used a different network can produce an empty result even though the transfer happened.
Ethereum’s block explorer documentation distinguishes transaction status, the address a transaction interacts with, and token transfers. Those fields answer different questions. For a token payment, inspect the relevant transfer entry and recipient as well as the headline transaction. A contract interaction can appear in the main destination field without that field being the person who ultimately received the token.
Keep the blockchain result and the customer account result on separate lines in your notes. A successful transfer does not, by itself, show that an exchange has credited your balance. Conversely, an absent balance does not prove a blockchain failure. Our guide to block explorers, confirmations and fees explains how to read the transaction record before interpreting the receiving account’s status.
If the record is pending, failed or not found
A pending record belongs in a different investigation from a completed transfer to an unsupported destination. Ask the sending provider about its pending withdrawal process if it still controls the request. For a transaction submitted from your own wallet, follow that wallet’s official pending transaction guidance. Do not assume a cancellation will work simply because a screen still says pending; the transaction’s state may change while you are checking.
If the explorer reports failure, preserve that result and ask how it relates to the provider’s withdrawal record. Do not describe a failed transfer as funds successfully sitting at the receiver. MetaMask’s transaction guide separates pending, failed and successful transactions and explains that a completed successful transaction cannot be reversed through MetaMask. The response therefore depends on the actual result, not just the presence of a hash.
For a transaction that cannot be found, work through the missing information before making another attempt. Check that you copied the complete hash, selected the actual sending network and searched a transaction rather than an internal reference. If uncertainty remains, send the provider the withdrawal reference and ask for confirmation of broadcast. “Not found in this explorer” is an observation, not proof that the original request can safely be repeated.
In a hypothetical case, a reader selects Base at withdrawal but searches an Ethereum explorer because the asset is labelled ETH. The search returns nothing. The useful next step is to verify the Base withdrawal record and its explorer link, not to send ETH again. Whether that original transfer can be credited remains a separate question for the receiving address and the recipient’s supported networks.
- AssetCheck the exact asset or token supported by the receiving service.
- NetworkMatch the sending network with the receiving instructions. The same ticker can exist on different networks.
- DestinationCompare the complete receiving address with the instructions obtained independently.
- Memo or tagCheck whether an additional account identifier is required, and what was actually sent.
Matching an address format is not the same as matching all receiving requirements. For an attempted transfer, also check whether the network accepted or rejected it.
Compare the asset, network and receiving instructions
Compare each receiving requirement separately: the precise asset, the blockchain network, the destination address, and any required memo or tag. Use the instructions from the receiving account, not a general list of coins on an exchange’s homepage. A provider can discuss or offer trading in an asset without accepting every form of that asset on every network.
Make a small comparison record using the evidence already available. Put “requested by receiver” beside “actually sent.” Leave an item marked unknown if you cannot establish it; do not fill the gap from memory. This is especially useful when a withdrawal screen offered several networks with different fees. The cheapest selection may have been valid for the sender while unsuitable for this particular destination.
| Detail | Evidence to compare | What a match still does not prove |
|---|---|---|
| Asset | Receiving instructions and transaction’s asset identifier | That all versions with the same ticker are supported |
| Network | Deposit network and actual withdrawal network | That the provider has credited the transfer |
| Address | Complete intended address and actual recipient | That you control the address on that network |
| Memo or tag | Required value and recorded transaction field | That a syntactically valid value belongs to your account |
| Amount | Amount sent, amount received and any minimum | That a quoted dollar value is the deposited token quantity |
| Account | Receiving product and customer account | That another product under the same brand can credit it |
Do not stop at a ticker such as USDC or USDT. For a token, record the network and the token identifier shown by the transaction, such as its contract address where applicable. Ask the provider whether that exact version is supported. Avoid substituting a token’s contract address for your deposit address: one identifies the token implementation, while the other is the destination the provider assigned to receive your deposit.
If the receive screen has changed since the transfer, preserve both versions when you have them. Label the older screenshot with the time it was captured and the new screenshot with today’s date. Explain the difference to support rather than treating a current menu as proof of what appeared earlier. A saved screenshot may help describe the instructions you followed, but it does not decide recovery eligibility on its own.
Why the same 0x address is not enough
An address beginning with 0x is not a promise that the recipient supports your network. Ethereum’s account documentation distinguishes accounts controlled by private keys from accounts controlled by contract code. The address format alone does not tell you which kind of destination you used, what controls it elsewhere, or what an exchange has configured to recognize as a customer deposit.
For a normal account you control, compatible networks may use the same address. MetaMask’s wrong destination guidance explains this situation for its EVM accounts. That does not establish an exchange’s ability or willingness to recover an unsupported deposit. It also does not justify assuming that a smart wallet, contract address or address on an unrelated network has the same access conditions.
Consider a hypothetical deposit screen that requests an asset on Ethereum, while a withdrawal screen offers the same ticker on both Ethereum and another network. The destination string remains unchanged after the sender chooses the other network. That tells you only that the sender accepted the string. The decisive missing fact is whether the receiving service accepts that asset at that address on the network actually used.
This distinction also changes the wording of a support request. Instead of saying “the addresses match, so you must have my money,” state that the recipient string matches but the network differs from the deposit instructions. Ask whether the service can identify the transfer and assess eligibility. It is a narrower question, supported by evidence, and gives the provider room to explain a technical or policy limitation.
Canadian account support needs its own check
Check availability for your Canadian account and the exact product receiving the deposit. A worldwide help article, an overseas tutorial and a trading app’s asset page are not interchangeable evidence. For a concrete example, Kraken’s Canadian asset delisting notice describes restrictions affecting named assets, including USDT. Seeing that ticker in a general crypto tutorial therefore does not establish Canadian deposit support.
You do not need to solve a provider’s entire regional policy before opening a missing deposit ticket. State that the receiving account is Canadian and ask whether the precise asset and network qualify for credit or return. If the answer points to another product, confirm whether that product is actually where you sent the funds. Do not create a new account or send another asset merely to imitate a recovery tutorial written for someone elsewhere.
If control is unknown, establish it first. Neither situation guarantees recovery, and a new payment does not reverse the original transfer.
Who controls the receiving address
The party able to act depends on the destination’s actual control. Classify it as your own wallet, a receiving service, another person’s wallet, a contract, or unknown. Use your account records and the original receiving instructions to make that classification. An explorer label can provide context, but it does not replace evidence that a specific customer account was entitled to receive this payment.
Think of two separate questions: who can authorize movement from the address, and whose account was supposed to receive credit? With your own ordinary wallet, those answers may point to you. With a shared exchange address, they point to different roles. Proving you initiated the payment may support an account investigation without giving you the keys to the receiving service’s address.
| Destination | Appropriate next step | Boundary |
|---|---|---|
| Your own wallet | Check official guidance for that wallet and the actual network | Seeing a balance does not establish safe access in every wallet type |
| Exchange or hosted service | Ask that receiver to assess the deposit | Its recovery policy and technical capability determine the options |
| Another person’s wallet | Contact the intended recipient through an established channel | Your wallet provider cannot authorize their outgoing transfer |
| Contract address | Ask the relevant project’s official support about that specific contract | There may be no supported recovery function |
| Unknown address | Preserve the transaction and investigate how it was selected | A public address does not reveal a verified owner |
Your own wallet on a different network
For a wallet you control, start with a viewing problem: is the correct account selected, is the actual network supported, and does the app display the asset? Kraken Wallet’s FAQ notes that unsupported or unindexed assets may not appear and directs users to check the selected wallet and network. That is a useful diagnostic distinction, not a recommendation to move your wallet into another app.
Stay within the official instructions for your existing wallet. Looking at a verified transaction record or changing an existing network view is different from granting a website spending access. If the proposed fix suddenly asks you to reveal recovery words, export keys or install an unfamiliar extension, stop that route. You have not established that those actions are necessary, and they introduce a new problem beyond the original missing balance.
A hypothetical reader owns an ordinary wallet and finds the expected token transfer at the correct address on another compatible chain. Their next question is whether the existing wallet supports viewing and using that asset on that chain. They should not start by funding the address for gas. First establish control, compatibility and the intended destination of any later movement; otherwise the extra payment could follow the original funds into another unresolved situation.
A deposit address supplied by an exchange
If an exchange supplied the receiving address, ask that exchange to assess the deposit. Do not try to reproduce its address in a personal wallet. Your exchange login and your personal wallet are different kinds of access. A support agent may investigate a transfer associated with your customer account, but that is not equivalent to giving you control of the provider’s wallet infrastructure.
Kraken’s deposit recovery guidance distinguishes unsupported tokens, incorrect networks, missing tags and deposits sent to operational hot wallets. It also says recovery is not guaranteed and that fees may apply. The practical lesson is to describe the precise error and obtain the applicable terms from the receiver, rather than assuming that any transfer to an address associated with its brand can be credited automatically.
The Canadian Coinbase recovery article similarly limits recovery to eligible assets and networks. It asks for the transaction ID, destination address and network, and describes returning eligible funds to a wallet under the customer’s control. This is a specific provider process. Its existence does not make a generic recovery website legitimate, and it does not prove that your transfer qualifies.
A wrong recipient or a contract
A wrong address is not repaired by selecting a different network view. Compare the full intended recipient with the actual recipient. If you recognize the recipient, contact them using a channel you already trust and explain the mismatch. If you do not recognize the address, preserve how you obtained it, including whether it came from a saved contact, a copied transaction or a message.
Do not turn an explorer’s suggestion into an accusation about a person. A label, a transaction history or a matching amount may be useful context, but none is a verified identity document. When you ask support to investigate, describe the records and their limits. If the payment followed deceptive instructions, use our crypto scam response guide for Canada alongside the deposit investigation.
For a contract destination, ask the relevant project’s official support whether the specific contract can handle the situation. Do not assume every contract has an owner who can simply send the tokens back. Equally, do not label every contract transfer irretrievably lost without examining the actual case. You need an answer about this contract’s capabilities, not a general promise from someone offering recovery services.
When a deposit needs a memo or destination tag
A memo or destination tag can tell a receiving service which customer should receive a payment at a shared address. It is separate from the asset and network checks. Coinbase’s memo guidance explains that the receiving platform determines when this information is required. Use the instructions for this deposit, including the required value, rather than a rule remembered from a different wallet.
The XRP Ledger documentation describes destination tags as information used by systems outside the ledger to identify a beneficiary. That explains an otherwise confusing result: a payment can be recorded on the ledger while the receiving business still needs to establish which customer should get the credit. The tag’s business meaning comes from the receiver’s records, not from the sender’s intention.
Distinguish an omitted tag from an incorrect one. An empty field provides no account reference; an incorrect field provides a reference that may be invalid or associated with a different account. Do not assume support can treat both cases identically. State which occurred and preserve both the expected value and the value recorded in the actual transaction, without publishing those account details on a public forum.
A missing XRP tag can produce different results
An XRP payment without a tag is not always a successful payment awaiting manual credit. The XRP Ledger’s required tag setting rejects a payment lacking a tag when that setting is enabled on the destination. The same documentation explains that the ledger cannot determine whether a provided tag is valid in a business’s customer system. A present but wrong tag therefore raises a different question.
In a hypothetical case, the sender omitted a required tag and the transaction result shows rejection. The support request should ask about the failed withdrawal and the sender’s account balance, not claim that the receiver already holds a completed deposit. In another hypothetical case, the payment succeeded with an incorrect tag. That request should ask the receiving provider to investigate account allocation. The screenshots may look similar at first; the recorded results are not.
Do not send a second payment carrying the correct tag and expect it to amend the first. If support later proposes any verification procedure, first confirm through your established ticket what it is intended to prove and whether an alternative is available. You should not invent your own payment experiment. A new transfer creates a new record and may leave the original dispute unresolved.
Stellar memo types and encoded references
For Stellar, record the memo type as well as the content. Stellar’s transaction documentation distinguishes text, numeric ID and other memo formats. A string that looks right to a person is not enough to establish that the requested field was used. Compare the receiving instructions and transaction details, and ask the provider to interpret the format if the sending app does not make it clear.
Some Stellar payment flows encode a routing identifier in a muxed address rather than presenting a separate memo field. Stellar’s contract account payment guidance explains this distinction. A missing visible memo box is therefore not, on its own, proof that the routing identifier was omitted. Preserve the complete receiving instruction and ask whether the sending and receiving products support the address form used.
For your evidence file, avoid “correcting” a memo by removing characters, replacing it with your name, or converting it to a number in a spreadsheet. Copy the displayed value as text and preserve the original screenshot. Your investigation should establish what happened, not create a tidier version that differs from the transaction. If you are unsure whether a value is a memo, tag or internal reference, label that uncertainty explicitly.
Confirmations do not settle deposit eligibility
Enough confirmations do not turn an unsupported deposit into a supported one. Kraken’s missing deposit checklist treats network, minimum amount, memo, address, confirmation requirements and maintenance as separate checks. More time may resolve a processing delay; it does not change the network or reference you originally submitted. Diagnose the mismatch before treating waiting as the entire solution.
For a hypothetical transfer that matches the receiving instructions, the useful question is whether the provider’s confirmation or processing requirements have been met. For one that used a different network, the useful question is whether the transfer is eligible for recovery. Both readers see an empty account balance, but they need different answers. Keep the evidence organized so the first support response addresses your situation rather than an assumed routine delay.
The amount deserves a separate check too. Record token units as shown by the sender and receiver, and note any fee or minimum stated by the receiving provider. Do not compare only a Canadian dollar portfolio value with a token quantity. A price display can change while the number of tokens remains unchanged. If the provider’s minimum is part of the issue, ask which rule applied to that exact deposit rather than attempting to top it up blindly.
Prepare the evidence for the receiving provider
Prepare a private evidence file that connects the requested destination with the actual transfer. Start a ticket through the provider’s genuine app or website, then attach what its secure process requests. The goal is to make the mismatch easy to inspect. A short explanation with exact identifiers is more useful than a long message that switches between a bank funding reference, a withdrawal number and a blockchain hash without naming them.
Include the transaction hash as copyable text, not only inside a screenshot. Record the network separately because the hash alone may not tell a support agent which system you used. Where available, include the explorer link and a screenshot of the relevant result. The screenshot preserves what you observed at that moment; the link lets the provider inspect the record independently.
- Identify the sending product and receiving product, including that the receiving account is Canadian where relevant.
- Record the asset, network actually used, amount, transaction hash and date with time zone.
- Compare the intended recipient with the recipient recorded in the transfer.
- Preserve the receiving instructions, including network and required memo or tag.
- State whether the memo was absent, incorrect or uncertain, and provide its expected and recorded values privately.
- Include the internal withdrawal reference and existing support case number as separate fields.
- Ask whether the transfer is eligible for account credit, return or further investigation, and what evidence is still missing.
When recording time, keep the time zone visible. A Canadian local time and an explorer’s UTC timestamp can describe the same event without displaying the same hour or calendar date. You do not need to convert every timestamp yourself. Preserve the original values and labels so the provider can reconcile them, especially when the sending record and receiving screenshot were captured around midnight.
Describe the suspected error as a hypothesis until it is verified. Useful wording is: “My withdrawal record lists a different network from the deposit instructions. The attached explorer record shows the recipient and amount. Please confirm whether this deposit can be identified and whether your recovery process applies.” This is suggested wording, not an official form. Add your actual details privately and remove any sentence you cannot substantiate.
For a memo case, the corresponding request is: “The destination address appears to match, but the recorded memo differs from the memo shown for my account. Please review the transaction and advise what evidence you need to establish the intended account.” Do not claim that another customer received it unless the provider confirms that conclusion. A wrong value and a proven miscredit are different facts.
Evidence of sending is not the same as control of an address
If you withdrew from another exchange, explain that fact. A blockchain record may show an address operated by the sending service rather than a personal wallet under your control. You should not promise to sign a message from that address or describe its keys as yours. Ask the receiving provider what account records it accepts and, if needed, request supporting withdrawal information from the sending provider.
Keep the original files and create redacted copies for any place that does not need the full details. A public forum usually does not need your customer number, account balance or complete transfer history. The genuine provider may need more information in its secure ticket. Decide what each recipient needs before attaching a screenshot, and inspect the edges of the image for unrelated account details.
Do not include recovery words, private keys, login codes or passwords in the evidence file. Those secrets do not help an agent distinguish an unsupported network from a missing memo. If someone requests them while claiming to investigate, stop that conversation and return to the provider through a known route. If you already disclosed them, treat the access exposure as a separate urgent problem alongside the missing deposit.
What to ask before agreeing to a recovery attempt
Ask the provider to explain what a successful outcome would actually be. Would the asset be credited to your account, or returned elsewhere? Which asset and network would be used? What fees apply, and how are they collected? Is there an estimated timeframe for this specific case? These questions let you assess the proposal without assuming that “recovery approved” means an immediately available Canadian dollar balance.
Obtain the return instructions before consenting to a return. If the original transfer came from another exchange, ask both providers how a return can reach the appropriate customer account, including any necessary memo. Do not simply request “send it back to where it came from” without checking the arrangement. Your purpose is to avoid creating another unmatched deposit while the first investigation is being resolved.
Read a quoted fee in its stated currency and distinguish it from network costs or a percentage deduction. Do not assume a dollar sign means Canadian dollars. If the estimate is unclear, ask for the expected deduction and the asset you would receive. Keep the provider’s explanation with the case record so a later change can be discussed using the same terms.
A legitimate provider’s conditional fee is different from a stranger demanding money to unlock guaranteed recovery. Navigate to the provider independently and verify that the request appears in your existing case. Never use an unsolicited message as the sole authority for a payment. If an alleged recovery agent demands repeated deposits or promises certainty, follow our Canadian guide to responding after a crypto scam.
If the provider declines, ask for the reason in terms you can preserve: unsupported asset, unsupported network, insufficient evidence, unavailable account credit, or another stated limitation. You may be able to supply missing evidence; you cannot assume every technical limitation has a workaround. Keep the final answer and transaction record. Avoid treating social media claims about another person’s success as proof that your case has the same conditions.
Do not bridge or fund an address to repair an earlier transfer
A bridge does not rewrite a completed transaction. Ethereum’s bridge explanation describes bridges as mechanisms for moving information and assets between blockchain ecosystems. Using one is a separate operation. You must first establish legitimate control of the assets and understand the supported route. A bridge cannot grant you control of a receiving exchange’s address merely because your earlier transfer landed there.
There may be a later decision about moving assets you already control, but that comes after the missing deposit has been understood. Keep it separate in your notes: the original transaction, the confirmed location, and any proposed new movement. If a tutorial jumps directly from “wrong network” to “connect wallet,” it has skipped the question that matters most for your situation: whose wallet can authorize the next action?
Network fees also belong to a specific proposed transaction. MetaMask’s sending guidance explains that transfers require sufficient fee coverage, with payment options depending on the supported network and feature. That does not mean you should automatically send a native coin to any address holding missing tokens. First confirm the wallet, network and intended action through official guidance.
For a hypothetical exchange deposit on an unsupported chain, sending gas to that exchange address does not give the customer access to it. For a hypothetical personal wallet whose control is uncertain, funding it first adds another amount to investigate. Record the proposed action and who requested it before paying anything. If you cannot explain why the payment is needed and who can use it, the evidence gathering stage is not finished.
Before your next transfer
Do not resume deposits until the instructions and the unresolved case are clear. When you are ready for a genuinely new transfer, reopen the receiving screen and compare the full asset, network, address and reference with the withdrawal preview. Review them together at the final confirmation step. A saved address label is a useful reminder, but it should not replace current receiving instructions.
If the provider permits a small initial transfer, choose an amount that satisfies its minimum and account for fees. Then verify actual receipt in the intended account before proceeding. A successful explorer entry alone is not the same check. This precaution belongs to a new, understood transfer; it is not a reason to keep sending tests while a wrong network or memo case remains unexplained.
Give saved destinations descriptive names that include their purpose and network, and review them when your provider changes its instructions. Keep a private record of the successful route if it helps you avoid confusion later. Do not copy a receiving address from an unrelated transaction history merely because the first and last characters look familiar. The next payment deserves a fresh comparison of the complete instructions.
Frequently asked questions
Can crypto sent on the wrong network be recovered?
Sometimes an official wallet or receiving provider process may apply, but recovery cannot be inferred from the ticker or address alone. Establish the actual network, destination control and provider eligibility first. For a Canadian account, ask about the exact asset and product rather than relying on another country’s tutorial. This guide’s comparison steps organize that assessment; they do not calculate a recovery probability.
I used the correct address but the wrong memo. Who should I contact?
Contact the receiving provider through its genuine support process and explain the memo mismatch. Keep the sender’s withdrawal record available because it may be needed to establish the payment’s origin. If the transaction failed rather than succeeded, tell both sides that result clearly. Do not assume the receiving provider is holding a successful deposit until the transaction evidence supports that description.
Can I change the network after the transaction is confirmed?
You cannot change the network of the existing confirmed transfer by editing a setting in your wallet. A network selector changes what you are viewing or prepares a different action. If funds are accessible to their legitimate owner, that owner may later evaluate a new transfer using official instructions. That is a separate decision with its own destination checks, possible costs and risks.
Why is my deposit confirmed but not credited?
The blockchain record and the provider’s account credit answer different questions. Compare the receiving instructions before assuming a routine delay: the asset, network, address, memo, minimum and processing requirements all matter. If they appear to match, send the provider the transaction evidence and ask which requirement or processing stage remains unresolved. If a field differs, state that mismatch at the start of the ticket.
Should I share my transaction hash publicly to get help?
Prefer sharing transaction details privately with the relevant provider first. A transaction hash is not a secret key, but it can connect your question with a public payment history and other information you disclose. If you ask a public question, remove unnecessary account details and ignore unsolicited recovery offers. Never add a password, login code or recovery phrase to make a public explanation seem more convincing.
Does a missing memo mean the funds went to another customer?
That conclusion requires evidence from the receiving provider. An absent memo, an invalid memo and a memo associated with another account are distinct situations. Preserve the value actually recorded rather than guessing the result. The provider must investigate its own account records, and its response may be limited by what it can disclose about other customers. Ask about resolving your deposit, not identifying someone else.
Sources and further reading
- MetaMask: I sent crypto to the wrong place
- Ethereum: Block explorers
- Ethereum: Accounts
- Coinbase: Recover unsupported crypto, Canadian help page
- Coinbase: Destination tags and memos
- Kraken: Cryptocurrency deposit is missing
- Kraken: Crypto assets deposit recovery
- Kraken: Asset delistings in Canada
- XRP Ledger: Source and destination tags
- XRP Ledger: Require destination tags
- Stellar: Operations and transactions
- Stellar: Payments to and from contract accounts
- Ethereum: Blockchain bridges
- MetaMask: How to send tokens
- MetaMask: Transactions and failed transactions
- Kraken Wallet: Frequently asked questions