StanCOMP Compliance Brief: HK Tokenised Securities & CBDC

    StanCompliance
    July 13, 2026
    Hong Kong digital asset regulation
    tokenised securities compliance
    asset-backed tokens RWA
    CBDC e-HKD
    tokenised government bonds
    SFC licensing
    StanCOMP Compliance Brief: HK Tokenised Securities & CBDC

    StanCOMP Compliance Brief: HK Tokenised Securities & CBDC

    Hong Kong just put more wood behind the arrow. With the Government signalling “regularised” issuance of tokenised Government bonds and committing to broaden tokenisation across asset classes, the policy direction is clear: digital assets (the Government now uses this term instead of “virtual assets”) are moving from pilots to market infrastructure. At the same time, the HKMA’s e-HKD workstream is zeroing in on settlement efficiency for tokenised instruments.

    If you’re structuring tokenised securities or RWAs, 2025 is about execution, not exploration.

    What changed and why it matters

    • Tokenised bonds become a programme, not a one-off: The Government has said it will regularise tokenised bond issuance, exploring multiple currencies and tenors, with roughly HK$6.8 billion already issued across pilots. This is a benchmark move aimed at steady, high-quality supply and broader investor access. See the Financial Services and the Treasury Bureau’s policy direction: https://www.fstb.gov.hk/en/
    • Wider RWA scope: Policymakers explicitly call out expansion into sectors like precious metals and other financial instruments—signalling comfort with the tech and a desire to make Hong Kong’s market data plug neatly into global systems.
    • Digital money integration is the next unlock: FSTB and HKMA are engaging industry on integrating “digital money” for secondary market use cases and faster settlement. That dovetails with the HKMA’s e-HKD Pilot Programme, which is now in its second phase focusing on programmability, tokenised asset settlement and privacy. Details: https://www.hkma.gov.hk/eng/key-functions/digital-currency/ehkd/

    A tightly framed image of a smartphone in use, with fingers ...
    A tightly framed image of a smartphone in use, with fingers ...

    Tokenised securities: what the SFC expects If your token represents a share, bond, fund unit, note, structured product or a participation right, assume the Securities and Futures Ordinance (SFO) applies. The SFC has made it clear that “tokenised” is a form factor, not a regulatory escape hatch.

    Key implications:

    • Offers and marketing: Public offers require a prospectus or an exemption. Private placements must be tightly controlled (professional investors, limited offerees, and no retail leakage). Don’t “airdrop” compliance.
    • Licensing: Dealing, advising, arranging placement and operating secondary venues trigger Type 1, 4 and 7 respectively. Asset managers of a tokenised fund need Type 9. Check the SFC licensing portal: https://www.sfc.hk/en/portal/home
    • Custody and wallets: Intermediaries must meet existing custody standards and tech risk controls. On-chain whitelists and transfer restrictions should enforce investor eligibility and lock-ups.
    • Secondary trading: If you want an order book, partner with an SFC-licensed ATS authorised to trade securities. Virtual asset platform licences under AMLO are for non-security tokens; tokenised securities remain under the SFO perimeter. VATP info: https://www.sfc.hk/en/portal/licensing/virtual-asset-trading-platforms

    Quick map: product vs. likely rules

    Product ideaLikely regulatory categoryTypical licences/approvals
    Tokenised corporate bond (PI-only)Security (debt)Type 1 for placement; prospectus exemption controls; licensed ATS for secondary
    Tokenised fund unitsSecurity/CISType 9 (management), Type 1/4 (distribution/advice), SFC authorisation if retail
    Gold-backed token with pooled storage and yieldOften a CIS/structured productTreat as security; avoid retail unless authorised; Type 1/4/9 as applicable
    Real estate fractional token with central managementCISSame as above; heavy on disclosure, valuation, governance
    Receivables token (true sale, no pooling/yield)May still be a securityLegal memo first; whitelist-only transfers; Type 1 if arranging

    Note: classification is fact-specific. Get a written legal analysis before you write code.

    Asset-backed tokens (RWA): design choices that keep you out of trouble

    • Full reserving and direct bailment rights reduce—but do not eliminate—securities/CIS risk. Avoid revenue shares, guaranteed yields or pooled management if you want to stay simple.
    • On-chain controls must mirror paper controls: whitelists, transfer restrictions, time-based locks, and smart-contract enforced caps aligned with offering terms.
    • Disclosures win trust: provenance of assets, custody arrangements, audit attestations, oracles, and redemption mechanics. Publish them and keep them current.

    CBDC (e-HKD) and settlement: plan for atomic DvP

    • Where e-HKD fits: HKMA’s pilots are targeting programmable payments and synchronised settlement for tokenised assets. This can compress settlement cycles and reduce counterparty risk. HKMA overview: https://www.hkma.gov.hk/eng/key-functions/digital-currency/ehkd/
    • Stablecoins: A dedicated stablecoin issuer regime is being developed by FSTB/HKMA. Assume licensing, 1:1 reserves, robust redemption and restrictions on issuance/marketing. Do not anchor mission-critical flows on unregulated stablecoins if you plan to offer in Hong Kong.

    What to do now

    1. Classification memo first: Decide security/CIS/structured product status and document exemptions. No marketing without this.
    2. Map licences and partners: Placement (Type 1), advice (Type 4), management (Type 9), trading (Type 7/ATS). Start partner diligence early.
    3. Build transfer controls into code: Whitelists, PI-only flags, lock-ups, and event-driven restrictions must be at the token contract level.
    4. Custody architecture: Segregated wallets, key governance (4-eyes), incident playbooks, and independent reconciliations. Consider a qualified custodian model.
    5. Settlement strategy: Design for e-HKD or regulated stablecoin rails; implement DvP with clear fallbacks to RTGS.
    6. Disclosure pack: Term sheet, risk factors, custody and redemption details, audit and oracle descriptions, and secondary market liquidity statements.

    One red line: don’t market to retail unless your product is authorised for retail.

    If you want a sanity check on structure, licences and smart-contract controls before launch, we can review your flow against SFC/HKMA expectations and draft the classification memo and PI controls in under two weeks (illustrative timeline).