> 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-hand.md).

# Capturing Biometrics (Hand)

The following procedure describes how to enrol a Cardholder's fingerprints using a MorphoWave Reader:

**Note:** Previously used DESFire cards should not be encoded for different cardholders.

1. Click the **Hand** tab.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-99ce13465e5e31de633dcdc75cf2fd8c455b3bf0%2Fcardholderbiometrics_operationalmode_morphowavetab.png?alt=media)

   **Note:** All eight finger locations displaying as ‘blank’ indicates that the Cardholder is not enrolled for MorphoWave.
2. Click the **Capture** button.

   The MorphoWave Fingerprint Enrolment screen displays.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-69d33d7289d3c279ff5eb6286bff128fb64d2c1d%2Fmorphowavefingerprintenrolmentscreen1.png?alt=media)

   **Note:** Hand overlays display briefly to demonstrate the order of the fingers.
3. If the Morpho Biometric Card Type (in the Configuration Client) has been configured to allow changes at the time of enrolment, you can change the following default values if necessary:
   * **Fingerprint Quality** by selecting Standard, High or Very High (Default and recommended option = Standard), and
   * 'Access and Duress hands’ by selecting Access, Unused or Duress for each hand.
4. If there is more than one **Enrolment Reader** listed, ensure the correct one is selected.
5. Change the status of each fingerprint as required:

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-a46b50232bf620883d4a0a6b7df92585af4b63c9%2F38897.png?alt=media) Active

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-b1aca8cb0c634a8fa6f85b01f9996aad0b293987%2F38898.png?alt=media) Bandaged

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-85e5a19faae17efacfd564c5229108b9fdcc7276%2F38899.png?alt=media) Missing

   **Note:** At least one fingerprint must be active on each hand.
6. Click the **Next** button.

   The wizard displays the enrolment screen for the hand selected as the ‘set access’ hand.

   **Notes:**

   * When both hands are selected as "ACCESS" hands, the right-hand enrolment is displayed first.
   * Only "ACCESS" biometrics will be encoded to the card, (e.g. if one hand is selected as "DURESS", then this hand’s fingerprints will not be written to the card).

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-d25cededc4933ce9e95cfeaa37456e6b216def31%2Fmorphowavefingerprintenrolmentscreen3.png?alt=media)

   A green light on the MorphoWave Reader indicates connection has been established.
7. Insert the hand to enrol between the cover and optical sensor of the reader, ensuring it is flat, palm down, and fingers are spread slightly apart.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-8fa6b7af94285a092068661e619912754f2e1ba3%2Fmorphowavecompactreader.png?alt=media)
8. Slide the hand in the appropriate direction for the hand being enrolled, (i.e. from right to left for the right-hand, and from left to right for the left-hand, with the Index finger first).

   Once the hand has enrolled successfully, a message displays indicating that the device is ready to enrol the other hand.

   **Notes:**

   * After 5 unsuccessful attempts the system times out.
   * If enrolment is unsuccessful, a message indicating the reason will display. *For example:*

     If the hand slides from the wrong direction the message *"Bad hand direction"* displays.

     If the hand is not waving properly between cover and optical sensor the message *"Wave hand in parallel"* displays.
9. Repeat Steps 7 - 8 for the other hand.

   Once that hand has enrolled successfully, another message displays indicating the hand has been enrolled, and the **Accept** button becomes enabled.
10. Click the **Accept** button.

    The MorphoWave Fingerprint Enrolment screen closes, and the **Hand** tab of the Cardholder Biometrics Tile now shows enrolled fingerprints.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-80cf88eb8e5bc7a3704e9ef12576f0e0669c201a%2Fcardholderbiometrics_morphowavetab_enrolled.png?alt=media)

    **Notes:**

    * The MorphoWave DESFire object will not encode "UNUSED" and "DURESS" fingerprints to a card. Only "ACCESS" fingerprints will encode to cardholder’s card.
    * Once fingerprints are enrolled and saved (to either database and card, or database only), any changes to the fingerprints status will result in the following message displaying on the Cardholder Biometrics Tile:

      *"If these biometrics are encoded to a card, the card will need re-encoding."*
    * If a cardholder has had biometrics enrolled previously and the fingerprint status for both hands has changed to "UNUSED", the following message will display on the Cardholder Biometrics Tile:

      *"At least one hand must be set to Access to use the reader. If these biometrics are encoded to a card, the card will need re-encoding."*

      When the operator starts encoding the card for the cardholder (with "Card Number + Biometrics") the following warning message will display, giving them the option to either proceed with encoding or not.

      ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-ee33baf104d9956a17f52edff9bfef13bc8ae97e%2Fmorphowave_noaccesshand.png?alt=media)

      **IMPORTANT:** Even if the card is encoded, the cardholder won’t be able to access any MorphoWave Biometric Readers. However, if the card has other objects, (e.g. MIFARE DESFire object), it can still be read by Gallagher readers.
11. Click the **Save** button to save the fingerprints to the database, or click the **Revert to Saved** button to undo.
12. Click the **Verify** button.

    **Note:** A dialog will display if there is more than one enrolment reader available. If so, select the correct reader from the list and click the **Next** button.

    A message displays on the tile indicating which hand to verify.

    ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-418bb264bed2c69a50d3122b7502b3e4a52a3175%2Fmorphowave_readytoverify.png?alt=media)
13. Wave the appropriate hand over the enrolment reader to verify the saved fingerprints.

    A message displays indicating the hand was successfully verified, followed by a message indicating it is ready to verify the other hand.
14. Wave the other hand over the enrolment reader.

    A message displays indicating that hand was also successfully verified.
15. 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-hand.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.
