HK Compliance: AML for Algo Stablecoins & RWA Tokens

    StanCompliance
    December 18, 2025
    HKMA AML/CFT
    algorithmic stablecoins
    FATF compliance
    licensed stablecoin issuers
    unhosted wallets risk
    RWA tokenisation Hong Kong
    sanctions evasion risks
    HK Compliance: AML for Algo Stablecoins & RWA Tokens

    HK Compliance: AML for Algo Stablecoins & RWA Tokens

    Hong Kong wants two things at once: safe stablecoins and practical tokenisation. The HKMA’s consultation conclusions on AML/CFT for Licensed Stablecoin Issuers (LSIs) signal a firm regulatory perimeter, while Policy Statement 2.0 nudges banks and issuers to experiment with RWAs and stablecoin payment use cases. The message from the BIS and FATF is equally clear: stablecoins (especially when used with unhosted wallets) carry elevated ML/TF and sanctions-evasion risks. If you’re building in HK, design for regulation from day one.

    Where Hong Kong is heading on algorithmic stablecoins

    • Expect exclusion from licensing: HK’s regime has consistently pointed to fully reserved, fiat-referenced models. Algorithmic or unbacked mechanisms will struggle to meet an LSI standard for payment use cases.
    • If you touch them anyway: OTCs, brokers or wallets providing access to algorithmic stables should treat them as high-risk virtual assets. Elevate onboarding thresholds, impose jurisdictional blocks, and prohibit use as settlement rails for customer transfers.

    AML/CFT requirements to plan for (for LSIs and VA businesses) The HKMA’s draft AML/CFT Guideline for LSIs received broad support and sets out what most compliance teams should already be planning:

    • Customer due diligence: Full KYC for all direct customers, with source-of-funds/wealth for higher-risk profiles. Screen against UN, HK, and other relevant sanctions lists.
    • Travel Rule: Implement FATF R.16 information-sharing for stablecoin transfers to and from VASPs. For unhosted wallets, apply a risk-based approach: verify ownership before enabling withdrawals, cap amounts, and require additional information for large or repeated flows.
    • Blockchain analytics: Monitor exposure to mixers, darknet services, sanctioned addresses and layering typologies. Tune thresholds and test models; don’t just “bolt on” a vendor.
    • Wallet policy: Distinguish hosted vs unhosted. Permit only verified self-custody wallets; block wallets linked to high-risk clusters.
    • Treasury, mint/burn, and redemption controls: Segregate reserves, reconcile mint/burn with fiat movements, and monitor redemption spikes for potential layering.
    • Governance and audit: Independent compliance testing, model validation for analytics, detailed recordkeeping, and timely STR filings to the JFIU.

    A close-up image features hands holding a smartphone, illumi...
    A close-up image features hands holding a smartphone, illumi...

    RWA tokenisation: the AML reality check Hong Kong is encouraging tokenisation pilots, including payment and securities use cases. But tokenising does not simplify AML—it redistributes it.

    • Issuance: KYC all primary purchasers; verify beneficial ownership for SPVs. Obtain attestations tying tokens to the underlying asset and enforce transfer restrictions on-chain (whitelists) where needed.
    • Secondary markets: If tokens are transferable P2P, treat them like other VAs—Travel Rule, market surveillance, settlement monitoring, and sanctions screening.
    • Valuation and provenance: Document valuation sources, custody location of the underlying, and audit trails. Opaque provenance is a classic layering vector.

    Quick risk/control map

    TopicKey RisksControls that satisfy HK expectations
    Algorithmic stablecoinsUnbacked value; rapid layering; mixer exposureTreat as high-risk VA; prohibit as settlement rail; enhanced due diligence and analytics
    Asset-backed stablecoins (LSI)Counterparty and sanctions risk; unhosted walletsFull CDD, Travel Rule, verified self-custody only, treasury controls, sanctions geofencing
    RWA tokensOwnership opacity; cross-border transfersOn-chain whitelists, issuer/venue KYC, provenance attestations, secondary market surveillance

    90-day checklist for HK teams

    • Finalise a wallet policy: allow only verified self-custody; block high-risk clusters.
    • Choose a Travel Rule solution and run end-to-end testing with counterpart VASPs.
    • Implement analytics rules for mixers, sanctioned addresses, and high-velocity peeling; backtest and document thresholds (illustrative: auto-review for any flow > HKD 250,000 through high-risk clusters).
    • For RWA pilots, issue on a permissioned or whitelisted chain segment; embed transfer restrictions and cap P2P until surveillance is proven.
    • Run a sanctions tabletop: simulate an OFAC-match redemption and document your response timeline (illustrative target: containment within 2 hours).

    One last point. Regulatory mood is supportive, but only for designs that make AML/CFT enforceable.

    References: BIS commentary on stablecoin vulnerabilities (bis.org), FATF guidance on VAs and unhosted wallets, HKMA AML/CFT resources for LSIs, Policy Statement on Digital Assets (FSTB), AMLO/Travel Rule (Cap. 615), and JFIU reporting guidance.