Depositing crypto to BC.Game: networks, memo & recovery
BC.Game supports an unusually long list of coins and networks, and most deposits land in minutes. The two mistakes that actually cost people here are less obvious than a plain wrong-network slip: sending from a smart contract, and forgetting a memo on XRP, XLM or EOS. Both are explained in BC.Game's own help centre, but rarely spelled out by review sites, so we lead with them.
- Memo / tag needed?XRP, XLM & EOS always need a tag
- Smart-contract depositsNot accepted — up to ~12h delay
- Minimum depositVaries by coin (not published)
- Confirmations~1 min to 2 hours by chain
- Wrong-network recoveryMissing memo → 24/7 chat; wrong-network out → no
From BC.Game's own help centre, verified 2026-06-23. Deposit terms change — confirm the network and any memo on the live deposit screen before sending.
The smart-contract trap: "sent, confirmed, but not credited"
This is the one that catches people out. BC.Game's deposit wallets do not accept deposits made directly from a smart contract. If you send from a contract address rather than an ordinary wallet, the transfer can sit unprocessed for up to roughly 12 hours before it shows. The block explorer will say the transaction confirmed, your sending app will say it's done, and the balance still won't appear — which is exactly when people panic and assume the funds are lost.
The usual culprit is the type of wallet you send from. A standard self-custody wallet such as MetaMask, Trust Wallet or Atomic sends a normal transfer that credits like any other. An exchange's internal "send" feature, a multisig, or a DeFi contract is where the contract-deposit delay bites. If you're moving funds off a centralised exchange, withdraw to your own wallet first, then deposit from there.
A worked example
Say you want to deposit USDT. BC.Game lists USDT on ERC-20, TRC-20, BEP-20 and Solana, so the first job is to read which network the deposit screen is showing and match it in your sending wallet. ERC-20 tokens sit under "Ethereum" and BEP-20 tokens under "Binance Smart Chain", which trips up players who look for the token name and not the chain. Pick TRC-20 for low fees, copy that exact address, and send from Trust Wallet. It confirms in a minute or two and credits. Now run the same deposit out of a contract-based wallet on the same network: the transaction confirms on-chain just the same, but it can take hours to appear in your BC.Game balance. Same coin, same network, different wallet type — and a very different wait.
Memo coins: XRP, XLM and EOS always need a tag
BC.Game uses a shared deposit wallet for XRP, XLM and EOS, which means the destination tag, memo or destination ID is what tells the platform the deposit belongs to you. For these three coins it is never optional. Leave it off and the deposit won't credit automatically; it lands in the shared wallet with nothing to route it to your account.
The fix is to copy both fields from the deposit screen — the address and the memo/tag — and paste both into your sending wallet. Some wallets hide the memo field behind an "advanced" or "optional" toggle, so check for it before you confirm. A test send is cheap insurance here: send a small amount, confirm it credits, then move the rest.
Minimums, confirmations and timing
Minimum deposits differ per coin and BC.Game doesn't publish them as fixed figures, so the deposit screen for your chosen coin is the only reliable source — we won't invent numbers we can't verify. There's no stated maximum. Confirmation time depends on the chain: roughly one minute on fast networks, up to about two hours on slower ones. BC.Game publishes a per-coin confirmations table; we're verifying the exact counts first-hand before listing them, rather than copying figures we haven't checked.
If a deposit is taking longer than you expect, the first thing to rule out is the smart-contract delay above, then the memo, then plain confirmation time. How confirmations work covers why some chains feel slow even when nothing is wrong.
Deposit safely
- Pick the coin first, then read its network on the deposit screen — don't assume USDT means TRC-20, and check whether it's listed under "Ethereum" or "Binance Smart Chain".
- Send from a standard wallet (MetaMask, Trust, Atomic), not an exchange's internal send or a contract address.
- Match the network exactly in your sending wallet.
- Add the memo/tag for XRP, XLM and EOS — every time.
- For a larger transfer, send a small test amount first.
If it doesn't credit
The recovery picture splits cleanly into two cases. A deposit that's missing its memo is recoverable: contact BC.Game's 24/7 live chat with your transaction hash and the platform can credit it manually. Confirm the deposit network and the memo/tag you used first, and wait out confirmation timing, so you can describe exactly what happened.
The other case is harder. If you sent funds out on the wrong network or to the wrong address, BC.Game can't pull them back — those coins are on a chain or an address the platform doesn't control. Your only route is to chase the receiving service with the transaction ID and hope they can locate them. And whatever happens, no legitimate recovery ever asks for an up-front fee; treat anyone who does as a scam.
Not sure which case you're in? Run your deposit through our checker to narrow it down before you contact anyone.
Want fewer networks to get wrong? See the Duel deposit walkthrough.
Compare: all crypto casino deposit guides.