> 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/licensable-features/apple-employee-badge/2-configure-mobile-wallet-readers.md).

# 2. Configure Mobile Wallet Readers

Only Gallagher Multi-Tech readers, with the NXP chip that supports reading wallet credentials can be used. Readers manufactured from 2019 onwards have the required NXP chip.

From Command Centre v8.90 readers report their device attributes. The FT Support Tool can be used to report all readers that are wallet capable, their assigned door(s), and controller. The FT Support Tool is included with the Command Centre installation software in the `'Utilities\FT Support Tool'` directory.

From Command Centre v9.10 CEIP reports the number of readers that are wallet capable.

<table><thead><tr><th width="354">CEIP Metric</th><th>Description</th></tr></thead><tbody><tr><td>hardware.usage<br>hardware.readers.count</td><td>This metric reports the total number of readers configured.</td></tr><tr><td>hardware.usage<br>hardware.readers.mobileWalletCapable.count</td><td>This metric reports the total number of readers configured that are wallet capable.</td></tr><tr><td>hardware.usage<br>hardware.readers.mobileWalletEnabled.count</td><td>This metric reports the total number of readers that have been configured to read wallet credentials, (i.e. the <strong>Mobile Wallet</strong> checkbox is ticked in the reader’s properties).</td></tr></tbody></table>

**Note:** High Sec Multi-Tech readers are not supported.

Readers can be configured individually (via the **Advanced** tab of the Reader Properties) or site-wide from the Server Properties.

This procedure describes how to configure all readers to read a wallet credential, as follows:

1. Click **File** from the menu bar, then **Server Properties**.

   The Command Centre Server Properties window opens.
2. Click the **Card Security** tab.
3. In the **Permitted Card Technology** section, tick the **Mobile Wallet** checkbox.

   **Note:** The T30 Keypad and T20 Terminal software will change, reducing the NFC read range for mobile wallets to less than 11cm, ensuring a valid access request is being made at the reader.

   ![](https://3000903572-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfCvaxj3suxNBzdwQndVT%2Fuploads%2Fgit-blob-9215f764ff049d330cf039e796a394eb3cdc79e6%2Fcardsecurity.png?alt=media)
4. Click the **OK** button.

   **Notes:**

   * A Reader Bulk Change can be performed to change the card technologies accepted at readers and Find tool results can be dragged onto the Reader Bulk Change wizard. See [Initiating a new Reader Bulk Change](https://help.security.gallagher.com/knowledge-hub/configuration-client/site-management/bulk-changes/initiating-a-new-reader-bulk-change.md) for further detail.
   * On the **Mobile Access Settings** tab of the Server Properties, the option Second factor always required for mobile, enforces second factor at all readers when reading an Apple Employee Badge. Passcode, Touch ID, or Face ID will be required at the iPhone. Passcode will be required at the Apple Watch.

     **Note:** This functionality is not supported when the reader is assigned to an Elevator Car.


---

# 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/licensable-features/apple-employee-badge/2-configure-mobile-wallet-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.
