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

# Facephi Onboarding

### **What does this product solve?**

It allows new users to be registered remotely, securely, and without friction. The process combines document capture, facial biometrics, and real-time validations.

### **SaaS Integration**

**Required SDKs**

* Frontend SDK (Web or Mobile): face and document capture
* [Mobile SDK Documentation](/docs.facephi-en/sdks/sdk-mobile.md)
* [Web SDK Documentation](/docs.facephi-en/sdks/sdk-web.md)

**Required backend services (Rest API)**

* Liveness check and facial comparison validation: `POST /v2/identity`
* Document OCR extraction:
  * Mobile: `POST /extractDocumentData`
  * Web: `POST /extractDocumentDataWeb`
* Document validation:
  * By morphology: `POST /documentValidation/v2`
  * Against the Civil Registry: `POST /civilValidation`
* [Rest API Documentation](/docs.facephi-en/rest-api/identity-api.md)

**Other services**

* Duplicate Onboarding validation (optional): `POST /blacklist`

### **Suggested technical Flow**

1\. SelphID component (document scanning)

* Perform document capture using the SelphID Widget (Web or Mobile).

2\. Selphi component (Face Capture)

* Perform Face Capture using the Selphi Widget (Web or Mobile).
* Call the following endpoints in this order:
  * /documentValidation/v2\
    Send the full image with context to validate the document morphology.
  * /extractDocumentDataWeb or /extractDocumentData\
    Retrieve the OCR data extracted from the document for processing.
  * /v2/identity

    Perform the liveness check and the comparison of the selfie against the document image in a single call.

#### **Requirements and licenses**

**Frontend**

* Web: URL / port
* Mobile: package name or bundle ID

**Backend**

* api-key for API consumption

## Technical recommendations

### Biometric Template persistence

It is mandatory that the client persist the Biometric Template (templateRaw) generated through the Selphi Widget during the Onboarding or enrollment Flow.

This template is an essential element, since it will later be used in facial biometric authentication Flow processes. Its proper preservation guarantees the continuity and effectiveness of the Identity Verification process in future sessions.

It is recommended to store this information securely and encrypted, in compliance with personal data protection regulations and the client's internal policies.

### **FAQs**

* What is the difference between morphological validation and validation by the Civil Registry?

Morphological validation is used in those countries where there are no government biometric and/or data databases available for Identity Verification. Its main objective is to determine the authenticity of the documents presented, by analyzing their physical and visual characteristics. Additionally, this type of validation is used to verify identity documents such as passports and driver's licenses.

* Is it mandatory to use both document validations?

It is not mandatory to use both document validations. However, it is recommended that at least one of the two validations be enabled, in order to ensure the truthfulness and authenticity of the presented document.\
However, there may be business, regulatory, or risk requirements that determine the need to use both validations together. For example, when screen presentations or digital copies of the document are not accepted, the use of morphological validation becomes mandatory to ensure the authenticity of the physical document.

***

#### Glossary and key concepts

* **Passive liveness check:** The liveness check (Liveness) in Facephi is a biometric security mechanism that allows verifying that the person interacting with the system is a real human being, is physically present, and is not an image, video, mask, or synthetic content.

  Its main objective is to prevent identity impersonation attacks, such as the use of printed photographs, pre-recorded videos, or more sophisticated fraud attempts, including deepfakes, during biometric verification and authentication processes.
* **Facial Matching:** In the Onboarding Flow, Facial Matching consists of comparing the selfie image captured in real time with the face image contained on the front of the identity document presented by the user, with the goal of verifying that both images correspond to the same person.

  This process allows confirming that the user carrying out the Onboarding is the legitimate holder of the document, reinforcing Identity Verification and reducing the risk of impersonation.