
On this page you will find the most efficient contact channels for AV Casino Support, clear step-by-step instructions for resolving common problems, and ready-to-use templates for support tickets and escalations. Our aim is to resolve your concerns at the first attempt with a precise message and a complete proof bundle.
Live chat is the best choice for urgent cash transactions and simple account questions. Email is more suitable for withdrawals, KYC checks and all processes that require viewing attachments. A callback is useful if your bank requires verbal confirmation and you need to log a support note in your file.
For each problem, use a separate thread, use a concise subject line such as "Withdrawal pending – Wallet Corridor – Request-ID 53421" and attach a single ZIP archive with receipts and screenshots. Write a three-part message: What happened? What have you already tried? What needs to be solved?
The SLA defines the target time within which a team should respond. Live chat usually responds within a few minutes. Email responses in standard queues occur within hours. Finance teams operate on business days – please factor in weekends and public holidays accordingly.
Use PNG for screenshots and PDF for bank statements. Ensure all margins are visible, highlight relevant lines and name files using the scheme "2025-11-13_Receipt_ProcessorID.pdf" so staff can find them quickly.
The case ID is the unique number of your ticket. Include it in the subject when you follow up, and avoid opening new threads for the same problem. An orderly thread will be processed faster than several overlapping ones.
| Channel | Best for | Typical first response | When to escalate? |
|---|---|---|---|
| Live chat | Wallet issues, code entry, quick checks | 2-10 minutes | After 20 minutes with no response |
| Withdrawals, KYC, Source of Funds, complex resolutions | 2-12 hours | After the stated window or 24 hours | |
| Callback | Bank confirmations, identity checks | Scheduled | When the bank deadline ends on the same day |
Practical example: A wallet withdrawal was pending for hours. The player opened the chat with the Request-ID and immediately attached a ZIP archive by email. The team confirmed an issue in the queue and released the withdrawal later that same day.
Start the reset from the login page, open the email on the same device, choose a new password you have not used before, then sign out of all sessions via your profile and update the 2FA backup codes.
Set up TOTP in an authenticator app, store the backup codes offline, and register a second factor on a spare device. If you lose access, support will request identity proof before temporarily disabling 2FA.
Too many failed login attempts or unusual device behaviour can lead to the account being locked at AV Casino. The cooling-off period is usually short. If you cannot wait, open a brief ticket with your full name, date of birth and a photo of your ID with sensitive details obscured to speed up the verification.
For email: confirm the new address and verify it from the old one if you still have access. For phone: expect SMS verification and sometimes a selfie check. Changes during a withdrawal check may be delayed for security reasons.
New devices require a one-time approval link. Sessions can end when tokens expire, you sign in elsewhere or after important cash actions. If you frequently log out, clear the cache and re-authenticate the 2FA.
| Symptom | Likely cause | Immediate solution | Next step |
|---|---|---|---|
| Password reset loop | Old link or autofill | Open the latest email, disable autofill | Request a manual reset with ID |
| 2FA code rejected | Time skew or wrong profile | Synchronise phone time, check account | Provide a screenshot of the backup code |
| Device sharing repeats | Blocked cookies | Allow cookies for the domain | Send a Console screenshot to support |
Locate the processor receipt, note the time, amount and descriptor, and take a blurred screenshot of the bank line. If the wallet remains empty after the usual window, submit a ticket with these proofs and request alignment for this specific Processor ID. For end-to-end steps by corridor see Mobile deposits and withdrawals.
Make sure your billing address matches the format used by your bank, enable online or international payments in your banking app and complete the 3DS challenge once. Do not retry payments while the page shows "Processing" as this risks duplicates.
Wallet tokens expire. If the wallet panel prompts you to re-authorise, complete the login in the wallet window and confirm the amount again. Closing the wallet early aborts the update and leaves the attempt pending.
Statuses typically move from "Pending" to "Approved" to "Released". "On Hold" means the team is waiting for KYC, Source of Funds, or the availability of the payment method. Provide the Request-ID when you ask about the next check time.
Some payment methods have transaction limits. Ask the staff to split the withdrawal into several parts within the limits. Do all parts under the same case ID and confirm receipt of each part before requesting the next.
After the specified window has passed, write a precise update that includes the Request-ID, timestamp, corridor and a one-line request such as: "Please confirm the next review time and whether a split withdrawal would be faster."
| Problem | Evidence to attach | First action | Wait for SLA | Escalation text |
|---|---|---|---|---|
| Deposit not credited | Receipt, descriptor, blurred bank line | Wait for the normal window, then ticket | 1-12 hours | "Please coordinate for Processor ID ..." |
| Withdrawal pending | Request-ID, KYC status | Ask for the next review time | Same day - next day | "Confirm next review and position in the queue" |
| Wallet reauth failed | Screenshot of wallet prompt | Relink the wallet | Immediately | "Wallet re-linked, please update status" |
| Duplicate charge suspected | Both Processor IDs | Stop retries, open ticket | 1 working day | "Check for duplicate charge and release hold" |
Check whether the progress bar appears after activation, whether your bet stays under the cap and the game is on the eligible list. If the bar doesn’t move, stop the game and take screenshots before switching the game.
Open the deposit, expand the details, enter the code as plain text and confirm it before paying. Turn the device if the keyboard covers the field. If the layout continues to hide it, you can enter codes in the mobile cashier, where the field is shown earlier.
h3>Safe bonus cancellation: When and howCancel the bonus in the Promotions area before placing qualifying bets. This preserves your cash balance, removes wagering restrictions and resets the session. Take a timestamped screenshot of the cancellation for your records.
Keep the activation summary, timestamp, code and the deposit receipt in a folder. When you write a ticket, attach the three images and mention whether the bar appeared.
The maximum withdrawal amount applies to winnings derived from a bonus. Quote the exact clause, show the composition of your balance and ask the staff to confirm the cash portion and the amount covered by the cap. For practical play see Low Wagering Rules and Examples.
| Error | Likely cause | Clean solution | Evidence |
|---|---|---|---|
| Code not accepted | Spaces or expired | Paste 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 withdrawn | Stake cap exceeded | Provide session log | Stake list, cap clause |
Use a passport or National ID with a clear photo and all visible edges. The proof of address should be a recent electricity bill or bank statement showing your full name and address. Screenshots are acceptable if sharp and complete.
Take photos in daylight, place the document on a flat, high-contrast surface and avoid reflections. Ensure that the profile name and address exactly match the documents. Upload the files as PNG or PDF within size limits.
Source of Funds proves where your deposits come from. Payslips, business invoices or bank statements work if the sums align with your pattern. Do not obscure essential lines, but leave issuer, names and sums visible. If you need general security context, read how to play in a secure environment.
Most rejections occur due to reflections, cropped edges or excessive shading. Take a new photo in bright, diffuse light, include all corners and ease the shading so that the verifiers can verify the key fields.
Simple KYC is approved on the same day if the files are clear. If the estimate runs over, reply in the same thread with a brief summary and ask for the next check time. Do not open a duplicate ticket.
| Reason | Example | Quick solution | Prevention |
|---|---|---|---|
| Reflection on the ID | Light streaks across the photo | Re-photograph in daylight | Use a matte background |
| Addresses do not match | Profile uses old format | Adjust the profile to the invoice | Copy the invoice format exactly |
| Excessive shading | Issuer obscured | Make issuer and sums visible | Only obscure non-essential details |
Escalate after the stated SLA has passed or if you have new evidence that changes the case. An escalation without new data slows everyone down. Keep your tone factual and precise.
Use three paragraphs: problem summary with IDs and dates, list of proofs and attempted solutions, one-line request. Attach a ZIP archive named "YYYY-MM-DD_case53421.zip".
A reversal returns a pending withdrawal to your player account so you can correct details or switch the payment method. Use this option once if a corridor is blocked or if the support recommends another faster route.
Log every action with timestamp, channel and the initials of the staff member. This log helps to review your request and increases the chance of a same-day decision.
A small test withdrawal validates the corridor and recipient details before a large request. It also provides the team with a clean history for future withdrawals. If speed is your aim, coordinate sessions and channels for fast withdrawals in real-money play.
Complete the cycle with a brief debrief: Which payment method worked? Which proofs helped? What can you change next time? Set stricter limits or switch to a more reliable corridor if you repeatedly encounter problems. If you have not yet completed the essential setup, read the Quickstart overview to align account hygiene and limits.
| Day | Action | Expected response | If no response | Note |
|---|---|---|---|---|
| 0 | Open initial ticket with proof bundle | SLA window starts | Wait for the full window | Only one thread |
| 1 | Brief follow-up email with Case-ID | Status update | Ask for next review time | No new thread |
| 2 | Escalation letter with the same bundle | Review by senior | Consider reversal if recommended | Be factual |
Practical example: A dispute over a not accepted code was closed within 2 hours after the player sent a single ZIP with cashier screen, code tile, receipt and a one-line request for manual creation or a new code. The staff manually added the code and added the missing free spins.