---
title: Use cases
description: The following are two common uses for the PingOne Verify Integration Kit.
component: pingone
page_id: pingone:pingone_verify_integration_kit_11:pf_p1_verify_ik_use_cases_11
canonical_url: https://docs.pingidentity.com/integrations/pingone/pingone_verify_integration_kit_11/pf_p1_verify_ik_use_cases_11.html
revdate: July 3, 2024
section_ids:
  authentication: Authentication
  registration: Registration
---

# Use cases

The following are two common uses for the PingOne Verify Integration Kit.

## Authentication

When a user signs on, you can use PingOne Verify to verify a user's identity instead of, or in combination with, a standard multi-factor authentication (MFA) *(tooltip: \<div class="paragraph">
\<p>An electronic authentication method where a user is granted access only after presenting two or more verification factors for authentication.\</p>
\</div>)* step.

For example, you might use PingOne MFA by default and only trigger PingOne Verify based on:

* Frequency, such as annually

* Group, such as for members of the "contractors" group

* Account age, such as for accounts made in the last two months

* Past verification, such as users that have never completed the verification process

* Security risk, such as for users with a PingOne Protect risk evaluation of `MEDIUM` or `HIGH`

You can create these rules in your PingFederate authentication policy.

## Registration

When a person registers a new user account, you can use PingOne Verify to verify their identity against a piece of government photo ID. By requiring identity verification, you can reduce the number of accounts created by bots, spammers, and imposters.

Optionally, your mobile app can use the reliable information from the person's government photo ID to populate user attributes in your datastore.