EMV® Contact Terminal Level 1 Type Approval – IFM Protocol Test Cases
Extracted document text
EMVCo's index flattens the document's layout, so this text is best used for searching and comparing versions rather than reading end-to-end.
This document is large; EMVCo's index truncates its extracted text, so the excerpt below is partial.
EMV® Contact Terminal Level 1 Type Approval IFM Protocol Test Cases Version 1.0a.r September 2025 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
EMV® Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Legal Notice Page i 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 noninfringement. 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. © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
EMV® Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Revision Log – Version 1.0a.r Page ii The following changes have been made to the document since the publication of Version 1.0a. Some of the numbering and cross references in this version have been updated to reflect changes introduced by the published bulletins. The numbering of existing requirements did not change, unless explicitly stated otherwise. Changes based on Specification Updates: Other changes (test coverage, test clarification, editorial correction):
• Editorial updates Version Initial 4.3c 4.3d 1.0a 1.0a.r Date April 2018 December 2021 December 2023 September 2025 Revision Description First version Multiple changes due to the change of Abstract Test Cases to Executable Test Cases Compliance with SB-216, SB-218 and SB-247 Many Test Cases have:
• changed due to the Update of incorrect Cold ATR that leads to Warm RESET for T=0 and T=1 in all relevant test cases
• created due to subcases duplication to improve coverage with D=4 Other changes to improve the Test Cases and editorial updates
• Minor editorial and reference corrections
• 1712: Improve coverage with ’60’ procedure byte between data out and SW
• 1713: Correction of step 17
• 1714: Update delay to repeat the character with parity error and improvement of coverage on step 31
• 1732: Update AC: deactivation delay reduced to 10.8 + D x 960
• 1755.07 to 10: Correction of TCk for the incorrect Cold ATR
• 1770.wx03, 1771.03z, 1772.03z, 1776.03z, 1778.03z, 1779.03z, 1784.03z, 1785.03z, 1788.03z, 1794.w03z, 1804.03z, 1807.04z, 1808.04z, 1809.04z, 1812.03z: Clarify NAD value that shall be used
• 1783: Update b1-b4 of PFB of R-Block in step 24
• 1790: Clarified the scenarios for Warm ATR
• 1792: Link acceptance criteria with support of chain abortion mechanism (ICS)
• 1800.12 and 13: AC update: Remove margin for the inter-character timing.
• 1807.04z: Clarification of expected R(ACK)
• See above © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
EMV® Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Contents Page iii 1. About this Document .................................................................................................... 1 1.1. Introduction ............................................................................................................ 1 1.2. Scope .................................................................................................................... 1 1.3. Reference Documents ........................................................................................... 1 1.3.1. Specification Documents ............................................................................ 2 1.3.2. Laboratory Test Documents........................................................................ 2 1.4. Acronyms and Abbreviations.................................................................................. 3 2. Generic Information about the Tests............................................................................ 5 2.1. Compliance Demonstration Objective .................................................................... 5 2.2. Device Under Test for Level 1 Approval ................................................................. 5 2.3. Test Tool Requirements ......................................................................................... 5 2.4. Default Environmental Test Conditions .................................................................. 5 2.5. Loop-Back Application ........................................................................................... 5 2.6. Test Case Format .................................................................................................. 6 2.7. About the ATR ....................................................................................................... 7 2.8. Warm Reset and Deactivation Windows ................................................................ 8 2.9. T=1 Exchanges: Mandatory S(IFS request) ........................................................... 9 2.10. T=1: Terminal Chaining and IFSC .......................................................................... 9 3. T=0 Test Cases ............................................................................................................ 10 3.1. [1701] Etu Measurement in Direct Convention Using T=0 when TA1 and TA2 are Absent (after cold and warm reset) ............................................................... 10 3.2. [1702] Etu Measurement in Negotiable Mode (cold and warm ATR) .................... 13 3.3. [1703] Valid ATR Timings (cold and warm reset) ................................................. 18 3.4. [1704] ATR Timings Exceeded (cold or warm reset) ............................................ 22 3.5. [1705] Inter-Character Timings Measurement (after cold and warm reset) in Same and Opposite Directions - INS Complemented in Reception ..................... 24 3.6. [1707] Erroneous ATR before and after Warm Reset (T=0 and T=1) ................... 29 3.7. [1708] ATR not Complete..................................................................................... 32 3.8. [1709] Use of ‘61’ and Minimum Inter-Character Timing in Same and Opposite Directions............................................................................................. 33 3.9. [1710] ICC is Slow but Respects WWT: Same and Opposite Directions .............. 38 3.10. [1711] ICC Exceeds WWT in Same and Opposite Directions ............................... 41 3.11. [1712] Several ‘60’ ............................................................................................... 43 3.12. [1713] ‘60’ amid INS Complemented .................................................................... 45 3.13. [1714] Error Detection Using T=0 (while DUT is receiving)................................... 47 3.14. [1715] Supported Value of TD2 - Error Correction Using T=0 (while ICC is receiving) ............................................................................................................ 49 3.15. [1716] Incorrect TS after Cold and Warm Reset ................................................... 52 3.16. [1717] Correct ATR after Warm Reset (T = 0) ...................................................... 54 3.17. [1718] Etu Measurement in Specific Mode (cold and warm ATR)......................... 56 3.18. [1719] Cold & Warm ATR Initiation Delay............................................................. 58 3.19. [1720] Etu Measurement in Specific Mode with TA2 = ‘00’ ................................... 61 3.20. [1722] Maximum Length of the T=0 ATR.............................................................. 63 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
EMV® Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page iv 3.21. [1725] Status Words different from ‘9000’ ............................................................ 65 3.22. [1726] Parity Error in the ATR after Cold and Warm Reset T=0 & T=1 ................. 69 3.23. [1727] Inverse Convention Using T=0 (after cold and warm reset) ....................... 71 3.24. [1730] INS Complemented in Reception .............................................................. 75 3.25. [1731] INS Complemented / INS in Reception...................................................... 77 3.26. [1732] Error Repetition (transmitting) ................................................................... 79 3.27. [1733] Interpretation of Repeated Character ........................................................ 81 3.28. [1734] Different Values of the Second Procedure Byte after ‘6C’ and ‘61’ ............ 82 3.29. [1735] Erroneous Procedure Byte Handling ......................................................... 86 3.30. [1736] Erroneous Status Word Handling .............................................................. 88 3.31. [1737] Error Repetition (receiving)........................................................................ 90 3.32. [1738] Case 3 Command: Status Word Different from ‘9000’ ............................... 92 3.33. [1740] Case 4 Command: Correct Warning Status............................................... 94 3.34. [1741] Case 4 Command: Incorrect Warning Status............................................. 96 3.35. [1742] Case 4 Command: Error Indicated after '61' .............................................. 98 3.36. [1743] Case 4 Command: Warning after INS and Error after '61' ....................... 100 3.37. [1744] Case 2, 3 or 4 Command: Abnormal Processing at Step 2...................... 102 4. T = 1 Test Cases ........................................................................................................ 106 4.1. [1750] Etu Measurement in Direct Convention Using T=1 in Specific and Negotiable Modes (after cold and warm reset) .................................................. 108 4.2. [1751] Etu Measurement in Inverse Convention Using T=1 in Specific and Negotiable Modes (after cold and warm reset) .................................................. 114 4.3. [1752] Etu Measurement in Specific Mode Using T=1 with TA2 = ‘01’................ 119 4.4. [1753] Maximum Length of the ATR T=1............................................................ 122 4.5. [1754] Correct ATR after Warm Reset (T=1) ...................................................... 124 4.6. [1755] Supported value of TB1 (any value or absent) and TB2 (any value or absent).............................................................................................................. 126 4.7. [1758] TCK is False or not Returned after Cold and Warm Reset ...................... 128 4.8. [1767] Card fully uses Timings: CWT, BGT, Minimum Inter-Character Timing ... 130 4.9. [1768] Proper then Improper Use of WTX .......................................................... 134 4.10. [1769] Request for I-Block Repetition ................................................................. 136 4.11. [1770] Non-Chained Blocks - One or Two Consecutive Errors in Response to an I-Block Then I-Block ..................................................................................... 139 4.12. [1771] Non Chained Block - Error in Response to an I-Block then Error Notification on I-Block then I-Block .................................................................... 142 4.13. [1772] Error in Response to an I-Block then Error Notification on R-Block then I-Block............................................................................................................... 144 4.14. [1775] ICC Exceeds WTX .................................................................................. 146 4.15. [1776] Error in Response to a Chained I-Block................................................... 148 4.16. [1777] Chaining - Various Error Notifications on R-Block ................................... 151 4.17. [1778] Chaining - Error in Response to an R-Block then I-Block......................... 154 4.18. [1779] Synchronization is Never Reached (with RESYNCH) .............................. 157 4.19. [1782] Chaining in both Directions...................................................................... 160 4.20. [1783] Error Assumed during Chaining in both Directions .................................. 162 4.21. [1784] Chaining in both Directions - Error Notification on Last I-Block of a Chain, then Two Errors during ICC Chaining..................................................... 165 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
EMV® Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page v 4.22. [1785] Non Chained Blocks - Excess of Errors in Response to an I-Block Deactivation ...................................................................................................... 168 4.23. [1787] DUT Chaining - Excess of Error Notifications on I-Block ......................... 171 4.24. [1788] DUT Chaining – Excess of Errors in Response to an I-Block................... 173 4.25. [1789] ICC Exceeds BWT .................................................................................. 176 4.26. [1790] ICC Exceeds CWT .................................................................................. 180 4.27. [1791] BWT Respected ...................................................................................... 186 4.28. [1792] DUT Chaining - Reception of an S(ABORT request) ............................... 188 4.29. [1793] Non Chained Blocks - Excess of Error Notifications on I-Block................ 190 4.30. [1794] Non Chained Blocks - Errors in Response to an I-Block then S(WTX request)............................................................................................................. 192 4.31. [1795] Non Chained Blocks - Error Notification on S(WTX response) ................ 196 4.32. [1797] Non Chained Blocks - Error Notification on S(IFS request) then S(IFS response) .......................................................................................................... 198 4.33. [1798] Respect of IFSI by Terminal .................................................................... 200 4.34. [1800] Timings Respected by the DUT: EGT, BGT, CWT .................................. 205 4.35. [1803] Chained Blocks - WTX Respected .......................................................... 208 4.36. [1804] Non Chained Blocks - Error in Response to an S(IFS request) then S(IFS response) ................................................................................................ 210 4.37. [1805] Chaining or Not - Repeated Requests to Change IFSC between Two Chains............................................................................................................... 212 4.38. [1806] Non Chained Blocks - Error Notification on S(IFS response) then IBlock ................................................................................................................. 214 4.39. [1807] Non Chained Blocks - Error in Response to an I-Block then S(IFS request)............................................................................................................. 216 4.40. [1808] Non Chained Blocks - Error in Response to an S(IFS Response), then I-Block............................................................................................................... 218 4.41. [1809] Non Chained Blocks - Error in Response to an S(IFS response), then Error Notification, then I-Block........................................................................... 220 4.42. [1812] Resynchronization Attempt after Excess of Invalid Blocks in Response to an I-Block ...................................................................................................... 222 4.43. [1814] Non Chained Blocks - Excess of Errors in Response to an S(IFS request)............................................................................................................. 224 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
EMV® Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Scenarios Page vi Scenario 1: [1701] Etu Measurement in Direct Convention Using T=0 when TA1 and TA2 are Absent (after cold and warm reset) ___________________________________________ 12 Scenario 2: [1702] Etu Measurement in Negotiable Mode (cold ATR - y=0) ____________ 15 Scenario 3: [1702] Etu Measurement in Negotiable Mode (warm ATR - y=1) ___________ 17 Scenario 4: [1703] Valid ATR Timings (cold reset - y=0) ___________________________ 19 Scenario 5: [1703] Valid ATR Timings (warm reset - y=1) __________________________ 21 Scenario 6: [1704] ATR Timings Exceeded (cold reset - y=0) _______________________ 22 Scenario 7: [1704] ATR Timings Exceeded (warm reset - y=1) ______________________ 23 Scenario 8: [1705] Inter-Character Timings Measurement (after cold reset) in Same and Opposite Directions - INS Complemented in Reception (y=0) _______________________ 26 Scenario 9: [1705] Inter-Character Timings Measurement (after warm reset) in Same and Opposite Directions - INS Complemented in Reception (y=1) _______________________ 28 Scenario 10: [1707] Erroneous ATR before and after Warm Reset (T=0 and T=1) _______ 31 Scenario 11: [1708] ATR not Complete ________________________________________ 32 Scenario 12: [1709] Use of ‘61’ and Minimum Inter-Character Timing in Same and Opposite Directions _______________________________________________________________ 37 Scenario 13: |1710] ICC is Slow but Respects WWT: Same and Opposite Directions ____ 40 Scenario 14: [1711] ICC Exceeds WWT in Same and Opposite Directions – y=0 ________ 42 Scenario 15: [1711] ICC Exceeds WWT in Same and Opposite Directions – y=1 ________ 42 Scenario 16: [1712] Several ‘60’ _____________________________________________ 44 Scenario 17: [1713] ‘60’ amid INS Complemented________________________________ 46 Scenario 18: [1714] Error Detection Using T=0 (while DUT is receiving)_______________ 48 Scenario 19: [1715] Supported Value of TD2 - Error Correction Using T=0 (while ICC is receiving) _______________________________________________________________ 51 Scenario 20: [1716] Incorrect TS after Cold Reset – y=0 ___________________________ 52 Scenario 21: [1716] Incorrect TS after Warm Reset – y=1__________________________ 53 Scenario 22: [1717] Correct ATR after Warm Reset (T = 0) ________________________ 55 Scenario 23: [1718] Etu Measurement in Specific Mode (cold ATR) – y=0 _____________ 57 Scenario 24: [1718] Etu Measurement in Specific Mode (warm ATR) – y=1 ____________ 57 Scenario 25: [1719] Cold & Warm ATR Initiation Delay (xy=10 and 20) _______________ 59 Scenario 26: [1719] Cold & Warm ATR Initiation Delay (xy=30) _____________________ 59 Scenario 27: [1719] Cold & Warm ATR Initiation Delay (xy=11 and 21) _______________ 59 Scenario 28: [1719] Cold & Warm ATR Initiation Delay (xy=31) _____________________ 60 Scenario 29: [1720] Etu Measurement in Specific Mode with TA2 = ‘00’ _______________ 62 Scenario 30: [1722] Maximum Length of the T=0 (x=1) ____________________________ 64 Scenario 31: [1722] Maximum Length of the T=0 (x=2) ____________________________ 64 Scenario 32: [1725] Status Words different from ‘9000’ ____________________________ 68 Scenario 33: [1726] Parity Error in the ATR after Cold Reset T=0 & T=1 – y=0 _________ 69 Scenario 34: [1726] Parity Error in the ATR after Warm Reset T=0 & T=1 – y=1 ________ 70 Scenario 35: [1727] Inverse Convention Using T=0 (after cold reset) – y=0 ____________ 72 Scenario 36: [1727] Inverse Convention Using T=0 (after warm reset) – y=1 ___________ 74 Scenario 37: [1730] INS Complemented in Reception _____________________________ 76 Scenario 38: [1731] INS Complemented / INS in Reception ________________________ 78 Scenario 39: [1732] Error Repetition (transmitting): x=1 ___________________________ 80 Scenario 40: [1732] Error Repetition (transmitting): x=2 ___________________________ 80 Scenario 41: [1733] Interpretation of Repeated Character__________________________ 81 Scenario 42: [1734] Different Values of the Second Procedure Byte after ‘6C’ and ‘61’ ___ 85 Scenario 43: [1735] Erroneous Procedure Byte Handling __________________________ 87 Scenario 44: [1736] Erroneous Status Word Handling _____________________________ 89 Scenario 45: [1737] Error Repetition (receiving) (x=1) _____________________________ 91 Scenario 46: [1737] Error Repetition (receiving) (x=2) _____________________________ 91 Scenario 47: [1738] Case 3 Command: Status Word Different from ‘9000’ _____________ 93 Scenario 48: [1740] Case 4 Command: Correct Warning Status _____________________ 95 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
EMV® Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page vii Scenario 49: [1741] Case 4 Command: Incorrect Warning Status____________________ 97 Scenario 50: [1742] Case 4 Command: Error Indicated after '61' ____________________ 99 Scenario 51: [1743] Case 4 Command: Warning after INS and Error after '61' _________ 101 Scenario 52: [1744] Case 2 Command: Abnormal Processing at Step 2 (x=1) _________ 104 Scenario 53: [1744] Case 3 Command: Abnormal Processing at Step 2 (x=2) _________ 104 Scenario 54: [1744] Case 4 Command: Abnormal Processing at Step 2 (x=3) _________ 105 Scenario 55: [1750] Etu Measurement in Direct Convention Using T=1 in Specific and Negotiable Modes (after cold reset ; y=0) _____________________________________ 111 Scenario 56: [1750] Etu Measurement in Direct Convention Using T=1 in Specific and Negotiable Modes (after warm reset ; y=1) ____________________________________ 113 Scenario 57: [1751] Etu Measurement in Inverse Convention Using T=1 in Specific and Negotiable Modes (after cold reset ; y=0) _____________________________________ 116 Scenario 58: [1751] Etu Measurement in Inverse Convention Using T=1 in Specific and Negotiable Modes (after warm reset ; y=1) ____________________________________ 118 Scenario 59: [1752] Etu Measurement in Specific Mode Using T=1 with TA2 = ‘01’ _____ 121 Scenario 60: [1753] Maximum Length of the ATR T=1 (x=1) _______________________ 122 Scenario 61: [1753] Maximum Length of the ATR T=1 (x=2) _______________________ 123 Scenario 62: [1754] Correct ATR after Warm Reset (T=1) ________________________ 125 Scenario 63: [1755] Supported value of TB1 (any value or absent) and TB2 (any value or absent) (xy = 01 to 06) ____________________________________________________ 127 Scenario 64: [1755] Supported value of TB1 (any value or absent) and TB2 (any value or absent) (xy = 07 to 10) ____________________________________________________ 127 Scenario 65: [1758] TCK is False or not Returned after Cold Reset (y=0) ____________ 128 Scenario 66: [1758] TCK is False or not Returned after Warm Reset (y=1) ___________ 129 Scenario 67: [1767] Card fully uses Timings: CWT, BGT, Minimum Inter-Character Timing (x=1 or x=3) ____________________________________________________________ 132 Scenario 68: [1767] Card fully uses Timings: CWT, BGT, Minimum Inter-Character Timing (x=2) __________________________________________________________________ 133 Scenario 69: [1768] Proper then Improper Use of WTX (behaviour 1)________________ 135 Scenario 70: [1768] Proper then Improper Use of WTX (behaviour 2)________________ 135 Scenario 71: [1769] Request for I-Block Repetition (x=1) _________________________ 137 Scenario 72: [1769] Request for I-Block Repetition (x=2) _________________________ 138 Scenario 73: [1770] Non-Chained Blocks - One Error in Response to an I-Block Then I-Block (x=1) __________________________________________________________________ 140 Scenario 74: [1770] Non-Chained Blocks - Two Consecutive Errors in Response to an IBlock Then I-Block (x=2) __________________________________________________ 141 Scenario 75: [1771] Non Chained Block - Error in Response to an I-Block then Error Notification on I-Block then I-Block___________________________________________ 143 Scenario 76: [1772] Error in Response to an I-Block then Error Notification on R-Block then IBlock__________________________________________________________________ 145 Scenario 77: [1775] ICC Exceeds WTX (behaviour 1) ____________________________ 147 Scenario 78: [1775] ICC Exceeds WTX (behaviour 2) ____________________________ 147 Scenario 79: [1776] Error in Response to a Chained I-Block _______________________ 150 Scenario 80: [1777] Chaining - Various Error Notifications on R-Block _______________ 153 Scenario 81: [1778] Chaining - Error in Response to an R-Block then I-Block _________ 156 Scenario 82: [1779] Synchronization is Never Reached (with RESYNCH) ____________ 159 Scenario 83: [1782] Chaining in both Directions ________________________________ 161 Scenario 84: [1783] Error Assumed during Chaining in both Directions ______________ 164 Scenario 85: [1784] Chaining in both Directions - Error Notification on Last I-Block of a Chain, then Two Errors during ICC Chaining_________________________________________ 167 Scenario 86: [1785] Non Chained Blocks - Excess of Errors in Response to an I-Block Deactivation ____________________________________________________________ 170 Scenario 87: [1787] DUT Chaining - Excess of Error Notifications on I-Block __________ 172 Scenario 88: [1788] DUT Chaining – Excess of Errors in Response to an I-Block ______ 175 Scenario 89: [1789] ICC Exceeds BWT (x=0,1, 2 - behaviour 1) ____________________ 177 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
EMV® Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page viii Scenario 90: [1789] ICC Exceeds BWT (x=3, 4, 5 - behaviour 1) ___________________ 177 Scenario 91: [1789] ICC Exceeds BWT (x=0, 1, 2 - behaviour 2) ___________________ 178 Scenario 92: [1789] ICC Exceeds BWT (x=3, 4, 5 - behaviour 2) ___________________ 179 Scenario 93: [1790] ICC Exceeds CWT (x=0, behaviour 1) ________________________ 181 Scenario 94: [1790] ICC Exceeds CWT (x=1, behaviour 1) ________________________ 181 Scenario 95: [1790] ICC Exceeds CWT (x=0, behaviour 2) ________________________ 182 Scenario 96: [1790] ICC Exceeds CWT (x=1, behaviour 2) ________________________ 183 Scenario 97: [1791] BWT Respected _________________________________________ 187 Scenario 98: [1792] DUT Chaining - Reception of an S(ABORT request) _____________ 189 Scenario 99: [1793] Non Chained Blocks - Excess of Error Notifications on I-Block _____ 191 Scenario 100: [1794] Non Chained Blocks - Errors in Response to an I-Block then S(WTX request) (x=1) ___________________________________________________________ 194 Scenario 101: [1794] Non Chained Blocks - Errors in Response to an I-Block then S(WTX request) (x=2) ___________________________________________________________ 195 Scenario 102: [1795] Non Chained Blocks - Error Notification on S(WTX response) ____ 197 Scenario 103: [1797] Non Chained Blocks - Error Notification on S(IFS request) then S(IFS response) ______________________________________________________________ 199 Scenario 104: [1798] Respect of IFSI by Terminal (x=0, y=1) ______________________ 201 Scenario 105: [1798] Respect of IFSI by Terminal (x=9, y=1) ______________________ 202 Scenario 106: [1798] Respect of IFSI by Terminal (x=0, y=2) ______________________ 202 Scenario 107: [1798] Respect of IFSI by Terminal (x=9, y=2) ______________________ 203 Scenario 108: [1798] Respect of IFSI by Terminal (y=1) (x=1 to 8) __________________ 204 Scenario 109: [1798] Respect of IFSI by Terminal (y=2) (x=1 to 8) __________________ 204 Scenario 110: [1800] Timings Respected by the DUT: EGT, BGT, CWT (cold reset) ____ 206 Scenario 111: [1800] Timings Respected by the DUT: EGT, BGT, CWT (warm reset) ___ 207 Scenario 112: [1803] Chained Blocks - WTX Respected __________________________ 209 Scenario 113: [1804] Non Chained Blocks - Error in Response to an S(IFS request) then S(IFS response) _________________________________________________________ 211 Scenario 114: [1805] Chaining or Not - Repeated Requests to Change IFSC between Two Chains (example x=2) ____________________________________________________ 213 Scenario 115: [1806] Non Chained Blocks - Error Notification on S(IFS response) then IBlock__________________________________________________________________ 215 Scenario 116: [1807] Non Chained Blocks - Error in Response to an I-Block then S(IFS request) _______________________________________________________________ 217 Scenario 117: [1808] Non Chained Blocks - Error in Response to an S(IFS Response), then I-Block ________________________________________________________________ 219 Scenario 118: [1809] Non Chained Blocks - Error in Response to an S(IFS response), then Error Notification, then I-Block ______________________________________________ 221 Scenario 119: [1812] Resynchronization Attempt after Excess of Invalid Blocks in Response to an I-Block ____________________________________________________________ 223 Scenario 120: [1814] Non Chained Blocks - Excess of Errors in Response to an S(IFS request) _______________________________________________________________ 225 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
EMV® Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Tables Page ix Table 1: Specification Documents ..........................................................................................2 Table 2: List of Abbreviations .................................................................................................4 Table 3: ATR Table (1) ...........................................................................................................7 Table 4: ATR Table (2) ...........................................................................................................8 Table 5: T = 1 Test Cases (with excess of errors) Content .................................................106 Table 6: T = 1 Test Cases (with error notifications) Content ...............................................106 Table 7: T = 1 Test Cases (with error generations) Content ...............................................106 Table 8: T = 1 Test Cases (with error generations then notification) Content......................107 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 1 / 226 1. About this Document 1.1. Introduction The present document describes the detailed organization and requirements of the executable tests the vendors has to comply with, to allow the protocol part of the Contact Terminal Level 1 Type Approval Testing. The intended audience of this document includes test tool vendors, recognised test laboratories and auditors. Describing the executable tests and the associated procedures is necessary to ensure reproducibility of the test results, even across different test laboratories. 1.2. Scope For each individual executable test in this document, the following information is available:
• The test number and codification,
• The objective of the test case,
• The specification references as section(s) of the EMV Book 1 specification document related to the test case,
• The conditions needed to perform the test,
• The procedure to perform the test – generally completed with the scenario below,
• The acceptance criteria are the criteria to meet in order to pass the test,
• The failure action is the action to be done if the test is fail,
• The scenario of the test presented as a flow chart. 1.3. Reference Documents EMV documents are available on the EMVCo web site: http://www.emvco.com/approvals.aspx and http://www.emvco.com/specifications.aspx © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 2 / 226 1.3.1. Specification Documents Document EMV® Level 1 Specifications for Payment Systems – EMV Contact interface Specification EMV® Specification Bulletin No. 284 Contact – Clarification for Procedure Byte Use EMV® Specification Bulletin No. 298 Contact – Clarification of Terminal Timing for Consecutive Characters EMV® – Contact Terminal Level 1 Type Approval – Administrative Process EMV® – Contact Terminal Level 1 Type Approval – Loopback Upper Tester Specification Version Issue date version 1.0, October 2022 First Edition, March 2023 First Edition, September 2023 version 1.0a, December 2023 version 1.0a, December 2023 Table 1: Specification Documents 1.3.2. Laboratory Test Documents The test documents to be applied by EMVCo recognised laboratories when performing an EMV Contact Terminal Type Approval Level 1 session are listed in the following document:
• EMVCo Type Approval
• Contact Terminal Level 1
• Laboratories Documentation Check the last version of this document for any update of the test documents. © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 3 / 226 1.4. Acronyms and Abbreviations The following abbreviations and notations are used in this document: Abbreviation Description APDU Application Protocol Data Unit ATR Answer To Reset BGT Block Guard Time BWI Block Waiting time Integer BWT Block Waiting Time C-APDU Command APDU CLA Class byte of the command message CLK Clock C-TPDU Command TPDU CWI Character Waiting time Integer CWT Character Waiting Time DUT Device Under Test EDC Error Detection Code etu Elementary time unit f Frequency ICC Integrated Circuit Card ICS Implementation Conformance Statement IFD Interface Device IFM Interface Module IFS Information Field Size IFSC Information Field Size for the ICC IFSD Information Field Size for the Terminal IFSI Information Field Size Integer INF Information Field INS Instruction byte for command message IUT Implementation Under Test I/O Input/Output ISO International Organization for Standardization Lc Exact Length of Data Sent by the TAL in a Case 3 or 4 Command Le Maximum Length of Data Expected by the TAL in Response to a Case 2 or 4 Command Licc Exact Length of Data Available in the ICC to be Returned in Response to the Case 2 or 4 Command Received by the ICC © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Abbreviation LEN Lr LT NAD NAK P1 P2 P3 PCB R-APDU R-block RST R-TPDU S-block SUT SW1 SW 2 TCK TPDU TTL UT V WI WTX Description Length Length of Response Data Field Lower Tester Node Address Negative Acknowledgment Parameter 1 Parameter 2 Parameter 3 Protocol Control Byte Response-APDU Receive ready block Reset Response TPDU Supervisory-block System Under Test Status Word 1 Status Word 2 Check Character Transport Protocol Data Unit Terminal Transport Layer Upper Tester Volt Waiting time Integer Waiting Time extension Table 2: List of Abbreviations Page 4 / 226 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r 2. Generic Information about the Tests Page 5 / 226 2.1. Compliance Demonstration Objective Within EMVCo Level 1 type approval process, EMVCo compliance demonstration objectives are composed of 4 test types:
• Type 1: functional – nominal (Valid DUT behavior,)
• Type 2: functional – robustness (DUT reaction to invalid events)
• Type 3: data- flow (PDUs sent to DUT, PDU received from DUT)
• Type 4: control-flow (dynamic interaction between PDUs sent and received) 2.2. Device Under Test for Level 1 Approval The DUT is the Interface Module (IFM) as defined in the “Terminal Level 1 Type Approval Administrative Process” document. 2.3. Test Tool Requirements When, for applied:
•
•
• Type Approval, a Test Tool is used as a LT, the following requirements should be Any executed subcase shall generate traces, logs and a test report. The generation of traces, logs and test reports shall indicate whether the acceptance criterias have been met. All acceptance criterias and related values shall be visible in the traces, logs or test reports (e.g. for a timing measurement, the timing measured by the Test Tool shall be present, so shall be the tolerance used by the Test Tool and the expected value or expected range of values for this timing). Any applied timing shall be visible in the traces, logs or test reports. 2.4. Default Environmental Test Conditions The following environmental conditions shall be used for all the tests described in the present document: Condition Temperature Ambient relative humidity Normal temperature 23°C ± 3°C 50% RH ± 10% RH 2.5. Loop-Back Application The Test Bench which is used to implement the EMV Contactless Terminal Type Approval tests is based on the use of the Loop-Back Application. For a description of this application, please refer to 1.3.1 Specification Documents. © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 6 / 226 2.6. Test Case Format Test codification: The tests described in the following sections are coded this way: [Test Number].[DTS]xyz -Rev V.Vw Where Test Number is the number of the test case:
• From 1701 to 1749: T=0 Test Cases
• From 1750 on: T=1 Test Cases DTS stands for Terminal L1 Protocol Test Case. b: Optional Subcase Reference xyz:
• From 0 to 999 V.Vw refers to the version of the Test Cases in which the Test Case was updated for the last time Objective: The objective describes the EMVCo requirements that will be tested. Conditions: This section describes the test conditions needed to reach the acceptance criteria Procedure. Procedure: This section describes the test procedure needed to perform this test. It is designed using flowcharts. Acceptance Criteria: This section describes the pass criteria to meet in order to pass the test. Scenario: The charts describe all the exchanges with the DUT. They use the following conventions:
• A scenario step number
• An arrow for the exchange direction
• Comments column precises the stage of the scenario: Power-Up, APDU exchange and number…
• Grey exchange box indicates an error. And under T=1:
• a light grey box indicates that an error is generated during the emission of the block
• a dark grey box indicates that an error is assumed during the reception of the block © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 7 / 226 2.7. About the ATR Here are tables with different syntax of ATR designed to help the reading of the following tests. We present multiple instances of ATR that are used in the description of the test cases. They shall be read vertically. The last column shows the general purpose of the character: ATR 1 ATR 2 ATR 3 ATR 4 ATR 5 ATR 6 ATR 7 Basic T=0 ATR. T0 indicates TB1 & TC1 T=0 ATR with inverse convent. & non null TC1 T=0 ATR, T0 indicates TA1 & TB1 T0 ->TD1 that -> T=0+TD2 which -> T=14 (so TCK) TD1 -> T=0 and TC2 TS 3B 3F 3B 3B 3B T0 60 60 30 E0 E0 TA1 11 TB1 00 00 00 00 00 TC1 00 10 TD1 TA2 TB2 TC2 TD2 TA3 TB3 TC3 TC K 00 00 80 40 09 0E 6E Basic T=1 ATR, TD1 -> TD2 -> TA3 and TB3 ( + TCK) T=1 ATR, inverse conv. + TD2 -> TB3 & TC3 3B 3F means direct or inverse convention E0 F0 indicates following TX1 + historical bytes 11 used for computing bit duration 00 00 Deprecated by ISO/IEC 7816-3:2006 , '00' kept for backward compatibility 00 00 used to compute extra- guard time 81 81 indicates following TX2 + protocol type indicates specific / negotiable mode ATR with TB2 is NOT compliant with this specification conveys WWT integer for T=0 31 61 indicates following TX3 + protocol type 20 used to compute IFSC for T=1 01 01 used to compute BWT & CWT for T=1 00 block error detection used for T=1 71 00 checks data integrity for T=1, T=14 Table 3: ATR Table (1) © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 8 / 226 TS T0 TA1 TB1 TC1 TD1 TA2 TB2 TC2 TD2 TA3 TB3 TC3 TCK ATR 8 ATR 9 ATR 10 ATR 11 T=0 ATR with TC2=0 0 (reject ed) T=0 ATR with inverse convent., TC2=00 (rejected) 3B 3F (direct (inverse) ) E0 E0 T=1 ATR with TA3=00 (rejected) 3B (direct)) E0 T=1 ATR with inverse convent., TA3=00 (rejected) 3F (direct)) E0 means direct (3B) or inverse (3F) convention indicates following TX1 + historical bytes 00 00 00 00 00 00 00 00 40 40 81 81 used for computing bit duration Deprecated by ISO/IEC 7816-3:2006 , '00' kept for backward compatibility used to compute extra-guard time indicates following TX2 + protocol type indicates specific / negotiable mode 00 00 31 31 00 00 01 01 ATR with TB2 is NOT compliant with this specification conveys WWT integer for T=0 indicates following TX3 + protocol type used to compute IFSC for T=1 used to compute BWT & CWT for T=1 51 51 block error detection used for T=1 checks data integrity for T=1, T=14 Table 4: ATR Table (2) 2.8. Warm Reset and Deactivation Windows For all the tests where the Terminal sends a warm RESET, the Test Tool shall ensure for the warm RESET that: 1. The Terminal initiates the warm RESET within 24,000 initial etus measured from the leading edge of the start bit of the TS character of the cold ATR to the time that RST is set low. 2. The Terminal does not initiate the warm RESET until T0 character of the cold ATR has been received. 3. The Terminal maintains the RST in state L between 40,000 and 45,000 CLK. © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 9 / 226 2.9. T=1 Exchanges: Mandatory S(IFS request) For all T=1 tests, immediately after reception of a correct ATR, the terminal shall send S(IFS request) with 'FE' and wait for relevant response. 2.10.T=1: Terminal Chaining and IFSC In all relevant tests, the LT shall check that if the terminal sends a chained I-block and this block is not the last one of the chain, the block length shall always be equal to IFSC. © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r 3. T=0 Test Cases Page 10 / 226 3.1. [1701] Etu Measurement in Direct Convention Using T=0 when TA1 and TA2 are Absent (after cold and warm reset) Test codification: 1701.DTSy - Rev 4.3d Test objective: To ensure that the terminal accepts a correct T=0 ATR: focusing on TS, T0, TB1, TC1. To ensure that the terminal continues the card session using the default values of D=1 and F=372 during subsequent exchanges (after the cold and the warm reset). To check the interpretation of procedure bytes INS, 61 and 6C. To check a case 1, case 2 (Le='00'), case 3 and basic case 4 commands. To ensure that the terminal is able to transmit a command with the 'CLA' byte different from '00'. Specifications references: 8.2, 8.3.1 , 8.3.2, 8.3.3.1, 8.4 6th bullet, 9.2.2.3.1, 5.3.1.1 Conditions: Under all standard test conditions. ATR = ATR 1 (basic ATR)
• y=0: cold ATR
• y=1: warm ATR (Incorrect cold ATR that leads to warm reset = ATR 8 (direct convention) or ATR 9 (inverse convention) according to the convention used in warm reset) Remark: With the simple loop-back concept used here, it is not possible to check what status bytes are actually passed as a mandatory trailer of the R-APDU to the Terminal Application Layer. Procedure: Run the following scenario. Acceptance criteria: The «loop-back» goes on until «End-of-Test command». The case 2 original command sent by the TTL shall have P3='00'. The case 4 commands sent by the TTL shall have P3 conformant with the length of the subsequent data sent. The DUT continues the card session using a current etu having a value of 372/f seconds, the same as the initial etu. © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Scenario: Step - Direction 1 DUT 2 DUT Cold Reset ATR (see conditions) Exchanges 3 DUT 4 DUT 5 DUT 6 DUT 7 DUT 8 DUT 9 DUT 10 DUT 11 DUT 12 DUT 13 DUT 14 DUT 15 DUT 16 DUT '00 A4 04 00 0E' (Case 4) ‘A4' "1PAY.SYS.DDF01" '61 05' '00 C0 00 00 05' 'C0' '10 B2 01 0C 00' + '90 00' C '10 B2 01 0C 00' (Case 2) '6C 15' '10 B2 01 0C 15' '61 15' '00 C0 00 00 15' 'C0' '00 82 00 00 10 00 01 02 …0E 0F'+ '90 00' 17 DUT 18 DUT 19 DUT 20 DUT '00 82 00 00 10' (Case 3) '82' '00 01 … 0F' '90 00' 21 DUT 22 DUT 23 DUT 24 DUT 25 DUT 26 DUT 27 DUT 28 DUT 29 DUT '00 A4 04 00 0E' (Case 4) 'A4’ "1PAY.SYS.DDF01" '61 04' '00 C0 00 00 04' 'C0' '00 1E 00 00' + '90 00' C '00 1E 00 00 00' (Case 1) '90 00' C Page 11 / 226 Comments EMV Power-Up APDU exchange 1 APDU exchange 2 APDU exchange 3 APDU exchange 4 APDU exchange 5 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 12 / 226 Step - Direction 30 DUT 31 DUT 32 DUT 33 DUT 34 DUT 35 DUT 36 DUT Exchanges '00 A4 04 00 0E' (Case 4) 'A4' "1PAY.SYS.DDF01" '61 05' '00 C0 00 00 05' 'C0' "EOT Cmd" + '90 00' Comments APDU exchange 6 Scenario 1: [1701] Etu Measurement in Direct Convention Using T=0 when TA1 and TA2 are Absent (after cold and warm reset) © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 13 / 226 3.2. [1702] Etu Measurement in Negotiable Mode (cold and warm ATR) Test codification: 1702.DTSxyz - Rev 4.3d Test objective: To check that the terminal accepts a correct T=0 (cold or warm) ATR indicating the negotiable mode (TA2 absent) with TA1 having any value and continues using the default values of D=1 and F=372, during all subsequent exchanges. Specifications references: 8.3.3.1, 8.4, 9.2.2.3.1, 9.3.1.1 Conditions: Under all standard test conditions.
• z=0: cold ATR
• z=1: warm ATR (Incorrect cold ATR that leads to warm reset = ATR 8 (direct convention) or ATR 9 (inverse convention) according to the convention used in warm reset) Subcases according to xy value are: xy Convention TA1 D 00 '11' 1 01 Direct '12' 2 02 '13' 4 03 '11' 1 04 Inverse '12' 2 05 '13' 4 06 '17' 64 07 Direct 'D1' 1 08 'D9' 20 09 '17' 64 10 Inverse 'D1' 1 11 'D9' 20 ATR 3B 70 11 00 00 3B 70 12 00 00 3B 70 13 00 00 3F 70 11 00 00 3F 70 12 00 00 3F 70 13 00 00 3B 70 17 00 00 3B 70 D1 00 00 3B 70 D9 00 00 3F 70 17 00 00 3F 70 D1 00 00 3F 70 D9 00 00 Procedure: Run the following scenarios. Acceptance criteria: The «loop-back» goes on until «End-of-Test command». The value of D and F used are their default values i.e. F = 372 and D = 1. The case 2 original command sent by the TTL shall have P3='00'. The case 4 commands sent by the TTL shall have P3 conformant with the length of the subsequent data sent. Accepted option for xy=01 and 04: If the terminal supports explicit negotiable mode (see ICS V-7) and TA1 bit 4 to 1 set to “2 (2)” may cause the terminal to initiate proprietary negotiations when TA2 is absent (see ICS V- © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 14 / 226 7.2), the terminal may send a PPS request block following the receipt of the ATR: this block starts with 'FF' and has a size between 3 and 6 bytes. After reception of this block, the Test Tool shall remain mute. Accepted option for xy=02 and 05: If the terminal supports explicit negotiable mode (see ICS V-7) and TA1 bit 4 to 1 set to “3 (4)” may cause the terminal to initiate proprietary negotiations when TA2 is absent (see ICS V7.2), the terminal may send a PPS request block following the receipt of the ATR: this block starts with 'FF' and has a size between 3 and 6 bytes. After reception of this block, the Test Tool shall remain mute. Accepted option for xy=06 and 09: If the terminal supports explicit negotiable mode (see ICS V-7) and TA1 bit 4 to 1 set to “7 (64)” may cause the terminal to initiate proprietary negotiations when TA2 is absent (see ICS V-7.2), the terminal may send a PPS request block following the receipt of the ATR: this block starts with 'FF' and has a size between 3 and 6 bytes. After reception of this block, the Test Tool shall remain mute. Accepted option for xy=08 and 11: If the terminal supports explicit negotiable mode (see ICS V-7) and TA1 bit 4 to 1 set to “9 (20)” may cause the terminal to initiate proprietary negotiations when TA2 is absent (see ICS V-7.2), the terminal may send a PPS request block following the receipt of the ATR: this block starts with 'FF' and has a size between 3 and 6 bytes. After reception of this block, the Test Tool shall remain mute. Accepted option for xy=07, 08, 10 and 11: If the terminal supports explicit negotiable mode (see ICS V-7) and TA1 bit 8 to 5 set to “D (2048)” may cause the terminal to initiate proprietary negotiations when TA2 is absent (see ICS V-7.2), the terminal may send a PPS request block following the receipt of the ATR: this block starts with 'FF' and has a size between 3 and 6 bytes. After reception of this block, the Test Tool shall remain mute. Scenarios: Step - Direction 1 DUT 2 DUT Exchanges Cold Reset ATR (see conditions) – according to x Comments EMV Power-Up 3 DUT 4 DUT 5 DUT 6 DUT 7 DUT 8 DUT 9 DUT 10 DUT 11 DUT '00 A4 04 00 0E' (Case 4) ‘A4' "1PAY.SYS.DDF01" '61 05' '00 C0 00 00 05' 'C0' '00 B2 01 0C 00' + '90 00' C '00 B2 01 0C 00' (Case 2) '6C 15' APDU exchange 1 APDU exchange 2 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 15 / 226 Step - Direction 12 DUT 13 DUT 14 DUT Exchanges '00 B2 01 0C 15' 'B2' '00 82 00 00 10 00 01 02 … 0E 0F'+ '90 00' Comments 15 DUT 16 DUT 17 DUT 18 DUT '00 82 00 00 10' (Case 3) '82' '00 01 02 03… 0F' '90 00' APDU exchange 3 19 DUT 20 DUT 21 DUT 22 DUT 23 DUT 24 DUT 25 DUT '00 A4 04 00 0E' (Case 4) 'A4’ "1PAY.SYS.DDF01" '61 04' '00 C0 00 00 04' 'C0' '00 1E 00 00' + '90 00' APDU exchange 4 26 DUT 27 DUT C '00 1E 00 00 00' (Case 1) '90 00' APDU exchange 5 28 DUT 29 DUT 30 DUT 31 DUT 32 DUT 33 DUT 34 DUT C '00 A4 04 00 0E' (Case 4) 'A4' "1PAY.SYS.DDF01" '61 05' '00 C0 00 00 05' 'C0' "EOT Cmd" + '90 00' APDU exchange 6 Scenario 2: [1702] Etu Measurement in Negotiable Mode (cold ATR - y=0) Step - Direction 1 DUT 2 DUT 3 DUT 4 DUT 5 DUT Exchanges Cold Reset Cold ATR (see conditions) – y=1 Warm Reset Warm ATR (see conditions) – according to x '00 A4 04 00 0E' (Case 4) Comments EMV Power-Up APDU exchange 1 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 16 / 226 Step - Direction 6 DUT 7 DUT 8 DUT 9 DUT 10 DUT 11 DUT Exchanges ‘A4' "1PAY.SYS.DDF01" '61 05' '00 C0 00 00 05' 'C0' '00 B2 01 0C 00' + '90 00' 12 DUT 13 DUT 14 DUT 15 DUT 16 DUT C '00 B2 01 0C 00' (Case 2) '6C 15' '00 B2 01 0C 15' 'B2' '00 82 00 00 10 00 01 02 … 0E 0F'+ '90 00' 17 DUT 18 DUT 19 DUT 20 DUT '00 82 00 00 10' (Case 3) '82' '00 01 02 03… 0F' '90 00' 21 DUT 22 DUT 23 DUT 24 DUT 25 DUT 26 DUT 27 DUT 28 DUT 29 DUT 30 DUT 31 DUT 32 DUT 33 DUT 34 DUT 35 DUT 36 DUT '00 A4 04 00 0E' (Case 4) 'A4’ "1PAY.SYS.DDF01" '61 04' '00 C0 00 00 04' 'C0' '00 1E 00 00' + '90 00' C '00 1E 00 00 00' (Case 1) '90 00' C '00 A4 04 00 0E' (Case 4) 'A4' "1PAY.SYS.DDF01" '61 05' '00 C0 00 00 05' 'C0' "EOT Cmd" + '90 00' Comments APDU exchange 2 APDU exchange 3 APDU exchange 4 APDU exchange 5 APDU exchange 6 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 17 / 226 Scenario 3: [1702] Etu Measurement in Negotiable Mode (warm ATR - y=1) © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 18 / 226 3.3. [1703] Valid ATR Timings (cold and warm reset) Test codification: 1703.DTSxy - Rev 4.3d Test objective: To ensure that the DUT correctly receives and interprets an ATR with a character-to-character time minimum and maximum. Specifications references: 8.1, 8.4 4th, 5th and 6th bullet Conditions: Under all standard test conditions.
• y=1: cold ATR
• y=2: warm ATR (Incorrect cold ATR that leads to warm reset = ATR 8) Subcases according to x value are: x ATR Inter-character timing (initial etus) 3B 11.8 0 20 11.8 00 9.8 (duration of last character) 3B 10,080 1 20 16 00 10 (duration of last character) 3B 10,074 2 20 10,074 00 10 (duration of last character) ATR duration (initial etus) 33.4 10,106 20,158 Procedure: Run the following scenarios. Acceptance criteria: The «loop-back» goes on until «End-of-Test command». The case 2 original command sent by the TTL shall have P3='00'. The case 4 commands sent by the TTL shall have P3 conformant with the length of the subsequent data sent. Scenarios: Step - Direction 1 DUT 2 DUT Cold Reset ATR (see conditions) Exchanges Comments EMV Power-Up 3 DUT 4 DUT 5 DUT 6 DUT '00 A4 04 00 0E' (Case 4) ‘A4' "1PAY.SYS.DDF01" '61 05' APDU exchange 1 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 19 / 226 Step - Direction 7 DUT 8 DUT 9 DUT Exchanges '00 C0 00 00 05' 'C0' '00 B2 01 0C 00' + '90 00' 10 DUT 11 DUT 12 DUT 13 DUT 14 DUT C '00 B2 01 0C 00' (Case 2) '6C 15' '00 B2 01 0C 15' 'B2' '00 82 00 00 10 00 01 …0E 0F'+ '90 00' Comments APDU exchange 2 15 DUT 16 DUT 17 DUT 18 DUT '00 82 00 00 10' (Case 3) '82' '00 01 02 03… 0E 0F' '90 00' APDU exchange 3 19 DUT 20 DUT 21 DUT 22 DUT 23 DUT 24 DUT 25 DUT 26 DUT 27 DUT 28 DUT 29 DUT 30 DUT 31 DUT 32 DUT 33 DUT 34 DUT '00 A4 04 00 0E' (Case 4) APDU exchange 4 'A4’ "1PAY.SYS.DDF01" '61 04' '00 C0 00 00 04' 'C0' '00 1E 00 00' + '90 00' C '00 1E 00 00 00' (Case 1) APDU exchange 5 '90 00' C '00 A4 04 00 0E' (Case 4) APDU exchange 6 'A4' "1PAY.SYS.DDF01" '61 05' '00 C0 00 00 05' 'C0' "EOT Cmd" + '90 00' Scenario 4: [1703] Valid ATR Timings (cold reset - y=1) © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Step - Direction 1 DUT 2 DUT 3 DUT 4 DUT Cold Reset ATR (see conditions) Warm Reset ATR (see conditions) Exchanges 5 DUT 6 DUT 7 DUT 8 DUT 9 DUT 10 DUT 11 DUT 12 DUT 13 DUT 14 DUT 15 DUT 16 DUT '00 A4 04 00 0E' (Case 4) ‘A4' "1PAY.SYS.DDF01" '61 05' '00 C0 00 00 05' 'C0' '00 B2 01 0C 00' + '90 00' C '00 B2 01 0C 00' (Case 2) '6C 15' '00 B2 01 0C 15' 'B2' '00 82 00 00 10 00 01 … 0E 0F'+ '90 00' 17 DUT 18 DUT 19 DUT 20 DUT '00 82 00 00 10' (Case 3) '82' '00 01 02 03… 0F' '90 00' 21 DUT 22 DUT 23 DUT 24 DUT 25 DUT 26 DUT 27 DUT 28 DUT 29 DUT 30 DUT '00 A4 04 00 0E' (Case 4) 'A4’ "1PAY.SYS.DDF01" '61 04' '00 C0 00 00 04' 'C0' '00 1E 00 00' + '90 00' C '00 1E 00 00 00' (Case 1) '90 00' C '00 A4 04 00 0E' (Case 4) Page 20 / 226 Comments EMV Power-Up APDU exchange 1 APDU exchange 2 APDU exchange 3 APDU exchange 4 APDU exchange 5 APDU exchange 6 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 21 / 226 Step - Direction 31 DUT 32 DUT 33 DUT 34 DUT 35 DUT 36 DUT 'A4' "1PAY.SYS.DDF01" '61 05' '00 C0 00 00 05' 'C0' "EOT Cmd" + '90 00' Exchanges Comments Scenario 5: [1703] Valid ATR Timings (warm reset - y=2) © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 22 / 226 3.4. [1704] ATR Timings Exceeded (cold or warm reset) Test codification: 1704.DTSxy - Rev 4.3d Test objective: To ensure that, if the ICC exceeds one of the ATR maximum timings (inter-character timing and ATR duration), the DUT initiates the deactivation. Specifications references: 8.4 3rd, 4th, 5th and 6th bullet Conditions: Under all standard test conditions.
• y=0: cold ATR
• y=1: warm ATR (Incorrect cold ATR – with correct timing - that leads to warm reset = ATR 8) Subcases according to x value are: x ATR Inter-character timing (initial etus) 3B 10,320 (= 9,600 + 480 + 240) 0 20 16 00 10 (duration of last character) 3B 6,876 1 60 6,876 00 6,876 00 10 (duration of last character) ATR duration (initial etus) 10,346 20,638 (19,200 + 960 + 478) Procedure: Run the following scenarios. Acceptance criteria:
• x=0: the terminal deactivates the ICC within 14,400 (4,800 + 9,600) initial etus following the leading edge of the start bit of the TS character of the ATR (cold or warm). No command is transferred.
• x=1: the terminal initiates the deactivation sequence within 24,000 initial etus (4,800 + 19,200 initial etus) following the leading edge of the start bit of the TS character. Scenarios: Step - Direction 1 DUT 2 DUT Cold Reset ATR – y=0 Exchanges Comments EMV Power-Up 3 DUT The IFM rejects the card EMV Power-Down (internal call) Scenario 6: [1704] ATR Timings Exceeded (cold reset - y=0) © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 23 / 226 Step - Direction 1 DUT 2 DUT 3 DUT 4 DUT Cold Reset cold ATR – y=1 Warm Reset warm ATR – y=1 Exchanges Comments EMV Power-Up 5 DUT The IFM rejects the card EMV Power-Down (internal call) Scenario 7: [1704] ATR Timings Exceeded (warm reset - y=1) © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 24 / 226 3.5. [1705] Inter-Character Timings Measurement (after cold and warm reset) in Same and Opposite Directions - INS Complemented in Reception Test codification: 1705.DTSxy - Rev 4.3d Test objective: To ensure that the DUT correctly receives and interprets a cold ATR in T=0, with TC1 having any value in the range ‘00’ to ‘FF’ or TC1 absent and continues the session using the correct inter-character timing. To ensure that the DUT correctly uses the procedure byte equal to complement of INS byte when it sends the data and also a pair of INS complement/INS procedure bytes. To ensure that the DUT respects the inter-character delay between two consecutive characters sent in opposite directions. Specifications references: 8.3.2, 8.3.3.3, 8.3.3.8, 8.3.3.11, 9.2.2.1, 9.2.2.3.1 Conditions: Under all standard test conditions.
• y=0: cold ATR
• y=1: warm ATR (Incorrect cold ATR that leads to warm reset = ATR 8) Subcases according to x value are: x TC1 Cold ATR (y=0) Warm ATR (y=1) 0 '00' '3B F0 13 00 00 10 '3B 60 00 00' 80' 1 '80' '3B F0 13 00 80 10 '3B 60 00 80' 80' 2 'F0' '3B F0 13 00 F0 10 '3B 60 00 F0' 80' 3 'FF' '3B F0 13 00 FF 10 '3B 60 00 FF' 80' 4 'FE' '3B F0 13 00 FE 10 '3B 60 00 FE' 80' 5 absent '3B B0 13 00 10 80' '3B 20 00' 6 '50' '3B F0 13 00 50 50 '3B E0 00 50 40 80 0A' 0A' minimum Intercharacter timing 12 etus 140 etus 252 etus 12 etus 266 etus 12 etus 92 etus maximum Intercharacter timing 13 141 253 13 267 13 93 Procedure: Run the following scenarios. Acceptance criteria: The «loop-back» goes on until «End-of-Test command». The delay between the start leading edges of two consecutive characters sent by the terminal respects the minimum inter-character timing supplied in the table above.The delay between © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 25 / 226 the start leading edges of the last character received by the terminal and the first character it sends exceeds 16 etus. The delay between the start leading edges of two consecutive characters sent by the terminal respects the maximum inter-character timing supplied in the table above The case 4 commands sent by the TTL shall have P3 conformant with the length of the subsequent data sent. Scenarios: Step - Direction 1 DUT 2 DUT Exchanges Cold Reset ATR depending on x and y=1 Comments EMV Power-Up 3 DUT 4 DUT 5 DUT 6 DUT 7 DUT 8 DUT 9 DUT 10 DUT 11 DUT 12 DUT 13 DUT 14 DUT 15 DUT 16 DUT 17 DUT '00 A4 04 00 0E' (Case 4) ‘A4 complemented’ “1” ‘A4 complemented’ “P” ‘A4 complemented’ “A” ‘A4 complemented’ “Y” ‘A4’ ".SYS.DDF01" '61 15' '00 C0 00 00 15' 'C0' '00 82 00 00 10 00 01 02…0E 0F' + '90 00' APDU exchange 1 18 DUT 19 DUT 20 DUT 21 DUT 22 DUT 23 DUT 24 DUT 25 DUT 26 DUT '00 82 00 00 10' (Case 3) '82 complemented’ ‘00’ '82 complemented’ ‘01’ '82 complemented’ ‘02’ '82 complemented’ ‘03’ APDU exchange 2 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 26 / 226 Step - Direction 27 DUT 28 DUT 29 DUT 30 DUT 31 DUT 32 DUT 33 DUT '82 complemented’ ‘04’ '82 complemented’ ‘05’ ‘82’ '06 07 08 09…0E 0F' '90 00' Exchanges Comments 34 DUT 35 DUT 36 DUT 37 DUT 38 DUT 39 DUT 40 DUT 41 DUT 42 DUT 43 DUT 44 DUT 45 DUT 46 DUT 47 DUT 48 DUT '00 A4 04 00 0E' (Case 4) ‘A4 complemented’ “1” ‘A4 complemented’ “P” ‘A4 complemented’ “A” ‘A4 complemented’ “Y” 'A4 ".SYS.DDF01" '61 05' '00 C0 00 00 05' 'C0' "EOT Cmd" + '90 00' APDU exchange 3 Scenario 8: [1705] Inter-Character Timings Measurement (after cold reset) in Same and Opposite Directions - INS Complemented in Reception (y=0) Step - Direction 1 DUT 2 DUT 3 DUT 4 DUT Exchanges Cold Reset ATR (see conditions) – y=1 Warm Reset ATR (see conditions) depending on x and y=1 Comments EMV Power-Up 5 DUT 6 DUT 7 DUT '00 A4 04 00 0E' (Case 4) ‘A4 complemented’ “1” APDU exchange 1 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 27 / 226 Step - Direction 8 DUT 9 DUT 10 DUT 11 DUT 12 DUT 13 DUT 14 DUT 15 DUT 16 DUT 17 DUT 18 DUT 19 DUT 20 DUT 21 DUT 22 DUT 23 DUT 24 DUT 25 DUT 26 DUT 27 DUT 28 DUT 29 DUT 30 DUT 31 DUT 32 DUT 33 DUT 34 DUT 35 DUT 36 DUT 37 DUT 38 DUT 39 DUT Exchanges ‘A4 complemented’ “P” ‘A4 complemented’ “A” ‘A4 complemented’ “Y” ‘A4’ ".SYS.DDF01" '61 15' '00 C0 00 00 15' 'C0' '00 82 00 00 10 00 01 02…0E 0F' + '90 00' '00 82 00 00 10' (Case 3) '82 complemented’ ‘00’ '82 complemented’ ‘01’ '82 complemented’ ‘02’ '82 complemented’ ‘03’ '82 complemented’ ‘04’ '82 complemented’ ‘05’ ‘82’ '06 07 08 09…0E 0F' '90 00' '00 A4 04 00 0E' (Case 4) ‘A4 complemented’ “1” ‘A4 complemented’ Comments APDU exchange 2 APDU exchange 3 © 2011-2025 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries.
Contact Terminal Level 1 Type Approval IFM Protocol Test Cases v1.0a.r Page 28 / 226 Step - Direction 40 DUT 4