XRP Mobile Help
Common issues

A deposit from another network never arrived

Deposits of Bitcoin, Ether, USDC, Solana and other non-XRP assets travel through a bridge and need network confirmations before they show. Most land within minutes; slow networks take longer; the wrong network or the wrong address cannot be recovered.

How it shows up

  • I sent USDC from Base, Ethereum, Solana or Arbitrum and it is not showing
  • My Bitcoin deposit is taking a long time
  • I deposited to the address in Receive and nothing happened
  • Deposit stuck

Support can resolve this in chat

Follow the steps below; the support agent can walk you through them.

Check it yourself

  1. Paste the transaction hash on the network you sent from into the explorer of the network you sent from (etherscan.io, basescan.org, solscan.io, arbiscan.io or mempool.space).
  2. Compare the network, asset and address you sent to with the ones the app showed you for this deposit.

Have this ready if you contact support

  • Which asset and which network you sent from
  • The transaction hash on the sending network
  • The deposit address the app showed you, and when you copied it
  • A screenshot of the deposit on the sending wallet or exchange

What is going on

XRP arrives natively on the XRP Ledger in seconds. Every other asset arrives through the multichain layer (NEAR Intents), which waits for the sending network to reach enough confirmations before crediting your wallet. On fast networks that is a minute or two. On Bitcoin it can be twenty minutes or more, and on Ethereum during congestion it can take longer than usual.

Check these in order

  1. Has the sending side actually sent it? Exchanges often show a withdrawal as done while it is still in their internal queue. Ask for the transaction hash on the sending network.
  2. Does the hash show as confirmed? Paste it into the explorer of that network (etherscan.io, basescan.org, solscan.io, mempool.space). If it is still pending there, nothing has reached us yet.
  3. Is it the right network? The deposit address in the app is generated for one asset on one network. USDC sent on Ethereum to an address the app gave you for USDC on Base is a different route, and the assets do not cross over automatically.
  4. Is it the right asset? The address for USDC does not accept USDT, even on the same network.
  5. Is the address the one the app showed you for this deposit? Deposit addresses are generated per asset and network and can change between deposits. An address saved months ago may no longer be yours.
  6. Is the amount above the minimum? Very small amounts, below the bridge minimum shown on the Receive screen, are not credited.

Look it up yourself

Paste your XRP address into the search box at explorer.near-intents.org. Every deposit the intents layer has seen for your wallet is listed there with its status. If your transfer is confirmed on the sending network but does not appear there after a while, the layer has not picked it up yet. That is the case to escalate, and you can open a ticket in parallel on Telegram at @near_intents_support_bot.

Some networks upgrade from time to time and deposits pause until the layer supports the new format. That happened with Zcash in mid 2026: transfers sat confirmed for a day and then appeared.

Confirmed, correct, and still missing after 30 minutes

That is when we need to look at it. Contact support from Settings, then Support, with the details listed at the top of this page. The team can trace the deposit through the bridge.

When it went to the wrong network, wrong asset or an old address

Read I sent funds to the wrong network or the wrong address. Some cases are recoverable and most are not, and it depends on exactly what happened.

On this page