Last updated: .
Casino KYC Documents GuideClassify the request before uploading sensitive files
Direct answer: casino KYC document requests usually fall into identity/age, proof of address, payment ownership, wallet ownership, bank/e-wallet/crypto transaction evidence, selfie/liveness checks and source-of-funds or enhanced review. The exact request depends on the operator, market, payment route, withdrawal status, bonus review and risk checks.
Submit only the document category requested through the verified operator portal. Do not share passwords, CVV, 2FA codes, full card numbers, seed phrases, private keys or recovery phrases. KYC documents do not guarantee legal access, account approval, withdrawal approval, payout speed or dispute resolution.
This page explains document categories; it does not collect or approve documents
The Playbook USA may earn commissions from some destination pages. This guide is educational and does not provide legal, tax, financial, privacy, identity-theft, gambling, payout, dispute-resolution or account-approval advice. We do not collect, review, store or forward KYC documents. Use only the verified operator portal or official support route before submitting sensitive files.
What documents can a casino request for KYC?
Common casino KYC document categories are government ID, proof of address, payment ownership, wallet ownership, bank/e-wallet/crypto transaction evidence and source-of-funds evidence. Some operators may also ask for selfie, liveness or video checks. Not every account needs every category; the exact request depends on the current portal message, account status, payment route, withdrawal request and risk review.
Documents can help an operator review identity, address, payment ownership or source-of-funds context, but they do not prove legality, guarantee withdrawal approval, override bonus terms or remove responsible-gambling review.
Sources to check before uploading KYC documents
Use source ownership before submitting sensitive files. Operator portals, regulator records, payment providers, FinCEN context, FTC identity-safety guidance and user records solve different problems.
| Source | Source owner | Checked | What it proves | What it does not prove | Safest use |
|---|---|---|---|---|---|
| Current operator KYC portal or official support request | Operator / KYC provider / official support | Before every upload or resubmission | The exact current document category, format, file-size, recency, name/address/payment/wallet or source-of-funds request. | Approval, legal access, payout timing, refund, dispute result or privacy outcome. | Treat as the primary instruction source; save request wording and ticket ID. |
| Operator terms, privacy policy and withdrawal/KYC policy | Operator | Before relying on timing or acceptance claims | Published policy context for verification, withdrawals, privacy handling and document review. | That a specific document package will be approved. | Use to compare portal request against published policy and save URL/date checked. |
| State regulator or licensing record | State regulator, gaming commission, lottery/gaming authority or official source | Before assuming market/legal availability | Whether a state-facing route or operator/source appears in an official regulator context. | KYC approval, payout approval or document acceptance. | Use for state/source context, not as a document-acceptance promise. |
| FinCEN Casino or Card Club Risk-Based Compliance Indicators | FinCEN | July 1, 2026 | Casino/card-club compliance can be risk-based and tied to business activity, products, services, customers and locations. | That one online casino will accept one specific document. | Use to explain why enhanced review/source-of-funds requests can vary. |
| Payment provider, card issuer, bank, e-wallet or exchange record | Issuer, bank, wallet provider, exchange or payment processor | Before submitting payment ownership proof | Account ownership evidence, transaction records, card/wallet/bank descriptors and official statements. | Casino approval, refund, chargeback outcome or source-of-funds clearance. | Use for payment proof only; do not expose unrelated history if not requested. |
| FTC personal-information safety guidance | Federal Trade Commission | July 1, 2026 | Personal information is valuable and should be protected from hackers and scammers. | Operator privacy compliance or document approval. | Use for privacy caution, scam suspicion and sensitive-data handling boundaries. |
| NCPG Helpline Chat | National Council on Problem Gambling | July 1, 2026 | Call/text 1-800-MY-RESET and NCPG chat are gambling-support routes. | KYC approval, payout, legal advice, financial advice or dispute resolution. | Use if verification delays, withdrawal stress, debt, secrecy or chasing becomes hard to control. |
| User records: request wording, files submitted, upload receipt, support ticket, rejection reason and last checked date | User, operator portal, support system and file metadata | Before resubmitting or escalating | Your account-specific timeline and evidence packet. | Approval, payout, identity-theft outcome or legal result. | Save before contacting support, regulator, payment provider or scam-report route. |
Map the KYC portal wording to the right document category
Do not upload random documents. Classify the request first, then use the exact owner route.
| Portal wording | Likely category | Do not confuse with | Owner route |
|---|---|---|---|
| Upload government ID / verify identity / age check | Identity and age verification | Payment ownership or address proof unless requested. | ID verification |
| Upload utility bill / proof of residence / address document | Proof of address | Bank ownership or source of funds. | Proof of address |
| Verify card / show payment method / card ownership | Payment ownership | Identity alone; never expose CVV/full card. | Payment verification |
| Wallet proof / crypto transaction / TXID / exchange account | Crypto wallet or transaction evidence | Seed phrase, private key or recovery phrase request. | Wallet/payment verification |
| Source of funds / source of wealth / enhanced due diligence | Enhanced review | Basic photo quality issue. | KYC best practices |
| Selfie / liveness / video verification | Identity confirmation / account holder presence | Document upload or source-of-funds review. | ID verification |
| Withdrawal pending until verification completed | KYC tied to payout workflow | Payout approval after upload. | Withdrawal verification |
| Send documents by email, DM, Telegram or external upload link | Potential phishing / unsafe route | Verified operator portal. | Phishing scams |
Casino KYC document category matrix
| Category | Common examples | Usually used for | Does not prove | Safety boundary |
|---|---|---|---|---|
| Government ID | Passport, driver's license, state ID, national ID where accepted. | Identity, date of birth, legal name and sometimes address. | Payment ownership, source of funds, state legality or withdrawal approval. | Use verified portal only; do not send ID via social DM or random support links. |
| Proof of address | Utility bill, bank statement, tax/official letter, lease or accepted government letter. | Residential address and document recency. | Identity by itself, payment ownership or source of funds. | Check issue date, full-page visibility, accepted file type and redaction rules. |
| Card payment ownership | Card photo, card statement, issuer record or payment-method screenshot where accepted. | Showing the card belongs to the account holder. | Withdrawal approval or source of funds. | Never show CVV or full card number; ask official support about middle digits and expiry if unclear. |
| E-wallet ownership | Wallet account page, name/email screen or transaction receipt requested by portal. | Funding route ownership and account match. | Full payment history, password access or source-of-funds clearance. | Never expose passwords, 2FA codes or unrelated transaction history unless explicitly required. |
| Bank ownership or bank statement | Bank statement, bank letter, ACH/bank-transfer record. | Bank-account ownership, address, transaction evidence or payment route. | Legal access, approval, refund or withdrawal speed. | Submit only requested pages/fields; do not expose unrelated balances or full account numbers unless required. |
| Crypto wallet ownership | Wallet address, TXID, exchange account evidence, transaction screenshot, portal-directed proof. | Relationship to a wallet or crypto transaction. | Tax status, legality, source of funds or payout approval. | Never share seed phrase, private key, recovery phrase, exchange password or full unrelated wallet history. |
| Source of funds / source of wealth | Pay slip, bank statement, sale record, transaction records or official financial evidence. | Enhanced/risk-based review for larger, unusual or flagged activity. | Assured approval or financial/tax clearance. | Submit exactly what official portal asks for and save ticket IDs. |
| Selfie, liveness or video check | Selfie with ID, liveness scan, short video or app-based identity step. | Confirming the account holder is present and matches ID. | Payment ownership, source of funds or withdrawal approval. | Use only official app/portal flow; do not send biometric/video files through social links. |
Safe upload and redaction boundaries
Redaction rules vary by operator. Ask official support if the portal does not clearly say which fields are required.
| Document or proof | Often needed | Never expose | Ask official support if unclear |
|---|---|---|---|
| Government ID | Full name, date of birth, photo, ID number, expiry, corners and machine-readable zone where required. | Do not send through social DMs, unofficial email links or public upload forms. | Whether front/back, selfie, notarized copy or specific file type is required. |
| Proof of address | Name, residential address, issuer, date, full-page document and all corners. | Unrelated pages or unrelated household/member data if not required. | Accepted document types, recency window, PDF vs screenshot and redaction policy. |
| Card photo | Name, last four digits, sometimes first six digits and card brand. | CVV, full card number, online banking login or one-time codes. | Whether expiry date and middle digits should be covered. |
| E-wallet | Name, email/account identifier and relevant transaction if requested. | Password, 2FA codes, recovery codes and full transaction history unless explicitly required. | Which account screen or downloadable statement is accepted. |
| Crypto wallet | Wallet address, TXID, transaction evidence or exchange account proof. | Seed phrase, private key, recovery phrase, exchange password or wallet recovery file. | Whether TXID, address ownership, exchange account proof or source-of-funds record is required. |
| Bank statement | Name, address, bank name, issue date and relevant transaction if requested. | Unrelated transaction history, full account numbers or balances if not required. | Whether a PDF, screenshot, statement page or bank letter is accepted. |
| Source-of-funds evidence | Specific official record requested by portal or compliance team. | More tax, employment, bank or household information than requested. | Exact date range, page count, acceptable source and whether redaction is allowed. |
How to reduce preventable KYC document rejection
| Rejection reason | Why it happens | Fix before resubmitting | Do not do |
|---|---|---|---|
| Blurry, cropped or glare-covered image | Corners, face, document number or text cannot be read. | Retake in good lighting with all corners visible. | Do not artificially enhance or edit required data. |
| Expired document | ID or proof has passed valid/accepted date. | Use current accepted document type. | Do not alter expiry date. |
| Name, address or DOB mismatch | Account details and document details differ. | Ask support how to correct account details or provide matching evidence. | Do not create duplicate accounts to avoid mismatch. |
| Wrong document category | Payment proof submitted for address, or ID submitted for wallet ownership. | Match portal wording to request classifier. | Do not upload every document you have. |
| Wrong file type, page count or file size | Portal requires PDF, full statement, multiple pages or specific format. | Follow exact portal instructions. | Do not convert/edit files in a way that hides authenticity. |
| Redacted required field | Operator needed a field you covered. | Ask official support what must remain visible. | Do not reveal CVV, passwords, seed phrases, private keys or 2FA codes. |
Basic KYC vs source-of-funds or enhanced review
Some requests are not photo-quality problems. They are risk-review or payment-ownership questions.
| Request type | Typical trigger | What to save | Boundary |
|---|---|---|---|
| Basic identity / age | Account opening, withdrawal, legal-age or identity check. | ID request wording, upload receipt, confirmation and rejection reason. | Does not prove payment ownership or payout approval. |
| Address verification | Market/state, tax, residency or account profile check. | Proof category, issue date, portal wording and file submitted. | Does not prove source of funds. |
| Payment ownership | Card/e-wallet/bank route, withdrawal mismatch, duplicate payment method or refund review. | Payment descriptor, transaction ID, masked proof and support ticket. | Never expose CVV, full card number, passwords or 2FA codes. |
| Crypto wallet ownership | Crypto deposit/withdrawal, TXID mismatch, wallet ownership or exchange proof request. | TXID, asset, network, address, exchange receipt and request wording. | Never expose seed phrase, private key or recovery phrase. |
| Source of funds / source of wealth | Large, unusual, repeated, flagged or risk-reviewed activity. | Exact requested documents, date range, ticket ID and official response. | This page is not legal, tax, financial or AML advice. |
| Responsible-gambling review | Deposit pattern, affordability concern, cooling-off/self-exclusion/support signals or operator risk check. | Support message, account notice and responsible-gambling route offered. | Do not chase losses or keep depositing to fix verification. |
Records to save during KYC document verification
| Record | Why it matters | Save | Boundary |
|---|---|---|---|
| Portal request wording | Shows exact category requested. | Screenshot/PDF of message, date and account context. | Do not infer extra documents beyond request. |
| Upload confirmation | Shows you submitted a file through the portal. | Confirmation screen, timestamp, filename/category. | Confirmation is not approval. |
| Support ticket ID | Connects follow-up responses to the same case. | Ticket number, agent response, transcript/email. | Support answer can change; save date/time. |
| Rejection reason | Prevents random resubmission. | Exact rejection reason and requested fix. | Do not edit or falsify documents. |
| Payment/wallet transaction evidence | Needed for payment ownership or wallet proof. | Transaction ID, masked card/wallet proof, TXID, asset/network where relevant. | Never save/share seed phrase or private key. |
| Withdrawal or payout ID | Shows whether KYC is tied to a withdrawal. | Withdrawal request ID, amount, date, status and linked KYC message. | KYC completion does not guarantee payout approval. |
| Source checked | Shows current policy context. | Operator terms/privacy/KYC URL, date checked and relevant paragraph. | Published policy is not individual approval. |
KYC documents do not prove these things
| KYC documents do not prove... | Why | Use instead | Boundary |
|---|---|---|---|
| Operator legality or state availability | Document review is separate from state/legal status. | State guide and regulator/source checks. | KYC approval is not legal advice. |
| Withdrawal approval | Withdrawal can still depend on bonus terms, payment ownership, risk review and operator policy. | Withdrawal verification. | No payout guarantee. |
| Payment or wallet ownership | ID/address proof is not payment proof. | Payment verification. | Never expose CVV, seed phrase or private key. |
| Source-of-funds clearance | Source-of-funds review is separate and can be risk-based. | Official portal request and qualified guidance where needed. | Not financial, tax, AML or legal advice. |
| Privacy outcome | Uploading personal data creates data-handling risk. | Data protection. | This page does not audit operator privacy controls. |
| A no-KYC or offshore claim is safe | No-KYC marketing can still involve risk, withdrawal review or misleading claims. | Scam signs. | No no-KYC recommendation. |
| Gambling is under control | Verification stress can trigger chasing, debt or repeated deposits. | Help resources. | Use support if urgency or loss of control appears. |
Where to go next by KYC document problem
Use one exact owner route after the document problem is clear. This is not a generic KYC directory.
| Problem | Use this route | Why | Boundary |
|---|---|---|---|
| General KYC flow is unclear | KYC verification guide | Owns the full verification workflow. | General flow is not account approval. |
| ID photo, expiry, selfie or name/DOB issue | ID verification | Owns identity and age document checks. | ID does not prove payment ownership. |
| Address proof, recency or full-page issue | Proof of address | Owns address document requirements. | Address proof does not prove source of funds. |
| Card, bank, e-wallet or crypto wallet ownership | Payment verification | Owns payment/wallet evidence boundaries. | Never expose CVV, passwords, seed phrases or private keys. |
| Withdrawal is delayed because KYC is pending | Withdrawal verification | Owns payout/KYC workflow and records. | KYC completion does not guarantee payout. |
| Privacy, ID upload or document exposure risk | Data protection | Owns personal-data handling and privacy boundaries. | Privacy policy is not a safety guarantee. |
| Suspicious upload link or support impersonation | Phishing scams | Owns fake domain/support link checks. | Do not upload documents through unverified links. |
| You think documents were misused or scam pressure appears | Report scam concern | Owns evidence-first reporting route. | Reporting does not guarantee recovery. |
| Verification delay is triggering chasing, debt or secrecy | Help resources | Owns gambling-support route selection. | Support route is not KYC approval. |
Casino KYC document questions
What documents can a casino ask for during KYC?
A casino may ask for government ID, proof of address, payment ownership, bank/e-wallet proof, crypto wallet or TXID evidence, selfie/liveness checks, or source-of-funds documents. The exact request depends on the operator, market, payment route, withdrawal status and risk review.
Is ID enough to pass casino KYC?
Not always. ID can verify identity and age, but it does not prove address, payment ownership, wallet ownership, source of funds, bonus compliance or withdrawal approval.
Can I redact a bank statement for casino KYC?
Sometimes, but rules vary. Ask official support before redacting required fields. Do not expose unrelated transactions, full account numbers or balances unless the verified portal specifically requires them.
Should I send a casino a photo of my card?
Only through the verified operator portal if the request is legitimate and current. Never expose CVV, full card number, online banking login, passwords or one-time codes.
What is crypto wallet proof for casino KYC?
It may include a wallet address, TXID, exchange account evidence or transaction record requested by the portal. Never share a seed phrase, private key, recovery phrase or exchange password.
Why is a casino asking for source-of-funds documents?
Source-of-funds or source-of-wealth requests are usually enhanced/risk-based review, not basic photo-quality KYC. Submit only the official documents requested and save the ticket ID and date.
What should I do if a KYC document is rejected?
Read the rejection reason, identify the exact category, fix the specific issue, and resubmit only the requested document through the verified portal. Do not upload random extra documents.
Do KYC documents guarantee a withdrawal?
No. A verified document package can still be followed by payment ownership checks, bonus review, source-of-funds review, responsible-gambling review or withdrawal policy checks.
What if support sends an upload link by email, chat or social media?
Pause and verify the route inside the official account portal or official support channel. Do not upload ID, bank statements, card photos or wallet proof through unverified links.
Page update notes
Reviewed casino KYC document categories, request classification, safe upload and redaction boundaries, source-of-funds and enhanced-review distinctions, rejection-risk fixes, evidence records, source snapshot rows, FAQ wording and responsible-gambling footer routing.