# Profile Use Case

## Overview

The `profile` parameter allows you to configure the level of strictness for face match and face liveness decisions during verification. By selecting an appropriate profile, you can tailor the verification process to fit different use cases, such as dating apps, banking, or other scenarios with varying levels of risk tolerance.

* Permissive Profile (`permissive-v0`)
* Optimal Profile (`optimal-v0`)
* Strict Profile (`strict-v0`)

### Usage

To use the `profile` parameter, include it in your API request as shown below. If the `profile` parameter is not included, the `optimal-v0` profile will be used by default.

{% tabs %}
{% tab title="Node.js" %}

```javascript
var request = require('request');
var fs = require('fs');
var options = {
  'method': 'POST',
  'url': 'https://idv-eu.kairos.com/v0.1/full-id-verification',
  'headers': {
    'app_id': 'put_app_id_here',
    'app_key': 'put_app_key_here'
  },
  formData: {
    'selfie': fs.createReadStream('/path/to/selfie_image'),
    'document': fs.createReadStream('/path/to/document_image'),
    'document_back': fs.createReadStream('/path/to/document_back_image'),
    'profile': 'put_your_profile_here',
  }
};
request(options, function (error, response) {
  if (error) throw new Error(error);
  console.log(response.body);
});
```

{% endtab %}

{% tab title="CURL" %}

```ruby
curl -X POST --location 'https://idv-eu.kairos.com/v0.1/full-id-verification' \
--header 'app_id: put_app_id_here' \
--header 'app_key: put_app_key_here' \
--form 'selfie=@"/path/to/selfie_image"' \
--form 'document=@"/path/to/document_image"' \
--form 'document_back=@"/path/to/document_back_image"'
--form 'profile=put_your_profile'
```

{% endtab %}
{% endtabs %}

**Permissive Profile (`permissive-v0`)**

* **Description**: This profile is the least strict and is suitable for use cases where the risk of fraud is low. It accepts most verifications.
* Face Match:
  * Reject if face match value is less than 0.3.
  * Review if face match value is between 0.3 and 0.4.
  * Accept if face match value is greater than 0.4.
* Liveness:

  * Reject if liveness value is less than 0.3.
  * Review if liveness value is between 0.3 and 0.7.
  * Accept if liveness value is greater than 0.7.

  **Use Cases:**

  1. **Social Media Applications**: Platforms where the priority is user convenience over stringent identity verification. The goal is to have a smoother onboarding experience for users.
  2. **Online Communities and Forums**: Websites where identity verification is more about confirming basic user information rather than strict authentication.
  3. **Loyalty Programs**: Retail or brand loyalty programs where the emphasis is on user engagement and rewards rather than preventing fraud.

**Optimal Profile (`optimal-v0`)**

* **Description**: This profile is set as the default if no profile is specified. It balances security and convenience and is suitable for most use cases.
* Face Match:
  * Reject if face match value is less than 0.4.
  * Review if face match value is between 0.4 and 0.56.
  * Accept if face match value is greater than 0.56.
* Liveness:

  * Reject if liveness value is less than 0.4.
  * Review if liveness value is between 0.4 and 0.6.
  * Accept if liveness value is greater than 0.6.

  **Use Cases:**

  1. **Dating Applications**: Platforms where verifying user identity is important for safety, but the process should remain user-friendly.
  2. **E-commerce Platforms**: Websites where moderate levels of security are required to prevent fraudulent transactions and ensure genuine user participation.
  3. **Ride-Sharing and Gig Economy Apps**: Services where user verification is important for trust and safety, but needs to be balanced with ease of use for quick onboarding.

**Strict Profile (`strict-v0`)**:

* **Description**: This profile is the most stringent and is suitable for high-security use cases, such as banking. It requires stricter matches for both face match and liveness.
* Face Match:
  * Reject if face match value is less than 0.48.
  * Review if face match value is between 0.48 and 0.64.
  * Accept if face match value is greater than 0.64.
* Liveness:

  * Reject if liveness value is less than 0.5.
  * Review if liveness value is between 0.5 and 0.7.
  * Accept if liveness value is greater than 0.7.

  **Use Cases:**

  * **Banking and Financial Services**: Applications where high levels of security are crucial to prevent identity theft, fraud, and ensure compliance with regulations.
  * **Government Services**: Platforms providing access to sensitive information or services that require strong identity verification to protect citizen data.
  * **Healthcare Services**: Systems where verifying the identity of patients and medical professionals is critical for safety and regulatory compliance.
  * **Corporate Security Systems**: Internal company systems that require strict authentication for access to confidential information and secure areas.

By configuring the `profile` parameter appropriately, you can ensure that the verification process aligns with your security requirements and use case scenarios.


---

# Agent Instructions: 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:

```
GET https://docs.kairos.com/documentation/full-api-reference/full-id-verification/profile-use-case.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.