> 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/cc-hardware/credentials/mobile-connect/troubleshoot/third-party-mifare-classic-cards-stop-working-when-mobile-wallet-is-enabled.md).

# Third-party MIFARE Classic cards stop working when Mobile Wallet is enabled

Understand why third-party MIFARE Classic cards stop working on T Series readers when Mobile Wallet is enabled.

**Applies to:** sites with Mobile Wallet enabled (third-party MIFARE Classic cards) · Gallagher T Series readers

Third-party MIFARE Classic cards do not work on any Gallagher T Series reader when the Command Centre system has Mobile Wallet enabled. Gallagher-issued MIFARE Classic cards work without issue. For the Apple Employee Badge, see [Employee badge in Apple Wallet](https://help.security.gallagher.com/knowledge-hub/products/cc-hardware/credentials/mobile-connect/employee-badge-in-apple-wallet.md).

**What is known:** the problem seems to be directly related to the manufacturer of the card. When Mobile Wallet is disabled, the card's CSN reads fine.

![A white third-party test card labelled Chip: NXPP71 Mifare 1K, Test date: 22/03/2024](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-1ffa9f53b46f0b709ba1600fd12258a7bba908c4%2FSECHUB-TS-APPLE-WALLET-MIFARE-01-third-party-card.png?alt=media)

### Resolution

At the time of writing (2024-12-02), there is no solution other than using a Gallagher-sourced card.


---

# 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/cc-hardware/credentials/mobile-connect/troubleshoot/third-party-mifare-classic-cards-stop-working-when-mobile-wallet-is-enabled.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.
