> 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/idv-suite/primeros-pasos/casos-de-uso-tipicos.md). # Typical use cases ## 1. Digital Onboarding of new customers #### Description It allows new customers to be registered remotely through digital Identity Verification processes. The goal is to validate the user's identity during onboarding using documentary and biometric evidence. #### Problem addressed In traditional onboarding processes, there may be: * Dependence on in-person or semi-in-person processes. * Risk of document fraud or identity impersonation. * Differences in the onboarding process across channels (web, mobile, etc.). #### Implementation in the platform The platform allows configurable onboarding Flow definitions that include different verification steps, including: * Identity document capture. * User selfie capture. * Biometric comparison between the document and the selfie. * Automatic validations on the document (OCR, data consistency checks, and security checks). If necessary, the Flow may include manual review by agents before the operation is finally resolved. Each operation is recorded in the operations module, where traceability of the process and the decisions made is preserved. *** ## 2. Strong authentication and re-Identity Verification #### Description It allows the identity of a user who already has an account or previous registration to be verified again, usually before executing sensitive operations. #### Problem addressed * Use of weak or shared authentication mechanisms. * Need to verify the user's identity again without repeating the entire onboarding process. #### Implementation in the platform Authentication Flow configurations can include: * Real-time selfie capture. * Biometric comparison against previously stored biometric records. * Automatic biometric similarity evaluation. The result of the process is recorded as part of the operation and can be used to determine whether or not the requested action is allowed to continue. *** ## 3. KYC review by agents (Backoffice) #### Description It allows automatic verification processes to be supplemented with manual review by agents in cases that require additional validation. #### Problem addressed * Non-centralized manual processes for reviewing operations. * Lack of structured recording of the decisions made by human operators. #### Implementation in the platform The agents module allows managing operations pending review through: * Queues of operations assigned to agents or supervisors. * Visualization of the data captured during the process (documents, images, verification results). * Decision to approve or reject the operation using standardized reason codes. The decisions made by the agents are recorded in the system and synchronized with the operation status, and can be notified to external systems via webhooks or integrations. *** ## 4. Anti-fraud management and blocklists #### Description It allows operations associated with identities or devices previously identified as potentially fraudulent to be detected and blocked. #### Problem addressed * Difficulty identifying repetitive fraud patterns. * Lack of centralized information across operations carried out in different channels. #### Implementation in the platform The platform maintains records associated with operations, including biometric information and device data. These records can be used to: * Create galleries of faces or devices associated with previous operations. * Apply anti-fraud rules that detect matches between operations. * Block or flag operations when suspicious matches are detected. The affected operations are recorded with the blocking reason and can be consulted from the operations module. *** ## 5. Flow and integration configuration (no-code / low-code) #### Description It allows identification and verification Flow configurations to be defined and modified using configuration tools, reducing the need for direct code changes. #### Problem addressed * Dependence on technical development to modify identification processes. * Difficulty iterating on or adjusting the steps of the Flow. #### Implementation in the platform The platform includes a Flow editor that allows verification processes to be configured using predefined components, such as: * Document Capture. * Selfie capture. * Biometric Verification. * NFC reading (when available). The configured Flow configurations can be exposed through different integration mechanisms, such as landings or SDKs. The system keeps versions of the Flow configurations, allowing you to identify which configuration was active at a given time. *** ## 6. Omnichannel execution of Flows #### Description It allows the same identification processes to be executed across different user interaction channels. #### Problem addressed * Implementation differences between channels. * Difficulty maintaining equivalent processes on the web and in mobile applications. #### Implementation in the platform The same Flow can be executed through different integration mechanisms: * Landings generated by the platform. * SDK Web for integration into web applications. * SDK Mobile for iOS and Android applications. All operations generated from these channels are recorded in a single operations console. *** ## 7. Operational monitoring and operations analysis #### Description It allows the behavior of identification Flow and the status of operations to be analyzed. #### Problem addressed * Lack of visibility into the status of operations. * Difficulty identifying drop-off points or incidents in the process. #### Implementation in the platform The platform includes monitoring tools that allow: * Consult operation funnel indicators (initiated, in progress, completed, blocked, rejected, or not finished). * Access operation listings with filters by status, date, channel, or other attributes. * Consult the details of each operation, including information captured during the process (document, biometrics, device data, or other context data). *** ## 8. User, role, and audit management #### Description It allows access to the system to be controlled and the actions performed by internal users to be recorded. #### Problem addressed * Need to limit access to sensitive information. * Audit requirements for actions performed in the system. #### Implementation in the platform The module of **User Management** allows: * Define roles and access permissions. * Manage the lifecycle of internal users (creation, removal, blocking). * Record relevant actions performed within the system. This information can be used for internal audits or compliance reviews.