Skip to main content

​
Singapore SGNIC Sender-ID Registration Rules

Singapore regulates commercial A2P SMS through the SGNIC sender-ID registry — the alphanumeric sender registration regime administered by the Infocomm Media Development Authority (IMDA). An alphanumeric Sender ID reaches a +65 handset only once that sender name is registered on the SGNIC registry and approved; unregistered alphanumeric traffic is rejected at the carrier edge, not held for review. Marketing SMS into SG follows the PDPA deemed-consent posture — opt-out, not opt-in — which the Singapore and Thailand PDPA Posture page documents at the privacy-law level. This page documents the sender-registration mechanics only: the SGNIC registry, the send-time gate, the opt-out keyword, and the quiet-hours convention. Singapore is a tenant-owned burden. Orbit never mandates your posture — it keeps the country-rules reference that feeds the send-time gates, and it gives you the consent ledger, the suppression layer, the English opt-out aliases, and the sender-registration tracking. The legal posture is yours.
This page is documentation, not legal advice. IMDA blocks unregistered alphanumeric senders at the carrier — traffic on a Sender ID with no approved SGNIC entry does not deliver — and the PDPA consent duty is enforced against the sender. Have counsel review your sender-name choice, your consent capture, and your DNC-register scrubbing; Orbit supplies the surfaces.

​
The SG row — accepted sender classes for Singapore

Read the SG row of GET /compliance/country-rules?channel=sms (see Country Compliance Requirements). Consolidated:

​
SGNIC — the alphanumeric sender registry

SGNIC is the Singapore sender-ID registry IMDA administers. Singapore runs a registry-based alphanumeric-sender regime: a Sender ID that appears as the “from” on an SMS must be on file with the SGNIC registry before the carriers pass it, and unregistered alphanumeric senders are rejected at the carrier edge — this is not a filtering posture you can negotiate with after the fact. The rules as they apply to your traffic:
  • Pre-registration is required. An alphanumeric Sender ID on an SMPP-routed channel into SG delivers only when the SG entry on your registration is approved. Before approval the send-time gate holds the traffic with MESSAGING_SG_SENDER_NOT_REGISTERED (422); troubleshoot that code with Troubleshooting Compliance Error Codes.
  • The 3-character floor is regulatory. SGNIC rejects Sender IDs shorter than 3 characters, the same floor enforced by AGCOM, ANATEL, and OFCOM — the format rule is 3–11 characters, letters, digits, space, hyphen, and underscore. A two-letter abbreviation is not a viable SG sender.
  • The sender name must match the brand. IMDA rejects generic names (INFO, SMS, ALERT) that do not tie back to your registered entity. Pick a registrable brand name the KYC documents you upload can support.
  • Register before traffic. Unlike a post-paid registration market, Singapore rejects the traffic itself when the name is unregistered — the send-gate returns the SG sender-not-registered error on any A2P attempt until the entry is approved.
Tenant-owned controls that map to the SGNIC rule:

​
SGNIC sender registration vs PDPA privacy posture

This page and the Singapore and Thailand PDPA Posture page cover different obligations under the same statute. Read both; neither substitutes for the other. A fully-registered SGNIC sender with no PDPA consent records is still a non-compliant SG posture; PDPA consent with an unregistered sender never delivers. Both surfaces close the SG row.
SGNIC’s registry is a sender-identity regime, not a consent regime. The PDPA consent duty applies on top of it — registering the sender never substitutes for consent. Singapore’s PDPA operates a deemed-consent posture (strengthened in the 2020 amendment with a deemed-by-business-necessity class): you may send marketing on a disclosed, recorded basis until the recipient opts out, subject to the DNC register.
  • Record the basis. At acquisition, record the grant with lawful_basis and a purpose string per (contact, channel) through Consent Management. The deemed-consent nuance lives in the basis you record, not in a platform default.
  • Scrub the DNC register. Singapore’s DNC register gates marketing SMS, voice, and fax to +65 numbers. Wire the pre-flight check into your campaign rollout so an SG-destination list scrubs against the combination of your suppression layer and the national register before the first send — see the PDPA posture page and DNC Scrubbing.
  • Withdrawal lands on one list. STOP keywords, the consent API with opt_in: false, and the preference center all land on the same suppression list. A revoked +65 contact stays suppressed regardless of which entry point they used.

​
No-send convention vs tenant quiet hours

Singapore’s marketing convention — the carrier expectation under PDPA’s consent context — treats overnight sends as violations of the consent you captured, but no single statutory SMS marketing window exists under PDPA. The posture is deliberate configuration, not a default Orbit sets for you. Singapore runs a fixed UTC+8 zone with no daylight saving, so a recipient-timezone-resolved window applies the same offset all year. Validate the recipient timezone resolution with Quiet-Hours Preview before you flip SG live.

​
English-language opt-out keyword handling

The Opt-Out Keyword Alias Table includes the English opt-out vocabulary: STOP, UNSUBSCRIBE, CANCEL, END, QUIT — matched with locale-insensitive case-folding and Unicode normalisation, so a reply stop, Stop, or STOP. all write the suppression entry. Singapore’s primary commercial-messaging language is English, so the seeded English aliases carry the SG opt-out vocabulary. When an SG opt-out fires, the suppression entry it writes is channel-scoped to all, not sms — the same propagation behaviour as the English STOP alias. A recipient’s STOP knocks that contact off SMS, WhatsApp, and RCS simultaneously: the opt-out is a request to stop being contacted, not a request to stop SMS. If you have pruned the seeded English rules in the dashboard, re-add them under Messages → SMS → Opt-out Rules before launching SG traffic. Publish the opt-out keyword you reference in your consent text and sender-name footer; the auto-reply your keyword rule writes should acknowledge the opt-out in English.

​
Posture-FAQ tuple for Singapore

When you answer “what does Singapore need?” against the Posture FAQ, the SG-specific tuple is:
  • Default quiet-hours window: platform fallback 21:00–09:00 (fail-open fallback only — configure tenant hours deliberately).
  • Opt-in required before marketing: no — PDPA deemed consent (opt-out), subject to the DNC register. See the PDPA posture page.
  • Sender registration level: required (SGNIC pre-registration; 3-character minimum Sender-ID length).
  • Opt-out keyword family: English STOP, UNSUBSCRIBE, CANCEL, END, QUIT.
  • Official law: Singapore Personal Data Protection Act 2012 (amended 2020); IMDA administers the SGNIC sender-ID registry.

​
Worked configuration to a defensible SG posture

Narrowed from the generic launch checklist in Country Compliance Requirements to the SG row:
1

Look up the SG row

Call GET /compliance/country-rules?channel=sms&country=SG and read the SG row’s sender_types, registration, content_restrictions, and stop_requirement. If registration is required, the send-time gate holds SG traffic until an approved sender is attached — this is the intended behavior, not a fault.
2

Pick a sender type

Alphanumeric Sender ID (pre-registered with SGNIC) or a numeric long code — both reach +65 handsets. Pick an alphanumeric brand of at least 3 characters if you want a named sender.
3

Pre-flight then file the Sender ID

GET /compliance/check?sender_id=<id>&country=SG to confirm the sender is viable, then POST /compliance/sender-id-registrations with a country: "SG" entry referencing your doc_… KYC documents. Budget the SGNIC registry approval lead time — days to weeks. See Sender-ID Registration.
4

Record PDPA consent with the basis

Record a consent entry with lawful_basis and a purpose string per (contact, channel) before any SG marketing send; Singapore is deemed-consent (opt-out) under PDPA, subject to the DNC register. See Consent Management and the PDPA posture page.
5

Scrub the DNC register before outbound

Wire GET /compliance/dnc/check into your campaign rollout so an SG-destination list scrubs against the national DNC register and your suppression layer before the first send. See DNC Scrubbing.
6

Set tenant quiet hours deliberately

Turn on tenant quiet hours covering a window your counsel accepts for SG marketing (a conservative start is 21:00–09:00 Asia/Singapore). Orbit defaults this off. Validate with Quiet-Hours Preview. See Quiet-Hours Configuration.
7

Wire the English opt-out family

Confirm STOP, UNSUBSCRIBE, CANCEL, END, QUIT are mapped into the alias table and write suppression entries at scope all. See Opt-Out Keyword Alias Table.
8

Launch

With the SG sender approved, PDPA consent recorded, DNC scrubbed, quiet hours set, and the English aliases wired, start sending.