MF2DL1000DA4SLASH02 datasheet(40/132 Pages) NXP

40 / 132 page

NXP Semiconductors

MF2DL(H)x0

MIFARE DESFire Light contactless application IC

MF2DL_H_x0

All information provided in this document is subject to legal disclaimers.

Product data sheet

Rev. 3.3 — 5 April 2019

COMPANY PUBLIC

430733

40 / 132

(Secure Access Module) which allows a secure commit of an ID that is then linked with

the merchant. The goal of this is that the merchant cannot forge the committed ID. This

ID is called ReaderID. For this feature, a key is assigned which is known by both the card

and the SAM: AppCommitReaderIDKey. At the merchant’s site, this key should not leave

the SAM.

The card supports linking ReaderIDs of merchants by storing the committed ReaderID

and returning the ReaderID of the previous transaction. This way the backend can detect

which merchant did not report missing transactions.

10.3.1 General Overview

The Transaction MAC can be activated by creating a TransactionMAC file. When

creating this file, one also specifies the AppTransactionMACKey, see Section 11.7.6.

Additionally, one can optionally also require the commitment of a ReaderID, by assigning

a AppCommitReaderIDKey for this, see Section 8.2.3.6. Once the Transaction MAC

feature is activated, the Transaction MAC computation consists of the following steps:

1. Initialization: before performing the first command that needs a Transaction MAC

computation update, the Transaction MAC Session Keys (SesTMMACKey and

SesTMENCKey) are derived from the AppTransactionMACKey using the next

Transaction MAC Counter value, see also Section 10.3.2.1.

2. Computation updates: during the transaction, the Transaction MAC is computed using

SesTMMACKey over the following commands:

• ReadData, GetValue and ReadRecords

• WriteData, Credit, Debit, LimitedCredit, WriteRecord, UpdateRecord and

ClearRecordFile

• CommitReaderID: the committed ReaderID is stored on the card and the ReaderID

of the previous transaction is returned encrypted with the SesTMENCKey. This is

also included in the ongoing Transaction MAC computation.

Note that for simplicity operations all file types are included. Note that StandardData

can be written without transaction finalization with CommitTransaction. Therefore, the

protection of StandardData files by the TransactionMAC is limited.

MF2DL(H)x0 does support an option that excludes unauthenticated data management

operations from the Transaction MAC calculation. This can be enabled with

ChangeFileSettings.

3. Finalization: on CommitTransaction, the Transaction MAC is finalized. The update

of the manipulated backup files and the computed Transaction MAC, the related

counter and (optionally) the committed ReaderID, are one atomic operation. The

computed Transaction MAC and the related counter are either provided with the

response of CommitTransaction or can be read afterwards using ReadData on the

TransactionMAC file.

MF2DL1000DA4/02 Datasheet(PDF) 40 Page - NXP Semiconductors

MF2DL1000DA4/02 Datasheet(HTML) 40 Page - NXP Semiconductors

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

Datasheet Download

Link URL