Identity verification best practices
Here, you can learn about the out-of-the-box solutions that come with every identity verification policy template.
Identity verification is a complex process that usually involves more than just identity establishment.
While establishing trust in online identities is the main focus, you should also
- know how to combine risk evaluation techniques for your benefit
- determine the success threshold customers should pass to get verified
- have an easy way to obtain customer consent and handle data collection
- pass customer information down to risk evaluation services
- guide customers throughout the whole process
There are a few best practices we've included in the identity verification policy templates so you can stay focused on building the journey while adding the rest of the capabilities as you go. You can also use default configurations to your benefit.
When you create a brand new identity verification policy, you will have a template on your hands that includes some pre-canned configurations:
Default verificaiton step settings
Each step contains default messages inside that you can use as a draft for creating your own messaging:
Default verification notification and preview
Default failure message and preview
Default consent collection setup
Phone number evaluation has a fixed spot in the verification journey: if enabled, it always comes before any other verification step. This setup allows you to filter out risky phone signals and detect recent SIM card changes (that are indicators of SIM swap attacks) before letting a customer move forward with identity verification.
Phone risk evaluation options
Default data display & collection fields
In the 'Verification data collection & display' step, you can add a compound address field to the customer journey. The compound address field is made up of individual attribute fields that are already selected and assigned a governing native claim when you start configuring the field:
Compound address field configuration
In the data collection step, customers can type in a few letters of their address to search for it and then select it to auto-fill the appropriate fields:
Compound address customer experience
In a knowledge-based verification (KBV) step, customers go through a series of questions to answer in order to affirm their identity. These verification exams are created based on the customer information handed off to the third-party credit bureau that takes care of generating questions.
When adding a new KBV step, claim mappings are already configured by default for each attribute:
Default claim mappings for knowledge-based verification