HK Compliance Guide: FATF Source of Wealth for CBDC
HK compliance teams keep asking the same question as e-HKD pilots scale: how deep do we go on Source of Wealth (SOW) for CBDC users? The short answer: treat CBDC like any other high-velocity fiat rail, but overlay FATF’s virtual asset risk lens where CBDC touches stablecoins, unhosted wallets, or tokenised rails.
What FATF actually expects
- SOW vs SOF: Source of Wealth explains how a customer accumulated their total wealth over time (e.g., career income, business proceeds, investments). Source of Funds explains where the money in a specific transaction comes from.
- Triggers: FATF requires enhanced due diligence, including SOW, for higher-risk customers and PEPs (Rec. 10, 12). For digital assets, FATF highlights the heightened risk of “unhosted” wallets due to anonymity and mobility, which should inform your CBDC risk assessment when there’s interoperability with such wallets. See FATF’s VA/VASP guidance and standards: https://www.fatf-gafi.org/en/publications/Fatfrecommendations/Virtual-assets-vasps.html and https://www.fatf-gafi.org/en/publications/Fatfrecommendations/International-standards-fatf-recommendations.html.
Why this matters for CBDC in Hong Kong
- Hong Kong’s Policy Statement 2.0 underscores a “trusted market where innovation flourishes in a risk-managed manner,” including facilitation of stablecoin use cases and tokenisation. Translation: more digital rails, same (or higher) AML bar. See FSTB’s policy direction: https://www.fstb.gov.hk/en/financial-services/policy-initiatives/digital-assets.html.
- The BIS has flagged stablecoins’ ML/TF and sanctions evasion vulnerabilities, reinforcing the need for robust controls at on/off-ramps and cross-rail bridges: https://www.bis.org/topic/stablecoins.htm.
- Hong Kong’s consultations on virtual asset custody emphasise core AML/CFT obligations (CDD and record-keeping) alongside cyber-fraud risks—expect alignment of CBDC intermediaries with those same principles as the ecosystem converges. Consultation hub: https://www.fstb.gov.hk/en/public/consultation/consultation.html.

Practical SOW playbook for CBDC onboarding Use a risk-based approach. Start simple for low-risk retail; escalate for higher-risk profiles, large limits, or cross-border corridors.
SOW triggers for CBDC users in HK
- PEPs or close associates
- High transaction limits or rapid velocity increases (e.g., daily throughput jumps >3x within 30 days) [illustrative]
- Links to stablecoin off-ramps/on-ramps or tokenised assets
- Repeated transfers to/from unhosted wallets or privacy-enhanced rails
- Complex corporate structures or beneficial ownership in higher-risk sectors/jurisdictions
What to collect (and when)
| Scenario | SOW evidence to obtain | Verification tips |
|---|---|---|
| Retail, low limit | Employer letter or payslips; bank statements | Cross-check employer via corporate registry; verify account name match |
| High-limit retail or rapid velocity growth | Tax returns; audited portfolio statements; property sale documents | Match proceeds timing to CBDC inflows; confirm beneficial ownership |
| SME/merchant wallets | Financial statements; major contracts/invoices; ownership chart | Validate counterparties; screen UBOs; reconcile cashflow logic |
| PEPs or higher-risk geographies | Full wealth narrative; asset registers; notarised documents where applicable | Senior management approval; enhanced ongoing monitoring |
| Stablecoin/CBDC bridge users | Exchange account statements; blockchain provenance (travel rule for VA legs) | Risk-score counterpart VASPs; analyze wallet clustering and sanctions exposure |
Operational guardrails you should implement now
- Tiered onboarding: Set CBDC wallet tiers with documentary SOW uplift at each threshold. Keep the rubric simple and published internally.
- Cross-rail analytics: If any flow touches VAs or stablecoins, perform blockchain heuristics, sanctions screening, and counterparty VASP due diligence.
- Event-driven reviews: Trigger SOW refresh on limit upgrades, anomalous patterns, sanctions updates, or new cross-border corridors.
- Record-keeping: Retain SOW/SOF evidence and verification notes as required under AMLO, and ensure retrieval within regulator-friendly SLAs.
- Fraud-cyber linkage: Align SOW assessment with fraud telemetry (device fingerprinting, mule account indicators) given custody and cyberattack risks highlighted in government consultations.
What to do this quarter
- Map CBDC flows against VA/stablecoin touchpoints; label where FATF “unhosted wallet” risk applies.
- Implement a two-page SOW interview template for high-risk tiers; pilot with 20 customers [illustrative] and refine based on gaps.
- Calibrate thresholds using your data (e.g., top 5% velocity profiles) rather than generic limits.
- Run a QA sweep on record completeness; regulators care as much about auditability as they do about analysis quality.
CBDC doesn’t rewrite AML fundamentals. It magnifies weak spots. If you anchor SOW to real risk—especially at the CBDC–stablecoin seam—you’ll be ready for scale and for scrutiny.


