smsroute is a crypto-only A2P SMS gateway. We deliver outbound SMS to 149 countries through direct operator interconnects, priced from $0.004 per message, paid for with Bitcoin, USDT, Ethereum, Litecoin, Monero, or Solana. Signup takes an email and about thirty seconds — no KYC, no business registration, no card.

What we are

smsroute is a transit-layer SMS gateway. We sit between application-to-person (A2P) senders — SaaS companies, fintechs, logistics platforms, e-commerce backends, games, fraud-prevention vendors — and the world's mobile carriers. Our API accepts a destination number in E.164 format and a message body, selects a route to the terminating carrier, submits the message, and returns a delivery receipt. That is the entire product surface: a REST API, a dashboard, and a crypto billing channel behind it.

We do not run an inbox, a voice product, an email service, or a chat stack. We are focused, single-purpose A2P SMS — the workload where price and routing reliability matter more than feature breadth.

Why crypto-only

Three reasons — cost, privacy, and global reach — and they reinforce each other.

Cost efficiency

Card-processor fees on retail payments run 2.9% + $0.30 per transaction on the low end and reach 4-5% with chargeback reserves and cross-border surcharges. For a product priced at fractions of a cent per unit, that overhead is larger than the cost of goods. Removing the card rail is how we can offer $0.004-per-SMS routes to countries where Twilio charges 5-20× more. Every fee we don't pay Stripe is a fee that doesn't land on your per-message price.

Privacy

Payment metadata is surveillance metadata. A card-funded SMS account produces a merchant-of-record line item in the customer's bank statement, an IP-mapped row in the processor's risk database, and a 3D Secure auth hop that fingerprints the device. Crypto top-ups bypass this entire trail. For users whose threat model includes coercive access to payment records — journalists, NGOs operating under authoritarian regimes, small businesses in jurisdictions with abusive banking systems — this matters practically, not theoretically.

Global reach

Our user base is distributed across 149 countries, including many where the incumbent card networks don't operate cleanly — Venezuela under sanctions, Iran under sanctions, Nigeria under FX controls, Argentina under dollar restrictions. A user in any of these places can fund a balance via USDT in under a minute without needing a US or EU bank relationship. The SMS product is global; the payment rail has to be global too.

How we route

smsroute operates three regional points of presence, each peered directly with the dominant operators in its region. When you submit a send, our router picks the POP with the lowest handset latency to the destination country and attempts the highest-quality direct route first, falling back to a secondary route only if the primary is congested or the carrier tier is unavailable.

Frankfurt POP (eu-central)
Europe, UK, MENA. Direct peering with Deutsche Telekom via DE-CIX, Vodafone DE, Orange FR, BT UK, TIM IT. 142 ms median delivery to German handsets, 310 ms 95th percentile.
Singapore POP (ap-southeast)
Southeast Asia, India, East Asia, Pacific. Direct interconnects with Singtel, Globe, Smart, XL Axiata, Telkomsel, Airtel India (via DLT-registered templates), Jio.
São Paulo POP (sa-east)
Brazil, Argentina, Mexico, Chile, Colombia, Peru. Direct routes to Vivo, Claro, TIM Brasil, Movistar Argentina, Telcel Mexico, Entel Chile.

Each POP terminates to multiple carrier-grade Session Management endpoints with SMPP and REST ingress, runs an independent routing engine, and synchronises delivery-receipt state back to the central ledger over a private backbone. No single-region dependency — if Frankfurt is brown, your EU traffic re-routes through Singapore with a small additional latency cost.

What makes smsroute different

The CPaaS market is dominated by three US-listed giants — Twilio, Vonage (Ericsson), and MessageBird (Bird). Their strengths are feature breadth, enterprise sales motion, and US 10DLC registration machinery. Their weaknesses are international price, friction at signup, and a payment rail that assumes every customer has a US or EU corporate card.

smsroute is built for the workloads those weaknesses hurt: international traffic, low-margin senders, non-US-incorporated customers, and anyone whose operational security requires crypto-native payment.

Dimension smsroute Twilio / Vonage / MessageBird
Price (international routes) From $0.004, 30-70% cheaper on most routes Retail CPaaS rates, enterprise markup
Signup Email only, ~30 seconds, no KYC Email + phone verification + business-registration prompt + card
Payment Crypto only — BTC, USDT, ETH, LTC, XMR, SOL Card, ACH, SEPA, wire
Billing model Pay-as-you-go, balance-based, non-refundable credits Postpaid invoicing, monthly commits, SLA tiers
Compliance scope Per-country guidance, transit-provider posture Full enterprise compliance suite (TCPA attestation, 10DLC registration assistance, HIPAA BAA)
Product breadth A2P SMS only SMS, voice, WhatsApp, email, video, verify, flex

If you need a HIPAA Business Associate Agreement, signed enterprise MSAs with SLA credits, or a sales rep on a named-account plan, the incumbents are the right fit and we will say so. If you need to send international A2P SMS at wholesale-adjacent prices, fund the account with crypto, and skip a KYC review at signup, smsroute is built for you.

Compliance posture

We are transit, not a controller of your message content. Under GDPR you remain the controller; under CCPA you remain the business; under TCPA you remain the sender of record. Our job is to carry the message and to flag country-specific requirements (§ 7 UWG in Germany, DLT template registration in India, PDPA consent in Singapore, HT-SMS rules in UAE) on the destination country pages so you know what applies before you send.

Carrier-imposed rules (10DLC registration in the US, sender-ID pre-registration for Thailand and KSA, alphanumeric blocks in France) are enforced by the operators themselves; our routing engine surfaces the rejection reason in the delivery receipt with a documented error code so you can fix the submission and retry.

Roadmap, honestly

We don't publish a product roadmap for competitive reasons, but a few commitments are stable: A2P SMS only (no voice, no WhatsApp Business, no email), crypto-only payment (no card rail is coming), per-country pricing transparency (the grid stays public and is updated monthly), and no ad-tech business model (we sell SMS delivery, not data).

See per-country pricing on the pricing grid or create an account — email only, crypto top-up from $5.

Related

Gateway Infrastructure Dossier

Global Backbone Topology & Zero-PII Telecom Architecture

Technical specifications of SMSRoute's decentralized edge network, Tier-1 carrier interconnects, and ephemeral memory routing.

Direct SS7 Signaling Interconnects

Eliminates wholesale aggregator hops. Direct MAP and ISUP signaling delivers sub-400ms median OTP delivery in primary markets.

Zero-PII Volatile RAM Routing

Mobile phone numbers and SMS payloads are buffered strictly in volatile memory. Discarded immediately after carrier DLR acknowledgment.

Global Anycast SMPP Nodes

4 global data center clusters: Equinix FR2 (Frankfurt), Ashburn VA (iad1), Singapore (sin1), and São Paulo (gru1).

First-Party Proprietary Telemetry

Live Carrier Route Latency & SMPP DLR Success Telemetry

Real-time telemetry measured across direct SS7 interconnects, local SMPP binds, and global operator gateways. Updated continuously via live probe handshakes.

Live Telemetry: Active • Rolling 1-Hour Window
Frankfurt, DE (fra1) ONLINE
18.4 ms
SMPP Submit ACK p50
N. Virginia, US (iad1) ONLINE
24.2 ms
SMPP Submit ACK p50
Singapore (sin1) ONLINE
31.8 ms
SMPP Submit ACK p50
São Paulo, BR (gru1) ONLINE
42.1 ms
SMPP Submit ACK p50
Carrier & Destination MCC-MNC Interconnect p50 Latency p95 Latency DLR Success Rate Route Health
🇺🇸 AT&T Mobility (US) 310-410 Direct SS7 382 ms 1,040 ms 99.88% Optimal
🇺🇸 Verizon Wireless (US) 311-480 Direct SS7 412 ms 1,120 ms 99.92% Optimal
🇬🇧 EE / BT Group (UK) 234-30 Local SMPP 320 ms 860 ms 99.94% Optimal
🇩🇪 Deutsche Telekom (DE) 262-01 Local SMPP 295 ms 790 ms 99.96% Optimal
🇫🇷 Orange France (FR) 208-01 Direct SS7 340 ms 910 ms 99.91% Optimal
🇮🇳 Reliance Jio (IN) 405-840 DLT Scrubbed 485 ms 1,380 ms 99.18% Operational
🇰🇪 Safaricom (KE) 639-02 Local SMPP 410 ms 1,150 ms 99.74% Optimal
* Delivery Latency is defined as duration between SMPP submit_sm PDU dispatch and carrier deliver_sm (DLR) ACK return. Zero SMS body logging • Ephemeral in-memory routing
Gateway Infrastructure Dossier

Global Backbone Topology & Zero-PII Telecom Architecture

Technical specifications of SMSRoute's decentralized edge network, Tier-1 carrier interconnects, and ephemeral memory routing.

Direct SS7 Signaling Interconnects

Eliminates wholesale aggregator hops. Direct MAP and ISUP signaling delivers sub-400ms median OTP delivery in primary markets.

Zero-PII Volatile RAM Routing

Mobile phone numbers and SMS payloads are buffered strictly in volatile memory. Discarded immediately after carrier DLR acknowledgment.

Global Anycast SMPP Nodes

4 global data center clusters: Equinix FR2 (Frankfurt), Ashburn VA (iad1), Singapore (sin1), and São Paulo (gru1).

First-Party Proprietary Telemetry

Live Carrier Route Latency & SMPP DLR Success Telemetry

Real-time telemetry measured across direct SS7 interconnects, local SMPP binds, and global operator gateways. Updated continuously via live probe handshakes.

Live Telemetry: Active • Rolling 1-Hour Window
Frankfurt, DE (fra1) ONLINE
18.4 ms
SMPP Submit ACK p50
N. Virginia, US (iad1) ONLINE
24.2 ms
SMPP Submit ACK p50
Singapore (sin1) ONLINE
31.8 ms
SMPP Submit ACK p50
São Paulo, BR (gru1) ONLINE
42.1 ms
SMPP Submit ACK p50
Carrier & Destination MCC-MNC Interconnect p50 Latency p95 Latency DLR Success Rate Route Health
🇺🇸 AT&T Mobility (US) 310-410 Direct SS7 382 ms 1,040 ms 99.88% Optimal
🇺🇸 Verizon Wireless (US) 311-480 Direct SS7 412 ms 1,120 ms 99.92% Optimal
🇬🇧 EE / BT Group (UK) 234-30 Local SMPP 320 ms 860 ms 99.94% Optimal
🇩🇪 Deutsche Telekom (DE) 262-01 Local SMPP 295 ms 790 ms 99.96% Optimal
🇫🇷 Orange France (FR) 208-01 Direct SS7 340 ms 910 ms 99.91% Optimal
🇮🇳 Reliance Jio (IN) 405-840 DLT Scrubbed 485 ms 1,380 ms 99.18% Operational
🇰🇪 Safaricom (KE) 639-02 Local SMPP 410 ms 1,150 ms 99.74% Optimal
* Delivery Latency is defined as duration between SMPP submit_sm PDU dispatch and carrier deliver_sm (DLR) ACK return. Zero SMS body logging • Ephemeral in-memory routing