PingOne Verify types of verification
PingOne Verify offers different types of verification to enable secure user verification. Learn more about configuring these verifications in Verify policies.
| Verification | Description | ||
|---|---|---|---|
Government ID |
Verification based on government-issued documents. For example, a driver license or a passport. Government ID verifications are, by default, run through an automated ID inspection system. When automated ID authentication is not supported or when it is not reliable, such as when the user submits poor quality image, verification can be replaced by manual ID inspection, or step-up (automated, then manual). Verification is performed on PingOne Verify transactions by default, unless a customized verify policy is assigned to the transaction when it’s created. |
||
Facial Comparison |
A live photo (selfie) compared with government ID documents for verification. Verification is performed on PingOne Verify transactions by default, unless a customized verify policy is assigned to the transaction when it’s created. |
||
Liveness |
A liveness check on the live photo (selfie) for verification. Verification is performed on PingOne Verify transactions by default, unless a customized verify policy is added to the transaction when it’s created. |
||
Voice Verification |
Verification using voice samples of the end user. There are two types of voice verification policies: enrollment and verification.
|
||
Phone |
Phone verification using OTP. |
||
Email verification using OTP. |
|||
Identity Data |
Data Matching compares the identity data extracted during verification with data from an identity record. |
||
Data-based Identity Verification |
Verify user identity attributes with trusted third-party data. |