Read the asset and network as a pair
The asset tells you what is being transferred; the network tells you how it reaches the destination. A cashier can support BTC without supporting Lightning. It can support USDT on one network without accepting USDT on every network. Keep those two fields visible when comparing costs or requesting a withdrawal.
| Payment choice | Receiving instruction | Essential distinction |
|---|---|---|
| BTC on Bitcoin mainnet | Supported Bitcoin receiving address | Uses an on-chain Bitcoin transaction |
| BTC through Lightning | Supported Lightning payment request or invoice | Requires a Lightning-compatible sending and receiving service |
| USDT on Ethereum | Correct token and Ethereum deposit instructions | Not a Bitcoin payment or a Tron deposit |
| USDT on Tron | Correct token and Tron deposit instructions | Not interchangeable with Ethereum USDT |
| Wrapped Bitcoin token | Exact token and host-network instructions | A token representation is not native BTC on mainnet |
Bitcoin Cash, commonly labelled BCH, is also not BTC. Never choose a cheaper network merely because the wallet offers it in a dropdown. The destination must explicitly support that asset and route. If an operator’s public page lists only a coin, use the actual cashier instructions to settle the network question before transferring.
Our comparison tool distinguishes documented payment support from a general crypto label. A review cannot safely infer all networks from the coin’s ticker.
Lightning invoices contain payment instructions and an expiry
Lightning Labs’ invoice documentation explains fields including destination, payment hash, amount information and expiry. Some invoices allow the amount to be supplied by the payer. Read the decoded amount and destination in a compatible wallet rather than assuming a QR code always represents the same kind of payment.
If the receiving service’s invoice expires before payment, obtain the appropriate new instruction through that service. Do not paste a Lightning invoice into an ordinary on-chain withdrawal address field. Likewise, a Bitcoin address does not prove the casino can send through Lightning. Both sides must support the intended route.
Routing and available channel capacity can affect whether a Lightning payment succeeds. Its fast settlement design does not compel a casino to approve an account withdrawal immediately. A custodial Lightning wallet can also have its own account rules and service fees. “Lightning” describes a payment technology, not a waiver of verification.
Calculate an on-chain fee without confusing value and data size
Bitcoin.org explains that network fees relate to transaction data size rather than simply the monetary amount transferred. Wallets commonly express an estimated fee rate in satoshis per virtual byte, or sat/vB. The actual transaction structure and current conditions affect the required fee; the following arithmetic is purely illustrative.
Suppose a transaction is 140 virtual bytes and the chosen example rate is 10 sat/vB. The calculation is 140 × 10 = 1,400 satoshis. With 100,000,000 satoshis in one BTC, that equals 0.000014 BTC. This is not a current network quote, a casino fee or a promise of confirmation time.
| Hypothetical input or result | Value | Interpretation |
|---|---|---|
| Transaction size | 140 vB | Assumed data size for this example |
| Fee rate | 10 sat/vB | Teaching assumption, not a live rate |
| Calculated network fee | 1,400 satoshis | 140 multiplied by 10 |
| Fee in BTC | 0.000014 BTC | 1,400 divided by 100,000,000 |
| Value at hypothetical C$100,000/BTC | C$1.40 | Illustrative conversion only |
An operator can charge a fixed withdrawal fee that differs from the actual network cost. It might batch payments, absorb fees or set an account-level charge. Compare the amount deducted and the amount delivered, and label the operator charge separately from a network estimate. Lightning routing fees can also exist; do not translate “fast” into “free”.
Three clocks determine the time you actually wait
Account review, authorisation and any withdrawal queue.
On-chain broadcast and confirmations, or the supported Lightning payment.
The wallet or exchange applies its own receipt and crediting conditions.
A site advertising fast crypto transfers may be describing only the middle stage. Record request, approval, sending and receipt times separately if you want a useful measurement. An on-chain transaction identifier helps investigate transmission; it does not show how long the casino held the request before broadcasting.
Bitcoin confirmation times vary, and receiving services can require different numbers of confirmations. A fixed “ten-minute withdrawal” promise cannot be derived from Bitcoin’s block timing. For Lightning, a completed payment can settle quickly while the preceding account review still takes much longer. See the withdrawal process guide for organising the full timeline.
Check the destination at the last decision point
Use the deposit or withdrawal instruction shown in the official account at the time of payment. A copied address from an old chat, a screenshot or a search advertisement may be wrong or no longer suitable. Verify the destination after pasting because the value in the clipboard is not necessarily the value you intended to copy.
- Confirm the exact asset and network on both services.
- Read the minimum deposit and whether fees reduce the received amount below it.
- Check any required memo, tag or payment reference for that particular route.
- Confirm the receiving address or decoded invoice details before approving.
- Save the payment reference and destination instructions privately.
Bitcoin’s introductory guidance explains the irreversibility of Bitcoin payments. A receiving service may sometimes assist with a mistaken transfer, but recovery is not guaranteed. Ask official support about an unsupported payment; do not send more money to an unsolicited “recovery expert”.
A different network does not erase the account record
Network choice affects compatibility, cost and the form of transaction evidence. It does not decide whether the operator accepts a province, whether documents can be requested or how Canadian tax rules apply. Keep those questions in the decision even when the payment screen is technically straightforward.
Save the asset quantity, time, network and reference, together with a reproducible CAD valuation where relevant. Lightning payment records and on-chain transaction records look different, so retain the receipt supplied by the actual service. The privacy guide explains what a public blockchain does and does not reveal; the tax guide covers the separate accounting record.
Questions about BTC, Lightning and stablecoin networks: match the payment before sending
Does a Bitcoin casino automatically accept Lightning?
No. BTC support can mean only mainnet deposits and withdrawals. Look for explicit Lightning instructions in the relevant cashier flow and confirm the sending wallet supports them. A Bitcoin logo, a fast-payment slogan or a general list of cryptocurrencies does not establish Lightning compatibility.
Can I send USDT on the cheapest network my wallet offers?
Only if the receiving service supports that exact network and token. Ethereum and Tron versions of USDT use different transfer routes even though the displayed currency name is similar. Match both services before authorising payment; a cheaper unsupported route can leave funds uncredited and recovery uncertain.
Is a casino withdrawal fee the same as a Bitcoin network fee?
Not necessarily. The casino may set a fixed charge, absorb the network cost or use a batched transaction. Compare the account deduction with the delivered amount and read its fee policy. A wallet’s network estimate is a different figure and can change with transaction size and network conditions.
Does Lightning guarantee an instant casino payout?
No. Lightning can provide rapid payment settlement when the route works, but the casino may first perform account checks and approval. Wallet service conditions can add another stage. Measure request-to-receipt time separately from the actual network payment instead of using one technology label as a total-time guarantee.
What should I retain if a crypto payment is missing?
Keep the asset, network, amount, destination instruction, submission time and transaction or payment reference. Establish whether the sender actually released it and whether the receiving service supports the route. Share relevant records through official support, while keeping recovery phrases and private keys entirely out of the conversation.