On this page you will find the fastest ways to reach support, clear step-by-step solutions for common problems and ready-made text blocks for tickets and escalations. The goal is to resolve each issue with a single, well-structured message and a complete evidence package, rather than ending up in endless email threads.
In everyday use it doesn’t matter whether someone searches in the browser for AV Kasino, AV Kasyno, AV Kazino or AV Cazino — it always refers to the same support area. What matters is that you are definitely on the official site before you submit any data or documents.
If you are just getting started, you can get an overview of account setup, limits and payment methods in the Quickstart Overview. This support page is about preparing specific cases cleanly and getting a quick result.
Live chat is ideal for urgent cashier issues, questions about entering codes or simple account queries. Email is better for withdrawals, KYC, Source-of-Funds (SoF) and anything that requires attachments. Phone or callback appointments are helpful when your bank wants a verbal confirmation and you also need a note in the support case.
Use exactly one thread per problem and a clear subject, for example: "Withdrawal pending - wallet corridor - request ID 53421". Combine all evidence into a single zip archive and describe your issue in exactly three paragraphs: what happened, which steps you have already tested, and what outcome you expect.
An SLA is the timeframe within which a team typically responds. Live chat usually provides the first reply within a few minutes. Emails typically receive responses within a few hours, depending on workload and the day of the week. Banking and compliance teams work primarily on business days, so you should factor weekends and holidays into your planning.
Use PNG for screenshots and PDF for account statements or invoices. Always leave all borders visible, mark the relevant lines subtly and name files in a traceable way, for example "2025-11-13_receipt_processorID.pdf". This way agents can find the evidence without follow-up questions and don’t have to guess which document belongs to which process.
The Case ID is the unique number of your ticket. Quote it in the subject of every further message and avoid new threads for the same issue. A clean, continuous thread will be processed faster than multiple overlapping cases that first need to be merged.
| Channel | Best suited for | Typical first response | When to escalate |
|---|---|---|---|
| Live Chat | Cashier errors, code field, quick follow-ups | 2–10 minutes | After about 20 minutes with no progress |
| Withdrawals, KYC, SoF, complex cases | 2–12 hours | After the stated window has passed or after 24 hours | |
| Callback | Bank confirmations, identity checks | After scheduling | If the bank deadline is the same day |
Mini-case: A wallet withdrawal remained pending for hours. The player opened a case in chat with the request ID and then immediately sent a zip with all evidence by email. The team confirmed a queueing issue and released the withdrawal the same day.
Always start the reset directly on the login page. Open the email on the same device, click only the most recent link and set a new password that you have never used for this account before. Then sign out of all sessions, re-enable two-factor protection and update your backup codes.
Set up TOTP in an authenticator app, store backup codes offline and, if possible, register a second factor on a backup device. If you lose access, support will ask for identity proofs before 2FA is temporarily disabled or reset.
Multiple failed login attempts or unusual device activity can trigger a temporary lock. The cooldown phase is usually short. If you cannot wait, open a concise ticket with your full name, date of birth and a masked ID scan to speed up the review.
To change the email address, verify the new address and confirm the change from the old one if possible. For phone numbers you’ll need an SMS code and sometimes a selfie match. Changes during an ongoing withdrawal review may be delayed for security reasons.
New devices usually require a one-time approval via a link. Sessions end when tokens expire, when you log in on another device or after major cashier actions. If logouts occur unusually often, clear cache and cookies and reset 2FA cleanly.
| Symptom | Likely cause | Quick fix | Next step |
|---|---|---|---|
| Password reset loop | Old link or auto-fill | Open the latest email, disable auto-fill | Request a manual reset with ID proof |
| 2FA code rejected | Time sync or wrong profile | Synchronize phone time, check account | Send screenshot with backup code or error message |
| Device approval repeats | Blocked or deleted cookies | Allow cookies for the domain | Send a console screenshot to support |
Find the receipt from the payment provider, note the time, amount and descriptor and take a masked screenshot of the account line. If the cashier is still empty after the usual window, open a ticket with exactly this evidence package and request reconciliation of the specific processor ID. A step-by-step guide per payment method is available in the mobile deposits and withdrawals section.
Enter your billing address exactly in the bank’s format, including abbreviations and special characters. Enable online and, if necessary, foreign transactions in the banking app and complete the 3DS dialog exactly once. Do not start another payment while the page still shows "processing", as duplicate authorizations often occur at this stage.
Wallet tokens expire for security reasons. If the panel asks you to sign in again, log in fully within the wallet window and confirm the amount and merchant. If you close the window prematurely, the token will not be refreshed and the attempt will remain in a pending state.
Status messages typically change from pending to approved to released. On hold means the team is still waiting for KYC, SoF or rail availability. Always quote the request ID in follow-ups and ask for the next planned review time.
Some rails have per-transaction caps. Ask the agent to split your withdrawal into several releases within those limits. Keep all partial amounts under a common Case ID and confirm each arrival before requesting the next tranche.
After the specified window has passed, write a short update with the request ID, timestamps, corridor and a one-sentence request, for example: "Please confirm the next review time and whether a split payout would be faster."
| Problem | Proof | First action | Wait SLA | Escalation text |
|---|---|---|---|---|
| Deposit not credited | Receipt, descriptor, masked account line | Wait normal window, then ticket | 1–12 hours | "Please reconcile payment for Processor-ID ..." |
| Withdrawal pending | Request ID, KYC status | Ask for next review time | Same or next day | "Please confirm the next review and queue position." |
| Wallet reauth failed | Screenshot of the wallet prompt | Relink the wallet | Immediately | "Wallet relinked, please update status." |
| Suspected duplicate charge | Both processor IDs | Stop further attempts, open ticket | 1 business day | "Please check and release the duplicate authorization." |
After activation, check whether a progress bar appeared, that your bet stays under the cap and that the chosen title is on the list of allowed games. If the bar doesn’t move despite bets, stop the game, take screenshots and only then switch to other categories.
Open the cashier, expand the details, enter the code as plain text and confirm it before triggering the payment. Rotate the device if the keyboard covers the field. If the layout persistently hides the field, you can enter the code in the mobile cashier, where the field is usually visible earlier in the flow.
Cancel the action in the promotions area before placing qualifying bets. This way your real-money balance remains untouched, caps are removed and the session is reset. Keep a timestamped screenshot of the cancellation for later queries.
Save the activation summary, time, code and deposit receipt in a folder. When you write a ticket, include these three screenshots and mention whether a progress bar was visible or not.
Max cashout refers to winnings from bonus funds. If in doubt, quote the exact clause, show how your balance is made up of bonus and real-money portions and ask to have the real-money portion clearly confirmed. Practical flows for caps and wagering requirements can be found in the Rules and examples for low wagering requirements section.
| Error | Likely cause | Clean solution | Required evidence |
|---|---|---|---|
| Code not accepted | Spaces or expiry date | Enter code as plain text, test once more | Error banner, offer tile |
| Progress bar missing | Game not allowed | Switch to a whitelisted slot | Game name, stake, timestamp |
| Winnings removed | Stake cap exceeded | Provide session log | Stake list, cap clause |
For identity proof, a passport or national ID with a clearly visible photo and all edges in the image are suitable. For address proof, recent utility bills or account statements are accepted that show your full name and address. Screenshots are fine if they are sharp and the full border is visible.
Photograph documents in daylight or with even artificial light, place them on a flat, contrasting surface and avoid reflections. Make sure the profile name and address are written exactly as on the documents. Upload files in the required format (PNG or PDF) and within the size limits.
A Source-of-Funds request is about where your deposits come from. Payslips, tax statements, business invoices or account statements are common, as long as amounts and patterns match your play behavior. Redact only truly irrelevant transactions, but keep the bank, name and totals clearly visible. General guidance on safe framework planning can be found in the play safely framework section.
Most rejections are caused by glare, cropped corners or excessive redaction. Retake the photo in calm light, show all corners and reduce redaction so that reviewers can clearly read all mandatory information.
Simple KYC cases are often completed the same day if files are sharp and consistent. If the announced window has been exceeded, reply in the same thread with a short summary and ask for the next review time. Do not open a new case on the same topic.
| Reason | Example | Quick fix | Prevention |
|---|---|---|---|
| Reflection on ID | Light streak across the photo | Retake in daylight | Matte surface and no flash |
| Address format mismatch | Profile uses old spelling | Adjust profile to match the bill | Adopt address format directly from the document |
| Too much redaction | Bank or sums hidden | Make bank, name and total sums visible | Redact only truly irrelevant lines |
You should escalate if the promised SLA window has been exceeded or if you have new, relevant evidence that changes the case significantly. An escalation without new facts slows down processing. Keep tone and content factual, without emotional wording.
Structure it in three paragraphs: a summary of the problem with IDs and dates, a list of the evidence and the steps you have taken, then a one-sentence request as a clear objective. Name the zip archive for example "YYYY-MM-DD_case53421.zip".
A reversal returns a still-pending withdrawal to your player account so you can correct data or change the rail. Use this option at most once per withdrawal if a corridor is blocked or if support explicitly recommends another route.
Record every action with time, channel and the agent’s initials. This log makes the case easier to review and increases the chance of a same-day decision.
A small test cashout checks the corridor and recipient details before you request a large amount. It also creates a clean history that later withdrawals can reference. If speed is your priority, the examples in the fast real-money withdrawals section help plan your sessions and payment paths.
Close the case with a short recap: which rail worked in the end, which evidence actually helped and what you will do differently next time. If necessary, tighten limits or switch to a more reliable payment method if you repeatedly run into the same issues. If you haven’t set basic settings like limits and rails properly yet, take a look at the Quickstart Overview.
| Day | Action | Expected response | If no response | Note |
|---|---|---|---|---|
| 0 | Initial ticket with evidence package | SLA window starts | Wait the full window | Only one thread on the topic |
| 1 | Short follow-up with Case ID | Status update | Ask for the next review time | No new thread |
| 2 | Escalation letter with the same evidence package | Review by a senior agent | Consider reversal if recommended | Remain factual |
Mini-case: A dispute over a code that wasn’t accepted was resolved in two hours after the player sent a single zip with a cashier screenshot, code tile, receipt and a one-sentence request for a manual credit or a new code. The agent applied the code manually and added the missing spins without further questions.
If you follow all these points, you will have support under control in daily life and use the structures of AV Casino so that cases are planned, documented and resolved within a manageable timeframe.
© 2026 AV Casino
