Skip to main content

Crypto deposit not crediting

Delayed Cryptocurrency Deposits – Possible Causes and Solutions

Updated over 2 months ago

Delays are rare, but they can happen. Use this guide to check what’s going on and how to fix it.

Likely causes

  • Network congestion
    Heavy traffic on the blockchain slows confirmations. Some networks take minutes; others can take hours.

  • Incorrect address, network, or missing tag/memo
    A wrong address, the wrong network (e.g., sending BSC to an ERC-20 address), or a missing tag/memo/destination ID can block or delay crediting—common with assets like XRP, XLM, ATOM, TON, etc. Contact Live Support immediately if you suspect this.

What to do?

  • Check the Tx on a block explorer
    Copy your transaction hash (TxID) from the sender and confirm:

    • Status is successful on the correct network

    • You used the exact Betski deposit address and any required tag/memo

  • Confirm confirmations
    Some assets need multiple block confirmations before crediting. If your Tx is confirmed and you still don’t see funds after a reasonable time, contact Support.

  • Review sender notifications
    Look for fee, queue, or compliance flags on the sending wallet/exchange.

Crypto

Typical processing time

Explorer

BNB (BSC)

2–5 s

BTC

10–30 min

ADA

15–30 s

DOGE

1–2 min

ETH

10–15 s

LTC

2–3 min

XRP

3–5 s

SOL

0.4–1 s

USDT (TRC20)

3–6 s

TON

2–6 s

TRX

3–6 s

USDC (ERC20)

10–15 s

Important — irreversible transfers

  • Blockchain transfers are final.

  • Sending to the wrong address or network, or omitting a required tag/memo, can lead to permanent loss of funds.

  • Betski can’t recover or refund funds that don’t arrive at the correct address/network with all required details. Always double-check before sending.

Contact us

If the deposit hasn’t arrived after network confirmation, reach Live Support or email [email protected] with:

  • Username and asset

  • TxID and network used

  • Deposit address and any tag/memo you entered

  • Timestamp and screenshots from the sender

We’ll trace it and help you resolve it.

Did this answer your question?