Operatsiyalar va Komplayens → Mablag’manbasini tekshirish

Manbani tekshirish (SoF/SoW)

1) SoF va SoW nima va nima uchun kerak

SoF (Source of Funds) - pul o’yin/depozit/olib qo’yish uchun kelib tushganligining hujjatli tasdig’i.
SoW (Source of Wealth) - o’yinchining umumiy holati (aktivlar/passivlar/daromadlar) qanday shakllanganligini tushuntirish.

Maqsadlar: litsenziyalar va to’lov sheriklari talablariga rioya qilish, yuvish va firibgarlik xavfini kamaytirish, himoyaga muhtoj o’yinchilarni (RG) himoya qilish va dalillar bazasini shakllantirish.

2) SoF/SoW prinsiplari

1. Risk-Based Approach: tekshirish chuqurligi geo/to’lov usuli/summa/patternlarga bog’liq.
2. Proportionality: Biz faqat kerakli hujjatlar to’plamini so’raymiz.
3. Evidence-by-Design: har bir qaror artefaktlar va trassalar bilan birga keladi.
4. Timeliness & Fairness: shaffof muddatlar (ETA), hujjatlarga qo’yiladigan tushunarli talablar, hurmatli ohangda.
5. Privacy-first: PD minimallashtirish, shifrlash, cheklangan kirish va retenshn.

3) SoF/SoW (triggerlar) ni qachon so’rash

Moliyaviy chegaralar: yakka tartibdagi ≥ X, jami depozitlar/aylanma N kun uchun ≥ Y.
Tavakkalchilik patternlari: velocity/strukturalash, multiple payment instruments, cash-like usullari.
O’yindagi xatti-harakatlar: kam daromadli yuqori aylanma, «naqd pul» (minimal xavf/minimal vaqt).
Profil voqealari: VIP/limitlarni oshirish, to’lov rekvizitlarini o’zgartirish, geo/RER/advers-media high-risk.
To’lov hodisalari: chargeback/qaytarish/mablag’egasi tafovutlari.

4) Dalil sifatida nima qabul qilinadi (misollar)

• Ish haqi: ish beruvchining ma’lumotnomasi/3-6 oylik ko’chirma/soliq shakli.
• O’zini o’zi band qilish/biznes: soliq deklaratsiyalari, shartnomalar, biznes hisobvarag’i bo’yicha bank ko’chirmalari.
• Investitsiyalar: brokerlik ko’chirmalari, dividendlar, kuponlar.
• Aktivlarni sotish: oldi-sotdi shartnomasi + hisobvaraqqa tushum.
• Meros/sovg’a: notarial hujjatlar + bank tasdig’i.
• Kripto-daromad: birja/kastodian hisobotlari, tx-tarix, fiat kesh-aut.

Hujjatlarga qo’yiladigan talablar: o’qish qobiliyati, rekvizitlarning to’liqligi, N oydan katta bo’lmagan sana, summalarni platforma bo’ylab harakatlanish bilan bog’laydigan F.I.O./manzilning mos kelishi.

5) SoF/SoW siyosati (karkas)

yaml policy_id: SOF-POL-001 scope: players rba:
low:  {geo: "trusted", methods: ["bank_transfer"], monthly_turnover_max: 1000}
medium:{geo: "mixed",  methods: ["cards","wallet"], monthly_turnover_max: 10000}
high: {geo: "high_risk" OR pep==true OR crypto_usage==true}
triggers:
- single_payout >= 3000
- rolling_deposits_30d >= 5000
- payout_destination_change == true
- aml_flags in {velocity, structuring, srcdst_mismatch}
required_evidence:
low:  [salary_stub OR bank_statement]
medium: [bank_statement_3m, employer_letter OR tax_return]
high:  [tax_return, bank_statement_6m, source_of_wealth_summary]
decisions:
approve:  sof_consistent==true request:  need_additional_docs==true decline:  inconsistencies OR unverifiable_sources review_sla_days: 180 owner: mlro

6) Controls-as-Code (parchalar)

yaml control_id: SOF-PAYOUT-GATE scope: payouts trigger:
expr: (payout_amount >= sof_threshold[country]) OR risk_band>=high actions:
- block: payout
- request: "sof_package"
- notify: aml_ops evidence:
fields: [player_id, payout_amount, risk_band, country, thresholds_version]

yaml control_id: SOF-SRC-TO-SRC scope: payouts trigger:
expr: payout_destination!= last_successful_deposit_source actions:
- limit: payout "require_same_source"
- request: "proof_of_ownership_for_destination"
exceptions:
- condition: method_type=="bank_transfer" AND policy. allow_bank_payouts==true

yaml control_id: SOF-CRYPTO-CASHOUT scope: payouts trigger:
expr: crypto_usage==true AND fiat_payout>=crypto_threshold actions:
- request: ["exchange_account_statement","tx_history","proof_of_fiat_offramp"]
- flag: aml_review

yaml control_id: SOF-RISK-SCORE inputs: [velocity, structuring, srcdst_mismatch, sanctions, pep, adverse_media]
score:
expr: 0. 25velocity + 0. 2structuring + 0. 2srcdst + 0. 2pep + 0. 1adverse + 0. 05geo thresholds:
- high:  score>=0. 8 -> KYC3_EDD + full_SoW
- medium: score>=0. 5 -> targeted_SoF
- low:  auto_clear

7) Jarayon (SOP) - keysning hayot sikli

SOP: SoF soʻrovi

1. Nazorat bo’yicha avtogeyt → sabablari va talab qilinadigan hujjatlar ro’yxati bilan keys yaratish.
2. Oʻyinchiga/chat orqali xat yuborish: hujjatlar roʻyxati, format, muddat, javob ETA.
3. Eslatmalar: T + 48 soat, T + 96 soat; javob bo’lmaganda - xulosani cheklash.

SOP: Hujjatlarni tahlil qilish

1. Ism/manzil/IBAN va summalarni profil/tranzaksiyalar bilan taqqoslash.
2. Vaqt doirasini (davrlar qamrovini), tushumlarning muntazamligini, nomuvofiqliklarni tekshirish.
3. Zarurat bo’lganda - qo’shimcha dalillar/tushuntirishlar so’rash.
4. Qaror qabul qilish:’approve/ request_more/decline’, asosni hujjatlashtirish.

SOP: Yechim va kommunikatsiyalar

1. ’approve’ uchun - blokirovkani olib tashlash, auditning evidence, logiga havolani qayd etish.
2. ’decline’ uchun - sababini/havolalarini qayd etish, AML/Compliance ni xabardor qilish, SAR/STRni ko’rib chiqish.
3. Xavf profilini va keysning taymline qismini yangilash, keysni yakuniy maqom bilan yopish.

SOP: Qayta tekshirish

Hodisa bo’yicha (yangi chegaralar/rekvizitlarning o’zgarishi/VIP/PEP) yoki SLA bo’yicha (masalan, high-risk uchun har 12 oyda bir marta).

8) Ma’lumotlarni integratsiyalash

KYC/KYB: tekshirish darajalari va mablag’egasi rekvizitlarining mos kelishi.
Payments: depozitlar/kreditlar tarixi, kartalar/IBAN/hamyonlar, chargeback.
AML: velocity/tuzilish/sanksiyalar/PEP/advers-media.
Case-tool: statuslar, muddatlar, kommunikatsiyalar, SLA va eksport SAR/STR.
DWH/BI: SoF vitrinalari, konsistentsiyani nazorat qilish, hisobot berish.

9) Maxfiylik, xavfsizlik, retenshn

Minimallashtirish: Biz faqat tegishli sahifalarni/maydonlarni soʻraymiz.
RBAC/ABAC: hujjatlardan foydalanish faqat AML/Compliance’da; suv belgilari/vaqtinchalik havolalar.
Shifrlash: at rest/in transit; kalitlar - HSM/Vault.
Retenshn: yurisdiksiya bo’yicha saqlash (odatda oxirgi operatsiyadan keyin 5 yil ≥) va olib tashlash siyosati.
Audit: har bir o’qish/qaror jurnalga olinadi.

10) Sifat va metrika (KPI/OKR)

• SoF Case Time-to-Triage (P95), Decision TAT (median), Hold Duration.
• Completion Rate (to’liq paketli keyslar ulushi), Re-request Rate.

• Approval/Decline/Escalation Share, SAR/STR on SoF (tasdiqlangan holatlar bo’yicha).
• Mismatch Rate, False Negative/Positive proxy.

• SoF Drop-off, CSAT kommunikatsiyalar bo’yicha, muddatlar/tushunarli talablar ustidan shikoyatlar.

• Chargeback/Fraud Loss ↓, SoF dan keyin MTTR to’lovlari ↓, Evidence Completeness ≥ 98%.

11) Shablonlar (parchalar)

yaml case_id: SOF-2025-1042 player_id: P-887231 risk_band: high reason: ["payout>=3000","srcdst_mismatch"]
requested_docs: ["bank_statement_6m","tax_return","employment_letter"]
deadline: "2025-11-08T23:59:00Z"
status: awaiting_docs  # triage    awaiting_docs    review    approved    declined    sar_submitted analyst: aml. ops@domain notes: []
evidence_uri: s3://sof-evidence/P-887231/2025-11/

- Name/address/details match?
- Does the statement period cover turnover?
- Is the regularity of income confirmed?
- Do sums and frequencies correspond to dep/conclusions?
- No obvious edits/anomalies?
- Result: approve/ request_more/decline (justification)

Subject: Additional confirmation of the source of funds
Hello, <Name>! For a secure withdrawal, we need documents:
Bank statement for the last 3-6 months (PDF/scan)
Income confirmation (certificate/tax form)
Please upload files by <date>. Funds are reserved, the status of payments will be updated immediately after verification. If you have any questions, please reply to this email.

12) Alohida holatlar

Kriptovalyuta: birja/kastodian hisobotlarini talab qiling, on-chain va off-rampni solishtiring, o’z-o’zidan hisobot bergan hamyon skrininglaridan qoching.
Kesh/naqd pul: faqat qonuniy hujjatlar (sotish, hadya qilish, meros) va bank hisobi mavjud bo’lganda yo’l qo’yiladi.
Sovg’alar/uchinchi shaxslar: jo’natuvchining manbasini tasdiqlash + tasarruf etish huquqi; yuqori xavf.
PEP/RCA: har doim EDD va kengaytirilgan monitoring.

13) Anti-patternlar

RBA → yuqori drop-off bo’lmagan barcha keyslar uchun universal «qalin» paket.
«Muddatsiz» va aniq kommunikatsiyasiz blokirovka qilish.
Asl nusxa/tekshirilayotgan PDF/ko’chirmalar o’rniga skrinshotlarni qabul qilish.
To’lovlar (source-to-source) va AML-signallar bilan tutashtirishning yo’qligi.
Haqiqatning ikkita versiyasi: pochtadagi qarorlar, DWHdagi ma’lumotlar - umumiy SSOTsiz.
Ishlarni qayta baholash yo’q, chegaralar qayta ko’rib chiqilmaydi.

14) 30/60/90 - joriy etish rejasi

• SOF-POL-001 (triggerlar, chegaralar, RBA) tasdiqlansin,’SOF-PAYOUT-GATE’va’SOF-SRC-TO-SRC’kiritilsin.
• Keys-menejment, xat shablonlari va chek varaqlarini, evidence-omborni ulash.
• SoF Overview dashbordlarini moslash.

• ’SOF-CRYPTO-CASHOUT’ va agregator’SOF-RISK-SCORE’, country-overrides qo’shing.
• KYC/KYB/Payments (owner-match, IBAN/karta/hamyon) va toʻlov avtopauzalarini integratsiyalash.
• FPs bo’yicha retro keyslarni sifat/auditdan o’tkazish.

• Evidence ≥ 98% ga erishish, Decision TAT va Hold Duration ni maqsadli
• KPI SoF ni OKR AML/Payments/Support bilan bogʻlash, dizayn va nazorat samaradorligi boʻyicha ichki audit oʻtkazish.
• Tashqi/tartibga soluvchi hisobotlar va chegaralarni davriy qayta ko’rib chiqish metodologiyasini tayyorlash.

15) FAQ

Q: SoF SoW’siz qachon yetarli?
A: bir martalik yoki mo’tadil ostonalar uchun. SoW sizga VIP/PEP/high-risk kerak, uzoq vaqt davomida yuqori aylanish yoki aniq mos kelmaslik holatlarida.

Q: Boshqa hisob raqamiga to’lash mumkinmi?
A: Faqat mulk huquqi tasdiqlangan va qo’shimcha tekshirishlar o’tkazilganda; afzalroq - «source-to-source».

Q: Summalar nomuvofiq bo’lsa nima qilish kerak?
A: Kengaytirilgan ko’chirmalar/tushuntirishlarni so’rash, tanqidiy tafovutlarda - decline va SAR/STR ko’rib chiqish.

Q: Futbolchiga yukni qanday kamaytirish mumkin?
A: Aniq talablar, yo’l qo’yiladigan hujjatlar namunasi, himoyalangan yuklash, qisman avtoto’ldirish va oqilona muddatlar.