CardExchange® Producer supports inline encoding and reading of MIFARE® DESFire cards. What information should be read or written can be configured by means of the DESFire Wizard, which will be the subject of this chapter. For a full understanding of the DESFire Wizard, it is essential to have knowledge about the functionality of the MIFARE® DESFire chip. Please, refer to the MIFARE® DESFire documentation published by NXP for more information
Please visit http://www.nxp.com for more information.
It is possible that the DESFire Wizard does not offer all functionality you need to achieve your goals. For example, you might need functionality of the DESFire protocol that is not configurable via the wizard, or special transformations of the database data before they can be written to the chip. For this type of situations, we can offer a solution by means of an External Plug In. Please, contact sales for more information about External Plug Ins.
Please, note that currently the following limitations exist with respect to MIFARE® DESFire encoding:
•The supported encoders are listed on our website: https://cardexchange.support/resource/supported-devices.
•The supported file types are Standard data files and Value files.
•Value files are only supported when using one of the supported OmniKey encoders.
•MIFARE® DESFire EV1 is only supported for certain encoders.
•Key diversification is only supported for AES keys.
•If a MIFARE® SAM is used for authentication, this should be a MIFARE® SAM AV2 and it should be inserted in a supported OmniKey encoder.
Note: EV1 refers to the hardware version of the MIFARE® DESFire chips.
Note: SAM stands for Secure Application Module. It is a chip on which the DESFire keys can be stored in such a way, that nobody involved in the encoding process has access to the actual key values, not even when the CardExchange® Producer software or computer would be hacked. AV2 refers to the hardware version of the MIFARE® SAM.
