> For the complete documentation index, see [llms.txt](https://dexsport-3.gitbook.io/dexsport-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dexsport-3.gitbook.io/dexsport-docs/troubleshooting/wrong-network.md). # I sent a deposit on the wrong network Contact support as early as possible. If you sent funds on a network that does not match the one selected on the platform, or to the wrong address, the transfer will not credit on its own, and the sooner support has your transaction details the sooner the check can start. What to do right now. 1. Do not repeat the transfer. Sending more funds the same way does not fix the first one. 2. Open the wallet or exchange you sent from and copy the transaction hash (TX hash) of that transfer. 3. Write to support in the platform chat and include your nickname, the transaction hash, the token, the network you sent from, the network that was selected on Dexsport, the amount, and the approximate time of the transfer. 4. Wait for the answer. Checking a transfer like this takes time, so keep the chat open and avoid starting a new conversation about the same case. ## Can the funds be recovered It depends on where they landed. If the transfer went to the deposit address shown on the platform but on a network other than the one selected, the funds can be returned. This is the usual case when you deposit from an exchange or from a wallet other than the one connected to your account. Send support the transaction hash together with your nickname, the token, both networks and the amount, then wait for the answer. If the funds left for an address that has nothing to do with the platform, an address typed by hand or copied from the wrong place, they cannot be recovered. That transfer happened outside Dexsport, so support has no access to it. ## How to avoid it next time Before every deposit, compare two things: the network selected in the currency and network selector in the top right corner of the platform, and the network you are sending from in your wallet or exchange. They have to be identical. This matters most for stablecoins. USDT and USDC exist on many chains, and the address can look valid on all of them, so the network is what determines where the money goes. Some networks also require a memo or tag. In XRP it is issued per deposit, so enter exactly the one shown in the deposit window. In TON it is permanent and belongs to your account, and it still has to be sent every time. A transfer sent without it, or with someone else's, ends up in the same situation as a wrong network. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://dexsport-3.gitbook.io/dexsport-docs/troubleshooting/wrong-network.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.