Tomcat
Professional
- Messages
- 2,689
- Reaction score
- 963
- Points
- 113
As noted earlier, an ADF file is an access point for AEF files that contain data for the application associated with the ADF file. After the terminal has selected the ADF file, all the AEF files of that application can be selected by the SFI name of those files. The SFI value of any application AEF file ranges from 1 to 30.
According to Book 3 of the EMV specifications, AEF files identified by SFI with values in the range 1 to 10 store data as defined in the EMV standard. Files identified by SFI with values in the range 11 to 20 and 21 to 30 are reserved for storing data for the payment system and issuer, respectively.
Each AEF file, defined by an SFI with a value in the range 1 to 10, is a linear file with variable or fixed length entries. All records in the file are numbered and identified by their number. The maximum number of entries in an AEF file, as explained in 3.4, is 255.
Each AEF file record is a composite data object called an AEF Data Template (Tag '70') followed by a parity byte controlled by the card's operating system. The structure of the AEF file record is shown in Fig. 3.5.
The AEF Data Template is only defined in the EMV standard (there is no description for it in ISO 7816). The Length of this object is two bytes. Since the operating system of the card for coding
MasterCard
^? 9
Record size control always uses one byte, that is, the length of the AEF file record does not exceed 255 bytes, the size of the entire AEF Data Template object, including the Tag and Length fields, and minus the parity check byte, does not exceed 254 bytes. It follows that the length of the Value field of the AEF Data Template is no more than 251 bytes.
Finally, note that the AEF Data Template contains data objects readable by the terminal using the READ RECORD command. These data objects are listed in table. A1 of Appendix A of Book 3 of the EMV Specification 4.2. There are EPLU data objects that are not stored in AEF files and become available to the terminal as a result of the application selection procedure (from the response to the SELECT command) or using the GET DATA command. These include the objects used to select the application (Table B1 in Appendix B in Book 1) and the internal parameters of the application (Application Transaction Counter, PIN Try Counter, etc.).
According to Book 3 of the EMV specifications, AEF files identified by SFI with values in the range 1 to 10 store data as defined in the EMV standard. Files identified by SFI with values in the range 11 to 20 and 21 to 30 are reserved for storing data for the payment system and issuer, respectively.
Each AEF file, defined by an SFI with a value in the range 1 to 10, is a linear file with variable or fixed length entries. All records in the file are numbered and identified by their number. The maximum number of entries in an AEF file, as explained in 3.4, is 255.
Each AEF file record is a composite data object called an AEF Data Template (Tag '70') followed by a parity byte controlled by the card's operating system. The structure of the AEF file record is shown in Fig. 3.5.
The AEF Data Template is only defined in the EMV standard (there is no description for it in ISO 7816). The Length of this object is two bytes. Since the operating system of the card for coding
| Tr = '70'h | ||
| Lr = 2 bytes | ||
| Vr | Data Object 1 | T1 |
| L1 | ||
| V1 | ||
| Data object N | TP | |
| Ln | ||
| Vn | ||
| Control byte |
MasterCard
^? 9
Record size control always uses one byte, that is, the length of the AEF file record does not exceed 255 bytes, the size of the entire AEF Data Template object, including the Tag and Length fields, and minus the parity check byte, does not exceed 254 bytes. It follows that the length of the Value field of the AEF Data Template is no more than 251 bytes.
Finally, note that the AEF Data Template contains data objects readable by the terminal using the READ RECORD command. These data objects are listed in table. A1 of Appendix A of Book 3 of the EMV Specification 4.2. There are EPLU data objects that are not stored in AEF files and become available to the terminal as a result of the application selection procedure (from the response to the SELECT command) or using the GET DATA command. These include the objects used to select the application (Table B1 in Appendix B in Book 1) and the internal parameters of the application (Application Transaction Counter, PIN Try Counter, etc.).
