KYC on withdrawal

1) KYC output task

KYC on withdrawal (withdrawal KYC) is a control point where the platform verifies that funds are being sent to the real account holder and the legitimate recipient, and transactions do not violate AML/sanction/bonus policy requirements. The goal is to reduce the risks of fraud, chargebacks, laundering and regulatory claims with minimal friction for honest players.

2) Basic principles

Necessity and proportionality: we ask only what is needed at this threshold of risk.
Verifiability: any solution relies on artifacts (documents, logs, scoring).
Transparency for the user: clear reasons, understandable list of documents, ETA, visible status.
Same-person/same-method: account holder name = payment method holder name; return to source if possible.
Impartiality: no discrimination; decisions - on facts, and not on origin/nationality (except for sanctions by law).

3) KYC trigger matrix on output

MinThreshold/Daily/Weekly thresholds are configured by geo and risk policy.

4) Packages of documents

4. 1 Basic (L1)

Color document: passport/ID/driver's license (country/term/series).
Selfie/live check (liveness) on request.
Proof of address ≤90 days: utility bill/statement/tax letter.

4. 2 Extended (L2)

Recalibrate L1 + current address (if older than 90 days).
Sanctions/PEP screening with manual confirmation.

• cards - masked card + bank statement/screen with full name;
• bank - Internet bank screen with full name and IBAN/ABA;
• e-wallet - profile screen with full name/ID;
• crypto - screen of the exchange aka with full name, wallet address in history.

4. 3 SoF/SoW (by risk)

SoF (Source of Funds): income/salary statement, deposit statement, dividends, sale agreement.
SoW (State Origin): tax returns/bank statements (rarely requested - with large and regular amounts/signals).

5) Sanctions/PEP: minimum standard

Screening at: registration, first deposit/withdrawal, change of personal data/payment, periodically (for example, once every 30-90 days).
Matches "by sound" (fuzzy) are always checked by a person.
If a match is confirmed, a compliance decision (allow/restrict/close) with logging of reasons.

6) KYC payment rules

1. Withdrawal rights arise in the absence of an active vager/bonus debt and successful checks.
2. Same-method: transfer to the replenishment source; if impossible (technically/limits/closed method) - an alternative method, but in the name of the user.
3. Name mismatch → confirmation request/refusal.
4. Third parties/wallets in other names are prohibited.
5. Crypto: only to the verified address of the user/exchange; ban mixers/anonymizers.

7) Process and SLA (sample model)

• A) Withdrawal Request → B) Auto Screening (CCR/Sanction/Fraud) → C) Docs (if required) → D) Moderation → E) Send to Payment Channel → F) Complete.

• Q0 Auto (net profiles, small amounts): up to 1-6 hours.
• Q1 Accelerated manual (VIP/newly confirmed payment): up to 24 hours
• Q2 Standard manual (new accounts/methods): up to 48 hours
• Q3 Investigation (SoF/disputes/sanctions): up to 3-7 employees. days after receipt of documents.

Account statuses: Under review → Need documents → In progress → Sent → Completed/Denied + visible ETA.

8) UX transparency (which must be on the Output page)

Clear KYC requirements and list of documents prior to bid confirmation.

ETA and queue policy; by methods - "usually X-Y hours/days."

Link "How to speed up verification" (checklist of photo/scan quality, what exactly is needed according to the method).
Decision history: who/when requested the document, what was checked, the result.
Visual correspondence between the name on the payment and the account name (hint "must match").

9) Frequent cases and politics

K1. Active bonus/outstanding WR → notify, show WR balance/deadline; allow cancellation of the bonus (with cancellation of bonus winnings) and withdraw Cash.

K2. New card in another name → refusal or request for evidence of legal possession; generally a ban.

K3. Crypto withdrawal to the address of a friend/third party → refusal; offer to verify the user's personal address/exchange.

K4. Sanctions match → manual check; at confirmation - block/closing according to the law and conditions.

K5. Chargeback on deposit → hold balance until resolution; after loss of dispute - settlement/limitation.

K6. No response to the request for documents (7-14 days) → cancellation of the application/refusal with the right to resubmit if there are documents.

10) Roles and responsibilities

Support (L1): informs, collects documents, checks format/quality.
Moderation/Risk (L2): checks the ownership of the payment, analyzes the fraud signals, recommends SoF/SoW.
Compliance (L3): sanctions/PEP, disputes, final decisions.
Payment team: routing, contacts with PSP/banks, monitoring TtW/failures.
DPO/Privacy: storage and access to documents, DPIA of high-risk streams (biometrics/anti-fraud).

11) Data storage and protection

Timing: KYC/AML and transactions - by law (often 5-10 years), SoF/SoW - by risk assessment (usually 2-5 years).
Rest/transmit encryption, RBAC/ABAC, access logging, annual audits.
Minimizing copies of documents, masking sensitive parts (maps - 6 + 4).

12) Quality metrics

Time-to-Wallet (p50/p95) by method/queue.
Approval Rate of withdrawal requests.
Share of auto payments (without manual moderation).
Repeated document requests (%).
SLA breach% (overdue applications).
Dispute/Chargeback Rate and Win-Rate on disputes.

13) Pre-market checklist

• KYC/SoF/SoW thresholds and triggers published.
• Describes valid methods and the same-method rule.
• You have set up statuses/ETA and the How to Speed Up Verification page.
• Ready email templates and macros for support (see below).
• Decision logs and export for audit/regulator.
• DPIA conducted for biometrics/antifraud, DPA agreed with providers.

14) Communication templates

A. Request basic documents (L1)

Subject: Identity verification required for output

• Hello, [Name]!

1. document (passport/ID) - color copy;

2. selfie/live check (according to the instructions in the office);

3. address confirmation (≤90 days).

Once the files are uploaded, we will continue to review. ETA after receipt - up to [X] hours. Thanks!

B. Confirmation of the payment method (Ownership)

Subject: Confirm that the payment method belongs to you

• Hello, [Name]!
• To display on [method], please upload a screen/extract with your full name and details. For the card - a photo of the front side (mask the numbers - leave the first 6 and the last 4). ETA after confirmation - up to [X] hours.

C. SoF request

Subject: I need a document confirming the source of funds

• Hello, [Name]!
• AML internal rules require us to confirm the source of the withdrawal [amount]. Suitable: income/salary statement, bank statement with incoming payments, sales document, etc. After loading ETA - up to [X] working days.

D. Refusal decision (clear reason + appeal)

Topic: Withdrawal Request Decision

• Hello, [Name].
• Unfortunately, we cannot conclude [amount], reason: [specifically - mismatch of full name/lack of documents/sanctions, etc.].
• You can appeal the decision by sending documents/explanations to [channel]. The appeal period is [X] days.

15) Mini FAQ for players

Why KYC in output? So we confirm that we send money to you and comply with the law.
How much does it take? Usually from minutes to 24-48 hours, if the documents are correct.
Why are they asking for SoF? Only at increased risk/large amounts is an AML requirement.
Can I withdraw to someone else's wallet? No, only for methods designed for you.
What will speed up verification? Clear photos/scans, a fresh document at the address, a screen of payment with your name.

16) Short section template for your Policies

key> KYC on output. Before sending funds, the Platform can conduct identity checks (ID/selfie), address, sanctions/POP, as well as request confirmation of ownership of the payment method and, if necessary, SoF/SoW documents. The conclusion is possible only on methods designed for the User (the same-method rule is applicable if possible). In the absence of requested documents or with reasonable fraud/AML risks, the application may be suspended or rejected with notice and right of appeal.

How to use this article

1. Insert your thresholds, ETAs, and document listings into the letter templates and interface.
2. Configure escalation queues/rules and TtW/Approval Rate metrics.
3. Align sections with Pay & Verify Policy, Bonus Rules, User Agreement, and Privacy.
4. Conduct support training: macros, checklists, case examples and correct wording of the reasons.