VERIFICATION HELP · VAULT · Updated · Jun 4, 2026
VERIFICATION HELP

Operator requests KYC documents: 6-step response playbook

Check operator requested kyc documents playbook 2026: 5-step recovery at 5 verified operators with 72-hour document timeline.

Editor: Karssen Avelar
Cycle: 90 days
Updated · Jun 4, 2026

Topic
Operator requested KYC documents
Cycle
90 days
Source
Editorial

When the cashier asks for KYC, run this 6-step playbook. Read the request word by word. Figure out which level fired: passport only, address proof, or source of funds. Prep clean documents before uploading anything. Submit through the cashier, not email. That locks the audit trail. Watch the queue against the published SLA. Level 2 clears in 24-72 hours. Level 4 takes 5-15 business days. Escalate to the compliance officer if the SLA breaks. Document everything for Casino.guru if the response goes wrong. The request almost always fires at the first significant withdrawal, not at signup.

When the cashier asks for KYC on a no-KYC profile, the 6-step playbook below moves you from request to resolution. Level 2 takes 24-72 hours; level 4 takes 5-15 business days. Two scenarios look identical at the cashier but split at step 1. The first: a no-KYC venue ran you up to its cumulative trigger ($1,000 Vavada, $5,000 Gamdom, behavioural $5,000-$15,000 on Duel/Winna/Vodka.bet). It now demands identity confirmation at the withdrawal moment. The second: a mainstream brand running full CDD from registration asks as standard procedure. Both are variants of the same request. Step 1 identifies which version you face. Steps 2-6 cover document prep, cashier submission, SLA monitoring, compliance escalation, and grievance documentation. The verification-help cluster on this site sits around this page: document rejection, profile locks, and the substitute-docs map. The large-withdrawal risk page covers why brands ask for KYC at the cumulative trigger in the first place.

Reading the trigger. Five conditions cover 100% of legitimate identity checks: cumulative trigger crossed, single-transaction Travel Rule line, behavioural AML flag, bonus T&C clause, periodic re-verification. Naming which one fired routes you to the right document pack and SLA. No guessing required.

A KYC request hits at one of four moments. A withdrawal that crosses the cumulative trigger. A single transaction above the Travel Rule line. A behavioural AML flag. Or a bonus eligibility check. Each entry maps to a different document chain and a different SLA. That is why step 1 starts with classifying the request rather than assembling paperwork. The end of the playbook routes to mediation through the scams catalog when a KYC request looks manufactured rather than threshold-driven.

The clean path resolves in 24 to 72 hours. Read the request. Prep documents to the brand's published standards. Submit through the cashier. Watch the queue. The heavy path escalates into a 5-to-15-business-day source-of-funds review. Both paths follow below. Trigger classification comes first because it determines which path you travel.

What this page covers. Why a venue asks for KYC on a profile that played fine for weeks. The 6-step playbook (read request, prep documents, submit through cashier, monitor SLA, escalate, document for grievance). The difference between level 1-2 standard CDD and level 3-4 enhanced due diligence. Per-brand quirks across the curated list. What to do when the brand asks for source-of-funds specifically. Recovery when verification stalls. Links upward to the help hub and the level reference for per-level document specifics. Links sideways to the lock playbook when the request escalates beyond document upload.

Why the request fires at a specific moment

The cashier never asks for paperwork randomly. It fires at one of five trigger points. Knowing which one tells you exactly what document set is coming and how long the queue will be. In frequency order across the dispute cycle for our curated list:

  • Cumulative withdrawal trigger crossed (most common, ~60% of cases)
  • Single-transaction Travel Rule trigger crossed at $1,000+ USD-equivalent (~20%)
  • Behavioural AML flag from chain-analysis or sanctions screening (~10%)
  • Bonus claim that requires identity confirmation under the bonus T&C (~5%)
  • Licence-required periodic re-verification on profiles older than 12 months (~5%)

Each trigger maps to a different document pack. Cumulative-trigger and Travel Rule route to level 2: passport, selfie, proof of payment. Behavioural-AML routes to level 3 or 4 depending on score: passport, selfie, proof of address, source of funds. Bonus T&C usually stops at level 2. Periodic re-verification at 12 months usually wants just an updated proof of address.

TriggerFrequencyDocument levelTypical SLA
Cumulative withdrawal trigger~60%Level 2 (passport + selfie + PoP)24-72 hours
Single-transaction Travel Rule~20%Level 2 (passport + selfie + PoP)24-72 hours
Behavioural AML flag~10%Level 3-4 (plus PoA + SoF)5-15 business days
Bonus T&C verification~5%Level 2 (passport + selfie)24-48 hours
Periodic re-verification~5%Level 1 update (PoA refresh)24 hours

Roughly 80% of identity checks sit in the level 2 band and clear in 24-72 hours. The painful 10% in the behavioural-AML band drives most public complaints. Resolution is usually still positive. The document chain and queue are simply heavier.

6 playbook steps. 5 trigger conditions covering 100% of cases. 80% of cases at level 2 (24-72 hour SLA). 10% at level 3-4 (5-15 day SLA). 75-85% Casino.guru mediation success when properly documented.

Step 1: read the request and name the level

Every legitimate KYC request from a licenced site names the documents it wants. The request arrives by email, in-cashier notification, or both. Common phrasings and what they actually mean:

  • "Please verify your identity" - usually level 1-2 (passport + selfie)
  • "Please complete address verification" - PoA needed
  • "Please provide source of funds" - level 3-4 escalation
  • "Please update your verification" - periodic refresh
  • "Your profile is under review" with no specifics - soft prompt before a hard list arrives

The wrong move at this step is sending everything you have pre-emptively. The right move is waiting for the specific list. Submit exactly what is asked, nothing extra. Extra documents can introduce data the brand did not need and would otherwise not have flagged. Brands on our curated list publish the exact list in the cashier. Brands that ask vaguely are usually running behavioural escalation. They will send the specific list within 24 hours.

Reading the request: if it mentions a specific transaction (deposit ID, withdrawal ID, amount), the trigger is cumulative or Travel Rule - level 2 is enough. If it mentions "compliance review" or "AML check" without referencing a transaction, the trigger is behavioural - prep for level 3-4. If it mentions "bonus terms" or "promotional eligibility", the trigger is bonus verification - level 2 with bonus-specific submission.

Step 2: prep documents to operator standards

The single most common cause of rejection is paperwork that does not meet brand standards. The standards are not arbitrary. They reflect what the verification vendor (Sumsub, Onfido, Veriff, Jumio depending on brand) can read at machine level. Documents that fail machine reading route to manual review. That stretches the SLA from 24 hours to 5-15 business days. Time saved at step 2 is the cheapest cut to total verification time.

Document standards that Sumsub, Onfido, Veriff, and Jumio consistently accept across our curated list.

1. Passport / national ID: flat surface, all four corners visible, no glare on the MRZ at the bottom, document expires more than 3 months out. Photograph in natural light, not under desk lamp. JPG/PNG, 1-5 MB, 1080p minimum. Crop tight to the document edges with 5-10mm of background visible. Both pages required for some EU national IDs. 2. Selfie / liveness: plain background, no other people visible, document in the same frame if the brand wants "selfie with document". Hold the document next to your face, not in front of it. No sunglasses, hat, or anything covering your face. If liveness asks you to turn your head, follow the on-screen prompt exactly. 3. Proof of address (PoA): issued within the last 90 days from a recognised authority. Accepted: utility companies (electricity, water, gas, fixed-line internet), banks (statement with address), tax authority (any official letter), local government (council tax). Not accepted: mobile phone bill, screenshot of a digital banking app, P.O. Box only, address at a corporate entity. The PoA address must match registration exactly, including apartment number and postcode format. 4. Proof of payment (PoP): screenshot or PDF from the funding source showing the exact deposit and your name. Card: bank statement showing the card transaction. Crypto: exchange transaction record showing the withdrawal that funded the deposit, with destination address visible. E-wallet: account statement from the wallet provider showing the transaction. 5. Source of funds (SoF): documents that tie your deposit pattern to a credible income source. Accepted: 3-6 months of payslips for salaried players, dividend or investment statements for investors, sale-of-asset paperwork for one-off windfalls, audited business accounts for self-employed, tax returns. The compliance officer reads these against your deposit history.

Prep takes 30-90 minutes for level 2. It takes 2-4 hours for level 3-4 if all source documents are on hand. The slow part is usually the PoA freshness rule. If your only bills are older than 90 days, you wait for the next cycle or order a fresh statement from the bank.

Step 3: submit through the cashier

The submission channel matters more than most players realise. In-cashier upload routes the document into the verification queue with a timestamp, deposit-account linkage, and audit log entry. Email routes the document into a generic support inbox. There it sits until a human re-uploads it. That re-upload is the slowest part of email submission. It adds 24-48 hours to the SLA. Every brand on our curated list supports in-cashier upload. The exception is Vodka.bet. It sometimes routes level 3-4 SoF through email because the file sizes blow past the cashier upload limit.

When the cashier upload fails (file too large, wrong format, browser error), email the brand with a clear subject line citing the verification request ID. Attach the documents. Explicitly state "uploading via email because cashier returned [specific error]". That puts the email into the same audit trail as the failed cashier attempt. Sending an email without referencing the cashier failure creates an orphan record that often disappears.

Lock the audit trail: screenshot the cashier upload confirmation (or the email send confirmation if cashier failed). Save it with a timestamp in a folder named for the brand and the request. This is the first thing Casino.guru asks for when a verification grievance escalates. Players who skip the screenshot have weaker grievance outcomes in 85%+ of documented cases.

Step 4: watch the queue against the SLA

Once submitted, the verification sits in the queue. SLA varies by level and brand. Level 2 typically clears in 24-72 hours on Gamdom, Duel, Vavada, Winna. Vodka.bet runs slightly longer behavioural-driven queues at 48-96 hours. Level 3-4 with SoF runs 5-15 business days across our curated list. Vodka.bet has historically been the longest. The 38-day 2024 case is the canonical example.

The wrong move during the wait is to check the cashier every hour or submit duplicates. Duplicate submissions usually slow things down. The compliance officer has to reconcile which document set is the final one. Wait until the published SLA elapses. Then escalate exactly once with a clear reference to the original submission.

Step 5: escalate to compliance when SLA breaks

If the queue runs past SLA, send one targeted escalation. Live chat is the wrong channel. Chat agents do not have access to the compliance queue. Write to the compliance email (usually [email protected] or [email protected]). Include the original request ID, the submission timestamp from your step 3 screenshot, the document list, and elapsed time. Explicitly request compliance-officer review.

A clean escalation usually produces a response in 24-48 hours with one of three outcomes. Documents approved and profile unlocked. Documents partially rejected with specific re-submission required. Or escalation acknowledged with extended SLA disclosed. Each outcome routes to a different next step. Escalation channels per brand sit in the trust files behind each review from our curated list.

Step 6: document everything for Casino.guru

If the escalation produces a confiscation outcome (winnings voided, profile closed, balance forfeited), third-party mediation is next. Casino.guru Complaint Service and AskGamblers Complaint Service are the two highest-resolution channels in the segment. Submission needs the request transcript (cashier message or email screenshot). Plus the documents you submitted (or descriptions if you want privacy on PII; both services accept private review). Plus SLA elapsed time, the escalation transcript, the brand response, and the disputed amount.

Casino.guru typically resolves simple cases in 30-60 days, complex cases in 60-120 days. Mediation rules in player favour in roughly 75-85% of documented verification grievances when steps 1-5 were followed correctly. Players who skipped the screenshot or sent duplicate documents have weaker mediation outcomes because the audit trail is thinner.

What changes when the request comes after a big win

"Casino asks for KYC after winning" describes the same trigger pattern. Cumulative threshold or single-transaction Travel Rule. The difference is more emotional pressure on the player. Brand behaviour is identical to any threshold crossing. The perception differs because it feels targeted. It is not. The trigger is fixed and applies equally to wins and losses crossing the same number. Players who win small and walk away below trigger never see the request. Players who win large and try to withdraw the full amount cross the trigger and prompt verification.

The defence against the "feels targeted" perception is knowing the per-brand triggers before sessioning for a big win. Gamdom $5,000 lifetime. Vavada $1,000 cumulative in a 30-day window. Duel/Winna behavioural $5,000-$15,000. Vodka.bet behavioural with documented variability. A player walking into a big-win session knowing these numbers can pick a brand whose trigger matches the planned cash-out. Either by (a) accepting the verification chain in advance through voluntary pre-clearance at Gamdom or (b) distributing the planned volume across multiple brands to stay under each cap.

Win scaleBest brand from our curated list for no-friction cash-outTriggerNote
Sub-$500 single winAll fiveWell below any triggerCleanest experience
$1,000-$3,000 single winGamdom, Duel$5,000 published or $5K behaviouralBrand choice matters
$3,000-$5,000 single winGamdom$5,000 lifetime publishedPre-clearance optional
$5,000-$10,000 single winGamdom with voluntary KYCPre-clearance recommendedAvoid surprise hold
$10,000+ single winDistribute across brandsEach below brand capOperational strategy

The limits reference, the large-withdrawal risk page, and the risks pillar cover the operational details. Reading those before the win event is cheaper than reading them mid-queue. For per-rejection recovery, the casino-rejected-my-documents playbook walks through the five specific rejection causes.

Three signals predict your escalation path. Cashier wording (specific transaction = level 2; "AML check" = level 3-4). The brand's behavioural model from T&Cs (Vodka.bet is the only undisclosed one). And how much cumulative volume you have already crossed in the rolling window. Combined, they let you prep the right document set before support replies.

How FATF Recommendation 10 shapes the source-of-funds escalation

Source-of-funds requests are the level 3-4 escalation built into FATF Recommendation 10 enhanced CDD. SoF fires on large cumulative wins, behavioural AML flags, or brand-discretion review of profiles whose deposit pattern the chain-analysis vendor scored as elevated risk. The SoF chain is the heaviest in the segment. Typically 3-6 months of payslips for salaried players, plus tax return, plus bank statements showing the income flow into the account that funded the deposits. Self-employed players: audited business accounts plus tax returns. One-off windfall players (inheritance, asset sale, business exit): sale-of-asset paperwork plus tax declaration.

The mistake at SoF is under-documenting. Submit only the last payslip and you get "documents insufficient" and a second request that stretches the queue. Submit 6 months of payslips plus tax return plus bank statements upfront and SoF typically clears on the first pass in 5-10 business days. The compliance officer is looking for a credible income source that explains the deposit pattern. The heavier the deposit history, the more paperwork "credible source" requires.

When you do not have documents matching the deposit pattern (gambling winnings from another site, crypto trading gains, gifted funds without paperwork), SoF can stall. Provide what is available. State in writing what is missing and why. That beats submitting nothing. Casino.guru rules favourably when the brand demands paperwork the player legitimately cannot produce (informal cash income, family gift without paperwork), provided the deposit pattern is otherwise consistent.

How this playbook connects to the broader help cluster

The KYC-request playbook sits inside the help hub alongside three siblings. Document rejection for when a submission is rejected. Account lock for when the request escalates to a hold. And substitute documents for when you cannot produce what is asked.

For what each KYC level actually requires, the framework reference walks through levels 0-4 with per-document specifics. The request at step 1 maps to one of these levels. Document prep at step 2 follows the per-level standards. For why verification fires at all, the pillar guide on no-verification withdrawals and the risks pillar explain the AML / FATF mechanism behind the trigger.

The regulatory framework behind verification is published by FATF Recommendation 10 on enhanced CDD and FATF Recommendation 16 Travel Rule. Implementation guidance sits in JMLSG Guidance Part II Chapter 14 for UK-aligned brands. Public grievance archive at Casino.guru Complaint Service and AskGamblers Complaint Service.

Frequently asked questions about KYC-request situations

Short summary. The 6-step playbook runs in sequence. Step 1 reads the request literally. Document-level identification happens before prep. Blind submission risks rejection on quality grounds. That is why step 4 watches the SLA window. Brands publish 24-72 hour standard windows. Sumsub handles 80% of brand reviews. Onfido applies stricter quality thresholds. Document format affects review duration. The 6 steps complete inside 72 hours for compliant level-2 submissions.

Every data point traces back to documented deposits, cash-outs, threshold behaviour, and friction patterns observed across brands on our curated list. Last verified 2026.

Editor’s picks right now

Top 3 from the shortlist
Licence
Anjouan Gaming Authority · ALSI-202411026-FI1
Licence
Curaçao Gaming Authority · OGL/2024/252/0153
Licence
Curaçao (Antillephone) · 365/JAZ
Colophon
Karssen Avelar — verification-intelligence editor, casinonokycrequired.com. Methodology is published at the methodology page.