> 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/risk.md).

# Risk

Risk products surface **signals from the mobile network** that help you detect account takeover, SIM-swap fraud, and other patterns where the line itself has changed in a way that matters. They're used as gates in fraud-sensitive flows — high-value transactions, account recovery, signup hardening, step-up authentication.

Risk products are **backend APIs**. They don't authenticate the user (that's [Number Verification](/products/number-verification.md) territory) — they answer a different question: *is something about this line state worth flagging?*

## In this section

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>SIM Swap</strong><br><code>Backend API</code> <code>GA</code></td><td>Detect whether the SIM card associated with a phone number has recently changed. A clean fraud signal for transactions, password resets, and step-up auth.</td><td><a href="/pages/iwMO47TJ3kh93LJ2HObY">/pages/iwMO47TJ3kh93LJ2HObY</a></td></tr></tbody></table>

## When to use a Risk product

Use a Risk product when:

* **You're gating a sensitive action** (transferring funds, adding a recovery device, changing a password) and want a real-time signal that the line hasn't recently changed hands.
* **You're hardening signup** against fraud rings using freshly-swapped numbers.
* **You're monitoring an active session** and want to re-check the line state on a cadence so a mid-session SIM change forces re-authentication.

Use a Number Verification product instead when the question is *"is this number on this device right now?"* — that's a possession signal, not a risk signal.

## Combining with other products

Risk + Number Verification closes a specific attack vector that neither product can close alone. Secure SNA proves the device currently holds the number; a fraudster's fresh SIM swap would also pass SNA. SIM Swap detects the recent SIM change but doesn't confirm the device holds the number. Used together, both signals are required, which closes the loop.

Pre-check [Eligibility](/products/eligibility.md) to know whether a Risk product is available for a given number before calling it.


---

# 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/risk.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.
