CTA Bulletin nº 40: Card Contactless Level 1 (PICC) Type Approval Update v3.2b

2025-02-04T00:00:00+00:00 v2.0 Type Approval Bulletins

Contactless Card

EMV® Card Type Approval Bulletin No. 40 Second Edition, January 2025 Card Contactless Level 1 (PICC) Type Approval Update v3.2b This bulletin announces the availability of PICC Test Plan v3.2b documents

Applicability

This Bulletin applies to Contactless PICC Level 1 Testing. Related Documents  EMV Level 1 Specifications for Payment Systems - EMV Contactless Interface Specification Version 3.2 – July 2022  EMV Specification Bulletin No. 282 PPS0 and PPS1 RFU Value Handling, First Edition, March 2023  EMV Specification Bulletin No. 283 PCD Carrier Phase Drift, First Edition, March 2023  EMV Specification Bulletin No. 300 PICC Presence Check Procedure, First Edition, June 2024  EMV Specification Bulletin No. 303 PCD Adding an Optional Suspend and a Mandatory Suspend in the Polling Loop, Second Edition, May 2024 Effective Date  See section titled “Activation and migration planning”

Description

EMVCo is pleased to announce the availability of Contactless Card Level 1 (PICC) Type Approval Test Plan v3.2b documents. Updated documents The following documents have been published on the EMVCo website:  EMV Contactless Card Level 1 Type Approval – PICC Analogue Test Bench and Test Case Requirements, v3.2b, January 2025.  EMV Contactless Card Level 1 Type Approval – PICC Digital Test Cases, v3.2b, January 2025.  EMV PICC Level 1 Implementation Conformance Statement (ICS), v3.2b Changes since previous versions Regarding the Analogue Test Cases, the most important changes since version 3.2a are:  Update of the acceptance criteria defined for the Test Case CA144 with the addition of a ±1/fc margin in favour of the PICC Under Test.  Update of FDTA,PICC Acceptance Criteria in Table A 4.  Update the definition of the tFSOFF measurement in the Test Case CB145 and Appendix D. Note: No technical changes have been made since version 3.2b draft 3, October 2024.

Regarding the Digital Test Cases, the most important changes since version 3.2a are:  Based on SB 300 – PICC Presence Check Procedure.

New subcase CC001.3 to check the PICC supports a Polling Loop with an optional suspend.  Based on SB 303 – Adding an Optional Suspend and a Mandatory Suspend in the Polling Loop
New TC CC102 to check that the PICC supports the presence check procedure.  Update CC203 pre- and post-processing to ensure consistent PICC behaviour. Note: No technical changes have been made since version 3.2b draft 1, October 2024. Regarding the ICS, the most important changes since version 3.2a are:  Updating version number Activation and migration planning The activation of testing in version 3.2b of the PICC Test Plan is defined in the latest edition of Card and Mobile Type Approval Bulletin No. 31.

Legal Notice

This document summarizes EMVCo’s present plans for evaluation services and related policies and is subject to change by EMVCo at any time. This document does not create any binding obligations upon EMVCo or any third party regarding the subject matter of this document, which obligations will exist, if at all, only to the extent set forth in separate written agreements executed by EMVCo or such third parties. In the absence of such a written agreement, no product provider, test laboratory or any other third party should rely on this document, and EMVCo shall not be liable for any such reliance. No product provider, test laboratory or other third party may refer to a product, service or facility as EMVCo approved, in form or in substance, nor otherwise state or imply that EMVCo (or any agent of EMVCo) has in whole or part approved a product provider, test laboratory or other third party or its products, services, or facilities, except to the extent and subject to the terms, conditions and restrictions expressly set forth in a written agreement with EMVCo, or in an approval letter, compliance certificate or similar document issued by EMVCo. All other references to EMVCo approval are strictly prohibited by EMVCo. Under no circumstances should EMVCo approvals, when granted, be construed to imply any endorsement or warranty regarding the security, functionality, quality, or performance of any particular product or service, and no party shall state or imply anything to the contrary. EMVCo specifically disclaims any and all representations and warranties with respect to products that have received evaluations or approvals, and to the evaluation process generally, including, without limitation, any implied warranties of merchantability, fitness for purpose or non-infringement. All warranties, rights and remedies relating to products and services that have undergone evaluation by EMVCo are provided solely by the parties selling or otherwise providing such products or services, and not by EMVCo, and EMVCo will have no liability whatsoever in connection with such products and services. This document is provided "AS IS" without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in this document. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AS TO THIS DOCUMENT. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to this document. EMVCo undertakes no responsibility to determine whether any implementation of this document may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of this document should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, this document may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement this document is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for any party's infringement of any intellectual property rights in connection with this document.