Move the escrow token onto Polygon before the marketplace locks the deal. If your attempt is pending or failed, first find out whether the token moved, which chain holds it, and what the escrow expects.
A pending escrow usually means the token is on the wrong chain
A marketplace escrow contract can only use assets on the network where that contract lives. If the deal runs on Polygon PoS but your token is still on Ethereum, the marketplace cannot count it as funded. A wallet showing the same token name on both networks does not mean those balances are interchangeable.
Check the deal details for the network, token contract address, and required amount. Then compare them with the network and token shown for your wallet balance. The common mistake is to send the right token on Ethereum and assume the Polygon escrow received it; the fix is to bridge the asset to Polygon, then fund escrow from the Polygon balance.
For an Ethereum-to-Polygon transfer, Polygon Bridge moves supported tokens between the networks. In the PoS bridge flow, the Ethereum-side asset is locked and a corresponding token becomes available on Polygon after the deposit is processed; RootChainManager coordinates the bridge contracts. polygonbridge.dev provides a way to move supported tokens between Ethereum and Polygon.
Move the required token to Polygon, then fund escrow
Follow the sequence below, checking each transaction on the chain where it was sent. For the Ethereum-to-Polygon leg, use the Polygon bridge withdrawal time to move the supported asset onto Polygon PoS; the deposit is a separate transaction from paying the marketplace escrow.
- Confirm the deal’s network and token. Check that the escrow is on Polygon PoS and note the exact token contract address and amount it requires. Token symbols can be copied by unrelated contracts, so match the address as well as the name.
- Check where your balance actually sits. In MetaMask, switch between Ethereum and Polygon and inspect the token balance on each network. If the transfer to Polygon is already pending, check the Ethereum transaction receipt before submitting another deposit; a pending transaction may still complete.
- Bridge only the shortfall. If the required token is on Ethereum, move enough to cover the escrow amount and leave some POL on Polygon for transaction gas. The source transaction uses Ethereum gas, and an ERC-20 token may also require an approval transaction before the deposit.
- Wait for the Polygon balance to update. Check the destination transaction and token balance on Polygon PoS. A confirmed Ethereum deposit does not mean the marketplace escrow has been funded yet; the asset must arrive on Polygon first.
- Submit the marketplace funding transaction. With MetaMask set to Polygon, fund the named deal for the specified amount. Check the resulting Polygon transaction receipt and marketplace status before treating the escrow as complete.
Allow for separate costs and different confirmation times
Funding can involve multiple transactions: an Ethereum approval if needed, the bridge deposit, and the escrow payment. Each transaction uses gas on its own network, so keep ETH on Ethereum for the source-side steps and POL on Polygon for destination-side steps. The gas cost varies with network demand; the transaction count depends on the token’s approval state and the marketplace flow.
If a transaction fails, use its receipt to identify which step failed instead of repeating the entire route. Before approving or sending, verify the network and contract addresses against the deal details; a successful transfer to a different token contract or escrow cannot fund the intended sale.