For a Mantle bridge mistake, two checks decide recovery: did the tokens leave your wallet, and who controls the receiving address? Mantle bridge moves or swaps assets still in your wallet toward Mantle after a failed send, once a supported route is available. A confirmed transfer into a contract cannot be reversed from your wallet.
First, Find Out Whether the Tokens Left Your Wallet
The source transaction tells you whether a transfer happened. Find its transaction hash in your wallet and open it in an explorer for the network you sent from. Check the status, the token transfer record and the receiving address; a wallet notification alone does not establish where the tokens went.
An approval and a bridge deposit are separate actions. An approval lets a specified contract spend up to a stated amount of your token, but does not send the token. If you approved an unsupported token and the following deposit failed or was never submitted, the token should still be at your address. Check its balance on the source network before trying anything else.
A successful source transaction needs closer inspection. Look for both an outgoing token transfer and a bridge deposit message, then check your address on Mantle for the destination token. A Mantle Network bridge transaction can finish on the source chain before its destination message is processed, so an empty wallet display alone does not prove a loss. Confirm the destination token’s contract address as well as its name; a wallet may need that address to display a balance it already holds.
The Receiving Address Determines Who Can Recover the Token
If the token left your wallet, recovery depends on the address that holds it now. A token symbol is insufficient evidence: two contracts can display the same name while representing different assets. Compare the token contract in the transaction record with the contract accepted by the route you meant to use.
Say you sent 250 tokens labelled USDT directly to a Mantle bridge contract, but their contract address differs from the USDT contract the route accepts. The source explorer can show a successful transfer of 250 while the destination shows zero credited. That is possible because an ERC-20 transfer changes the token’s ledger without necessarily calling the bridge’s deposit function. Ethereum.org’s ERC-20 reference describes this contract reception problem.
- Your own wallet address: If the tokens reached an address you control on another EVM network, switch your wallet to that network and inspect its token balance. You can then choose a route for the actual token you hold.
- A bridge contract: Check whether a deposit message was created. If the contract merely received a direct token transfer, you cannot withdraw its balance with your wallet key; recovery requires a suitable contract function or action by its operator, if either exists.
- An exchange deposit address: Give the exchange the transaction hash, network and token contract. The exchange controls that address and decides whether it can credit or return an unsupported deposit.
- An unrelated address: Only its controller can send the tokens back. A confirmed transaction has no recall instruction.
The distinction matters if you are used to an exchange correcting a deposit internally. From your own wallet, you authorize on-chain actions directly; the exchange’s ability to adjust its records does not extend to tokens held by an unrelated smart contract. MetaMask’s Help Center likewise says recovery from a contract address is not guaranteed.
Give the Contract Operator a Complete Recovery Record
For tokens sitting at a bridge contract without a deposit message, identify the contract’s operator through the project’s established channels and ask whether that specific contract can release accidental ERC-20 transfers. Provide the source transaction hash, source network, your sending address, receiving contract address, token contract and amount. These details let the operator distinguish your transfer from a deposit that is simply waiting to complete.
The operator may have no recovery function, or its controls may not permit returning that token. There is no standard recovery time or fee: reading an explorer costs nothing, while any on-chain return requires gas and someone authorized to make it. Do not pay a stranger who claims they can reverse the transaction or give anyone your wallet’s recovery phrase.
If a genuine deposit message exists, report that message and its destination status instead of requesting an accidental-transfer return. If the tokens remain at your address, there is nothing for an operator to retrieve. Those are different cases, even when all three initially look like “nothing arrived.”
Once You Control the Assets, Choose a Supported Route
After the tokens are back in your wallet—or if they never left—choose the route using the source network and token contract, then check what asset will arrive on Mantle. A swap to Mantle may involve changing the asset as part of the cross-chain transfer; a bridge of the same asset still needs a valid mapping between networks. If your token has no available route, it must first be exchanged for an asset a route accepts.
Check the quoted amount you will receive and keep the source network’s gas token for any approval and transfer. For example, an Ethereum ERC-20 transfer needs ETH for gas even though the asset being moved is a token. Once the asset arrives on Mantle, you also need Mantle’s native gas token for later transactions.
The practical sequence is short once you know where the balance sits:
- Confirm whether the source transaction failed, approved spending, or transferred tokens.
- Identify the receiving address, token contract and any bridge deposit message.
- Recover through the address controller where possible, then move assets you control through a supported route.