> For the complete documentation index, see [llms.txt](https://help.security.gallagher.com/knowledge-hub/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/enrolling-users/capturing-biometrics-fingerprint-or-finger-vein.md).

# Capturing Biometrics (Fingerprint or Finger Vein)

Use the following procedure to enrol a Cardholder for a Morpho Fingerprint or Finger Vein:

1. Click the **Capture** button for either the Main or Duress Biometrics group.

   **Note:** For fingerprint or finger vein capture to work the following needs to be installed:

   <table><thead><tr><th width="184">For the...</th><th>you need...</th></tr></thead><tbody><tr><td>Server Workstation</td><td><ul><li>Microsoft Visual vc10redist_x86</li><li>Microsoft Visual vc12redist_x86</li><li>Microsoft Visual vc14redist_x86</li><li>Microsoft Visual vc14redist_x64</li></ul></td></tr><tr><td>Client Workstation</td><td><ul><li>Microsoft Visual vc10redist_x86</li><li>Microsoft Visual vc12redist_x86</li><li>Microsoft Visual vc14redist_x86</li><li>Microsoft Visual vc14redist_x64</li></ul></td></tr></tbody></table>

   If they are missing, the following error message will display when you click the **Capture** button:

   *"Failed to capture fingerprints.*

   *Reason: Device DLL or one of its dependencies is missing or not registered."*

   These files are located in the `'Utilities\Morpho\Microsoft Redistributables'` folder of the Command Centre installation files. See [Installing Microsoft Redistributables](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/installation/installing-microsoft-redistributables.md).

   The Capture Finger screen displays with instructions on what to do next within the appropriate finger capture area.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-caf8ba0b52452909b1c17583c9eed8d709811db4%2Fcapturefirstfingerprint_tile.png?alt=media)
2. Select the finger you want to capture biometric templates for from the **Finger** drop-down list.

   As a complete capturing process, both the Main and Duress Biometric groups require fingerprints or finger veins to be captured for two fingers, (e.g. the 'Left Index Finger' and the 'Left Middle Finger'), and three fingerprints/finger veins must be captured per finger.

   **Note:** Biometric captures are stored on the reader and take up quite a bit of space, therefore if duress is not an issue for your site it is suggested that you do not bother capturing 'Duress Biometrics'. Also, duress will only work if a cardholder has been given access to that Morpho Reader.
3. Place the appropriate finger on the enrolment device.

   As each biometric capture occurs the quality of that individual capture is displayed at the bottom of the biometric display area, which remains visible after they have moved on to the next capture.

   **Notes:**

   * The overall quality (score) of the biometrics that are captured needs to be more than 165 to be validated by the system.
   * At any time the user can click the **Recapture** button to re-start the process for capturing the three samples for the current finger.
4. Repeat Step 2 twice so you have three captures of the same finger.
5. Repeat Steps 2 - 3 for the second finger of that Biometric group.

   On capturing two fingers successfully:

   * an image displays under the appropriate Biometric group on the Cardholder Biometrics Tile to indicate that something has been captured,
   * the **Clear** button (used for deleting the captured biometrics) for the group is enabled, and
   * the **Verify** button is enabled.

     This button allows you to verify that the Cardholder's fingerprint/finger vein templates that have been captured can actually be used successfully for biometric authentication, (i.e. there is a match between the captured templates and the person's fingerprints/finger veins).
6. Click the **Verify** button.

   The Verify Biometric pop-up displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-6b08c30c64f1e3d40b8534d4e85049cf58786cd9%2Fverifyfingerprint_popup.png?alt=media)
7. Place the appropriate finger on the enrolment device.

   The system verifies whether the captured biometrics match the existing templates already captured, and the appropriate message box displays indicating if there is a match or not. Once a match has been made the finger image is removed and result is displayed at the bottom.
8. Click the **Close** button.


---

# 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://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/enrolling-users/capturing-biometrics-fingerprint-or-finger-vein.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.
