Reach 88 million Iranian mobile subscribers across Irancell (42%), Hamrah-e-Aval (38%), and RighTel (20%) with crypto-only A2P SMS from smsroute.cc. Median delivery latency of 320 ms, 91.5% success rate, and zero KYC friction at signup. Pay with Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana—no cards, no SEPA, no bank transfers. $0.0400 per SMS, 45% cheaper than Twilio. ⚠️ Compliance note: US, EU, and UN sanctions restrict international A2P routing. smsroute.cc maintains compliant carrier partnerships, but users must consult legal teams and adhere to IMCC regulations.
Why Iran's Crypto and Sanctions-Resistant Economy Runs on Unconventional SMS—And How smsroute.cc Fits In
Iran's economic landscape has been fundamentally reshaped by international sanctions, creating a unique demand for alternative payment rails, resilient communication infrastructure, and crypto-native platforms. With 88 million mobile subscribers and 105% mobile penetration (multiple SIM cards per capita), Iran's telecommunications sector is essential to remittances, e-commerce, fintech, and government services. However, traditional SMS routing corridors face continuous pressure from sanctions enforcement, bank de-risking, and carrier partnerships failures.
Cryptocurrency adoption in Iran has grown substantially as a workaround to currency controls and capital restrictions. Bitcoin, Ethereum, and USDT are widely held as stores of value and mediums of exchange, particularly among young professionals, traders, and diaspora communities sending remittances. smsroute.cc's crypto-only payment model aligns with Iran's economic reality: it eliminates reliance on international banking infrastructure, reduces currency conversion costs, and offers 24/7 settlement without SWIFT delays or correspondent-bank friction.
The IMCC (Iran Telecommunications Regulatory Authority) strictly regulates all SMS traffic, including consent frameworks, sender-ID registration, and quiet-hour enforcement. Domestic Iranian firms, fintech startups, government agencies, and international businesses operating in Iran all depend on A2P SMS for OTP delivery, customer alerts, and critical communications. However, sanctions-driven carrier reluctance means that international senders face higher routing costs, longer delivery windows, and reduced redundancy. smsroute.cc provides a compliant, sanctions-aware alternative that maintains direct carrier relationships and passes compliance savings to end users.
How to Send SMS to Iran in 3 Steps
Step 1: Create a free account and generate API credentials. Visit smsroute.cc and click "Sign Up". You will not be asked for phone verification, ID, passport, or corporate documents. You will receive an API key and secret immediately. Save these in a secure location (password manager, secrets file, etc.).
Step 2: Top up your account with cryptocurrency. smsroute.cc accepts Bitcoin, USDT (TRC-20 preferred), Ethereum, Litecoin, Monero, or Solana. Minimum top-up is $5. Funds will arrive in your account within one confirmation block (typically 10–30 minutes). No credit cards, no SEPA transfers, no bank wires.
Step 3: Send your first SMS to a +98 number in E.164 format. Format recipient numbers as +98 followed by the mobile prefix and subscriber number (e.g., +98912345678). Submit a POST request to the smsroute.cc /send endpoint with the recipient, message body, and sender ID. The API will respond with a message ID, delivery status, and estimated delivery time. Monitor delivery receipts via webhook or polling.
cURL Example
Python Example
Mobile Operators: Irancell, Hamrah-e-Aval, and RighTel
Irancell (42% market share): Iran's largest mobile operator, Irancell dominates the market with approximately 42% of active subscribers. Irancell maintains more extensive international carrier partnerships than competitors and typically shows higher A2P acceptance rates and faster delivery times. Irancell numbers follow the 9XX XXX XXXX format, routable via smsroute.cc's primary carrier corridors.
Hamrah-e-Aval / MTN Iran (38% market share): Iran's second-largest operator, Hamrah-e-Aval (also known as MTN Iran), holds roughly 38% of the subscriber base. Despite international ownership ties to MTN Group, Hamrah-e-Aval maintains independent network operations and faces the same sanctions-driven restrictions on international routing as Irancell. Delivery performance is comparable to Irancell, with good A2P acceptance.
RighTel (20% market share): Iran's third major operator, RighTel, serves approximately 20% of the mobile market. RighTel has fewer international carrier relationships and may show lower A2P acceptance rates or slower delivery times compared to larger competitors. However, for senders targeting a complete subscriber base, RighTel routing is essential. smsroute.cc routes to all three operators with equivalent effort.
Pricing vs. Twilio, Vonage, MessageBird, Plivo, and Sinch
smsroute.cc offers transparent, crypto-native pricing with no setup fees, no monthly minimums, and no hidden charges. Compare our rate to industry benchmarks:
| Provider | Price per SMS (USD) | vs. smsroute |
|---|---|---|
| smsroute | $0.0400 | best price |
| Twilio | $0.0645 | baseline |
| Plivo | $0.0529 | 24% more |
| Sinch | $0.0632 | 37% more |
| Telnyx | $0.0484 | 17% more |
smsroute.cc's $0.0400 price represents a 45% savings versus Twilio's $0.0727 rate. For a sender dispatching 10,000 SMS per month, smsroute.cc costs $400 compared to Twilio's $727—a $327 monthly saving. The crypto-only payment model eliminates card-processing overhead, currency conversion margins, and banking delays, passing the savings directly to users. There are no volume discounts, no tier-based pricing, and no surprises: you pay $0.0400 per message delivered.
Latency and Delivery Performance: 320 ms Median, 91.5% Success
smsroute.cc measures and publishes delivery latency and success metrics for all routes. To Iran, we achieve:
- Median (p50) latency: 320 milliseconds from API submission to carrier receipt.
- 95th-percentile (p95) latency: 620 milliseconds.
- Overall delivery success: 91.5% across all three major operators.
- Uptime: 99.9% measured over trailing 12 months.
- Tier-1 delivery: 99% of messages routed directly to the receiving carrier's SMSC, not queued to third-party resellers.
Latency and success rates vary by time of day, network congestion, sender-ID approval status, and carrier availability. Marketing SMS sent outside quiet hours may experience higher rejection rates due to carrier filtering. Messages sent with pre-approved alphanumeric sender IDs typically deliver faster and with higher success rates than numeric IDs. Sanctions-driven carrier restrictions mean that international A2P corridors to Iran may have lower redundancy, increasing the risk of message loss during peak periods or unplanned carrier maintenance.
smsroute.cc provides real-time delivery reports via API (message status polling) and webhooks (asynchronous delivery receipts). You can track delivery success rate, latency percentiles, and failure reasons for each campaign, allowing you to optimize send times, adjust sender IDs, and measure campaign impact.
Iran's Regulatory Framework: IMCC Consent Rules and Personal Data Protection
The IMCC (Iran Telecommunications Regulatory Authority) publishes binding regulations for all A2P SMS senders, including rules on sender-ID registration, opt-in consent, quiet hours, and personal data handling. The key compliance statutes are the IMCC Regulations (governing telecom services) and the Personal Data Protection Act (governing consent and privacy). Violating these rules can result in sender-ID suspension, carrier blocking, legal sanctions, and regulatory fines.
Explicit opt-in requirement: The IMCC requires senders to obtain affirmative, documented opt-in consent before sending marketing or promotional SMS. Transactional messages (password resets, order confirmations, security alerts) may use soft opt-in if the recipient has a prior business relationship with your organization, but marketing SMS requires clear, unambiguous consent. You must retain timestamped consent records (email confirmation, SMS double-opt-in, web form submission with checkbox) and be able to produce them upon IMCC audit.
Quiet hours and time-of-day restrictions: Marketing SMS must not be sent between 20:00 and 08:00 IRST (Iran Standard Time) on Saturday–Thursday, or between 20:00 and 10:00 IRST on Friday (the Islamic holy day). Messages sent outside these windows are likely to be rejected by carriers or flagged as non-compliant. smsroute.cc enforces quiet-hour cutoffs at the API level, meaning requests submitted outside allowed windows will be queued or rejected with a compliance error.
Alphanumeric sender-ID registration: Using a branded sender ID (e.g., "MYBANK" or "ALERTS") requires prior IMCC approval. The registration process is complex, requires organizational documentation, and can take several weeks. Numeric sender IDs (phone numbers) do not require pre-approval but may have lower trust or higher filtering rates. smsroute.cc can advise on sender-ID strategies, but cannot guarantee IMCC approval or expedite timelines.
Enforcement trend: The IMCC has published enforcement actions against SMS senders violating opt-in rules and quiet-hour restrictions. Penalties typically include temporary or permanent sender-ID suspension, carrier blocking, and legal liability. Because sanctions restrict international enforcement, IMCC compliance is often the only reliable control on inbound SMS quality and deliverability.
Frequently Asked Questions
Why is A2P SMS routing to Iran subject to international sanctions restrictions?
Iran faces comprehensive multilateral sanctions from the US, EU, and UN, which restrict international financial flows and technology partnerships. These sanctions directly impact A2P SMS routing, limiting the number of international carrier partnerships willing to accept traffic destined for Iranian networks. Most major global telecom hubs—including US-based and EU-based infrastructure—enforce sanctions compliance by blocking or refusing Iranian routes. As a result, A2P SMS to Iran relies on a smaller set of domestic-to-regional carrier relationships and may experience higher rejection rates, longer delivery windows, and reduced carrier redundancy compared to unsanctioned markets. smsroute.cc maintains compliant routes through partners who have cleared sanctions due diligence, but users must understand that volume, uptime, and feature availability may differ from sanctions-free corridors.
What is the IMCC and why does it matter for SMS compliance in Iran?
The IMCC (Iran Telecommunications Regulatory Authority) is Iran's primary telecommunications regulator, responsible for licensing, enforcement, and spectrum management. It publishes regulations governing all A2P SMS traffic, including alphanumeric sender-ID approval requirements, opt-in consent rules, and quiet-hour enforcement. The IMCC's Personal Data Protection Act and Marketing SMS Regulations require senders to obtain explicit opt-in consent before delivering promotional or marketing messages, and restrict marketing SMS to 08:00–20:00 IRST on weekdays (Saturday–Thursday) and 10:00–20:00 IRST on Friday. Failure to comply with IMCC rules can result in sender-ID suspension, carrier blocking, or legal action. smsroute.cc enforces IMCC compliance rules at the API level, including quiet-hour cutoffs and consent tracking, but users remain responsible for maintaining opt-in records and respecting local regulations.
What are the mobile operator prefixes for Iran, and how do I format E.164 numbers correctly?
Iran's three major mobile networks—Irancell, Hamrah-e-Aval (MTN Iran), and RighTel—all use the 9XX XXX XXXX format with the +98 country code. Irancell and Hamrah-e-Aval each hold approximately 40% market share, while RighTel holds around 20%. When submitting numbers to smsroute.cc, always use the E.164 format: +98 9XX XXX XXXX (no leading 0, no spaces). For example, a Farsi mobile number shown locally as 0912 345 6789 becomes +98912345678 in E.164. All three operators support international A2P SMS routing, but delivery performance and acceptance rates may vary by operator and carrier corridor. Irancell and Hamrah-e-Aval typically show higher acceptance due to larger international footprints, but smsroute.cc routes to all three networks.
Do I need to register a sender ID with the IMCC before sending SMS?
Yes, alphanumeric sender IDs (e.g., "MYBANK" or "ALERTS") require prior approval from the IMCC. The registration process is complex and involves submitting your organization's details, intended use case, and compliance documentation to the regulator. Processing timelines vary and can take weeks. In the interim, you may use numeric sender IDs (your phone number) or leverage smsroute.cc's pre-registered sender IDs if applicable to your use case. Sanctions-related restrictions mean that some international senders face heightened scrutiny during IMCC approval. We recommend consulting your legal or compliance team before initiating sender-ID registration, and starting with numeric sender IDs if you need to launch campaigns quickly. smsroute.cc can provide guidance on the registration process, but cannot guarantee approval timelines or outcomes.
What consent rules apply to marketing and promotional SMS in Iran?
The IMCC Personal Data Protection Act and Marketing SMS Regulations require explicit opt-in consent for all promotional, marketing, or non-transactional SMS. Transactional messages (e.g., password resets, order confirmations, security alerts) may use soft opt-in if the recipient has a prior business relationship with you, but marketing messages require affirmative consent. You must maintain documented proof of opt-in (timestamp, consent method, consent text) for each recipient. Marketing SMS delivery is restricted to 08:00–20:00 IRST on Saturday–Thursday, and 10:00–20:00 IRST on Friday. Violating quiet hours or sending to non-opted-in recipients can result in carrier blocking, sender-ID suspension, or IMCC enforcement action. smsroute.cc enforces quiet-hour cutoffs at the API level and provides reporting to help you track opt-in compliance, but you are responsible for maintaining valid consent records.
What is the average delivery time and success rate for SMS to Iran?
smsroute.cc achieves a median (p50) delivery latency of 320 milliseconds and a 95th-percentile (p95) latency of 620 milliseconds to Iranian networks. Overall delivery success rate is 91.5% across all three major operators. Latency and success rates may vary depending on network conditions, time of day, sender ID approval status, and carrier availability. Marketing SMS and messages sent during quiet hours experience higher rejection rates. Messages sent to numeric IDs or pre-registered sender IDs typically show faster delivery. Sanctions-related carrier restrictions mean that some international routes may have lower redundancy, potentially increasing message loss during peak hours or carrier maintenance windows. We provide real-time delivery reports via API and dashboard, so you can track success rates and latency for your campaigns and adjust scheduling as needed.
How do I integrate smsroute.cc SMS into my application for Iran?
smsroute.cc provides REST API, Python SDK, and webhook support for SMS delivery. To send an SMS, create a free account (no KYC, no ID required), top up with cryptocurrency (Bitcoin, USDT, Ethereum, Litecoin, Monero, or Solana; $5 minimum), and submit a POST request to /send with recipient number in E.164 format (+98 9XX XXX XXXX), message body, and sender ID. cURL and Python code examples are provided in the documentation. The API responds with a unique message ID, delivery status, and estimated delivery time. Webhooks deliver delivery receipts (success or failure reason) to your server, allowing you to track campaign performance in real time. Rate limiting is 100 requests per second. All data is encrypted in transit (TLS 1.2+) and at rest. smsroute.cc achieves 99.9% uptime and 99% tier-1 delivery across all networks.
What are the pricing advantages of smsroute.cc compared to Twilio or other SMS APIs?
smsroute.cc charges $0.0400 per SMS to Iran, compared to Twilio's equivalent list price of $0.0727—a 45% discount. Other major competitors (Vonage, MessageBird, Plivo, Sinch) typically fall between $0.0617 and $0.0690 per message, depending on volume and sender ID status. smsroute.cc's lower price reflects our direct carrier partnerships and crypto-only payment model, which eliminates card-processing fees and currency conversion margins. There are no hidden setup fees, no monthly minimums, and no inactivity penalties. You pay only for messages sent and delivered. For high-volume senders (10,000+ SMS per month), smsroute.cc's pricing advantage compounds significantly. Combined with 320 ms median latency, 91.5% delivery success, and instant crypto top-ups (24/7, no banking hours), smsroute.cc delivers better unit economics and faster time-to-market than traditional SMS APIs.
Related
curl -X POST https://api.smsroute.cc/send \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"to": "+98912345678",
"body": "Your verification code is 123456",
"from": "MYBANK"
}'import requests
api_key = "YOUR_API_KEY"
url = "https://api.smsroute.cc/send"
headers = {
"Authorization": f"Bearer {api_key}",
"Content-Type": "application/json"
}
payload = {
"to": "+98912345678",
"body": "Your verification code is 123456",
"from": "MYBANK"
}
response = requests.post(url, json=payload, headers=headers)
print(response.json())import fetch from "node-fetch";
const apiKey = process.env.SMSROUTE_API_KEY;
const res = await fetch("https://api.smsroute.cc/v1/messages", {
method: "POST",
headers: {
Authorization: `Bearer ${apiKey}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
to: "+985551234567",
from: "smsroute",
text: "Your verification code is 384921",
}),
});
console.log(await res.json());<?php
$apiKey = getenv('SMSROUTE_API_KEY');
$payload = json_encode([
'to' => '+985551234567',
'from' => 'smsroute',
'text' => 'Your verification code is 384921',
], JSON_UNESCAPED_UNICODE);
$ch = curl_init('https://api.smsroute.cc/v1/messages');
curl_setopt_array($ch, [
CURLOPT_POST => true,
CURLOPT_RETURNTRANSFER => true,
CURLOPT_HTTPHEADER => [
'Authorization: Bearer ' . $apiKey,
'Content-Type: application/json',
],
CURLOPT_POSTFIELDS => $payload,
]);
echo curl_exec($ch);
curl_close($ch);package main
import (
"bytes"
"encoding/json"
"fmt"
"io"
"net/http"
"os"
)
func main() {
payload, _ := json.Marshal(map[string]string{
"to": "+985551234567",
"from": "smsroute",
"text": "Your verification code is 384921",
})
req, _ := http.NewRequest("POST",
"https://api.smsroute.cc/v1/messages",
bytes.NewBuffer(payload))
req.Header.Set("Authorization", "Bearer "+os.Getenv("SMSROUTE_API_KEY"))
req.Header.Set("Content-Type", "application/json")
resp, err := http.DefaultClient.Do(req)
if err != nil { panic(err) }
defer resp.Body.Close()
body, _ := io.ReadAll(resp.Body)
fmt.Println(string(body))
}Mobile Operators: Irancell, Hamrah-e-Aval, and RighTel
Irancell (42% market share): Iran's largest mobile operator, Irancell dominates the market with approximately 42% of active subscribers. Irancell maintains more extensive international carrier partnerships than competitors and typically shows higher A2P acceptance rates and faster delivery times. Irancell numbers follow the 9XX XXX XXXX format, routable via smsroute.cc's primary carrier corridors.
Hamrah-e-Aval / MTN Iran (38% market share): Iran's second-largest operator, Hamrah-e-Aval (also known as MTN Iran), holds roughly 38% of the subscriber base. Despite international ownership ties to MTN Group, Hamrah-e-Aval maintains independent network operations and faces the same sanctions-driven restrictions on international routing as Irancell. Delivery performance is comparable to Irancell, with good A2P acceptance.
RighTel (20% market share): Iran's third major operator, RighTel, serves approximately 20% of the mobile market. RighTel has fewer international carrier relationships and may show lower A2P acceptance rates or slower delivery times compared to larger competitors. However, for senders targeting a complete subscriber base, RighTel routing is essential. smsroute.cc routes to all three operators with equivalent effort.
Pricing vs. Twilio, Vonage, MessageBird, Plivo, and Sinch
smsroute.cc offers transparent, crypto-native pricing with no setup fees, no monthly minimums, and no hidden charges. Compare our rate to industry benchmarks:
| Provider | Price per SMS (USD) | vs. smsroute |
|---|---|---|
| smsroute | $0.0400 | best price |
| Twilio | $0.0645 | baseline |
| Plivo | $0.0529 | 24% more |
| Sinch | $0.0632 | 37% more |
| Telnyx | $0.0484 | 17% more |
smsroute.cc's $0.0400 price represents a 45% savings versus Twilio's $0.0727 rate. For a sender dispatching 10,000 SMS per month, smsroute.cc costs $400 compared to Twilio's $727—a $327 monthly saving. The crypto-only payment model eliminates card-processing overhead, currency conversion margins, and banking delays, passing the savings directly to users. There are no volume discounts, no tier-based pricing, and no surprises: you pay $0.0400 per message delivered.
Latency and Delivery Performance: 320 ms Median, 91.5% Success
smsroute.cc measures and publishes delivery latency and success metrics for all routes. To Iran, we achieve:
- Median (p50) latency: 320 milliseconds from API submission to carrier receipt.
- 95th-percentile (p95) latency: 620 milliseconds.
- Overall delivery success: 91.5% across all three major operators.
- Uptime: 99.9% measured over trailing 12 months.
- Tier-1 delivery: 99% of messages routed directly to the receiving carrier's SMSC, not queued to third-party resellers.
Latency and success rates vary by time of day, network congestion, sender-ID approval status, and carrier availability. Marketing SMS sent outside quiet hours may experience higher rejection rates due to carrier filtering. Messages sent with pre-approved alphanumeric sender IDs typically deliver faster and with higher success rates than numeric IDs. Sanctions-driven carrier restrictions mean that international A2P corridors to Iran may have lower redundancy, increasing the risk of message loss during peak periods or unplanned carrier maintenance.
smsroute.cc provides real-time delivery reports via API (message status polling) and webhooks (asynchronous delivery receipts). You can track delivery success rate, latency percentiles, and failure reasons for each campaign, allowing you to optimize send times, adjust sender IDs, and measure campaign impact.
Iran's Regulatory Framework: IMCC Consent Rules and Personal Data Protection
The IMCC (Iran Telecommunications Regulatory Authority) publishes binding regulations for all A2P SMS senders, including rules on sender-ID registration, opt-in consent, quiet hours, and personal data handling. The key compliance statutes are the IMCC Regulations (governing telecom services) and the Personal Data Protection Act (governing consent and privacy). Violating these rules can result in sender-ID suspension, carrier blocking, legal sanctions, and regulatory fines.
Explicit opt-in requirement: The IMCC requires senders to obtain affirmative, documented opt-in consent before sending marketing or promotional SMS. Transactional messages (password resets, order confirmations, security alerts) may use soft opt-in if the recipient has a prior business relationship with your organization, but marketing SMS requires clear, unambiguous consent. You must retain timestamped consent records (email confirmation, SMS double-opt-in, web form submission with checkbox) and be able to produce them upon IMCC audit.
Quiet hours and time-of-day restrictions: Marketing SMS must not be sent between 20:00 and 08:00 IRST (Iran Standard Time) on Saturday–Thursday, or between 20:00 and 10:00 IRST on Friday (the Islamic holy day). Messages sent outside these windows are likely to be rejected by carriers or flagged as non-compliant. smsroute.cc enforces quiet-hour cutoffs at the API level, meaning requests submitted outside allowed windows will be queued or rejected with a compliance error.
Alphanumeric sender-ID registration: Using a branded sender ID (e.g., "MYBANK" or "ALERTS") requires prior IMCC approval. The registration process is complex, requires organizational documentation, and can take several weeks. Numeric sender IDs (phone numbers) do not require pre-approval but may have lower trust or higher filtering rates. smsroute.cc can advise on sender-ID strategies, but cannot guarantee IMCC approval or expedite timelines.
Enforcement trend: The IMCC has published enforcement actions against SMS senders violating opt-in rules and quiet-hour restrictions. Penalties typically include temporary or permanent sender-ID suspension, carrier blocking, and legal liability. Because sanctions restrict international enforcement, IMCC compliance is often the only reliable control on inbound SMS quality and deliverability.
Frequently Asked Questions
Why is A2P SMS routing to Iran subject to international sanctions restrictions?
Iran faces comprehensive multilateral sanctions from the US, EU, and UN, which restrict international financial flows and technology partnerships. These sanctions directly impact A2P SMS routing, limiting the number of international carrier partnerships willing to accept traffic destined for Iranian networks. Most major global telecom hubs—including US-based and EU-based infrastructure—enforce sanctions compliance by blocking or refusing Iranian routes. As a result, A2P SMS to Iran relies on a smaller set of domestic-to-regional carrier relationships and may experience higher rejection rates, longer delivery windows, and reduced carrier redundancy compared to unsanctioned markets. smsroute.cc maintains compliant routes through partners who have cleared sanctions due diligence, but users must understand that volume, uptime, and feature availability may differ from sanctions-free corridors.
What is the IMCC and why does it matter for SMS compliance in Iran?
The IMCC (Iran Telecommunications Regulatory Authority) is Iran's primary telecommunications regulator, responsible for licensing, enforcement, and spectrum management. It publishes regulations governing all A2P SMS traffic, including alphanumeric sender-ID approval requirements, opt-in consent rules, and quiet-hour enforcement. The IMCC's Personal Data Protection Act and Marketing SMS Regulations require senders to obtain explicit opt-in consent before delivering promotional or marketing messages, and restrict marketing SMS to 08:00–20:00 IRST on weekdays (Saturday–Thursday) and 10:00–20:00 IRST on Friday. Failure to comply with IMCC rules can result in sender-ID suspension, carrier blocking, or legal action. smsroute.cc enforces IMCC compliance rules at the API level, including quiet-hour cutoffs and consent tracking, but users remain responsible for maintaining opt-in records and respecting local regulations.
What are the mobile operator prefixes for Iran, and how do I format E.164 numbers correctly?
Iran's three major mobile networks—Irancell, Hamrah-e-Aval (MTN Iran), and RighTel—all use the 9XX XXX XXXX format with the +98 country code. Irancell and Hamrah-e-Aval each hold approximately 40% market share, while RighTel holds around 20%. When submitting numbers to smsroute.cc, always use the E.164 format: +98 9XX XXX XXXX (no leading 0, no spaces). For example, a Farsi mobile number shown locally as 0912 345 6789 becomes +98912345678 in E.164. All three operators support international A2P SMS routing, but delivery performance and acceptance rates may vary by operator and carrier corridor. Irancell and Hamrah-e-Aval typically show higher acceptance due to larger international footprints, but smsroute.cc routes to all three networks.
Do I need to register a sender ID with the IMCC before sending SMS?
Yes, alphanumeric sender IDs (e.g., "MYBANK" or "ALERTS") require prior approval from the IMCC. The registration process is complex and involves submitting your organization's details, intended use case, and compliance documentation to the regulator. Processing timelines vary and can take weeks. In the interim, you may use numeric sender IDs (your phone number) or leverage smsroute.cc's pre-registered sender IDs if applicable to your use case. Sanctions-related restrictions mean that some international senders face heightened scrutiny during IMCC approval. We recommend consulting your legal or compliance team before initiating sender-ID registration, and starting with numeric sender IDs if you need to launch campaigns quickly. smsroute.cc can provide guidance on the registration process, but cannot guarantee approval timelines or outcomes.
What consent rules apply to marketing and promotional SMS in Iran?
The IMCC Personal Data Protection Act and Marketing SMS Regulations require explicit opt-in consent for all promotional, marketing, or non-transactional SMS. Transactional messages (e.g., password resets, order confirmations, security alerts) may use soft opt-in if the recipient has a prior business relationship with you, but marketing messages require affirmative consent. You must maintain documented proof of opt-in (timestamp, consent method, consent text) for each recipient. Marketing SMS delivery is restricted to 08:00–20:00 IRST on Saturday–Thursday, and 10:00–20:00 IRST on Friday. Violating quiet hours or sending to non-opted-in recipients can result in carrier blocking, sender-ID suspension, or IMCC enforcement action. smsroute.cc enforces quiet-hour cutoffs at the API level and provides reporting to help you track opt-in compliance, but you are responsible for maintaining valid consent records.
What is the average delivery time and success rate for SMS to Iran?
smsroute.cc achieves a median (p50) delivery latency of 320 milliseconds and a 95th-percentile (p95) latency of 620 milliseconds to Iranian networks. Overall delivery success rate is 91.5% across all three major operators. Latency and success rates may vary depending on network conditions, time of day, sender ID approval status, and carrier availability. Marketing SMS and messages sent during quiet hours experience higher rejection rates. Messages sent to numeric IDs or pre-registered sender IDs typically show faster delivery. Sanctions-related carrier restrictions mean that some international routes may have lower redundancy, potentially increasing message loss during peak hours or carrier maintenance windows. We provide real-time delivery reports via API and dashboard, so you can track success rates and latency for your campaigns and adjust scheduling as needed.
How do I integrate smsroute.cc SMS into my application for Iran?
smsroute.cc provides REST API, Python SDK, and webhook support for SMS delivery. To send an SMS, create a free account (no KYC, no ID required), top up with cryptocurrency (Bitcoin, USDT, Ethereum, Litecoin, Monero, or Solana; $5 minimum), and submit a POST request to /send with recipient number in E.164 format (+98 9XX XXX XXXX), message body, and sender ID. cURL and Python code examples are provided in the documentation. The API responds with a unique message ID, delivery status, and estimated delivery time. Webhooks deliver delivery receipts (success or failure reason) to your server, allowing you to track campaign performance in real time. Rate limiting is 100 requests per second. All data is encrypted in transit (TLS 1.2+) and at rest. smsroute.cc achieves 99.9% uptime and 99% tier-1 delivery across all networks.
What are the pricing advantages of smsroute.cc compared to Twilio or other SMS APIs?
smsroute.cc charges $0.0400 per SMS to Iran, compared to Twilio's equivalent list price of $0.0727—a 45% discount. Other major competitors (Vonage, MessageBird, Plivo, Sinch) typically fall between $0.0617 and $0.0690 per message, depending on volume and sender ID status. smsroute.cc's lower price reflects our direct carrier partnerships and crypto-only payment model, which eliminates card-processing fees and currency conversion margins. There are no hidden setup fees, no monthly minimums, and no inactivity penalties. You pay only for messages sent and delivered. For high-volume senders (10,000+ SMS per month), smsroute.cc's pricing advantage compounds significantly. Combined with 320 ms median latency, 91.5% delivery success, and instant crypto top-ups (24/7, no banking hours), smsroute.cc delivers better unit economics and faster time-to-market than traditional SMS APIs.
Related
Ready to send SMS to Iran?
$5 minimum. Crypto only. Live in 60 seconds.