---
title: Mobile SDK Integration Flows
description: Learn how the PingOne Recognize components interact with your app.
component: recognize
page_id: recognize:mobile-sdk:mobile-sdk-integration-flows
canonical_url: https://docs.pingidentity.com/recognize/mobile-sdk/mobile-sdk-integration-flows.html
llms_txt: https://docs.pingidentity.com/recognize/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: April 20, 2026
section_ids:
  introduction: Introduction
  integration-overview: Integration Overview
  enrollment-flow: Enrollment Flow
  authentication-flow: Authentication Flow
  authentication-in-a-web-application: Authentication in a Web Application
  authentication-on-a-mobile-app: Authentication on a Mobile App
  pingone-recognize-components: PingOne Recognize Components
  pingone-recognize-sdk: PingOne Recognize SDK
  pingone-recognize-backend: PingOne Recognize Backend
---

# Mobile SDK Integration Flows

## Introduction

Learn how the PingOne Recognize SDK components can be integrated into a mobile application and backend server to enable biometric authentication.

## Integration Overview

### Enrollment Flow

To authenticate with PingOne Recognize, a user must first enroll their biometric template. Enrollment with PingOne Recognize consists of registering the user's biometric features in a privacy-preserving manner using the various [enrollment methods](mobile-sdk-enrollment.html) from the PingOne Recognize SDK.

### Authentication Flow

The most common authentication scenarios for the PingOne Recognize SDK are:

* Access to a web application

* Access on a mobile application

### Authentication in a Web Application

In this scenario, the user is trying to access a resource in a web application for which strong authentication is required. The web application backend sends a push notification to the customer app to request that the user identify themselves with PingOne Recognize. After biometric authentication is successful, the flow returns to the web application backend, which leverages the APIs exposed by the PingOne Recognize backend to perform additional security checks.

Once the PingOne Recognize backend confirms that the authentication was successful, the user is allowed access to the resource.

### Authentication on a Mobile App

In this scenario, the user is trying to access a resource directly in the mobile application for which strong authentication is required. The mobile application sends a push notification to the customer app to request that the user identify themselves with PingOne Recognize. After biometric authentication is successful, the flow returns to the mobile application backend, which leverages the APIs exposed by the PingOne Recognize backend to perform additional security checks.

Once the PingOne Recognize backend confirms that the authentication was successful, the user is allowed access to the resource.

## PingOne Recognize Components

As mentioned, PingOne Recognize is composed of two main blocks:

* PingOne Recognize SDK

* PingOne Recognize backend / Confirmation API Service

### PingOne Recognize SDK

The PingOne Recognize SDK supports both Android and iOS and exposes API methods to interact with the PingOne Recognize Privacy-Preserving Network to perform the following actions:

* Enroll a user

* Authenticate

* De-enroll

* Restore backup

### PingOne Recognize Backend

The PingOne Recognize SaaS backend offers APIs that can be used to perform security checks through backend-to-backend calls. Specifically, it is possible to interrogate the PingOne Recognize backend after the SDK returns an OK response for an authentication attempt.