> 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/encoding-a-card.md).

# Encoding a card

To encode a card for a Cardholder:

1. There are potentially seven options that the **Print/Encode Card** button can display as, (i.e. **Print**, **Quick Print**, **Encode**, **Quick Encode**, **Print and Encode**, **Quick Print and Encode** and **Print Preview** ) depending on what was last selected.

   **Note:** The **Quick Encode** option is not available if the card has previously been encoded, unless the Card Type has **Allow re-encoding** enabled. You will not be able to re-encode a card using a Card Type that does not allow re-encoding, unless you have the "Allows Re-Printing and Re-Encoding" privilege, in which case using **Encode** will prompt you to 'Proceed' or 'Cancel'. If you have the "Edit Cardholder" privilege you are prompted to increase the Issue Level. If you have both the "Edit Cardholder" and "Allows Re-Printing and Re-Encoding" privileges you can either increase the Issue Level or 'Proceed'.

   If it does not display as the option you require, (in this case **Encode** ), then click on the ![](https://2455150842-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi6UYAoyykM6nimMN9yss%2Fuploads%2Fgit-blob-9e87a3e5f9187fac583c377b7bf12511adc135a1%2Farrowbutton.png?alt=media) beside it and select the option you require.

   The Encoding Card pop-up displays.

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

   **Notes:**

   * A red **\*** will display next to the **Reason** field if it is compulsory.
   * The **PIN selection** section only appear if the Card Type has been configured for PIN.

   **Notes:**

   * The "Quick" options for printing and/or encoding cards are to help speed up the process, however for them to work effectively the following configuration needs to be in place first:
     * the "Reason for printing" is not configured as compulsory in Configuration Client
     * that a card has already been printed so that a default printer is known, and
     * the cardholder only has one card.
   * If you use the **Quick Encode** option, the Encoding Card pop-up does not display, and the card is encoded by the default printer.
2. Select the required device to be used for card printing/encoding from the **Device** drop-down list of available printers/encoders.

   The system will remember this printer and default to it every time you preview/print a card until you change it again using the same procedure.
3. Click the **Setup** button to alter the printer settings if necessary, then click the **OK** button.

   **Note:**

   If you are encoding a Mifare card, using a serial Mifare encoder, you need to select the port that the encoder is connected to. To do this:

   1. Click the **Setup...** button to display the Printer properties.
   2. Click the **Encoding** tab.
   3. Select the port the encoder is connected to from the drop-down list.
4. Select the appropriate reason for printing/encoding from the **Reason** drop-down list, or type your own reason into the text field. The reason selected will be logged in the event details.

   **Note:**

   The **OK** button will be disabled until a reason is entered if the **Operator must provide a reason for printing or encoding a card** checkbox was checked on the Photo ID Configuration window when "Reasons for Printing" were configured.
5. Does the **PIN selection** section display?

   <table><thead><tr><th width="78">If...</th><th>then...</th></tr></thead><tbody><tr><td>no</td><td>go to Step 6.</td></tr><tr><td>yes</td><td><p>either:</p><ul><li>manually type a PIN number into the <strong>User PIN</strong> field, and then retype the PIN into the <strong>Confirm</strong> field that appears when the minimum PIN length is reached. The confirmation PIN must match the user defined PIN before the card can be encoded.<br><strong>Note:</strong> There is no mechanism to reduce the maximum size of a PIN. Hence if a site sets minimum at 4, the user can enter PIN length anywhere from 4 to 8 digits, OR</li><li>click the <strong>Generate PIN</strong> button to automatically generate a random PIN.<br><strong>Note:</strong> Generated PINs will only display while the pop-up remains open. There will be no way of reviewing the PIN number since the PIN itself is not stored. Generated PINs will be of length equal to the minimum PIN length set against the Card type.</li></ul><p><strong>Note:</strong> The system prevents PINs with 3 consecutive or 3 repeating numbers from being either manually entered or automatically generated.<br>If you leave it unchecked, the PIN number will display as a row of X's.<br>If you check it, for audit purposes, an event is logged to say you viewed PINs.</p></td></tr></tbody></table>
6. Click the **OK** button.

   The card is encoded by the selected printer.


---

# 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/encoding-a-card.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.
