Step one of the route
From a wallet to a casino balance: what a deposit passes through
A deposit modal shows an address and a QR code and implies that the hard part is copying correctly. The hard part is upstream of it, in the two or three places where the coin has to come from somewhere before it can go anywhere.
| Casino | Coins listed | Ceiling on the way out | Amount that triggers documents | Licence | Visit |
|---|---|---|---|---|---|
| Vavepays for this link | not published | not published | not published | not published | Go to site |
| Bitcasino.io | not published | 1,000,000 USDT a week clause 6.10 | 2,500 EUR | Curaçao Gaming Authority | |
| Empire.io | not published | not published | 2,000 USDT | Anjouan Gaming Board licence bars NL | |
| Bitsler | not published | not published | not published | Curaçao Gaming Authority | |
| Cloudbet | 40 | not published | not published | Curaçao Gaming Authority | |
| CoinCasino | not published | 500,000 EUR a month clause 9.6 | not published | Anjouan Gaming Board licence bars NL | |
| Rakebit | 15 | not published | not published | Anjouan Gaming Board licence bars NL | |
| Primedice | not published | not published | not published | Government of Curaçao | |
| Stake | not published | not published | not published | Curaçao Gaming Authority | |
| BetPlays | not published | 5,000 EUR a week clause 6.11 | not published | not published |
The modal is the last step, not the first
The deposit screen at a crypto casino is one of the simplest interfaces in online payments. It shows an address, a QR code, sometimes a network selector, and a note about a minimum. There is nothing to fill in and nothing to sign. It looks like the whole process.
It is the fourth step of five. Ahead of it sit the questions of where the coin comes from, which coin it is, and which network it will travel on. Behind it sit confirmations and crediting, neither of which the player controls. Laid out in order, a deposit looks like this: acquire the coin, choose the network, send to the address, wait for confirmations, see the balance credited. Only the middle one happens on the casino's site.
That imbalance is why deposit problems almost never look like deposit problems. They look like a balance that has not appeared, and the natural response is to contact the casino — which is frequently the one party in the chain that cannot see what went wrong, because the part that went wrong happened before the money reached it.
Where the coin comes from changes what the send looks like
There are two common starting points and they behave differently at exactly the moment it matters.
From an exchange account. The coin was bought with ordinary money, sits in a hosted account, and leaves it through a withdrawal form. The exchange picks its own fee, often applies its own minimum, and — critically — decides for itself which networks it will send on. An exchange that does not support a given chain simply will not offer it in the dropdown, which is safer than offering it wrongly, but it also means the network available at the sending end may not be the network offered at the receiving end. That mismatch is discovered in the dropdown, before anything moves, and costs nothing if noticed there.
From a self-custody wallet. The coin sits under a key held by the person sending it. There is no withdrawal form and no support desk, and there is also no second party to catch an obviously bad instruction. A self-custody wallet will broadcast whatever it is told to broadcast, on any chain it supports, to any address that passes a format check.
Neither is better as a general matter. The relevant difference for a deposit is that the exchange route has one extra pair of eyes and one extra set of restrictions in it, and the self-custody route has neither. A person who has used one of them for a year usually has habits that do not transfer to the other.
Confirmations are the network's business, not the casino's
After the send, the transfer sits in the network's queue until enough blocks have been built on top of it for the receiving side to treat it as settled. How many blocks counts as enough is a policy set by the receiver, and different receivers pick different numbers for the same chain.
Two properties of this stage are worth knowing, and both belong to blockchains rather than to any operator. First, chains differ enormously in how quickly blocks appear: some settle a transfer in the time it takes to read this paragraph, others take an order of magnitude longer, and the slowest common ones are slower still. Second, when a network is busy, a transfer that paid a low fee waits behind transfers that paid more. That is not a fault and not a queue anyone can jump on a player's behalf.
What this means practically is that a deposit which has not appeared is, most of the time, a deposit that is still confirming, and the place to look is a block explorer for the chain in question rather than a support chat. The transaction either exists on the network or it does not, and that question has a public answer that neither party has to be trusted for.
Crediting is where the operator's rules start
Once the required confirmations exist, the operator credits the balance, and from that point onward every rule that applies is the operator's own. This is the boundary that matters for everything else on this site: before crediting, the facts are properties of a network; after crediting, they are clauses in a document.
Among the ten operators read here, that document is readable for nine and not readable for one. Bitcasino.io, Empire.io, Bitsler, Cloudbet, CoinCasino, Rakebit, Primedice, Stake and BetPlays all publish terms in which the relevant clauses could be located and cited. Vave, which pays for the single commercial link on this site, publishes no terms page that could be read, so every figure in its row is recorded as not published.
The asymmetry deserves stating plainly rather than being buried: the operator with the paid link is the operator about whose rules the least is known here. That is what the sources support, and it is the reverse of the direction a paid link normally pushes a comparison.
A minimum is not the same as a sensible amount
Most deposit screens name a minimum, and it is usually small. It is a technical floor — below it the transfer costs more to move than it is worth — and it should not be read as a suggestion.
Because the costs attached to moving a coin are largely fixed per transfer rather than proportional to the amount, a small deposit loses a much larger share of itself in transit than a large one does. The same total, sent in ten pieces, pays roughly ten fixed costs instead of one. Nothing in any operator's terms says this, and no deposit screen mentions it, because the fixed cost is largely charged by the network rather than by the house. The fees page works through where each deduction goes.
The counter-argument is real and belongs here rather than in a footnote. Money that sits in a casino balance is money that can be played, and depositing in larger, less frequent amounts puts more of it within reach. Anyone for whom that is a live concern should treat the more expensive pattern as the correct one. That is a decision about play, not about payments, and the two should not be traded off silently against each other.
What cannot be established from outside
Whether a given operator credits fast or slow, whether its deposit screen displays a fee before confirmation, and whether it silently rejects a network it does not support are all things that can only be seen from inside a funded account. This site does not hold funded accounts and does not report on any of them.
What can be established is what the operators publish, and what they publish about deposits is thin. Coin lists could be read for two of the ten — Cloudbet names forty, Rakebit names fifteen — and the other eight publish no count that could be found. Deposit fees could be read for none of them. The coin lists page sets out exactly which of the ten publish what.