A2P SMS, OTP, and sender ID rules in Nepal.
BroadNet delivers A2P SMS and OTP in Nepal over direct connections to Nepal Telecom and Ncell, with NTA sender ID registration in 7-14 business days. Operator-direct termination into Nepal Telecom (NTC) and Ncell with NTA-aligned sender ID registration handled in-house.
From-rates by channel in Nepal
- SMSfrom$0.0360per SMSIndicative list rate, reviewed September 24, 2026Volume pricing available
- OTPRequest a quote Channel list rate from $0.0120 per verification (all markets)
- WhatsAppRequest a quote Channel list rate from $0.0135 per template message (all markets)
- RCSRequest a quote Channel list rate from $0.0080 per session (all markets)
- VoiceRequest a quote Channel list rate from $0.0150 per minute (all markets)
Indicative list prices in USD, excluding taxes and sender-ID registration fees. Final per-operator pricing is confirmed in your quote.
The Nepal A2P market at a glance.
Nepal is served by 2 licensed mobile networks (Nepal Telecom and Ncell) covering a subscriber base of 38M. Nepal Telecommunications Authority (NTA) regulates A2P messaging and sender-ID registration. NTA + operator sender ID registration. Nepali (Devanagari) and English supported. Nepal IT Bill 2019 governs PII.
Technical facts for Nepal
Network codes, message lengths and sender-ID rules in one table. Segment lengths are the GSM standard values (3GPP TS 23.038).
| Mobile country code (MCC) | 429 |
|---|---|
| Dialling code | +977 |
| Operators (MCC-MNC) |
|
| 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 | NTA (Nepal Telecommunications Authority) |
| Sender-ID rules | NTA + operator sender ID registration. Nepali (Devanagari) and English supported. |
| Sender-ID lead time | 7-14 business days |
Channels live in Nepal.
One contract, one contact model. Fall back between SMS, WhatsApp, and Voice with shared opt-in evidence and a single audit trail.
SMS
Operator-direct A2P with local-language script support where applicable.
OTP
Sub-4-second median; flash-call OTP available in select markets as a low-latency alternative.
WhatsApp Business API live. High consumer penetration across South and Southeast Asia.
RCS
RCS Business Messaging available on Google's MaaP where the carrier has enabled it.
Voice
Voice OTP and TTS available as fallback; recommended for high-fraud verticals.
How do I register a sender ID in Nepal?
Filed end-to-end by BroadNet's compliance team — KYC pack, operator approval, and renewal cycles handled on your behalf.
NTA · Nepal Telecom and Ncell
- Format
- Alphanumeric (local script supported), up to 11 chars
- Pre-registration
- Set by the operators; BroadNet confirms the current requirements during onboarding
- KYC documents
- Confirmed during onboarding
- Renewal cycle
- Confirmed during onboarding
- Common rejection causes
- Sender-ID rules are set by the operators; BroadNet confirms current requirements during onboarding.
What OTP delivery looks like in Nepal.
Latency profile, peak-hour behaviour, recommended fallback chain, and the fraud signals our firewall watches in-market.
Typical latency window
Median 3.5 s with a 95th-percentile inside 8 seconds across operator-direct binds. Two-shot delivery confirmed by DLR.
Peak-hour behaviour
Operator throughput holds steady through local business peaks; throttling kicks in only during outlier mass-send events. BroadNet load-shapes per-MNO to avoid firewall blocks.
Fallback chain
Recommended fallback: WhatsApp OTP → Voice OTP after 30s. Flash-call OTP is an option in markets where the carrier permits it.
Fraud signals we watch
Flash-call abuse, SIM-farm OTP harvesting, and template variance attacks are the dominant signals. BroadNet's anomaly engine watches per-MSISDN velocity.
What you can — and can't — send.
Opt-in, opt-out, quiet hours, content restrictions, and the penalty regime for the Nepal market.
Opt-in
Verifiable opt-in required, with traffic categorised by use case at the time of registration. DLT-style template approval applies in several markets.
Opt-out
STOP keyword and DND-registry suppression applied automatically. Records retained per regulator requirements.
Quiet hours
We have not found a regulator-published time-of-day window for promotional SMS in this market. Agree sending hours with the operator and schedule promotional sends for the recipient's local daytime; transactional traffic runs 24/7.
Content restrictions
Local-language templates preferred. Loan, gambling, crypto, and supplements blocked at the operator firewall.
Regulator penalties
NTA penalties for off-template, off-category, or grey-route traffic — fines, sender-ID delisting, and template re-registration required.
Termination,
network by network.
The route status column shows how each operator is reached — a direct BroadNet bind or a labelled partner route. No grey-route exposure. Route grades are indicative planning guides, not live measurements.
| Operator | MCC-MNC | Route status | Grade | A2P rate (typ.) |
|---|---|---|---|---|
| Nepal Telecom (NTC) | 429-01 | Direct | A+ | USD 0.0383 |
| Ncell | 429-02 | Direct | A+ | USD 0.036 |
Rates shown are typical pay-as-you-go for transactional traffic. Promotional traffic is priced separately, and volume tiers reduce both. See the rate-card section below for the full ladder.
| Tier | Transactional | Promotional | Notes |
|---|---|---|---|
| Pay-as-you-go | USD 0.0360 | USD 0.0439 | List rate up to 100K messages/month |
| Growth · 100K+ | USD 0.0317 | USD 0.0387 | Auto-tier discount |
| Volume · 1M+ | USD 0.0266 | USD 0.0325 | Includes quarterly route review |
| Enterprise | Custom | Custom | Direct operator pricing + signed SLA |
NTA + operator sender ID registration: 7-14 business days.
Open the Nepal rate cardCompliant
by default.
Every send is pre-screened against Nepal Telecommunications Authority (NTA) rules, the operator firewalls, and the local privacy framework. Where registration is required, BroadNet files the paperwork on your behalf.
Nepal IT Bill 2019 governs PII.
Full regulatory deep-diveNTA sender ID
Sender IDs registered via operator route.
Nepali (Devanagari)
UCS-2 routing native.
IT Bill 2019
Nepal PII framework.
Programmes that work well in Nepal.
Where the BroadNet operator-direct footprint, the local regulator regime, and consumer messaging habits line up.
- 01
E-commerce OTP, order confirmation, and dispatch alerts at festival-season scale.
- 02
Fintech, lending, and digital-wallet OTP and KYC-step notifications.
- 03
Ride-hail, food-delivery, and logistics rider-and-rider coordination messages.
- 04
Travel and airline itinerary changes, check-in, and visa-status updates.
- 05
Government citizen-services notifications and public-sector campaign messaging.
What we run for Nepal senders.
The operator relationships, the compliance workflow, the routing position — all on a single contract and a single account team.
Operator-direct binds with Nepal Telecom and Ncell — no aggregator hops, no grey-route exposure.
Sender-ID requirements confirmed during onboarding.
Live in 8–19 business days from test-access request to production (set by the sender-ID lead time), with a dedicated solution engineer through go-live.
Typical delivery rate 98.6% and typical OTP delivery time 3.5 s across the country.
Template approval and DLT-style category management handled in-platform.
Local-language UCS-2 routing first-class — no transliteration penalty.
Buyer questions about Nepal.
The questions BroadNet's sales engineers field every week from teams shipping into this market.
What's the typical sender-ID approval time with NTA in Nepal?
Typical lead time: 7-14 business days. BroadNet confirms the current sender-ID requirements and documents during onboarding.
Are BroadNet's routes to Nepal operator-direct?
Yes — every operator on the public coverage table is a direct A2P bind. No aggregator hops, no grey-route exposure. Route grades are indicative planning guides, not live measurements.
Can I send marketing SMS in Nepal without prior consent?
No. Verifiable opt-in is required across every market BroadNet supports, with the consent source, timestamp, and channel logged. Transactional OTP and account-level alerts are exempt from marketing-consent rules.
Which channels do you support for Nepal — SMS only, or also WhatsApp and Voice?
SMS, OTP, WhatsApp Business, and Voice OTP are all supported. RCS Business Messaging is available where the local operator has launched it. All channels run on the same contract and contact model.
Can I be billed in a currency other than USD?
Yes — billing is available in USD. Volume tiers apply automatically from 100K messages a month.
Do I need a local-language version of my templates for Nepal?
For consumer-facing transactional and marketing traffic, yes — a local-script template materially improves trust and recall. BroadNet handles UCS-2 routing without a price or SLA penalty.
What happens if a route to Nepal degrades?
BroadNet runs continuous DLR monitoring on every operator. If a route flaps, traffic is automatically re-shaped to the next-best operator on the same destination, and your account manager is notified with a remediation note within the hour.
Do you sign an SLA for traffic to Nepal?
Yes — traffic to this market runs under BroadNet's standard SLA: 99.99% monthly platform uptime, with service credits on enterprise contracts. Support response targets and the credit schedule are published on our Support & SLA page.
A ready-to-adapt template for Nepal.
In the local script alongside English. Copy, swap the brand, and we'll register it as part of your sender-ID onboarding.
- Mobile subscribers
- 38M
- Sender ID lead
- 7-14 business days
- Time-to-launch
- Live in 8–19 business days from test-access request to production (set by the sender-ID lead time)
- Billed in
- USD
Your code is 619204.
तपाईंको कोड 619204 हो।
NTA + operator sender ID registration. Nepali (Devanagari) and English supported.
Continue across the region.
See how enterprises put these operator-direct routes to work in banking and finance messaging and e-commerce and retail messaging, or weigh the options on the messaging platform comparison hub.
More on Nepal
Request current route availability for Nepal.
Live in 8–19 business days from test-access request to production (set by the sender-ID lead time). Sender ID filed with NTA on your behalf. Billed in USD from day one.
$ curl -X POST https://api.broadnet.me/sms/sendSms·mno = +977