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

# Smile Secure

{% hint style="info" %}
To get access to Smile Secure, please contact our [sales team](https://usesmileid.com/talk-to-an-expert)
{% endhint %}

### Overview <a href="#sc4q6lhuch33" id="sc4q6lhuch33"></a>

Our real time Smile Secure product helps identify rogue users attempting to use multiple IDs to access your system. Our models deduplicate facial biometrics and layer on side-channel data to inform you if you have previously verified the same user, even if the user is presenting a different name or government ID for KYC.

We automatically perform a deduplication check for every [Biometric KYC](/products/for-individuals-kyc/biometric-kyc.md), [Document Verification](/products/for-individuals-kyc/document-verification.md), [SmartSelfie™ Authentication](/products/for-individuals-kyc/biometric-authentication.md)(Registration) job.

{% hint style="info" %}
For [Biometric KYC](/products/for-individuals-kyc/biometric-kyc.md), the `Antifraud` section is returned in the final response.
{% endhint %}

### Return Values <a href="#xr8jnvx9sqdf" id="xr8jnvx9sqdf"></a>

When the service is enabled, its results are returned in the response of the products in use, such as Biometric KYC, Document Verification, etc. The product response includes:

* Verification result – Contains the outcome of the identity verification process
* Antifraud object – Provides fraud detection insights

The `Antifraud` object contains a SuspectUsers list that identifies potentially fraudulent activity. Each entry includes:

* Related user IDs that share suspicious characteristics
* Specific reasons for flagging, such as:
  * Matching facial biometric data across multiple accounts
  * Reuse of the same ID number by different users

These indicators help detect duplicate accounts and ID number reuse.

{% hint style="info" %}
The `Antifraud` object will be empty if the primary verification request is not approved.
{% endhint %}

{% hint style="info" %}
Please note that Smile Secure no longer sends responses through separate callbacks. Responses are now provided via the primary request flow.
{% endhint %}

#### Example:

```json
{
    "Actions": {
      "Human_Review_Compare": "Passed",
      "Human_Review_Liveness_Check": "Passed",
      "Human_Review_Selfie_Check": "Passed"
    },
    "Antifraud": {
        "summary": {
            "fraud_detected": true,
            "fraud_sources": ["smile_secure"]
        },
        "smile_secure": {
            "ResultCode": "5211",
            "ResultText": "Suspect Users Found",
            "SuspectUsers": [
                {
                    "user_id": "user002",
                    "reasons": ["same-face"]
                },
                {
                    "user_id": "user003",
                    "reasons": ["same-id-number"]
                },
                {
                    "user_id": "user001",
                    "reasons": ["same-id-number", "same-face"]
                }
            ]
        },
    },
    "ResultCode": "0810",
    "ResultText": "Enroll User",
    "PartnerParams": {
      "job_id": "KE_TEST_100",
      "job_type": 1,
      "user_id": "KE_TESTTEST_100"
    },
    "SmileJobID": "0000056574",
    "timestamp": "2021-05-06T08:48:50.763Z",
    "signature": "----signature-----"
  }

```

{% hint style="info" %}
With Smile Secure you decide how to handle **flagged requests** i.e reject automatically, trigger internal manual review, or implement custom workflows depending on your compliance policies.
{% endhint %}

{% hint style="info" %}
Time Window Protection: Default 30 day lookback period ensures the user catches recent fraud attempts while maintaining system performance. Extended look back period is available on request.
{% endhint %}

### Result Codes <a href="#jueuxtpoad59" id="jueuxtpoad59"></a>

| Code | Text                   | Description                                                                             |
| ---- | ---------------------- | --------------------------------------------------------------------------------------- |
| 5210 | No Suspect Users Found | Our Smile Secure algorithms ran over the job and were unable to identify related users. |
| 5211 | Suspect Users Found    | Our algorithms identified related users that should be investigated.                    |
| 5212 | System Error           | We were not able to run Smile Secure on this job.                                       |


---

# 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://legacy-docs.usesmileid.com/products/for-individuals-kyc/smile-secure.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.