Silent Network Authentication (SNA)
Add Silent Network Authentication (SNA) to your workflow for seamless, secure, in-session phone number possession verification.
What is Silent Network Authentication?
Socure’s Silent Network Authentication confirms in-session possession of a mobile phone number using real-time mobile operator signals. When SNA is unavailable, One-Time Passcode (OTP) serves as a ubiquitous, configurable fallback.
How it works
Socure gives you a unique, one-time use, time-bound URL to initiate on the phone. The phone starts a data session and the SIM and mobile operator authenticate the phone number from that session using special cryptographic keys that protect the $3 Trillion global wireless network. This authentication happens without any end-user intervention, so the authentication is frictionless (great user experience) and 100% secure and deterministic since there is no PIN that can be intercepted by a third party. Socure can confirm with the mobile operator in a server-to-server call whether the actual phone number engaged in the data session matches what the end-user claims they possess.
SNA is deployed through Socure’s Digital Intelligence SDKs for iOS, Android, or React Native, and leveraged as an enrichment module in RiskOS™.
Enrichment | Input fields | Signals returned | Coverage | Best for |
|---|---|---|---|---|
| SNA | Phone number (via device with active SIM) |
| Major mobile operators (usually no MVNOs) in the countries listed below | High-assurance, low-friction phone number possession verification |
Availability
Available for users in:
When to use Silent Network Authentication
- New account creation, especially for higher conversion
- Logins for greater security, better conversion due to reduced authentication friction, and lower operational costs (no more "I'm having trouble with my OTP" customer service calls)
- Fast check-out transactions due to reduced authentication friction
Natural product pairings
- Since not every mobile operator supports SNA, you should configure SNA as the first option and then fall back to SMS OTP when there is no coverage.
- If you have a sensitive transaction (e.g. large money transfer, access to health or legal records, or change of contact information) then adding a SIM swap check might be appropriate. With some effort, fraudsters can claim ownership over a phone number by socially engineering a SIM swap from a mobile operator, so adding a SIM swap check will give you assurance that the phone number possession check is legitimate.
Integration
Ensure your account is provisioned for the SilentNetworkAuth feature.
Use the Digital Intelligence SDK for iOS, Android, or React Native. Add android.permission.CHANGE_NETWORK_STATE to Android manifest.
Add SNA as an enrichment module in RiskOS workflows alongside OTP or other identity checks.
Operational notes
- SNA validation may take 1 - 4 seconds — display an interstitial screen in mobile apps during processing.
- Device must have an active SIM card and cellular data enabled.
- Devices on Wi-Fi will automatically switch to cellular for authentication.
- Devices without SIM or cellular connectivity will not complete authentication (status is still reported).
- Currently supported only in select countries (see the current list above).
- Requires mobile operator approval for the use case.
Latest launches
- Mobile operator support expansion: Continued expansion of SNA in more countries.
- Fallback to SMS OTP: Configurable SMS OTP fallback when SNA is unavailable.
- Improved UX: SDKs automatically switch from Wi-Fi to cellular when needed for authentication.
Check out more updates in the release notes.
Updated 4 days ago