HK VASP Compliance: Cold Wallet EDD & KYT Guide
HK VASP Compliance: Cold Wallet EDD & KYT Guide
If you’re a Hong Kong VASP facing cold wallet deposits, redemptions, or withdrawals (especially in stablecoins), the hard part isn’t custody. It’s proving you’ve done enough Enhanced Due Diligence (EDD) and ongoing KYT to satisfy the SFC and your auditor—without blocking legitimate users.
Here’s a practical playbook that aligns with Hong Kong’s AML/CFT Guideline for VASPs and the stablecoin consultation conclusions: do wallet-level due diligence, and when you can’t satisfy yourself on the counterparty or wallet type, you must screen the address with appropriate technology and mitigate heightened ML/TF risks. See the SFC AML/CFT Guideline (VASPs) and Hong Kong’s stablecoin policy direction from the HKMA/FSTB for context: SFC, HKMA, FATF.
What regulators expect (in plain language)
- Different wallets, different risks: The AML/CFT Guideline distinguishes between custodial wallets (held by FIs or VASPs) and self-hosted wallets used by those institutions. For other wallets (e.g., unhosted retail cold wallets), or when you can’t conduct satisfactory due diligence—such as where the custodial provider isn’t subject to AML/CFT regulation and supervision—licensees must screen the addresses with appropriate tools and mitigate higher ML/TF risks.
- Stablecoin angle: For redemption flows, expect due diligence on the institution providing the customer’s custodial wallet, plus additional controls for unhosted wallets.

A pragmatic EDD playbook for cold/unhosted wallets
- Prove control of the wallet
- Signed message or micro-transaction from the address.
- If hardware wallet: require a short video verification plus a timestamped test transfer (for high-value thresholds).
- No proof of control? Treat as high-risk and apply mitigations or decline.
- Classify the wallet type
- Custodial (FI/VASP) vs unhosted retail vs institutional self-custody.
- If custodial: request evidence of the provider’s AML/CFT supervision (license/registration link, jurisdiction, contact at compliance). If the provider is not supervised, treat as higher risk and escalate controls.
- KYT screening before first use and on every in/outflow
- Chain analytics across exposure categories (sanctions, darknet, mixers/tumblers, ransomware, scam clusters).
- Set numeric risk thresholds with action matrices. Example (illustrative): Risk score 0–24=auto-clear; 25–59=analyst review; 60+=block and file STR if warranted.
- Source-of-funds narrative tied to on-chain evidence
- Ask for trading venue records, TXIDs, and fiat off/on-ramp records matching timestamps and amounts.
- Triangulate with analytics clustering heuristics; don’t rely only on self-declarations.
- Travel Rule integration
- For VA transfers to/from other VASPs, collect and transmit originator/beneficiary information as required under AMLO/SFC Guideline. If the counterparty VASP is unknown or non-compliant, apply enhanced controls or reject.
- Mitigations when due diligence is not “satisfactory”
- Lower transaction caps, delayed availability, or staged settlement.
- Require additional corroboration (bank statements, exchange withdrawal logs).
- Heightened post-transaction monitoring for 90 days.
Quick control map
| Wallet type | Core checks | When to escalate |
|---|---|---|
| Custodial (FI/VASP) | Verify supervision/license, KYT on addresses, Travel Rule | Provider not AML/CFT supervised; jurisdiction concerns; inconsistent records |
| Institutional self-custody | Proof-of-control, governance docs, KYT | No policy evidence; unexplained high-risk exposure |
| Unhosted retail cold wallet | Proof-of-control, KYT, SOF narrative, velocity checks | High-risk exposure ≥60 (illustrative), mixer links, sanctions proximity, no documentation |
KYT that actually works in production
- Continuous monitoring: rescreen active addresses daily; dormant addresses weekly. Auto-escalate on new negative tags.
- Event-driven reviews: trigger on large-value spikes (e.g., >HKD 500,000 equivalent, illustrative), mixer contact, or rapid address reuse.
- Case management discipline: every override needs a documented rationale, data snapshots (TXIDs, screenshots), and second-line sign-off.
Documentation, because audits happen
- Maintain a wallet dossier: proof-of-control artefacts, analytics screenshots, provider supervision evidence, Travel Rule messages, and case notes.
- Exceptions register owned by Compliance; quarterly review with metrics (number of high-risk cold wallets approved, average time to EDD, SAR/STR conversion rate). If your STR conversion is near zero or 100%, recalibrate thresholds.
Stablecoin specifics to watch
- For redemptions, perform due diligence on the institution that provides the customer’s custodial wallet. If the institution isn’t AML/CFT supervised, treat as higher risk and add controls as above.
- Monitor issuer blacklists, freeze mechanics, and contract upgrade events; these are KYT-relevant risk signals.
Bottom line Cold wallets aren’t a loophole; they’re a control test. If you can prove control, verify the counterparty’s supervision where applicable, run credible KYT, and document mitigations when assurance is imperfect, you’ll meet Hong Kong’s standard without freezing your business. If you’re unsure whether your thresholds or playbooks will pass an SFC inspection, get an external dry-run review before the next audit cycle.


