StanCOMP Compliance: HK Tokenised Securities & CBDC 2025
StanCOMP Compliance: HK Tokenised Securities & CBDC 2025
Hong Kong has moved from pilots to playbook. With the Government signalling “regularisation” of tokenised government bond issuance and incentives for RWA tokenisation, the question for issuers, managers, and brokers isn’t “if” but “how” you’ll operate on-chain within existing rules.

Compliance is a product feature in tokenisation.
What changed in 2025 (and why it matters)
- Policy direction is explicit. Policy Statement 2.0 sets out a unified regulatory approach, continued legal review on tokenisation, and the plan to regularise tokenised Government bond issuance to provide a steady supply of high‑quality digital bonds. It also flags expansion into broader RWAs, including sectors like precious metals.
- Market plumbing is maturing. Two landmark tokenised Government green bond issuances (totalling about HK$6.8 billion) proved feasibility; the next phase focuses on different currencies, tenors and programmability to broaden access and investor base.
- CBDC rails are closer. The HKMA continues e‑HKD work and participates in the BIS mBridge wholesale CBDC project, exploring programmable payments and cross‑border atomic settlement that can anchor tokenised securities and funds.
References:
- SFC guidance on tokenised securities activities and tokenised SFC‑authorised products: https://www.sfc.hk/en/news-and-announcements/policy-statements-and-announcements/sfc-provides-guidance-on-tokenised-securities-related-activities-and-tokenised-sfc-authorised-investment-products
- HKMA e‑HKD Pilot Programme: https://www.hkma.gov.hk/eng/key-functions/digital-currency/e-hkd/
- BIS mBridge (wholesale CBDC): https://www.bis.org/about/bisih/topics/cbdc/mcbdc_bridge.htm
Tokenised securities: what the SFC actually expects If your product is a tokenised representation of a traditional security, the SFC largely applies existing rules, with extra scrutiny on the tech stack:
- Smart contract risk: independent audits, deterministic logic for corporate actions, and upgradability controls (who can pause/upgrade, with what approvals).
- Key and wallet controls: segregation of issuer vs. registrar keys; dual controls for mint/burn; recovery procedures for lost keys and compromised wallets.
- Settlement and venue: secondary trading must occur on SFC‑licensed venues (ATS) that can list tokenised securities; be clear on whether on‑chain records or the off‑chain register is the legal book of record.
- Disclosure: pinpoint technology risks in offering docs—vulnerabilities, oracle dependencies, gas fee arrangements, and fallbacks for network downtime.
Fund tokenisation: deal mechanics drive compliance The SFC will consider tokenised SFC‑authorised funds case‑by‑case. The friction is operational, not conceptual:
- Transfer agent vs. token registrar: define the golden source of the register; reconcile cycles and exception handling.
- Deal cut‑off and NAV: ensure time‑stamping and block‑finality line up with subscription/redemption windows; guard against MEV and chain reorgs.
- Distribution controls: wallet whitelisting, professional investor gating (where applicable), and sanctions screening on‑chain and off‑chain.
- Gas, fees, and wallets: disclose who pays gas, how fees are wrapped (e.g., fee subsidies, meta‑tx), and what happens if network fees spike.
CBDC (e‑HKD and mBridge): where it clicks with tokenisation
- Atomic DvP: settle tokenised government bonds and funds against CBDC for near‑instant finality and reduced counterparty risk.
- Programmable cash flows: automate coupon, dividend, and management fee distributions via smart contracts with clear rulebooks.
- Cross‑border liquidity: mBridge pilots point to on‑chain FX PvP and intraday liquidity management for multi‑jurisdictional issuances.
Quick compliance actions you can take now
| Area | Do this next week | Owner |
|---|---|---|
| Product docs | Add a dedicated “Tokenisation Risk” section with audit summaries, key roles, and fallback processes | Legal/Compliance |
| Tech assurance | Commission an external smart contract and key‑management review; document upgradability governance | CTO |
| Venue/settlement | Map primary and secondary flows to SFC‑licensed intermediaries/ATS; define the legal register | COO |
| Ops controls | Implement wallet whitelisting, sanctions screening, and gas‑payment policy | Operations |
| CBDC readiness | Draft a DvP playbook for e‑HKD/mBridge pilots; identify bank/SVF partners | Treasury |
What this means if you’re shipping in 2025
- Issuers: Design tokens around registrar realities. If the off‑chain register rules, ensure deterministic reconciliation and investor communications when chain activity diverges.
- Fund managers: Treat tokenisation as a distribution and operations upgrade; your risk is in cut‑offs, corporate actions, and wallet governance.
- Brokers/venues: You’ll be gatekeepers. Prepare for enhanced onboarding, wallet risk scoring, and incident runbooks for smart contract pauses.
Hong Kong is setting the benchmark by making tokenisation regular, not experimental. If you want a second set of eyes before launch, StanCOMP can pressure‑test your tokenised security or fund against SFC and HKMA expectations—and get you CBDC‑ready without surprises.


