> 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/products/integrations/third-party-readers/idemia-morpho/configure/idemia-morpho-encoding-a-card-to-use-on-morpho-readers.md).

# Encode cards for IDEMIA readers

Configure Morpho card objects and authentication modes for IDEMIA biometric reader access.

You can enable card-only access on Morpho readers that have built-in MIFARE readers.

{% hint style="warning" %}
**Morpho objects can only be encoded on-site, not via Bureau encoding.**
{% endhint %}

The site needs to be able to encode cards on site, or to have a Morpho object on the cards it uses.

1. Add a **Morpho object** (Classic, Plus, or DESFire, per the site's card type) to the card layout configuration.
2. Re-encode cardholders' cards to add the object.
3. Change the reader configuration so the card can be used to gain access. See Authentication Mode below.

{% hint style="info" %}
Wave Templates encode only onto **DESFire 4k+** cards, from **v8.70+**. They do not include the Duress Templates.
{% endhint %}

### Authentication Mode (at the reader)

Authentication Mode decides whether the cardholder has card-only access, or must present their finger, or enter a PIN, or both. The reader authenticates a cardholder using one of these methods. The options are:

* **Finger Only** (Identification).
* **Card Selects** (Verification with fingerprint/vein or ID on card).
* **User Selects** (default; Identification, or Verification with fingerprint/vein or ID on card).

For card use, set **User Selects**. Card Selects blocks cardholders without a Morpho object on their card, whereas User Selects lets them fall back to finger. After changing the mode, it is good practice to press **Set MIFARE Key** on the reader to push card keys to it.

A common encoding error is "Failed to derive the biometric master and read keys from the site key". For the fix, see [Card encoding fails with a biometric master-key error](/knowledge-hub/products/integrations/third-party-readers/idemia-morpho/troubleshoot/idemia-morpho-morpho-card-encoding-error-failed-to-derive-the-biometric-master-keys.md).


---

# 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/products/integrations/third-party-readers/idemia-morpho/configure/idemia-morpho-encoding-a-card-to-use-on-morpho-readers.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.