Other A2P SMS regulations

Hong Kong SMS sender scheme expands

This matters for SMS operations, product integration, and compliance teams sending OTPs, billing alerts, service messages, and membership notifications to Hong Kong users. Hong Kong’s SMS Sender Registration Scheme is no longer just a public-awareness measure; it is increasingly part of sender authenticity, anti-scam controls, and delivery trust. In May 2026, OFCA refreshed scheme materials and sender lists, signaling continued operationalization. Brands still using unregistered or inconsistent sender IDs should expect lower user trust, higher complaint exposure, and greater scrutiny from carriers and local partners.

Published:05/31/2026 Updated:05/31/2026

1. Regulatory focus

In May 2026, OFCA continued updating the SMS Sender Registration Scheme webpage and registered-sender lists, showing that the framework is moving into steady-state operation rather than remaining a one-off anti-fraud campaign. The regulatory focus is not a blanket restriction on enterprise SMS, but the creation of a recognizable trust layer through 「#」-prefixed registered sender IDs, plus service-provider registration, public sender lists, and lookup tools. In practice, this is aimed at reducing spoofed messages that imitate banks, telecom operators, and service brands.

2. Business impact

For cross-border senders, the impact is broader than message wording. The real issue is end-to-end consistency across the sender identity chain: brand name, legal entity, Hong Kong operating entity, agent-submitted documents, and the actual sender ID used in traffic. Mismatches can delay onboarding, trigger additional manual review, and cause users to treat legitimate alerts as scams. That is especially risky for OTP, payments, logistics, and service-alert use cases, where timing and brand recognition directly affect conversion, support volume, and fraud-loss controls.

3. Operating recommendations

Companies should structure Hong Kong sender governance in three layers. First, inventory every sender ID used locally and remove legacy variants, case differences, and mixed-brand usage. Second, verify the registration status of agents, aggregators, and local SMS service providers so that the filing entity and the live sending entity match. Third, align front-end customer messaging across the app, website, and support scripts to explain the registered sender format and expected use. For OTP and high-risk account alerts, maintain a sender-template-use-case matrix instead of reusing one sender across unrelated workflows.

Frequently Asked Questions

If our SMS already delivers in Hong Kong, do we still need a sender registration review?
Yes. Deliverability alone does not mean your traffic is trusted or future-proof. Review whether the live sender ID matches the registered name, contracting entity, and actual message purpose. Also check whether multiple business teams are sharing one sender. Those inconsistencies tend to surface first when anti-scam controls tighten.
Do we need to rewrite message templates because Hong Kong users will see the 「#」 prefix?
Yes, in most cases. The opening line should immediately state the use case—login verification, billing, delivery, or service alert—and clearly align the brand reference with the sender ID. If the message includes a link, payment step, or account action, early identity cues are even more important to reduce hesitation and scam suspicion.
When sending through an international aggregator, who owns sender consistency for Hong Kong traffic?
It cannot sit solely with the aggregator. The brand should maintain an auditable sender inventory, use-case mapping, and Hong Kong entity details, while the aggregator handles local filing and routing controls. Both sides should also agree on a change process so that new sub-brands, template revisions, or routing shifts trigger a registration review before launch.
This article is for informational purposes only and does not constitute legal advice.

Related products

Need compliance guidance?

Contact us for guidance on target markets, message scenarios, and sending routes.

Get in Touch