> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v2.1/access/public-health-product-suite/health-campaign-management-hcm/facial-recognition/use-backup-pin-distributor.md).

# Use Backup Pin: Distributor

Follow these steps if face verification fails

## Overview

You get three attempts at a face scan. If all three fail, the app offers the PIN. The reason for the fallback is tagged on the attendance event, so a PIN check-in is distinguishable from a face check-in in the records.

## Steps

{% stepper %}
{% step %}

### Retry the scan

After a failed attempt, the app shows Attempt 1 of 3 with the match percentage achieved. Reposition your face, improve the lighting, and capture again.

<div align="left"><figure><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FhlFWu7tYNuZXlxPsYQRb%2Fimage.png?alt=media&amp;token=eb27688f-e881-47b6-aa88-f3f510bba984" alt="" width="145"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Read the failure screen

After three failed attempts, you see Face Verification Failed — Maximum face verification attempts exceeded.
{% endstep %}

{% step %}

### Tap Use PIN Instead

The PIN keypad opens with the prompt: Enter the 4-digit backup PIN.

<div align="left"><figure><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FigNUIaLioUujlocZ30VA%2Fimage.png?alt=media&amp;token=afe6ca55-a3cf-4ed2-9bd8-6d580208f575" alt="" width="145"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### Enter your PIN&#x20;

Tap Verify PIN. Use the PIN issued at the end of your enrollment. An incorrect entry shows Invalid PIN and clears the field.

<div align="left"><figure><img src="https://2077406040-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI0KFbSBTySIQ7TCOKnJF%2Fuploads%2FVy1cyeHRjkvIkn37lL3V%2Fimage.png?alt=media&amp;token=7d8a3e55-e0fd-4c97-a70a-4b143b63d70e" alt="" width="145"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}

### You are logged in

Continue working. The event is recorded against your user with PIN Used rather than a face match, and appears that way in Verification History.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Note for system users:**

A system user has two fallback routes: the enrollment PIN and their normal HCM credentials. A helper has neither — a helper can only be verified by face, by the Distributor whose device they are enrolled on.

Repeated PIN use is visible in the records but is not automatically flagged as an anomaly in this release. Supervisors should review the Verification History for workers who check in by PIN more than occasionally.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digit.org/health/v2.1/access/public-health-product-suite/health-campaign-management-hcm/facial-recognition/use-backup-pin-distributor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
