PingOne

Introduction to PingOne Verify

PingOne Verify is a service that enables secure user identity verification based on a government-issued document and live face capture (a selfie), ensuring end users are who they claim to be. It bridges the gap between a person’s physical identity and their digital presence.

PingOne Verify ensures the person behind the screen is genuine and ensures three essential benefits:

  • Prevents fraud: Detects and blocks deepfakes, tampered documents, and synthetic identities during registration or high-risk transactions.

  • Minimizes user friction: Substitutes manual reviews with a seamless, automated flow that takes only seconds to complete in a browser or application.

  • Strengthens compliance: Helps meet strict Know Your Customer (KYC) and Anti-Money Laundering (AML) regulatory requirements.

Verification flow

Diagram of a PingOne Verify flow.

The image shows the following verification flow:

  1. The end user initiates verification by capturing a photo of their government-issued ID and a live selfie. This is supported through a mobile web browser, the PingOne Verify mobile SDK, or desktop browsers with an integrated or external web camera.

  2. The captured data is sent to PingOne Verify. The PingOne ID verification service uses Optical Character Recognition (OCR) and barcode scanning to extract personally identifiable information (PII) from the document. This data is used to validate document authenticity and perform a biometric match against the live selfie. Learn more in A note on extracted data in the PingOne developer documentation..

  3. When an end user’s ID information is successfully verified, the verification status is then instantly updated in the PingOne admin console and the PingOne Verify API.

    PingOne retains metadata about what was performed and the ID verification status. Any personally identifiable information (PII data) passed to PingOne is deleted by the ID verification service.

PingOne Verify transaction flow

Diagram of a PingOne Verify transaction flow.

  1. A verification transaction is triggered through PingFederate, a PingOne DaVinci flow, or a direct API call. When an end user attempts to sign on or register, they are prompted with instructions on their mobile app or desktop browser.

  2. The end user scans a QR code that links their session to a unique transaction ID. This ID is sent to the mobile app or browser to track the verification process.

  3. The end user is prompted to submit:

    • A photo of their government ID (driver license or passport).

    • A live selfie for biometric matching.

  4. The mobile app or browser sends the data and transaction ID to the PingOne ID verification service, which coordinates with a specialized service provider SP to validate the information. Once the SP returns the results, PingOne stores only the final verification status. All PII is stored for 30 minutes and then deleted by the ID verification service.

  5. The way this verification status is used depends on your specific integration and use case, for example if you’re using PingFederate you can use the authentication policy to check the stored status for all future sign-ons. You can also monitor all transaction activity in the Identity Verification dashboard in the PingOne admin console.

Features

Custom domains

Because PingOne Verify supports custom domains, your domain name can appear in any browser-based user interface that’s presented to end users. PingOne routes your domain name to the relevant PingOne services. Learn more in Domains.

Branding and themes

PingOne Verify supports branding and themes to easily change the look of your registration pages, sign-on pages, and verification pages for a particular environment. Learn more in Branding and Themes.

Email and phone notifications templates

PingOne Verify supports email and phone notifications templates so that you can create a notification for end users to verify their email address or phone number. Learn more in Notification Templates.

Metrics collection and messaging

PingOne Verify supports metrics collection and messaging for admin users to collect and audit PingOne Verify transaction events, such as the Verify App event. Learn more in Webhooks.

Language localization

PingOne Verify supports language localization so end users can interact with PingOne Verify in their preferred language. Learn more in Configuring PingOne Verify language localization.