PCI Watch

Tracking changes across the Payment Card Industry

SB nº SU-19 : Support for Transaction Log Files (Spec Change)

v1.0 Specification Bulletins

Specification Update Bulletin N°19 Second Edition May 2004 This Bulletin has immediate effect Support for Transaction Log Files

Applicability

This Specification Update Bulletin applies to: EMV 2000 Integrated Circuit Card Specifications for Payment Systems Version 4.0 Books 1 and 3.

Related Documents

None In order to provide support for accessing of transaction log files by special devices such as PCs, PDAs, and ATMs, the following option is being added to the current EMV specifications. The option specifies how special devices determine the transaction log location and the format of the records in this log. It does not define how the special device uses the log data. The device could print or display selected log data or include it in a database. Card support for the transaction log is optional. This bulletin does not specify which transactions are logged, the data that is logged, or when the logging occurs during the transaction. Option in Support of Transaction Log Files Please add the following data elements in EMV 2000 Integrated Circuit Card Specifications for Payment Systems Version 4.0 Book 3 Annex A Data Elements Table after the entry for Last Online Application Transaction Counter (ATC) Register: This document contains proprietary and confidential information of EMVCo LLC. Copyright © EMVCo LLC 2003

Name Log Entry Log Format

Description

Provides the SFI of the Transaction Log file and its number of records. List (in tag and length format) of data objects representing the logged data elements that are passed to the terminal when a transaction log record is read. Source ICC ICC Format Template Tag b 'BF0C' '9F4D' b '9F4F' Length 2 var. In the same table please assign the tag '9F4E' to the entry for Merchant Name and Location. The updated entry is as follows: Name Merchant Name and Location Description Indicates the name and location of the merchant Source Terminal Format ans Template Tag Length '9F4E' var. In Table A-2 of the same volume please add the following data elements after the entry for ICC Dynamic Number: Name Log Entry Merchant Name and Location Log Format Template 'BF0C' Tag '9F4D' '9F4E' '9F4F' This document contains proprietary and confidential information of EMVCo LLC. Copyright © EMVCo LLC 2003

Please add the following section to EMV 2000 Integrated Circuit Card Specifications for Payment Systems Version 4.0 Book 3 after Annex C.6: Annex C.7 – Transaction Log Information Purpose: Provide support for accessing a transaction log file by special devices. Conditions of Execution: This optional function is intended to be executed by special devices. Sequence of Execution: This function may be executed after Application Selection. Description: To get the Transaction Log information, the two following data elements are used: Log Entry and Log Format. The following table describes the format of the Log Entry data element (tag '9F4D'): Byte 1 2 Format b b Length 1 1 Value SFI containing the cyclic transaction log file Maximum number of records in the transaction log file Table C-8 – Log Entry Devices that read the transaction log use the Log Entry data element to determine the location (SFI) and the maximum number of transaction log records. The SFI shall be in the range 11 to 30. The Transaction Log records shall be accessible using the READ RECORD command as specified in Book 3, section 2.5.11. The file is a cyclic file as defined in ISO/IEC 7816-4:1995. Record #1 is the most recent transaction. Record #2 is the next prior transaction, etc. The Transaction Log records shall not be designated in the Application File Locator. Each record is a concatenation of the values identified in the Log Format data element. The records in the file shall not contain the Application Elementary File (AEF) Data Template (tag '70'). The Log Format and the Transaction Log records shall remain accessible when the application is blocked. To read the transaction log information, the special device uses the following steps: This document contains proprietary and confidential information of EMVCo LLC. Copyright © EMVCo LLC 2003

  • Perform Application Selection and retrieve the Log Entry data element located in the FCI Issuer Discretionary Data. If the Log Entry data element is not present, the application does not support the Transaction Log function.
  • Issue a GET DATA command to retrieve the Log Format data element.
  • Issue READ RECORD commands to read the Transaction Log records. Example: Note that the following data elements are shown for example purpose only. A Log Entry data element equal to '0F14' indicates that the transaction log file is located in SFI 15 ('0F') and contains a maximum of 20 records ('14'). A Log Format data element equal to '9A039F21035F2A029F02069F4E149F3602' indicates that the transaction log records have the following content: Data Content Transaction Date Transaction Time Transaction Currency Code Amount, Authorized Merchant Name and Location Application Transaction Counter Tag '9A' '9F21' '5F2A' '9F02' '9F4E' '9F36' Length 3 3 2 6 20 2 Table C-9 Example of Log Format In table C-9, lengths and tags are shown for clarity. They do not appear in the log record which is the concatenation of values (no TLV coding). Data elements listed in the Log Format may come from the terminal and the card. Terminal data elements such as Merchant Name and Location might have been passed to the card in the PDOL or CDOL data. This document contains proprietary and confidential information of EMVCo LLC. Copyright © EMVCo LLC 2003 Other Updates: In the second paragraph of EMV 2000 Integrated Circuit Card Specifications for Payment Systems Version 4.0 Book 3, section 2.5.7 GET DATA Command-Response APDUs, subsection 2.5.7.1 Definition and Scope, please add Log Format (tag '9F4F') to the list of data elements that are retrievable using GET DATA. In the same book Section 2.5.7.2, change the Value column entry in the P1 P2 row to " '9F36', '9F13', '9F17', or '9F4F' " In section 3.2, Data Retrievable by GET DATA Command, Table II-5 of the same book, please add the following entry after the entry for Last Online ATC Register: Tag '9F4F' Value Log Format Presence O At the end of the sentence immediately preceding Table II-5 add "unless the card supports retrieval of the PIN Try Counter or the Log Format using GET DATA." In EMV 2000 Integrated Circuit Card Specifications for Payment Systems Version 4.0 Book 1 Section 7.3.4 Data Field Returned in the Response Message, please replace table 40 with the following table: Tag Value Presence '6F' FCI Template M '84' DF Name M 'A5' FCI Proprietary Template M '50' Application Label O '87' Application Priority Indicator O '9F38' PDOL O '5F2D' Language Preference O '9F11' Issuer Code Table Index O '9F12' Application Preferred Name O 'BF0C' FCI Issuer Discretionary Data O '9F4D' Log Entry O 'XXXX' 1 or more additional O (Tag (Private) Data elements according to from application provider, Book 3) issuer, or IC Card Supplier Table 40- SELECT Response Message Data Field (FCI) of an ADF This document contains proprietary and confidential information of EMVCo LLC. Copyright © EMVCo LLC 2003