Skip to the article
Crypto Daybook

Markets, chains and policy news

What to Do When an XMR Bridge Times Out

A bridge timeout often means a status check stalled, not that XMR vanished. Verify the Monero payment and order record before retrying or requesting a refund.

Crypto Daybook Newsroom3 min read

If an XMR bridge times out, first check whether your Monero payment reached the service before sending anything again. A timeout can mean the page stopped checking for an update; it does not by itself show that the transfer failed. A bridge takes XMR on one network and arranges for another asset to reach a destination on a different network. For a fuller look at how an Monero bridge transfer to BTC, ETH or USDT works, see the linked guide. The key is to check the payment and the order separately.

What should I check first after an XMR bridge timeout?

Start with the bridge order page and note its status, order ID, and any stated deposit address and amount. Check whether the order is waiting for a deposit, confirming one, or processing the payout; these stages point to different delays. Keep the page open only if it is still updating, and save a screenshot or copy of the order details in case you need support.

Then check your Monero wallet. Look for the outgoing transfer and its transaction ID (often called a txid), then see whether it is pending or included in a block. Monero targets a block about every two minutes, but actual confirmation time varies. The receiving service may also wait for more confirmations before it acts. A wallet can show an outgoing transfer before the bridge has marked the deposit as confirmed.

How can I tell if my XMR arrived?

Compare the transfer in your wallet with the deposit details saved from the order. Check the amount, address, and network, and confirm that the transaction has been broadcast and confirmed. A pending transfer is still waiting to be recorded in a block; a confirmed transfer has been recorded, though the bridge may require additional confirmations before paying out.

Monero keeps transaction amounts and recipient addresses private on the public blockchain, so a public block explorer generally cannot show an outsider that a particular address received your payment. That makes your wallet’s record and the bridge’s order details important. If your wallet shows a confirmed payment but the bridge still says no deposit, send support the order ID and txid through its official channel. If the wallet shows no transfer, check whether the send failed or remains unsent before taking another step.

Should I resend the payment or ask for a refund?

Do not resend XMR to the same deposit address until you know what happened to the first payment. A second transfer can create a second order or complicate a manual review, and some deposit addresses or quotes may be valid only for a limited period. Ask the service what to do if the order has expired; refund rules and recovery steps depend on the service.

When contacting support, include the order ID, txid, amount, and the status shown in your wallet and on the order page. Never send your seed phrase or private spend key. If support needs extra proof, check its official help page for the accepted method and share only what it requests. A transaction key can reveal details about a Monero payment, so treat it as sensitive.

What if the Monero payment is confirmed but no payout arrives?

If the XMR is confirmed and the order is still waiting, contact support with the saved order details and ask whether the deposit met that order’s amount and confirmation requirements. If the service marks the payout as sent, ask for the destination-chain transaction ID and check that it matches the address and network you selected. A completed XMR deposit and a completed payout are separate steps, so record both transaction IDs when available.

The practical rule is simple: verify the first transfer, keep the order record, and wait for the service to identify the stuck step before retrying. That gives support enough information to trace the payment without risking a duplicate send.