Source of Funds / Source of Wealth

1) SoF vs SoW: what's the difference and why is it iGaming

Source of Funds (SoF) - the direct source of a specific transaction/deposit or series of deposits: salary for the period, sale of an asset, dividends, winnings, transfer from a personal account, etc.
Source of Wealth (SoW) - the source of the client's general condition: how his capital is formed as a whole (business income, savings over years, inheritance, etc.). SoW is required at high/PEP/EDD limits.

In iGaming, SoF/SoW reduces AML risks (placement/layering), reputational (banks/PSP), and also accelerates conclusions for honest players through a pre-loaded "dossier."

2) When to ask (triggers)

• One-time deposit/withdrawal ≥ the T₁ threshold (by jurisdiction) or total deposits ≥ T₂ for 30/90 days.
• Abnormal dynamics: fast deposit → short activity → large output (rapid in-out).
• Risk factors: PEP/adverse media, high-risk geo, crypto on/off ramp, previously noticed AML alerts.
• Profile inconsistency: reported revenue vs actual turnover.
• Escalation: at the request of the bank/PSP/regulator, during investigation cases.

Rule: the minimum possible amount of progressive → request.

3) What documents are suitable (catalog with "strength" of evidence)

3. 1 Salary/labor income (strong)

Bank statement for 3-6 months with salary credits (full name of the client).
Income statement/tax form (country-specific).

HR Contract/Formal Letter (if required)

3. 2 Self-employed/freelance/PI (medium/strong)

Bank statements for 6-12 months with regular receipts, invoices/acts.
Tax returns/entrepreneur registration, site/portfolio as indirect confirmation.

3. 3 Business income/dividend (strong)

Owner account statements, board decisions/dividend payments, contracts.
Financial statements/audited reports (at large amounts).

3. 4 Asset Sales (Strong)

Purchase and sale agreement (real estate/auto/securities) + statement of credit.
Brokerage reports/profit taking.

3. 5 Inheritance/gift (medium)

Notarial documents/gift + credit statement.
With large amounts - confirmation of origin from the donor (by risk).

3. 6 Investment income/crypto (variable)

Broker/exchange: transaction report, confirmation of withdrawal to a personal account, KYC status of the exchange.
Crypto: KYT report on addresses/transactions, proof of wallet ownership (message sign/UI screen with address and UID), tracing of input funds, conversion on a regulated exchange.

3. 7 Cache (weak, use carefully)

Cash orders/certificates - only in combination with bank credits and context.

4) Authentication and comparability

Formal check: completeness of details, dates, full name/address, coincidence with KYC profile.
Comparability of amounts: rule 3 × - 6 × month income as a "reasonable limit" of turnover (set by policy).
Temporary proximity: crediting funds to the bank/exchange within N days before the deposit/withdrawal.
Authenticity: checks for edits (PDF metadata, digital stamps), return requests (bank letter), provider webhooks (exchanges/brokers).
Crypto: correspondence of addresses, lack of connections with mixers/sanctions clusters; white-list regulated exchanges.

5) Solution matrix (example for orchestrator)

6) SLA and prioritization

Request/submission of documents: auto-letter + office → client response up to 72 hours (configurable).
Check SoF (auto/manual): ≤ 24 h p95; with high-rollers/block for output - ≤ 8 hours.
EDD by SoW: 2-5 business days depending on volume.
Communication: every 24 hours status update, transparent requirements, acceptable formats.

7) UX query templates (so as not to break the conversion)

Clear checklist: "select source type" → dynamic form (salary/business/sale/crypto).
Examples of correct documents by country, tips for masking sensitive fields (residuals, numbers).
Preview and validation: readability, ≤ date 90/180 days, file size.
Secure Download - End-to-end Encryption, Received/Under Review/Approved.
With controversial cases - call/video-KYC as an accelerator.

8) Special scenarios

8. 1 Crypto on/off-ramp

Accepted: exchange/transaction reports, KYT-assessment of addresses, proof of ownership.
Cut off: P2P without KYC, high-risk exchange, chains through mixers.
Conversion: withdrawal is better after conversion on a regulated exchange → a personal bank.

8. 2 Self-employed/creators/arbitrage

Stabilization: aggregate invoice revenues + receipts from payment platforms (PayPal/Stripe/Adsense, etc.).
Permissible: contracts/screenshots of offices as auxiliary, but the solution is for bank credits.

8. 3 Inheritance/gifts

Ask for notarial documents + bank transfer confirmations; with large amounts - SoF of the donor.

9) Data and privacy (GDPR/PCI/security)

Minimization: keep only the necessary pages/fields; close balances/account numbers if not required.
Encryption: at rest (KMS/HSM) and in transit; access - RBAC, activity logs.
Retention: retention period according to law (often 5 + years after the last operation) and policy; After - delete/anonymize.
DSR/Entitlement: Copy/Delete processes where possible.
PCI DSS: SoF/SoW storage separated from payment PANs; in logs - only/last4 tokens.

10) Integration with KYC/KYB/AML/Payments

KYC: SoF signals increase confidence in scoring, reduce the frequency of 3DS challenges.
KYB (affiliates/merchants): Request SoF/SoW from UBO for large payouts/shares in the company.
AML: Rapid In-Out/Structuring triggers → SoF request; positive SoF can close alert.
Payments Orchestrator: automatic hold/partial release prior to verification.

11) Quality metrics

SoF pass rate, SLA hit rate, average approval time.
Share of EDD cases and their win-rate (success of confirmation).
Number of cancellations/failures due to SoF/SoW and their contribution to CBR/AML incidents.
Repeated requests for one player (reduce due to the "dossier").
Impact on conversion of conclusions: how many conclusions are accelerated after pre-approval of SoF.

12) Anti-patterns

Require SoW for every small operation - kills UX without security growth.
Accept screenshots without a bank statement as the main SoF.
Ignore temporal connectivity: "year old" documents for a large current output.
"Deaf" failure without alternatives: do not offer partial release/step-by-step SoF.
Store redundant PII/documents without goals and retention plans.

13) Implementation checklist (short)

• T₁/T₂ threshold policy, SoF/SoW trigger map.
• Directory of valid documents + fittings by country/language.
• Auto-request process and download cabinet, secure storage, RBAC.
• Decision Matrix (Approve/Conditional/EDD/Freeze) and letter templates.
• KYT integration for crypto, white-list exchanges.
• SLA: SoF ≤ 24 h, EDD ≤ 2-5 days; prioritization of high-rollers/blocks per output.
• Audit logs, versioning decisions, retention/deletion.
• Metrics dashboards and monthly case retrospective.
• Support/compliance training; "partial release" playbooks and escalations.
• Link to AML/Payments: automatic hold/limits before confirmation.

14) Summary

An efficient SoF/SoW process is adequate triggers, sufficient documents, authentication and amount connectivity, reasonable SLAs, and transparent UX. Connect him with a KYC/KYB/AML/payment orchestrator, keep your data safe, and "be mindful of the goal" of letting bona fide players through quickly and stopping risky scenarios without too much friction.