18+ only. Crypto gambling involves risk - never wager more than you can afford to lose. Some links may be affiliate links; rankings stay independent. Gamble responsibly.

How to Deposit Zcash at an Online Casino

Illustration for How to Deposit Zcash at an Online Casino

Short answer: Open the casino cashier, copy the exact Zcash deposit address it shows, and send ZEC from your own wallet to it. Check the address type first (t... or u...), send at least the listed minimum, and expect the credit after the operator's confirmation window - usually a few minutes for transparent sends.

Depositing Zcash to a casino is fast and cheap - most of the real risk is not the chain, it is sending the wrong kind of payment to the wrong kind of address. This walkthrough covers the whole route: reading the cashier page, picking the right address type, memos, confirmation windows, real fee numbers, and what to do when the credit does not arrive.

One thing changed in 2026 that every ZEC depositor should know before sending: the Ironwood upgrade sealed Zcash's old Orchard pool, so the pool your wallet spends from - and the one the operator's address points at - now matter more than they used to [7].

table of contents
  1. Read the cashier page before you touch your wallet
  2. The deposit, step by step
  3. Confirmations: what is actually happening
  4. Fees: what a ZEC deposit actually costs
  5. When the deposit does not credit
  6. The TEX trap: "accepts ZEC" does not mean "accepts every ZEC payment path"
  7. Where to deposit right now

Read the cashier page before you touch your wallet

The deposit page tells you three things you must not guess: the address, the minimum amount, and the address type. Zcash has three visibly different address families [4]:

  • Transparent addresses start with t1 (or t3 for multisig-style) and behave like Bitcoin: amounts, sender and receiver are public on-chain.
  • Shielded addresses start with zs (Sapling) and carry encrypted amounts - and the only place a ZEC memo can live.
  • Unified addresses start with u and bundle several receiver types into one encoding [4]. A unified address can include a transparent receiver.
The three Zcash deposit address families and what each one actually tells you: transparent t1/t3, shielded zs, and the unified u1 container Transparent t1... / t3... amount, sender and receiver are public on-chain - no memo what exchanges read Shielded (Sapling) zs... amount and parties encrypted on-chain; a memo field is possible here Unified u1... bundles several receivers - the sender's wallet picks which one A u1 address is a container, not a promise - it can hold a transparent receiver, so "u1" alone never proves the operator accepts shielded deposits.
The three Zcash address families and what each one actually tells you - and the trap in the middle: a unified address is a container, not a promise.

That last point decides everything: a u... deposit address does not tell you whether the operator actually processes shielded payments. It only tells you the address format. If the cashier page does not say which receiver it uses, the pragmatic assumption for a deposit is: it works - operators watch their own deposit addresses. The subtlety matters on the way out (see our shielded vs transparent guide).

If the cashier offers a ZIP-321 payment URI (a zcash:... link with amount and memo pre-filled), use it - the standard exists exactly so wallets fill these fields automatically [1].

The two deposit clocks: the operator's credit window and the wallet's spendability window run independently You send from your wallet Chain confirms 75 s blocks, fixed Operator credits own policy, minutes Bet balance lobby ledger Clock 1: when can you play? operator's credit policy - unpublished at many sites, longer for shielded sends (their scan must catch up) Clock 2: when can you send it out? your wallet's confirmation policy - ~10 confs for third-party ZEC (ZIP 315) [1] Fees ZIP 317 keeps the standard send tiny [2] no replace-by-fee: never double-send
The two deposit clocks run independently: the operator's credit window decides when you can play, your wallet's confirmation policy decides when you can send it out again.

The deposit, step by step

  1. Open the casino's cashier and select Zcash (ZEC) - not a wrapped or bridged variant. If the operator offers ZEC on a non-Zcash network, that is a different asset with different risks; our review pages flag the difference where we found it.
  2. Copy the deposit address exactly. Wallets and casinos both warn about clipboard-hijacking malware for a reason - after pasting, verify the first and last six characters visually.
  3. Check the address type your wallet will send from and to. Sending to a t... address from a shielded wallet is technically possible via the wallet's transparent path, but a shielded-to-shielded flow (or unified-to-unified) is what actually protects you [4].
  4. Send at least the listed minimum, from your own wallet. Exchange withdrawals work too, but they add KYC, batching and minimum-withdrawal rules of the exchange on top.
  5. Note your transaction ID immediately - it is your receipt if anything goes sideways.
  6. If the deposit flow shows a memo field, use exactly what the cashier displays. Memos exist only for shielded payments; a transparent deposit has no memo, and ZIP-321 explicitly makes a memo parameter on a transparent address invalid [1].

Confirmations: what is actually happening

Two different clocks run after your send, and confusing them causes most deposit panic:

  • The operator's credit window. Casinos credit deposits after their own confirmation policy, and many do not publish it - ask support or test with a small amount first instead of assuming a fixed number. Shielded deposits additionally depend on when the operator's wallet scans the chain. Our review pages list each documented policy.
  • Your own spendability clock. ZIP 315 recommends wallets treat received third-party ZEC as spendable only after 10 confirmations, and self-created notes after 3 - roughly twelve minutes at the 75-second target block spacing [2][9]. That number is wallet guidance, not a consensus rule: wallets implement their own policy and may configure it differently.

Neither clock is the "10-block unlock" folklore from other coins. A credit that shows up in four minutes and a spendable balance two minutes later are both normal.

Fees: what a ZEC deposit actually costs

Zcash fees are set by policy, not by auction. ZIP 317 prices a transaction at 5000 zatoshis (0.00005 ZEC) per logical action, with a grace of 2 actions - so an ordinary payment sits in the sub-cent range at any sane ZEC price [3]. Wallets implementing ZIP 317 charge that by default; some offer slow/standard/fast choices that differ by little.

Two fee facts worth knowing before a deposit:

  • Zcash has no replace-by-fee. A too-low fee does not vanish; it confirms late or drops back to your wallet. Never "retry" a slow send by double-sending.
  • Deposits themselves are usually free at the operator side - casinos that charge a deposit fee at all list it in the cashier. Our comparison table shows the documented ones.

When the deposit does not credit

Work this checklist in order - our payment help tool walks the same logic interactively:

The zcashcasinos payment-help tool - it walks the stuck-deposit checklist branch by branch, entirely in the browser. Checked 2026-10-22.
The zcashcasinos payment-help tool - it walks the stuck-deposit checklist branch by branch, entirely in the browser. Checked 2026-10-22.
  1. Paste the transaction ID into an explorer (for transparent sends). Zero or few confirmations means wait - a low-fee send confirms late, it does not vanish. Zcash has no replace-by-fee; do not double-send.
  2. Compare against the minimum listed on the cashier page on the day you sent. Under-minimum sends are typically held until support maps them.
  3. Re-open the deposit page in the same account session and confirm the address you used is still the one shown. Session-scoped deposit addresses rotate on some sites.
  4. Only then contact support - with transaction ID, amount, date, and the deposit address. For transparent sends the explorer link is your proof. For shielded sends, your wallet's own record (address, amount, transaction ID, memo) is the evidence - keep it.

Over 24 hours uncredited is past every normal window: escalate in writing, and never pay a "release fee" or share your seed to "fix" a stuck deposit. Those are scam patterns, not support - our scam checklist lists them.

The TEX trap: "accepts ZEC" does not mean "accepts every ZEC payment path"

The single most documented Zcash deposit failure is not about casinos at all, but it explains the checklist: in 2024, Binance stopped crediting deposits sent from shielded addresses to its transparent deposit system, and affected users waited weeks [6]. The exchange said the deposits had to come from "readily identifiable" transparent sources.

The 2024 thread where Binance's shielded-deposit rejections were confirmed - and where the TEX address standard was announced as the fix. Checked 2026-10-22.
The 2024 thread where Binance's shielded-deposit rejections were confirmed - and where the TEX address standard was announced as the fix. Checked 2026-10-22.

That demand became formalized as ZIP-320, the "Transparent Exchange Address" (TEX): a transparent address encoding that wallets must treat as a directive to spend no shielded notes into it [5]. The ZIP's own background names the November 2023 Binance delisting threat as the reason it exists.

ZIP-320 itself: the TEX standard was written so that wallets never send shielded notes to exchange deposit addresses - the formalized version of the 2024 problem. Checked 2026-10-22.
ZIP-320 itself: the TEX standard was written so that wallets never send shielded notes to exchange deposit addresses - the formalized version of the 2024 problem. Checked 2026-10-22.

The lesson transfers directly to casinos: an operator that demands transparent sources (or hands out TEX addresses) will document it somewhere - read the deposit page and the terms before funding, and keep your first deposit small enough to lose nothing but time. If the casino credits per-address and you deposit from a batched exchange withdrawal, the mapping can also confuse support - one more reason the no-KYC buying route starts from your own wallet.

Where to deposit right now

Operators with an active, operator-documented ZEC listing in our database - live values, no stale numbers (research candidates sit in the full table until their cashier is verified):

CasinoKYCVPNMin depositPayoutScore
CloudbetRisk-based KYCVPN tolerated0.0003 ZECvaries7.2Visit
RakebitunknownVPN friendlysee reviewvaries4.4Visit
Bspinunknownunknownsee reviewvaries4Visit
DuckDiceRisk-based KYCVPN toleratedsee reviewvaries6.2Visit (read warnings)
1xBitSelective KYCVPN toleratedsee reviewvaries5.4Visit (read warnings)

Live values from our database - details and caveats in each review. "Visit" links may be affiliated.

Ready to move money the other way? The withdrawal walkthrough covers payout addresses, the KYC trigger line, and how to verify what actually arrives.

FAQ

Do I need a memo when depositing ZEC?

Only if the casino's deposit page shows a memo field you are told to include. Memos only exist for shielded payments - a transparent (t...) deposit has no memo at all, and ZIP-321 makes a URI with a memo parameter on a transparent address invalid [1].

Why is my confirmed deposit not credited yet?

Operators credit after their own confirmation policy, and many do not publish it - ask support or test with a small amount first. A few minutes of delay are normal; over an hour past the stated window is a support case.

Can I deposit from an exchange instead of my own wallet?

You can if the exchange supports ZEC withdrawals, but you inherit its KYC and its withdrawal rules - and exchanges force transparent-rail deposits (see the TEX section below). A test deposit from your own shielded wallet first is the safer route.

What happens if I send less than the minimum deposit?

Many operators hold under-minimum deposits uncredited until support maps them manually. Send the listed minimum or more; if it already happened, open a ticket with the transaction ID and the exact amount.

My transaction has zero confirmations for over an hour - is the money gone?

No. Zcash has no replace-by-fee, so a low-fee send either confirms eventually or returns to your wallet. Do not send the same amount again to "retry" - the first send can still land.

Can the casino see my wallet balance after a deposit?

If you deposited to a transparent address, the deposit address history is public on-chain - that address, its amounts and its counterparties, not the rest of your wallet. A shielded deposit reveals none of that [4]. This is why the address type you send to decides the privacy of the whole route.

What address type should I send from?

From a shielded-first wallet you control (see the wallet guide). The receiving address type is the operator's choice; your sending wallet decides what your side of the transaction exposes.

Does the Ironwood upgrade change deposits?

It changed the pools. The old Orchard pool was sealed on 2026-07-28, so fresh deposits flow to the Ironwood or Sapling pools (or transparent) depending on the address the operator shows [7][8]. A wallet that is not Ironwood-ready can fail to see or spend newer shielded funds - check the wallet before you send.

Ready to pick a casino? The comparison table has the live values, the finder narrows them down:

No-KYC picks → Find my casino in 30s

Sources

  1. ZIP 321: Payment Request URIs - memo rule and URI format - accessed 2026-10-22
  2. ZIP 315: Best Practices for Wallet Implementations - 10/3 confirmation policy - accessed 2026-10-22
  3. ZIP 317: Recommended Transaction Fee Policy - 5000 zatoshi per logical action - accessed 2026-10-22
  4. ZIP 316: Unified Addresses - one address encoding bundling several receiver types - accessed 2026-10-22
  5. ZIP 320: Transparent Exchange Address (TEX) - background and requirements - accessed 2026-10-22
  6. Zcash forum: Binance rejecting deposits from Zcash shielded addresses (2024) - the deposit-route problem class, with the Shielded Labs TEX response - accessed 2026-10-22
  7. Zcash Foundation forum: Zebra, Zakura, and the road through NU6.3 (2026-07-16) - Ironwood activation and zcashd end of life - accessed 2026-10-22
  8. ZecHub wallet tracker - which wallets read which pools, Ironwood readiness - accessed 2026-10-22
  9. ZIP 208: Shorter Block Target Spacing - 75-second blocks after Blossom - accessed 2026-10-22

Further reading

Tools for this