What information a support team actually needs to trace a missing swap deposit

05 September 2026

A support team needs three things to trace a missing swap deposit: the transaction ID (TXID), the sending address, and the exact amount sent. Without these, most teams cannot even begin to investigate, because swap systems match deposits against automated records, and manual tracing starts from the blockchain data that only those three details can locate.

The TXID is the single most important piece. It functions as a permanent receipt on the blockchain. Every transaction, once confirmed, generates a unique hash. A support agent can take that hash, paste it into a block explorer, and see exactly where the funds went. If the swap site's system failed to credit your account, the TXID shows whether the funds reached the address you were given, or whether they ended up somewhere else entirely. Without the TXID, the agent must guess which transaction among thousands might be yours. Most will not guess at all.

The sending address matters because it proves ownership. Anyone could claim a random TXID. But if you provide the address that sent the funds, and can prove you control it - by signing a message or by accessing it from the same IP session - the support team can confirm you are the rightful claimant. This step is not optional. Swap sites handle disputed deposits daily, and they reject requests from people who cannot demonstrate control of the source wallet.

The exact amount sent, including decimals and the specific token, eliminates ambiguity. A deposit of 0.5 ETH is not the same as 0.5 WETH. A deposit of 100 USDC on one network is not the same as 100 USDC on another. Support systems often have automated matching logic that looks for a precise numeric match. If your amount is off by a fraction of a cent, or you sent the wrong token variant, the match fails and your deposit sits in a manual review queue. Giving the exact figure lets the agent bypass that queue.

Three other details help but are not essential: the destination address you were given, the timestamp of the transaction, and the network you used. The destination address is usually already in the system's logs, so providing it mainly confirms that you followed the correct swap path. The timestamp narrows the search window. The network matters because a TXID is only unique within a single blockchain; the same hash can exist on Ethereum and on a testnet, and an agent needs to know which chain to check.

Do not send screenshots as your only evidence. Screenshots can be faked. A support agent cannot enter a screenshot into a database query. The text values - TXID, address, amount - are what get typed into the search fields. Screenshots are useful as supplementary proof, but they are never sufficient alone. The page "What details to screenshot before confirming a crypto swap" covers what to capture; this page covers what to actually send.

If you have all three pieces and the agent still cannot locate your deposit, the problem is likely not a missing transaction but a mismatch between what you sent and what the system expected. Check whether you used the correct network. Check whether the swap contract required a memo or destination tag; some networks, like those using XRP Ledger or Stellar, will not credit a deposit without that tag. Check whether the token you sent has a transfer fee that reduced the amount below the minimum. Those checks belong to the broader topic of swapping crypto safely, which explains how to verify every condition before you send.

Prepare your three pieces before you contact support. Write them down. Send them in a single message. Do not add a story about how urgent the situation is. Do not demand escalation. Present the TXID, the sending address, and the exact amount. That is the fastest way to get a human to look at the right transaction and tell you what actually happened.

Back to solana