A2P SMS, OTP, and sender ID rules in Romania.
BroadNet delivers A2P SMS and OTP in Romania over direct connections to Vodafone Romania, Orange Romania, Digi Romania, and Telekom Romania, with ANCOM sender ID registration in 5-10 business days. Direct termination into Vodafone Romania, Orange Romania, Digi, and Telekom Romania with ANCOM-aligned sender ID registration.
From-rates by channel in Romania
- SMSfrom$0.0440per 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 Romania A2P market at a glance.
Romania is served by 4 licensed mobile networks (Vodafone Romania, Orange Romania, Digi Romania, and Telekom Romania) covering a subscriber base of 22M. Autoritatea Națională pentru Administrare și Reglementare în Comunicații (ANCOM) regulates A2P messaging and sender-ID registration. Alphanumeric sender ID registration via operator. Romanian diacritics supported. GDPR + ANSPDCP enforcement.
Technical facts for Romania
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) | 226 |
|---|---|
| Dialling code | +40 |
| 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 | ANCOM (Autoritatea Națională pentru Administrare și Reglementare în Comunicații) |
| Sender-ID rules | Alphanumeric sender ID registration via operator. Romanian diacritics supported. |
| Sender-ID lead time | 5-10 business days |
Channels live in Romania.
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. Numeric senders preferred for transactional; alphanumeric supported.
OTP
Sub-3-second median across tier-1 operators. PSD2 SCA-grade reliability.
WhatsApp Business API live; growing share for customer-care and re-engagement traffic.
RCS
RCS Business Messaging rolled out on major operators via Google MaaP; verified senders supported.
Voice
Voice OTP / TTS available as SMS fallback. PSD2-grade audit trail.
How do I register a sender ID in Romania?
Filed end-to-end by BroadNet's compliance team — KYC pack, operator approval, and renewal cycles handled on your behalf.
ANCOM · Vodafone Romania and Orange Romania
- Format
- Alphanumeric, up to 11 chars (numeric long-code also supported)
- 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 Romania.
Latency profile, peak-hour behaviour, recommended fallback chain, and the fraud signals our firewall watches in-market.
Typical latency window
Median 2.7 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: Voice OTP after 30s no-delivery. WhatsApp OTP increasingly used as a low-friction alternative.
Fraud signals we watch
SIM-swap attempts on PSD2-SCA flows, robocall-style voice OTP abuse, and number-rented OTP harvesting. PSD2 audit-trail retained for 13 months.
What you can — and can't — send.
Opt-in, opt-out, quiet hours, content restrictions, and the penalty regime for the Romania market.
Opt-in
GDPR-compliant opt-in required. Double opt-in is the operator-preferred standard for marketing.
Opt-out
STOP keyword honoured network-wide. Opt-out is one-step and irreversible until the recipient re-consents.
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
Sender-ID brand-impersonation is policed; templates flagged against fraud heuristics. PSD2-SCA flows must use a dedicated transactional sender ID.
Regulator penalties
ANCOM can fine for breaches; GDPR penalties run up to 4% of global turnover for the underlying data-processing violation.
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.) |
|---|---|---|---|---|
| Vodafone Romania | 226-01 | Direct | A+ | EUR 0.0472 |
| Orange Romania | 226-10 | Direct | A+ | EUR 0.045 |
| Digi Romania | 226-05 | Direct | A | EUR 0.0427 |
| Telekom Romania | 226-03 | Direct | A | EUR 0.0405 |
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 | EUR 0.0405 | EUR 0.0478 | List rate up to 100K messages/month |
| Growth · 100K+ | EUR 0.0356 | EUR 0.0421 | Auto-tier discount |
| Volume · 1M+ | EUR 0.0300 | EUR 0.0354 | Includes quarterly route review |
| Enterprise | Custom | Custom | Direct operator pricing + signed SLA |
ANCOM + operator sender ID registration: 5-10 business days.
Open the Romania rate cardCompliant
by default.
Every send is pre-screened against Autoritatea Națională pentru Administrare și Reglementare în Comunicații (ANCOM) rules, the operator firewalls, and the local privacy framework. Where registration is required, BroadNet files the paperwork on your behalf.
GDPR + ANSPDCP enforcement.
Full regulatory deep-diveANCOM sender ID
Sender IDs registered via operator.
GDPR + ANSPDCP
GDPR plus Romanian ANSPDCP enforcement.
Romanian diacritics
UCS-2 routes carry Romanian diacritics natively.
Programmes that work well in Romania.
Where the BroadNet operator-direct footprint, the local regulator regime, and consumer messaging habits line up.
- 01
PSD2-SCA OTP and banking transaction alerts under the local financial regime.
- 02
B2B SaaS account onboarding, MFA, and operational alerts.
- 03
E-commerce shipment and click-and-collect notifications.
- 04
Healthcare appointment reminders aligned with national health-data rules.
- 05
Mobility, ride-hail, and travel itinerary updates with multilingual templates.
What we run for Romania senders.
The operator relationships, the compliance workflow, the routing position — all on a single contract and a single account team.
Operator-direct binds with Vodafone Romania, Orange Romania, and Digi Romania — no aggregator hops, no grey-route exposure.
Sender-ID requirements confirmed during onboarding.
Live in 5–15 business days from test-access request to production, with a dedicated solution engineer through go-live.
Typical delivery rate 99.3% and typical OTP delivery time 2.7 s across the country.
GDPR-aligned operations and EU-resident data plane; PSD2-SCA audit trail retained per regulator guidance.
Numeric and alphanumeric senders supported, with operator-preferred defaults applied automatically.
Buyer questions about Romania.
The questions BroadNet's sales engineers field every week from teams shipping into this market.
What's the typical sender-ID approval time with ANCOM in Romania?
Typical lead time: 5-10 business days. BroadNet confirms the current sender-ID requirements and documents during onboarding.
Are BroadNet's routes to Romania 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 Romania 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 Romania — 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 EUR?
Yes — billing is available in EUR / USD / RON. Volume tiers apply automatically from 100K messages a month.
Do I need a local-language version of my OTP for Romania?
Not strictly required for OTP, but operators prefer the body to match the registered template. Marketing traffic should be in the local language — GDPR consent must be in a language the recipient understands.
What happens if a route to Romania 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 Romania?
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 Romania.
In the local script alongside English. Copy, swap the brand, and we'll register it as part of your sender-ID onboarding.
- Mobile subscribers
- 22M
- Sender ID lead
- 5-10 business days
- Time-to-launch
- Live in 5–15 business days from test-access request to production
- Billed in
- EUR / USD / RON
Your code is 384921.
Codul tău de verificare este 384921.
Alphanumeric sender ID registration via operator. Romanian diacritics 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 Romania
Request current route availability for Romania.
Live in 5–15 business days from test-access request to production. Sender ID filed with ANCOM on your behalf. Billed in EUR from day one.
$ curl -X POST https://api.broadnet.me/sms/sendSms·mno = +40