A verify policy dictates what is required to verify a user, such as an ID verification, facial comparison, or liveness.
This allows you to create PingOne Verify transactions for different scenarios, for example:
- Choosing documents for verification during employee onboarding
- Selfie liveness and comparison during multi-factor authentication (MFA) authentication in PingID using PingOne Verify
A default verify policy based on your environment capabilities is listed.
- Click the + icon.
Enter the following information.
Policy Configurations Field Description
The policy’s name.
The policy’s description.
Time period (in minutes) in which data can be collected after a transaction is created.
Maximum transaction timeout is 30 minutes.
Data Collection Timeout
Time period (in minutes) in which data can be collected after initiating verification from the UI. By default, the data collection timeout is set to 15 minutes.
Maximum data collection timeout is 30 minutes.
Data Collection Only
Data collection only collects documents from a user, but does not process them for verification.
Verification based on Government-issued documents. For example, a driver’s license or a passport.
A live photo (selfie) compared with government ID documents or reference selfie for verification.
A liveness check on the live photo (selfie) for verification.
The probability that selfies are likely to match with document images (facial comparison) or pass liveness checks (liveness) with a low, medium, or high threshold.
Selfies are less likely to match or pass with a higher threshold.
Phone verification using one-time passcode (OTP).
Email verification using OTP.
Create MFA Device
Registration of a user’s phone number or email address as a trusted MFA device after successful OTP or web link verification.
Your new policy is shown on the Verify policies page.