> 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/using-command-centre/working-with-viewers/tile-actions/cardholder-cards-tile-actions/re-issuing-cards-or-mobile-credentials.md).

# Re-issuing cards or mobile credentials

### Re-issue a card

If a card is replaced, you do not need to go through the process of creating a new card; you can simply increment the issue number (1 - 15).

A card may need to be replaced if the Cardholder has lost their card, for example.

To re-issue a card:

1. Click the **Issue Level** button of the card.

   The Reissue Card pop-up displays.

   ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-68cd50163af4ad495254526fb719bdb74cfd570e%2Fcardholdercards_reissuecardpopup.png?alt=media)
2. The **Issue Level** of the card needs to increment by one.

   Ensure the number that defaults into the **Issue Level** field is correct.
3. Select the appropriate reason for why you are re-issuing the card, (e.g. Lost, Damaged, etc.) from the **Change Reason (Card Status)** drop-down of available card states.
4. Click the **OK** button.

   The Reissue Card pop-up closes.
5. Click the **Save** button.

### Re-issue a mobile credential

Mobile Credentials can be re-issued similarly to re-issuing cards. This may happen for a number of reasons, for example if the Cardholder’s phone is stolen, lost, damaged, or replaced. To re-issue a mobile credential:

1. Select the Mobile Credential that needs to be re-issued and click the **Reissue** button.

   If you have Card States enabled (see [Creating a Card State Set](https://help.security.gallagher.com/knowledge-hub/command-centre-client/configuring-command-centre/administration/card-states/creating-a-card-state-set.md)), the Remove Card popup displays.

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

   Select a **Change Reason** from the drop-down menu, then click the **OK** button.

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

   The Reissue Card pop-up displays.

   The **Email** and **Mobile** fields will be pre-populated if you have the "View Mobile Credential Email and Mobile" privilege.
2. Adjust field data as required, then click the **OK** button.

   The Reissue Card pop-up closes.
3. Click the **Save** button in the lower-right corner of the Cardholder Viewer screen.

   The Mobile Credential is re-issued to the Cardholder.


---

# 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/using-command-centre/working-with-viewers/tile-actions/cardholder-cards-tile-actions/re-issuing-cards-or-mobile-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.
