---
title: Configuring and setting up PingOne Verify
description: Configure and set up PingOne Verify as an administrator.
component: pingone
page_id: pingone:identity_verification_using_pingone_verify:p1_verify_configuration_setup
canonical_url: https://docs.pingidentity.com/pingone/identity_verification_using_pingone_verify/p1_verify_configuration_setup.html
llms_txt: https://docs.pingidentity.com/pingone/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: April 7, 2026
page_aliases: ["p1_verify_language_localization.adoc"]
section_ids:
  p1_verify_language: Configuring PingOne Verify language localization
  steps: Steps
  p1-verify-orchestration: Configuring and orchestrating PingOne Verify
  before-you-begin: Before you begin
  steps-2: Steps
  choose-from: Choose from:
  integrating-with-pingone-advanced-identity-cloud-and-pingam: Integrating with PingOne Advanced Identity Cloud and PingAM
  before-you-begin-2: Before you begin
  steps-3: Steps
  using-pingfederate: Using PingFederate
  steps-4: Steps
  steps-5: Steps
  result: Result:
  choose-from-2: Choose from:
  before-you-begin-3: Before you begin
  steps-6: Steps
  result-2: Result:
  choose-from-3: Choose from:
  using-the-pingone-verify-mobile-sdk: Using the PingOne Verify mobile SDK
  steps-7: Steps
---

# Configuring and setting up PingOne Verify

To seamlessly integrate PingOne Verify into your identity workflows, first optionally configure language localization for your end users, then choose your orchestration method.

## Configuring PingOne Verify language localization

Optionally use language localization to configure one or more languages and modify the PingOne Verify text fields that are presented to end users in notifications and agreements.

Language localization detects the user's browser locale and refers to the corresponding language pack in PingOne.

Integrating PingOne language packs provides seamless localization and translation of PingOne Verify user interfaces, allowing users to interact with it in their preferred language. Learn more in [Languages](../user_experience/p1_languages.html).

## Steps

1. In the PingOne admin console, go to **User Experience > Languages**.

2. Click your preferred language or add a language. Learn more in [Adding a language](../user_experience/p1_add_a_language.html).

3. In the **Module** list, select **Identity Verification**.

4. In the **Page** list, select a page to view the associated keys. The **Identity Verification** module includes the following pages:

   * **Device**

   * **Document**

   * **Error Messages**

   * **General**

   * **ID Capture**

   * **Retry**

   * **Selfie**

   * **Voice**

   ![Identity Verification module showing pages.](_images/languagelocalization.png)

5. (Optional) In the **Compare to:** list, select another language to compare the text with a language other than the default language.

6. In the translation column, click the **Pencil** icon ([icon: pencil, set=fa]).

7. Edit the text in the translation field to your preferred translation.

8. Click **Save**.

9. In the upper right, click the toggle to enable the language.

|   |                                                                                                                                                                                                |
| - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | Learn more in [Downloading a language bundle](../user_experience/p1_downloading_language_bundle.html) and [Uploading a language bundle](../user_experience/p1_uploading_language_bundle.html). |

## Configuring and orchestrating PingOne Verify

Seamlessly integrate PingOne Verify into your identity workflows.

## Before you begin

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

* A PingOne account with at least one environment that includes the PingOne Verify service. Learn more in [Starting a PingOne trial](../pingone_tutorials/p1_start_a_trial_tutorial_basic_passwordless.html) and [Creating an environment](../getting_started_with_pingone/p1_getting_started_adding_environment.html).

* A PingOne Verify policy, which can be the default policy you modify or a new policy. Learn more in [Creating a verify policy](p1_verify_creating_verify_policy.html).

* (Optional) To [configure language](#p1_verify_language) localization and modify the PingOne Verify text fields that are presented to end users in notifications and agreements.

![Metro map of configuring and orchestrating PingOne Verify.](_images/p1-verify-metro-map.png)

The metro map shows:

1. The PingOne Verify service is enabled within the PingOne environment.

2. The default PingOne Verify policy is customized with specific rules and transaction requirements, such as **Facial Comparison** and **Liveness**.

3. Verification transactions are orchestrated using integrated identity options.

4. The verification flow is executed with the end user, and the results are retrieved.

5. Oversight is maintained by reviewing results and dashboards.

## Steps

1. Choose one of the following methods to orchestrate a verify transaction:

   ### Choose from:

   > **Collapse: PingOne Advanced Identity Cloud and PingAM**
   >
   > ## Integrating with PingOne Advanced Identity Cloud and PingAM
   >
   > 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 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](https://docs.pingidentity.com/pingoneaic/latest/realms/journeys.html).
   >
   > ### Before you begin
   >
   > Make sure you have:
   >
   > * A PingOne Advanced Identity Cloud or PingAM account. [Getting started with PingOne Advanced Identity Cloud](https://docs.pingidentity.com/pingoneaic/latest/home.html).
   >
   > * A PingOne account. Learn more in [Starting a PingOne trial](../pingone_tutorials/p1_start_a_trial_tutorial_basic_passwordless.html).
   >
   > * A verify policy configured in PingOne (or use the default verify policy).
   >
   > * A worker application with the Identity Data Admin role assigned in PingOne.
   >
   > ### Steps
   >
   > 1. [Configure the PingOne service](https://docs.pingidentity.com/pingoneaic/latest/home.html) in Advanced Identity Cloud.
   >
   > 2. Set up your user journey in Advanced Identity Cloud or PingAM with PingOne Verify nodes in the journey:
   >
   >    * The [PingOne Verify Evaluation node](https://docs.pingidentity.com/auth-node-ref/latest/pingone/pingone-verify-evaluation.html) to start a new identity verification with PingOne Verify.
   >
   >    * The [PingOne Verify Completion Decision node](https://docs.pingidentity.com/auth-node-ref/latest/pingone/pingone-verify-completion-decision.html) to check the status of the last verify transaction.
   >
   >    * The [PingOne Verify Authentication node](https://docs.pingidentity.com/auth-node-ref/latest/pingone/pingone-verify-authn.html) to integrate biometric authentication functionality in your journey.
   >
   >    * The [PingOne Verify Proofing node](https://docs.pingidentity.com/auth-node-ref/latest/pingone/pingone-verify-proof.html) to integrate verification functionality using Government ID, Facial Comparison, and Liveness in a journey.
   >
   >      |   |                                                                                                                                                                                                                                                                                                |
   >      | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   >      |   | For self-managed deployments, these nodes are available only PingAM 8.0 or later. If you're using an earlier version of PingAM, use Marketplace nodes, such as the [PingOne Verify Authentication node](https://docs.pingidentity.com/auth-node-ref/latest/pingone/pingone-verify-authn.html). |
   >
   > 3. Validate that the PingOne Verify Evaluation node is working by doing the following:
   >
   >    1. Configure the node with **Store Verification Metadata** and **Store Verified Data** enabled.
   >
   >    2. Use a [Scripted Decision node](https://docs.pingidentity.com/auth-node-ref/latest/scripted-decision.html) to return the node state and make sure the values of the `pingOneVerifyMetadata`, `pingOneVerifyVerifiedData`, and `pingOneVerifyEvaluationFailureReason` properties are what you expect. You can also run the journey with Debugging enabled.
   >
   >    3. Add message nodes attached to individual results outputs to understand the flow.
   >
   > 4. Validate that the PingOne Verify Completion Decision node is working by doing the following:
   >
   >    1. Use logger messages in your Completion processing script to determine the processing goals and outcomes, and monitor the log.
   >
   >    2. Evaluate the `nodeState` values of the PingOne Verify nodes that were set in the script using a Scripted Decision node that returns the nodeState, or with the Debugger enabled
   >
   >    3. Add message nodes attached to individual results outputs to understand the flow.

   > **Collapse: PingFederate**
   >
   > ## Using PingFederate
   >
   > To use PingFederate to configure the PingOne Verify Integration Kit:
   >
   > ### Steps
   >
   > * Download PingFederate and the PingOne Verify Integration Kit from the [PingFederate Downloads website](https://www.pingidentity.com/en/resources/downloads/pingfederate.html).
   >
   >   |   |                                                                                                     |
   >   | - | --------------------------------------------------------------------------------------------------- |
   >   |   | You'll need to work with your Ping Identity account team to start a trial license for PingFederate. |
   >
   >   Learn more about getting started in the [PingOne Verify Integration Kit documentation](https://docs.pingidentity.com/integrations/pingone/pingone_verify_integration_kit/pf_p1_verify_ik.html).

   > **Collapse: PingOne API**
   >
   > To configure PingOne Verify with the PingOne REST API:
   >
   > ## Steps
   >
   > 1. Create your theme in PingOne [Branding and themes](../user_experience/p1_branding_themes.html) to brand the PingOne Verify web experience for your end users.
   >
   > 2. (Optional) Use [language localization](#configuring-pingone-verify-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 one-time passcode (OTP) *(tooltip: \<div class="paragraph">
   >    \<p>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.\</p>
   >    \</div>)* through phone or email verification in your policy, [create notification templates](../user_experience/p1_notifications.html).
   >
   > 4. Trigger your first verify transaction:
   >
   >    1. Read [Getting started with the PingOne APIs](https://developer.pingidentity.com/pingone-api/getting-started/introduction.html).
   >
   >    2. Download the [PingOne Postman collection](https://developer.pingidentity.com/pingone-api/getting-started/where-to-go-from-here.html#platform-postman-collection).
   >
   >    3. Note the [Variables you must value](https://developer.pingidentity.com/pingone-api/verify/working-with-pingone-apis/postman-and-pingone/use-the-pingone-postman-environment-template.html#variables-you-must-value).
   >
   >    4. Obtain a [PingOne access token](https://developer.pingidentity.com/pingone-api/getting-started/create-a-test-environment/step-1-get-access-token.html).
   >
   >       Your *{{authPath}}* environment variable in Postman should begin with `auth.pingone`. See [Variables you must value](https://developer.pingidentity.com/pingone-api/verify/working-with-pingone-apis/postman-and-pingone/use-the-pingone-postman-environment-template.html#variables-you-must-value) in the PingOne API documentation to determine the correct *{{authPath}}* for your geography. Note that nothing trails the domain in the *{{authPath}}* variable.
   >
   >    5. Create a new verify transaction with the [Create Verify Transaction API call](https://developer.pingidentity.com/pingone-api/verify/verify-transactions/create-verify-transaction.html).
   >
   >       Your *{{apiPath}}* environment variable in Postman should begin with `api.pingone`. See [Variables you must value](https://developer.pingidentity.com/pingone-api/verify/working-with-pingone-apis/postman-and-pingone/use-the-pingone-postman-environment-template.html#variables-you-must-value) in the PingOne API documentation to determine the correct *{{apiPath}}* for your geography. Note that the trailing `/v1` is required (for example, `api.pingone.com/v1`).
   >
   >       Learn more in [PingOne API requests](https://developer.pingidentity.com/pingone-api/foundations/conventions/pingone-api-requests.html).
   >
   >       ### Result:
   >
   >       Postman renders a QR code.
   >
   >       ![A screen capture of the QR code that Postman renders when creating a Verify transaction.](_images/wtk1692637325156.png)
   >
   >    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](https://developer.pingidentity.com/pingone-api/verify/verified-data.html) and [Verification Metadata](https://developer.pingidentity.com/pingone-api/verify/verification-metadata.html) 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.
   >
   >         |   |                                                                                                                                                                                                                       |
   >         | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   >         |   | You can find a complete list of events logged in PingOne in [Audit Reporting Events](https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html) in the PingOne API documentation. |
   >
   >         ![A screen capture of the PingOne Audit page with 'verify' entered in the Filter field.](_images/wse1692638943327.png)
   >
   >      6. Click **Run**.
   >
   >      7. To view the specific data and scores from an event, click **View** in the **Details** column in the report summary.

   > **Collapse: PingOne DaVinci**
   >
   > To configure PingOne Verify using PingOne DaVinci:
   >
   > ## Before you begin
   >
   > Add PingOne DaVinci to your PingOne environment. Learn more in [Creating an environment](../getting_started_with_pingone/p1_getting_started_adding_environment.html).
   >
   > ## Steps
   >
   > 1. Create your theme in PingOne [Branding and themes](../user_experience/p1_branding_themes.html) to brand the PingOne Verify web experience for your end users.
   >
   > 2. (Optional) Use [language localization](#configuring-pingone-verify-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 OTP *(tooltip: \<div class="paragraph">
   >    \<p>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.\</p>
   >    \</div>)* through phone or email verification in your policy, [create notification templates](../user_experience/p1_notifications.html).
   >
   > 4. Import the [PingOne Verify quick start flow template](https://marketplace.pingone.com/item/pingone-verify-quick-start) in PingOne DaVinci by downloading it from the Ping Identity Marketplace.
   >
   > 5. Update the flow with your PingOne Verify policy:
   >
   >    1. Click the PingOne Verify `Create transaction` node in the flow.
   >
   >    2. In the **Verify Policy** list, select the policy to use.
   >
   >    ![A screen capture of the PingOne Verify Create transaction node details in PingOne DaVinci.](_images/mmx1692649385736.png)
   >
   > 6. To run the flow and trigger a PingOne Verify transaction, click **Try Flow**.
   >
   >    ### Result:
   >
   >    PingOne DaVinci renders a QR code.
   >
   >    ![A screen capture of the QR code that you can scan with your mobile device to start the verification process.](_images/qui1692650257383.png)
   >
   >    include::partial$p1\_verify\_scan\_qr\_code]
   >
   > 7. View the data submitted in the transaction and the scores returned from verification services.
   >
   >    ### Choose from:
   >
   >    * Using the API: Use the [Verified Data](https://developer.pingidentity.com/pingone-api/verify/verified-data.html) and [Verification Metadata](https://developer.pingidentity.com/pingone-api/verify/verification-metadata.html) 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.
   >
   >         |   |                                                                                                                                                                                                                       |
   >         | - | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   >         |   | You can find a complete list of events logged in PingOne in [Audit Reporting Events](https://developer.pingidentity.com/pingone-api/platform/reference/audit-reporting-events.html) in the PingOne API documentation. |
   >
   >         ![A screen capture of the PingOne Audit page with 'verify' entered in the Filter field.](_images/wse1692638943327.png)
   >
   >      6. Click **Run**.
   >
   >      7. To view the specific data and scores from an event, click **View** in the **Details** column in the report summary.

   > **Collapse: Mobile SDK**
   >
   > ## Using the PingOne Verify mobile SDK
   >
   > Mobile application developers use the PingOne Verify mobile SDK for iOS and PingOne Verify mobile SDK for Android to create the PingOne Verify app for their users. The app is a self-service app for iOS or Android devices that guides the user through the process of taking photos of their ID and a selfie and submitting the photos to PingOne for verification.
   >
   > To use the PingOne Verify mobile SDK:
   >
   > ### Steps
   >
   > 1. Run the sample app from Github:
   >
   >    * [Running the sample app for iOS](https://developer.pingidentity.com/pingone-api/native-sdks/pingone-neo-native-sdks/pingone-verify-native-sdks/pingone-verify-native-sdk-for-ios.html)
   >
   >    * [Running the sample app for Android](https://developer.pingidentity.com/pingone-api/native-sdks/pingone-neo-native-sdks/pingone-verify-native-sdks/pingone-verify-native-sdk-for-android.html)
   >
   > 2. Integrate the PingOne Verify mobile SDK into your own app:
   >
   >    * [Integrating the PingOne Verify SDK into your own app (iOS)](https://github.com/pingidentity/pingone-verify-mobile-sdk-ios/blob/master/README.md)
   >
   >    * [Integrating the PingOne Verify SDK into your own app (Android)](https://github.com/pingidentity/pingone-verify-mobile-sdk-android/blob/master/README.md)

2. Review results and dashboards in [Reviewing and managing verification](p1_verify_managing_verification.html) and [Monitoring PingOne Verify transaction activity and license usage](p1_verify_monitoring.html).