To receive the asset you need, match both the token and its units to the destination chain. A balance can look different because tokens use different decimal places, or because the destination holds a different token altogether. These are separate problems, and the fix depends on which one caused the delay.
Check what the destination chain accepts
First, check the destination network and the exact token you expected to receive. A token’s name and ticker, such as USDC, do not prove it is the same asset: a chain may have several tokens with that name. The token address on Ethereum, or the mint address on Solana, identifies the specific token.
Decimal places set how a token’s smallest units appear as a human-readable balance. For example, one USDC with six decimals is stored as 1,000,000 smallest units; one ETH with 18 decimals is 1,000,000,000,000,000,000 wei. If acrossbridge is part of your recovery, an acrossbridge bridge can move and swap assets between chains in one flow, so you can target the asset the destination chain uses. Check the intended destination token before starting another transfer.
Decimals do not change a token’s value or identity. A token with six decimals is not worth less than one with 18. A swap changes one asset into another at an exchange rate; a bridge may carry an asset to another chain in a corresponding form. The destination token’s identity and available route decide what arrives.
Read the pending or failed status before retrying
A pending source transaction has not finished sending funds, so a destination balance may not appear yet. Open the source transaction in that chain’s explorer, a public record of transactions, and check whether it is still pending, confirmed, or failed. A confirmed source transaction means the send happened, but the receiving step can still be processing.
If the source transaction failed, check the wallet and transaction record before retrying. Confirm whether the original tokens remain in your wallet or were returned; avoid sending again while the outcome is unclear. If the source shows confirmed but the destination has no balance, verify the destination network and token address or mint first. Also check whether your wallet can display that token; a missing display does not always mean the tokens failed to arrive.
Choose the right correction for the mismatch
Use the example of sending 1.25 units of a token with 18 decimals and expecting a destination token with six. The raw source amount is 1,250,000,000,000,000,000 smallest units. If the destination asset is the same token represented with six decimals, a correct transfer still displays 1.25 tokens; the software handles the unit conversion. Do not manually alter a raw amount unless the transaction details specifically require it.
If you received the wrong token, or need a different destination asset, decimals alone cannot fix it. You need a swap into the token the destination accepts. For example, a route from ETH to USDC converts assets, and the USDC amount depends on the exchange rate and fees at execution. Acrossbridge may suit this task when you need a cross-chain move and a swap in one flow; check the destination asset before authorising a fresh transaction.
My decision rule is simple: confirm the source outcome, identify the destination token, then retry only if the original funds are accounted for and the new route matches both.
Top comments (0)