> 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/products/integrations/third-party-readers/aperio/aperio-hardware/aperio-adding-mifare-desfire-to-a-aperio-lock.md).

# Aperio - Adding MIFARE DESFire to a Aperio Lock

{% hint style="info" %}
**Prerequisites:** Install the latest **PAP** from `Utilities\Aperio` of the Command Centre install files. Newer locks are not supported by older PAP versions. First create the card layout with a [non-diversified MIFARE DESFire object](/knowledge-hub/products/integrations/third-party-readers/aperio/aperio-hardware/aperio-non-diversified-mifare-desfire-object-advanced.md) in Configuration Client, which also generates the AES key.
{% endhint %}

How to encode a non-diversified MIFARE DESFire object onto an Aperio lock using the PAP.

## Steps

1. In PAP, right-click the lock and choose **Lock/Sensor > Configure**.

![Aperio Programming Application — right-click a lock and choose Configure](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-2493547273a364fb73cd3e5fd9f6805c6001ca20%2FSECHUB-APERIO-01-pap-configure-lock.png?alt=media)

2. In the RFID Configuration screen, select **MIFARE DESFire** from the dropdown, then **Add**.

![RFID Configuration dropdown with MIFARE DESFire selected](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-135b956f0d33e98442ba82627e0bdb3c36188675%2FSECHUB-APERIO-02-rfid-config-select-desfire.png?alt=media)

3. Change **RFID Card Type** from `DESFire UID` to **`DESFire`**.

![MIFARE DESFire Configuration — RFID Card Type dropdown (DESFire UID / SE / DESFire)](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-2a28a1653be5fd119a51ef0af5681552afa2c543%2FSECHUB-APERIO-03-desfire-card-type.png?alt=media)

4. Convert the object's **Application Id** from hex to decimal (for example `ABC123` becomes `11256099`) and enter the decimal value. Then set the fields:

   | Field                      | Value                                      |
   | -------------------------- | ------------------------------------------ |
   | File Identity              | 0                                          |
   | File Start Position        | 0                                          |
   | Length to read in File     | 16                                         |
   | File Data Protection Level | Plain                                      |
   | Key Type                   | AES-128                                    |
   | Key                        | the AES Key from the object (32 hex chars) |
   | Key Number                 | 0                                          |

![MIFARE DESFire Configuration dialog (Application Id 11256099, Key Type AES-128) alongside the Non-diversified object properties](https://328339335-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6bM8WhlBE9BYizPWJaPN%2Fuploads%2Fgit-blob-31188c8a765792474df0fc628f157bf350c6159d%2FSECHUB-APERIO-04-desfire-config-with-object.png?alt=media)

5. Click **Next** to the **Device Update** screen, then badge the card at the sensor to upload the configuration. Save the configuration first so you can reuse it on other locks.

***

🔗 **Related**

* [Aperio - Non-diversified MIFARE DESFire Object Advanced](/knowledge-hub/products/integrations/third-party-readers/aperio/aperio-hardware/aperio-non-diversified-mifare-desfire-object-advanced.md). Create the object and AES key in Configuration Client first.
* [Aperio - Troubleshooting](/knowledge-hub/products/integrations/third-party-readers/aperio/aperio-hardware/aperio-troubleshooting.md). Cards not recognised, and DESFire EV2 limits.


---

# 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/products/integrations/third-party-readers/aperio/aperio-hardware/aperio-adding-mifare-desfire-to-a-aperio-lock.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.