Scan & Verify ID
Available in SDK v1.0+
This capability extracts information from a government-issued identity document, but also verifies the document itself for authenticity and physical presence.
Configuration
Verification policy
The main configuration option is the verification policy, which can be:
- permissive
- standard
- strict
- very strict
When selecting a policy, the trade-off is one between the pass rate and false positives. In other words, the more permissive it is, the more users will pass through your verification process, but at the cost of a greater risk of bypassing our detection: lower false rejection rate (FRR) but higher false acceptance rate (FAR). Conversely, the stricter the policy, the fewer the number of missed detections. However, that comes at the cost of (a greater risk of) flagging legitimate users: higher FRR, lower FAR. Ultimately you will need to tune this policy to best suit your needs. For example, if you have additional checks that come later, you might reduce the strictness.
Verification context
If you know that your workflow will happen in the presence of a human reviewer, for example creating an account with the help of staff, you can select In person to not perform certain checks that only make sense in a remote context, such as whether the document is a photocopy (you would rely on the human reviewer to easily catch such violations).
Match levels
You can specify the match level for each subcomponent of the overall verification policy. The general verification policy setting affects these values: depending on what you selected (permissive, strict, etc.), the default values for subcomponents will be different.
Fine-tuning individual values means that the general policy is no longer applied. Each of the subcomponents has a tuning scale. The lower you set the value for that specific subcomponent, the more of that specific type of anomaly will be allowed. The higher the value, the more strict the matching (for that subcomponent).
Rules
The result of the document verification can impact the overall status of the step, or can simply be informative, and not affect the status.
In addition to this, you can configure two common rules: age verification and document validity. These two rules are not impacted by the previous step status setting. This means that if you set the step status not to be affected by Verify's recommended outcome, but in age and validity sections, you configure a rejection, the step will fail if the age or validity conditions are met.
Special case: image upload
Instead of activating the camera to scan an identity document, Verify supports using uploaded images of ID documents. The only requirement is to properly link the image, and to ensure that Verify comes after the user input step. For more info, see the image upload functionality.