HK Compliance Guide: FATF Source of Wealth for CBDC

    StanCompliance
    March 7, 2026
    Hong Kong compliance
    FATF
    Source of Wealth
    CBDC
    AML/CFT
    Stablecoins
    Virtual asset regulation
    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

    Why this matters for CBDC in Hong Kong

    A close-up of a hand engaging with virtual checklists, featu...
    A close-up of a hand engaging with virtual checklists, featu...

    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)

    ScenarioSOW evidence to obtainVerification tips
    Retail, low limitEmployer letter or payslips; bank statementsCross-check employer via corporate registry; verify account name match
    High-limit retail or rapid velocity growthTax returns; audited portfolio statements; property sale documentsMatch proceeds timing to CBDC inflows; confirm beneficial ownership
    SME/merchant walletsFinancial statements; major contracts/invoices; ownership chartValidate counterparties; screen UBOs; reconcile cashflow logic
    PEPs or higher-risk geographiesFull wealth narrative; asset registers; notarised documents where applicableSenior management approval; enhanced ongoing monitoring
    Stablecoin/CBDC bridge usersExchange 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.