---
title: PingOne Verify Integration Kit
description: The PingOne Verify Integration Kit allows PingFederate to use the PingOne Verify service for personal identity verification based on government photo ID.
component: pingone
page_id: pingone:pingone_verify_integration_kit:pf_p1_verify_ik
canonical_url: https://docs.pingidentity.com/integrations/pingone/pingone_verify_integration_kit/pf_p1_verify_ik.html
revdate: October 28, 2025
section_ids:
  features: Features
  components: Components
  intended-audience: Intended audience
  system-requirements: System requirements
---

# PingOne Verify Integration Kit

The PingOne Verify Integration Kit allows PingFederate to use the PingOne Verify service for personal identity verification based on government photo ID.

## Features

* Initiate an identity verification process as part of user registration or sign-on.

* Supports mobile web identity verification.

* Supports the [PingFederate authentication API](https://docs.pingidentity.com/pingfederate/latest/developers_reference_guide/pf_authentication_api.html).

* Supports the [JavaScript Widget for the PingFederate Authentication API](https://github.com/pingidentity/pf-authn-js-widget).

* Supports version 2 of the [PingOne Verify Mobile SDK with QR verification flows](https://apidocs.pingidentity.com/pingone/native-sdks/v1/api/#pingone-verify-native-sdks).

## Components

* PingOne Verify IdP Adapter

  * Allows PingFederate to use PingOne Verify to trigger an identity verification challenge as part of the PingFederate authentication policy or registration flow.

* Templates

  * Allow the adapter to show the status of the verification process.

  * Allow you to modify the appearance of pages shown to the user during authentication.

* Language packs

  * Allow you to customize or localize the messages returned by the PingFederate authentication application programming interface (API) *(tooltip: \<div class="paragraph">
    \<p>A specification of interactions available for building software to access an application or service.\</p>
    \</div>)* and shown on the templates during authentication. Learn more in [Localizing messages for end users](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_local_message_end_users.html) in the PingFederate documentation.

## Intended audience

This document is intended for PingFederate administrators.

If you need help during the setup process, learn more in the following resources:

* The following sections of the PingOne documentation:

  * [Introduction to PingOne Verify](https://docs.pingidentity.com/pingone/identity_verification_using_pingone_verify/p1_verify_introduction.html)

* The following sections of the PingFederate documentation:

  * [Managing IdP adapters](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_managing_idp_adapters.html)

  * [Authentication policies](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_authentication_policies.html)

## System requirements

* PingFederate 11.3 or later

* To allow PingFederate to make outbound HTTPS connections, you might need to allow the following host names in your firewall:

  * https\://api.pingone.com, https\://api.pingone.asia, or https\://api.pingone.eu

  * https\://auth.pingone.com, https\://auth.pingone.asia, or https\://auth.pingone.eu