EMV® Contactless Mobile Payment PPSE Applet Implementation Conformance Statement

Export Form Data Import Form Data EMVCo Contactless Mobile Payment PPSE Applet Implementation Conformance Statement Version 1.0g ICS Reference Number and Validity Period (for EMVCo administrative use only) ICS Reference Number: Valid from: Valid to: Notice: This ICS form shall be completed for CMP PPSE Applet submitted for CMP PPSE Applet Functional evaluations. The form shall be completed in its entirety. All Yes and No questions shall be answered. If a feature/option is NOT supported, i.e. a question is answered "No," the sub-questions for that feature/question shall be left blank. A

• Administrative Product Provider Identification A.1.1 – Company Legal Name: (As listed on the Letter of Registration) A.1.2 – EMVCo Registration Number: Laboratory Identification A.1.3
• Company Legal Name: A.1.4 – EMVCo Registration Number: ICS Submission Type A.2.1
• Select submission type A.2.2
• For any submission except Initial, please provide the EMVCo letter of approval reference number of the previously approved product (if already granted) A.2.3 – Is this ICS a replacement of Yes No a previously accepted ICS? A.2.4 – If Yes. please provide the reference number of the previously accepted ICS A.2.5
• If Yes, please provide the reason for replacing the ICS A.2.6 – If Yes, please provide details of ICS replacement 6 Product Specification

References

Name A.3.1 – EMV Specification PPSE and Application Management for Secure Element A.3.2 – EMV Bulletins (list all applicable) Version Number Release Date Released by Audit Report Tracking Number

6 Product and Chip Descriptions A.4.1 – Product Name: Product Version: (This is the name that will appear on the Approved Products List) A.4.4 – PPSE Applet Provider: A.4.5 – PPSE Applet Identifier: A.4.11 – Secure Element form factor: In case of eSE please describe the eSE package provided: A.4.12 – Test chip reference: A.4.20 – AID of the SD in which the SE applets shall be loaded Logical Channel for Interface Device Note: If the SE supports several interfaces to the Device, and the number of supported logical channels is different for each interface, then please document the supported range for the interface that supports the maximum number of channels. In question A.4.25, please document first the interface that supports the maximum number of channels so that all channels are tested. The other interface(s) will only go through reduced set of testing on channel 0. A.4.21 – Logical Channel for Interface Device Supported If yes please fill question A.4.22 Yes No A.4.22 – Logical Channel(s) limited to range 1 - 3 Yes No Logical Channel for Interface Antenna Note: If the SE supports several interfaces to the Antenna, and the number of supported logical channels is different for each interface, then please document the supported range for the interface that supports the maximum number of channels. In question A.4.26, please document first the interface that supports the maximum number of channels so that all channels are tested. The other interface(s) will only go through reduced set of testing on channel 0. A.4.23 – Logical Channel for Interface Antenna Supported If yes please fill question A.4.24 Yes No A.4.24 – Logical Channel(s) limited to range 1 - 3 Yes No Physical and Logical Communication channel used by the SE during testing Note: Please document the interfaces from the test environment to the SE. Do not document the ones from the test tool to the test environment Note: Only the described interfaces will be tested and covered by the Letter of Compliance A.4.25 – For the communication from the baseband to the SE (APDUs) If other or multiple interface please describe: A.4.26 – For the contactless APDUs exchanges between the CLF and the SE If other or multiple interface please describe:

6 GP Test Platform A.5.1 – Please provide GP Qualification Number (if already available) and attach a copy of GP Letter of Qualification of the Test Platform used during evaluation A.5.2 – Please provide GP SCO Reference Number (mandatory if GP Qualification Number is not available) A.5.3 – GlobalPlatform Letter of Qualification testing coverage We hereby declare that the testing of the SWP protocol using a SWP/HCI test suite qualified by GlobalPlatform (for SEs using SWP) is, or will be, in the scope of the GlobalPlatform Letter of Qualification A.5.4.1 – Does the GP Test Platform supports GP Card Specification v 2.2 Amendment C version 1.1 or higher? Yes No A.5.4.2 – GP Card Specification v 2.2 Amendment C version: A.5.5 – What version of the GP Contactless API (org.globalplatform.contactless) is supported? A.5.6 – What version of the UICC Contactless Extension is supported? A.5.7 – Does the GP Platform allow an application to activate itself on the contactless interface (as defined in GP2.2 amendment C (self activation)? Yes No Note: When Internal Mode is supported, at least one response ‘Yes’ is required at question L2.3.1 (when the Test Payment Application can be activated via the CRS) or at question A.5.7 (when the Test Payment Application has the self-activation privilege) Note: Application group, notification of priority events transmission (from GP Card Specification version 2.2 Amendment C version 1.1) and notification of Discretionary Data change are mandatory features of the GP Platform

6 L2

• Application Optional Functionality included in the PPSE application L2.2.1 – Is the External Mode supported by the PPSE application? Yes No L2.2.2 – Is the Internal Mode supported by the PPSE application? Yes No L2.2.3 – Is the SET MODE supported by the PPSE application? Yes No L2.2.4 – Is the Switched Off Detection supported by the PPSE application? Yes No L2.2.5 – Is the Internal Mode with Mutual Exclusivity Rule supported by the PPSE application? Yes No Note: The Base AID functionality is a mandatory feature of the PPSE application Functionality included in the CRS Application of the test platform used for the certification ** L2.3.1 – Does the CRS application support SET STATUS for Application Activation as defined in GP Card Specification v 2.2 Amendment C? Yes No L2.3.2 – If L2.2.2 and A.5.4.1 are "Yes", does the CRS application support SET STATUS for Priority setting as defined in GP Card Specification v 2.2 Amendment C? Yes No L2.3.3 – If L2.2.2 and A.5.4.1 are "Yes", does the CRS application support SET STATUS for Priority override as defined in GP Card Specification v 2.2 Amendment C? Yes No ** Even if all these parameters are not directly linked to the PPSE applet; their settings impact the PPSE behavior and so the tests to be performed on the PPSE Note: When the Internal Mode is supported, at least one response ‘Yes’ is required at question L2.3.1 (when the Test Payment Application can be activated via the CRS) or at question A.5.7 (when the Test Payment Application has the self-activation privilege). Test Payment Applications and PPSE application L2.4.1 – Channel Number to be used when APDU are sent to the Test Application using the Device Interface (Channel 0 if no specific Channel) L2.4.2 –What is the Maximum number of Application Groups supported? L2.4.3 –What is the Maximum number of Applications in a Group supported? 6 C
• Digital Signatures Product Provider I agree and understand that if the CMP PPSE product requires a code change, a patch or new executable code, EMVCo must be notified. In such a case, a new PPSE Applet must be submitted for Functional Level 2. I hereby declare that the above referenced product currently is and will remain in compliance with the above referenced EMV specifications for all mandatory and supported optional requirements. Comments Signature Laboratory I hereby declare that this ICS document has been reviewed, and that all product information is consistent throughout the ICS. Comments Signature EMVCo Approval Secretariat Signature 6