Search Results

El módulo de Review es un sistema de análisis manual que permite a los asesores y analistas de seguridad del banco evaluar, clasificar y proporcionar retroalimentación sobre sesiones que han sido reportadas por clientes o escaladas por los sistemas automáticos...

En esta sección se describen los campos adicionales necesarios para mejorar significativamente el rendimiento de la detección de fraudes, reducir los falsos positivos y fortalecer la capacidad de identificar actividades fraudulentas donde...

PurposeAnalyze frames from the front-facing camera entirely on device to enhance fraud detection—no images are stored or transmitted; only metadata/results are sent. How it works App decides when to activate (e.g., after login, during a transfer, or only...

PurposeLet the app confirm whether an incoming/recent call was genuinely initiated by the bank—helping stop voice phishing and number spoofing. System architecture Bank Call Center reports each outbound call to the Secure Call backend. Secure Call B...

Continuously monitor SIM state changes to help mitigate SIM-swap account takeovers. Runs silently in the background and sends only non-sensitive metadata for risk scoring. High-level flow User installs/opens the banking app with the SDK. A lightweig...

This document type is accepted by our service and is referenced by an integer ID. Before using it in any request, verify with Support which document type will be validated so we can enable it via the dashboard. ID Nombre País / Entidad 1 ...

2.5 General optimization of the capture and validation flow to improve stability across consecutive sessions. Performance adjustments to reduce latency when returning results to the host. Initial improvements in evidence reduction (Base64) to decrease pay...

As part of the SDK update, starting now we will generate standardized response objects, including the full detail of fields and their possible values.  Additionally, we improved the tagging logic to correctly detect icons and related events. With these improv...

The Enrollment routine is intended for users who do not have a previously successful verification record. In operational terms, the flow should start only after FindByNumberIdSuccess indicates that there is no successful transaction for the customer. Once that...

The Customer Verification routine is designed for users who already have a previously successful identity record. The routine should only be triggered after FindByNumberIdSuccess returns a successful match for the customer. In this case, the platform performs ...

How to Communicate Responses The integration should communicate Uid as the technical correlation value across the capture phase, and TransactionId as the final reference used to retrieve the result. The business-facing response should be derived from the Vali...

This routine is designed as a two-step face comparison transaction. The process begins with StartCompareFaces, which creates the transaction and returns the Uid required to continue the flow. The transaction is then completed with CloseCompareFaces, where the ...