PCI Watch

Tracking changes across the Payment Card Industry

SB nº SB-78 : Removal of DDF Entries from PSE Records (Spec Change)

v1.0 Specification Bulletins

Specification Bulletin No. 78 First Edition February 2010 Removal of DDF Entries from PSE Records This Specification Update Bulletin removes support for DDF entries within PSE records and describes the changes for removal of this support from the EMV Integrated Circuit Card Specifications for Payment Systems.

Effective Date

This bulletin is effective from November 2010, at which time any affected or new type approval testing will also come into effect.

Applicability

This Specification Update Bulletin applies to:

  • EMV Integrated Circuit Card Specifications for Payment Systems Version 4.2 Book 1 Application Independent ICC to Terminal Interface Requirements
  • EMV Integrated Circuit Card Specifications for Payment Systems Version 4.2 Book 2 Security and Key Management
  • EMV Integrated Circuit Card Specifications for Payment Systems Version 4.2 Book 3 Application Specification
  • EMV Integrated Circuit Card Specifications for Payment Systems Version 4.2 Book 4 Cardholder, Attendant, and Acquirer Interface Requirements

Related Documents

None.

Description

This EMV Specification Bulletin removes the EMV option that allows DDF directory entries in records referenced by the PSE. EMVCo is removing this option because it has come to our attention that many terminals do not correctly process these PSE DDF entries during Application Selection. When one of these terminals encounters a card that has DDF entries in the PSE, the terminal might not locate all common applications referenced by the PSE and these DDF entries. EMVCo is therefore removing the option for DDF directory entries in PSE records from the EMV specification to prevent potential interoperability problems. Specification Changes Books 1, 2, 3, and 4:

  • In section 3, replace the definition of Payment System Environment with: “A logical construct within the ICC, the entry point to which is a Directory Definition File (DDF) named '1PAY.SYS.DDF01'. This DDF contains a Payment System Directory which in turn contains entries for one or more Application Definition Files (ADFs) which are formatted according to this specification.” Book 1: Make the following changes to Contents, table of Tables:
  • Change “Table 48” to “Table 47”, “Table 49” to “Table 48”, “Table 50” to “Table 49”, “Table 51” to “Table 50”.
  • Add a new final entry to the Table: “Table 51: Example of a DDF Directory Entry Format” Make the following changes to section 10.1.4 Directory Structure:
  • In the first paragraph change the last sentence to "In that case, the applications are listed in a Payment System Directory file (DIR file), the location of which is indicated in the FCI of the PSE DDF."
  • Replace the second paragraph with: “The directory structure allows for retrieval of an application using its ADF Name”
  • In the third paragraph change "The presence of the DIR file" to "The location of the DIR file"
  • Replace the first bullet with: "One or more records that each contains one or more Application Templates (tag '61') containing an ADF directory entry (see figure 41)". Make the following changes to section 12.2.2 Structure of the PSE:
  • In the third paragraph delete the final sentence that begins "The directory may also contain entries…"
  • Replace the fourth paragraph with the following: "The directory is not required to have entries for all ADFs in the card. However, if the PSE exists, only applications that are revealed by reading the directory can be assured of international interoperability." Make the following changes to section 12.2.3 Coding of a Payment System Directory:
  • Insert the following paragraph after the first paragraph: "Payment Systems Directory records shall not contain any entries for DDFs. If the terminal encounters a directory entry for a DDF in one of these records, it may ignore it or may optionally process the DDF, but any such processing is outside the scope of EMV.”
  • In Table 46, Payment System Directory Record Format, delete "or DDF" from Directory entry 1 and Directory entry n.
  • In the paragraph below Table 46, delete "or Table 48".
  • Move existing Table 47 to new annex section C4 – see below.
  • Change the table number of the current Table 48: ADF Directory Entry Format to Table 47, and change the table number of the current Table 49: Format of Application Priority Indicator to Table 48.
  • In the renumbered Table 47: ADF Directory Entry Format, in the fourth row for Application Priority Indicator, change "(see Table 49)" to "(see Table 48)." Delete section 12.2.4 and renumber section 12.2.5 to 12.2.4. Make the following changes to section 12.3.2 Using the PSE:
  • In the last paragraph of step 1, change "steps 2 through 5" to "steps 2 through 4."
  • In step 2, change "step 6" at the end of the first paragraph to "step 5", and change "steps 3 through 5" in the second paragraph to "steps 3 and 4."
  • In step 3, replace "If the entry is for an ADF and the ADF name matches" with "If the entry's ADF name matches."
  • Remove step 4 describing the processing of DDF entries in the PSE, change step 5 to step 4 and change step 6 to step 5.
  • In step 6 (now renumbered as step 5), change "If steps 1 through 5" to "If steps 1 through 4." Replace the flow in Figure 17, Terminal Logic Using Directories, with the following flow: Begin Application Selection If the terminal and card support implicit selection as defined by ISO 7816-4, it is performed prior to this step. Terminate Session Terminal Supports PSE? Yes Select DFNAME = No '1PAY.SYS.DDF01' Yes S=W'61A8S1W' ?2 No PSE No Found? Yes PSE Yes Blocked? No Empty candidate list Selection from terminal list See “Using a List of AIDs” in next section Get SFI for directory from FCI Set record number for read to 1 Read directory record Record found? Yes Get first entry from Yes record A Is there No an entry in this record? Terminal No supports application? Yes No ADF is exact match of AID? Yes Terminal Application Selection Indicator No allows partial match? Yes Add ADF to candidate list No Are there any No entries on the candidate list? Yes Candidate list is complete. Choose application from candidate list. Is there another entry in this record? Yes Get next entry Increment record No number for next read by 1 A Make the following changes to Annex B Data Elements Table:
  • Renumber existing Table 50 to Table 49
  • Renumber existing Table 51 to Table 50 Add a new section C4 as follows: “C4 Coding of Proprietary Directories EMV does not mandate the formats for proprietary directories that may be present on the card in addition to the Payment System Directory. Directories following the structure defined in section 12.2 can be accessed using the methods described in this section. These directories can have the same format as shown in Table 46 for the Payment System Directory Record Format, and can in addition to the one or more ADF Directory Entries also contain one or more DDF Directory Entries. If present, these DDF Directory entries can have the format as shown in Table 51 below.”
  • Move the current Table 47 from section 12.2.3 to the end of new section C4 and rename to “Table 51: Example of a DDF Directory Entry Format”.