TTA Bulletin n°280: Contactless Terminal Level 1 Type Approval v3.2a Release
EMV® Terminal Type Approval Bulletin No. 280 Second Edition, January 2025 Contactless Terminal Level 1 Type Approval v3.2a Release This Bulletin announces the availability of PCD Test Plan v3.2a documents
Applicability
This Bulletin applies to Contactless Terminal 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 2024
- EMV Specification Bulletin No. 300 PICC Presence Check Procedure, First Edition, June 2024
- EMV Specification Bulletin No. 303 Adding an Optional Suspend and a Mandatory Suspend in the Polling Loop, Second Edition, May 2024
Effective Date
- March 1st, 2025
Description
EMVCo is pleased to announce the availability of Contactless Terminal Level 1 (PCD) Type Approval Test Plan v3.2 documents. 1. Updated documents The following documents have been published on EMVCo website:
- EMV Type Approval Contactless Terminal Level 1― PCD Analogue Test Bench and Test Case Requirements, Version 3.2a, January 2025
- EMV Type Approval Contactless Terminal Level 1― PCD Digital Test Cases Version 3.2a, January 2025
- EMV Type Approval Contactless Terminal Level 1 ― Device Test Environment Version 3.2a, January 2025
- EMVCo Type Approval Contactless Terminal Level 1 ― Implementation Conformance Statement Version 3.2a
- EMV Terminal Type Approval PCD Level 1 – Administrative Process, version 3.2a, January 2025 2. Changes since previous versions Regarding the Analogue Test Bench and Test Case Requirements, the most important changes since version 3.1a are:
- SB 300 – PICC Presence Check Procedure: Update of the Frame Trails defined in Table C.1 and Table C.3.
- SB303 – Adding an optional Suspend and a Mandatory Suspend in the Polling Loop:
- Update of TAB115 Test Case
- New Test Case TAB116
- SB283 – PCD Phase Drift: New Test Case TAB117.
- Type A overshoot and undershoot measurements:
- Update of Test Case TA128 to cover only overshoot measurements.
- New Test Case TA129 to measure undershoots.
- New definition of the detection measurement window for overshoots following rising edges in Test Cases TA128, TB126, TB127 and in Appendix E.
- Update of the tFSOFF definition and modification of the default tFSOFF value applied during Test Transactions. Note: No technical changes have been made since v3.2a draft 2, October 2024. Regarding the Digital Test Cases, the most important changes since version 3.1a are:
- Based on SB 300 – PICC Presence Check Procedure
- Remove removal procedure steps from most TC
- Indicate that TC TA002, TA420, TB003 and TB420: depend on PCD support of removal procedure (ICS)
- New TC for presence check TA004, TB007, TA419 and TB419 that depend on PCD support of presence check procedure (ICS)
- Based on SB 303 – Adding an Optional Suspend and a Mandatory Suspend in the Polling Loop
- New requirement to disable the optional suspend by default
- Update TC TC002 with suspend instead of reset
- New TC TC003 that depend on support of optional suspend
- TA307.0: Restore subcase x = 0 with modulation with a duration of a 3-byte frame
- In TA412.xy and TB412.xy: New subcases with WTXM and FWT combinations such that FWTTEMP ⩽ FWTMAX, PICC Note: No technical changes have been made since v3.2a draft 1, October 2024. Regarding the Device Test Environment, the most important changes since version 3.1a are:
- Based on SB300 – PICC Presence Check Procedure
- Require new function to select the transaction completion procedure during testing.
- Based on SB303 – Adding an Optional Suspend in the Polling Loop
- Require new function to enable/disable the optional suspend of the Operating Field during polling loop. Note: No technical changes have been made since v3.2a draft 1, October 2024. Regarding the Implementation Conformance Statement, the most important changes since version 3.1a are:
- Based on SB300 – PICC Presence Check Procedure
- New questions III.1.4 and III.1.5 to check which transaction completion procedure(s) the PCD implements.
- Based on SB303 – Adding an Optional Suspend in the Polling Loop
- New question III.1.1.3 to check if the PCD performs the optional suspend after a polling cycle.
- New optional section for identification of hardware and interface configuration in case of PCD in a Contactless Product. Regarding the Administrative Process, the most important changes since version 3.1a are:
- Clarification on PCD Late Renewal.
- Introduction of PCD Anticipated Renewal process. 3. Activation and migration planning The version 3.2a of the PCD Test Plan will be activated on March 1st, 2025 and will become mandatory on May 1st, 2025.
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.