> 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 it addresses In traditional onboarding processes, there may be: * Dependence on in-person or semi-in-person processes. * Risk of documentary fraud or identity theft. * Differences in the onboarding process between channels (web, mobile, etc.). #### Implementation on the platform The platform allows configurable onboarding flows that include different verification steps, including: * Document Capture of the identity document. * User selfie capture. * Biometric comparison between document and selfie. * Automated validations on the document (OCR, data consistency checks, and security verifications). If necessary, the flow may include manual review by agents before the operation's final resolution. Each operation is recorded in the operations module, where the traceability of the process and the decisions made is retained. *** ## 2. Strong authentication and identity re-verification #### Description It allows the identity of an already registered user to be verified again, usually before executing sensitive operations. #### Problem it addresses * Use of weak or shared authentication mechanisms. * Need to re-verify the user's identity without repeating the entire onboarding process. #### Implementation on the platform Authentication flows can be configured to 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 complemented with manual review by agents in cases requiring additional validation. #### Problem it addresses * Non-centralized manual processes for operation review. * Lack of structured recording of decisions made by human operators. #### Implementation on the platform The agent module allows pending operations to be managed for review through: * Queues of operations assigned to agents or supervisors. * Viewing 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 agents are recorded in the system and synchronized with the operation status, and may be notified to external systems via webhooks or Integration mechanisms. *** ## 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 it addresses * Difficulty identifying repetitive fraud patterns. * Lack of centralized information across operations performed in different channels. #### Implementation on 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. Affected operations are recorded with the block reason and can be consulted from the operations module. *** ## 5. Flow configuration and Integrations (no-code / low-code) #### Description It allows identification and verification flows to be defined and modified through configuration tools, reducing the need for direct code changes. #### Problem it addresses * Dependence on technical developments to modify identification processes. * Difficulty iterating or adjusting the flow steps. #### Implementation on 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). Configured flows can be exposed through different integration mechanisms, such as landings or SDKs. The system maintains versions of the flows, allowing it to identify which configuration was active at a given moment. *** ## 6. Omnichannel execution of flows #### Description It allows the same identification processes to be executed across different user interaction channels. #### Problem it addresses * Differences in implementation between channels. * Difficulty maintaining equivalent processes on the web and mobile applications. #### Implementation on 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 analysis of the behavior of identification flows and the status of operations. #### Problem it addresses * Lack of visibility into the status of operations. * Difficulty identifying drop-off points or incidents in the process. #### Implementation on the platform The platform includes monitoring tools that allow: * Consult funnel indicators for operations (initiated, in progress, completed, blocked, rejected, or not completed). * Access operation listings with filters by status, date, channel, or other attributes. * View 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 control of access to the system and recording of actions performed by internal users. #### Problem it addresses * Need to restrict access to sensitive information. * Audit requirements for actions performed in the system. #### Implementation on the platform The module for **User Management** allows: * Define roles and access permissions. * Manage the lifecycle of internal users (additions, removals, blocks). * Record relevant actions performed within the system. This information can be used for internal audits or compliance reviews.