Compliance Brief: HK Travel Rule for Cross-Border Crypto AML
Compliance Brief: HK Travel Rule for Cross-Border Crypto AML
Why this matters now Cross-border crypto payments are back in focus in Hong Kong. With the VATP licensing regime live under the Anti-Money Laundering and Counter-Terrorist Financing (Amendment) Ordinance 2022 and the Hong Kong Monetary Authority’s consultation conclusions for licensed stablecoin issuers, the Travel Rule is no longer a “nice to have.” If you touch external transfers, you’re in scope—either directly or as an intermediary.
What the Travel Rule requires in Hong Kong
- Global baseline: FATF Recommendation 16 requires originator and beneficiary information to “travel” with virtual asset transfers. See FATF’s guidance on virtual assets and VASPs.
- HK context: VATPs must meet AML/CFT obligations under AMLO. HKMA’s consultation conclusions for licensed stablecoin issuers confirm general support for Travel Rule requirements and point licensees to practical guidance in paragraphs 6.25–6.42 of the AML/CFT Guideline (handling interoperability gaps, unhosted wallets, and data shortfalls). The HKMA also reiterates that the Travel Rule is a key FATF requirement, applying by role: ordering, intermediary, and beneficiary institutions.
- Custody next: The Government’s public consultation on a virtual asset custodian services regime signals custodians will be subject to AML/CFT requirements. Expect alignment with Travel Rule expectations when custodians facilitate external VA transfers.
Role-by-role obligations (at a glance)
| Role | Core obligations | Typical decision points |
|---|---|---|
| Ordering institution (sender-side VASP/issuer) | Collect and verify required originator and beneficiary data; transmit using an interoperable standard; screen counterparties; withhold/return if data unavailable. | Counterparty VASP not TR-compliant; beneficiary is unhosted wallet; high-risk jurisdiction. |
| Intermediary institution (relay, bridge, custodian routing) | Ensure transmitted data remains with the transfer; identify and remediate missing fields; apply risk-based controls when data cannot be passed. | Protocol doesn’t support data fields; message dropped mid-route; on-chain vs off-chain reconciliation. |
| Beneficiary institution (receiver-side VASP/issuer) | Receive and screen required data; detect missing/deficient info; decide to credit, reject, or hold funds; file STRs where appropriate. | Partial data; name mismatch; sanctioned originator. |

Three cross-border friction points you should plan for
- Non-compliant counterparties
- Problem: You’re ready to send, but the offshore VASP can’t receive IVMS 101 or won’t provide beneficiary verification.
- What to do: Adopt a counterparty tiering policy. Only allow straight-through processing with TR-compliant VASPs; for others, require manual enrichment, capped limits, or route via a compliant correspondent.
- Unhosted wallets
- Problem: Customer wants to withdraw to self-custody. There’s no counterparty VASP to share data with.
- What to do: Per the HKMA AML/CFT Guideline (paras. 6.25–6.42), apply additional verification before execution: proof-of-control checks, enhanced KYC on the customer, purpose-of-transfer, and post-transfer monitoring. Consider thresholds and cooling-off periods.
- Interoperability gaps
- Problem: Your system uses IVMS 101, but the recipient demands a proprietary schema; or the chain doesn’t support metadata.
- What to do: Implement a message-layer gateway (e.g., TRP/IVMS 101 mappings) decoupled from on-chain settlement. Maintain fallbacks: secure out-of-band exchange, then reconcile on-chain TXIDs to message IDs.
Stablecoin issuers: you may be “intermediary” more often than you think
- If you’re neither the ordering nor beneficiary institution in a transfer using your rails, you can still be an intermediary under the Travel Rule. The HKMA’s conclusions make clear the rule’s centrality as a FATF requirement.
- Close the gap between wallet tech and compliance ops: embed data-capture at issuance/redemption, and ensure metadata persistence across bridges and swaps within your ecosystem.
Implementation moves for the next 90 days
- Map flows: Inventory every cross-border pathway (exchange-to-exchange, exchange-to-custodian, issuer-to-wallet, wallet-to-wallet). Label the role you play per leg.
- Set data standards: Use IVMS 101 end-to-end. Test with top counterparties in your corridors (e.g., HK–SG, HK–EU).
- Counterparty certification: Collect attestations on Travel Rule readiness; bake into onboarding and periodic reviews.
- Policy for non-compliant routes: Define when to block, when to hold for enrichment, and when to re-route.
- Unhosted wallet controls: Implement proof-of-ownership, velocity limits, and post-transaction alerts.
- Evidence pack: Log message payloads, transmission timestamps, and reconciliation to on-chain TXIDs for audit and investigations.
One last point The Travel Rule is not an IT project. It’s a cross-border risk posture.
If you’re unsure whether a specific transfer makes you the ordering, intermediary, or beneficiary institution, document your role analysis and apply the corresponding controls. Regulators won’t expect perfection on day one—but they will expect a defensible, risk-based approach grounded in the HKMA guideline and FATF standards.
References
- HKMA consultation conclusions for licensed stablecoin issuers and AML/CFT Guideline (see paras. 6.25–6.42 on practical Travel Rule challenges)
- FATF Recommendation 16 and Virtual Assets Guidance
- HKSAR Government: AMLO 2022 VATP licensing regime
- Public consultation on legislative proposal to regulate virtual asset custodian services


