Application Configuration and Capabilities
|
|
C.1
|
Is Multi-Instantiation supported
|
|
C.2
|
Are “Partial Select” and “Select Next” supported?
|
|
|
Application Data Sharing Capabilities
|
|
C.3
|
Is PIN sharing supported?
|
|
C.4
|
Is other EMV data sharing supported?
|
|
C.4.1
|
If yes, which data?
|
|
|
Application Session Key Capabilities
|
|
C.5
|
Session Key Derivation method supported
|
|
C.5.1
|
If ‘Other’ please specify
|
|
Application RSA Capabilities
|
C.6
|
Odd RSA Key length supported?
|
|
C.7
|
Maximum Certificate length supported for Static Data Authentication (SDA)
|
Bytes
|
C.8
|
Maximum Key length supported for Combined DDA/Generate AC (CDA)
|
Bytes
|
A dedicated card profile will be requested when odd RSA key length is supported (i.e. profile 1’ )
|
|
Application Offline PIN Management
|
|
C.9
|
Is Plain text Offline PIN supported?
|
|
A dedicated card profile will be requested when personalization of the reference PIN is optional (i.e. profile 10)
|
C.10
|
Is Enciphered Offline PIN supported?
|
(If yes please complete C.10.1 – C.10.2)
|
C.10.1
|
Is the application able to manage a dedicated RSA key for PIN encryption?
|
|
C.10.2
|
Maximum RSA Key length supported for PIN encryption?
|
Bytes
|
|
M/Chip 4 based Application Capabilities
|
|
C.11
|
Please provide us with the (or one) Application File Locator (AFL) that will be used for the test cards
|
|
Please select into this AFL a file and a record for which the maximum length (memory size reserved) is longer than the length used by your personalization.
|
C.12
|
Short File Identifier (SFI) - if possible SFI 1
|
|
C.13
|
Record (if possible Record 1)
|
|
Mobile Mastercard PayPass M/Chip 4 Application Capabilities
|
|
C.14
|
Maximum Card Layout Description (CLD) length
|
|
C.15
|
Shall the power be maintained On the Secure Element/UICC between 1st tap and 2nd tap of a transaction?
|
|
C.16
|
When log feature is not supported is it possible to have the following data object not present?
|
C.16.1
|
SFI11
|
|
C.16.2
|
Log Format
|
|
M/Chip 4 based Application & Mobile Mastercard PayPass M/Chip 4 Application Capabilities
|
C.17
|
Maximum record length supported (between 180 and 247 (decimal))
|
|
According to EMV an issuer may chose a record length up to 180. An M/Chip 4 application is then requested to support such length.
|
C.18
|
Maximum number of entries (records) in the Log file
|
10 (Default value)
|
C.19
|
Maximum CDOL 1 Related Data Length
(CDOL =Card risk management Data Object List)
|
53 (minimum value)
|
C.20
|
Please add any useful comments, for instance the list of points that have been previously discussed with MasterCard
|
|
Personalization Capabilities
|
C.21
|
Does the application implement proprietary Data Group Identifiers (DGIs)?
|
|
C.21.1
|
Is the personalization of these proprietary DGIs mandatory for the application to be functional?
|
|
C.22
|
Does the application require a specific order for the DGIs?
|
|
C.22.1
|
If a specific DGI order is require please supply the ordering.
|
|
