On this page you'll find the fastest paths to AV Casino Support, clean step-by-step solutions for typical problems, and ready-made text blocks for tickets and escalations. The goal is simple: to resolve a topic with as few messages as possible—ideally a single clearly worded message with a complete supporting package—instead of getting stuck in long email threads.
The Live Chat is ideal for urgent cashier issues and simple account questions. Email is better for withdrawals, KYC, and anything that requires attachments. A callback is sensible if your bank needs a verbal confirmation and you want to have a note in the support profile at the same time.
Use exactly one thread per problem and a clear subject line, for example: Withdrawal pending - Wallet route - Request ID 53421. Attach a single ZIP file that contains all receipts and screenshots. The body text works well with three short paragraphs: what happened, what you have already tried, what outcome you want from support.
SLA stands for the target response time. In Live Chat responses usually come within minutes. Emails are answered in typical queues within a few hours. Banking and Compliance teams operate on bank business days, so plan around weekends and holidays.
Use PNG for screenshots and PDF for account statements or invoices. Leave all margins visible, mark relevant lines, and name files clearly, for example 2025 11 13_receipt_processorID.pdf. This helps agents find the right spot without having to search for long.
The Case ID is the unique number of your ticket. Include it in the subject line with every reply and do not open a new thread for the same topic. A clean process with a complete history can be checked faster than multiple scattered inquiries.
| Channel | Best suited for | Typical initial response | When to escalate |
|---|---|---|---|
| Live Chat | Cashier issues, code field, quick checks | 2 to 10 minutes | After 20 minutes with no progress |
| Withdrawals, KYC, SoF, complex cases | 2 to 12 hours | After the stated window or 24 hours | |
| Callback | Bank confirmations, identity questions | By arrangement | If the bank deadline expires on the same day |
Mini Case: A wallet withdrawal was pending for several hours. The player contacted via chat with the Request ID and immediately afterwards sent an email with a single ZIP file. The team identified a queue error and approved the withdrawal the same day.
Start the reset from the login page, open the email on the same device, create a new password you have not used before, and then sign out of all sessions via the profile. Finally update the 2FA backup codes in your password manager or on paper.
Set up TOTP codes in an authenticator app, keep the backup codes offline, and attach a second factor to a spare device. If you lose access, support will require identity verification before temporarily disabling 2FA.
Several incorrect password attempts or unusual device activity can temporarily lock the account. The wait time is often short. If you cannot wait, draft a short ticket with your full name, date of birth, and a partially redacted photo of your ID to speed up the verification.
When changing an email, you must confirm the new address, often also via the old one if you still have access. When changing the phone number, there is usually an SMS verification and sometimes a selfie check. Changes during an ongoing withdrawal review may be delayed for security reasons.
New devices require a one-time confirmation via a link or code. Sessions end when tokens expire, you sign in on another device, or after sensitive cashier actions. If you have to log in too often, clear browser cache, allow cookies for the domain, and re-authenticate 2FA.
| Symptom | Likely cause | Quick fix | Next step |
|---|---|---|---|
| Password reset loop | Old email or auto-fill | Use the latest email, disable auto-fill | Request manual reset with ID photo |
| 2FA code rejected | Wrong time or different profile | Synchronize time, check account | Provide backup code or screenshot |
| Device authorization repeats | Cookies blocked | Allow cookies for the domain | Send a screenshot of the console to support |
Deposit not credited means the payment processor charged the funds, but no entry appears in the cashier area. Find the processor receipt, note the time, amount, and descriptor, and create a redacted screenshot of the account line. If the balance is still missing after the usual time window, open a ticket with exactly these proofs and request reconciliation on this Processor ID. For the steps per rail, you can find concrete instructions in the area mobile deposits and withdrawals.
Match the billing address exactly to your bank’s format, enable online or international transactions in the banking app, and complete the 3DS verification once. Do not start a new payment while the page is still processing to avoid double charges.
Wallets use access tokens that expire for security reasons. If the wallet window asks you to sign in again, log in there completely and confirm the amount. If you close the window before confirming, the token will not refresh and the attempt stays pending.
Typical status phases are Pending, Approved, and Released. On hold means that KYC, SoF, or the rail still needs to be clarified. Always include the Request ID when asking and ask specifically for the next planned review time.
Some rails have a limit per transaction. In such cases ask to split a larger withdrawal into multiple parts within these limits. Keep all parts under the same Case ID and confirm each receipt before requesting the next release.
If the announced time window has passed, send a short update with Request ID, timestamps, chosen rail, and a one-sentence request such as: Please confirm the next review and whether a split withdrawal would be faster.
| Problem | Attach receipt | First step | Await SLA | Escalation phrase |
|---|---|---|---|---|
| Deposit not credited | Receipt, descriptor, redacted account line | Wait for the normal window, then file a ticket | 1 to 12 hours | Please verify the Processor ID ... |
| Withdrawal pending | Request ID, KYC status | Ask for next review time | Same day or next day | Please confirm the next review and the queue. |
| Wallet Reauth error | Screenshot of wallet prompt | Relink the wallet | Immediately | Wallet has been relinked, please update status. |
| Suspect double charge | Both Processor IDs | Stop attempts, open ticket | 1 bank business day | Please review and release a double reservation. |
Check after activation whether a progress bar appears, your stake stays under the cap, and you are really playing on an eligible game. If the display doesn’t move, stop immediately, take screenshots, and don’t switch between many titles spontaneously.
Open the deposit, expand details, enter the code as plain text and confirm it before paying. Rotate the device if the keyboard hides the field. If the browser layout stubbornly hides the field, you can enter codes directly in the mobile cashier, where the field is usually shown earlier.
Break the bonus in the promotions area before placing qualifying bets. This keeps your real-money balance, removes the bet cap, and resets the session. Get a screenshot with the date and time of the cancellation.
Place activation overview, timestamp, code, and deposit receipt in the same folder. Mention in the ticket whether the progress bar was visible. With three to four well-chosen screenshots you usually avoid follow-up questions.
Max Cashout refers to winnings from bonus funds. Quote the relevant clause, show the composition of your balance, and ask to separately confirm the pure cash amount and the portion affected by the cap. For practical examples, caps, and procedures, see Rules for bonuses with low wagering requirements.
| Error | Likely cause | Clean solution | Evidence |
|---|---|---|---|
| Code not accepted | Whitespace or expired | Enter as plain text, try again once | Error banner, code tile |
| Progress bar missing | Not eligible game | Switch to a whitelisted slot | Game name, stake, timestamp |
| Winnings removed | Stake cap exceeded | Send session log and cap clause | Stake list, text excerpt of the limit |
A passport or national ID with a clearly visible photo and all edges in the shot is accepted as identity proof. For address proof, recent utility bills or bank statements with full name and address are accepted. Screenshots are fine if sharp and complete.
Photograph documents in daylight or even lighting, place them on a flat, high-contrast surface, and avoid reflections. Ensure that the profile name and address exactly match the documents. Upload as PNG or PDF within the size limits.
Source of Funds proofs show where your deposits come from. Payslips, business invoices, or bank statements are common, as long as sums and patterns match your playing behavior. Do not redact relevant lines, but keep issuer, name, and total sums visible. For the general safety framework you can read how you play within a safe framework inside a safe framework.
Common rejection reasons are reflections, cropped corners, or too much redaction. Re-photograph the document in better light, include all edges in the shot, and loosen the redactions enough so that the examiner can clearly see the name, issuer, and totals.
Simple KYC checks are often completed on the same day if the files are clear. If the case exceeds the stated deadline, reply in the existing thread with a short summary and ask for the next check. Do not open a second ticket for the same topic.
| Reason | Example | Quick correction | How to avoid in the future |
|---|---|---|---|
| Reflection on the ID | Light streak across the photo | Take a new photo in daylight | Use a matte surface |
| Address discrepancy | Profile uses old spelling | Match profile to the billing format | Copy address exactly from the document |
| Too much redaction | Bank name or amounts hidden | Reveal issuer and amounts | Only redact truly unnecessary lines |
Escalate if the promised SLA was clearly exceeded or you have new evidence that truly changes the case. Escalations without new information slow down processing. Stay concise, factual, and precise with the facts.
Three-paragraph structure: a brief summary with IDs and dates, a list of receipts and prior steps, and one sentence of what you specifically expect. Attach another ZIP file, for example 2025 11 28_case53421.zip.
A reversal means an outstanding withdrawal is credited back to your player account so you can correct data or switch rails. Use this option sparingly and ideally only once per withdrawal, especially if the support recommends an alternative route.
Note every action with time, channel, and agent initials. This log makes your case easier to verify and increases the chance of a same-day decision if the process is escalated.
A small test cashout before larger requests validates the rail and recipient data. Once this test has run cleanly, you can argue more easily in a dispute that this was only a technical exception. If speed is your main concern, see the guide to fast withdrawals in real-money play, and align sessions and payment paths accordingly.
Conclude the process with a brief recap: which rail worked most reliably, which receipts were decisive, what you would change next time. Adjust limits or switch to a more stable payment route if you have repeatedly encountered friction. If you haven’t set up the basics yet, check the Quickstart Overview to organize account hygiene and limits.
| Day | Action | Expected response | If no response | Note |
|---|---|---|---|---|
| 0 | Open first ticket with complete package | SLA window starts | Wait for the complete window | Only one thread |
| 1 | Brief follow-up with Case ID | Status update | Ask for next review time | Do not create a new case |
| 2 | Escalation email with the same evidence package | Review by senior team | Consider reversal if recommended | Be factual |
Mini Case: An unaccepted code was resolved within two hours after the player sent a single ZIP file with cashier view, code tile, receipt, and a one-sentence request (manual credit or new code). The agent manually credited the code and added the missing free spins.
© 2026 AV Casino
