Deposits not showing up properly is one of those issues that feels random—until the pattern becomes obvious. A growing number of users are running into this when sending funds over networks like Ethereum, BNB Smart Chain, and Polygon.
The short version: the way some transactions are sent means the system can’t see the amount properly. The good news is it’s avoidable once understood.
What Is an Internal Transaction?
An internal transaction isn’t something sent directly from one wallet to another in the traditional sense. Instead, it’s triggered by a smart contract.
Think of it like this:
A normal transaction = sending money directly from A to B
An internal transaction = asking a program (contract) to handle the transfer on your behalf
Exchanges and platforms use these because they’re efficient. They batch transactions, reduce fees, and streamline withdrawals across thousands of users. From their side, it’s faster and cheaper.
From a user’s side, though, it changes how the transaction appears on-chain.
(example of an internal transaction – Value: 0 ETH)
Why the Deposit Never Shows
When sending the native token (like ETH, BNB, or POL), CryptoGames’ system looks for a straightforward transfer amount.
With internal transactions:
The “main” transaction often shows a value of 0
The actual movement of funds happens inside the contract logic
That detail isn’t always picked up by automated crediting systems
So while the funds have been sent, the system effectively sees:
“Transaction received, but amount = 0”
At that point, it won’t credit automatically.
What Happens Next?
When this happens, the deposit isn’t lost—but it does need manual handling.
That means:
The transaction has to be reviewed manually
The correct amount has to be verified
Funds are then credited by hand
Depending on workload, this can take up to 24 hours.
Not ideal if the intention was to jump straight into a game.
The Simple Fix: Use Your Own Wallet First
The easiest way to avoid this entirely is to route funds through a wallet you control.
For example, wallets like MetaMask* or Trust Wallet* give full control over transactions.
The flow becomes:
Withdraw from the exchange to a personal wallet
Send from that wallet to the casino
Why this works:
The transfer is now a standard transaction
The full amount is clearly visible on-chain
The system can credit it instantly without intervention
It also comes with an important bonus: full ownership of the funds during the process.
*Always do your own research into what wallet is best for you. These are just examples of wallets on the market.
A Quick Note on Exchange Policies
There’s another angle that often gets overlooked.
Many exchanges explicitly state in their terms that they don’t support or condone gambling-related transactions. Sending funds directly from an exchange to a casino can:
Lead to blocked withdrawals
Trigger compliance checks
Delay access to funds
Even when it works, it’s not a risk worth taking.
The Bottom Line
If a deposit fails to show in your account, it’s almost always down to how the transaction was sent—not whether it arrived.
To keep things smooth:
Avoid sending directly from exchanges
Use a personal wallet as a middle step
Make sure the transaction is a standard transfer, not contract-driven
It’s a small extra step that saves a lot of waiting around—and gets funds where they need to be, first time.
