Card
Capabilities
Form
Version 4.28
Card Capabilities Form
MasterCard Worldwide
Chip Centre of Excellence
Revision History
New Version
1.0
…
Date
Chapter modified
Nov 6, 2001
Document creation
6.1
6.5
4.21 (not issued)
Sept 15, 2010
4.9.5
4.2.3
1
All
4.22
Sept 21, 2010
1, 2
4.23
4.24
October 13, 2010
October 22, 2010
4.25
May 3, 2012
4.9.1
Chapter 1
All
Chapter 2
4.8, 4.9
4.26
Nov 19, 2012
Modification
1.
4.10
A8/A8B
4.27
July 9, 2013
4.9.1
4.9.5
4.28
July 16, 2013
4.2.3
Question added on application code
location in ICC
Field D5 renamed: ‘RSA Cryptoprocessor’ for clarification
Field D5b added: ‘Application Code
Location’
New form sections related to M/Chip
Advance products added
Questions updated related to ISO/IEC
14443 version and added for Mifare
Guidelines added regarding filename
format to be used when registering a
product
Entire document review (old section 2 and
3 deleted)
Typo corrected
Field A8b added
Field D54 corrected
Reference to CSI for innovative products
Fields corrected
Field A29 added: Product Compliance
with Cryptography Research Inc. (CRI)
Personalization of Offline PIN, optional
features (Log and Compute Cryptogram
Checksum) in M/Chip Advance
Combo card capable for PayPass M/Chip
4 and M/Chip Advance
Questions related to Mobile MasterCard
M/Chip products added
Address to provide CCF
Non M/Chip product : update of the
question index
Introduce Advance v 1.1 products in the
list
Linked update on MC4
Linked update on Advance
DI3 Product type created
Additional EMV contactless specifications
listed
The information in this form supersedes and replaces all previous versions.
Information in this form is subject to change. Any changes will result in an update to the current version of the
document
CCF Version 4.28
©2013 MasterCard
Page 2 of 27
MasterCard Worldwide
Chip Centre of Excellence
Card Capabilities Form
Table of contents
1.
2.
3.
4.
Purpose of this document ....................................................................... 4
Administrative Information ..................................................................... 5
Technology Identifier .............................................................................. 7
Application Description........................................................................... 9
4.1 Chip Description .............................................................................................................................. 9
4.2 Card Initialization ............................................................................................................................. 9
4.2.1 Contact interface ................................................................................................................. 9
4.2.2 Low voltage capabilities ................................................................................................... 10
4.2.3 Contactless interface ......................................................................................................... 11
4.3 Additional applications .................................................................................................................. 12
4.4 Application selection ...................................................................................................................... 14
4.5 Data Sharing .................................................................................................................................... 15
4.6 Session Key Derivation ................................................................................................................. 15
4.7 RSA capabilities .............................................................................................................................. 15
4.8 Offline PIN management ............................................................................................................. 16
4.9 Specific questions for M/Chip products .................................................................................... 17
4.9.1 M/Chip 4 products ........................................................................................................... 17
4.9.2 M/Chip Lite 2.1, M/Chip 2.2 and Select V2.0.x ......................................................... 17
4.9.3 PayPass – M/Chip 4 products (v1.3.1 or v1.4) ............................................................ 18
4.9.4 PayPass – M/Chip Flex products................................................................................... 18
4.9.5 M/Chip Advance .............................................................................................................. 19
4.9.5.1 MCADDS (Payment and Data Storage) ....................................................................... 19
4.9.5.2 MCADP (payment only) .................................................................................................. 20
4.9.5.3 MCADP-C (contact-only)................................................................................................ 21
4.9.5.4 MCADP-NO-RSA ............................................................................................................ 22
4.9.5.5 MCADP-C-NO-RSA Only ............................................................................................. 23
4.9.6 Mobile MasterCard M/Chip products........................................................................... 24
4.10 Specific questions for non M/Chip products ........................................................................... 25
CCF Version 4.28
©2013 MasterCard
Page 3 of 27
MasterCard Worldwide
Chip Centre of Excellence
Card Capabilities Form
1. Purpose of this document
As part of the Interface and Application Testing Process, this form aims at gathering in
a very synthetic document the main features of the submitted product. It will be used to
define the profiles used during the testing session.
Please fill in each grey zone of the document. When required, help is provided using
the "F1" key. Help is also available in the “Status Bar” at the bottom of the window.
This Card Capabilities Form (CCF) shall be provided to MasterCard at:
Chip_certification_CHD@mastercard.com .
The name of the product (even partial) and the version of the CCF have to appear
into the filename. This version must be incremented into the filename each time
the CCF is updated. Otherwise the update will be rejected
In order to speed up as possible the administrative processing of the requests for
Interface and Application Testing, MasterCard has put in place an automated process
to retrieve the pieces of information filled in by the product Vendors.
As a consequence the CCF shall be provided in a ‘Word’ format (.doc) only. PDF
versions are not permitted anymore.
Please also note that previously it was not required to provide MasterCard with this
form when submitting a PayPass – Mag Stripe product for Interface and Application
Testing. At present all the relevant sections must be filled-in (that is, from section 2 to
4.3 included)
Note:
If the card body(s) of the submitted products is not made of laminated PVC or does not
meet the applicable ISO/IEC specifications, the card manufacturer should seek CSI
review at CSI_Security@mastercard.com
CCF Version 4.28
©2013 MasterCard
Page 4 of 27
Card Capabilities Form
MasterCard Worldwide
Chip Centre of Excellence
2. Administrative Information
A1. Company Legal Name
A2. Company Details
A3. Technical Contact during the test campaign
A5. Product Technical Name and Version
A6. Product Commercial Name and Version
A6b. Product Name and Version used for CAST
registration
A8b. This product is registered as
A8. Name and Version of Application
Specification used for development
if NMC (specifications reference) :
A9. Type
A10. Supplier
A11. Name and Version
Operating
System
X value:
A13. If MULTOS
A24 API
version
Java
AMD version:
Card
Comment:
If Java
A25. GP Version
Application
Y value:
Comment:
A14. Name and Version
A14b. Supplier
A26. Is this a renewal request?
Renewal
Inheritance
A27. if Yes: fill in the Registration
Number or CFA Summary
A21. Inheritance
product
with
other
A22. if Yes: fill in the Registration
Number(s)
A23. CAP supported with specific AID
A18. CCF filled in on the
A20. Additional Vendor’s Comments (including
reason to update CCF if accurate)
A28. CCF Update History (Exhaustive list of
changes applied versus previous CCF
submitted)
A29. The Integrated Circuit used by this product and identified in the below field T5 (page 7)
has been licensed by Cryptography Research Inc. (CRI) under CRI's patent portfolio related
to differential power analysis (DPA) and related external monitoring attacks.
CCF Version 4.28
©2013 MasterCard
Page 5 of 27
MasterCard Worldwide
Chip Centre of Excellence

Note
-
CCF Version 4.28
©2013 MasterCard
Card Capabilities Form
The Product Technical Name and Version must identify a unique
product.
The consistency of MULTOS parameters will be checked out during
the CPV process.
Inheritance Field (A21): for instance a PICC based on an approved PIC.
Any information request or question related to CRI licensing shall be
addressed to your IC supplier.
Page 6 of 27
MasterCard Worldwide
Chip Centre of Excellence
Card Capabilities Form
3. Technology Identifier
Components Identification – T1. Product Type:
CQM Identification
Production Site
(City / Country)
Component
(Name / Version)
T2. Form Factor:
Supplier
Chip
T3.
T4.
T5.
Module
T7.
T8.
T9.
Antenna
T11.
T12.
T13.
Inlay
T14.
T15.
T16.
Lamination
T18.
T19.
Card Body
T21.
Embedding
T23.
Product it applies
CT
CL
DI1
DI2
DI3
PIC1
T6. 1
x
x
x
x
x
x
T10. 2
x
x
x
x
x
x
x
x
x
x
o
x
o
Label
n/a
Antenna /
Inlay
ID-1 Card
T26. Antenna size for ID-1 products:
1
with
T17. 6
x
x
n/a
T20. 7
x
x
T22.
n/a
T22’. 3
x
x
x
T24.
n/a
T25. 4
x
x
x
lines embossing. If ‘Other’ please specify here:
Approving an antenna is allowed for PIC as well
CCF Version 4.28
©2013 MasterCard
Page 7 of 27
MasterCard Worldwide
Chip Centre of Excellence
Note

Card Capabilities Form
– Column ‘Product it applies’ shows which lines have to be filled in
according to the product selected into the ‘Product Type’ field
– Product Types:
o
o
o
o
‘CT’: Usual EMV Product
‘CL’: Usual PayPass – Mag Stripe product
‘DI1’: Dual Interface product where chip is embedded after
card body manufacturing (currently usual ID-1 product)
‘DI2’: Dual Interface product where chip is added to inlay
before lamination
– The default value into the ‘Label’ column refers to the CQM workshop
involved and then is the first digit of the label to fill in.
– Do not add any additional information besides the requested data
CCF Version 4.28
©2013 MasterCard
Page 8 of 27
MasterCard Worldwide
Chip Centre of Excellence
Card Capabilities Form
4. Application Description
Note

Please fill in sections 4.1, 4.2 and 4.3 for all products (including PayPass –
Mag Stripe).
4.1
Chip Description
D1.
D2.
D3.
D3’
D4.
ROM Size (KB)
RAM Size (KB)
EEPROM Size*
FLASH Size
CPU type (8, 16 or 32 bit etc.)
D5. RSA Crypto-processor
D5b Payment Application code location
Note

4.2
Comments:
*Only a rough estimation is expected here. This estimation shall take into
account the domestic and the international application(s) if the card
supports both of them.
Card Initialization
4.2.1 Contact interface
–
–
D6. Is the Warm Reset supported?
D7. Is there any application implicitly selected at Cold Reset?
Note

–
–
If ‘Yes’, additional configuration(s) showing different timing may be
requested in the CEP for Level 1 testing.
D8. Contact Protocols supported?
D9. ATR values registered for the approval:
T=0
 Cold
 Warm
T=1
 Cold
 Warm
Please use the following field if you register several ATR:
CCF Version 4.28
©2013 MasterCard
Page 9 of 27
MasterCard Worldwide
Chip Centre of Excellence
Note

Provide the longest historical byte string the card can support.
When T=0 and T=1 are both supported:
–
–
–
–
–
Card Capabilities Form
One configuration per supported communication protocol will be fully
tested during Level 1 testing.
A full functional testing session will be conducted in T=0
Only regression functional tests will be conducted in T=1
Each configuration will be tested during integration
D10. Communication speed supported once the card has been issued:
Note

For ATR indicating a negotiable mode of operation supported, only the
default values will be tested (that is, D = 1 and F = 372) as defined in EMV
book 1 and not the maximum speed announced.
4.2.2 Low voltage capabilities
D11. According to the EMV2000 - Book 1 - Amendment 1 the card is compliant with
Note

CCF Version 4.28
©2013 MasterCard
Please refer to EMVCo General Bulletin No.11 for Lower Voltage Card
Migration Mandatory Implementation Schedule on EMVCo website.
Page 10 of 27
MasterCard Worldwide
Chip Centre of Excellence
Card Capabilities Form
4.2.3 Contactless interface
–
D12b. What is the Contactless Communication Protocol Specification version supported?
–
–
–
–
–
D13. Protocol used by the card:
D14. Frame Waiting Time Integer (FWI) of the card:
D15. Does the card support the use of the CID?
D16. Does the card support the use of the NAD?
D17. If the card uses the Type A protocol:

ATQA value:

UID Size (simple, double or triple):

SAK value
o

ATS value:
o
o
–
(Last SAK for double and triple UID Size):
FSCI value:
SFGI value:
o Historical Bytes value (if any):
D18. If the card uses the Type B protocol:

ATQB value:
o
o
o
Application Data Field value:
Max Frame Size value:
ADC value (2 bits):

ATTRIB Response value:

HLTB Response value:

Does the card implement the Higher Layer
command/response feature?

–
–
–
If the card implements the Higher Layer command/response feature,
what command supported by the card and what response is sent by the card?
D19. Does the card use chaining to transmit data?
D20. If the card uses chaining to transmit data, is the size of the blocks indicating chaining
always the same (fixed block size)?
D21. Does the card use FWT Extension Requests?
Comments:
–
–
M1. Does the chip support Mifare?
If yes, please fill in the protocol parameters when Mifare is activated on the card:

M2. ATQA value:

M3. UID Size (simple, double or triple):

M4. SAK value
o M5. (Last SAK for double and triple UID Size):

M6. ATS value:
o M7. FSCI value:
o M8. SFGI value:
CCF Version 4.28
©2013 MasterCard
Page 11 of 27
MasterCard Worldwide
Chip Centre of Excellence
–
4.3
Card Capabilities Form
o M9. Historical Bytes value (if any):
M10. Does the chip support DESFire?
Additional applications
D24. Can several EMV payment applications (the application that is submitted to the type approval)
be personalized on the card (multi-instantiation of M/Chip applet for instance)?
Note

If CAP is supported (question A23 in chapter 2) a dedicated card profile will
be requested for testing (i.e. M4x)
D26. Are other applications available on this card?
If "Yes" please fill the following table taking into account the following instruction:
-
Application Name
The technical name of the application shall be provided here. It could be either a
MasterCard application (MODS, CAP, …) or a non-MasterCard application.
-
AID
The Application Identifier shall be provided here. If the AIDs are not yet defined, the
value to be entered is a plausible value that will be used during the approval session.
-
Short Description
A brief description of the application shall be provided here.
-
Does this application share the PIN and/or other Data with M/Chip?
-
Does this application act as a filter?
An application is considered as a filter if it intercepts all incoming or outgoing commands
(APDU or R-APDU) even if it just forwards the command or (and) the response without
modifying it (them).
-
Is this application a default application?
A default application is an application implicitly selected during the card initialization
(power on). Such an application may interfere during the EMV selection mechanism.
CCF Version 4.28
©2013 MasterCard
Page 12 of 27
MasterCard Worldwide
Chip Centre of Excellence
Application Name
AID
Card Capabilities Form
Short Description
Does this application
share the PIN and/or
other Data with
M/Chip?
D27.
D28.
D29.
D30.
D31.
D32.
D33.
D34.
D35.
D36.
CCF Version 4.28
©2013 MasterCard
Page 13 of 27
Does this
application
act as a
filter?
Is this application
a default
application?
MasterCard Worldwide
Chip Centre of Excellence
Card Capabilities Form
Comments:
Note

If you have responded “Yes” to one ‘act as a filter’ box:

Additional information will be requested on the filter mechanism to
determine the impact(s) on the CEP.

If the presence of a filter application is optional an additional
configuration may be requested for testing in the CEP for performing
some complementary level 1 and level 2 tests.
Please list below all configurations (combination of applications) you would like to market. For each of
them complementary tests may be run. The test report will repeat this list.
D36b.
Note

Please be aware that the laboratory costs may be impacted by the number
of configurations.
Usage of a non tested configuration may require a regression session if
not initially planned.
4.4
Application selection
D37. Is the PSE supported?
D38. If yes, is the PSE an independent application (Codelet, Applet…)?
Note

When PSE is supported a specific card profile will be requested for testing
except if PSE presence is mandatory in the card implementation.
When PSE is an independent application some further Level 1 testing will
be conducted by the lab.
D39. Are "Partial Selection" and "Select Next" supported?
Note

CCF Version 4.28
©2013 MasterCard
If supported a dedicated card profile will be requested for testing (i.e. M1)
Page 14 of 27
MasterCard Worldwide
Chip Centre of Excellence
4.5
Card Capabilities Form
Data Sharing
Does the card/application provide a mechanism:
D40.
D41.
D42.
For PIN sharing?
For sharing of any other EMV data
If yes, which data?
Note

4.6
If you answered “Yes” to one of these questions:
–
Additional information will be requested on the data sharing
mechanism. It is also highly recommended to discuss this as soon as
possible with the team in charge of the security evaluation of the
product (i.e. CAST).
–
Multi-applicative card profiles have been defined by MasterCard for
testing the data sharing mechanism (M2 for PIN sharing and M3 for
data sharing). These additional profiles will be indicated in the CEP.
Session Key Derivation
D43. Session Key Derivation method supported:
D43bis. If ‘Other’ please specify:
Comments:
4.7
RSA capabilities
D44. DDA supported?
D45. CDA supported?
D46. Odd RSA Key length supported?
D47. Maximum Certificate length supported for SDA
D48. Maximum Key length supported for DDA
D49. Maximum Key length supported for CDA
Note

CCF Version 4.28
©2013 MasterCard
Bytes
Bytes
Bytes
A dedicated card profile will be requested when odd RSA key length is
supported (i.e. profile 1’ )
Page 15 of 27
MasterCard Worldwide
Chip Centre of Excellence
4.8
Card Capabilities Form
Offline PIN management
D50. Is Plain text Offline PIN supported?
D50.1: Can the PIN value not be present if not requested?
Note

A dedicated card profile will be requested when personalization of the
reference PIN is optional (i.e. profile 10)
D51. Is Enciphered Offline PIN supported?
D52. If yes, is the card able to manage a dedicated RSA key for PIN encryption?
D53. If yes, maximum RSA Key length supported for PIN encryption?
CCF Version 4.28
©2013 MasterCard
Bytes
Page 16 of 27
MasterCard Worldwide
Chip Centre of Excellence
4.9
Card Capabilities Form
Specific questions for M/Chip products
4.9.1 M/Chip 4 products
D54. Please provide us with the (or one) AFL that will be used for the test cards:
D55. 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.
SFI (if possible SFI 1):
Record (if possible Record 1):
Actual size reserved (between 180 and 240 (decimal)):
Note

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.
D56. Maximum number of entries (records) in the Log file:
D57. Maximum CDOL 1 Related Data Length:
values)
10 (Default value)
53 for Select, 45 for Lite (Default
D57a. Is Linked Update supported?
D57a1. Maximum size of template A5 supported in Linked Update?
D57a2. Is it possible to have Linked Update on 3 applications?
Note

Linked Update is an additional feature specified in MChip 4 linked
applications updates_3.pdf document.
Please insert below any useful comments, for instance the list of points that have been previously
discussed with MasterCard:
Comments:
4.9.2 M/Chip Lite 2.1, M/Chip 2.2 and Select V2.0.x
No additional information is required.
CCF Version 4.28
©2013 MasterCard
Page 17 of 27
MasterCard Worldwide
Chip Centre of Excellence
Card Capabilities Form
4.9.3 PayPass – M/Chip 4 products (v1.3.1 or v1.4)
D57b. Can the product be personalized as an M/Chip 4 one?
D57c. Can the product be personalized as a PayPass – Mag Stripe one?
Note

Dedicated card profiles are requested when a dual product can be
personalized as contact only or Mag Stripe only.
Contact interface
Please fill in section 4.9.1 related to M/Chip 4 products
Contactless interface
D57.d. Is it possible to personalize a Combo card (extended AID in contact and non extended AID in
contactless with all internal data shared)
4.9.4 PayPass – M/Chip Flex products
Active co-application information
D58. Co-Application Type:
D59. Co-Application Name:
D60. Co-Application Version:
Note

Only one co-application may be identified per product.
In case of CCD-Compliant application, you have to provide us with a copy
of the Letter of Approval issued by EMVCo (including the Card Compliance
Certificate Number and ICS).
In case of UKIS Compliant Payment Application, please fill in the Section
4.10 ‘Specific Question for non-M/Chip products’.
Comments:
Reset Offline Counters
D61. Please describe in detail how the co-application decides to reset the PayPass – M/Chip Flex
offline consecutive and cumulative counters:
Update Limits of Offline Counters
D62. Please describe in detail the proprietary script commands to be used for updating the PayPass –
M/Chip Flex offline counters limits DF0A, DF0B, DF0C and DF0D (e.g. PUT DATA, UPDATE
RECORD):
CCF Version 4.28
©2013 MasterCard
Page 18 of 27
MasterCard Worldwide
Chip Centre of Excellence
4.9.5
Card Capabilities Form
M/Chip Advance
Please fill-in only the section corresponding to the M/Chip Advance product you submit for approval.
Five products may be submitted to approval based on M/Chip Advance Product Derivation Version
1.0 (Draft D) — November 2009 (this specification is referenced within this form as [MCAD])
M/ChipTM Advance with Payment and Datastorage functionalities
M/ChipTM Advance with Payment functionalities only
Contact-only card
Dual interface card without RSA capability
Contact-only card without RSA capability
4.9.5.1
MCADDS
MCADP
MCADP-C
MCADP-NO-RSA
MCADP-C-NO-RSA
MCADDS (Payment and Data Storage)
D110. Maximum number of log files supported?
D111. Maximum CDOL1 extension supported?
D112. Are the mechanisms used to recover torn transactions for
contact and contactless the same?
D113. When are the data restored (if needed) when in contact
mode?
D114. When are the data restored (if needed) when in contactless
mode?
D115. What is the maximum size supported for the
Protected/Unprotected Data Envelopes?
D116. What is the maximum number of Slot supported in the Data
Storage File?
D117. Is the update of Data Storage record (via Update Record
command) supported with a data length coded on 1 byte (ODS tag
and record Template)?
D118. When Log feature is not personalized, is it possible to have
the following data object not present?
 SFI11
 Log Format
 Log Data Table
D119. Is it possible to personalize a Combo card (extended AID in
contact and non extended AID in contactless with all internal data
shared)
D119a. Is Linked Update supported?
D119b. Is it possible to have linked Update on 3 applications?
Note

CCF Version 4.28
©2013 MasterCard
Linked Update is an additional feature specified in MChip Advance linked
applications updates_3.pdf document.
Page 19 of 27
MasterCard Worldwide
Chip Centre of Excellence
4.9.5.2
Card Capabilities Form
MCADP (payment only)
D70. Maximum number of log files supported?
D71. Maximum CDOL1 extension supported?
D72. Are the mechanisms to recover torn transactions used for
contact and contactless the same?
D73. When are the data restored (if needed) when in contact
mode?
D74. When are the data restored (if needed) when in contactless
mode?
D75. When Log feature is not personalized, is it possible to have
the following data object not present?
 SFI11
 Log Format
 Log Data Table
D76. Is it possible to personalize a Combo card (extended AID in
contact and non extended AID in contactless with all internal data
shared)
D77. Is Linked Update supported?
D78. Is it possible to have linked Update on 3 applications?
CCF Version 4.28
©2013 MasterCard
Page 20 of 27
MasterCard Worldwide
Chip Centre of Excellence
4.9.5.3
Card Capabilities Form
MCADP-C (contact-only)
D120. Is Log Option implemented?
D121. If Not, are the "Log Data Table" and "Log Format"
personalized on the sample cards sent for TA
D122. Maximum number of log files supported?
D123. Maximum CDOL1 extension supported?
D124. Is Compute Cryptographic Checksum supported?
D125. If Not, are the "IVCVC3(Track1) (Contact), IVCVC3(Track2)
(Contact), KDCVC3 (Contact)" personalized on the sample cards
sent for TA?
D126. When are the data restored (if needed)?
D127. How are personalized other data listed in 2.3.3 and 2.3.4 of
[MCAD] on the sample cards sent for TA?
D128. Is the "Interface Enabling Switch" still implemented?
D129. Is the code identified in 2.4, 2.5, 2.6, 2.7 and 2.8 of [MCAD]
modified or removed?
D130. When Log feature is not personalized, is it possible to have
the following data object not present?
 SFI11
 Log Format
 Log Data Table
D132. Is Linked Update supported?
D133. Is it possible to have linked Update on 3 applications?
CCF Version 4.28
©2013 MasterCard
Page 21 of 27
MasterCard Worldwide
Chip Centre of Excellence
4.9.5.4
Card Capabilities Form
MCADP-NO-RSA
D100. Is Log Option implemented?
D101. If Not, are the "Log Data Table" and "Log Format"
personalized on the sample cards sent for TA?
D102. Maximum number of log files supported?
D103. Maximum CDOL1 extension supported?
D104. Is the code identified in 4.5 and 4.6 of [MCAD] related to the
CDA modified or removed?
D105. Is the code identified in 4.5 and 4.6 of [MCAD] related to the
Transaction Log modified or removed?
D106. Is the OFFLINE CHANGE PIN branch • Encrypted PIN
(OCP.2) removed as per 4.9 of [MCAD]?
D107. Is the CDA branch in the RECOVER AC command removed
as per 4.12 of [MCAD]?
D108. Is the Encrypted PIN (VY.2) branch in the Verify command
removed as per 4.13 of [MCAD]?
D109. When Log feature is not personalized, is it possible to have
the following data object not present?
 SFI11
 Log Format
 Log Data Table
D131. Is it possible to personalize a Combo card (extended AID in
contact and non extended AID in contactless with all internal data
shared)
D134. Is Linked Update supported?
D135. Is it possible to have linked Update on 3 applications?
CCF Version 4.28
©2013 MasterCard
Page 22 of 27
MasterCard Worldwide
Chip Centre of Excellence
4.9.5.5
Card Capabilities Form
MCADP-C-NO-RSA Only
D80. Is Log Option implemented?
D81. If Not, are the "Log Data Table" and "Log Format"
personalized on the sample cards sent for TA
D82. Maximum number of log files supported?
D83. Maximum CDOL1 extension supported?
D84. Is Compute Cryptographic Checksum supported?
D85. If Not, are the "IVCVC3(Track1) (Contact),
IVCVC3(Track2) (Contact), KDCVC3 (Contact)"
personalized on the sample cards sent for TA?
D86. How are personalized other data listed in 4.3.3 and 4.3.4 of
[MCAD] on the sample cards sent for TA?
D87. Is the "Interface Enabling Switch" still implemented?
D88. Is the code identified in 4.5 and 4.6 of [MCAD] related to the
contactless interface modified or removed?
D89. Is the code identified in 4.5 and 4.6 of [MCAD] related to the
CDA modified or removed?
D90. Is the code identified in 4.5 and 4.6 of [MCAD] related to the
Transaction Log modified or removed?
D91. Is the OFFLINE CHANGE PIN branch • Encrypted PIN
(OCP.2) removed as per 4.9 of [MCAD]?
D92. Is the CDA branch in the RECOVER AC command removed
as per 4.12 of [MCAD]?
D93. Is the Encrypted PIN (VY.2) branch in the Verify command
removed as per 4.13 of [MCAD]?
D94. When Log feature is not personalized, is it possible to have
the following data object not present?
 SFI11
 Log Format
 Log Data Table
D95. Is Linked Update supported?
D96. Is it possible to have linked Update on 3 applications?
CCF Version 4.28
©2013 MasterCard
Page 23 of 27
MasterCard Worldwide
Chip Centre of Excellence
Card Capabilities Form
4.9.6 Mobile MasterCard M/Chip products
D140. Maximum number of entries (records) in the Log file:
D141. Maximum CDOL 1 Related Data Length:
D142. Maximum size f CLD data
D143. PowerOff/Power On supported between 1st tap and 2nd tap
of a transaction
D144. When Log feature is not personalized, is it possible to have
the following data object not present?
 SFI11
 Log Format
D145. Channel supported by the application
CCF Version 4.28
©2013 MasterCard
10 (Default value)
53 (minimum value)
255 (minimim value)
Page 24 of 27
MasterCard Worldwide
Chip Centre of Excellence
Card Capabilities Form
4.10 Specific questions for non M/Chip products
Command Format
What is the format used in the command response data field for the following commands (either
Format 1 or 2 as defined in EMV):
–
D63. Get Processing Options command
–
D64. Generate AC command
–
D65. Internal Authenticate command (if supported)
Transaction Initialization
D66. May the card return different (AIP: AFL) as response to the Get Processing Options
command depending on PDOL?
Cardholder verification
–
–
–
D67. Is the plaintext PIN supported?
D68. Is the enciphered PIN supported?
D69. Is the ICC PIN PK supported?
Issuer Authentication
–
D150. Is the Issuer Authentication mandatory?
Script Processing
–
–
–
–
–
D151. Are Critical Script processing commands supported?
D152. Are Non-Critical Script processing commands supported?
D153. Is External Auth mandatory to process script processing commands?
If yes, for which script commands?
If yes, are the "Issuer Script Command Counter" and the "Issuer Script Failure Indicator"
updated even when the External Authentication has not been received?
CCF Version 4.28
©2013 MasterCard
Page 25 of 27
MasterCard Worldwide
Chip Centre of Excellence
–
Card Capabilities Form
D74. Script processing (list of the data that could be updated). Please complete the table with
proprietary data elements.
Data Element
Tag
Application Control
Lower Consecutive
Offline Limit
Upper Consecutive
Offline Limit
Non-Domestic Control
Factor Exponent (value
‘n’)
Lower Maximum Offline
Cumulative Amount
Upper Maximum Offline
Cumulative Amount
Card TVR Action Code
Card Issuer Action Code
(offline)
Card Issuer Action Code
(online)
Card Issuer Action Code
(denial)
Consecutive
Transaction Limit
(International - Country)
Consecutive
Transaction Limit
(International)
Cumulative Total
Transaction Amount
Limit
Cumulative Total
Transaction Amount
Limit (Dual Currency)
Currency Conversion
Factor
Lower Consecutive
Offline Limit
Upper Consecutive
Offline Limit
‘D5’
CCF Version 4.28
©2013 MasterCard
Update
Record
(Y/N)
Put Data
(Y/N)
Update
Supported by
the application
(Y/N)
Update could be
forbidden by
personalization
(Y/N)
‘9F14’
‘9F23’
‘CE’
‘CA’
‘CB’
‘C6’
‘C4’
‘C5’
‘C3’
‘9F53’
‘9F72’
‘9F54’
‘9F75’
‘9F73’
‘9F58’
‘9F59’
Page 26 of 27
MasterCard Worldwide
Chip Centre of Excellence
Card Capabilities Form
Comments:
_____________ END OF FORM ____________
CCF Version 4.28
©2013 MasterCard
Page 27 of 27