In September 2019, SentiLink was selected by the SSA to participate in the eCBSV pilot, an electronic version of the SSA’s existing CBSV program. This new product offering presents several compelling options for risk teams in terms of preventing synthetic fraud as well as validating identities of applicants who may have been incorrectly flagged by legacy KYC solutions. This blog post is the third in a series of eCBSV-related content that we will be publishing as the program goes live.
The successful implementation of a verification product depends tactically on understanding its requirements and use cases. But a truly successful implementation means understanding the verification product’s strengths and weaknesses, its mismatch rates and why they occur, how to integrate the product into your existing environment, and what supplementary services may be necessary or rendered redundant as a result.
eCBSV is no exception. In order to fully understand and optimize its deployment, we need to first understand the Numident — the SSA database on which the product is built — and the way queries interact with it, as well as issues that may arise in the queries themselves.