Stake deposit not showing?

A Stake deposit not showing in your balance is almost always one of a handful of things, and most of them fix themselves within the hour. Before you contact support, it helps to know what has to happen between pressing Send and seeing the money in your Stake wallet.

1. The address. Stake gives you a deposit address in the cashier for each coin, and for coins that run on several chains, a separate address per network. Your account is identified by that address (and, for some coins, by a tag or memo as well), not by your username.
2. The network. The coin must travel on the network you selected in the Stake cashier. The same token on a different chain is a different asset as far as Stake's wallet is concerned.
3. Confirmations. Once the transfer is broadcast, Stake sees it as pending. It credits the deposit only after the blockchain has added the number of confirmations Stake requires for that coin.
4. The balance. After the last required confirmation, the amount appears in that coin's balance. Stake keeps a separate balance per currency, so a Litecoin deposit shows under LTC, not under your Bitcoin or USDT balance.

If any of the four steps goes wrong, the deposit stalls or goes missing. The sections below take each one in turn. If the problem is that you cannot reach Stake at all, start with the live mirror list or the login troubleshooting guide instead; a deposit cannot be checked from a page that will not load.

Stake sets its own confirmation requirement per coin and network and shows it in the cashier, sometimes on the deposit screen and sometimes in the transaction history once the deposit is pending. The figures are not published as a fixed list, and they change. The table below is a guide to what to expect, not a promise.

Two things push the real wait well beyond these figures. The first is exchange processing: many exchanges batch or review withdrawals, and the clock only starts when they broadcast. The second is a low fee on Bitcoin, which can leave a transaction unconfirmed for hours on a busy day. Values vary, so treat the cashier as the only number that counts. The Bitcoin and Litecoin guides explain block times in more detail.

Work through these in order. Most "missing" deposits turn out to be waiting at step one or two.

1. Find the TXID and paste it into a block explorer. The transaction ID (also called hash) is in your wallet or exchange withdrawal history. Use an explorer for the right chain: a Bitcoin explorer for BTC, Tronscan for TRC-20, Etherscan for ERC-20 and so on. If the explorer finds nothing, the transfer has not been broadcast yet, and the delay is with your wallet or exchange, not Stake.
2. Count the confirmations. The explorer shows how many blocks have been added since your transaction. If the number is below what Stake needs, it is still on its way. A Bitcoin transaction with zero confirmations and a low fee is stuck in the mempool, not lost.
3. Compare the receiving address. Check the "to" address on the explorer against the address in your Stake cashier, character by character at the start and end. An address from an old screenshot, a different coin or a different account will not credit to you. If the addresses differ and you did not make a typing error, scan your device for clipboard malware.
4. Check the network. The explorer you used tells you which chain the transfer is on. It must match the network selected in the Stake cashier. ERC-20, BEP-20 and Polygon all use addresses starting with 0x, so an exchange can send on the wrong one without complaint. If this is the problem, go to the next section.
5. Check the amount against the minimum. Look at the amount that actually arrived on the explorer, after any exchange fee was taken off. If it is below Stake's minimum for that coin, see the section on minimums below.

If all five checks pass and the transaction has more confirmations than Stake requires, give it a short while longer and then contact support. Do not send the same amount again to "push it through"; a second transfer does not speed up the first.

This is the one problem that does not resolve on its own, and the one where speed matters.

Wrong network

If you sent, for example, USDT on BNB Smart Chain to the address Stake gave you for Ethereum, the transfer is complete on-chain but it arrived somewhere Stake was not watching. The same applies to wrapped Bitcoin or Litecoin sent on another chain instead of the native network. Whether Stake can recover it depends on the coin, the chains involved and its own wallet setup. Recovery of wrong-network deposits is not guaranteed, may take time if it is possible at all, and Stake can decline it. Third-party payment processors commonly charge a fee for manual recovery when they attempt it; any fee Stake applies would be set by Stake.

What to do:

• Contact Stake support straight away with the TXID, coin, network used, network intended and amount.
• Do not send more on the same route to test it.
• Expect to be told honestly whether recovery is possible. If it is not, the funds may be lost.

Missing memo or tag

Some coins identify the receiving account by a destination tag or memo as well as an address. XRP uses a destination tag; EOS uses a memo. When Stake shows a tag or memo field for a coin, the deposit address is shared, and the tag is what links the money to your account. Sending without it, or with the wrong one, leaves the funds at Stake's address with no owner attached.

These cases are usually more recoverable than wrong-network ones, because the money did reach Stake, but it is still a manual process handled by support and not guaranteed. Send the TXID and the tag you should have used, which is shown in your cashier.

Prevention is simpler than recovery: confirm the network name on both screens before you send, and fill in every tag or memo field exactly as shown. The USDT guide covers network choice in detail.

If you bought crypto through the buy-crypto option in Stake's wallet, or by card through any exchange, there are two steps: the provider takes your payment and buys the coin, then sends it on-chain to your Stake address. A delay can happen at either step, and the first step is outside Stake's control.

• Provider processing. Stake's buy-crypto option hands you over to third-party payment partners, such as MoonPay where available. The partner, the payment methods and the fees vary by country and are shown when you start the purchase. Card payments can be held for fraud review before the coin is sent.
• Identity checks at the provider. Payment partners run their own verification. A first purchase can stop at a request for ID, a selfie or proof of address, and nothing is sent until it is complete. Check your email for messages from the provider, not from Stake.
• Payment declined or reversed. Some banks block card payments to crypto providers or to gambling-related merchants. If the bank declined, no crypto was bought.
• Sent but not yet confirmed. Once the provider sends, you are back to the normal on-chain checks above. The provider's order page or email usually includes the TXID.

If the provider shows the order as completed with a TXID, and the TXID is confirmed on-chain to your Stake address, take it to Stake support. If the provider shows the order as pending, failed or awaiting verification, contact the provider; Stake cannot see or speed up that part.

The same applies to exchange purchases: buying on an exchange and withdrawing to Stake is two separate events, and the exchange's withdrawal history tells you whether the second one has happened.

Support can only trace a deposit with on-chain evidence. Give them everything at once and you avoid a slow back-and-forth:

• Your Stake username (never your password or 2FA code; support will not ask for them).
• The coin and the network you sent on, and the network you selected in the cashier if different.
• The TXID (transaction hash), copied in full.
• The amount sent and the time, with your timezone.
• The receiving address, and the tag or memo if the coin uses one.
• For card or cashier purchases, the provider's name and order reference.

Use live chat or the support contact inside your Stake account, reached through a genuine address. Phishing copies of Stake and fake "support agents" in messaging apps target exactly this situation. If the main domain is blocked or slow on your network, find a working address on the mirror list or read how to find a working Stake mirror. Mirrors help when a working address is blocked or slow on your network; you still have to follow local law and Stake's terms, and using a VPN breaks those terms and can get an account closed.