This guide explains how AV Casino payments work from the first top up to the first cashout. You will learn how to choose a method that also supports withdrawals, how pending and release windows behave, what documents pass KYC on the first try, and how to fix typical banking issues without back and forth.
Minimums are method dependent. Card and wallet rails usually offer the lowest threshold and instant posting. Bank transfers and some crypto routes have higher minimums because of external fees or confirmation costs. Check the cashier note next to each method for current min - max ranges before you pay.
When you plan your very first top up, prefer two way rails that allow both deposit and withdrawal. A two way method keeps your money on the same corridor, avoids bank fallbacks and speeds up the first payout after KYC. Filters in the cashier often mark methods with a Works for cashout badge.
Instant deposits post as soon as the processor confirms the authorization. Pending deposits wait for a third party handoff like 3DS, wallet reauth or bank batch posting. Do not repeat payments while the page shows processing - let the handoff settle first to avoid duplicates.
If a promotion requires a qualifying amount or a specific rail, align your first payment to those terms, then keep the receipt. You can review the exact steps for a qualifying deposit for a bonus and confirm that the same rail will support your eventual cashout.
A descriptor is the text your bank shows for the charge. It may include a processor code or a shortened brand. Keep the descriptor in your notes because support can use it to locate the transaction if your cashier does not update immediately.
| Method | Min - max deposit | Typical speed | Fees note | Works for cashout |
|---|---|---|---|---|
| Cards - wallets | Low - medium | Instant | Issuer dependent | Sometimes via the same rail |
| Bank transfer | Medium | Same day - next day | Possible bank fees | Usually yes after KYC |
| Crypto | Medium | After confirmations | Network fee applies | Yes when address - tag match |
3DS is your bank's extra verification. The page switches to a bank controlled frame to collect a one time code or biometric approval. If you close the tab before the handoff completes, the gateway may hold the attempt and the cashier will not update.
Wallets use access tokens that expire. When the wallet panel asks to reauthenticate, finish the login inside the wallet window and confirm the amount again. Closing the wallet too early cancels the token refresh and leaves the deposit pending.
If the page looks stuck, do one clean reload of the cashier and check the transactions list before a second attempt. Duplicates happen when a user repeats payment while the first handoff is still settling in the background.
A slightly different descriptor is normal if a processor routes the payment via a partner. Mismatch is a concern if the amount is wrong or if two authorizations appear for one attempt. In that case, take screenshots and open a ticket with proof.
If a method is blocked, cancel the flow before you switch so the bonus code does not attach to an unfinished transaction. Then start a fresh deposit with the eligible rail and confirm the offer tile before you pay. For mobile flows and cashouts see mobile deposits and withdrawals with layout tips.
Mini-case: a card kept failing with code do not honor. The user corrected the postal code format to match the bank record, retried once, passed 3DS and the deposit posted with the promotion attached.
Transfers that cross banks or currencies can settle on the next business day. Start early and avoid late Friday payments if you plan to withdraw on the weekend. Banks may charge a fixed fee or a spread, so compare rails for total landed cost.
Attach a statement or payment confirmation that shows your name, account, date, amount and beneficiary reference. Redact non relevant lines. Support needs an official document or a clear online banking screenshot with full edges visible.
Crypto payments need confirmations before crediting. Some chains require a tag or memo field to route the funds. If you send without a mandatory tag, the payment may not auto match. Always copy the exact address and tag from the cashier before you send.
BTC should use native BTC, ETH on mainnet, and USDT should match the chain specified in the cashier like ERC20 or TRC20. Do not send across incompatible networks because cross chain recovery is rarely possible.
Network fees and price movement can cause small differences between sent and credited amounts. The cashier usually shows the net credit after fees. Keep the transaction hash to reconcile variances if needed.
Send a small test first, whitelist the address, check the tag, and verify the chain. Wait for the first credit before you attempt a larger amount. If you are new to the corridor, verify basics before you deposit and confirm you are on the official domain.
| Asset | Common chains | Min confirms | Tag needed | Notes |
|---|---|---|---|---|
| BTC | Bitcoin | 1-3 | No | Fee varies with network load |
| ETH | Ethereum | 6-12 | No | Gas price spikes increase delay |
| USDT | ERC20, TRC20, others | Varies by chain | Sometimes | Match chain exactly to cashier |
Mini-case: a crypto payout stayed pending because the destination tag was missing. The user opened a new request with the correct tag, support matched the original hash and released the funds to the proper address.
The fastest rail is the one that is verified, two way and supported by your bank without manual review. Wallets and some card corridors can release same day after KYC, while bank transfers align to banking hours and crypto waits for chain confirmations.
Pending review is the internal check of play history, balance composition and documents. Clean profiles often pass the same day. Expect longer if SoF is triggered or if you switched rails right before requesting the payout.
Cancel only if you need to correct details or choose a faster rail. Avoid cancel - reapply loops because they reset the queue position. If you must edit, do it once and save the new confirmation.
Releases may queue until business hours. Start withdrawals Tuesday - Thursday to reduce idle time. For large amounts consider splitting into several requests within daily method limits.
Split payouts occur when a method has caps per transaction or when compliance prefers staged releases. Keep the same case ID and track each part to completion before you switch corridors.
A small test payout validates the corridor and your beneficiary details without risking a large hold. Run it after your first WR completion, then scale the amount once the route proves stable. If speed is a priority, explore fast payouts for real money play and align your sessions to methods with same day release potential.
Use the transactions page, avoid multiple tickets for the same request, and escalate only after the normal window passes. Keep your notes updated with request IDs and timestamps.
| Rail | Typical pending | Release window | Notes | Reversal policy |
|---|---|---|---|---|
| Wallet | Same day | Minutes - hours | Issuer policies may cap daily amounts | Allowed while pending |
| Card corridor | Same day | Hours - next day | Often returns via original method | Allowed while pending |
| Bank transfer | Same day | Next business day | Cut off and holidays apply | Allowed while pending |
| Crypto | Same day | After chain confirms | Address - tag must match | Rare after release |
Mini-case: a player split a large payout into three parts because of corridor caps. Each part released within the expected window and reached the beneficiary without additional requests.
Acceptable ID includes a passport or national ID with a clear photo and visible edges. Proof of address includes a recent utility bill or bank statement showing your full name and address. Screenshots are fine if the edges and URL bar are visible and the file is crisp.
SoF validates where your deposits come from. It can include payslips, tax returns, business invoices or bank statements with irrelevant lines redacted. SoF often appears before larger withdrawals or after unusual deposit patterns.
Hide card numbers, unrelated balances and third party names, but keep your name, date, amounts and issuer visible. Over redaction causes rejections because reviewers cannot validate the document.
Basic KYC tends to clear the same day when files are sharp and consistent. If the estimate expires, prepare a concise ticket with proofs and politely escalate with documents if needed using your case ID.
Use one thread per case. Duplicate tickets slow down the queue because agents must merge them. Update the same thread with any new file and keep your summary at the top.
| Document | Must show | Common rejection | Fix |
|---|---|---|---|
| Passport or ID | Full name, photo, expiry, edges | Glare or cropped edges | Reshoot in daylight, include all corners |
| Proof of address | Name, address, issue date | Old date or partial address | Provide a document under 60-90 days |
| Bank statement | Name, account, transactions | Over redaction | Leave totals and issuer visible |
| Payslip | Name, employer, amount | Blurred scan | Upload a higher resolution file |
Start by confirming the processor reference on your receipt. If the cashier shows nothing after a reasonable window, attach the receipt, time, descriptor and masked bank line. A clear single ticket with evidence is faster than multiple short messages. For onboarding, the quick start overview explains how to set up a clean payments profile from day one.
Check if KYC or SoF tasks are open. If none, reply with your request ID, timestamp and the rail used. Ask for a status update and the next review time. Avoid cancel - reapply loops unless support asks to correct details.
Methods can be temporarily disabled for maintenance or issuer limits. If your cashout rail is unavailable, ask support which corridor is open and whether a split payout to bank is faster than waiting.
When a processor fee looks off, attach a side by side comparison of expected vs posted amounts with timestamps. Ask for a reconciliation and confirm whether future payments should use a different rail to reduce costs.
Reversal returns a pending payout to your balance so you can correct details or change corridors. Use it sparingly and only once per request so you do not lose your queue position repeatedly.
Subject: one line summarizing the issue and rail. Body: one paragraph with the problem and steps taken, one with the evidence list, one with the desired outcome. Attach a single zip with receipts and screenshots, label files by date and type.
| Symptom | Likely cause | Quick fix | Next step | Evidence to attach |
|---|---|---|---|---|
| Deposit not credited | Processor lag | Wait, refresh, avoid duplicates | Open ticket after window | Receipt, descriptor, masked bank line |
| Withdrawal pending too long | KYC - SoF hold | Upload missing docs | Ask next review time | Request ID, doc list |
| Method unavailable | Maintenance or cap | Pick alternate rail | Confirm speed - limits | Screenshot of message |
| Duplicate charge suspected | Double click during handoff | Check transactions | Ask reconciliation | Both processor IDs |
| Crypto not received | Wrong chain or missing tag | Verify chain and tag | Provide hash and tag | Tx hash, address, memo |
Mini-case: a payout stalled because the profile address did not match the proof. The player updated the profile to the exact utility bill format, reuploaded a sharper document and the payout moved to release without further questions.
© 2026 AV Casino All rights reserved
