HK KYT Onboarding Risk Matrix: StanCOMP Compliance Guide
HK KYT Onboarding Risk Matrix: what HK teams should do before first deposit
If you onboard customers transacting in stablecoins or other virtual assets in Hong Kong, you can’t rely on KYC alone. Regulators expect live, on-chain context from day one. That’s KYT — Know Your Transaction — and it now sits at onboarding, not just post-trade monitoring.
Two anchors to keep in mind:
- The HKMA’s stablecoin AML consultation acknowledges it’s hard to reliably classify “unhosted” vs. custodial wallets with today’s tools, and specifically “appreciates comments and suggestions on risk management of customers’ wallets” (HKMA consultation conclusions).
- The proposed VA custodian regime will require licensees to “adopt appropriate technological solutions (e.g. blockchain analytic tools)” to track assets and flag suspicious activity (FSTB public consultation).

Translation: don’t over-promise certainty on wallet types; do ship a defensible, technology-enabled risk framework from onboarding.
The onboarding problem (and opportunity)
Stablecoins carry the same ML/TF risks as other VAs — anonymity features, global reach, layering — and can be sent to wallets outside AML/CFT-obliged entities (HKMA consultation conclusions). HKMA also notes that the information accompanying a stablecoin transfer is essential for transaction monitoring, sanctions screening, and risk mitigation. This means your first interaction with a client must already test: who controls the wallets, what the on-chain history looks like, and whether counterparties are obliged entities.
One more line for emphasis: your first deposit sets your baseline risk.
A pragmatic HK KYT Onboarding Risk Matrix
Use a two-layer matrix — Customer Profile x Wallet/Asset Signals — to decide controls. The tiers and thresholds below are illustrative, not prescriptive.
| Risk Tier | Typical Customer/Profile | Wallet/Asset Signals | KYT Controls at Onboarding | Decision/Limits |
|---|---|---|---|---|
| Low | HK/Singapore regulated FIs, SFC-licensed VASPs | Custodial wallets from obliged entities; no sanctions hits | Travel Rule data exchange where applicable; 365-day address screening; proof of control | Approve; standard limits |
| Medium | Regulated overseas VASPs, listed corporates, HK custodian applicants | Mixed custodial/unhosted wallets; minor indirect exposure (<0.5% of flow) to risk services | Ownership challenge (signed message/test tx); 365-day backtrace; counterparty typology tagging | Approve; monitor with tighter thresholds |
| High | OTC brokers, DAOs/foundations, HNW with self-custody | Unhosted wallets; exposure to mixers/gambling DApps (≥0.5% in 180 days) | Enhanced due diligence; source-of-coin narrative + evidence; whitelist-only withdrawals | Conditional approve; reduced limits; enhanced monitoring |
| Very High | High-risk geographies, sanctioned nexus, privacy coins bridging | Direct exposure to sanctioned/darknet services; obfuscated flows | Independent escalations; verification through alternative attestations; senior sign-off | Decline or hold pending remediation |
Implementation notes:
- Ownership challenge: ask clients to sign a message from the declared address or send a nominal test transaction from it.
- Backtrace window: 365 days for business, 180 days minimum for retail. Extend if funds show slow-move layering.
- Exposure math: use the larger of value-weighted or transaction-count-weighted exposure to risky categories.
- Counterparty typology: tag peers as obliged entity, unhosted, or unknown; do not assume analytics’ “custodial” labels are perfect — HKMA explicitly flags the classification limits.
What to do now (checklist you can ship this quarter)
- Map Travel Rule readiness: when counterparties are obliged entities, exchange sender/beneficiary info to support sanctions/AML screening per AMLO requirements.
- Integrate blockchain analytics: score customer-declared addresses at onboarding; require pre-approval for new deposit/withdrawal addresses.
- Build a sanctions heatmap: auto-block any direct exposure; escalate indirect exposures above an internal threshold (e.g., 0.5% over 365 days, illustrative).
- Record wallet evidence: screenshots, signed messages, and TX hashes tied to your files. If you can’t verify control, treat as higher risk.
- Set tiered limits and review cadence: low risk quarterly; high risk monthly; very high risk only with senior approval.
- Document your exceptions playbook: when you allow remediation (e.g., address rotation) vs. when you decline the relationship.
Why this aligns with HK expectations
- HKMA’s stablecoin AML conclusions highlight both the difficulty in classifying wallets and the importance of information accompanying transfers for monitoring and sanctions screening. Design your matrix to use information you can actually verify at onboarding.
- The proposed VA custodian regime expects robust analytics and suspicious activity identification. Your onboarding KYT becomes evidence you can operate a license-ready control environment.
There’s supportive policy tailwind too: Hong Kong’s Policy Statement 2.0 signals resources for tokenisation pilots via Cyberport — helpful if you’re investing in compliance infrastructure rather than deferring it.
If you want a working template calibrated for your flows, StanCOMP can help you operationalise this matrix — from analytics selection to exception governance — and get you audit-ready before the first coin lands.
References:
- HKMA consultation conclusions on stablecoin AML (wallet classification challenges and information needs)
- FSTB public consultation on VA custodian services (analytics requirement)
- AMLO Cap. 615 (Travel Rule obligations for VASPs and obliged entities)


