The Verify Person results page displays more details about a Verify Person check by allowing users to drill down further into the databases that were used to determine the result. Find out more information about how to perform a Verify Person check here.
The Verify Person page can be accessed by selecting the Verify Person block on the Person Summary page (as highlighted below).
Once on the Verify Person page, users will be able to view an overview of the Verify Person check and the databases used to perform the check.
The above shows the result for the Verify Person check alongside fields that relate specifically to the verification. See below for a description of what each field indicates.
|Name||The inputted forename and surname for the person id|
|Result||The result for the Verify Person check (the result is a reflection of the decision bands that would have been set up for an organisation during the on boarding process)|
|Score||The total score for the Verify Person check (the scoring logic would have been set up for an organisation during the on boarding process). If you want to alter the configuration set up, please contact your Account Manager.|
A unique string that our help desk can use if they need to assist with a specific Verify Person check
|Performed On||The date and time the Verify Person check was carried out|
A unique string that references the configuration used to dictate the results, scoring and databases used with the Verify Person check.
The profile version that dictates which version of the configuration was used for the verification on a Verify Person check
|Person Id||A unique string of characters assigned to a specific set of verification checks that are associated with a single individual (this is created in the API after the first verification for an individual is done)|
The Input Summary section enables users to view the inputted person data used for a Verify Person check, making it easier to identify whether the data was inputted correctly and assess the reliability of the results.
The Databases section will allow users to view information about each database that has been used for the Verify Person check. The databases displayed have been configured for a specific Profile used for the Verify Person check (this can be altered for you by our professional services team). Within each database, users can drill down on what input data has matched against a particular database or not. Users are also able to view any alerts highlighted against a database or any insufficient data that could have been provided and checked against the given database.
Initially, users will be able to view high-level details of each database. A user can click on the 'More Info' button to expand it, which will allow them to view and switch between the Supplied and Insufficient Data.
Note: Supplied data is the only area where users will find potential matches, no matches or alerts.
For each database, users are able to find out what input data did or did not match against a that particular database.
Match – inputted data has matched against a record within a database.
No Match – inputted data has not matched against a record within a database
Important: Databases may not hold detail of every field that was inputted for the Verify Person check. For example, a forename, surname, current address and date of birth is provided in the input data for a Verify Person check, and it is checked against a database that only stores forename, surname and address, then these will only be returned as matches or no matches.
Below is an example of what a ‘Match’ would look like and the detail of what data has matched against that database. For the example below, the forename, surname and address matched a record found in the UK Edited Electoral Roll. Note: Item Codes are used as a reference point if any assistance is needed from our Professional Services team.
Input data may not always match against a database, and when this happens, a ‘No Match’ will be displayed. The example below details that an Address has matched against the UK National Identity Register, however the Surname has not matched against that database.
Alerts aim to flag information that may be of relevance to the verification. An example of this may be if a database was unable to determine whether a field of data was a Match or No Match. The below example indicates that the Forename, Surname and Address has matched against the UK National Identity Register, however the database was unable determine a match or no match for the Date of Birth or Landline.
The Insufficient Data tab displays information about input data that was not provided but could have been to check against the particular database.