Live · India · Airtel, Vi, Jio

Verify a phone number
without OTP.

SNA verifies a user's mobile number directly with their telecom operator — no OTP, no tap, no app switch. The user enters their number, and they're in. Authentication completes in under a few seconds, at the network layer, with proof of SIM possession that no SMS code can match.

Before · SMS OTP
~15s
Time to login
  • Delivery fails or arrives late
  • Users mistype the code
  • Phishable & SIM-swappable
  • One provider outage = downtime
After · SNA
<4s
P90 verification
  • Zero user action
  • Verifies at the network layer
  • SIM-swap resistant
  • Multi-channel fallback
≤4s
P90 verification
85–95%
SNA success rate
15–20%
Conversion lift
0
Permissions required
The protocol

How it actually works.

SNA is a real telecom protocol. OTPless abstracts it behind one SDK call - every actor, every hop, every guarantee.

End userphone
OTPless SDKclient
OTPlessbackend
Telco gatewayauth
Telco corenetwork
01
App → OTPless
User submits phone number
The SDK posts the number to the OTPless edge over TLS — hashed and anonymised before it leaves the device.
+0.0s
02
OTPless → SDK
Operator detected, SNA URL issued
OTPless identifies the carrier from MCC/MNC, generates a one-time SNA URL, and returns it with an opaque token. No PII embedded in the URL.
+0.4s
03
SDK → Operator
SDK opens SNA URL on cellular
Device calls the SNA URL on the cellular interface via fetch call in background. Wi-Fi is bypassed automatically - SIM-bound network identity is the validation surface.
+1.2s
04
Operator (silent)
Operator validates SIM & network
Operator confirms SIM is active and the network identity matches. No screen, no consent prompt, no user-visible event.
+2.2s
05
OTPless ↔ Operator (S2S)
OTPless fetches the verdict
After URL load, OTPless fetches the result via a server-to-server API call. The operator returns yes or no — nothing more.
+3.0s
06
OTPless → Backend
Signed auth token returned
If verified, OTPless issues a signed auth token to your backend, which validates and creates a session.
+3.4s
Operator coverage

Live across India. Expanding globally.

SNA runs on every major Indian operator and is live in 38 countries — with operator-level details per market on request.

Bharti Airtel
Live
Reliance Jio
Live
Vodafone-Idea
Live
APAC · 12 countries % of country subscribers
🇹🇭Thailand100%
🇮🇩Indonesia100%
🇮🇳India97%
🇰🇭Cambodia97.6%
🇵🇭Philippines89.4%
🇸🇬Singapore67%
🇲🇾Malaysia63%
🇻🇳Vietnam55.9%
Europe · 16 countries % of country subscribers
🇳🇱Netherlands100%
🇦🇹Austria100%
🇪🇸Spain100%
🇮🇹Italy87.6%
🇫🇷France82.5%
🇬🇧United Kingdom81.2%
🇩🇪Germany80.5%
🇵🇹Portugal58%
Americas · 6 countries % of country subscribers
🇧🇷Brazil96.5%
🇺🇸United States95.8%
🇨🇦Canada90.8%
🇲🇽Mexico68.4%

SNA coverage is telco-dependent and shown as % of country subscribers reachable today. Talk to us for the live country-by-carrier list.

Use case · Payments

UPI SIM Binding

Every UPI account must be bound to the SIM that holds the registered mobile number. The legacy flow is opaque and slow. SNA replaces it with a silent network check.

NPCI · Approved
UPI SIM binding · SNA Secure
01
User enters mobile in the UPI app
No outbound SMS, no permissions prompt.
02
SNA verifies SIM at the operator
Operator confirms the SIM matches the MSISDN — silently.
03
Bank receives a signed bind token
PSP / bank validates the token and proceeds with VPA creation.
04
UPI handle bound to the verified SIM
Account ready · audit trail preserved · no SMS sent.
Onboarding conversion lift
+30%

Measured vs. outbound SMS binding.

SIM-swap & spoofing fraud
−85%

Measured on first-time binding.

P90 bind time
≤ 3s

Silent, no SMS sent.

No SMS

Independent of the SMS protocol.

SNA uses the data network, not SMS. No carrier pack dependency.

No prompt

Zero permissions required.

No SMS-read, SIM-state, or phone-state prompts on the device.

Hardened

SIM-swap surface collapses.

Bind only succeeds if device, SIM, and registered MSISDN are all present.

Customer voice
From talks to go live in 24 hours. SNA gave us 4–5% higher success rates than any SMS vendor we'd evaluated.
Prashant Pandey
Engineering Manager · Navi
24h
From talks to live
+4–5%
Higher success vs SMS vendors
2M+
Auths / month at Navi
Integration

One call. Every channel routed for you.

The platform decides the channel by operator health, country, and device — so your code stays the same wherever it ships.

SignInActivity.kt android · kotlin
import com.otpless.main.OtplessManager
import com.otpless.dto.HeadlessRequest
import com.otpless.dto.HeadlessResponse

// 1. Init the OTPLESS view in your sign-in activity
private val otplessView = OtplessManager
    .getInstance().getOtplessView(this)

// 2. Build the verify request — just a phone number
val request = HeadlessRequest()
request.setPhoneNumber("91", "7069914791")

// 3. Start headless auth — SDK picks the best channel
otplessView.startHeadless(request, ::onHeadlessCallback)

private fun onHeadlessCallback(res: HeadlessResponse) {
    if (res.statusCode == 200 &&
        res.responseType == "ONETAP") {
        val token = res.response.optString("token")
        // → verify token on your backend
    }
}
// build.gradle  implementation 'io.github.otpless-tech:otpless-android-sdk:2.5.3'
onHeadlessCallback · ONETAP
340ms
auths[0] · primary
channelSILENT_AUTH
statusSUCCESS
identityValue917069914791
verifiedAt1778612141195
phoneDetail
operatorJIO
homeOperatorVI
countryIN · +91
portedtrue
deviceFingerprinting.riskAssessment
Session risk HIGH · 95 / 100
⚠ isAppTampered ⚠ debuggingEnabled
device: iQOO I2410 · Android 16 asn: Bharti Airtel · Haryana
Frequently asked

Common questions.

Does Silent Network Authentication work on Wi-Fi?
No. SNA requires the device to briefly use mobile data for the carrier handshake — SIM-bound network identity is the validation surface, and Wi-Fi masks the SIM. The OTPless SDK auto-detects connectivity and routes the SNA call over cellular even when the device is on Wi-Fi. If only Wi-Fi is available and the cellular switch fails, Mobile Auth falls back to WhatsApp or SMS automatically.
Which carriers support SNA in India?
Jio, Vi, and Airtel are supported. Population coverage in India is approximately 95–97% of country subscribers.
Where else is SNA live?
38 countries today across APAC, Europe, the Americas, and parts of MENA & Africa — including the US, UK, Germany, France, Spain, Brazil, and Indonesia. New operators come online every quarter.
Is SNA phishing-proof?
Yes. There is no OTP code that can be intercepted, screenshotted, or socially engineered. Verification happens on the actual cellular network with the actual SIM — which also makes it resistant to SIM-swap attacks.
How is SNA different from SMS OTP?
SMS OTP loses about 25% of users at the front door because of delivery failure, mistyping, missed timers, and app switching. SNA verifies in under four seconds at P90 with zero user action and no code to intercept. It's also resilient to single-provider outages because of multi-operator routing.
Is SNA RBI and NPCI compliant?
Yes. SNA is built on telecom-grade rails compliant with RBI and NPCI guidelines in India and equivalent regulators globally. It is cleared by NPCI as an SMS-binding alternative for UPI handle issuance.
Start with SNA

Stop sending codes. Start verifying silently.

SDK integration in under 30 minutes. SNA on every supported carrier — with automatic fallback to every channel that follows.

SOC 2 · ISO 27001 · 38 countries · ~95% IN