PingOne Verify types of verification (early access)
PingOne Verify offers different types of verification to enable secure user verification. Learn more about configuring them in Verify policies.
| Verification | Description | ||
|---|---|---|---|
Government ID |
Verification based on government-issued documents. For example, a driver license or a passport. By default, Government ID verifications use an automated inspection system. If automated verification is unsupported or fails due to poor image quality, the process falls back to manual inspection or a step-up approach (automated followed by manual). For users in India, you can also perform Aadhaar eID verification using DigiLocker. This method allows users to share official identity attributes directly from their government-backed electronic wallet. By using this electronic path instead of image-only checks, you can reduce manual reviews and document failures while maintaining compliance with Indian digital identity standards. 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. You can also configure the policy to enroll a verified selfie into PingOne Recognize automatically. Learn more in Creating a verify policy (early access) and Enrollment in the PingOne Recognize documentation. |
||
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 one-time passcode (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. |
||
Device Ownership and Risk |
Verify the end user legally owns or is associated with the phone number or email being used to complete the verification transaction. |