Card Data

3.1 Card Data

The card data elements used in Application Selection are listed and briefly described in Table 3-1. For a detailed description of these data elements and their usage, see Appendix A, VIS Data Element Tables.

Table 3-1: Application Selection—Card Data (1 of 3)

Data Element Description

Application Identifier (AID) The AID is composed of the Registered Application Provider Identifier (RID) and the Proprietary Application Identifier Extension (PIX). It identifies the application as described in ISO/IEC 7816-5.

All Visa AIDs shall begin with a RID expressed as hexadecimal 'A000000003'.

The Visa RID is concatenated with a PIX representing the Visa payment type.

The global Visa PIXs are:

'1010' Visa Debit or Credit '2010' Visa Electron '3010' Interlink '8010' PLUS

The card AID shall have a suffix if more than one application with the same AID is present on a single card. The card AID should not have a suffix if only one application with the AID is on the card unless another application with the same AID may be added to the card after personalization.

A card with both a Visa credit and a Visa debit application might use the suffix as follows:

'A000000003101001'—first Visa application (Visa Credit) 'A000000003101002'—second Visa application (for Visa Debit) The AID is used in two different ways:

 AID (tag '4F') is used if Directory Selection is supported.

 Dedicated File (DF) Name (tag '84'), part of the response to SELECT when an Application Definition File is selected, contains the AID.

Visa Integrated Circuit Card Specification (VIS) 3 Application Selection

Version 1.5 3.1 Card Data

Application Definition File (ADF)

A file that is the entry point to application elementary files (AEF) that contain data elements for the application.

 File Control Information (FCI) Template – DF Name

– FCI Proprietary Template

 Application Label

 Application Priority Indicator

 PDOL

 Language Preference (Cards should specify Language Preference in lowercase)

 Issuer Code Table Index

 Application Preferred Name

 FCI Issuer Discretionary Data

Application Elementary Files (AEFs)

Application elementary files contain data elements used by the application in processing.

Application Label, '50' Mnemonic associated with the AID according to ISO/IEC 7816-5. Used in application selection. Application Label is mandatory in the File Control

Information (FCI) of an Application Definition File (ADF) and in an ADF directory entry.

The naming conventions for Application Label are that it shall contain “Visa” if included in the acceptance mark and shall clearly identify the payment function or product as needed to differentiate among the applications stored on the card:

Visa Debit/Credit Shall contain “Visa”. For example, “Visa”, “Visa Credit”,

“Visa Debit”, or “Visa Business”

Electron Shall include “Visa” and should include “Electron”. For example, “Visa” or “Visa Electron”

Interlink Shall include “Interlink”. For example, “Interlink” or “Visa Interlink”

PLUS Shall include “PLUS”. For example, “PLUS” or “PLUS ATM”

Application Preferred Name, '9F12'

Mnemonic associated with the AID. If the Application Preferred Name is present and the Issuer Code Table Index entry is supported by the terminal, then the Application Preferred Name rather than the Application Label is displayed to the Table 3-1: Application Selection—Card Data (2 of 3)

Data Element Description

3 Application Selection Visa Integrated Circuit Card Specification (VIS)

3.1 Card Data Version 1.5

Application Priority Indicator, '87'

Indicates the priority of the given application in a directory and whether the application requires cardholder confirmation to be selected.

If the card contains more than one payment account, then the account reflected in the magnetic stripe shall be priority 1.

Directory Definition File (DDF)'

A file that defines the directory structure beneath it. The FCI for a DDF is as follows:

 FCI Template – DF Name

– FCI Proprietary Template

 SFI of directory

 FCI Issuer Discretionary Data (optional)

Directory File A directory file is a file listing DDFs and ADFs contained within the directory. After selection, the directory is accessed with the READ RECORD command.

For more detailed information on directory files, refer to EMV Book 1, Annex C.

File Control Information (FCI) Template, 'A5'

Contains information provided in response to the SELECT command. This information varies depending on the type of file selected.

Issuer Code Table Index, '9F11'

Indicates the code table according to ISO/IEC 8859 required in the terminal to display the Application Preferred Name.

Payment Systems Environment (PSE)

The PSE begins with a DDF named ”1PAY.SYS.DDF01”. The directory file associated with this DDF is known as the Payment Systems Directory.

Payment Systems Directory The Payment Systems Directory contains entries for ADFs that are formatted according to EMV. The applications defined by the ADFs may or may not conform to EMV.

Processing Options Data Object List (PDOL), '9F38'

A list of tags and lengths for terminal resident data objects needed by the card in processing the GET PROCESSING OPTIONS command during Initiate

Application Processing. (See Chapter 4, Initiate Application Processing, for more information.)

Short File Identifier (SFI) The SFI is a pointer to Elementary Files (EF). Use of SFIs is allocated as follows:

1–10 Reserved for EMV 11–20 Payment system specific 21–30 Issuer specific

Table 3-1: Application Selection—Card Data (3 of 3) Data Element Description

Visa Integrated Circuit Card Specification (VIS) 3 Application Selection

Version 1.5 3.1 Card Data

Note: Issuers should expect that EMV-compliant terminals will ignore any historical bytes present in the Answer to Reset (ATR), even if they are ISO-compliant and contain only ISO-defined information. Issuers are free to encode the historical bytes in any way they choose, but are cautioned that unintentional conflict of coding between cards may exist, leading to possible misinterpretation at terminals.

Neither payment system card personalization checks nor EMVCo type approval testing include tests on the coding or interpretation of historical bytes.

3 Application Selection Visa Integrated Circuit Card Specification (VIS)