Skip to content
Docs

Deposit from another network is slow or returned

How a deposit from another network runs, from 1Click's quote to the NEAR in your account: what each status and card title means, how long each network takes, what it costs, and what to do when it's slow or returned.

A deposit from another network goes to a single-use address, and NEAR Intents converts it to NEAR on the way in. 1Click, the NEAR Intents service that quotes and runs the conversion, reports a status at each stage. The deposit card shows that status as a title, and the title changes when something needs a look.

Where your money is at each title the card shows

Waiting for your token: still in your wallet. Confirming on the network and Converting to NEAR: with 1Click, at the deposit address. Crediting your account: in your trading account; on some routes it lands first in the account's own NEAR Intents balance and is moved in. Part of your token arrived: the part you sent is with 1Click, the rest is still in your wallet. Returned to your NEAR Intents balance: there. Returned to an address: back in your wallet. Needs attention: the line under the title says which, with 1Click if it wasn't converted or in NEAR Intents. This address expired: nothing was sent, so it is in your wallet. Your wallet other network With 1Click deposit address NEAR Intents balance Trading account your account Moving PENDING_DEPOSIT Waiting for your token KNOWN_DEPOSIT_TX Confirming on the network PROCESSING Converting to NEAR SUCCESS Crediting your account some routes, first Needs you, or returned INCOMPLETE_DEPOSIT Part of your token arrived the rest the part sent REFUNDED Returned to your NEAR Intents balance REFUNDED Returned to an address FAILED Needs attention if not converted if it says so past the deadline This address expired

Where your money is at each title the card shows

Waiting for your token: still in your wallet. Confirming on the network and Converting to NEAR: with 1Click, at the deposit address. Crediting your account: in your trading account; on some routes it lands first in the account's own NEAR Intents balance and is moved in. Part of your token arrived: the part you sent is with 1Click, the rest is still in your wallet. Returned to your NEAR Intents balance: there. Returned to an address: back in your wallet. Needs attention: the line under the title says which, with 1Click if it wasn't converted or in NEAR Intents. This address expired: nothing was sent, so it is in your wallet. Moving PENDING_DEPOSIT Waiting for your token Your wallet KNOWN_DEPOSIT_TX Confirming on the network With 1Click PROCESSING Converting to NEAR With 1Click SUCCESS Crediting your account NEAR Intents: some routes, first Trading account Needs you, or returned INCOMPLETE_DEPOSIT Part of your token arrived Your wallet: the rest With 1Click: the part sent REFUNDED Returned to your NEAR Intents balance NEAR Intents REFUNDED Returned to an address Your wallet FAILED Needs attention With 1Click: if not converted NEAR Intents: if it says so past the deadline This address expired Your wallet
Figure 1.Where your money is at each title the card shows. A dot is where the funds are; a word is where part of them are, or when.

How a deposit runs

Section titled “How a deposit runs”

The quote and the address

Section titled “The quote and the address”

Before your browser shows the deposit address, it checks 1Click’s signed quote. If any check fails, the app shows “Deposit address could not be verified — do not send funds.” instead of an address.

Sending, and the status

Section titled “Sending, and the status”

You send once, from the network you chose.

On NEAR

Section titled “On NEAR”

On NEAR, a bridge relay credits the deposit address inside NEAR Intents, and 1Click’s solver swaps your token to wNEAR and sends it on. Your trading account signs neither transaction and pays no gas for them. Most deposits are delivered straight to the trading account. Some, such as USDT from BNB Chain or Tron, are delivered to the account’s own NEAR Intents balance instead. While trading is unlocked, the app then moves them in, with no pop-up.

What each status shows

Section titled “What each status shows”
1Click status 1Click says Card title What to do
PENDING_DEPOSIT Awaiting your token deposit Waiting for your token Send once, to this address
KNOWN_DEPOSIT_TX Deposit transaction detected Confirming on network Nothing
PROCESSING Swap being executed Converting to NEAR Nothing
SUCCESS Tokens delivered to destination address Crediting your account, then “n NEAR is in your trading account” Nothing
KNOWN_DEPOSIT_TX or PROCESSING, past three times the estimate — Network is slower than usual Nothing. The card updates by itself
INCOMPLETE_DEPOSIT Deposit below required amount Part of your token arrived Send the rest before the time shown, or it is refunded. Deposit the rest shows the address again
REFUNDED Swap failed, funds returned to refund address Returned to your NEAR Intents balance Move it in, as below
REFUNDED, to an address Swap failed, funds returned to refund address Returned to address Nothing. Try again starts a new deposit
FAILED, or SUCCESS with the NEAR not in the account Swap encountered an error Needs attention Read the line under the title
PENDING_DEPOSIT past the deadline — This address expired Don’t send to it. Deposit again gives you a new one

Needs attention

Section titled “Needs attention”

Needs attention has three forms:

  • “In NEAR Intents balance” with Move into your trading account: the conversion worked, but the last move into your account hasn’t run. Press the button.
  • “We can’t see this deposit in your account yet.” Keep the deposit address and the transaction on the other network, and write to Support.
  • “The conversion couldn’t complete” with “Not converted”: keep the deposit address and the transaction hash for Support.

Contact support on the card closes it. It doesn’t send anything to us, so write to Support yourself.

How long each network takes

Section titled “How long each network takes”

1Click’s quote carries a timeEstimate, which its API reference describes as the “Estimated time in seconds for the swap to be executed after the deposit transaction is confirmed”. The card shows it under Waiting for your token, and switches to slower than usual once a seen deposit has taken three times that long (10 minutes when 1Click gives no estimate). Neither the 1Click docs nor the NEAR Intents docs publish how many confirmations each network needs, so the estimate is the figure to go by.

1Click's time estimate per network, in seconds

1Click's timeEstimate on dry quotes of $20 to wNEAR, read 15 October 2026. Solana 20 s, slower than usual after 60 s. Arbitrum 25 s, slower than usual after 75 s. XRP Ledger 25 s, slower than usual after 75 s. Base 35 s, slower than usual after 105 s. Polygon 35 s, slower than usual after 105 s. BNB Chain 35 s, slower than usual after 105 s. Ethereum 45 s, slower than usual after 2 min. Tron 80 s, slower than usual after 4 min. Dogecoin 127 s, slower than usual after 6 min. Zcash 455 s, slower than usual after 23 min. Bitcoin 805 s, slower than usual after 40 min. 0 200 400 600 800 Solana slow after 60 s 20 s Arbitrum slow after 75 s 25 s XRP Ledger slow after 75 s 25 s Base slow after 105 s 35 s Polygon slow after 105 s 35 s BNB Chain slow after 105 s 35 s Ethereum slow after 2 min 45 s Tron slow after 4 min 80 s Dogecoin slow after 6 min 127 s Zcash slow after 23 min 455 s Bitcoin slow after 40 min 805 s

1Click's time estimate per network, in seconds

1Click's timeEstimate on dry quotes of $20 to wNEAR, read 15 October 2026. Solana 20 s, slower than usual after 60 s. Arbitrum 25 s, slower than usual after 75 s. XRP Ledger 25 s, slower than usual after 75 s. Base 35 s, slower than usual after 105 s. Polygon 35 s, slower than usual after 105 s. BNB Chain 35 s, slower than usual after 105 s. Ethereum 45 s, slower than usual after 2 min. Tron 80 s, slower than usual after 4 min. Dogecoin 127 s, slower than usual after 6 min. Zcash 455 s, slower than usual after 23 min. Bitcoin 805 s, slower than usual after 40 min. 0 200 400 600 800 Solana 20 s Arbitrum 25 s XRP Ledger 25 s Base 35 s Polygon 35 s BNB Chain 35 s Ethereum 45 s Tron 80 s Dogecoin 127 s Zcash 455 s Bitcoin 805 s
Figure 2.1Click's own time estimate for a $20 deposit to NEAR, per network, from quotes read on 15 October 2026. Under each name: when the card would read slower than usual. The estimate changes with the network and the amount; your quote has its own.

What it costs

Section titled “What it costs”

UNRLZD adds no fee to deposits. On the measured deposit, 20 bps went to 1Click’s fee account. NEAR Intents’ own protocol fee is 0.0001%, which NEAR Intents calls 1 pip. The rest of the difference between what you send and what arrives is the conversion rate.

Returned to your NEAR Intents balance

Section titled “Returned to your NEAR Intents balance”

Where the funds wait depends on how you signed in.

  • Most deposits return to a NEAR Intents balance that belongs to your trading account. The card says “The conversion couldn’t complete. Move it into your account from Withdraw.” Unlock trading, open Withdraw, and press Move into your trading account. While trading is locked, the card shows Unlock trading first.
  • NEAR sent from BNB Chain, or a deposit made before your account existed, returns to your wallet’s own NEAR Intents balance. You can use it here in UNRLZD or at near.com.

Don’t send twice

Section titled “Don’t send twice”

A deposit address takes one transfer and expires after 24 hours. The app says: “Use this address only once. Any later transfer to it may be lost.” For a second deposit, get a new address.

Your funds

Section titled “Your funds”

A deposit that can’t convert is returned, minus the network fee where one applies, to a NEAR Intents balance you control or to your own address. UNRLZD adds no fee to deposits. NEAR Intents takes its conversion fee and spread.

Sources

  1. 1Click, Making a request: statuses (read 2026-10-15)
  2. 1Click OpenAPI 0.1.10: status enum, timeEstimate (read 2026-10-15)
  3. NEAR Intents, Fees: protocol fee 0.0001% (1 pip), 1Click fees (read 2026-10-15)

Last verified 15 October 2026 against R4.