Examples Of Key Mapping; Common File Structure - Magtek DynaFlex II Go Programmer's Manual

4 - Data Types and Shared TLV Data Objects
SRED
Data Type
Data
(Working Key Purpose)
ID
5 MagTek Token (RFU)
6 User Data #1 (RFU)
7 PIN-AES (supported on PED devices Only)
... RFU
Note: If SRED Data ID 2 and 4 are mapped to the same Key Set, then they must have the same Transformation ID.
If the Transformation ID of the latest key mapping request is different, then the original OID setting of the other
SRED Data ID will be forced to match the latest OID setting. For example, SRED Data ID 2 has been mapped to
0x2007 0x04, user wants to map SRED Data ID 4 to 0x2007 0x05, then the OID setting of SRED Data ID 2 will be
forced to 0x2007 0x05.

4.17.6 Examples of Key Mapping

The following OID Values indicate that:
a) 200701: Map PIN-TDES to DKPTM7-2007 PIN Encryption Variant.
b) 20020B: Map Account Data to DKPTM2-2002 Data Encryption Usage.
c) 200702: Map MAC to DKPTM7-2007 MAC Generate/Verify Variant.
d) 20030B: Map MangePrint to DKPTM3-2003 Data Encryption Usage.
e) 000004: MagTek Token is RFU, 0000 ID does not exist (this is default value).
f) 000004: User Data is RFU, 0000 ID does not exist (this is default value).
g) 200207: Map PIN-AES to DKPTM2-2002 PIN Encryption Usage.
Figure 4-1 - Configuration Usage Values

4.18 Common File Structure

Some files types conform to the common file structure format that follows.
The following is a list of file types that conform to this format.
1) EMV file types
2) Certificate File Types
DynaFlex II Go| Secure Card Reader | Programmer's Manual (COMMANDS)
Page 88 of 301 (D998200597-102)
Allowed Legacy Allowed AES
DUKPT DUKPT
Transforms Transforms
RFU RFU
RFU RFU
Not allowed 07
- -