> 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/site-management/cardholders/reading-mifare-cards-using-a-mifare-usb-encoder.md).

# Reading MIFARE Cards using a MIFARE USB Encoder

### Introduction

When lost, unnamed cards are handed in, this feature allows you to identify the cardholder that has lost their card. The Cardholders data is displayed when the system is prompted by the user and an active card is swiped against either an **ACR1252**, a **SDI010** or **SDI011G Contactless MIFARE Reader and Encoder**.

**Notes:**

* This feature is **not** a licensed feature, and only works with the following encoders:
  * **ACS ACR1252 1S CL Reader PICC 0**
  * **SCM Microsystems Inc. SDI010 Contactless Reader 0**
  * **SCM Microsystems Inc. SDI011G Contactless Reader 0**
* Operators require the "View Cardholder" operator privilege to use this feature.

This procedure describes how to read a MIFARE card using an ACS or SCM MIFARE USB Encoder in Gallagher Command Centre.

### Procedure

1. Click **Monitor** from the menu bar, then **Read MIFARE Card**.

   The **Read MIFARE Card** dialog displays.

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

   By default, the first available USB encoder is used for reading and populates the **Encoder** field. If there are other USB encoders connected to the workstation they will also appear in the drop-down list.
2. Select the required **Encoder** from the drop-down list.

   <table><thead><tr><th width="216">If...</th><th>then...</th></tr></thead><tbody><tr><td>no USB Encoder is detected</td><td>the message <em>"No USB Encoder was detected"</em> appears in the Status bar.</td></tr><tr><td>the workstation is enabled for SmartCard logon</td><td><ul><li>the 'Read MIFARE Card' feature will be disabled on the workstation,</li><li>the <strong>Encoder</strong> field will be empty, and</li><li>the message <em>"Disabled on workstations enabled for Smartcard log-on"</em> will appear in the Status bar.</li></ul></td></tr></tbody></table>
3. Place the card on the encoder.

   The details of the card display in the **Read MIFARE Card** dialog if the card contains Gallagher data and the corresponding cardholder can be found in the system.

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

   **Notes:**

   * If the Card Type and Cardholder are found in Gallagher Command Centre but the issue level is different, (e.g. a new card was issued to the cardholder with the same card number but different issue level), then the message **"\*Issue level differs"** will display to the left of the **Cancel** button.
   * If no Gallagher data is found on the card, then the card details will be greyed out and the message **"No Gallagher data was found"** will appear in the Status bar.
   * If Gallagher data is found on the card, but the card does not belong to the system, then:
     * the **Card Type** field will show as "Unknown Card Type",
     * the **Cardholder** field will show as "Unknown Cardholder", and
     * the **View Cardholder Properties** button will be disabled.
   * Possible **MIFARE Card Types** that could display are:

     MIFARE Classic 1k

     MIFARE Classic 4k

     MIFARE Plus S - Security Level 0

     MIFARE Plus X - Security Level 0

     MIFARE Plus S 2k - Security Level 3

     MIFARE Plus X 2k - Security Level 3

     MIFARE Plus S 4k - Security Level 3

     MIFARE Plus X 4k - Security Level 3

     MIFARE DESFire 2k

     MIFARE DESFire 4k

     MIFARE DESFire 8k
   * The **Serial Number to use as card number** field shows the unique Card Serial Number (CSN) of the card in decimal format and reverse byte order. The **Serial number to use in other systems** field shows the unique serial number of the card (UID).

     **Note:** If the card is assigned to a Cardholder, is of a type where re-encoding is prevented, and it has a different CSN from one recorded in the past for that identifier, a 'Potential Duplicate Card' alarm will be generated. If this occurs, we recommend the safest course of action for your site is to issue the Cardholder who is currently assigned a Card with that identifier, a new card.
   * If the card is unknown, the **MIFARE Card Type** field may display "Unknown ISO1444-3". Likewise, the message **"The card selected is an unsupported ISO14443-3 card"** may display in the Status bar if the card is detected as one of the known unsupported types.
4. Click the **View Cardholder Properties** button.

   The properties of the Cardholder that the card belongs to opens.
5. Present the next card if there are more to read.

### Notes

* The encoder beeps the first time a card is placed on it and the **Read MIFARE Card** utility in Command Centre is used, and then goes quiet.
* The encoder beeps when a card is placed on it, before Command Centre is opened and the **Read MIFARE Card** utility is used.


---

# 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/site-management/cardholders/reading-mifare-cards-using-a-mifare-usb-encoder.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.
