> 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/command-centre-client/configuring-command-centre/configuring-licensable-features/universal-credential.md).

# Universal Credential

### Introduction

The Universal Credential feature enables Gallagher readers to read third-party DESFire mobile wallets and cards using a flexible, configuration-based approach. By defining credential formats through configuration rather than custom software development, Command Centre can more easily support new formats, improving interoperability, and expanding the range of credentials that can be read by Gallagher readers.

Universal Credential Types are created and managed within the Universal Credentials Viewer in Command Centre. Credential formats are defined using a JSON configuration file. The Universal Credential Type can then be assigned to cardholders using REST APIs or within Command Centre for cards.

### Features and Functionalities

The Universal Credential feature supports:

* Reading Gallagher Apple Employee Badges synced from another system.
* Reading third-party DESFire mobile wallets on Apple and Google devices.
* Reading Gallagher DESFire Non-Diversified cards encoded by another system.
* Reading third-party DESFire cards, encoded with provider-defined formats and secured with a custom key.
* Reading customer-defined DESFire cards, encoded with a customer-specific format and secured with a customer-managed key.
* Reading multiple DESFire formats, each with its own key.
* Adding support for new DESFire wallet and card formats through JSON configuration files.

### Compatibility

* Reading third-party mobile wallets and cards is supported on Controller 7000 only.
* Reading third-party mobile wallets is supported on multi-tech readers only. High Security multi-tech readers do not support mobile wallets.
* The RESTCardholders license feature is required when assigning Universal Credentials to cardholders via REST APIs.
* Multi-server Command Centre deployments are not supported.
* The Universal Credential feature supports low-level elevator integrations when using Gallagher readers. The Kone ELI (KONE 1000 Integration) and ThyssenKrupp high-level interfaces are supported when using Gallagher readers.
* Changing a Card Type to a Universal Credential Type using the Cardholder Bulk Change Wizard or Enterprise Data Interface (EDI) is not supported. Cards can be assigned or removed in bulk using REST APIs.

### Limitations

* A maximum of ten Universal Credential Types is supported.
* Apple’s Enhanced Contactless Polling (ECP) protocol can advertise only a single Terminal Capabilities Identifier (TCI) across all Gallagher readers. As a result, only one Apple Wallet Universal Credential Type can be supported at a time.
* Card PINs are not supported as part of the credential format. Where a second factor is required for physical cards, Gallagher recommends using "PIN is User Code". User Codes can be assigned manually or imported using EDI or REST APIs.
* Authentication will fail for a diversified 2K3DES key, because the controller only supports diversifying AES-128 keys.

### Licensing

To create and configure Universal Credential Types, the following feature license is required:

`[Features]`\
`UniversalCredential=1`

To read third-party mobile wallet credentials, the following license is required:

`[Limits]`\
`Mobile Wallet Readers=X`

Where `X` is the number of readers that can read mobile wallet credentials.

**Notes:**

* The *Mobile Wallet Readers=X* limit license string is required when using this feature to read third-party mobile wallet credentials, or Gallagher Apple credentials synced from another system. This limit controls the number of "Mobile Wallet" checkboxes that can be ticked within the "Permitted Card Technology" frame, on the "Advanced" tab of the Reader’s FT item. If the "Mobile Wallet" count exceeds the licensed limit, whether through configuration changes or a licence reduction, the periodic licence check raises a "Licence Limit Exceeded" alarm for "Mobile Wallet Readers" and the site enters the normal grace period. If the overage is not resolved before the grace period expires, the site becomes unlicensed and creation of new items is prevented.
* The *Mobile Credentials=X* limit license string **is not** required when using this feature to read Gallagher Apple credentials synced from another Gallagher system.
* The *Mobile Wallet Readers=X* limit license string **is not** required when using this feature to read third-party physical cards.

### Configuration

To configure Universal Credentials, select the item that you require further detail on:

[Mobile Wallet Credentials](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/universal-credential/mobile-wallet-credentials.md)

[Physical Credentials](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/universal-credential/physical-credentials.md)

[Creating a Universal Credential Type](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/universal-credential/creating-a-universal-credential-type.md)

[Editing a Universal Credential Type](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/universal-credential/editing-a-universal-credential-type.md)

[JSON File Configuration](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/configuring-licensable-features/universal-credential/json-file-configuration.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/command-centre-client/configuring-command-centre/configuring-licensable-features/universal-credential.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.
