> 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/encoding-morpho-cards-for-verification.md).

# Encoding Morpho Cards for Verification

### Introduction

This section describes the overall process for encoding Morpho cards for biometric verification, (i.e. when a person identifies themselves prior to the biometric operation, e.g. by badging their card, and then the biometric operation is used to verify that the person is in fact who they say they are).

When necessary, this process refers to separate step-by-step procedures that are detailed elsewhere, (i.e. either as separate procedures in this section, or in other sections in this online help).

**Notes:**

* If you are reusing existing cards you will need to contact Gallagher Technical Support for a MIFARE Eraser Utility to blank the cards.
* **Card sizes for DESFire Biometric objects:**

  For Fingerprints (Sigma) only the minimum is 1k.

  For Hand (MorphoWave) only the minimum is 4k.

  For Face (VisionPass) only the minimum is 2k.

  The recommendation is 4k minimum for biometric objects on card.

### Process

1. Set up a Morpho Biometric Type.

   Refer to the [Creating a new Morpho Biometric Card Type](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/morpho-biometric-integration/creating-a-new-morpho-biometric-card-type.md) for the procedure.
2. Set up a Card Type with:

   * the same Region and Facility codes used for the Morpho Biometric Type, and
   * the correct card number range that is valid for Morpho.

     **Note:** The valid range for Gallagher is 31 - 8,388,607, and for Morpho it is 8,388,608 - 16,777,215.

   Refer to [Setting up Card Types](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/card-types/setting-up-card-types.md) for the procedure.
3. Create a card layout for the Card Type created in Step 2, and include the appropriate Morpho object in the layout.

   Refer to:

   * [Designing Card Layouts](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/designing-card-layouts.md) for full details on configuring a card layout, and
   * the appropriate procedure below for the type of Morpho object you are adding to the card layout and what you want encoded on the card:
     * [Adding a Morpho MIFARE Classic object](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/designing-card-layouts/working-with-objects/card-type-objects/adding-a-morpho-mifare-classic-object.md),
     * [Adding a MorphoWave DESFire object](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/designing-card-layouts/working-with-objects/card-type-objects/adding-a-morphowave-desfire-object.md),
     * [Adding a Morpho DESFire object](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/designing-card-layouts/working-with-objects/card-type-objects/adding-a-morpho-desfire-object.md),
     * [Adding a Morpho FVP DESFire or Morpho VisionPass DESFire object](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/designing-card-layouts/working-with-objects/card-type-objects/adding-a-morpho-fvp-visionpass-desfire-object.md) and
     * [Adding a Morpho FVP MIFARE Classic object](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/designing-card-layouts/working-with-objects/card-type-objects/adding-a-morpho-fvp-mifare-classic-object.md)
4. Assign the Card Type to a cardholder.

   Refer to [Adding a Card to a Cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/cardholders/adding-a-card-to-a-cardholder.md) for the procedure.
5. Encode the card (via the **Print/Encode** tab of the Cardholder properties).

   Refer to [Printing and/or Encoding a card from a cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/printing-encoding-cards/printing-and-or-encoding-a-card-from-a-cardholder.md) for the procedure. Although this procedure presumes you located the Cardholder via the **Cardholder** List Window, it can still be followed if you used the Find Tool to locate the Cardholder.

   **Notes:**

   * If a card fails to encode, the encode procedure should be repeated, or the card should be securely discarded.
   * If you haven’t enrolled any biometrics when "Card Number + Biometrics" is selected, or any fingerprints/veins when "Card Number + Biometrics" is selected, a warning message will display indicating that these must be captured prior to encoding the card.
   * If the Morpho MIFARE object on the Card Type is set to "Card Number Only", then the card will be encoded normally. However, if it is set to "Card Number + Biometrics", then an additional **Capturing biometrics** dialog MAY display if you have not already captured fingerprints/veins normally. This dialog may allow you to save the fingerprints/veins to the database as well as encode them on the card, depending on the **Privacy Settings** set on the Morpho Biometric Type created at Step 1.
   * The Issue Level is ignored so changing the Issue Level on a Morpho card has no impact on the Cardholder's ability to gain access through Morpho readers. It is advised that you configure a default Issue Level, (i.e. '1') by checking the Card Issue Level must match default checkbox for all encoded cards.


---

# 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/encoding-morpho-cards-for-verification.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.
