PingOne

PingOne Verify types of verification

PingOne Verify offers different types of verification to enable secure user verification.

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.

You can also verify users in India using their Aadhaar ID, a one-time passcode (OTP), and match the user’s selfie against the Aadhaar registry. During this verification process, the standard document authentication flow (docauth) is bypassed and enhances the efficiency and reach of identity verification for users in India.

Learn more in Creating a verify policy.

Facial Comparison Government ID

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.

Learn more in Creating a verify policy.

Facial Comparison Reference Selfie

A new live photo (selfie) compared with a reference selfie sent by the admin through PingOne application programming interface (API) for verification.

Verification is supported by the PingOne Verify DaVinci connector and the PingOne Verify PingFederate Integration Kit.

Learn more in Verify transactions, PingOne Verify Connector, and PingOne Verify Integration Kit.

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.

Learn more in Creating a verify policy.

Phone

Phone verification using OTP. Verification can be enabled on the Verify Policies page.

Email

Email verification using OTP. Verification is enabled on the Verify Policies page.

Voice

Voice verification using a voice sample. Voice verification has 2 steps:

  1. Enrollment: The end user provides live voice samples by speaking a predetermined phrase into their device’s microphone, or a customer support service or call center records an end user’s voice on a phone call and submits the voice recording to the customer.

    PingOne stores voice templates abstracted from user voice samples.

  2. Verification: The end user’s voice is verified either by speaking the same phrase from enrollment into their device microphone or using a customer support service recording of the end user’s voice. The support service can also send the user a link to verify their voice using a web-based flow. The voice sample is then compared to the user’s voice template (created from previously captured voice samples) and verified using a voice recognition engine.

Manual ID inspection

Verification done by a manual review team to determine the authenticity, originality, and validity of a document.

This verification is for circumstances where automated authentication isn’t achievable (unsupported government ID type) or reliable, such as poor image quality. Manual ID inspection license can be configured and used as a complement to the default automated ID inspection system (multistep) or its replacement (direct-to-manual).

Manual ID inspection requires an additional license to configure this verification through the PingOne admin console and the PingOne API.

AAMVA

Additional document verification provided by the American Association of Motor Vehicle Administrators (AAMVA) service through the Driver’s License Data Verification (DLDV) service.

Verification is enabled based on the active license capabilities your environment has. Learn more in US-based driver licenses in the PingOne developer documentation.

AAMVA requires an additional license to configure this verification through the PingOne admin console or the PingOne API.

Biographic matching

Biographic field values compared against attributes from the verified data of government-issued documents. These values are provided by the admin through PingOne APIs. Verification is also based on the result of PingOne Verify government ID verification.

You can configure this verification through the PingOne API.

Biographic matching results do not effect the final PingOne Verify verification status.

Learn more in Create Verify Transaction (Biographic Matching) in the PingOne developer documentation.