Paying a merchant from the wrong chain
When checkout names the wrong network, match the merchant’s chain first, then bridge or swap only after checking the asset, fees and final recipient.
The Blockheight Editors··3 min read
If a merchant accepts payment on a different blockchain from the one holding your funds, move funds to the accepted chain before paying, or use a checkout that explicitly handles the transfer. Sending a token on the wrong network can leave the merchant unable to credit the payment.
How do I tell which chain the merchant requires?
Read the network and token in the checkout instructions before opening your wallet. A payment request may name a chain such as Ethereum or Mantle and an asset such as USDC; the same ticker can refer to different token contracts on different chains.
Check that your wallet is connected to the named chain and that the recipient address and amount match the checkout. A chain label is part of the payment instructions, not a cosmetic wallet setting. For more detail on bridge mechanics in an app integration, see mantle bridge.
What can I do if my funds are on another chain?
There are three common routes, and the right one depends on what the checkout supports:
- Switch networks if you already hold the required asset on the merchant’s chain.
- Bridge funds if the checkout accepts the destination-chain asset and you can use a bridge that supports both chains.
- Swap into the accepted asset if your funds are on the right chain but in a different token.
- Use a checkout’s cross-chain option only if it clearly states that it accepts your source chain and asset.
A bridge moves value between chains; it does not automatically complete the merchant’s payment. Usually, the bridged funds arrive in a wallet on the destination chain, and you then make a separate payment to the merchant. Some checkouts handle more of this flow, but their instructions should say so.
What should I check before sending?
Confirm the source and destination chains, token, amount, fees and final recipient. A bridge may charge a fee on the source chain, and the destination asset may be a bridged representation rather than the token the merchant accepts. Leave enough of the source chain’s native token to pay transaction fees.
After bridging, wait for the destination funds to appear and confirm the checkout still recognizes the payment details before sending. If the merchant’s chain or token is unclear, ask the merchant before transferring; a completed transaction on the wrong chain may be difficult to recover.
What is the simplest way to avoid a failed payment?
For most readers, the simplest route is to hold the accepted asset on the accepted chain before checkout. Bridging adds a separate transaction and fee, while a direct payment keeps the chain, token and recipient easier to verify.
The next step is to follow the merchant’s stated network and payment window. Whether a particular checkout can recover a payment sent on the wrong chain remains merchant-specific.