> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-components/biometrics/biometric-devices.md).

# 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.

![](/files/bwhNSN0Q8NsmzSjeF9XF)

## 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

![](/files/FeeBHmAvK0mvRoMhDjAM)

## Authentication flow

![](/files/QNTavnji1hIFbnzXfM2H)

## 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](/1.2.0/id-lifecycle-management/support-systems/partner-management-services/partners.md#device-partner-dp)
* [FTM Provider](/1.2.0/id-lifecycle-management/support-systems/partner-management-services/partners.md#ftm-partner-ftmp)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.mosip.io/1.2.0/id-lifecycle-management/supporting-components/biometrics/biometric-devices.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.