Palestine · MTIT

A2P SMS regulations in Palestine.
Compliance with MTIT rules and sender-ID registration.

A2P SMS to Palestine is regulated by the Ministry of Telecommunications and Information Technology (MTIT). Sender IDs registered with Jawwal and Wataniya via MTIT-aligned framework. Arabic + Latin scripts supported, with approval typically taking 7-10 business days. Routing handles West Bank and Gaza differently due to network topology — BroadNet's engine selects the right MNO per recipient prefix automatically. BroadNet carries this traffic over direct operator connections.

By the numbers

MTIT

Ministry of Telecommunications and Information Technology regulates A2P messaging

7-10 days

Typical sender-ID approval time

99.99%

Platform uptime SLA

Carrier-grade infrastructure, operating since 2003.

Who regulates A2P SMS in Palestine?

Application-to-person messaging to Palestine is overseen by the Ministry of Telecommunications and Information Technology (MTIT), which licenses the operators that terminate A2P traffic and sets the conditions those routes run under. BroadNet delivers into Palestine over direct operator connections — Jawwal and Wataniya — rather than through resold or grey routes, so the sender ID, the delivery receipt and the audit trail all come back from the licensed path.

Telecoms regulator: Ministry of Telecommunications and Information Technology (MTIT).
Direct operator routes: Jawwal and Wataniya.
Sender-ID registration: Sender IDs registered with Jawwal and Wataniya via MTIT-aligned framework. Arabic + Latin scripts supported.
Typical lead time: 7-10 business days.

Sender ID registration in Palestine

Sender IDs registered with Jawwal and Wataniya via MTIT-aligned framework. Arabic + Latin scripts supported. Registration is not a formality — an unregistered or mismatched sender ID is the most common reason otherwise-valid traffic is filtered, and the failure is usually silent rather than a hard rejection. Plan 7-10 business days for approval and register before you need the route, not during a launch.

Lead time: 7-10 business days.
BroadNet files sender IDs on your behalf through the MTIT-licensed operators.
Arabic + Latin: UCS-2 routes at parity with GSM-7.
Time to production: Live in 5–15 business days from test-access request to production.

Consent, content and timing rules

Routing handles West Bank and Gaza differently due to network topology — BroadNet's engine selects the right MNO per recipient prefix automatically. Promotional traffic requires a consent record you can produce on request, and an opt-out that is honoured immediately and permanently. Transactional messages — one-time passcodes, delivery and account alerts — are treated differently from marketing, but the distinction is decided by the content of the message rather than by how the campaign is labelled.

MTIT sender ID: Sender IDs registered through MTIT-aligned operator framework.
Arabic + Latin: UCS-2 routes at parity with GSM-7.
PII handling: Recipient PII handled per Jordanian/Palestinian data protection framework.
Auto MNO selection: Engine routes per West Bank / Gaza prefix automatically.

What this means for your integration

Practically, three things decide whether traffic to Palestine performs: a registered sender ID on an MTIT-licensed route, a consent and opt-out record you can evidence, and message content that matches the category it was registered under. BroadNet's compliance engine checks each submission against the Palestine ruleset before it reaches the operator, so a non-compliant send is rejected back to you rather than filtered silently downstream — which is the difference between a fixable error and traffic that quietly disappears.

Every message returns a delivery receipt (DLR); BroadNet does not publish per-country delivery percentages.
Indicative list pricing: USD 0.04 – 0.07 per message.
Addressable mobile base: 4.6M subscribers.
PII handling: Recipient PII handled per Jordanian/Palestinian data protection framework.

DiagramSender ID registration, step by step

Submit your KYC packTrade licence, authorisation letter and sample messages
BroadNet files the applicationWith the operators or the regulator, as the market requires
Review and approvalTypical lead time7-10 business days
Send under your brandYour approved sender ID on every message

Palestine

PalestineOther BroadNet marketsBroadNet HQ, Dubai

Technical facts

Technical facts for Palestine

Network codes, message lengths and sender-ID rules in one table. Segment lengths are the GSM standard values (3GPP TS 23.038).

Technical facts for Palestine
Mobile country code (MCC)	425
Dialling code	+970
Operators (MCC-MNC)	Jawwal · 425-05 Wataniya · 425-06
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	MTIT (Ministry of Telecommunications and Information Technology)
Sender-ID rules	Sender IDs registered with Jawwal and Wataniya via MTIT-aligned framework. Arabic + Latin scripts supported.
Sender-ID lead time	7-10 business days

Sources

MTIT · mtit.gov.ps

Last reviewed September 29, 2026

How we write and review content

Related markets

Compare A2P SMS rules across the region.

Each market pairs a regulatory playbook with its live coverage and operator-direct routing detail.

Palestine rules: promotional vs. transactional SMS

Capability	Promotional / marketing	Transactional / service (OTP, alerts)
Registered sender ID required
Prior consent required		—
Opt-out instruction required		—
Timing restrictions apply		—
Delivery receipts available

FAQ

Common questions

Who regulates SMS in Palestine?

the Ministry of Telecommunications and Information Technology (MTIT). It licenses the operators that terminate A2P traffic and sets the conditions those routes operate under. BroadNet delivers into Palestine over direct connections to Jawwal and Wataniya.

Do I need to register a sender ID for Palestine?

Yes. Sender IDs registered with Jawwal and Wataniya via MTIT-aligned framework. Arabic + Latin scripts supported. Allow 7-10 business days for approval. An unregistered sender ID is the most common cause of silently filtered traffic, so register before the campaign rather than during it.

How long does it take to start sending to Palestine?

Live in 5–15 business days from test-access request to production. The sender-ID registration is usually the long pole at 7-10 business days; the technical integration itself is the same REST or SMPP interface you would use for any other market.

What content and consent rules apply in Palestine?

Routing handles West Bank and Gaza differently due to network topology — BroadNet's engine selects the right MNO per recipient prefix automatically. Promotional traffic needs a consent record you can produce on request and an opt-out honoured immediately; transactional messages such as passcodes are treated separately, judged on content rather than campaign label.

What does A2P SMS cost in Palestine?

Indicative list pricing is USD 0.04 – 0.07 per message, with volume tiers below that. The rate depends on the operator, the message category and committed volume — see the Palestine coverage page for the per-operator breakdown.

What delivery rate should I expect in Palestine?

BroadNet does not publish per-country delivery percentages. Every message on these direct operator routes returns a delivery receipt (DLR), so you can measure delivery on your own traffic, and the platform carries a 99.99% uptime SLA. Grey routes deliver until they do not, and give you no receipt when they fail.

Keep exploring

Palestine coverage

All regulations

Test first. Go live with confidence.

Test access on request, reply within one business day. Pay-as-you-go in production. Volume pricing from 1M messages/month.

Request test access Talk to sales

A2P SMS regulations in Palestine. Compliance with MTIT rules and sender-ID registration.