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. For circumstances where automated ID authentication is not achievable (unsupported) or reliable, such as poor image quality, verification can be complemented (multi-step) or replaced by manual ID inspection (direct-to-manual).

Verification is performed on PingOne Verify transactions by default, unless a customized verify policy is assigned to the transaction when it's created.

For more information, see 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.

For more information, see Creating a verify policy.

Facial Comparison Reference Selfie

A new live photo (selfie) compared with a reference selfie sent by the admin through PingOne APIapplication programming interface (API) A specification of interactions available for building software to access an application or service. for verification.

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

For more information, see 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.

For more information, see Creating a verify policy.

Phone

Phone verification using one-time passcode (OTP)one-time passcode (OTP)OTP A passcode valid for only one sign on or transaction on a computer system or other digital device. Also known as a one-time password, one-time PIN, or dynamic password.. Verification can be enabled on the PingOne Verify Policies page.

Email

Email verification using OTP. Verification is enabled on the PingOne 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/call center records an end user’s voice on a phone call and submits the voice recording to the customer.
    Note:

    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 is not 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 (multi-step) or its replacement (direct-to-manual).

Note:

You cannot configure this verification through the PingOne admin console or the PingOne API. Manual ID inspection requires an additional license.

AAMVA

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

Verification is enabled based on the active license capabilities your environment has. For more information, see US based driver's license.

Note:

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

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.

Note:

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

For more information, see Create Verify Transaction (Biographic Matching).