> 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/configuration-client/integrated-systems/salto-lock-interface/command-centre-site-configuration/encoding-cards.md).

# Encoding cards

### Introduction

Each Cardholder can be issued with a single MIFARE® SmartCard that can be used to grant access through Gallagher doors, Salto doors or doors using Morpho readers. Encoding of all three types together on the same card is only possible on 4k MIFARE Classic® cards, 4k MIFARE® DESFire® EV1 to EV3 cards, or 8k MIFARE® DESFire® EV1 to EV3 cards.

**Notes:**

* MIFARE DESFire EV1 to EV3 cards are encoded using the MIFARE DESFire Object added to the Card Layout.
* If your site is using Gallagher, Salto, and Morpho Biometric Readers, the Salto information will NOT fit onto 1k MIFARE Classic cards along with the currently encoded data.

  There are 15 'usable' sectors (16 in total) on a 1k MIFARE Classic card encoded with Gallagher data.

  **Gallagher** requires 2 MIFARE sectors.

  1 MIFARE sector is used for the Card Application Director (CAD) and the other for Gallagher data.

  **Salto** requires at least 5 MIFARE sectors (4-14 are default sectors).

  **Morpho** fingerprint readers require 10 MIFARE sectors.

  Allow 25 MIFARE sectors when using both fingerprint and finger vein readers.

  This is 17 sectors in total - too many to fit onto a 1k MIFARE Classic card.
* Salto encoding from Command Centre is supported for both 4k and 8k MIFARE DESFire EV1 to EV3 cards (as stated above). Differentiation between the two can be achieved by using two Card Types in Command Centre if needed. For instance "Gallagher 4k DESFire Card Type" and "Gallagher and Salto 8k DESFire Card Type".
* If a card has been encoded with Gallagher data and either Salto, Morpho or ASCII data; when re-encoding the card, ensure the Gallagher object is present on the Card Layout, unless an object is going to overwrite the sector that the Card Application Directory (CAD) has previously been written to.
* Encoding of the MIFARE SmartCard used for accessing both Command Centre doors and Salto doors is performed via Command Centre.
* A Salto USB or Ethernet encoder must be connected to the Salto Server to enable encoding of Salto data on MIFARE cards from the Command Centre workstation.

### Procedure

1. Does your site have Cardholders that will be accessing **only** Salto Doors?

   <table><thead><tr><th width="66">If...</th><th>then...</th></tr></thead><tbody><tr><td>yes</td><td><p>create a new Card Type, (or edit an existing one).</p><p>Refer to <a href="https://help.security.gallagher.com/knowledge-hub/configuration-client/site-installation/card-types/setting-up-card-types.md">Setting up Card Types</a> for the procedure.</p></td></tr><tr><td>no</td><td>go to Step 2.</td></tr></tbody></table>
2. Either create a new card layout, or copy an existing card layout.

   Refer to [Designing Card Layouts](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/designing-card-layouts.md) for full details on configuring a card layout.
3. Add a Salto MIFARE object to the card layout.

   Refer to [Adding Salto MIFARE objects to a card layout](https://help.security.gallagher.com/knowledge-hub/configuration-client/integrated-systems/salto-lock-interface/command-centre-site-configuration/encoding-cards/adding-salto-mifare-objects-to-a-card-layout.md) for the procedure.
4. Print and/or encode the card.

   Refer to [Printing and/or Encoding a card from a cardholder](https://help.security.gallagher.com/knowledge-hub/configuration-client/licensable-features/card-layouts-designing-printing-encoding/printing-encoding-cards/printing-and-or-encoding-a-card-from-a-cardholder.md) for the procedure.
5. Repeat Step 4 for all subsequent Cardholders.


---

# 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/configuration-client/integrated-systems/salto-lock-interface/command-centre-site-configuration/encoding-cards.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.
