# A2P SMS regulations in Jordan > In Jordan, every A2P sender ID must be pre-registered with the Telecommunications Regulatory Commission (TRC), and promotional SMS needs verifiable opt-in. Consent records are kept for 12 months and shown to the TRC on request, and recipients' personal data falls under the Personal Data Protection Law of 2023. - Canonical URL: https://www.broadnet.me/regulations/jordan - Language: en - Last reviewed: 2026-10-20 - Publisher: BroadNet (https://www.broadnet.me) ## Who regulates A2P SMS in Jordan? The Telecommunications Regulatory Commission (TRC) regulates the sector and licenses the three mobile operators that terminate A2P traffic: Zain Jordan, Orange Jordan and Umniah. Sender-ID registration runs through the TRC, and the TRC can ask to see the consent records behind promotional traffic. - Regulator: TRC (trc.gov.jo). - Mobile operators: Zain Jordan, Orange Jordan and Umniah. - Data protection: the Personal Data Protection Law of 2023. ## How does sender-ID registration work? All alphanumeric sender IDs must be pre-registered with the TRC before A2P traffic is sent to Jordanian mobile numbers. The rule is one ID per use case per entity, and registrations are renewed every year. BroadNet files the registration and the renewals for you; filing typically takes 5–7 business days. - Pre-registration with the TRC for every alphanumeric ID. - One ID per use case per entity. - Annual renewal. - Typical filing time: 5–7 business days. ## Promotional vs. transactional messages Promotional SMS requires verifiable opt-in from each recipient. The consent records must be retained for 12 months and made available to the TRC on request. Transactional messages such as OTPs and account alerts still go out under a TRC-registered sender ID. - Promotional: verifiable opt-in, records kept for 12 months. - Consent records available to the TRC on request. - Transactional: registered sender ID required. ## Data protection: the PDPL of 2023 Jordan's Personal Data Protection Law (2023) applies to all recipient personal data, including mobile numbers. It covers consent, breach notification and restrictions on cross-border transfers of personal data. - Applies to all recipient personal data. - Consent and breach-notification duties. - Cross-border transfer restrictions. - Law: Personal Data Protection Law No. 24 of 2023. ## Arabic and Latin content Arabic and Latin scripts are supported at parity. Arabic messages are sent in UCS-2 encoding, which fits 70 characters in a single SMS instead of the 160 of GSM-7, so long Arabic templates split into more parts. Latin transliteration of Arabic is optional and rarely used in-market. - Arabic in UCS-2: 70 characters per single SMS. - Latin in GSM-7: 160 characters per single SMS. - Transliteration optional, rarely used. ## Jordan rules: promotional vs. transactional SMS | | Promotional / marketing | Transactional (OTP, alerts) | |---|---|---| | TRC-registered sender ID | Yes | Yes | | Verifiable opt-in, records kept 12 months | Yes | No | | Personal Data Protection Law (2023) applies | Yes | Yes | | Arabic (UCS-2) and Latin supported | Yes | Yes | ## Frequently asked questions ### Who regulates SMS in Jordan? The Telecommunications Regulatory Commission (TRC). It licenses Zain Jordan, Orange Jordan and Umniah, the three operators that carry A2P traffic, and runs sender-ID registration. ### Do I need to register sender IDs in Jordan? Yes. All alphanumeric sender IDs must be pre-registered with the TRC: one ID per use case per entity, renewed every year. BroadNet handles the filing, which typically takes 5–7 business days. ### Is consent required for marketing SMS in Jordan? Yes. Promotional SMS requires verifiable opt-in, and the consent records must be kept for 12 months and made available to the TRC on request. ### What are the penalties for non-compliance? The TRC enforces the sender-ID and consent rules. We do not quote a fine amount here because we have not found one published by the TRC for A2P SMS; check trc.gov.jo for the current framework. BroadNet's compliance engine blocks sends that break the registration and opt-in rules. ## Related - [Jordan coverage](https://www.broadnet.me/coverage/jordan) - [All regulations](https://www.broadnet.me/regulations) ## Technical facts for Jordan Network codes, message lengths and sender-ID rules in one table. Segment lengths are the GSM standard values (3GPP TS 23.038). | Technical facts | | |---|---| | Mobile country code (MCC) | 416 | | Dialling code | +962 | | Operators (MCC-MNC) | Zain Jordan · 416-01; Orange Jordan · 416-77; Umniah · 416-03 | | SMS length, GSM-7 (Latin alphabet) | 160 characters in a single SMS; 153 per part when concatenated | | SMS length, UCS-2 (Arabic, Cyrillic and other scripts) | 70 characters in a single SMS; 67 per part when concatenated | | Regulator | TRC (Telecommunications Regulatory Commission) | | Sender-ID rules | All alphanumeric IDs must be pre-registered with TRC. One ID per use-case per entity; renewals annual. Arabic and Latin scripts both supported at parity. | | Sender-ID lead time | 5-7 business days | ## How to register a sender ID in Jordan What to prepare, who approves it and how long it takes. Send us the documents below and BroadNet coordinates the registration with the operators, the regulator or the registry, as the market requires. - Who approves: TRC, which licenses Zain Jordan, Orange Jordan and Umniah. The ID is filed with all three operators. - Typical lead time: 5–7 business days once the paperwork is in - Renewal: Annual, handled automatically ### Document checklist - [ ] Jordan commercial registration - [ ] Authorisation letter - [ ] Sample message templates in English and Arabic - [ ] Traffic-type declaration ### Steps 1. Choose the sender ID: alphanumeric, Latin or Arabic, up to 11 characters. Use one ID per use case per entity. 2. Send BroadNet the documents. BroadNet files with TRC and all three operators in parallel. 3. Approval typically takes 5–7 business days. Renewals are annual and handled automatically. 4. Promotional SMS needs verifiable opt-in, and the TRC can ask to see the consent records. Gambling and unlicensed financial services are blocked at the operator firewall. ### Common reasons for rejection - Generic IDs such as INFO or ALERT - A brand that does not match the trade registration - Marketing templates without retained opt-in evidence - Templates that mix promotional and transactional intent ### Official sources - [TRC — Telecommunications Regulatory Commission](https://trc.gov.jo/) Requirements are set by the regulator and the operators and can change. Check the official sources, or ask our team, before you file. ## Sources - [TRC — Telecommunications Regulatory Commission](https://trc.gov.jo/)