PingOne

Getting started with PingOne Verify

With PingOne Verify, you can integrate identity verification directly into your mobile app.

Using the PingOne Verify mobile SDK, you can prompt your customers to provide proof of identity, streamlining customer identity verification, while preventing fraud and abuse, by capturing live facial image and voice, scanning and validating government-issued identity documents, and confirming they match, all within your app.

Configuring PingOne Verify

Configure and integrate PingOne Verify into your user identity verification flow.

Before you begin

Regardless of the configuration method you choose, you’ll need:

About this task

There are five ways to configure PingOne Verify:

  • API integration

  • PingOne DaVinci

  • PingFederate Integration Kit

  • Mobile SDK

  • PingOne Advanced Identity Cloud and PingAM

The configuration method that you choose depends on your role.

Role Configuration Method

Admins and developers

Typically use the PingOne REST API or PingOne DaVinci to get started quickly and test a verify transaction.

PingFederate admins

Use the PingFederate admin console to configure the PingOne Verify Integration Kit. PingFederate supplies the authentication policy and user verification status for PingOne Verify.

Mobile developers

Use the PingOne Verify mobile SDK (iOS or Android) to create the app your users employ for ID verification.

Advanced Identity Cloud and PingAM admins

Use verification nodes in an authentication journey.

Integrating PingOne Verify with user authentication journeys

Advanced Identity Cloud is a digital identity and access management (IAM) software as a service (SaaS) solution for any identity, workforce, or consumer.

PingAM software manages access to resources, such as web pages, applications, or web services, that are available over a network. PingAM centralizes access control by handling both authentication and authorization.

To take advantage of PingOne Verify features, you can integrate PingOne Verify nodes into your Advanced Identity Cloud and PingAM journeys. Learn more in Journeys.

Use the following nodes to integrate PingOne Verify with Advanced Identity Cloud and PingAM:

For self-managed deployments, these nodes are available only from PingAM 8.0 onwards. If you’re using an earlier version of PingAM, use the corresponding Marketplace nodes.

Using the PingOne REST API

About this task

To configure PingOne Verify with the PingOne REST API:

Steps

  1. Create your theme in PingOne Branding and themes to brand the PingOne Verify web experience for your end users.

  2. (Optional) Use language localization to configure one or more languages and modify the PingOne Verify text fields that are presented to end users.

  3. (Optional) If you enabled through phone or email verification in your policy, create notification templates.

  4. Trigger your first Verify transaction:

    1. Read Getting started with the PingOne APIs.

    2. Download the PingOne Postman collection.

    3. Note the variables you must value.

    4. Obtain a PingOne access token.

      Your {{authPath}} environment variable in Postman should begin with auth.pingone. See PingOne API domains to determine the correct {{authPath}} for your region. Note that nothing trails the domain in the {{authPath}} variable.

    5. Create a new Verify transaction with the Create Verify Transaction API call.

      Your \{{apiPath}} environment variable in Postman should begin with api.pingone. See PingOne API domains to determine the correct \{{apiPath}} for your region. Note that the trailing /v1 is required (for example, api.pingone.com/v1).

      For more information, see PingOne API requests.

      Result:

      Postman renders a QR code.

      A screen capture of the QR code that Postman renders when creating a Verify transaction.
    6. Scan the QR code with a smartphone camera to try the mobile web flow.

  5. View the data submitted in the transaction and the scores returned from verification services.

    Choose from:
    • Using the API: Use the Verified Data and Meta Data endpoints.

    • Using the PingOne admin console:

      1. In PingOne, go to Environment → Audit.

      2. Edit the Time Range and Within fields as needed.

      3. For Filter Type, select Event Type.

      4. For Filter, enter verify in the Search Filter Type field.

      5. Select any of the Verify event types.

        Learn more in Event types.

        A screen capture of the PingOne Audit page with 'verify' entered in the Filter field.
      6. Click Run.

      7. To view the specific data and scores from an event, click View in the Details column in the report summary.

Next steps

After you’ve familiarized yourself with how PingOne Verify works and have it running: