The Cross Check module compares a data field from one source against the same field from a second source and identifies whether the values match. For example, it can confirm that the name on a user's ID matches the name on their proof of address document.
Integrations
:white_check_mark: Web | :white_check_mark: iOS | :white_check_mark: Android
How It Works
In Workflows, Cross Check is a process module. It operates on data collected by earlier modules in the Workflow, such as ID Capture, Proof of Address, and Custom Fields. It doesn't ask the user for data directly. In Flows, Cross Check is a configurable setting. It also relies on modules that collect data.
You configure one or more comparisons. Each comparison specifies two document sources, the field to compare across those sources, and a severity level that controls how strictly the values must match. You can give each comparison a name to make it easier to identify when viewing results later.
Cross Check executes each configured comparison and produces a match or mismatch result. You can use these results in later conditional logic to route the session. For example, you can continue the flow on a match or mark the Session for review on a mismatch.
Fetch and Read Results
You can fetch results using the Fetching Crosscheck Results API. When reading results, iterate through the dictionary and use a "contains" comparison with the comparison name. Do not read the comparison name as a direct key on the JSON response. Incode's system automatically appends metadata to the end of each name, so a direct key lookup will not work.
For example, if you name a comparison FirstNameComparison in Dashboard, the API may return it as FirstNameComparison #i1class. The appended metadata varies and should be ignored. To retrieve the result, loop through the top-level keys of the JSON response and find the key that contains FirstNameComparison.
Name comparisons so there is no overlap in "contains" matching. For example, do not name one comparison FirstNameComp and another FirstNameComparison. This can cause your code to read from the wrong field.
Use Cross Check
For instructions on implementing and configuring Cross Check on each supported platform, use the following pages: