> 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/mobile-wallet-credentials.md).

# Mobile Wallet Credentials

### Mobile Wallets

Third-party mobile wallet credentials are sourced from a Gallagher Technology Partner. The Technology Partner's backend integrates with a wallet Credential Provider to manage the mobile credential lifecycle, including provisioning and revocation, and to initiate the “Add to Wallet” experience.

The Credential Provider supplies the wallet credential technology and associated provisioning services. The Credential Provider also manages their wallet credential formats, cryptographic keys, and wallet artwork. To retrieve your wallet keys, you may need to complete the Credential Provider’s key retrieval form online.

### Mobile Wallets Architecture

This architecture allows Gallagher readers to read third-party mobile wallet credentials. The credential formats and keys are stored at the controller, allowing multiple formats to be read and distributed from the Command Centre server.

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

### Mobile Wallets High-Level Process

* A Command Centre operator creates and configures Universal Credential Types. For example, an Apple Wallet Universal Credential Type and Google Wallet Universal Credential Type. Keys are entered into Command Centre. The credential format is specified using a JSON file.
* The Technology Partner provisions mobile wallet credentials to users.
* Users select “Add to Wallet” on their smartphones, which will create the credential records within the Technology Partner’s platform.
* The Technology Partner creates a REST API import utility. Using Gallagher REST APIs, the Universal Credentials are assigned to cardholders in Command Centre.
* The Command Centre server distributes the configuration to controllers.
* When a user presents their smartphone at a reader. The reader uses NFC to retrieve the credential identifier and sends it to the controller. The controller processes the credential, makes the access decision, and sends it to the reader and server.

**Note:** The REST API import utility is developed by the Technology Partner using [Gallagher Cardholder REST APIs](https://gallaghersecurity.github.io/cc-rest-docs/ref/cardholders.html). The Technology Partner is responsible for mitigating risks associated with malformed or malicious API requests, including the injection of harmful data and the potential compromise of API endpoints.


---

# 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/mobile-wallet-credentials.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.
