HK VASP Onboarding: Hot Wallet & Source-of-Fund Matrix
HK VASP Onboarding: Hot Wallet & Source-of-Fund Matrix
If you run onboarding at a Hong Kong VASP, two things will make or break your approval rates in 2025: how you treat hot wallets and how you evidence source of funds (SoF). Get those right, and most of your “borderline” cases turn into clean passes without bloating your false-positive queue.
What’s changed (and why it matters)
- HKMA’s stablecoin consultation conclusions underline a wallet-risk approach: if a customer’s wallet is custodial, perform due diligence on the FI/VASP providing it; for unhosted wallets, add extra controls. When you cannot complete satisfactory due diligence, you must screen the addresses with appropriate tech and mitigate higher ML/TF risk. See HKMA’s consultation materials and conclusions.
- The SFC’s AML/CFT Guideline for VASPs expects ongoing wallet screening, Travel Rule implementation where applicable, and risk-based onboarding. Put simply: custodial ≠ automatically safe; unhosted ≠ automatically banned. But the control stack must differ.
A practical wallet onboarding risk matrix Use this as a starting point for your internal playbook.
| Wallet Type | Examples | Inherent Risk | Required Checks | Decision Guide |
|---|---|---|---|---|
| Custodial wallet at regulated FI/VASP | SFC-licensed platform, major FI | Medium | KYB on provider (licence, jurisdiction, sanctions posture), confirm account ownership, Travel Rule data match, address screening | Approve if provider DD is satisfactory and screening is clean |
| Custodial wallet at non-AML‑regulated provider | Offshore app with unclear licensing | High | Enhanced DD on provider (corporate docs, AML policy, audit/assurance if any), attestations; address screening | Approve only with strong mitigants or limit functionality; otherwise decline |
| Unhosted/self-custody (user-controlled) | Ledger, MetaMask | High | Proof-of-control signing (message or micro-txn), clustering and on-chain provenance for 12–24 months, sanctions/typology screening, whitelist-only withdrawals | Approve with EDD and stricter limits; decline if taint > “moderate” |
| FI/VASP omnibus wallet (stablecoin redemption) | Institutional custodians | Medium–High | KYB on institution; chain analysis of omnibus flows; test redemption pathway | Approve if counterpart’s AML/supervision status is validated and flows are explainable |

Note: Where DD cannot be performed to a satisfactory level or the wallet is unhosted, screen the wallet addresses with appropriate technology and apply additional mitigants (limits, manual review). This aligns with HKMA’s stated approach for stablecoin-related wallets.
Hot wallet policy that actually reduces loss and alerts noise
- Cap exposure: Hold 3–10% of user assets in hot wallets; move the rest to warm/cold with automated sweep rules.
- Real-time blocklist and typology screening: Sanctions, ransomware, darknet markets, high-risk mixers, cross-chain bridges, and sanctioned nexus heuristics.
- Stablecoin-specific checks: Monitor issuer blacklisting events (e.g., freeze lists) and centralized redemption addresses; maintain per-issuer exposure caps.
- Withdrawal controls: Velocity rules (e.g., step-up checks beyond HKD [illustrative] 200k/day), first-withdrawal cooling-off, address whitelisting, and proof-of-control for external destinations.
Source-of-fund verification matrix (what to accept, and how)
| SoF Type | Documents | On-chain Evidence | Risk Notes |
|---|---|---|---|
| Salary via HK bank | Last 3–6 months bank statements; employment contract | N/A | Low; reconcile fiat in-flow to VA purchase records |
| Corporate dividends / founder proceeds | Board resolution, audited FS, bank advices | N/A | Medium; ensure beneficial ownership traceability |
| Regulated exchange withdrawals | Account statement/export; exchange confirmation | Tx hash to/from exchange clusters | Low–Medium; check exchange licence/jurisdiction |
| OTC brokered trades | Invoice, broker licence/registration, trade chat transcript | Tx hash; broker cluster attribution | Medium–High; reject cash-heavy or unlicensed OTCs |
| Long-held self-custody | N/A | Full wallet history; age-of-funds; taint score; clustering | Medium; require signing proof and narrative of acquisition |
| DeFi yields / staking | Protocol statements, wallet screenshots | Reward flows by protocol; LP/NFT positions | High variance; watch for mixer/bridge adjacency |
| Mining proceeds | Equipment receipts, electricity bills, pool payouts | Payout addresses to pool clusters | Medium; geographic sanctions risk check |
Operationalise this in 30 days
- Build decision trees: Codify the matrix into your case management tool with pass/EDD/decline branches.
- Calibrate thresholds: Use a 3-tier taint model (clean / moderate / elevated) tied to limits and senior approvals.
- Close the Travel Rule gap: Integrate a TR provider; auto-reject incomplete originator/beneficiary data where required.
- Evidence everything: Store provider DD packs, signing proofs, and screening snapshots in the case file. Auditors will ask.
The goal isn’t zero risk. It’s documented, defensible risk.
References:
- HKMA stablecoin AML/CFT consultation conclusions (wallet risk and unhosted wallet controls)
- SFC Guideline on Anti-Money Laundering and Counter-Financing of Terrorism for VASPs
If you need a second pair of eyes on your matrices or want a quick gap review against current HK expectations, StanCOMP can usually turn around a practical checklist within five working days.


