> For the complete documentation index, see [llms.txt](https://docs.idlayr.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.idlayr.com/products/number-verification/secure-sna.md).

# Secure SNA

{% hint style="info" %}
**Device API** · NV 1.0 · GA
{% endhint %}

Silent, real-time verification that a claimed mobile phone number is currently mapped to the SIM card on the device's live mobile data connection. The user receives no SMS, code, or visible challenge — the check happens against the mobile network operator while the device is on cellular data.

## What it does

* Verifies a claimed MSISDN against the network-attached number on the device that's actively making the request.
* Uses the SIM card as a possession factor — cryptographically rooted in the mobile network, not in a user-typed value.
* Returns a deterministic `match` boolean. Your backend uses the result to allow, fail, step up, or route to an alternative path.

## What it doesn't do

* It does not prove the natural person using the device. Combine with biometrics, KYC, passkeys, or a customer-side risk policy when person-trust is required.
* It does not replace risk-based authentication. It's a high-confidence possession signal that fits inside a broader risk policy.

## Common use cases

* Onboarding and signup — verify the phone number a new user provides is on their device.
* Login or step-up authentication — silently confirm device-and-number ownership before a sensitive action.
* Account recovery — re-establish trust without sending an OTP.
* Transaction confirmation — verify before a payment or account change.

Pair with [SIM Swap](/products/risk/sim-swap.md) when the use case is fraud-sensitive: SNA confirms the device holds the number now, SIM Swap confirms the SIM hasn't recently changed. Used together, both signals must hold — which closes the SIM-swap attack vector.

## In this section

* [**How it works**](/products/number-verification/secure-sna/how-it-works.md) — the verification flow end-to-end, from backend to device to MNO and back.
* [**Prerequisites**](/products/number-verification/secure-sna/prerequisites.md) — what you need before integrating.
* [**Integration**](/products/number-verification/secure-sna/integration.md) — iOS, Android, and backend walkthroughs.
* [**Testing in sandbox**](/products/number-verification/secure-sna/testing.md) — MSISDN suffix patterns and platform-specific sandbox modes.
* [**Endpoints**](/products/number-verification/secure-sna/endpoints.md) — REST endpoint summary; full reference in API Reference.
* [**Callbacks**](/products/number-verification/secure-sna/callbacks.md) — terminal-state callback payload, delivery, and retry.
* [**Error codes**](/products/number-verification/secure-sna/error-codes.md) — HTTP errors and terminal-state codes specific to Secure SNA.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.idlayr.com/products/number-verification/secure-sna.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.