# Biometric Devices

## Overview

Biometric devices capture individuals' biometric data (fingerprint, iris scan, photo) and send it to a registration client or authentication client (app). The functional architecture of the various entities involved is shown below.

![](https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-7027df65229b99e195af7f2ec7a040e49fbe8a46%2Fsdk.png?alt=media\&token=a0f4ee02-2e62-4c06-b297-175d1e9fa16d)

## Device types

| Purpose        | Type        | Subtype\*             | Certification | Specification                                                                                        |
| -------------- | ----------- | --------------------- | ------------- | ---------------------------------------------------------------------------------------------------- |
| Registration   | Fingerprint | Slap scanner          | SBI 1.0       | [Fingerprint image spec](https://docs.mosip.io/1.1.5/biometrics/biometric-specification#fingerprint) |
| Registration   | Iris        | Double eye scanner    | SBI 1.0       | [Iris image spec](https://docs.mosip.io/1.1.5/biometrics/biometric-specification#iris)               |
| Registration   | Face        | Camera                | SBI 1.0       | [Face image spec](https://docs.mosip.io/1.1.5/biometrics/biometric-specification#face-capture)       |
| Authentication | Fingerprint | Single finger scanner | SBI 2.0       | [Fingerprint image spec](https://docs.mosip.io/1.1.5/biometrics/biometric-specification#fingerprint) |
| Authentication | Iris        | Single eye scanner    | SBI 2.0       | [Iris image spec](https://docs.mosip.io/1.1.5/biometrics/biometric-specification#iris)               |
| Authentication | Face        | Camera                | SBI 2.0       | [Face image spec](https://docs.mosip.io/1.1.5/biometrics/biometric-specification#face-capture)       |

\* An adopter may choose to have different subtypes, however, the certification needs to be adhered to.

## Enrolment flow

![](https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-4d6a56ae14bf3affe824aae2313b8e39995b192d%2Fdevices-enrolment.png?alt=media\&token=decb4613-d568-49f6-b6c2-44dcb9c1960f)

## Authentication flow

![](https://1836199994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4EyCrLbFom7vj7UcMIUZ%2Fuploads%2Fgit-blob-fd9222326bbba66e80eb78728aa849a3d2b76c3d%2Fdevices-authentication.png?alt=media\&token=5c19c530-798c-413e-bbf5-edf73699da6a)

## Compliance test kit

Compliance of a device may be tested using an [Compliance Tool Kit (CTK)](https://docs.mosip.io/compliance-tool-kit).

## Devices calculator

The following calculator may be used to estimate the number of devices required for a rollout.

[MOSIPDevicesCalculator](https://github.com/mosip/documentation/blob/84384099540b09b265703e96644a944adcdd2f3b/docs/_files/mosip-devices-calculator.xlsx)

## Partners

Providers of biometric devices are Partners of MOSIP and need to be onboarded to a given deployment of MOSIP. Specifically,

* [Device Provider](https://docs.mosip.io/1.2.0/support-systems/partner-management-services/partners#device-partner-dp)
* [FTM Provider](https://docs.mosip.io/1.2.0/support-systems/partner-management-services/partners#ftm-partner-ftmp)