KYC and AML checks
Know Your Customer checks verify the identity behind an account. Anti-money-laundering controls look for prohibited use of financial systems. Platforms may run these checks during registration, deposits, cash entry, redemptions, or withdrawals, or after detecting a risk signal.
Information commonly checked
Section titled “Information commonly checked”- legal name, date of birth, and residential address;
- Social Security number or a permitted portion of it;
- phone and email ownership;
- government-issued photo identification;
- a live selfie or liveness check;
- payment-method ownership;
- bank statement or address evidence;
- physical location when cash play is requested.
The exact request depends on the platform model and applicable rules. The platform may ask for more information after reviewing the first document.
A safe verification process
Section titled “A safe verification process”- Confirm the domain or app publisher through an official regulator listing, platform site, or app store publisher page.
- Open verification from the authenticated account, not a link in an unsolicited message.
- Read why the data is requested and how it is handled.
- Upload only the requested pages through the secure form.
- Make sure the image is current, complete, legible, and not altered.
- Save the case or upload reference without storing identity documents in a shared folder.
- Delete unnecessary local copies after the platform confirms receipt, subject to your record needs.
Do not email a password, one-time code, full card security code, or remote-access credentials.
Common mismatch fixes
Section titled “Common mismatch fixes”| Problem | Safer response |
|---|---|
| Nickname differs from ID | Ask support to update the account to the legal name |
| Recent move | Submit the accepted current-address document listed by the platform |
| Blurry or cropped image | Retake all requested sides in good light with every edge visible |
| Payment method belongs to another person | Stop using it and ask how to resolve the deposit |
| Duplicate account | Disclose it to support rather than creating another account |
| Location check fails | Enable required permissions and contact support, without using a VPN workaround |
Why verification may recur
Section titled “Why verification may recur”Documents expire, addresses change, payment sources change, and risk controls can flag unusual activity. Licensed operators also have ongoing compliance duties. A repeat request is not by itself proof of a scam, but it should still arrive through a verified channel.
Red flags
Section titled “Red flags”Stop if a supposed agent asks for gift cards, cryptocurrency sent to a personal address, a fee paid outside the cashier, screen sharing into a bank account, or a fabricated document. A legitimate review can restrict the account while it checks information. It should not require falsifying it.
The Federal Trade Commission’s impersonator scam guidance explains common payment and identity warning signs.
When an AML review starts
Section titled “When an AML review starts”A platform’s risk model is not public, but review can follow unusual transaction size or frequency, rapid deposit and withdrawal activity with little play, inconsistent identity details, multiple payment owners, chargebacks, linked accounts, location anomalies, or attempted limit avoidance.
A review does not prove wrongdoing. It can pause transactions while the operator checks an explanation and records. It is different from a game’s fairness review or an ordinary password check.
Possible financial-record requests
Section titled “Possible financial-record requests”Depending on the operator and circumstances, support may request:
- proof that the player owns a bank account, card, or wallet;
- transaction statements;
- an explanation of account activity;
- source-of-funds or source-of-wealth evidence;
- information about linked accounts or devices;
- updated tax identification details.
Use the secure upload route and redact only what the platform says may be redacted. An altered or selectively edited record can extend the review.
Do not structure transactions
Section titled “Do not structure transactions”Breaking one transaction into smaller amounts to evade a reporting threshold or control is not a safe workaround. Do not rotate wallets, use another person’s identity, create duplicate accounts, or misstate the source of money.
The Financial Crimes Enforcement Network publishes US AML information. Specific obligations differ across casinos, financial institutions, contest platforms, and sweepstakes operators, so avoid applying one casino reporting rule to every product.
Responding to a hold
Section titled “Responding to a hold”- Read the message in the authenticated account.
- Confirm the case number and requested documents through official support.
- Ask for a secure upload link if one is not provided.
- Answer accurately and keep copies of submissions and dates.
- Request status after the stated review period, not through multiple new tickets.
- Preserve withdrawal and transaction records if a formal complaint becomes necessary.
Support may not reveal internal detection logic or whether a report was filed. That limitation does not permit an operator to invent a fee for releasing funds. Treat any off-platform “clearance payment” as a scam signal.
AML records and privacy
Section titled “AML records and privacy”Sensitive financial records deserve careful handling. Check the operator’s privacy policy, retention terms, and contact route. Use a unique password and multifactor authentication where available. Do not upload documents over public chat or to an unverified cloud folder.