EMV®
Terminal Type Approval
Level 2
Test Cases
Version 4.3f
February 2017
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page ii
Legal Notice
The EMV® Specifications are provided “AS IS” without warranties of any kind, and EMVCo
neither assumes nor accepts any liability for any errors or omissions contained in these
Specifications. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES,
EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NONINFRINGEMENT, AS TO THESE SPECIFICATIONS.
EMVCo makes no representations or warranties with respect to intellectual property rights of
any third parties in or in relation to the Specifications. EMVCo undertakes no responsibility to
determine whether any implementation of the EMV® Specifications 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
the EMV® Specifications should consult an intellectual property attorney before any such
implementation.
Without limiting the foregoing, the Specifications 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 these Specifications 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 the EMV®
Specifications.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page iii
Revision Log – Version 4.3f
The following changes have been made to the document since the publication of Version 4.3e.
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
Incorporated changes described in the following Specification Updates:
Test Case
Modification
2CA.019.01
Pass Criterias updates
2CA.025.04
Conditions updates
2CA.030.06
Conditions updates
2CA.056.00
Conditions updates
2CA.119.05
Pass criterias, Conditions and Options updates
2CA.119.06
Pass criterias, Conditions and Options updates
2CA.119.08
New test
2CA.121.01
Conditions updates
2CA.122.00
Conditions updates
2CA.122.01
New test
2CA.122.02
New test
2CA.122.03
New test
2CA.122.04
New test
2CA.123.00
Conditions updates
2CA.123.01
New test
2CA.123.02
New test
2CA.124.00
Pass criterias, Conditions updates
2CA.124.01
Conditions updates
2CA.124.02
Conditions updates
2CA.124.03
Conditions updates
2CA.127.00
New test
2CA.128.00
New test
2CA.129.00
New test
2CA.130.00
New test
2CA.131.00
New test
2CA.132.00
New test
2CA.133.00
New test
2CA.134.00
New test
2CA.135.00
New test
2CA.136.00
New test
2CA.137.00
New test
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
2CA.138.00
New test
2CA.139.00
New test
2CA.140.00
New test
2CC.014.03
Pass Criterias updates
2CC.046.02
Pass Criterias updates
2CC.046.03
Pass Criterias updates
2CC.047.02
Pass Criterias updates
2CC.047.03
Pass Criterias updates
2CC.050.02
Pass Criterias updates
2CC.052.02
Pass Criterias updates
2CC.053.02
Pass Criterias updates
2CC.054.02
Pass Criterias updates
2CC.055.02
Pass Criterias updates
2CC.056.02
Pass Criterias updates
2CC.057.02
Pass Criterias updates
2CC.058.02
Pass Criterias updates
2CC.058.09
Pass Criterias updates
2CC.059.02
Pass Criterias updates
2CC.060.04
Pass criterias and Options updates
2CC.061.02
Pass Criterias updates
2CC.063.02
Pass Criterias updates
2CC.063.03
Pass Criterias updates
2CC.064.02
Pass Criterias updates
2CC.064.03
Pass Criterias updates
2CC.065.02
Pass Criterias updates
2CC.065.03
Pass Criterias updates
2CC.066.02
Pass Criterias updates
2CC.066.03
Pass Criterias updates
2CC.067.02
Pass Criterias updates
2CC.067.03
Pass Criterias updates
2CC.068.02
Pass Criterias updates
2CC.068.03
Pass Criterias updates
2CC.069.02
Pass Criterias updates
2CC.069.03
Pass Criterias updates
2CC.086.03
Pass criterias and Options updates
2CC.086.05
New test
2CC.098.00
Pass Criterias updates
2CC.100.01
Pass Criterias updates
2CC.119.01
Options updates
Page iv
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
2CC.122.04
Options updates
2CC.122.05
Options updates
2CC.122.06
Options updates
2CC.122.07
Options updates
2CC.122.08
Options updates
2CC.123.01
Options updates
2CC.123.03
Options updates
2CC.124.01
Options updates
2CC.125.01
Options updates
2CC.125.03
Options updates
2CC.126.01
Options updates
2CC.126.03
Options updates
2CC.127.02
Options updates
2CC.128.01
Options updates
2CC.128.03
Options updates
2CC.129.01
Options updates
2CC.129.03
Options updates
2CC.130.02
Options updates
2CC.130.03
Options updates
2CC.131.01
Options updates
2CC.133.02
Options updates
2CC.134.05
Options updates
2CC.134.06
Options updates
2CC.134.07
Options updates
2CC.134.08
Options updates
2CC.134.09
Options updates
2CC.134.10
Options updates
2CC.134.11
Options updates
2CC.134.12
Options updates
2CC.134.13
Pass Criterieas and Options updates
2CC.134.14
Pass Criterieas and Options updates
2CC.134.15
Options updates
2CC.134.16
Options updates
2CC.134.18
Pass Criterieas and Options updates
2CC.135.01
Options updates
2CC.136.01
Options updates
2CC.136.02
Options updates
2CC.137.01
Options updates
2CC.137.02
Options updates
Page v
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
2CC.139.02
Options updates
2CC.139.03
Options updates
2CC.139.04
Options updates
2CC.140.00
Options updates
2CC.141.00
Options updates
2CC.141.01
Options updates
2CC.141.02
Options updates
2CC.141.03
Options updates
2CC.142.00
Options updates
2CC.143.00
Options updates
2CC.144.03
Options updates
2CC.144.05
Options updates
2CC.144.06
Options updates
2CE.003.10
conditions updated
2CI.035.00
conditions updated
2CJ.012.05
Conditions updates
2CJ.021.03
Options updates
2CJ.021.04
Options updates
2CJ.022.00
Test deleted
2CJ.024.01
Test deleted
2CJ.083.00
Conditions updates
2CJ.083.08
New test
2CJ.083.09
New test
2CJ.083.10
New test
2CJ.086.00
Conditions and Options updates
2CJ.086.01
Conditions and Options updates
2CJ.086.03
New test
2CJ.086.04
New test
2CJ.087.00
Conditions updates
2CJ.087.03
New test
2CJ.087.04
New test
2CJ.087.05
New test
2CJ.088.00
Conditions updates
2CJ.088.01
Conditions updates
2CJ.088.04
New test
2CJ.088.05
New test
2CJ.088.06
New test
2CJ.088.07
New test
2CJ.088.08
New test
Page vi
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
2CJ.088.09
New test
2CJ.089.00
Conditions updates
2CJ.089.01
Conditions updates
2CJ.089.04
New test
2CJ.089.05
New test
2CJ.089.06
New test
2CJ.089.07
New test
2CJ.089.08
New test
2CJ.089.09
New test
2CJ.090.00
Conditions updates
2CJ.090.01
Conditions updates
2CJ.090.04
New test
2CJ.090.05
New test
2CJ.090.06
New test
2CJ.090.07
New test
2CJ.090.08
New test
2CJ.090.09
New test
2CJ.091.00
Conditions updates
2CJ.091.01
Conditions updates
2CJ.091.04
New test
2CJ.091.05
New test
2CJ.091.06
New test
2CJ.091.07
New test
2CJ.091.08
New test
2CJ.091.09
New test
2CJ.092.00
Conditions updates
2CJ.092.01
Conditions updates
2CJ.092.04
New test
2CJ.092.05
New test
2CJ.092.06
New test
2CJ.092.07
New test
2CJ.092.08
New test
2CJ.092.09
New test
2CJ.093.00
Conditions updates
2CJ.093.01
Conditions updates
2CJ.093.04
New test
2CJ.093.05
New test
2CJ.093.06
New test
2CJ.093.07
New test
Page vii
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
2CJ.093.08
New test
2CJ.093.09
New test
2CJ.094.00
Conditions updates
2CJ.094.01
Conditions updates
2CJ.094.04
New test
2CJ.094.05
New test
2CJ.094.06
New test
2CJ.094.07
New test
2CJ.094.08
New test
2CJ.094.09
New test
2CJ.095.00
Conditions updates
2CJ.095.02
New test
2CJ.095.03
New test
2CJ.095.04
New test
2CJ.097.00
Conditions and Options updates
2CJ.097.01
New test
2CJ.097.02
New test
2CJ.099.00
Conditions and Options updates
2CJ.099.01
New test
2CJ.099.02
New test
2CJ.100.00
Pass criterias, Conditions and Options updates
2CJ.100.01
Pass criterias, Conditions and Options updates
2CJ.100.02
Conditions and Options updates
2CJ.100.03
Conditions and Options updates
2CJ.100.04
Conditions updates
2CJ.100.05
Conditions updates
2CJ.100.06
Conditions and Options updates
2CJ.100.07
Conditions and Options updates
2CJ.100.08
New test
2CJ.100.09
New test
2CJ.100.10
New test
2CJ.100.11
New test
2CJ.100.12
New test
2CJ.100.13
New test
2CJ.100.14
New test
2CJ.100.15
New test
2CJ.100.16
New test
2CJ.100.17
New test
2CJ.100.18
New test
Page viii
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
2CJ.100.19
New test
2CJ.100.20
New test
2CJ.100.21
New test
2CJ.100.22
New test
2CJ.100.23
New test
2CJ.100.24
New test
2CJ.100.25
New test
2CJ.100.26
New test
2CJ.100.27
New test
2CJ.100.28
New test
2CJ.100.29
New test
2CJ.100.30
New test
2CJ.100.31
New test
2CJ.100.32
New test
2CJ.100.33
New test
2CJ.115.00
Conditions and Options updates
2CJ.115.02
Pass criterias, Conditions and Options updates
2CJ.115.03
New test
2CJ.115.04
New test
2CJ.140.03
Pass criterias, Conditions updates
2CJ.166.01
Options updates
2CJ.167.01
Options updates
2CJ.168.01
Options updates
2CJ.175.01
Options updates
2CJ.203.02
Options updates
2CK.004.00
Pass criterias, Conditions and Options updates
2CK.004.01
New test
2CK.004.02
New test
2CK.004.03
New test
2CK.013.00
Conditions updates
2CK.013.01
New test
2CK.013.02
New test
2CK.017.00
Conditions updates
2CK.017.01
New test
2CL.062.00
Conditions updates
2CL.063.00
Conditions updates
2CL.064.00
Conditions updates
2CL.065.00
Conditions updates
2CM.001.00
Conditions updates
Page ix
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
2CM.001.01
New test
2CM.002.00
Conditions updates
2CM.002.01
New test
2CM.018.01
Pass criterias updates
2CM.022.00
Conditions and Options updates
2CM.022.01
Conditions and Options updates
2CM.022.02
New test
2CM.022.03
New test
2CM.022.04
New test
2CM.022.05
New test
2CM.023.00
Conditions and Options updates
2CM.023.01
Conditions and Options updates
2CM.023.02
New test
2CM.023.03
New test
2CM.023.04
New test
2CM.023.05
New test
2CM.028.05
New test
2CM.042.08
Options updates
2CM.092.00
Conditions updates
2CM.093.00
Conditions updates
2CM.094.00
Pass criterias, Conditions updates
2CM.094.01
Pass criterias, Conditions updates
2CM.095.00
Conditions updates
2CO.003.00
Conditions updates
2CO.003.01
New test
2CO.015.05
Pass criterias updates
2CO.017.00
Pass criterias updates
2CO.017.01
Test deleted
2CO.022.00
Pass criterias updates
2CO.026.00
Conditions and Options updates
2CO.026.01
New test
2CO.026.02
New test
2CO.026.03
New test
2CO.034.02
Conditions and Options updates
2CO.034.03
Conditions and Options updates
2CS.014.02
Pass criterias updates
2CT.010.00
Pass criterias, Conditions and Options updates
2CT.010.01
Pass criterias, Conditions and Options updates
2CT.010.02
New test
Page x
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
2CT.010.03
New test
2CT.018.00
Conditions and Options updates
2CT.018.01
Conditions and Options updates
2CT.040.00
Conditions updates
2CT.040.01
Conditions updates
2CT.040.02
New test
2CT.040.03
New test
Page xi
Other editorial changes:
New versioning policy of the present document:
Current version is 4.3f, where 4.3 follows the current EMV ICC Specification revision number,
and where .f is incremented (a, b, c, d, e, f…) for each new revision of the present document
issued to correct any issues, or to incorporate Type Approval Bulletins.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xii
Contents
1
Scope............................................................................................................................... 1
2
Referenced Documents ................................................................................................. 2
3
Abbreviations and Notations ........................................................................................ 3
4
Global Glossary .............................................................................................................. 5
5
Test Settings ................................................................................................................. 13
6
7
5.1
Default Values setting ............................................................................................. 13
5.2
Cryptogram Type requested by Terminal ............................................................... 16
5.3
Recommended Test Script Commands .................................................................. 16
Test Structure ............................................................................................................... 18
6.1
Test numbering and associated sub cases ............................................................ 18
6.2
Test Category ......................................................................................................... 18
Test Cases .................................................................................................................... 20
7.1
Data Element and Command ................................................................................. 21
2CA.001.01 Data Elements Storage .................................................................................. 22
2CA.001.02 Data Elements Storage .................................................................................. 23
2CA.001.03 Data Elements Storage .................................................................................. 24
2CA.001.04 Coding of Length in TLV ................................................................................ 25
2CA.002.00 Mapping of data objects into records ............................................................. 26
2CA.004.00 Coding of a Payment System Directory: SFI Range ...................................... 27
2CA.013.00 Processing DOLs: unknown tag ..................................................................... 28
2CA.013.01 Processing DOLs: unknown tag (2) ............................................................... 29
2CA.014.00 Processing DOLs: constructed tag................................................................. 30
2CA.014.01 Processing DOLs: constructed tag (2) ........................................................... 31
2CA.015.00 Processing DOLs: data absent from ICC ....................................................... 32
2CA.015.01 Processing DOLs: data absent from ICC (2).................................................. 33
2CA.016.00 Processing DOLs: shorter data object length, numeric format....................... 34
2CA.016.01 Processing DOLs: shorter data object length, numeric format (2) ................. 35
2CA.017.00 Processing DOLs: shorter data object length, other format ........................... 36
2CA.017.01 Processing DOLs: shorter data object length, other format (2) ...................... 37
2CA.018.00 Processing DOLs: longer data object length, numeric format ........................ 38
2CA.018.01 Processing DOLs: longer data object length, numeric format (2) .................. 39
2CA.019.00 Processing DOLs: longer data object length, compressed numeric format ... 40
2CA.019.01 Processing DOLs: longer data object length, compressed numeric format
(2) ......................................................................................................................................... 41
2CA.020.00 Processing DOLs: longer data object length, other format ............................ 42
2CA.020.01 Processing DOLs: longer data object length, other format (2) ....................... 43
2CA.021.00 Processing DOLs: data not applicable ........................................................... 44
2CA.021.01 Processing DOLs: data not applicable (2)...................................................... 45
2CA.022.00 Data Object List consistency (1) .................................................................... 46
2CA.023.00 Data Object List consistency (2) .................................................................... 47
2CA.025.00 Normal Processing for EXTERNAL AUTHENTICATE - Functions specified in
the AIP: Issuer Authentication .............................................................................................. 49
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xiii
2CA.025.01 ARC checking for contrary response when declining..................................... 51
2CA.025.02 ARC checking for contrary response when approving ................................... 52
2CA.025.03 ARC checking for contrary response when issuing a referral ........................ 53
2CA.025.04 Terminal Processing when Issuer Authentication is not present.................... 54
2CA.026.00 Status Word Processing for EXTERNAL AUTHENTICATE ........................... 55
2CA.026.01 Status Word Processing for EXTERNAL AUTHENTICATE ........................... 57
2CA.027.00 Normal Processing for GENERATE AC ......................................................... 59
2CA.028.00 Normal Processing for GET CHALLENGE .................................................... 60
2CA.029.04 Failed Processing for GET DATA .................................................................. 61
2CA.029.05 Failed Processing for GET DATA (1) ............................................................. 62
2CA.029.06 Failed Processing for GET DATA (2) ............................................................. 63
2CA.029.07 Failed Processing for GET DATA (3) ............................................................. 64
2CA.029.08 Status Word Processing for GET DATA ........................................................ 65
2CA.029.09 Status Word Processing for GET DATA (2) ................................................... 67
2CA.029.10 Status Word Processing for GET DATA (3) ................................................... 69
2CA.029.11 Status Word Processing for GET DATA (4) ................................................... 71
2CA.030.00 Normal Processing for GET PROCESSING OPTIONS ................................. 73
2CA.030.05 Failed Processing for GET PROCESSING OPTIONS ................................... 74
2CA.030.06 Failed Processing for GET PROCESSING OPTIONS (2) ............................. 75
2CA.031.00 Normal Processing for Internal Authenticate.................................................. 76
2CA.031.01 Status Word Processing for Internal Authenticate ......................................... 77
2CA.032.00 Normal Processing for READ RECORD ........................................................ 79
2CA.033.00 Normal Processing for Select......................................................................... 80
2CA.033.01 Failed Processing for Select ADF .................................................................. 81
2CA.033.02 Status Word Processing for SELECT PSE .................................................... 82
2CA.033.04 Failed Processing for Select ADF (2) ............................................................. 84
2CA.034.02 Failed Processing for VERIFY ....................................................................... 85
2CA.034.05 Failed Processing for VERIFY (2) .................................................................. 86
2CA.034.06 Failed Processing for VERIFY (3) .................................................................. 87
2CA.034.07 Failed Processing for VERIFY (4) .................................................................. 89
2CA.035.00 Status Word Processing for GENERATE AC................................................. 90
2CA.036.00 Status Word Processing for GET CHALLENGE ............................................ 92
2CA.037.00 Status Word Processing for GET PROCESSING OPTIONS ......................... 94
2CA.039.00 Status Word Processing for READ RECORD ................................................ 96
2CA.040.00 Status Word Processing for VERIFY ............................................................. 98
2CA.041.00 Coding of Bits and Bytes RFU ....................................................................... 99
2CA.041.01 Coding of Bits and Bytes RFU (2) ................................................................ 100
2CA.041.02 Coding of Bits and Bytes RFU (3) ................................................................ 101
2CA.041.03 Coding of Bits and Bytes RFU (4) ................................................................ 102
2CA.041.04 Coding of Bits and Bytes RFU (5) (Implied) ................................................. 103
2CA.041.05 Coding of Bits and Bytes RFU (5) ................................................................ 104
2CA.041.06 Coding of Bits and Bytes RFU (5) ................................................................ 105
2CA.054.00 Syntax of GENERATE AC returned Data Field (Format 1) .......................... 106
2CA.054.01 Syntax of GENERATE AC returned Data Field (Format 1) (2) .................... 107
2CA.055.00 Syntax of GENERATE AC returned Data Field (Format 2) .......................... 108
2CA.055.01 Syntax of GENERATE AC returned Data Field (Format 2) .......................... 109
2CA.056.00 Proprietary Data Object transmitted in Response to GENERATE AC: Format
2 ......................................................................................................................................... 110
2CA.058.00 Application Transaction Counter .................................................................. 111
2CA.059.00 Application Cryptogram ................................................................................ 112
2CA.060.00 Issuer Application Data ................................................................................ 113
2CA.061.00 Cryptogram Information Data: AAC ............................................................. 114
2CA.062.00 Cryptogram Information Data: TC ................................................................ 115
2CA.062.01 Cryptogram Information Data: TC (2)........................................................... 116
2CA.063.00 Cryptogram Information Data: ARQC .......................................................... 117
2CA.064.00 Cryptogram Information Data: AAR ............................................................. 118
2CA.067.00 Cryptogram Information Data: PIN try limit exceeded .................................. 119
2CA.068.00 Advice requested in the CID and unable to go online .................................. 120
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xiv
2CA.069.00 Advice requested in the CID and advice is unsupported ............................. 121
2CA.070.00 Syntax of GET DATA returned Data Field (ATC) ......................................... 122
2CA.071.00 Syntax of GET DATA returned Data Field (LOATC) .................................... 123
2CA.072.00 Syntax of GET DATA returned Data Field (PIN try limit) - Terminal Behaviour
When PIN Try Counter Equals 0 ........................................................................................ 124
2CA.072.01 Syntax of GET DATA returned Data Field (PIN try limit) - Terminal Behaviour
When PIN Try Counter Equals 0 (2) .................................................................................. 125
2CA.074.00 Syntax of GET PROCESSING OPTIONS Data Field (PDOL) ..................... 126
2CA.075.00 Syntax of GET PROCESSING OPTIONS Data Field (no PDOL) ................ 127
2CA.076.00 Syntax of GET PROCESSING OPTIONS Data Field: PDOL empty
(implied) ............................................................................................................................. 128
2CA.077.00 Syntax of GPO returned Data Field: Format 1 ............................................. 129
2CA.077.01 Syntax of GPO returned Data Field: Format 1 (2)........................................ 130
2CA.078.00 Syntax of GPO returned Data Field: Format 2 ............................................. 131
2CA.078.01 Syntax of GPO returned Data Field: Format 2 (2)........................................ 133
2CA.082.00 Syntax of INTERNAL AUTHENTICATE Data Field ..................................... 134
2CA.083.00 Syntax of INTERNAL AUTHENTICATE returned Data Field: Format 1....... 135
2CA.084.00 Syntax of INTERNAL AUTHENTICATE returned Data Field: Format 2....... 136
2CA.084.01 Syntax of INTERNAL AUTHENTICATE returned Data Field: Format 2 (2) . 138
2CA.089.00 Syntax of READ RECORD returned Data Field ........................................... 139
2CA.092.00 Syntax of SELECT Data Field ...................................................................... 140
2CA.093.00 Syntax of SELECT PSE returned Data Field ............................................... 141
2CA.094.00 Syntax of SELECT PSE returned Data Field: no optional data.................... 142
2CA.097.00 Syntax of SELECT ADF returned Data Field ............................................... 143
2CA.098.00 Syntax of SELECT ADF returned Data Field: optional data......................... 144
2CA.099.00 Response to Proprietary Data in FCI from a SELECT ADF ......................... 145
2CA.099.01 Response to Proprietary Data in FCI from a SELECT PSE ......................... 146
2CA.100.01 Additional data object facilitating domestic processing in selection with
PSE .................................................................................................................................... 147
2CA.103.00 Syntax of VERIFY Data Field for option plaintext offline PIN ....................... 148
2CA.103.01 Syntax of VERIFY Data Field for Enciphered offline PIN ............................. 150
2CA.108.00 Syntax of GET CHALLENGE returned Data Field ....................................... 152
2CA.109.00 Maximum Data Length ................................................................................. 153
2CA.110.00 Maximum Data Length: CVM List ................................................................ 154
2CA.111.00 Maximum Data Length: Issuer Script Commands........................................ 155
2CA.112.00 Maximum Data Length: Issuer Script ........................................................... 157
2CA.113.00 Maximum Data Length: Issuer Script (2)...................................................... 159
2CA.114.00 Maximum Data Length: Issuer Script Commands (2) .................................. 161
2CA.115.00 Terminal or Issuer sourced data .................................................................. 163
2CA.115.01 Terminal or Issuer sourced data (2) ............................................................. 165
2CA.116.00 Issuer-Approved Transaction ....................................................................... 166
2CA.117.00 Issuer-Approved Transaction (2).................................................................. 167
2CA.118.00 Syntax of SELECT PSE returned Data Field with data order not as given in
EMV Specifications ............................................................................................................ 168
2CA.118.01 Syntax of SELECT PSE returned Data Field with unexpected data element in
templates '6F' or 'A5' .......................................................................................................... 169
2CA.119.00 Data order in template for Select ADF ......................................................... 170
2CA.119.01 Data order in template for Select PSE ......................................................... 171
2CA.119.02 Data order in template for GET PROCESSING OPTIONS (Format 2) ........ 172
2CA.119.03 Data order in template for First GENERATE AC Command (format 2) without
CDA .................................................................................................................................... 173
2CA.119.04 Data order in template for Second GENERATE AC Command (format 2)
without CDA ....................................................................................................................... 174
2CA.119.05 Data order in template for First GENERATE AC Command (format 2) with
CDA .................................................................................................................................... 175
2CA.119.06 Data order in template for Second GENERATE AC Command (format 2) with
CDA .................................................................................................................................... 176
2CA.119.07 Data order in template for Reading a Payment System Directory ............... 177
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xv
2CA.119.08 Data order in template for First GENERATE AC Command (format 2) with
CDA (2) .............................................................................................................................. 178
2CA.120.00 Padding in response to SELECT PSE ......................................................... 179
2CA.120.01 Padding in response to PSE Payment System Directory selection ............. 181
2CA.121.00 Minimum Data Length .................................................................................. 183
2CA.121.01 Minimum Data Length (2)............................................................................. 184
2CA.122.00 Payment System reserved Data objects processing.................................... 185
2CA.122.01 Payment System reserved Data objects processing (2) .............................. 186
2CA.122.02 EMV reserved Data objects processing (1).................................................. 187
2CA.122.03 EMV reserved Data objects processing (2).................................................... 189
2CA.122.04 Proprietary Data objects processing (1) ....................................................... 190
2CA.123.00 Payment System reserved Data objects processing.................................... 191
2CA.123.01 EMV reserved Data objects processing ....................................................... 192
2CA.123.02 Proprietary Data objects processing ............................................................ 193
2CA.124.00 Application Version Number assigned by the payment system ................... 194
2CA.124.01 Application Version Number assigned by the payment system ................... 196
2CA.124.02 Application Version Number assigned by the payment system ................... 198
2CA.124.03 Application Version Number assigned by the payment system ................... 200
2CA.125.00 Coding of AIP reserved Bits for Contactless ................................................ 202
2CA.125.01 Coding of AIP reserved Bits for Contactless (2)........................................... 203
2CA.126.00 Coding of TVR reserved Bits for Contactless............................................... 204
2CA.127.00 ASRPD Data in FCI from a SELECT ADF ................................................... 205
2CA.128.00 ASRPD Data in Directory Entry.................................................................... 206
2CA.129.00 PAR Data in Authorisation or in Financial Request...................................... 209
2CA.130.00 PAR Data in Authorisation or in Financial Request (2) ................................ 210
2CA.131.00 PAR Data in Authorisation or in Financial Request and Response ............. 211
2CA.132.00 PAR Data in Authorisation or in Financial Request and Response (2) ........ 212
2CA.133.00 PAR Data in Batch Data Capture ................................................................. 213
2CA.134.00 PAR Data in Batch Data Capture (2) ........................................................... 214
2CA.135.00 PAR Data in Reserval .................................................................................. 215
2CA.136.00 PAR Data in Reserval (2) ............................................................................. 216
2CA.137.00 PAR Data in Online Advice .......................................................................... 217
2CA.138.00 PAR Data in Online Advice (2) ..................................................................... 218
2CA.139.00 PAR Data supported .................................................................................... 219
2CA.140.00 PAR Data supported (2) ............................................................................... 220
7.2
Application Selection ............................................................................................ 221
2CB.002.00 Definition of PSE .......................................................................................... 222
2CB.004.00 Definition of a Record in Payment Systems Directory ................................. 223
2CB.005.00 Definition of Directory Entry Format ............................................................. 224
2CB.007.00 Terminal's List of Supported Applications .................................................... 225
2CB.010.00 Matching AIDS: « same AID » criteria supported......................................... 226
2CB.010.01 Matching AIDS: « same AID » criteria supported (2) ................................... 227
2CB.011.00 Matching AIDs: « AID beginning with Terminal AID » criteria supported ..... 228
2CB.011.01 Matching AIDs: « AID beginning with Terminal AID » criteria supported (2) 229
2CB.012.00 Selection Using the Payment Systems Directory: SELECT PSE................. 230
2CB.013.00 Selection Using the Payment Systems Directory: Card Blocked or Command
Not Supported .................................................................................................................... 231
2CB.016.00 Indicating end of record................................................................................ 232
2CB.017.00 Directory entry does not exist....................................................................... 233
2CB.018.00 Directory entry processing ........................................................................... 234
2CB.019.01 Candidate list with exact match (2) .............................................................. 235
2CB.019.02 Candidate list with exact match (3) .............................................................. 236
2CB.019.04 Candidate list with partial match (2) ............................................................. 237
2CB.019.05 Candidate list with partial match (3) ............................................................. 238
2CB.023.00 Candidate List empty after selection with PSE ............................................ 239
2CB.023.01 Failed Processing for READ RECORD in selection by PSE ........................ 240
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xvi
2CB.024.00 Selection using a list of AIDs........................................................................ 242
2CB.025.06 DF name and AID identical & SELECT command successful ..................... 243
2CB.026.05 DF name and AID identical & application blocked ....................................... 244
2CB.028.00 Selection using a list of AIDs........................................................................ 245
2CB.029.00 Selection using a list of AIDs: candidate list completion .............................. 247
2CB.031.00 Application Selection Indicator: One Occurrence Permitted ........................ 248
2CB.031.06 DF name longer than AID & multiple occurrence & application not blocked 249
2CB.031.07 DF name longer than AID & multiple occurrence & application blocked ...... 251
2CB.031.08 DF name longer than AID & multiple occurrence ......................................... 252
2CB.032.00 DFNAME is different from AID ..................................................................... 254
2CB.034.00 Multiple occurrence of application: next option supported: 90 00 ................ 255
2CB.035.00 Multiple occurrence of application: next option failed: 62 83........................ 256
2CB.036.00 Multiple occurrence of application: next option failed: other ........................ 257
2CB.037.00 Final Selection: no mutually supported application ...................................... 259
2CB.038.00 Final Selection: one mutually supported application .................................... 260
2CB.038.01 Final Selection: Terminal AID match DF Name and Card AID..................... 261
2CB.039.00 Final Selection: cardholder confirmation ...................................................... 262
2CB.039.01 Final Selection: cardholder confirmation (2)................................................. 263
2CB.040.00 Final Selection: no cardholder confirmation ................................................. 264
2CB.041.00 Final Selection: cardholder does not approve .............................................. 265
2CB.042.00 Displaying Application to Cardholder: priority sequence .............................. 266
2CB.042.01 Displaying Application to Cardholder when cardholder confirmation is
supported ........................................................................................................................... 267
2CB.049.00 Terminal Selection of Application without Cardholder Assistance ............... 268
2CB.050.00 Terminal Selection of Application without Cardholder Assistance: confirmation
required .............................................................................................................................. 269
2CB.053.00 Final Selection of Application from Candidate List: list of AID ..................... 270
2CB.053.01 Final Selection of Application from Candidate List: list of AID (2) ................ 271
2CB.054.00 Final Selection of Application from Candidate List: PSE.............................. 272
2CB.055.00 Final Selection of Application from Candidate List: SELECT status different
from 90 00 .......................................................................................................................... 273
7.3
Security Aspects ................................................................................................... 275
2CC.003.00 Terminal shall be able to store 6 CA Index per RID..................................... 276
2CC.004.00 Algorithm For SDA ....................................................................................... 279
2CC.006.00 Bit Length of all Moduli................................................................................. 280
2CC.007.00 Value of Certification Authority Public Key Exponent .................................. 281
2CC.008.00 Value of Issuer Public Key Exponent ........................................................... 282
2CC.009.00 Data missing: CA Public Key Index ............................................................. 283
2CC.010.00 Data missing: Issuer PK Certificate ............................................................. 284
2CC.011.00 Data missing: Issuer PK Exponent .............................................................. 285
2CC.012.00 Data missing: Signed Static Application data .............................................. 286
2CC.014.00 Retrieving CA Public Key used to Perform SDA: Key absent ...................... 287
2CC.014.01 Retrieving CA Public Key used to Perform DDA: Key absent...................... 288
2CC.014.02 Retrieving CA Public Key used to Perform Combined DDA/AC: Key
absent ................................................................................................................................ 289
2CC.014.03 Retrieving CA Public Key used to Perform PIN Encryption: Key absent ..... 290
2CC.014.08 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent
(9) ....................................................................................................................................... 291
2CC.014.09 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent
(10) ..................................................................................................................................... 292
2CC.015.00 Length of Issuer Public Key Certificate ........................................................ 293
2CC.017.00 Recovered Data Trailer not equal to 'BC'..................................................... 294
2CC.018.00 Recovered Data Header not equal to '6A'.................................................... 295
2CC.019.00 Certificate Format not equal to '02' .............................................................. 296
2CC.020.00 Difference between calculated Hash Result and recovered Hash Result.... 297
2CC.021.00 Issuer Identifier does not match leftmost 3-8 PAN digits ............................. 298
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
2CC.022.00
2CC.023.00
2CC.023.01
2CC.023.02
2CC.024.00
2CC.026.00
2CC.028.00
2CC.029.00
2CC.030.00
2CC.031.00
2CC.032.00
2CC.032.01
2CC.033.00
2CC.036.00
2CC.036.01
2CC.036.02
2CC.037.00
2CC.037.01
2CC.039.00
2CC.039.01
2CC.039.02
2CC.040.00
2CC.040.01
2CC.040.02
2CC.041.00
2CC.041.01
2CC.041.02
2CC.042.00
2CC.042.01
2CC.043.00
2CC.043.01
2CC.044.00
2CC.044.01
2CC.044.06
2CC.044.07
2CC.045.00
2CC.045.01
2CC.046.00
2CC.046.01
2CC.046.02
2CC.046.03
2CC.047.00
2CC.047.01
2CC.047.02
2CC.047.03
2CC.050.00
2CC.050.01
2CC.050.02
2CC.050.07
2CC.050.08
2CC.052.00
2CC.052.01
2CC.052.02
2CC.052.07
2CC.052.08
2CC.053.00
2CC.053.01
2CC.053.02
Page xvii
Certificate Expiration Date earlier than today's date .................................... 299
RID, CA Public Key Index and Certificate Serial Number not valid, SDA .... 300
Certification Revocation List update, removal.............................................. 302
Certification Revocation List update, addition .............................................. 303
Issuer Public Key Algorithm not recognized ................................................ 305
Signed Static Application Data Length not OK ............................................ 306
Recovered Data Trailer not equal to 'BC'..................................................... 307
Recovered Data Header not equal to '6A'.................................................... 308
Certificate Format not equal to '03' .............................................................. 309
Difference between calculated Hash Result and recovered Hash Result.... 310
SDA Tag List in Static Data Authentication.................................................. 311
SDA Tag List in Static Data Authentication (2) ............................................ 312
Data Authentication Code Stored ................................................................ 313
Terminal shall be able to store 6 CA Index per RID..................................... 314
Terminal shall be able to store 6 CA Index per RID (2) ............................... 316
Terminal shall be able to store 6 CA Index per RID (3) ............................... 318
Algorithm for DDA ........................................................................................ 320
Algorithm for DDA (2)................................................................................... 322
Bit Length of All Moduli ................................................................................ 324
Bit Length of All Moduli (2) ........................................................................... 325
Bit Length of All Moduli (3) ........................................................................... 326
Value of CA Public Key Exponent................................................................ 327
Value of CA Public Key Exponent (2) .......................................................... 328
Value of CA Public Key Exponent (3) .......................................................... 329
Value of Issuer Public Key Exponent ........................................................... 330
Value of Issuer Public Key Exponent (2) ..................................................... 331
Value of Issuer Public Key Exponent (3) ..................................................... 332
Value of ICC Public Key Exponent .............................................................. 333
Value of ICC Public Key Exponent (2) ......................................................... 334
Data missing: CA Public Key Index ............................................................. 335
Data missing: CA Public Key Index (2) ........................................................ 336
Data missing: Issuer Public Key Certificate ................................................. 338
Data missing: Issuer Public Key Certificate (2) ............................................ 339
Data missing: Issuer Public Key Certificate (7) ............................................ 340
Data missing: Issuer Public Key Certificate (8) ............................................ 342
Data missing: Issuer PK Exponent .............................................................. 344
Data missing: Issuer PK Exponent (2) ......................................................... 345
Data missing: ICC Public Key Certificate ..................................................... 346
Data missing: ICC Public Key Certificate (2) ............................................... 347
Data missing: ICC Public Key Certificate (3) ............................................... 348
Data missing: ICC PIN Encryption Public Key Certificate ............................ 349
Data missing: ICC Public Key Exponent ...................................................... 350
Data missing: ICC Public Key Exponent (2) ................................................ 351
Data missing: ICC Public Key Exponent (3) ................................................ 352
Data missing: ICC PIN Encryption Public Key Exponent ............................. 353
Length of Issuer Public Key Certificate ........................................................ 354
Length of Issuer Public Key Certificate (2)................................................... 355
Length of Issuer Public Key Certificate (3)................................................... 356
Length of Issuer Public Key Certificate (8)................................................... 357
Length of Issuer Public Key Certificate (9)................................................... 358
Recovered Data Trailer not equal to 'BC'..................................................... 360
Recovered Data Trailer not equal to 'BC' (2) ............................................... 361
Recovered Data Trailer not equal to 'BC' (3) ............................................... 362
Recovered Data Trailer not equal to 'BC' (8) ............................................... 363
Recovered Data Trailer not equal to 'BC' (9) ............................................... 364
Recovered Data Header not equal to '6A'.................................................... 365
Recovered Data Header not equal to '6A' (2) .............................................. 366
Recovered Data Header not equal to '6A' (3) .............................................. 367
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xviii
2CC.054.00 Certificate Format not equal to '02' .............................................................. 368
2CC.054.01 Certificate Format not equal to '02' (2) ......................................................... 369
2CC.054.02 Certificate Format not equal to '02' (3) ......................................................... 370
2CC.055.00 Difference between calculated Hash Result and recovered Hash Result.... 371
2CC.055.01 Difference between calculated Hash Result and recovered Hash Result
(2) ....................................................................................................................................... 372
2CC.055.02 Difference between calculated Hash Result and recovered Hash Result
(3) ....................................................................................................................................... 373
2CC.055.07 Difference between calculated Hash Result and recovered Hash Result
(8) ....................................................................................................................................... 374
2CC.055.08 Difference between calculated Hash Result and recovered Hash Result
(9) ....................................................................................................................................... 375
2CC.056.00 Issuer Identifier does not match leftmost 3-8 PAN digits ............................. 377
2CC.056.01 Issuer Identifier does not match leftmost 3-8 PAN digits (2) ........................ 378
2CC.056.02 Issuer Identifier does not match leftmost 3-8 PAN digits (3) ........................ 379
2CC.057.00 Certificate Expiration Date earlier than today's date .................................... 381
2CC.057.01 Certificate Expiration Date earlier than today's date (2) .............................. 382
2CC.057.02 Certificate Expiration Date earlier than today's date (3) .............................. 383
2CC.057.07 Certificate Expiration Date earlier than today's date (8) .............................. 384
2CC.057.08 Certificate Expiration Date earlier than today's date (9) .............................. 385
2CC.058.00 RID, CA Public Key Index and Certificate Serial Number not valid, DDA .... 386
2CC.058.01 RID, CA Public Key Index and Certificate Serial Number not valid, CDA
(2) ....................................................................................................................................... 388
2CC.058.02 RID, CA Public Key Index and Certificate Serial Number not valid, Offline
Enciphered PIN .................................................................................................................. 390
2CC.058.04 Certification Revocation List update, removal (2) ........................................ 392
2CC.058.05 Certification Revocation List update, addition (2) ........................................ 393
2CC.058.06 Certification Revocation List update, removal (3) ........................................ 395
2CC.058.07 Certification Revocation List update, addition (3) ........................................ 397
2CC.058.08 Certification Revocation List update, removal (4) ........................................ 398
2CC.058.09 Certification Revocation List update, addition (4) ........................................ 399
2CC.059.00 Issuer Public Key Algorithm not recognized ................................................ 401
2CC.059.01 Issuer Public Key Algorithm not recognized (2) ........................................... 402
2CC.059.02 Issuer Public Key Algorithm not recognized (3) ........................................... 403
2CC.060.00 Issuer Identifier with length between 3 to 8 digits ........................................ 404
2CC.060.01 Issuer Identifier with length between 3 to 8 digits (2) ................................... 405
2CC.060.02 Issuer Identifier with length between 3 to 8 digits (2) ................................... 406
2CC.060.03 Issuer Identifier with length between 3 to 8 digits (3) ................................... 407
2CC.060.04 Issuer Identifier with length between 3 to 8 digits (4) ................................... 408
2CC.060.05 Issuer Identifier with length between 3 to 8 digits (5) ................................... 410
2CC.061.00 Length of ICC Public Key Certificate............................................................ 412
2CC.061.01 Length of ICC Public Key Certificate (2) ...................................................... 413
2CC.061.02 Length of ICC Public Key Certificate (3) ...................................................... 414
2CC.061.03 Length of ICC PIN Encipherment Public Key Certificate ............................. 415
2CC.061.08 Length of ICC Public Key Certificate (9) ...................................................... 416
2CC.061.09 Length of ICC Public Key Certificate (10) .................................................... 418
2CC.063.00 Recovered Data Trailer not equal to 'BC'..................................................... 420
2CC.063.01 Recovered Data Trailer not equal to 'BC' (2) ............................................... 421
2CC.063.02 Recovered Data Trailer not equal to 'BC' (3) ............................................... 422
2CC.063.03 Recovered Data Trailer not equal to 'BC' (4) ............................................... 423
2CC.064.00 Recovered Data Header not equal to '6A'.................................................... 424
2CC.064.01 Recovered Data Header not equal to '6A' (2) .............................................. 425
2CC.064.02 Recovered Data Header not equal to '6A' (3) .............................................. 426
2CC.064.03 Recovered Data Header not equal to '6A' (4) .............................................. 427
2CC.065.00 Certificate Format not equal to '04' .............................................................. 428
2CC.065.01 Certificate Format not equal to '04' (2) ......................................................... 429
2CC.065.02 Certificate Format not equal to '04' (3) ......................................................... 430
2CC.065.03 Certificate Format not equal to '04' (4) ......................................................... 431
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xix
2CC.066.00 Difference between calculated Hash Result and recovered Hash Result.... 432
2CC.066.01 Difference between calculated Hash Result and recovered Hash Result
(2) ....................................................................................................................................... 433
2CC.066.02 Difference between calculated Hash Result and recovered Hash Result
(3) ....................................................................................................................................... 434
2CC.066.03 Difference between calculated Hash Result and recovered Hash Result
(4) ....................................................................................................................................... 435
2CC.066.08 Difference between calculated Hash Result and recovered Hash Result
(9) ....................................................................................................................................... 436
2CC.066.09 Difference between calculated Hash Result and recovered Hash Result
(10) ..................................................................................................................................... 437
2CC.067.00 Recovered PAN is not equal to read PAN ................................................... 439
2CC.067.01 Recovered PAN is not equal to read PAN (2) .............................................. 440
2CC.067.02 Recovered PAN is not equal to read PAN (3) .............................................. 441
2CC.067.03 Recovered PAN is not equal to read PAN (4) .............................................. 442
2CC.068.00 Certificate Expiration Date earlier than today's date .................................... 443
2CC.068.01 Certificate Expiration Date earlier than today's date (2) .............................. 444
2CC.068.02 Certificate Expiration Date earlier than today's date (3) .............................. 445
2CC.068.03 Certificate Expiration Date earlier than today's date (4) .............................. 446
2CC.069.00 ICC Public Key Algorithm not recognized .................................................... 447
2CC.069.01 ICC Public Key Algorithm not recognized (2)............................................... 448
2CC.069.02 ICC Public Key Algorithm not recognized (3)............................................... 449
2CC.069.03 ICC Public Key Algorithm not recognized (4)............................................... 450
2CC.069.08 ICC Public Key Algorithm not recognized (9)............................................... 451
2CC.069.09 ICC Public Key Algorithm not recognized (10)............................................. 452
2CC.071.00 Dynamic Signature generation..................................................................... 453
2CC.072.00 Default DDOL............................................................................................... 454
2CC.074.00 Source of Unpredictable Number................................................................. 455
2CC.075.00 DDOL does not contain unpredictable Number ........................................... 456
2CC.076.00 Default DDOL does not contain unpredictable Number ............................... 457
2CC.078.00 Signed Dynamic Application Data Length not OK ....................................... 458
2CC.079.00 Recovery Function ....................................................................................... 459
2CC.080.00 Recovered Data Trailer not equal to 'BC'..................................................... 460
2CC.081.00 Recovered Data Header not equal to '6A'.................................................... 461
2CC.082.00 Certificate Format not equal to '05' .............................................................. 462
2CC.083.00 Difference between calculated Hash Result and recovered Hash Result.... 463
2CC.085.00 SDA Tag List in Dynamic Data Authentication............................................. 464
2CC.085.01 SDA Tag List in Dynamic Data Authentication (1) ....................................... 465
2CC.085.02 SDA Tag List in Dynamic Data Authentication (3) ....................................... 466
2CC.085.03 SDA Tag List in Dynamic Data Authentication (4) ....................................... 467
2CC.085.08 SDA Tag List in Dynamic Data Authentication (9) ....................................... 468
2CC.085.09 SDA Tag List in Dynamic Data Authentication (10) ..................................... 469
2CC.086.00 ICC Dynamic Number Stored ...................................................................... 470
2CC.086.01 ICC Dynamic Data ....................................................................................... 471
2CC.086.02 ICC Dynamic Data (2) .................................................................................. 473
2CC.086.03 ICC Dynamic Data (3) .................................................................................. 475
2CC.086.04 ICC Dynamic Data (4) .................................................................................. 477
2CC.086.05 ICC Dynamic Data (5) .................................................................................. 479
2CC.091.00 Key used for PIN Encryption/Decryption...................................................... 481
2CC.094.00 Random behaviour of PIN Encipherment padding pattern .......................... 482
2CC.095.00 Value of ICC PIN Encryption Public Key Exponent ..................................... 484
2CC.095.01 Value of ICC Public Key Exponent .............................................................. 485
2CC.096.00 ICC PIN Encipherment Public Key recovering: ICC PIN Encipherment Public
Key ..................................................................................................................................... 486
2CC.097.00 ICC PIN Encipherment Public Key recovery: ICC Public Key...................... 488
2CC.098.00 ICC PIN Encipherment Public Key recovering failed ................................... 490
2CC.099.00 PIN Entry...................................................................................................... 491
2CC.100.00 Unpredictable Number ................................................................................. 492
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xx
2CC.100.01 Unpredictable Number (2)............................................................................ 493
2CC.102.00 VERIFY ........................................................................................................ 494
2CC.119.00 PDOL in Enhanced Combined DDA/AC ...................................................... 495
2CC.119.01 PDOL in Enhanced Combined DDA/AC ...................................................... 496
2CC.122.00 Response to GENERATE AC when responding AAC is in format 1 or 2 .... 497
2CC.122.01 Response to GENERATE AC when responding AAC is in format 1 or 2
(2) ....................................................................................................................................... 498
2CC.122.02 ICC responds with AAR ............................................................................... 499
2CC.122.03 ICC responds with AAR (2) .......................................................................... 500
2CC.122.04 Response to GENERATE AC when responding AAC is in format 1 or 2
(3) ....................................................................................................................................... 501
2CC.122.05 Response to GENERATE AC when responding AAC is in format 1 or 2
(4) ....................................................................................................................................... 502
2CC.122.06 ICC responds with AAR (3) .......................................................................... 503
2CC.122.07 ICC responds with AAR (4) .......................................................................... 504
2CC.122.08 Response to GENERATE AC when responding AAC is in format 1 or 2
(5) ....................................................................................................................................... 505
2CC.123.00 Signed Dynamic Application Data Length.................................................... 507
2CC.123.01 Signed Dynamic Application Data Length (2) .............................................. 509
2CC.123.02 Signed Dynamic Application Data Length (3) .............................................. 510
2CC.123.03 Signed Dynamic Application Data Length (4) .............................................. 511
2CC.124.00 Recovered Data Trailer not equal to BC ...................................................... 512
2CC.124.01 Recovered Data Trailer not equal to BC (2)................................................. 514
2CC.125.00 Recovered Data Header not equal to 6A ..................................................... 515
2CC.125.01 Recovered Data Header not equal to 6A (2)................................................ 517
2CC.125.02 Recovered Data Header not equal to 6A (3)................................................ 518
2CC.125.03 Recovered Data Header not equal to 6A (4)................................................ 519
2CC.126.00 Recovered Signed Data Format not equal to 05.......................................... 520
2CC.126.01 Recovered Signed Data Format not equal to 05 (2) .................................... 522
2CC.126.02 Recovered Signed Data Format not equal to 05 (3) .................................... 523
2CC.126.03 Recovered Signed Data Format not equal to 05 (4) .................................... 524
2CC.127.00 Recovered CID different from CID obtained after Generate AC (1)............. 525
2CC.127.01 Recovered CID different from CID obtained after Generate AC (2)............. 526
2CC.127.02 Recovered CID different from CID obtained after Generate AC (3)............. 527
2CC.128.00 Compare hash result.................................................................................... 528
2CC.128.01 Compare hash result (2) .............................................................................. 530
2CC.128.02 Compare hash result (3) .............................................................................. 531
2CC.128.03 Compare hash result (4) .............................................................................. 532
2CC.129.00 Compare Transaction Data Hash Code ....................................................... 533
2CC.129.01 Compare Transaction Data Hash Code (2) ................................................. 535
2CC.129.02 Compare Transaction Data Hash Code (3) ................................................. 536
2CC.129.03 Compare Transaction Data Hash Code (4) ................................................. 537
2CC.130.00 Issuer Application Data in Enhanced Combined DDA/AC ........................... 538
2CC.130.01 Issuer Application Data in Enhanced Combined DDA/AC (2)...................... 539
2CC.130.02 Issuer Application Data in Enhanced Combined DDA/AC (3)...................... 540
2CC.130.03 Issuer Application Data in Enhanced Combined DDA/AC (4)...................... 541
2CC.130.04 Issuer Application Data in Enhanced Combined DDA/AC (5)...................... 542
2CC.131.00 ICC Dynamic Number is stored ................................................................... 543
2CC.131.01 ICC Dynamic Number is stored (2) .............................................................. 545
2CC.133.00 Unpredictable Number generated by the terminal ....................................... 546
2CC.133.01 Unpredictable Number not present in CDOLs ............................................. 547
2CC.133.02 Unpredictable Number not present in CDOLs ............................................. 548
2CC.134.00 Response to GENERATE AC when responding TC or ARQC is in format
2 ......................................................................................................................................... 549
2CC.134.03 Response to GENERATE AC when responding AAC is not digitally signed
(implied) ............................................................................................................................. 551
2CC.134.04 GENERATE AC Reference Control Parameter for Combined DDA/AC
generation. ......................................................................................................................... 552
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxi
2CC.134.05 Response to GENERATE AC when responding TC or ARQC is in format 2
(2) ....................................................................................................................................... 553
2CC.134.06 Response to GENERATE AC when responding TC or ARQC is not in format
1 (Implied) (2) ..................................................................................................................... 555
2CC.134.07 Response to GENERATE AC when responding AAC is not digitally signed
(implied) (2) ........................................................................................................................ 556
2CC.134.08 GENERATE AC Reference Control Parameter for Combined DDA/AC
generation (2) ..................................................................................................................... 557
2CC.134.09 Response to GENERATE AC when responding TC or ARQC is in format 2
(3) ....................................................................................................................................... 558
2CC.134.10 Response to GENERATE AC when responding TC or ARQC is not in format
2 (Implied) (3) ..................................................................................................................... 560
2CC.134.11 Response to GENERATE AC when responding TC or ARQC is in format 2
(3) ....................................................................................................................................... 561
2CC.134.12 Response to GENERATE AC when responding TC or ARQC is not in format
1 (Implied) (3) ..................................................................................................................... 563
2CC.134.13 Response to GENERATE AC when responding AAC is not digitally signed
(implied) (3) ........................................................................................................................ 564
2CC.134.14 Response to GENERATE AC when responding AAC is not digitally signed
(implied) (4) ........................................................................................................................ 565
2CC.134.15 GENERATE AC Reference Control Parameter for Combined DDA/AC
generation (3) ..................................................................................................................... 566
2CC.134.16 GENERATE AC Reference Control Parameter for Combined DDA/AC
generation (3) ..................................................................................................................... 567
2CC.134.17 GENERATE AC Reference Control Parameter for Combined DDA/AC
generation (3) ..................................................................................................................... 568
2CC.134.18 Response to GENERATE AC when responding AAC is not digitally signed
(implied) (5) ........................................................................................................................ 569
2CC.135.00 Mandatory data objects are not present in response to generate AC, in
Enhanced Combined DDA/AC ........................................................................................... 570
2CC.135.01 Mandatory data objects are not present in response to generate AC, in
Enhanced Combined DDA/AC (2)...................................................................................... 572
2CC.135.02 Mandatory data objects are not present in response to generate AC, in
Enhanced Combined DDA/AC (3)...................................................................................... 573
2CC.136.00 Values of CDOL2 for Transaction Data hash............................................... 574
2CC.136.01 Values of CDOL2 for Transaction Data hash (2) ......................................... 575
2CC.136.02 Values of CDOL2 for Transaction Data hash (3) ......................................... 576
2CC.137.00 Values of PDOL for Transaction Data hash ................................................. 577
2CC.137.01 Values of PDOL for Transaction Data hash (2) ........................................... 578
2CC.137.02 Values of PDOL for Transaction Data hash (3) ........................................... 579
2CC.138.00 First Combined DDA/AC generation AAC request....................................... 580
2CC.138.01 First Combined DDA/AC generation AAC request....................................... 581
2CC.139.00 Values of CDOL1 for Transaction Data hash............................................... 582
2CC.139.01 Values of CDOL1 for Transaction Data hash (2) ......................................... 583
2CC.139.02 Values of CDOL1 for Transaction Data hash (3) ......................................... 584
2CC.139.03 Values of CDOL1 for Transaction Data hash (4) ......................................... 585
2CC.139.04 Values of CDOL1 for Transaction Data hash (5) ......................................... 586
nd
2CC.140.00 2 GENERATE AC for Combined DDA/AC generation not performed for
ARQC ................................................................................................................................. 587
2CC.141.00 GENERATE AC for Combined DDA/AC generation, case unable to go online,
TC ...................................................................................................................................... 588
2CC.141.01 GENERATE AC for Combined DDA/AC generation, case unable to go online,
AAC .................................................................................................................................... 589
2CC.141.02 GENERATE AC for Combined DDA/AC generation, case unable to go online,
TC (2) ................................................................................................................................. 590
2CC.141.03 GENERATE AC for Combined DDA/AC generation, case unable to go online,
AAC (2) .............................................................................................................................. 591
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxii
nd
2CC.142.00 2 GENERATE AC for Combined DDA/AC generation, Terminal never
requesting CDA .................................................................................................................. 592
2CC.143.00 Response to GENERATE AC when responding TC or ARQC can be in format
1 without CDA .................................................................................................................... 593
2CC.144.00 Hash Result of SDA calculated with a long string of data ............................ 594
2CC.144.01 Hash Result of ICC Public Key calculated with a long string of data ........... 596
2CC.144.02 Hash Result of ICC Public Key calculated with a long string of data (2)...... 598
2CC.144.03 Hash Result of ICC Public Key calculated with a long string of data (3)...... 600
2CC.144.04 Hash Result of ICC Public Key calculated with a long string of data (4)...... 602
2CC.144.05 Hash Result of ICC Public Key calculated with a long string of data (5)...... 604
2CC.144.06 Hash Result of ICC Public Key calculated with a long string of data (6)...... 606
2CC.145.00 Unpredictable Number generated by the terminal ....................................... 608
2CC.145.01 Unpredictable Number generated by the terminal (2) .................................. 609
7.4
Data Objects ......................................................................................................... 611
2CE.001.00 Length field: 1 byte ....................................................................................... 612
2CE.001.01 Length field: 2 bytes ..................................................................................... 613
2CE.001.02 Length field: 2 bytes (2)................................................................................ 614
2CE.003.00 Recognition of ‘Space’ characters in AN formatted Data Objects ................ 615
2CE.003.01 Acceptance of format errors for Selection data objects - PSE ..................... 616
2CE.003.02 Acceptance of format errors for Selection data objects - List of AIDs .......... 617
2CE.003.03 Acceptance of format errors for Selection data objects – FINAL SELECT .. 619
2CE.003.04 Inconsistent selection data for FCI of the PSE and FCI of ADF................... 620
2CE.003.05 Inconsistent selection data between list of AIDs and FINAL ADF................ 621
2CE.003.06 Inconsistent data: only one occurrence in PSE or FINAL SELECT ............. 622
2CE.003.07 Inconsistent data: only one occurrence in SELECT ADF or FINAL
SELECT ............................................................................................................................. 623
2CE.003.08 List of AID format errors ............................................................................... 624
2CE.003.09 Acceptance of format errors for Selection data objects ............................... 625
2CE.003.10 Acceptance of format errors for Selection data objects (2) .......................... 626
2CE.003.11 Acceptance of format errors for Selection data objects (3) .......................... 627
2CE.003.12 Acceptance of format errors on data objects ............................................... 629
7.5
Approved Cryptography Algorithm ....................................................................... 630
2CH.001.00 The Relationship Between the Lengths of the CA, Issuer, and ICC Public
Keys ................................................................................................................................... 631
2CH.001.01 The Relationship Between the Lengths of the CA, Issuer, and ICC Public
Keys (2) .............................................................................................................................. 632
2CH.001.02 The Relationship Between the Lengths of the CA, Issuer, and ICC Public
Keys (3) .............................................................................................................................. 633
2CH.001.03 The Relationship Between the Lengths of the CA, Issuer, and ICC PIN
Encipherment Keys (4)....................................................................................................... 634
2CH.001.04 The Relationship Between the Lengths of the CA, Issuer, and ICC Public
Keys (5) .............................................................................................................................. 635
2CH.003.00 Upper bound for size of moduli .................................................................... 636
2CH.003.01 Upper bound for size of moduli (2)............................................................... 637
2CH.003.02 Upper bound for size of moduli (3)............................................................... 638
2CH.003.03 Upper bound for size of moduli (4)............................................................... 639
2CH.003.04 Upper bound for size of moduli (5)............................................................... 640
7.6
File for Financial Transaction Interchange ........................................................... 641
2CI.001.00
2CI.002.00
2CI.003.00
2CI.004.00
2CI.005.00
READ RECORD with the Short File Identifiers (SFI) ranged from 1 to 10 .... 642
READ RECORD in linear files ....................................................................... 643
READ RECORD in files containing multiple records ..................................... 644
READ RECORD with the record size in the range from 1 to 254 bytes ........ 645
Record Data Format ...................................................................................... 647
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxiii
2CI.007.00 Free access conditions for files accessible using the READ RECORD
command ........................................................................................................................... 648
2CI.009.00 Mandatory Data Objects: Application Expiration Date................................... 649
2CI.010.00 Mandatory Data Objects: PAN ...................................................................... 650
2CI.010.01 Length of Mandatory Data Objects: PAN ...................................................... 651
2CI.011.00 Padding of Data Objects: Track 2 equivalent Data........................................ 652
2CI.013.00 Optional Data Objects ................................................................................... 653
2CI.014.00 Mandatory Data Objects for Offline Static Data Authentication ..................... 654
2CI.015.00 Mandatory Data Objects for Offline Dynamic Data Authentication ................ 655
2CI.017.00 GET DATA on PIN Try Counter..................................................................... 657
2CI.017.01 GET DATA on PIN Try Counter (2) ............................................................... 658
2CI.020.00 Either the LCOL or the UCOL data objects is not present in the ICC............ 659
2CI.021.00 Data retrievable by GET PROCESSING OPTIONS command ..................... 660
2CI.023.00 Functions not specified in the AIP: Offline Static Data Authentication .......... 662
2CI.025.00 Functions not specified in the AIP: Offline Dynamic Data Authentication ..... 663
2CI.027.00 Functions not specified in the AIP: Cardholder verification ........................... 664
2CI.028.00 Functions specified in the AIP: Terminal Risk Management ......................... 665
2CI.028.01 Functions specified in the AIP: Terminal Risk Management (2) .................... 666
2CI.031.00 Functions not specified in the AIP: Issuer Authentication.............................. 667
2CI.034.00 Functions not specified in the Application Interchange Profile: Enhanced
Combined DDA / GENERATE AC ..................................................................................... 668
2CI.035.00 Record Data Format: Payment System & Proprietary data ignored by Terminal
in SFI 1 to 30 ...................................................................................................................... 669
7.7
Functions used in Transaction Processing ........................................................... 670
2CJ.002.00 All bits in TSI and TVR are set to 0b ............................................................. 671
2CJ.002.01 All bits in TSI and TVR are set to 0b (2) ....................................................... 672
2CJ.002.02 All bits in TSI and TVR are set to 0b (3) ....................................................... 673
2CJ.002.03 All bits in TSI and TVR are set to 0b (4) ....................................................... 674
2CJ.002.04 All bits in TSI and TVR are set to 0b (5) ....................................................... 675
2CJ.002.05 All bits in TSI and TVR are set to 0b (6) ....................................................... 676
2CJ.002.06 All bits in TSI and TVR are set to 0b (7) ....................................................... 677
2CJ.002.07 All bits in TSI and TVR are set to 0b (8) ....................................................... 678
2CJ.002.08 All bits in TSI and TVR are set to 0b (9) ....................................................... 679
2CJ.002.09 All bits in TSI and TVR are set to 0b (10) ..................................................... 680
2CJ.002.10 All bits in TSI and TVR are set to 0b (11) ..................................................... 681
2CJ.002.11 All bits in TSI and TVR are set to 0b (12) ..................................................... 682
2CJ.002.12 All bits in TSI and TVR are set to 0b (13) ..................................................... 683
2CJ.002.13 All bits in TSI and TVR are set to 0b (14) ..................................................... 684
2CJ.002.14 All bits in TSI and TVR are set to 0b (15) ..................................................... 685
2CJ.005.00 Rules for Processing Tags listed in the PDOL (1) ........................................ 686
2CJ.006.00 Rules for Processing Tags listed in the PDOL (2) ........................................ 687
2CJ.007.00 Rules for Processing Tags listed in the PDOL (3) ........................................ 688
2CJ.009.00 READ RECORD command execution .......................................................... 689
2CJ.010.00 READ RECORD on each entry in the AFL ................................................... 690
2CJ.010.01 READ RECORD on each entry in the AFL (2).............................................. 691
2CJ.011.00 Data objects processing ............................................................................... 692
2CJ.012.00 Data objects processing (Unrecognized Data Objects) ................................ 693
2CJ.012.01 Non recognized data objects participating in offline data authentication ...... 694
2CJ.012.02 Non recognized data objects participating in offline data authentication (2). 695
2CJ.012.03 Non recognized data objects participating in offline data authentication (3). 696
2CJ.012.04 Data objects processing (Proprietary Data Objects in Records to be Read) 697
2CJ.012.05 Data objects processing (Proprietary Data Objects in Response to PSE
Reading)............................................................................................................................. 698
2CJ.013.00 Record Data Format: mandatory data: Application Expiration Date ............. 699
2CJ.014.00 Record Data Format: mandatory data: PAN ................................................. 700
2CJ.015.00 Record Data Format: mandatory data: CDOL1 ............................................ 701
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxiv
2CJ.016.00 Record Data Format: mandatory data: CDOL2 ............................................ 702
2CJ.017.00 Record Data Format: Unique data objects ................................................... 703
2CJ.018.00 Record Data Format: Proprietary data participating in offline data
authentication ..................................................................................................................... 704
2CJ.018.01 Record Data Format: Proprietary data participating in offline data
authentication (2) ............................................................................................................... 705
2CJ.018.02 Record Data Format: Non-TLV coded proprietary data participating in offline
data authentication (2) ....................................................................................................... 706
2CJ.018.03 Record Data Format: Non-TLV coded proprietary data participating in offline
data authentication (3) ....................................................................................................... 707
2CJ.018.04 Record Data Format: Proprietary data participating in offline data
authentication (3) ............................................................................................................... 709
2CJ.018.09 Record Data Format: Non-TLV coded proprietary data participating in offline
data authentication (10) ..................................................................................................... 710
2CJ.018.10 Record Data Format: Non-TLV coded proprietary data participating in offline
data authentication (11) ..................................................................................................... 712
2CJ.019.00 Record Data Format: Non-TLV coded proprietary data participating in offline
data authentication ............................................................................................................. 714
2CJ.020.00 Offline Static Data Authentication is supported ........................................... 715
2CJ.021.00 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC,
1st Generate AC) ............................................................................................................... 716
2CJ.021.01 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC,
2nd Generate AC) .............................................................................................................. 718
2CJ.021.02 Both the Terminal and the Card support Enhanced Combined DDA/AC
(ARQC) .............................................................................................................................. 720
2CJ.021.03 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC,
2nd Generate AC) (2)......................................................................................................... 722
2CJ.021.04 Both the Terminal and the Card support Enhanced Combined DDA/AC
(ARQC) (2) ......................................................................................................................... 724
2CJ.021.05 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC,
2nd Generate AC) (2)......................................................................................................... 726
2CJ.022.01 Both the Terminal and the Card support Offline SDA (2) ............................. 728
2CJ.022.02 Both the Terminal and the Card support Offline SDA (3) ............................. 729
2CJ.023.00 Both the Offline DDA and the Offline SDA are supported ............................ 730
2CJ.023.01 Both the Offline DDA and the Offline SDA are supported (2) ....................... 731
2CJ.024.00 Neither the Offline DDA nor the Offline SDA nor the Enhanced Combined
DDA/AC is performed ......................................................................................................... 732
2CJ.024.03 Neither the Offline DDA nor the Offline SDA nor the Enhanced Combined
DDA/AC is performed (3) ................................................................................................... 734
2CJ.025.00 Rules for Processing the Input Data ............................................................. 735
2CJ.025.01 Rules for Processing the Input Data (2)........................................................ 737
2CJ.025.02 Rules for Processing the Input Data (3)........................................................ 739
2CJ.025.03 Rules for Processing the Input Data (4)........................................................ 741
2CJ.025.04 Rules for Processing the Input Data (5)........................................................ 743
2CJ.025.05 Rules for Processing the Input Data (6)........................................................ 745
2CJ.026.00 Rules for Processing the records identified by the AFL, when the Offline DDA
is performed (1) .................................................................................................................. 747
2CJ.026.01 Rules for Processing the records identified by the AFL, when the Offline
Combined DDA/AC is performed ....................................................................................... 749
2CJ.027.00 Rules for Processing the records identified by the AFL, when the Offline DDA
is performed (2) .................................................................................................................. 751
2CJ.027.01 Rules for Processing the records identified by the AFL, when the Offline
Combined DDA/AC is performed (2) .................................................................................. 753
2CJ.028.00 Rules for Processing the records identified by the AFL, when the Offline SDA
is performed (1) .................................................................................................................. 755
2CJ.029.00 Rules for Processing the records identified by the AFL, when the Offline SDA
is performed (2) .................................................................................................................. 757
2CJ.030.00 Processing AIP during Offline Static Data Authentication ............................ 759
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxv
2CJ.030.01 Processing AIP during Offline Data Authentication (2) ................................. 761
2CJ.030.02 Processing AIP during Offline Data Authentication: Enhanced Combined DDA
/ GENERATE AC ............................................................................................................... 763
2CJ.032.00 Offline Static Data Authentication fails.......................................................... 765
2CJ.033.00 Offline Dynamic Data Authentication fails..................................................... 766
2CJ.035.00 Processing Restrictions function execution .................................................. 767
2CJ.036.00 Application Version Number assigned by the payment system .................... 768
2CJ.037.00 Application Version Number is not present in the ICC.................................. 769
2CJ.039.00 Application Version Number present in the ICC and in the terminal are the
same (implied).................................................................................................................... 770
2CJ.041.00 AUC is present in the ICC and Transaction is conducted at an ATM ........... 771
2CJ.042.00 AUC is present in the ICC and Transaction is conducted at an ATM
(implied) ............................................................................................................................. 772
2CJ.043.00 AUC is present in the ICC and Transaction is not conducted at an ATM ..... 773
2CJ.044.00 AUC is present in the ICC and Transaction is not conducted at an ATM
(implied) ............................................................................................................................. 774
2CJ.045.00 Transaction type is a Cash transaction, and Issuer Country Code = Terminal
Country Code ..................................................................................................................... 775
2CJ.046.00 Transaction type is a Cash transaction, and Issuer Country Code = Terminal
Country Code (implied) ...................................................................................................... 776
2CJ.047.00 Transaction type is a Cash transaction, and Issuer Country Code differs from
Terminal Country Code ...................................................................................................... 777
2CJ.048.00 Transaction type is a Cash transaction, and Issuer Country Code differs from
Terminal Country Code (implied) ....................................................................................... 778
2CJ.049.00 Transaction type is a Purchase of goods and services, and Issuer Country
Code = Terminal Country Code ......................................................................................... 779
2CJ.050.00 Transaction type is a Purchase of goods and Services, and Issuer Country
Code = Terminal Country Code (implied) .......................................................................... 780
2CJ.051.00 Transaction type is a Purchase of goods and Services, and Issuer Country
Code differs from Terminal Country Code ......................................................................... 781
2CJ.052.00 Transaction type is a Purchase of goods and services, and Issuer Country
Code differs from Terminal Country Code (implied)........................................................... 782
2CJ.053.00 Transaction type is a Purchase of goods and services, and Issuer Country
Code = Terminal Country Code ......................................................................................... 783
2CJ.054.00 Transaction type is a Purchase of goods and services, and Issuer Country
Code = Terminal Country Code (implied) .......................................................................... 784
2CJ.056.00 Transaction type is a Purchase of goods and services, and Issuer Country
Code differs from Terminal Country Code (implied)........................................................... 785
2CJ.057.00 Transaction has a Cashback amount, and Issuer Country Code = Terminal
Country Code ..................................................................................................................... 786
2CJ.058.00 Transaction has a Cashback amount, and Issuer Country Code = Terminal
Country Code (implied) ...................................................................................................... 787
2CJ.059.00 Transaction type is a Cashback amount, and Issuer Country Code differs from
Terminal Country Code ...................................................................................................... 788
2CJ.060.00 Transaction type is a Cashback amount, and Issuer Country Code differs from
Terminal Country Code (implied) ....................................................................................... 789
2CJ.061.00 Application Usage Control is not present in the ICC (implied) ...................... 790
2CJ.062.00 Application Usage Control is present in the ICC but not Issuer Country code
(implied) ............................................................................................................................. 791
2CJ.063.00 Current Date is earlier than Application Effective Date................................. 792
2CJ.064.00 Current Date is later than Application Effective Date (implied) ..................... 793
2CJ.064.01 Current Date is equal to Application Effective Date (implied) ....................... 794
2CJ.065.00 Current Date is later than Application Expiration Date ................................. 795
2CJ.066.00 Current Date is earlier than Application Expiration Date (implied)................ 796
2CJ.066.01 Current Date is equal to the Application Expiration Date (implied) ............... 797
2CJ.068.00 Cardholder Verification is supported in the AIP ............................................ 798
2CJ.069.00 Supported CVR condition: Always ................................................................ 799
2CJ.070.00 Supported CVR condition: If unattended cash.............................................. 800
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxvi
2CJ.070.01 Supported CVR condition: If manual cash .................................................... 801
2CJ.070.02 Supported CVR condition: If purchase with cashback .................................. 802
2CJ.071.00 Supported CVR condition: If 'not unattended cash and not manual cash, and
not purchase with cashback' .............................................................................................. 803
2CJ.073.00 Supported CVR condition: If Terminal supports the CVM and CVM is offline
PIN ..................................................................................................................................... 804
2CJ.073.01 Supported CVR condition: If Terminal supports the CVM and CVM is
Enciphered offline PIN ....................................................................................................... 805
2CJ.074.00 Supported CVR condition: If Terminal supports the CVM and CVM is online
PIN ..................................................................................................................................... 806
2CJ.075.00 Supported CVR condition: If Terminal supports the CVM and CVM is
signature ............................................................................................................................ 807
2CJ.077.00 Supported CVR condition: If Transaction is in the application currency and is
under X value when the transaction amount is less than X ............................................... 808
2CJ.077.01 Supported CVR condition: If Transaction is in the application currency and is
under X value when the transaction amount is greater than X .......................................... 809
2CJ.077.02 Supported CVR condition: If Transaction is in the application currency and is
under X value when the transaction amount is equal to X ................................................. 810
2CJ.078.00 Supported CVR condition: If Transaction is in the application currency and is
over X value when transaction amount is greater than X................................................... 811
2CJ.078.01 Supported CVR condition: If Transaction is in the application currency and is
over X value when transaction amount is less than X........................................................ 812
2CJ.078.02 Supported CVR condition: If Transaction is in the application currency and is
over X value when transaction amount is equal to X. ........................................................ 813
2CJ.079.00 Supported CVR condition: If Transaction is in the application currency and is
under Y value when the transaction amount is less than Y. .............................................. 814
2CJ.079.01 Supported CVR condition: If Transaction is in the application currency and is
under Y value when the transaction amount is greater than Y .......................................... 815
2CJ.079.02 Supported CVR condition: If Transaction is in the application currency and is
under Y value when the transaction amount is equal to Y. ................................................ 816
2CJ.080.00 Supported CVR condition: If Transaction is in the application currency and is
over Y value when the transaction amount is greater than Y............................................. 817
2CJ.080.01 Supported CVR condition: If Transaction is in the application currency and is
over Y value when the transaction amount is equal to Y. .................................................. 818
2CJ.080.02 Supported CVR condition: If Transaction is in the application currency and is
over Y value when the transaction amount is less than Y.................................................. 819
2CJ.081.01 Random Transaction Selection: Transaction Amount Less than the Threshold
Value for Biased Random Selection .................................................................................. 820
2CJ.081.02 Random Transaction Selection: Transaction Amount Less than the Threshold
Value for Biased Random Selection .................................................................................. 821
2CJ.081.03 Random Transaction Selection: Transaction Amount Equal to or Greater than
the Threshold Value for Biased Random Selection but Less than the Floor Limit ............. 822
2CJ.081.04 Random Transaction Selection: Transaction Amount Equal to or Greater than
the Threshold Value for Biased Random Selection but Less than the Floor Limit ............. 823
2CJ.081.05 Random Transaction Selection: Transaction Amount Equal to or Greater than
the Threshold Value for Biased Random Selection and Greater than the Floor Limit ....... 824
2CJ.081.06 Random Transaction Selection: Transaction Amount Equal to or Greater than
the Threshold Value for Biased Random Selection and Greater than the Floor Limit ....... 825
2CJ.082.01 CVM List is not present in the ICC ................................................................ 826
2CJ.083.00 Second byte of a Cardholder Verification Rule is not satisfied ..................... 827
2CJ.083.01 Non Supported CVR condition: If Terminal supports the CVM and CVM is
offline Plaintext PIN ............................................................................................................ 828
2CJ.083.02 Non Supported CVR condition: If Terminal supports the CVM and CVM is
offline Enciphered PIN ....................................................................................................... 829
2CJ.083.03 Non Supported CVR condition: If Terminal supports the CVM and CVM is
online Enciphered PIN ....................................................................................................... 830
2CJ.083.04 Non Supported CVR condition: If Terminal supports the CVM and CVM is
Signature ............................................................................................................................ 831
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxvii
2CJ.083.05 Non Supported CVR condition: If Terminal supports the CVM and CVM is
offline Plaintext PIN and Signature .................................................................................... 832
2CJ.083.06 Non Supported CVR condition: If Terminal supports the CVM and CVM is
offline Enciphered PIN and Signature ................................................................................ 833
2CJ.083.07 Non Supported CVR condition: If Terminal supports the CVM and CVM is No
CVM Required .................................................................................................................... 834
2CJ.083.08 Second byte of a Cardholder Verification Rule is not satisfied (2)................ 835
2CJ.083.09 Second byte of a Cardholder Verification Rule is not satisfied (3)................ 836
2CJ.083.10 Second byte of a Cardholder Verification Rule is not satisfied (4)................ 837
2CJ.084.00 ICC Data required by the CVM Condition Code is missing .......................... 838
2CJ.084.01 ICC Data required by the CVM Condition Code is missing (Amount
Authorised) ......................................................................................................................... 839
2CJ.085.00 CVM Condition Code is outside the range of codes understood by the
terminal .............................................................................................................................. 840
2CJ.086.00 Cardholder Verification Rule for cash transactions not satisfied, transaction
type .................................................................................................................................... 842
2CJ.086.01 Cardholder Verification Rule for cash transactions not satisfied, terminal type
(2) ....................................................................................................................................... 843
2CJ.086.03 Cardholder Verification Rule for cash transactions not satisfied, transaction
type (3) ............................................................................................................................... 844
2CJ.086.04 Cardholder Verification Rule for cash transactions not satisfied, terminal type
(4) ....................................................................................................................................... 845
2CJ.087.00 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail
CVM (1) .............................................................................................................................. 846
2CJ.087.01 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail
CVM (2) .............................................................................................................................. 847
2CJ.087.02 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail
CVM (3) .............................................................................................................................. 848
2CJ.087.03 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail
CVM (4) .............................................................................................................................. 849
2CJ.087.04 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail
CVM (5) .............................................................................................................................. 850
2CJ.087.05 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail
CVM (6) .............................................................................................................................. 851
2CJ.088.00 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
(Plain text PIN verified by ICC supported) ......................................................................... 852
2CJ.088.01 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
(Plain text PIN verified by ICC not supported) ................................................................... 853
2CJ.088.02 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
(Plain text PIN verified by ICC supported) (2) .................................................................... 854
2CJ.088.03 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
(Plain text PIN verified by ICC not supported) (2) .............................................................. 855
2CJ.088.04 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
(Plain text PIN verified by ICC supported) (3) .................................................................... 857
2CJ.088.05 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
(Plain text PIN verified by ICC not supported) (3) .............................................................. 858
2CJ.088.06 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
(Plain text PIN verified by ICC supported) (4) .................................................................... 859
2CJ.088.07 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
(Plain text PIN verified by ICC not supported) (4) .............................................................. 860
2CJ.088.08 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
(Plain text PIN verified by ICC supported) (5) .................................................................... 861
2CJ.088.09 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
(Plain text PIN verified by ICC not supported) (5) .............................................................. 862
2CJ.089.00 Second byte of CVR satisfied and CVM Code is - Enciphered PIN Online
(Enciphered PIN Online supported) ................................................................................... 863
2CJ.089.01 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online
(Enciphered PIN Online not supported) ............................................................................. 864
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxviii
2CJ.089.02 Second byte of CVR satisfied and CVM Code is - Enciphered PIN Online
(Enciphered PIN Online supported) (2) .............................................................................. 865
2CJ.089.03 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online
(Enciphered PIN Online not supported) (2) ........................................................................ 867
2CJ.089.04 Second byte of CVR satisfied and CVM Code is - Enciphered PIN Online
(Enciphered PIN Online supported) (3) .............................................................................. 869
2CJ.089.05 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online
(Enciphered PIN Online not supported) (3) ........................................................................ 870
2CJ.089.06 Second byte of CVR satisfied and CVM Code is - Enciphered PIN Online
(Enciphered PIN Online supported) (4) .............................................................................. 871
2CJ.089.07 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online
(Enciphered PIN Online not supported) (4) ........................................................................ 872
2CJ.089.08 Second byte of CVR satisfied and CVM Code is - Enciphered PIN Online
(Enciphered PIN Online supported) (5) .............................................................................. 873
2CJ.089.09 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online
(Enciphered PIN Online not supported) (5) ........................................................................ 874
2CJ.090.00 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
and signature (Plain text PIN verified by ICC and signature supported) ............................ 875
2CJ.090.01 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
and signature (Plain text PIN verified by ICC and signature not supported) ...................... 876
2CJ.090.02 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
and signature (Plain text PIN verified by ICC and signature supported) (2) ...................... 877
2CJ.090.03 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
and signature (Plain text PIN verified by ICC and signature not supported) (2) ................ 879
2CJ.090.04 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
and signature (Plain text PIN verified by ICC and signature supported) (3) ...................... 881
2CJ.090.05 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
and signature (Plain text PIN verified by ICC and signature not supported) (3) ................ 882
2CJ.090.06 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
and signature (Plain text PIN verified by ICC and signature supported) (4) ...................... 883
2CJ.090.07 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
and signature (Plain text PIN verified by ICC and signature not supported) (4) ................ 884
2CJ.090.08 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
and signature (Plain text PIN verified by ICC and signature supported) (5) ...................... 885
2CJ.090.09 Second byte of CVR satisfied and CVM Code is Plain text PIN verified by ICC
and signature (Plain text PIN verified by ICC and signature not supported) (5) ................ 886
2CJ.091.00 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC (Enciphered PIN verified by ICC supported) ............................................................... 887
2CJ.091.01 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC (Enciphered PIN verified by ICC not supported) ......................................................... 888
2CJ.091.02 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC (Enciphered PIN verified by ICC supported) (2) ......................................................... 889
2CJ.091.03 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC (Enciphered PIN verified by ICC not supported) (2) ................................................... 891
2CJ.091.04 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC (Enciphered PIN verified by ICC supported) (3) ......................................................... 893
2CJ.091.05 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC (Enciphered PIN verified by ICC not supported) (3) ................................................... 894
2CJ.091.06 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC (Enciphered PIN verified by ICC supported) (4) ......................................................... 895
2CJ.091.07 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC (Enciphered PIN verified by ICC not supported) (4) ................................................... 896
2CJ.091.08 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC (Enciphered PIN verified by ICC supported) (5) ......................................................... 897
2CJ.091.09 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC (Enciphered PIN verified by ICC not supported) (5) ................................................... 898
2CJ.092.00 Second byte of CVR satisfied and CVM Code Enciphered PIN verified by ICC
and signature (Enciphered PIN verified by ICC and signature supported) ........................ 899
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxix
2CJ.092.01 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC and signature (Enciphered PIN verified by ICC and signature not supported) ........... 900
2CJ.092.02 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC and signature (Enciphered PIN verified by ICC and signature supported) (2) ............ 901
2CJ.092.03 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC and signature (Enciphered PIN verified by ICC and signature not supported) (2) ...... 903
2CJ.092.04 Second byte of CVR satisfied and CVM Code Enciphered PIN verified by ICC
and signature (Enciphered PIN verified by ICC and signature supported) (3) ................... 905
2CJ.092.05 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC and signature (Enciphered PIN verified by ICC and signature not supported) (3) ...... 906
2CJ.092.06 Second byte of CVR satisfied and CVM Code Enciphered PIN verified by ICC
and signature (Enciphered PIN verified by ICC and signature supported) (4) ................... 907
2CJ.092.07 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC and signature (Enciphered PIN verified by ICC and signature not supported) (4) ...... 908
2CJ.092.08 Second byte of CVR satisfied and CVM Code Enciphered PIN verified by ICC
and signature (Enciphered PIN verified by ICC and signature supported) (5) ................... 910
2CJ.092.09 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by
ICC and signature (Enciphered PIN verified by ICC and signature not supported) (5) ...... 911
2CJ.093.00 Second byte of CVR satisfied and CVM Code is signature (signature
supported) .......................................................................................................................... 912
2CJ.093.01 Second byte of CVR satisfied and CVM Code is signature (signature not
supported) .......................................................................................................................... 913
2CJ.093.02 Second byte of CVR satisfied and CVM Code is signature (signature
supported) .......................................................................................................................... 914
2CJ.093.03 Second byte of CVR satisfied and CVM Code is signature (signature not
supported) .......................................................................................................................... 915
2CJ.093.04 Second byte of CVR satisfied and CVM Code is signature (signature
supported) (3)..................................................................................................................... 916
2CJ.093.05 Second byte of CVR satisfied and CVM Code is signature (signature not
supported) (3)..................................................................................................................... 918
2CJ.093.06 Second byte of CVR satisfied and CVM Code is signature (signature
supported) (4)..................................................................................................................... 919
2CJ.093.07 Second byte of CVR satisfied and CVM Code is signature (signature not
supported) (4)..................................................................................................................... 920
2CJ.093.08 Second byte of CVR satisfied and CVM Code is signature (signature
supported) (5)..................................................................................................................... 921
2CJ.093.09 Second byte of CVR satisfied and CVM Code is signature (signature not
supported) (5)..................................................................................................................... 922
2CJ.094.00 Second byte of CVR satisfied and CVM Code is no CVM required (No CVM
required is supported) ........................................................................................................ 923
2CJ.094.01 Second byte of CVR satisfied and CVM Code is No CVM required (No CVM
required is not supported) .................................................................................................. 924
2CJ.094.02 Second byte of CVR satisfied and CVM Code is no CVM required (No CVM
required is supported) ........................................................................................................ 925
2CJ.094.03 Second byte of CVR satisfied and CVM Code is No CVM required (No CVM
required is not supported) .................................................................................................. 926
2CJ.094.04 Second byte of CVR satisfied and CVM Code is no CVM required (No CVM
required is supported) (3) ................................................................................................... 928
2CJ.094.05 Second byte of CVR satisfied and CVM Code is No CVM required (No CVM
required is not supported) (3) ............................................................................................. 929
2CJ.094.06 Second byte of CVR satisfied and CVM Code is no CVM required (No CVM
required is supported) (4) ................................................................................................... 930
2CJ.094.07 Second byte of CVR satisfied and CVM Code is No CVM required (No CVM
required is not supported) (4) ............................................................................................. 931
2CJ.094.08 Second byte of CVR satisfied and CVM Code is no CVM required (No CVM
required is supported) (5) ................................................................................................... 932
2CJ.094.09 Second byte of CVR satisfied and CVM Code is No CVM required (No CVM
required is not supported) (5) ............................................................................................. 933
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxx
2CJ.095.00 Second byte of CVR satisfied and CVM Code not understood by the
terminal .............................................................................................................................. 934
2CJ.095.01 Second byte of CVR satisfied and CVM Code not understood by the terminal
(2) ....................................................................................................................................... 935
2CJ.095.02 Second byte of CVR satisfied and CVM Code not understood by the terminal
(3) ....................................................................................................................................... 936
2CJ.095.03 Second byte of CVR satisfied and CVM Code not understood by the terminal
(4) ....................................................................................................................................... 937
2CJ.095.04 Second byte of CVR satisfied and CVM Code not understood by the terminal
(5) ....................................................................................................................................... 938
2CJ.096.00 CVM processing succeeds ........................................................................... 939
2CJ.096.01 CVM processing succeeds (2) ...................................................................... 940
2CJ.096.02 CVM processing succeeds (3) ...................................................................... 941
2CJ.097.00 CVM processing fails and CVR indicates to proceed with next rule ............. 942
2CJ.097.01 CVM processing fails and CVR indicates to proceed with next rule (2)........ 943
2CJ.097.02 CVM processing fails and CVR indicates to proceed with next rule (3)........ 944
2CJ.098.00 CVM processing fails and no more CVRs in the CVM List ........................... 945
2CJ.099.00 CVM processing fails and CVR indicates to not proceed with next rule ....... 946
2CJ.099.01 CVM processing fails and CVR indicates to not proceed with next rule (2).. 947
2CJ.099.02 CVM processing fails and CVR indicates to not proceed with next rule (3).. 948
2CJ.100.00 Non Supported CVR condition: If unattended Cash and transaction is not
cash .................................................................................................................................... 949
2CJ.100.01 Non Supported CVR condition: If not unattended Cash and not manual cash
and not purchase with cashback, and transaction is unattended cash .............................. 950
2CJ.100.02 Non Supported CVR condition: If manual cash, and transaction is not manual
cash .................................................................................................................................... 951
2CJ.100.03 Non Supported CVR condition: If purchase with cashback, and transaction is
not purchase with cashback ............................................................................................... 952
2CJ.100.04 Non Supported CVR condition: If unattended Cash and transaction is not
cash .................................................................................................................................... 953
2CJ.100.05 Non Supported CVR condition: If manual cash, and transaction is not manual
cash .................................................................................................................................... 954
2CJ.100.06 Non Supported CVR condition for Inquiry/Transfert/Payment: If unattended
Cash ................................................................................................................................... 955
2CJ.100.07 Non Supported CVR condition for Inquiry/Transfert/Payment: If unattended
Cash ................................................................................................................................... 956
2CJ.100.08 Non Supported CVR condition: If unattended Cash and transaction is not cash
(2) ....................................................................................................................................... 957
2CJ.100.09 Non Supported CVR condition: If unattended Cash and transaction is not cash
(3) ....................................................................................................................................... 958
2CJ.100.10 Non Supported CVR condition: If unattended Cash and transaction is not cash
(4) ....................................................................................................................................... 959
2CJ.100.11 Non Supported CVR condition: If unattended Cash and transaction is not cash
(5) ....................................................................................................................................... 960
2CJ.100.12 Non Supported CVR condition: If not unattended Cash and not manual cash
and not purchase with cashback, and transaction is unattended cash (2)......................... 961
2CJ.100.13 Non Supported CVR condition: If not unattended Cash and not manual cash
and not purchase with cashback, and transaction is unattended cash (3)......................... 962
2CJ.100.14 Non Supported CVR condition: If manual cash, and transaction is not manual
cash (2) .............................................................................................................................. 963
2CJ.100.15 Non Supported CVR condition: If manual cash, and transaction is not manual
cash (3) .............................................................................................................................. 964
2CJ.100.16 Non Supported CVR condition: If manual cash, and transaction is not manual
cash (4) .............................................................................................................................. 965
2CJ.100.17 Non Supported CVR condition: If manual cash, and transaction is not manual
cash (5) .............................................................................................................................. 966
2CJ.100.18 Non Supported CVR condition: If manual cash, and transaction is not manual
cash (6) .............................................................................................................................. 967
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxxi
2CJ.100.19 Non Supported CVR condition: If manual cash, and transaction is not manual
cash (7) .............................................................................................................................. 968
2CJ.100.20 Non Supported CVR condition: If manual cash, and transaction is not manual
cash (8) .............................................................................................................................. 969
2CJ.100.21 Non Supported CVR condition: If purchase with cashback, and transaction is
not purchase with cashback (2) ......................................................................................... 970
2CJ.100.22 Non Supported CVR condition: If purchase with cashback, and transaction is
not purchase with cashback (3) ......................................................................................... 971
2CJ.100.23 Non Supported CVR condition: If purchase with cashback, and transaction is
not purchase with cashback (4) ......................................................................................... 972
2CJ.100.24 Non Supported CVR condition: If purchase with cashback, and transaction is
not purchase with cashback (5) ......................................................................................... 973
2CJ.100.25 Non Supported CVR condition: If purchase with cashback, and transaction is
not purchase with cashback (6) ......................................................................................... 974
2CJ.100.26 Non Supported CVR condition: If purchase with cashback, and transaction is
not purchase with cashback (7) ......................................................................................... 975
2CJ.100.27 Non Supported CVR condition: If purchase with cashback, and transaction is
not purchase with cashback (8) ......................................................................................... 976
2CJ.100.28 Non Supported CVR condition: If unattended Cash and transaction is not cash
(2) ....................................................................................................................................... 977
2CJ.100.29 Non Supported CVR condition: If manual cash, and transaction is not manual
cash (2) .............................................................................................................................. 978
2CJ.100.30 Non Supported CVR condition for Inquiry/Transfert/Payment: If unattended
Cash (2) ............................................................................................................................. 979
2CJ.100.31 Non Supported CVR condition for Inquiry/Transfert/Payment: If unattended
Cash (3) ............................................................................................................................. 980
2CJ.100.32 Non Supported CVR condition for Inquiry/Transfert/Payment: If unattended
Cash (2) ............................................................................................................................. 981
2CJ.100.33 Non Supported CVR condition for Inquiry/Transfert/Payment: If unattended
Cash (3) ............................................................................................................................. 982
2CJ.103.00 Offline PIN is the selected CVM and Terminal does not support offline PIN 983
2CJ.103.01 Offline PIN is the selected CVM and Terminal does not support offline PIN
(2) ....................................................................................................................................... 984
2CJ.103.02 Offline PIN is the selected CVM and Terminal does not support offline PIN
(3) ....................................................................................................................................... 985
2CJ.107.00 Offline PIN is the selected CVM and the number of remaining PIN trials is
zero .................................................................................................................................... 986
2CJ.107.01 Offline PIN is the selected CVM and the number of remaining PIN trials is zero
(2) ....................................................................................................................................... 987
2CJ.108.00 Offline PIN is the selected CVM and the offline PIN processing is
successful .......................................................................................................................... 988
2CJ.108.01 Offline PIN is the selected CVM and the offline PIN processing is successful
(2) ....................................................................................................................................... 990
2CJ.109.00 Online PIN is the selected CVM and Terminal does not support online PIN 992
2CJ.112.00 Online PIN is the selected CVM and the online PIN processing is
successful .......................................................................................................................... 993
2CJ.113.00 Signature is a required CVM and Terminal supports the signature process CVM is Set to 'unknown' When Signature is Used ............................................................. 994
2CJ.114.00 Combination CVM: success.......................................................................... 995
2CJ.114.01 Combination CVM: success (2) .................................................................... 996
2CJ.115.00 Combination CVM: failure ............................................................................. 997
2CJ.115.01 Multiple CVR entries when at least one is supported ................................... 998
2CJ.115.02 Combination CVM: failure (2) ....................................................................... 999
2CJ.115.03 Combination CVM: failure (3) ..................................................................... 1000
2CJ.115.04 Combination CVM: failure (4) ..................................................................... 1001
2CJ.116.00 Terminal Risk Management is supported in AIP......................................... 1002
2CJ.119.00 Transaction log entry with the same PAN is available and Terminal Floor Limit
is exceeded ...................................................................................................................... 1003
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxxii
2CJ.120.00 Transaction log entry with the same PAN is available and Terminal Floor Limit
is not exceeded (implied) ................................................................................................. 1004
2CJ.123.00 Transaction log is not available and Terminal Floor Limit is exceeded ...... 1005
2CJ.124.00 Transaction log is not available and Terminal Floor Limit is not exceeded
(implied) ........................................................................................................................... 1006
2CJ.127.00 Transaction log entry with the same PAN is not available and Terminal Floor
Limit is exceeded ............................................................................................................. 1007
2CJ.128.00 Transaction log entry with the same PAN is not available and Terminal Floor
Limit is not exceeded (implied)......................................................................................... 1008
2CJ.137.00 Both the Lower and the Upper Consecutive Offline Limit are present in the
ICC ................................................................................................................................... 1009
2CJ.138.00 Lower Consecutive Offline Limit is not present in the ICC.......................... 1010
2CJ.138.01 Upper Consecutive Offline Limit is not present in the ICC.......................... 1011
2CJ.139.00 GET DATA on both the ATC and the Last Online ATC Register ................ 1012
2CJ.140.00 The ATC Register is not present in the ICC ............................................... 1013
2CJ.140.01 The Last Online ATC Register is not present in the ICC - LATC > 0 .......... 1014
2CJ.140.02 The ATC Register is less than the Last online ATC ................................... 1015
2CJ.140.03 The ATC Register is equal to Last online ATC ........................................... 1016
2CJ.140.04 The ATC Register is not present in the ICC – LATC = 0 ............................ 1017
2CJ.141.00 (ATC - Last Online ATC Register) > Lower Consecutive Offline Limit ....... 1018
2CJ.142.00 (ATC - Last Online ATC Register) = Lower Consecutive Offline Limit
(implied) ........................................................................................................................... 1019
2CJ.143.00 (ATC - Last Online ATC Register) < Lower Consecutive Offline Limit
(implied) ........................................................................................................................... 1020
2CJ.144.00 (ATC - Last Online ATC Register) > Upper Consecutive Offline Limit ....... 1021
2CJ.145.00 (ATC - Last Online ATC Register) = Upper Consecutive Offline Limit
(implied) ........................................................................................................................... 1022
2CJ.146.00 (ATC - Last Online ATC Register) < Upper Consecutive Offline Limit
(implied) ........................................................................................................................... 1023
2CJ.147.00 Last Online ATC Register = 0 ..................................................................... 1024
2CJ.147.01 ATC and Last Online ATC Register = 0 ...................................................... 1025
2CJ.148.00 Terminal Risk Management completion ..................................................... 1026
2CJ.150.00 TAC Denial processing bit set to 1b ........................................................... 1027
2CJ.151.00 TAC Denial processing bit set to 0b ........................................................... 1028
2CJ.151.01 TAC Denial processing bit set to 0b (2) ...................................................... 1029
2CJ.152.00 TAC Online Processing, bit set to 1b .......................................................... 1030
2CJ.153.00 TAC Online Processing, bit set to 0b .......................................................... 1031
2CJ.154.00 TAC Default processing bit set to 1b, & terminal unable to go online......... 1032
2CJ.155.00 TAC Default processing bit set to 0b, & terminal unable to go online......... 1033
2CJ.156.00 TAC Default processing bit set to 1b, & terminal has no online capability.. 1034
2CJ.157.00 TAC Default processing bit set to 0b, & terminal has no online capability.. 1035
2CJ.157.01 Online Only device skips TAC default ........................................................ 1036
2CJ.158.00 Terminal Action Analysis & TVR and Issuer Action Code-Denial check
requests an AAC .............................................................................................................. 1037
2CJ.159.00 Terminal Action Analysis & TVR and IAC-Denial check requests a TC
(implied) ........................................................................................................................... 1038
2CJ.159.01 Terminal Action Analysis & TVR and IAC-Denial check requests an ARQC
(implied) ........................................................................................................................... 1039
2CJ.160.00 Terminal has online capability, TVR and Issuer Action Code-Online check
requests an ARQC ........................................................................................................... 1040
2CJ.160.01 Online only terminal requests an ARQC when not matching TAC-Online or
IAC-Online ........................................................................................................................ 1041
2CJ.161.00 Terminal has online capability, TVR and Online Action Codes check requests
a TC (implied)................................................................................................................... 1042
2CJ.162.00 Terminal is unable to go online, TVR and Issuer Action Code-Default check
requests an AAC .............................................................................................................. 1043
2CJ.163.00 Terminal is unable to go online, TVR and Default Action Codes check
requests a TC ................................................................................................................... 1044
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxxiii
2CJ.164.00 Terminal has not online capability, TVR and Issuer Action Code-Default check
requests an AAC .............................................................................................................. 1045
2CJ.165.00 Terminal has not online capability, TVR and Default Action Codes check
requests a TC ................................................................................................................... 1046
2CJ.166.00 IAC-Denial is not present in the ICC ........................................................... 1047
2CJ.166.01 TAC-Denial is not present in the terminal ................................................... 1048
2CJ.167.00 IAC-Online is not present in the ICC........................................................... 1049
2CJ.167.01 TAC-Online is not present in the terminal ................................................... 1050
2CJ.168.00 IAC-Default is not present in the ICC and the Terminal is unable to go
online................................................................................................................................ 1051
2CJ.168.01 TAC-Default is not present in the Terminal and the Terminal is unable to go
online................................................................................................................................ 1052
2CJ.169.00 IAC-Default is not present in the ICC and the Terminal is offline only ........ 1053
2CJ.169.02 IAC-Default is not present in the ICC and the Terminal is offline only (2) .. 1054
2CJ.170.00 Card Action Analysis function completion................................................... 1055
2CJ.175.00 Generate AC Response in a Public Key Envelope ..................................... 1056
2CJ.175.01 Generate AC Response in a Public Key Envelope ..................................... 1057
2CJ.177.00 Advice messages during Card Action Analysis (Cryptogram Information Data:
Advice required) ............................................................................................................... 1058
2CJ.178.00 Online Processing function execution......................................................... 1059
2CJ.180.00 IAD is received from the Issuer and Issuer Authentication is supported in
AIP ................................................................................................................................... 1060
2CJ.181.01 Failed Processing for EXTERNAL AUTHENTICATE ................................. 1061
2CJ.182.00 IAD is received from the Issuer and Issuer Authentication is not supported in
AIP (Second Gen AC) ...................................................................................................... 1062
2CJ.183.00 IAD is not received from the Issuer............................................................. 1063
2CJ.187.00 Issuer Script may contain several Issuer Script Commands ...................... 1064
2CJ.187.01 Issuer Script may contain several Issuer Script Commands (2) ................. 1065
2CJ.187.02 Issuer Script may contain several Issuer Script Commands (3) ................. 1066
2CJ.188.00 Issuer Script Command unknown to the terminal ....................................... 1067
2CJ.188.01 Issuer Script Command unknown to the terminal (2).................................. 1068
2CJ.188.02 Issuer Script Command unknown to the terminal (3).................................. 1069
2CJ.189.00 Issuer Script with Tag '71' execution .......................................................... 1070
2CJ.190.00 Issuer Script with Tag '72' execution .......................................................... 1071
2CJ.191.00 Issuer Script Format ................................................................................... 1072
2CJ.191.01 Issuer Script Format (2) .............................................................................. 1073
2CJ.192.00 Script Identifier in Issuer Script ................................................................... 1074
2CJ.192.01 Script Identifier in Issuer Script (2).............................................................. 1075
2CJ.193.00 Issuer Script processing ............................................................................. 1076
2CJ.193.01 Issuer Script processing (2) ........................................................................ 1078
2CJ.193.02 Issuer Script processing (3) ........................................................................ 1080
2CJ.194.00 Issuer Script Commands not BER-TLV encoded and Issuer Script tag is
'71' .................................................................................................................................... 1082
2CJ.194.01 Issuer Script Commands not BER-TLV encoded and Issuer Script tag is
'71' .................................................................................................................................... 1083
2CJ.195.00 Issuer Script Commands not BER-TLV encoded and Issuer Script tag is
'72' .................................................................................................................................... 1084
2CJ.195.01 Issuer Script Commands not BER-TLV encoded and Issuer Script tag are '71'
and '72' ............................................................................................................................. 1085
2CJ.195.02 Issuer Script Commands not BER-TLV encoded and Issuer Script tag are '71'
and '72' (2) ....................................................................................................................... 1086
2CJ.195.03 Issuer Script Commands not BER-TLV encoded and Issuer Script tag are '71'
and '72' (3) ....................................................................................................................... 1088
2CJ.195.04 Issuer Script Commands not BER-TLV encoded and Issuer Script tag are '71'
and '72' (4) ....................................................................................................................... 1090
2CJ.197.00 SW1 in the Status Code equals '90', '62', or '63' ........................................ 1092
2CJ.197.01 SW1 in the Status Code equals '90', '62', or '63' (2) ................................... 1093
2CJ.197.02 SW1 in the Status Code equals '90', '62', or '63' (3) ................................... 1094
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxxiv
2CJ.199.00 SW1 in the Status Code is different from '90', '62', or '63' and Issuer Script tag
is '71' ................................................................................................................................ 1096
2CJ.200.00 SW1 in the Status Code is different from '90', '62', or '63' and Issuer Script tag
is '72' ................................................................................................................................ 1098
2CJ.200.01 SW1 in the Status Code is different from '90', '62', or '63' and Issuer Script tag
is '72' ................................................................................................................................ 1100
2CJ.202.00 Issuer Script not processed (implied) ......................................................... 1102
2CJ.202.01 Issuer Script not sent when no Script performed ........................................ 1103
2CJ.203.00 Enhanced Combined DDA/AC failed when ICC responded with TC (1)..... 1105
2CJ.203.01 Enhanced Combined DDA/AC failed when ICC responded with TC (2)..... 1106
2CJ.203.02 Enhanced Combined DDA/AC failed when ICC responded with TC (3)..... 1108
2CJ.203.03 Enhanced Combined DDA/AC failed when ICC responded with TC (4)..... 1110
7.8
Generate AC Command coding ......................................................................... 1112
2CK.001.00 CDOL1 for the first GENERATE AC .......................................................... 1113
2CK.002.00 CDOL2 for the second GENERATE AC..................................................... 1114
2CK.003.00 CDOL requests a TC Hash Value and TDOL is present in the ICC ........... 1115
2CK.004.00 CDOL requests a TC Hash Value and TDOL is not present in the ICC ..... 1116
2CK.004.01 CDOL requests a TC Hash Value and TDOL is not present in the ICC ..... 1117
2CK.004.02 CDOL requests a TC Hash Value and TDOL is not present in the ICC (2) 1118
2CK.004.03 CDOL requests a TC Hash Value and TDOL is not present in the ICC ..... 1119
2CK.005.00 CDOL requests a TC Hash Value and neither TDOL nor default TDOL is
present ............................................................................................................................. 1120
2CK.005.01 CDOL requests a TC Hash Value and neither TDOL nor default TDOL is
present (2) ........................................................................................................................ 1121
2CK.006.00 CDOL requests a TC Hash Value during the second GENERATE AC...... 1122
2CK.007.00 Terminal requests a TC on first GENERATE AC ....................................... 1123
2CK.008.00 Terminal requests an ARQC on first GENERATE AC ............................... 1124
2CK.009.00 Terminal requests an AAC on first GENERATE AC .................................. 1125
2CK.010.00 Card responds with an ARQC on first GENERATE AC ............................. 1126
2CK.012.00 Card responds with a TC on first GENERATE AC ..................................... 1127
2CK.013.00 Card responds with an AAC on first GENERATE AC (1) ........................... 1128
2CK.013.01 Card responds with an AAC on first GENERATE AC (2) ........................... 1129
2CK.013.02 Card responds with an AAC on first GENERATE AC (2) ........................... 1130
2CK.015.00 Terminal requests an AAC on second GENERATE AC............................. 1131
2CK.016.00 Terminal requests a TC on second GENERATE AC ................................. 1132
2CK.017.00 Cryptogram at a higher level than requested (1)........................................ 1133
2CK.017.01 Cryptogram at a higher level than requested (2)........................................ 1134
2CK.018.00 Cryptogram at a higher level than requested (2)........................................ 1135
2CK.018.01 Cryptogram at a higher level than requested (3)........................................ 1136
7.9
Erroneous or Missing Data in ICC ...................................................................... 1137
2CL.001.00
2CL.001.01
2CL.001.02
2CL.002.00
2CL.002.01
2CL.003.00
2CL.004.00
2CL.005.00
2CL.006.00
2CL.006.01
2CL.006.02
2CL.006.03
2CL.007.00
2CL.008.00
2CL.009.00
Mandatory data objects missing: FCI (1) .................................................... 1138
Mandatory data objects missing: Final SELECT ........................................ 1139
Mandatory data objects missing: FCI (2) .................................................... 1140
Mandatory data objects missing: DF Name................................................ 1141
Mandatory data objects missing: DF Name (2) .......................................... 1142
Mandatory data objects missing: SFI ......................................................... 1143
Mandatory data objects missing in directory entry: ADF Name.................. 1144
Mandatory data objects missing in directory entry: Application Label ........ 1145
Mandatory data objects missing: FCI Proprietary Template....................... 1146
Mandatory data objects missing: FCI Proprietary Template (2) ................. 1147
Mandatory data objects missing: Application Label.................................... 1148
Mandatory data objects missing: Application Label.................................... 1149
Mandatory data objects missing: AFL ........................................................ 1150
Mandatory data objects missing: AIP ......................................................... 1151
Mandatory data objects missing: CDOL1 ................................................... 1152
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxxv
2CL.010.00 Mandatory data objects missing: CDOL2 ................................................... 1153
2CL.011.00 Mandatory data objects missing: PAN........................................................ 1154
2CL.012.00 Mandatory data objects missing: Application Expiration Date .................... 1155
2CL.013.00 ATC not returned by GET DATA and Both LCOL and UCOL are present . 1156
2CL.014.00 Last Online ATC Register not returned by GET DATA and Both LCOL and
UCOL are present ............................................................................................................ 1157
2CL.019.00 Issuer Public Key Certificate not present and Offline SDA is supported in
AIP ................................................................................................................................... 1158
2CL.021.00 Issuer Public Key Exponent not present and Offline SDA is supported in
AIP ................................................................................................................................... 1159
2CL.023.00 Issuer Public Key Remainder not present and Offline SDA is supported in
AIP ................................................................................................................................... 1160
2CL.023.01 Issuer Public Key Remainder not present and Offline SDA is supported in AIP
(implied) ........................................................................................................................... 1161
2CL.024.00 Issuer Public Key Remainder not present and Offline DDA is supported in
AIP ................................................................................................................................... 1162
2CL.024.01 Issuer Public Key Remainder not present and Offline DDA is supported in AIP
(2) ..................................................................................................................................... 1163
2CL.024.02 Issuer Public Key Remainder not present and Offline DDA is supported in AIP
(implied) ........................................................................................................................... 1165
2CL.024.03 Issuer Public Key Remainder not present and Offline DDA is supported in AIP
(2) (implied) ...................................................................................................................... 1166
2CL.024.08 Issuer Public Key Remainder not present and Offline DDA is supported in AIP
(9) ..................................................................................................................................... 1167
2CL.024.09 Issuer Public Key Remainder not present and Offline DDA is supported in AIP
(10) ................................................................................................................................... 1169
2CL.028.00 ICC Public Key Remainder not present and Offline DDA is supported in
AIP ................................................................................................................................... 1171
2CL.028.01 ICC Public Key Remainder not present and Offline DDA is supported in AIP
(2) ..................................................................................................................................... 1172
2CL.028.02 ICC Public Key Remainder not present and Offline DDA is supported in AIP
(implied) ........................................................................................................................... 1174
2CL.028.03 ICC Public Key Remainder not present and Offline DDA is supported in AIP
(2) (implied) ...................................................................................................................... 1175
2CL.028.07 ICC PIN Encipherment Public Key Remainder not present and Offline
Enciphered PIN is supported ........................................................................................... 1176
2CL.028.09 ICC Public Key Remainder not present and Offline DDA is supported in AIP
(10) ................................................................................................................................... 1177
2CL.028.10 ICC Public Key Remainder not present and Offline DDA is supported in AIP
(11) ................................................................................................................................... 1179
2CL.029.00 Constructed Data Objects do not parse correctly: FCI of PSE ................... 1181
2CL.029.05 Constructed Data Objects do not parse correctly: Directory Record in
Payment System Directory ............................................................................................... 1182
2CL.030.00 Constructed Data Objects do not parse correctly: Record Template ......... 1183
2CL.032.00 Constructed Data Objects do not parse correctly: FCI of ADF ................... 1184
2CL.033.00 Constructed Data Objects do not parse correctly: GPO response
template ........................................................................................................................... 1185
2CL.034.00 Constructed Data Objects do not parse correctly: GENERATE AC response
template '77' ..................................................................................................................... 1186
2CL.035.00 Constructed Data Objects do not parse correctly: INTERNAL
AUTHENTICATE response template ............................................................................... 1187
2CL.036.00 Dates are out of the range: effective date .................................................. 1188
2CL.036.01 Dates are out of the range: expiration date ................................................ 1189
2CL.037.00 Data that must be in a specific range of values but are not: SFI ................ 1190
2CL.044.00 CVM List with no Cardholder Verification Rules ......................................... 1191
2CL.045.00 Errors in CVM List ...................................................................................... 1192
2CL.047.00 AFL with an incorrect SFI ........................................................................... 1193
2CL.048.00 AFL with an incorrect starting record number............................................. 1194
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxxvi
2CL.049.00 AFL with an incorrect ending record number.............................................. 1195
2CL.050.00 AFL with an incorrect number of records participating in Offline Data
Authentication .................................................................................................................. 1196
2CL.054.00 ISO Padding: padding between Data object............................................... 1197
2CL.054.01 Padding: padding between Data object with FF ......................................... 1198
2CL.054.02 Padding: padding between Data object ...................................................... 1200
2CL.055.00 Format of Application Label and Application preferred Name are 'ans'...... 1201
2CL.056.00 Mandatory data objects missing, format 1 GENERATE AC, TC response 1202
2CL.057.00 Mandatory data objects missing, format 1 GENERATE AC, ARQC
response .......................................................................................................................... 1203
2CL.058.00 Mandatory data objects missing, format 2 GENERATE AC, TC response 1204
2CL.059.00 Mandatory data objects missing, format 2 GENERATE AC, ARQC
response .......................................................................................................................... 1205
2CL.060.00 Mandatory data objects missing, format 1 INTERNAL AUTHENTICATE
response .......................................................................................................................... 1206
2CL.061.00 Mandatory data objects missing, format 2 INTERNAL AUTHENTICATE
response .......................................................................................................................... 1207
2CL.062.00 Incorrectly formatted PAN .......................................................................... 1208
2CL.063.00 Incorrectly formatted Data .......................................................................... 1210
2CL.064.00 Incorrectly Public Key ................................................................................. 1212
2CL.065.00 Incorrectly formatted Data .......................................................................... 1214
7.10
Terminal General Requirements ..................................................................... 1218
2CM.001.00 Merchant-controlled Terminal Provides Amount ....................................... 1219
2CM.001.01 Merchant-controlled Terminal Provides Amount (2) .................................. 1220
2CM.002.00 Merchant-controlled Terminal Obtains Amount if Not Available ................ 1221
2CM.002.01 Merchant-controlled Terminal Obtains Amount if Not Available (2)........... 1222
2CM.003.00 PDOL Requests Amount, Authorized & Amount, Other ............................ 1223
2CM.004.00 Online Only Terminal Not Supporting Data Authentication Sets Bit .......... 1224
2CM.006.00 Card and Terminal Application Version Numbers are different ................. 1225
2CM.009.00 Terminal Recognition of CVM Codes ('No CVM required' supported) - CVM is
Set When no CVM is Required ........................................................................................ 1226
2CM.009.05 Terminal Recognition of CVM Codes ('No CVM required' not supported). 1227
2CM.010.00 Terminal Recognition of CVM Codes ('Fail CVM processing') - CVM is Set
When CVM is 'Fail CVM Processing' ............................................................................... 1228
2CM.011.00 Supported CVM ......................................................................................... 1229
2CM.013.00 PIN Try Counter Not Retrievable by ICC ................................................... 1230
2CM.013.01 PIN Try Counter Not Retrievable by ICC (2) ............................................. 1231
2CM.016.00 Terminal Prompt for PIN Entry (PIN Try Counter >0) ................................ 1232
2CM.016.01 Terminal Prompt for PIN Entry (PIN Try Counter >0) (2) .......................... 1233
2CM.018.00 Offline PIN Not Successful ........................................................................ 1234
2CM.018.01 Offline PIN Not Successful (2) ................................................................... 1235
2CM.020.00 Online PIN When PIN Try Limit is Exceeded and Terminal Supports GET
DATA for PIN Try Counter ............................................................................................... 1236
2CM.020.01 Online PIN When PIN Try Limit is Exceeded and the Terminal does not
support GET DATA for PIN Try Counter .......................................................................... 1237
2CM.022.00 TVR is Set When PIN Entry is bypassed at Attended Terminal ................ 1238
2CM.022.01 TVR is Set When PIN Entry is bypassed at Unattended Terminal (2)....... 1239
2CM.022.02 TVR is Set When PIN Entry is bypassed at Attended Terminal (2) ........... 1240
2CM.022.03 TVR is Set When PIN Entry is bypassed at Attended Terminal (3) ........... 1241
2CM.022.04 TVR is Set When PIN Entry is bypassed at Unattended Terminal (2)....... 1242
2CM.022.05 TVR is Set When PIN Entry is bypassed at Unattended Terminal (3)....... 1243
2CM.023.00 CVM unsuccessful When PIN Entry is bypassed at Attended Terminal.... 1244
2CM.023.01 CVM unsuccessful When PIN Entry is bypassed at Attended Terminal
(2) ..................................................................................................................................... 1245
2CM.023.02 CVM unsuccessful When PIN Entry is bypassed at Attended Terminal
(3) ..................................................................................................................................... 1246
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxxvii
2CM.023.03 CVM unsuccessful When PIN Entry is bypassed at Attended Terminal
(4) ..................................................................................................................................... 1247
2CM.023.04 CVM unsuccessful When PIN Entry is bypassed at Attended Terminal
(5) ..................................................................................................................................... 1248
2CM.023.05 CVM unsuccessful When PIN Entry is bypassed at Attended Terminal
(6) ..................................................................................................................................... 1249
2CM.024.00 PIN Entry bypass affected all PIN methods............................................... 1250
2CM.024.01 PIN Entry bypass does not affected all PIN methods ................................ 1251
2CM.024.02 PIN Entry bypass affected all PIN methods (2) ......................................... 1252
2CM.024.03 PIN Entry bypass does not affected all PIN methods (2) .......................... 1253
2CM.025.00 Terminal Prints Receipt With Line for Cardholder Signature ..................... 1255
2CM.028.00 CVM Results Set With Method Code and Condition Code of Last CVM
Performed ........................................................................................................................ 1256
2CM.028.01 CVM Results Set With Method Code and Condition Code of Last CVM
Performed (2) ................................................................................................................... 1257
2CM.028.02 CVM Results Set With Method Code and Condition Code of Last CVM
Performed (3) ................................................................................................................... 1258
2CM.028.03 CVM Results Set With Method Code and Condition Code of Last CVM
Performed (4) ................................................................................................................... 1259
2CM.028.04 CVM Results Set With Method Code and Condition Code of Last CVM
Performed (5) ................................................................................................................... 1260
2CM.028.05 CVM Results Set With Last CVM Performed and side TVR bits remain to
zero (6) ............................................................................................................................. 1261
2CM.030.00 CVM Result when no CVM performed ...................................................... 1263
2CM.030.01 CVM Result when no CVM performed ...................................................... 1264
2CM.030.02 CVM Result when no CVM performed ...................................................... 1265
2CM.031.00 Terminal Checks Presence of Application Selected .................................. 1266
2CM.032.00 TVR Set if Match is Found in Exception File ............................................. 1267
2CM.033.00 Authorization Response Code Set When Terminal Accepts Transaction
Offline ............................................................................................................................... 1268
2CM.034.00 Authorization Response Code Set When Terminal Declines Transaction
Offline ............................................................................................................................... 1269
2CM.035.00 Authorization Response Code Not Set When Terminal Opts To Transmit
Transaction Online ........................................................................................................... 1270
2CM.036.00 Terminal Completes Transaction When Card Indicated Approval............. 1271
2CM.036.01 Terminal Completes Transaction When Card Indicated Approval (2) ....... 1272
2CM.038.00 Terminal Transmits Auth. or Financial Transaction Request Message ..... 1273
2CM.040.00 Advice is Requested by Card and is Supported by the Terminal and
transaction is captured ..................................................................................................... 1274
2CM.042.00 Terminal Terminates Transaction if Card Indicates 'Service Not Allowed'
(Cryptogram Information Data: Service Not allowed)....................................................... 1275
2CM.042.01 Terminal Terminates Transaction if Card Indicates 'Service Not Allowed'
(Cryptogram Information Data: Service Not allowed) (2) ................................................. 1276
2CM.042.06 Combined DDA/AC Generation failed and ICC returned an ARQC .......... 1277
2CM.042.07 Online Capable Terminal Terminates Transaction If Card Indicates ‘Service
Not Allowed’ (Cryptogram Information Data: Service Not Allowed) ................................. 1278
2CM.042.08 Combined DDA/AC Generation failed and ICC returned an ARQC (2) ..... 1279
2CM.043.00 Terminal Decides To Accept or Decline Transaction and Issues 2nd
GENERATE AC ............................................................................................................... 1280
2CM.044.00 Authorization Response Code is 'Online Approved' .................................. 1281
2CM.045.00 Terminal Support of Issuer Scripts in Authorization or Financial Transaction
Response ......................................................................................................................... 1282
2CM.045.01 Terminal Support of Issuer Scripts in Authorization or Financial Transaction
Response (2).................................................................................................................... 1283
2CM.045.02 Terminal Support of Issuer Scripts in Authorization or Financial Transaction
Response (2).................................................................................................................... 1284
2CM.048.00 Terminal Reporting of Script Identifier ....................................................... 1285
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxxviii
2CM.052.00 Terminal Creates an Advice When No Message is Created for
Transaction ...................................................................................................................... 1287
2CM.055.00 Terminal Supporting DDA Shall Support SDA........................................... 1288
2CM.055.01 Terminal Supporting CDA Shall Support SDA........................................... 1289
2CM.056.00 Offline Only Terminal Shall Support SDA .................................................. 1290
2CM.057.00 Offline Terminal With Online Capability Shall Support SDA ...................... 1291
2CM.058.00 Offline Only Terminal Shall Support Terminal Risk Management ............. 1292
2CM.059.00 Offline Terminal With Online Capability Shall Support Terminal Risk
Management .................................................................................................................... 1293
2CM.060.00 Financial Institution Terminal Supports TRM ............................................. 1294
2CM.061.00 Merchant Controlled Terminal Supports TRM ........................................... 1295
2CM.062.00 Terminal Displays Amount of Transaction ................................................. 1296
2CM.063.00 Cashback Amount is Transmitted in the Amount, Other Data Object ....... 1297
2CM.064.00 Purchase and Cashback Transmitted in Amount Authorised .................... 1298
2CM.066.00 Authorised Amount Is Expressed With Implicit Decimal Point................... 1299
2CM.067.00 Other Amount Is Expressed With Implicit Decimal Point ........................... 1300
2CM.074.00 Terminal Displays Message To Attendant When Issuer Requests Voice
Referral ............................................................................................................................ 1301
2CM.075.00 Data Displayed or Printed to Perform Referral initiated by issuer ............. 1302
2CM.076.00 Messages Displayed Requesting Attendant to Indicate Approval or Denial of
a Referral initiated by issuer............................................................................................. 1303
2CM.077.00 Authorization Response Code when Referral is initiated by Issuer ........... 1304
2CM.078.00 Terminal Issues Second GENERATE AC ................................................. 1305
2CM.079.00 TVR Set When Merchant Forces Transaction Online ............................... 1306
2CM.080.00 Attendant forces Approval of the Transaction ........................................... 1307
2CM.081.00 Authorization Response Code when acceptance is forced ....................... 1308
2CM.082.00 Terminal Sets Indicator When Attendant forces Approval of the
Transaction ...................................................................................................................... 1309
2CM.083.00 Terminal Maintains Transaction Sequence Counter ................................. 1310
2CM.086.00 Terminal Reading of Service Code on Magnetic Stripe............................. 1311
2CM.087.00 Terminal Reading of Service Code on Magnetic Stripe............................. 1312
2CM.091.00 POS Entry Mode Code Read .................................................................... 1313
2CM.092.00 Calculation of Dates Associated With Static Data Authentication ............. 1314
2CM.093.00 Calculation of Dates Associated With Processing Restrictions ................. 1316
2CM.094.00 Calculation, Storage, and Display Date-Dependant Fields For Year 2000
+ ....................................................................................................................................... 1317
2CM.094.01 Calculation, Storage, and Display Date-Dependant Fields For Year 2000
+ ....................................................................................................................................... 1318
2CM.095.00 Processing the Year .................................................................................. 1319
2CM.102.00 Display For Attendant for Attended Terminal ............................................ 1320
2CM.103.00 Display of Alphanumeric Characters ......................................................... 1321
2CM.105.00 Protection of Captured Transactions and Advices Stored ......................... 1322
2CM.106.00 Clock With Local Date and Time ............................................................... 1323
2CM.109.00 Magnetic Stripe Reader Using Full Track 1 and/or Track 2....................... 1324
2CM.129.00 PIN Pad Shall Support Entry of 4-12 Digit PIN .......................................... 1325
2CM.129.01 PIN Pad Shall Support Entry of 4-12 Digit PIN (2) .................................... 1326
2CM.129.02 PIN Pad Shall Support Entry of 4-12 Digit PIN (online PIN) ...................... 1327
2CM.130.00 Display of Indication of Entry on PIN Pad - Protection of Values of Entered
PIN ................................................................................................................................... 1328
2CM.130.01 Display of Indication of Entry on PIN Pad - Protection of Values of Entered
PIN (2) .............................................................................................................................. 1329
2CM.130.02 Display of Indication of Entry on PIN Pad - Protection of Values of Entered
PIN (3) .............................................................................................................................. 1330
2CM.137.00 Protection of PIN During Online PIN Verification....................................... 1331
7.11
Software Architecture ...................................................................................... 1332
2CN.004.00 Data Elements are Initialised in Terminal .................................................. 1333
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xxxix
2CN.012.00 Language Support by Terminal.................................................................. 1336
2CN.016.00 Terminal Displays Error Message if Verification Process fails ................... 1337
7.12
Cardholder and Merchant Interface ................................................................. 1338
2CO.001.00 Terminal Support of Local Language......................................................... 1339
2CO.002.00 Terminal Display of Messages in Local Language .................................... 1340
2CO.003.00 Terminal Support of Relevant Character Set (1) ....................................... 1341
2CO.003.01 Terminal Support of Relevant Character Set (2) ....................................... 1342
2CO.005.00 Terminal uses language With Highest Preference .................................... 1343
2CO.006.00 Terminal Allows Cardholder to Select Language....................................... 1344
2CO.006.01 Terminal Allows Cardholder to Select Language (2) ................................. 1345
2CO.006.02 Terminal use local language ...................................................................... 1346
2CO.006.03 Terminal use local language ...................................................................... 1347
2CO.008.00 Terminal Displays Message in Supported Language ................................ 1348
2CO.008.01 Terminal Displays Message in Supported Language ................................ 1349
2CO.011.00 Terminal Support of Explicit Selection ....................................................... 1350
2CO.013.00 Terminal Creates a List of Applications Supported (1) .............................. 1351
2CO.014.00 Terminal Creates a List of Applications Supported (2) .............................. 1352
2CO.015.05 Terminal Presents Application List ............................................................ 1353
2CO.016.00 Terminal Selects Application With Next Highest priority ............................ 1354
2CO.017.00 Application Used Identified on Receipt ...................................................... 1356
2CO.019.00 Authorization Message Used ..................................................................... 1357
2CO.020.00 Financial Transaction Message Used........................................................ 1358
2CO.021.00 Offline Advice message Conveyed ............................................................ 1359
2CO.022.00 Online Advice message transmitted .......................................................... 1360
2CO.023.00 Reversal Used ........................................................................................... 1361
2CO.025.00 Terminal Issues a 2nd GENERATE AC Command When Unable to Go
Online (1) ......................................................................................................................... 1362
2CO.026.00 Terminal Issues a 2nd GENERATE AC Command When Unable to Go
Online (2) ......................................................................................................................... 1363
2CO.026.01 Terminal Issues a 2nd GENERATE AC Command When Unable to Go
Online (3) ......................................................................................................................... 1364
2CO.026.02 Terminal Issues a 2nd GENERATE AC Command When Unable to Go
Online (4) ......................................................................................................................... 1365
2CO.026.03 Terminal Issues a 2nd GENERATE AC Command When Unable to Go
Online (5) ......................................................................................................................... 1366
2CO.028.00 Terminal Continues Processing Based on Authorization Response Code 1367
2CO.028.01 Terminal Continues Processing Based on Authorization Response Code 1368
2CO.030.00 Terminal Issues a 2nd GENERATE AC Command (1).............................. 1369
2CO.031.00 Terminal Issues a 2nd GENERATE AC Command (2).............................. 1370
2CO.032.00 Terminal Sends Reversal Message ........................................................... 1371
2CO.033.00 Terminal Creates Financial Record ........................................................... 1372
2CO.034.00 Terminal Terminates Processing of Issuer Script ...................................... 1373
2CO.034.01 Terminal Terminates Processing of Issuer Script (2)................................. 1374
2CO.034.02 Terminal Terminates Processing of Issuer Script exceeding device limit
(1) ..................................................................................................................................... 1375
2CO.034.03 Terminal Terminates Processing of Issuer Script exceeding device limit
(2) ..................................................................................................................................... 1376
2CO.034.04 Terminal Terminates Processing of Issuer Script (3)................................. 1377
2CO.035.00 Terminal Reports in Issuer Script results ................................................... 1378
2CO.035.01 Terminal Reports in Issuer Script results (2) ............................................. 1379
2CO.035.02 Terminal Reports in Issuer Script results (3) ............................................. 1380
2CO.035.03 Terminal Reports in Issuer Script results (4) ............................................. 1381
2CO.035.04 Terminal Reports in Issuer Script results (5) ............................................. 1382
2CO.036.00 Terminal Continues Processing any Subsequent Issuer Script ................. 1384
2CO.036.01 Terminal Continues Processing any Subsequent Issuer Script (2) ........... 1385
2CO.036.02 Terminal Continues Processing any Subsequent Issuer Script (2) ........... 1386
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xl
2CO.037.00 All data in the Messages are originated from chip ..................................... 1387
2CO.038.00 All data in the Messages are originated from chip (2) ............................... 1388
7.13
Coding of Terminal Data Element ................................................................... 1389
2CP.001.00
2CP.002.00
2CP.003.00
2CP.004.00
7.14
Terminal Type ............................................................................................ 1390
Terminal Capabilities.................................................................................. 1391
Additional Terminal Capabilities ................................................................. 1392
Account Type ............................................................................................. 1394
Command Syntax ............................................................................................ 1395
2CS.001.00 Mandatory Command Set .......................................................................... 1396
2CS.002.00 Select Next Command ............................................................................... 1398
2CS.003.00 Internal Authenticate Command................................................................. 1400
2CS.004.00 Verify Command ........................................................................................ 1402
2CS.005.00 Get Challenge command ........................................................................... 1405
2CS.006.00 Get Data command .................................................................................... 1408
2CS.007.00 External Authenticate command ................................................................ 1411
2CS.014.00 Combined functions on Transaction Flow: Offline PIN and Advice with PIN Try
Limit exceeded ................................................................................................................. 1414
2CS.014.01 Combined functions on Transaction Flow: Offline PIN and Advice with PIN Try
Limit exceeded (2)............................................................................................................ 1415
2CS.014.02 Combined functions on Transaction Flow: Offline PIN and Advice with PIN Try
Limit exceeded (3)............................................................................................................ 1416
2CS.014.03 Combined functions on Transaction Flow: Offline PIN and Advice with PIN Try
Limit exceeded (4)............................................................................................................ 1417
2CS.015.00 Combined functions on Transaction Flow: SDA and Record length coded on 1
or 2 bytes ......................................................................................................................... 1418
2CS.015.01 Combined functions on Transaction Flow: SDA and Record length of
proprietary file coded on 1 or 2 bytes ............................................................................... 1420
2CS.015.02 Combined functions on Transaction Flow: DDA and Record length coded on 1
or 2 bytes ......................................................................................................................... 1422
2CS.015.03 Combined functions on Transaction Flow: DDA and Record length of
proprietary file coded on 1 or 2 bytes ............................................................................... 1424
2CS.015.04 Combined functions on Transaction Flow: CDA and Record length coded on 1
or 2 bytes ......................................................................................................................... 1426
2CS.015.05 Combined functions on Transaction Flow: CDA and Record length of
proprietary file coded on 1 or 2 bytes ............................................................................... 1428
2CS.016.00 Combined Test: SDA Tag List and AFL in Static Data Authentication ....... 1430
2CS.016.03 Combined Test: SDA Tag List and AFL in Dynamic Data Authentication .. 1432
2CS.016.05 Combined Test: SDA Tag List and AFL in Combined Data
Authentication .................................................................................................................. 1434
7.15
Combined Test ................................................................................................ 1436
2CT.008.00 Combined functions on Transaction Flow: SDA and PIN Encryption ......... 1437
2CT.009.00 Combined functions on Transaction Flow: DDA and PIN Encryption......... 1438
2CT.009.01 Combined functions on Transaction Flow: DDA and PIN Encryption (2) ... 1439
2CT.010.00 Combined functions on Transaction Flow: CDA and PIN Encryption......... 1440
2CT.010.01 Combined functions on Transaction Flow: CDA and PIN Encryption......... 1441
2CT.010.02 Combined functions on Transaction Flow: CDA and PIN Encryption (3) ... 1443
2CT.010.03 Combined functions on Transaction Flow: CDA and PIN Encryption (4) ... 1444
2CT.011.00 Combined functions on Transaction Flow: Issuer Authentication and Script
Processing ....................................................................................................................... 1446
2CT.011.01 Combined functions on Transaction Flow: Issuer Authentication and Script
Processing (2) .................................................................................................................. 1447
2CT.011.02 Combined functions on Transaction Flow: Issuer Authentication and Script
Processing (3) .................................................................................................................. 1448
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xli
2CT.011.03 Combined functions on Transaction Flow: Issuer Authentication and Script
Processing (4) .................................................................................................................. 1449
2CT.011.04 Combined functions on Transaction Flow: Issuer Authentication and Script
Processing (5) .................................................................................................................. 1451
2CT.012.00 Combined functions on Transaction Flow: Advice and Issuer
Authentication .................................................................................................................. 1453
2CT.012.01 Combined functions on Transaction Flow: Advice and Issuer Authentication
(2) ..................................................................................................................................... 1454
2CT.013.00 Combined functions on Transaction Flow: Advice on first and second
Generate AC .................................................................................................................... 1455
2CT.013.01 Combined functions on Transaction Flow: Advice on first and second
Generate AC (2) ............................................................................................................... 1456
2CT.017.00 Combined Test: Get Processing and Generate AC with different response
format ............................................................................................................................... 1457
2CT.017.01 Combined Test: Get Processing and Generate AC with different response
format (2).......................................................................................................................... 1458
2CT.018.00 Combined Test: Get Processing and Generate AC with different response
format, CDA ..................................................................................................................... 1459
2CT.018.01 Combined Test: Get Processing and Generate AC with different response
format, CDA (2) ................................................................................................................ 1460
2CT.019.00 Combined Test: Get Processing, Internal Authenticate and Generate AC with
different response format ................................................................................................. 1461
2CT.019.01 Combined Test: Get Processing, Internal Authenticate and Generate AC with
different response format (2) ............................................................................................ 1462
2CT.020.00 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Plaintext
PIN, Issuer Authentication, Generate AC Format 1, Script .............................................. 1463
2CT.020.01 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Plaintext
PIN, Issuer Authentication, Generate AC Format 1 ......................................................... 1464
2CT.021.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA,
Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script ............................... 1465
2CT.021.01 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA,
Plaintext PIN, Issuer Authentication, Generate AC Format 1 .......................................... 1467
2CT.022.00 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, ‘, Issuer
Authentication, Generate AC Format 1, Script ................................................................. 1468
2CT.022.01 Combined functions on Transaction Flow: PSE, PDOL empty, SDA,
Signature, Issuer Authentication, Generate AC Format 1 ................................................ 1469
2CT.023.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA,
Signature, Issuer Authentication, Generate AC Format 1, Script..................................... 1470
2CT.023.01 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA,
Signature, Issuer Authentication, Generate AC Format 1, Script (2) ............................... 1471
2CT.024.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Paper
Signature, No Issuer Authentication, Generate AC Format 1, Script ............................... 1472
2CT.024.01 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA,
Signature, No Issuer Authentication, Generate AC Format 1, Script (2) .......................... 1473
2CT.025.00 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Paper
Signature, No Issuer Authentication, Generate AC Format 1, Script ............................... 1474
2CT.025.01 Combined functions on Transaction Flow: PSE, PDOL empty, SDA,
Signature, No Issuer Authentication, Generate AC Format 1, Script (2) .......................... 1475
2CT.026.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA,
Plaintext PIN, No Issuer Authentication, Generate AC Format 2, Script .......................... 1476
2CT.026.01 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA,
Plaintext PIN, No Issuer Authentication, Generate AC Format 2, Script (2) .................... 1477
2CT.027.00 Combined functions on Transaction Flow: No PSE, Get Processing Option
Format 2, SDA, Plaintext PIN, No Issuer Authentication, Generate AC Format 2, Script 1478
2CT.027.01 Combined functions on Transaction Flow: No PSE, Get Processing Option
Format 2, SDA, Plaintext PIN, No Issuer Authentication, Generate AC Format 2, Script
(2) ..................................................................................................................................... 1479
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page xlii
2CT.028.00 Combined functions on Transaction Flow: No PSE, Get Processing Option
Format 1, SDA, Signature, No Issuer Authentication, Generate AC Format 1, Script (2) 1480
2CT.028.01 Combined functions on Transaction Flow: No PSE, Get Processing Option
Format 1, SDA, Signature, No Issuer Authentication, Generate AC Format 1, Script (2) 1481
2CT.029.00 Combined functions on Transaction Flow: No PSE, Get Processing Option
Format 1, TRM, SDA, DDA, Signature, No Issuer Authentication, Generate AC Format 1,
Script ................................................................................................................................ 1482
2CT.029.01 Combined functions on Transaction Flow: No PSE, Get Processing Option
Format 1, TRM, SDA, DDA, Signature, No Issuer Authentication, Generate AC Format
1 ....................................................................................................................................... 1484
2CT.030.00 Combined functions on Transaction Flow: No PSE, PDOL Empty, SDA, DDA,
Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script (2) .......................... 1485
2CT.030.01 Combined functions on Transaction Flow: No PSE, PDOL Empty, SDA, DDA,
Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script (2) .......................... 1487
2CT.031.00 Combined functions on Transaction Flow: PSE, Get Processing Option
Format 2, SDA, DDA, Enciphered PIN, Issuer Authentication, Generate AC Format 2,
Script ................................................................................................................................ 1488
2CT.031.01 Combined functions on Transaction Flow: PSE, Get Processing Option
Format 2, SDA, DDA, Enciphered PIN, Issuer Authentication, Generate AC Format 2, Script
(2) ..................................................................................................................................... 1490
2CT.032.00 Combined functions on Transaction Flow: No PSE, Get Processing Option
Format 2, TRM, SDA, DDA, CDA, Enciphered PIN, Issuer Authentication, Generate AC
Format 2, Script................................................................................................................ 1491
2CT.032.01 Combined functions on Transaction Flow: No PSE, Get Processing Option
Format 2, TRM, SDA, DDA, CDA, Enciphered PIN, Issuer Authentication, Generate AC
Format 2, Script (2) .......................................................................................................... 1493
2CT.033.00 Combined functions on Transaction Flow: No PSE, Get Processing Option
Format 2, SDA, DDA, CDA, Signature, No Issuer Authentication, Generate AC Format 2,
Script (2)........................................................................................................................... 1495
2CT.033.01 Combined functions on Transaction Flow: No PSE, Get Processing Option
Format 2, SDA, DDA, CDA, Signature, No Issuer Authentication, Generate AC Format 2,
Script (2)........................................................................................................................... 1497
2CT.034.00 Combined functions on Transaction Flow: Proprietary Data and EMV
data .................................................................................................................................. 1498
2CT.035.00 Combined functions on Transaction Flow: SDA, Keys remainder not present,
Proprietary Data and EMV data ....................................................................................... 1499
2CT.036.00 Combined functions on Transaction Flow: DDA, Keys remainder not present,
Proprietary Data and EMV data ....................................................................................... 1500
2CT.037.00 Combined functions on Transaction Flow: CDA, Keys remainder not present,
Proprietary Data and EMV data ....................................................................................... 1501
2CT.038.00 Combined functions on Transaction Flow: LCOLL = 00, UCOLL= FF
Proprietary Data and EMV data ....................................................................................... 1503
2CT.038.01 Combined functions on Transaction Flow: LCOLL = 00, UCOLL= FF
Proprietary Data and EMV data ....................................................................................... 1504
2CT.039.00 ICC supporting DDA Only .......................................................................... 1505
2CT.040.00 CPA compliant profile ................................................................................. 1506
2CT.040.01 CPA compliant profile (2) ........................................................................... 1507
2CT.040.02 CPA compliant profile (3) ........................................................................... 1508
2CT.040.03 CPA compliant profile (4) ........................................................................... 1509
8
Annex A: Test cases applicable depending on the terminal options.................. 1511
< End Of The Document>................................................................................................ 1545
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
1
Page 1
Scope
EMV Integrated Circuit Card Specifications for Payment Systems is now divided in 4 books:
•
•
•
•
Book 1: Application Independent ICC to Terminal Interface Requirements
Book 2: Security and Key Management
Book 3: Application Specification
Book 4: Cardholder, Attendant, and Acquirer Interface Requirements
The Book 1 (Part II) and Book 2 define the complete flow of a transaction between an
Integrated Circuit Card (ICC) and a terminal, from the selection of an application in the ICC to
the completion of the transaction.
Book 3 defines the format of ICC commands used during the transaction flow between the
ICC and terminal. Also defined is the transaction flow and associated data for an application
compliant with the EMV specifications.
Finally Book 4 defines the characteristics of a Terminal that supports an ICC conforming to
the two previous specifications mentioned.
The present document, 'EMVCo Terminal Type Approval - Level 2 Test Cases’, describes
a set of test cases which when applied to the terminals, are designed to determine whether
the terminal meets the requirements stated in EMV Integrated Circuit Card Specifications for
Payment Systems. Test cases are defined for unitary tests that are performed without
presence of a valid EMV payment application and functional testing dependent of the presence
of the EMV payment application.
Terminal/host protocol (if present) is not tested since requirements for terminal communication
with external components is not defined by EMV specifications.
If any special conditions are required for a specific test case, these conditions are described
in the test case.
The intended audience for this document are EMVCo accredited laboratories, EMV application
providers, acquiring members or merchants. Although acquiring members and merchants
may reference this document, type approval testing is oriented toward EMV application
providers.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
2
Page 2
Referenced Documents
[N1]
EMV Integrated Circuit Card Specifications for Version 4.3 - November
Payment Systems – Book 1 – Application Independent 2011
ICC to Terminal Interface Requirements
[N2]
EMV Integrated Circuit Card Specifications for Version 4.3 - November
Payment Systems - Book 2 - Security and Key 2011
Management
[N3]
EMV Integrated Circuit Card Specifications for Version 4.3 - November
Payment Systems - Book 3 - Application Specification 2011
[N4]
EMV Integrated Circuit Card Specifications for Version 4.3 - November
Payment Systems - Book 4 - Cardholder, Attendant, 2011
and Acquirer Interface Requirements
AN xx
All published Application Note bulletins
Bulletins 1 to 41
SU xx
All published Specification Update bulletins
Bulletins 1 to 164
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
3
Page 3
Abbreviations and Notations
APDU
Application Protocol Data Unit
ATR
Answer to Reset
C-APDU
Command APDU
CLA
Class Byte of the Command Message
EMV
A term referring to certain technical specifications developed and
maintained by EMVCo and/or technologies conforming to such specification
ICC
Integrated Circuit Card
IFD
Interface Device
INS
Instruction Byte of Command Message
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 or Remaining in the ICC (as Determined by
the ICC) to be Returned in Response to the Case 2 or 4 Command
Received by the ICC
LEN
Length
Lr
Length of Response Data Field
l.s.
Least Significant
LT
Lower Tester
m.s.
Most Significant
NCA
Length of the Certification Authority Public Key Modulus
NI
Length of the Issuer Public Key Modulus
NIC
Length of the ICC Public Key Modulus
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
P1
Parameter 1
P2
Parameter 2
P3
Parameter 3
PI
Issuer Public Key
PIC
ICC Public Key
R-APDU
Response APDU
RST
Reset
SCA
Certification Authority Private Key
SI
Issuer Private Key
SIC
ICC Private Key
SW1
Status Word One
SW2
Status Word Two
Page 4
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
4
Page 5
Global Glossary
Acquirer - A financial institution that supports merchants by providing services for processing
payment card transactions.
Acquirer System - A logical entity that provides electronic commerce services to the
merchants in support of the acquirer and interfaces to the acquirer to support the authorization
and capture of electronic commerce transactions.
Answer to Reset (ATR) - A string of bytes sent by the integrated circuit card (ICC) in response
to the reset by the terminal. These bytes convey information to the terminal that define certain
characteristics of the communication to be established between the ICC and the terminal.
Application - The application protocol between the card and the terminal and its related set
of data.
Application Protocol Data Unit (APDU) - A message sent from the interface device (IFD) to
the card or conversely. It may contain either a command message or a response message.
Asymmetric Cryptographic Technique - A cryptographic technique that uses two related
transformations, a public transformation (defined by the public key) and a private
transformation (defined by the private key). The two transformations have the property that,
given the public transformation, it is computationally infeasible to derive the private
transformation.
Authentication- The provision of assurance of the claimed identity of an entity [ISO/IEC
10181-2: 1996].
Authorization- The process by which a properly appointed person or persons grants
permission to perform some action on behalf of an organization. This process assesses
transaction risk, confirms that a given transaction does not raise the account holder's debt
above the account's credit limit, and reserves the specified amount of credit. (When a
merchant obtains authorization, payment for the authorized amount is guaranteed - provided
that the merchant followed the rules associated with the authorization process.)
Authorization Reversal - A transaction sent when a previous authorization needs to be
canceled (a full reversal) or decreased (a partial reversal). A full reversal will be used when
the transaction can not be completed, such as when the cardholder cancels the order or the
merchant discovers that the goods are no longer available, as when discontinued. A partial
reversal will be used when the authorization was for the entire order and some of the goods
cannot be shipped, resulting in a split shipment.
Block - A succession of characters comprising two or three fields defined as prologue field,
information field, and epilogue field.
Byte - 8 bits.
Card - A payment card as defined by a payment system.
Cardholder - An authorized holder of a payment card supported by an issuer.
Cardholder System - The combination of hardware and software required to interact with the
cardholder, his or her IC Card, and a SET Merchant Server in order to participate in EMV chip
electronic commerce.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 6
Certificate: The public key and identity of an entity together with some other information,
rendered unforgeable by signing with the secret key of the certification authority which issued
that certificate.
Certificate Revocation: The process of revoking an otherwise valid certificate by the entity
that issued that certificate.
Certification Authority: A centre trusted to create and assign public key certificates which
provide evidence linking a public key and other relevant information to its owner.
Certification Authority - Trusted third party that establishes a proof that links a public key
and other relevant information to its owner.
Ciphertext - Enciphered information.
Cold Reset - The reset of the ICC that occurs when the supply voltage (VCC) and other
signals to the ICC are raised from the inactive state and the reset (RST) signal is applied.
Command - A message sent by the terminal to the ICC that initiates an action and solicits a
response from the ICC.
Concatenation - Two elements are concatenated by appending the bytes from the second
element to the end of the first. Bytes from each element are represented in the resulting string
in the same sequence in which they were presented to the terminal by the ICC, that is, most
significant byte first. Within each byte bits are ordered from most significant bit to least
significant. A list of elements or objects may be concatenated by concatenating the first pair
to form a new element, using that as the first element to concatenate with the next in the list,
and so on.
Conformance - Meeting all the requirements (and also any optional requirements) that the
interface module (IFM) provider instituted of that specification.
Contact - A conducting element ensuring galvanic continuity between integrated circuit(s) and
external interfacing equipment.
Contact Interface - The area where a contact if the interface device (IFD) physically touches
a contact on the integrated circuit card (ICC) allowing an electrical current to flow between the
contacts.
Cryptogram - Result of a cryptographic operation.
Cryptography- The practice of digitally "scrambling" a message using a secret key or keys.
These keys are used to unscramble or decrypt the message.
Cryptographic Algorithm - An algorithm that transforms data in order to hide or reveal its
information content.
Data Integrity - The property that data has not been altered or destroyed in an unauthorised
manner
Data Key (KD): Cryptographic key used for the encipherment, decipherment or authentication
of data. (ISO 8908)
Decipherment: Process of transforming cipher text into plain text - the reversal of a
corresponding encipherment.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 7
Declaration of conformity - Written statement by an interface module (IFM) provider claiming
that their production of a specific IFM type is in conformance with all related specifications, as
defined by EMVCo.
Digital Envelope - A cryptographic technique to encrypt data and send the encryption key
along with the data. Generally, a symmetric algorithm is used to encrypt the data and an
asymmetric algorithm is used to encrypt the encryption key.
Digital Signature - An asymmetric cryptographic transformation of data that allows the
recipient of the data to prove the origin and integrity of the data, and protect the sender and
the recipient of the data against forgery by third parties, and the sender against forgery by the
recipient.
Electronic Commerce - The exchange of goods and services for payment between the
cardholder and merchant when some or all of the transaction is performed via electronic
communication.
Electronic Commerce Access Device - The combination of hardware and software required
to interact with the cardholder, the ICC, and an electronic commerce system in order to
conduct EMV-based electronic commerce purchases.
Embossing - Characters raised in relief from the front surface of a card.
EMVCo - The limited liability company organized to facilitate worldwide interoperability and
acceptance of secure payment transactions.
Encipherment - The reversible transformation of data by a cryptographic algorithm to produce
ciphertext.
Expiry Date: Date after which a financial instrument or agreement ceases to be valid.
External operating conditions (EOC) - In addition to the implementation conformance
statement (ICS), this document describes the setup and handling of the system under test
(SUT) before and during the type approval tests, and describes the environmental conditions
and maximum rating the interface module (IFM) is designed for. The IFM provider in
cooperation with the testing laboratory defines this document.
Financial Transaction - The act between a cardholder and a merchant or acquirer that results
in the exchange of goods or services against payment.
Function - A process accomplished by one or more commands and resultant actions that are
used to perform all or part of a transaction.
Hash Function - A function that maps strings of bits to fixed-length strings of bits, satisfying
the following two properties:
• It is computationally infeasible to find for a given output an input which maps to this output.
• It is computationally infeasible to find for a given input a second input that maps to the same
output.
Additionally, if the hash function is required to be collision-resistant, it must also satisfy the
following property:
• It is computationally infeasible to find any two distinct inputs that map to the same output.
Hash Result - The string of bits that is the output of a hash function.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 8
Implementation conformance statement (ICS) - A form completed by the interface module
(IFM) provider. The written statement lists all optional functions as specified in the reference
specification implemented in the interface module (IFM). It includes the identification
description and external operating conditions (EOC) of the IFM.
Implementation under test (IUT) - A virtual or abstract device, implementing the EMV
specification, to be submitted for testing (a view of the interface module (IFM) is attached to
the design).
Installation guideline - Set of guidelines, delivered by the interface module (IFM) provider
with every IFM, describing under what conditions a terminal or an IFM can be installed.
Integrated Circuit(s) - Electronic component(s) designed to perform processing and/or
memory functions.
Integrated Circuit(s) Card - A card into which one or more integrated circuits are inserted to
perform processing and memory functions.
Integrated Circuit Module - The sub-assembly embedded into the ICC comprising the IC,
the IC carrier, bonding wires, and contacts.
Interface Device - That part of a terminal into which the ICC is inserted, including such
mechanical and electrical devices that may be considered part of it.
Interface Module - A virtual or abstract device attached to a type production configuration
implemented as a physical device included in a terminal.
Interoperability - The ability of the software and hardware from different interface module
(IFM) providers to work together.
Issuer - A financial institution that supports issuing payment card products to individuals.
Key - A sequence of symbols that controls the operation of a cryptographic transformation.
Key Activation: The process of beginning to use a key at the Certification Authority for the
production of public key certificates.
Key Expiry Date: The date after which a signature made with a particular key is no longer
valid. Issuer certificates signed by the key must expire on or before this date. Keys may be
removed from terminals after this date has passed.
Key Installation Deadline: The date by which all terminals must be able to verify issuer
certificates based on this key, and the earliest date that cards may be issued that contain
issuer certificates based on this key.
Key Introduction: The process of generating, distributing, and beginning use of a key pair.
Key Life Cycle: All phases of key management, from planning and generation, through
revocation, destruction, and archiving.
Key Replacement: The simultaneous revocation of a key and introduction of a key to replaced
the revoked one.
Key Revocation: The key management process of withdrawing a key from service and
dealing with the legacy of its use. Key Revocation can be as-scheduled or accelerated.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 9
Key Revocation Date: The date after which no legitimate cards still in use should contain
certificates signed by this key, and therefore the date after which this key can be deleted from
terminals. For a planned revocation the Key Revocation Date is the same as the key expiry
date.
Key Withdrawal: The process of removing a key from service as part of its revocation.
Laboratory - A facility that performs type approval testing.
Letter of accreditation - Written statement that confirms a testing laboratory is performing
type approval tests in conformance to the common rules, as defined by EMVCo.
Letter of approval - written statement that documents the decision of EMVCo that a specified
product type has demonstrated sufficient conformance to the EMV Specification on the date
of it being tested..
Logical Compromise: The compromise of a key through application of improved cryptanalytic
techniques, increases in computing power, or combination of the two.
Lower tester - The integrated circuit card (ICC) simulator going to allow the implementation
under test (IUT) to react on normal and error conditions.
Magnetic Stripe - The stripe containing magnetically encoded information.
Major modification - Technical change of an interface module (IFM) or its functionality that
implies that the IFM provider can no longer guarantee conformance of the modified IFM with
the requirements of Part 1 of the EMV Integrated Circuit Card Specification for Payment
Systems.
Merchant - A seller of goods, services, and/or information who accepts payment for them
electronically, and may provide selling services and/or electronic delivery of items for sale
(e.g., information).
Merchant Server - A system that interacts with the Cardholder System for electronic
payments. The Merchant Server also interacts with the Acquirer using the payment protocol
to receive authorization and capture services for electronic payment transactions.
Merchant System - A system that interfaces with the cardholder (or ECAD) to offer goods
and services in return for electronic payment and interfaces with the acquirer system to
process electronic commerce transactions.
Message - A string of bytes sent by the terminal to the card or vice versa, excluding
transmission-control characters.
Message Authentication Code - A symmetric cryptographic transformation of data that
protects the sender and the recipient of the data against forgery by third parties.
Migration Key- A key introduced into the system for future use.
Minor modification - Technical change of an interface module (IFM) or its functionality that
does not impact the functionality of that IFM with respect to the requirements of Part 1 of the
Integrated Circuit Card Specification for Payment Systems and the implementation
conformance statement (ICS).
Network - A collection of communication and information processing systems that may be
shared among several users.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 10
Nibble - The four most significant or least significant bits of a byte.
Padding - Appending extra bits to either side of a data string.
Path - Concatenation of file identifiers without delimitation.
Payment System - For the purposes of this specification, American Express, Discover, JCB,
MasterCard, UnionPay or Visa.
Payment Systems Environment - The set of logical conditions established within the ICC
when a payment system application conforming to this specification has been selected, or
when a directory definition file (DDF) used for payment system application purposes has been
selected.
Plaintext - Unenciphered information.
Planned Revocation: A Key Revocation performed as scheduled by the published key expiry
date.
Potential Compromise: A condition where cryptanalytic techniques and/or computing power
has advanced to the point that compromise of a key of a certain length is feasible or even
likely.
Primary Account Number (PAN) - The assigned number that identifies the card issuer and
cardholder. This account number is composed of an issuer identifier, an individual account
number identification, and an accompanying check digit, as defined by ISO 7812-1985.
Private Key - That key of an entity’s asymmetric key pair that should only be used by that
entity. In the case of a digital signature scheme, the private key defines the signature function.
Proficiency - Ability of a testing laboratory to perform the specified tests in an exact and
reproducible fashion and to provide an accurate test report.
Prologue Field - The first field of a block. It contains subfields for node address (AD), protocol
control byte (PCB), and length (LEN).
Protocol - Method of communication between the integrated circuit card (ICC) and the
terminal, represented in this specification by T=0 (character protocol) and T=1 (block protocol).
Prototype - Implementation of a design for evaluation purposes but not for type approval.
Public Key - That key of an entity’s asymmetric key pair that can be made public. In the case
of a digital signature scheme, the public key defines the verification function.
Public Key Certificate - The public key information of an entity signed by the certification
authority and thereby rendered unforgeable.
Quality assurance - For purpose of this specification, all activities targeted at maximizing the
level of confidence that the quality of a product is constant and demonstrated throughout
volume production.
Quality system - An organization implementing quality procedures describing the operations
performed by its people in order to achieve its activity with the correct level of quality.
Redundancy - Any information that is known and can be checked.
Reference specification - A set of documents defining the requirements to which the
interface module (IFM) shall comply. The reference specification consists of the current EMV
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 11
Integrated Circuit Card Specification for Payment Systems and any additional documentation
required to proceed with type approval.
Registration Authority An independent third-party organization that process payment card
applications for multiple payment card brands and forwards applications to the appropriate
financial institutions.
Response - A message returned by the ICC to the terminal after the processing of a command
message received by the ICC.
RSA Failure: An advance in mathematics, cryptanalysis or technology that renders RSA key
technology ineffective, regardless of key or key size.
Sample - Terminal, including the implementation under test (IUT), picked out of production for
testing.
Secret Key - A key used with symmetric cryptographic techniques and usable only by a set
of specified entities.
Script - A command or a string of commands transmitted by the issuer to the terminal for the
purpose of being sent serially to the ICC as commands.
Secure Socket Layer (SSL) - a standard (developed by Netscape Communications
Company) that encrypts data between a Web browser and a Web server. SSL does not specify
what data is sent or encrypted. In an SSL session, all data sent is encrypted.
Service provider - The entity that provides a product or a service to customers, using
terminals and a payment system.
Signal Amplitude - The difference between the high and low voltages of a signal.
Signal Perturbations - Abnormalities occurring on a signal during normal operation such as
undershoot/overshoot, electrical noise, ripple, spikes, crosstalk, etc. Random perturbations
introduced from external sources are beyond the scope of the specification.
Statement of readiness - Part of the implementation conformance statement (ICS); it is a
declaration by the interface module (IFM) provider that the IFM type conforms to the EMV
specifications.
Statement of specification acceptance- Written statement from the interface module (IFM)
provider that states the IFM provider accepts all related specifications as defined by EMVCo.
Suspected Compromise: A condition where information from system monitoring indicates
malfunction which could be caused by key compromise, but which has not been confirmed as
such.
Symmetric Cryptographic Technique - A cryptographic technique that uses the same secret
key for both the originators and recipient’s transformation. Without knowledge of the secret
key, it is computationally infeasible to compute either the originator’s or the recipient’s
transformation.
System integrator - The entity that integrates interface modules (IFMs) and devices
containing IFMs into a system for use by a service provider.
System under test (SUT) - System, module, part, or component actually tested or to be tested
(either a part of the terminal or the entire terminal) including the implementation under test
(IUT).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 12
T=0 - Character-oriented asynchronous half-duplex transmission protocol.
T=1 - Block-oriented asynchronous half-duplex transmission protocol.
Template - Value field of a constructed data object, defined to give a logical grouping of data
objects.
Terminal - The device used in conjunction with the ICC at the point of transaction to perform
a financial transaction. It incorporates the interface device and may also include other
components and interfaces such as host communications.
Terminal application layer (TAL) - The part of the terminal that initiates a command. It sends
an instruction via the terminal transport layer (TTL) to the integrated circuit card (ICC) in the
form of a five-byte header called the command header.
Test - Any activity that aims at verifying the conformance of a selected product or process to
a given requirement under a given set of conditions.
Test bench - A defined combination of a set of test methods and test equipment for the
purpose of type approval tests.
Type Approval - Acknowledgment by EMVCo that the specified product has demonstrated
sufficient conformance to the EMVCo ICC specifications for its stated purpose.
Type Approval documentation - Full set of documents and procedures issued by EMVCo to
perform the type approval process.
Type Approval process - The processes followed to test a product type for compliance with
a certain specification.
Type Approval test - The execution of a defined set of tests against requirements described
in a specification to determine compliance with that specification.
Type approval test report - The result of type approval testing on a product.
Upper tester - The internal (or back external) application of the interface module (IFM) that
emulates a real application in order to test the implementation under test (IUT) under all
possible conditions.
Warm Reset - The reset that occurs when the reset (RST) signal is applied to the ICC while
the clock (CLK) and supply voltage (VCC) lines are maintained in their active state.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
5
Page 13
Test Settings
5.1 Default Values setting
Unless otherwise specified in each test case individually, the following default value are used
to perform the terminal level 2 test cases.
CDOL1
Transaction Date, Transaction Amount, Terminal
Capabilities, Terminal Additional Capabilities, TVR,
TSI, CVM Result
CDOL2
Transaction Date, Transaction Amount, Terminal
Capabilities, TVR TSI
TDOL
Up to the Implementer
DDOL
Up to the Implementer
Batch message
Message Format - Authorization/Financial/Batch
messages shall contain TSI & Service Code
AID of application 1 (default
application)
Up to the Implementer
AID of application 2 (if present)
Up to the Implementer
AID of application 3 (if present)
Up to the Implementer
AID of application 4 (if present)
Up to the Implementer
AID of application 5 (if present)
Up to the Implementer
PAN
Up to the Implementer
Payment Scheme Public Key
Up to the Implementer
Application Primary Account
Number ‘PAN)
Up to the Implementer
Application Primary Account
Number ‘PAN) Sequence Number
Up to the Implementer
Issuer Public Key
Up to the Implementer
For the 2CT category of tests, an American Express
AID, an UnionPay AID , a Discover AID, a MasterCard
AID, a VISA and a JCB AID shall be used once.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 14
ICC Public Key (if present)
Up to the Implementer
Application File Locator (AFL)
Up to the Implementer
Application currency code
Up to the Implementer
Application currency exponent
Up to the Implementer
Application Discretionary Data
Up to the Implementer
Application Effective Date
Up to the Implementer
Application Expiration Date
Up to the Implementer
Application Interchange Profile
Up to the Implementer
Application Preferred Name
Up to the Implementer
Application Priority Indicator
Up to the Implementer
Application Reference Currency
Up to the Implementer
Application Reference Currency
Exponent
Up to the Implementer
Application Usage Control
Up to the Implementer
Application Version Number
Up to the Implementer
Cardholder Name
Up to the Implementer
Cardholder Name extended
Up to the Implementer
Certification Authority Public Key
Index
Up to the Implementer
Cardholder Verification Method
(CVM) List
Up to the Implementer
Directory Discretionary Template
Up to the Implementer
Dedicated File (DF) Name
Up to the Implementer
Directory Definition File (DDF)
Name
Up to the Implementer
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 15
Integrated Circuit Card (ICC) PIN
Encipherment Public Key Certificat
Up to the Implementer
Integrated Circuit Card (ICC) PIN
Encipherment Public Key
Exponent
Up to the Implementer
Integrated Circuit Card (ICC) PIN
Encipherment Public Key
Remainder
Up to the Implementer
Issuer Action Code-Default
Up to the Implementer
File Control Information (FCI)
Template
Up to the Implementer
File Control Information (FCI)
Issuer Discretionary Data
Up to the Implementer
Issuer Application Data
Up to the Implementer
Issuer Action Code – Denial
Up to the Implementer
Issuer Action Code – Online
Up to the Implementer
Issuer Code Table Index
Up to the Implementer
Issuer Country Code
Up to the Implementer
Issuer Public Key Certificate
Up to the Implementer
Issuer Public Key Exponent
Up to the Implementer
Issuer Public Key Remainder
Up to the Implementer
Language Preference
Up to the Implementer
Last Online Application
Transaction Counter (ATC)
Register
Up to the Implementer
Lower Consecutive Offline Limit
Up to the Implementer
Personal Identification Number
(PIN) Try Counter
03
Personal Identification Number
(PIN) Try Limit
03
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 16
Service Code
Up to the Implementer
Short File Identifier (SFI)
Up to the Implementer
Signed Static Application Data
Up to the Implementer
Upper Consecutive Offline Limit
Up to the Implementer
Static Data Authentication Tag List
Up to the Implementer
Track 1 Discretionary Data
Up to the Implementer
Track 2 Discretionary Data
Up to the Implementer
Track 2 Equivalent Data
Up to the Implementer
5.2 Cryptogram Type requested by Terminal
In each test case, it is assumed that terminal action analysis conditions (i.e. TAC/IAC values)
will be set appropriately in order that the cryptogram expected by test conditions is requested
in either 1st or 2nd GENERATE AC.
5.3 Recommended Test Script Commands
For the implementation of the test cases related to the issuer script function, it is recommended
that the following EMV commands be used:
•
Application Block
•
Application Unblock
•
Card Block
•
PIN Change/Unblock
When the test cases are related to non-EMV commands, it is recommended that the following
commands be used:
•
Put Data
•
Update Record
All AID listed in the present document shall be always selectable according to EMV Book
1. In case that the Application Kernel Level 2 implementation allow some applications to
be eliminated from the candidate list with proprietary mechanism, according to Book 1
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 17
Section 12.3 second paragraph, such applications shall not be part of the AIDs used in the
present test plan document.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
6
Page 18
Test Structure
6.1 Test numbering and associated sub cases
Test Numbers are structured as follow:
2Cx.yyy.zz
Version: 10a Sub Case Number: 3
Where:
•
x is the category of the test (see next section),
•
yyy is the test number in the category,
•
zz is test number extension, used when test needs to be added between two existing
tests,
•
Version: it is the version of the test case,
•
Sub case number: is the number of the sub case associated to the related test.
Numbering can start at zero, meaning no sub cases in the related test. When subcases
are present, reference to a specific sub case in a test case can be seen as follow:
2Cx.yyy.zz.ss, where ss is the number of the sub case.
6.2 Test Category
The Test Cases listed in this document are categorized. This rule is not strictly followed
however, as depending on the objective of the test, it may happen that a test listed in a specific
category also covers functions listed in another category. Test Cases are divided into the
following categories:
•
2CA, Data Element and Command: The intent of the test cases in this category is to
verify that cryptography is in accordance with [N3] – Sections 5 & 6 Data Element and
Commands.
•
2CB, Application Selection: The intent of the test cases in this category is to verify that
cryptography is in accordance with [N1] – Section 12 Application Selection.
•
2CC, Security Aspects: The intent of the test cases in this category is to verify that
cryptography is in accordance with [N2] – Sections 5 to 9.
•
2CE, Data Objects: The intent of the test cases in this category is to verify that
cryptography is in accordance with [N3] – Annex B, Data Objects.
•
2CH, Approved Cryptography Algorithm: The intent of the test cases in this category
is to verify that cryptography is in accordance with [N2] – Annexes.
•
2CI, File for Financial Transaction Interchange: The intent of the test cases in this
category is to verify that Data and file management is in accordance with [N3] –
Sections 3, and 4.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 19
•
2CJ, Functions used in Transaction Processing: The intent of the test cases in this
category is to verify that Transaction processing is in accordance with [N1] and [N3]
for transaction processing.
•
2CK, Generate AC Command coding: The intent of the test cases in this category is to
verify that Generate AC management is in accordance with [N3] – Sections 1, 3 and
5.
•
2CL, Erroneous or Missing Data in ICC: The intent of the test cases in this category is
to verify that Terminal management of mandatory data is in accordance with [N1] –
Sections 7 & 8, and [N3] – Sections 4 & 7.
•
2CM, Terminal General Requirements: The intent of the test cases in this category is
to verify that the terminal icomplies with [N4] – General Requirements (Sections 2, 3
and 11).
•
2CN, Software Architecture: The intent of the test cases in this category is to verify that
the terminal complies with [N4] – Section 6, Data Management.
•
2CO, Cardholder and Merchant Interface: The intent of the test cases in this category
is to verify that the terminal complies with [N4] - Section 8, Cardholder Attendant and
Acquirer Interface.
•
2CP, Coding of Terminal Data Element: The intent of the test cases in this category is
to verify that the terminal complies with [N4] - Annex A, Terminal Data Elements.
•
2CS, Command Syntax: The intent of the test cases in this category is to verify that
the commands used are in accordance with [N3] Part 1 - Application Specification.
When the application is used to perform command syntax checking, functionality
testing will not be specifically performed, but will be tested in other sections, as
specified.
•
2CT, Combined Test: The intent of the test cases in this category is to verify that the
Terminal transaction flow is in accordance with [N3] Part 2 – Transaction flow, where
test cases are related to combination of EMV functions. Goal of this series is to ensure
that whatever the terminal type being tested, the terminal correctly performs the EMV
flow by declining or accepting the transaction, depending on the predefined card profile
(reflecting CCD, MasterCard, VISA and JCB card profiles).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
7
Page 20
Test Cases
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 21
7.1 Data Element and Command
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 22
2CA.001.01 Data Elements Storage
Test No: 2CA.001.01 - Revision 15 - Number of sub cases: 0
Objective: To ensure that the retrieved values fields of the data elements are stored
in the terminal buffer for possible later use in the application.
Reference Book 3 - Section 5.2 - Data Objects
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
The terminal receive and store data element sent by the LT
•
LT responds ARQC on first GENERATE AC
•
CDOL2 requests all data Elements read in file referenced in
AFL, Except CDOL1 and CDOL 2(The total expected length of
the data to be returned shall not exceed 256 bytes).
•
CDOL2 requests Signed Static Application Data, tag '93'
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall complete and approve the transaction
•
The LT shall receive in the second GENERATE AC data field,
correct values for data elements stored during the Read
Application Data phase.
•
Tag '93' or any other encrypted data objects shall not be
returned in a decrypted format.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 23
2CA.001.02 Data Elements Storage
Test No: 2CA.001.02 - Revision 15 - Number of sub cases: 0
Objective: To ensure that the retrieved values fields of the data elements are stored
in the terminal buffer for possible later use in the application.
Reference Book 3 - Section 5.2 - Data Objects
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
The terminal receive and store data element sent by the LT
•
CDOL1 requests all data Elements read in file referenced in
AFL, Except CDOL1 and CDOL2 (The total expected length of
the data to be returned shall not exceed 256 bytes).
•
CDOL1 requests Signed Static Application Data, tag '93'
•
LT parameters are set so that transaction is approved off-line
and responds ARQC to the first GENERATE AC
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria: The LT shall receive in the first GENERATE AC data field, correct values
for data elements stored during the Read Application Data phase
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 24
2CA.001.03 Data Elements Storage
Test No: 2CA.001.03 - Revision 13 - Number of sub cases: 0
Objective: To ensure that the retrieved values fields of the data elements are stored
in the terminal buffer for possible later use in the application.
Reference Book 3 - Section 5.2 - Data Objects
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
The terminal receives and stores data element sent by the LT
•
The data elements sent by the LT are set up so that the
transaction will be approved
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall complete and approve the transaction
•
The data in the terminal buffer when stored in the batch data
capture, Online Data Capture, financal message or any other
area shall be in accordance with values sent back by the LT
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 25
2CA.001.04 Coding of Length in TLV
Test No: 2CA.001.04 - Revision 11 - Number of sub cases: 0
Objective: To ensure that the terminal is able to correctly interpret TLV data objects
with a length field coded '00' as defined in ISO/IEC 7816. A data element
with length '00' shall be treated as not present.
Reference Book 3 - Section 5.2 - Data Objects
EMV 4.3:
Terminal NA
Configuration:
Conditions: A record of LT contains a data object with a length field coded '00'
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria: The terminal shall treat this data as not present and process the
transaction until completion, by requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 26
2CA.002.00 Mapping of data objects into records
Test No: 2CA.002.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal accepts any mapping of data object into
records.
Reference Book 3 - Section 5.2 - Data Objects
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Data objects of LT are mapped into different records
organization (and AFL is in accordance) (for instance Track 2
Equivalent Data can be located in file with any SFI value)
•
Data objects of LT are ordered differently within records (for
instance mandatory data object Expiration Date, PAN, CDOL1
and CDOL2 can be ordered differently)
Action: NA
Procedure: Read Application Data phase is performed with the LT for all conditions
above
Pass Criteria:
•
The terminal shall perform Read Application Data phase
correctly and process the transaction until completion, by
requesting a TC or an AAC.
•
Data objects shall be stored with the good value in the terminal
(whenever it is possible to have access to their value)
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 27
2CA.004.00 Coding of a Payment System Directory: SFI Range
Test No: 2CA.004.00 - Revision 10d - Number of sub cases: 10
Objective: To ensure that if the terminal supports selection with PSE, it accepts any
value in the range of 1 to 10 for the SFI of the directory file.
To ensure that if the terminal supports selection with PSE, it is able to
retrieve the directory file.
Reference Book 1 - Section 10.1.4 - Directory Structure
EMV 4.3:
Book 1 - Section 12.2.3 - Coding of a Payment System Directory
Terminal [PSE] supported
Configuration:
Conditions:
•
LT contains a PSE
•
Case 01: SFI value is 1 for the FCI of PSE of LT
•
Case 02: SFI value is 2 for the FCI of PSE of LT
•
Case 03: SFI value is 3 for the FCI of PSE of LT
•
Case 04: SFI value is 4 for the FCI of PSE of LT
•
Case 05: SFI value is 5 for the FCI of PSE of LT
•
Case 06: SFI value is 6 for the FCI of PSE of LT
•
Case 07: SFI value is 7 for the FCI of PSE of LT
•
Case 08: SFI value is 8 for the FCI of PSE of LT
•
Case 09: SFI value is 9 for the FCI of PSE of LT
•
Case 10: SFI value is 10 for the FCI of PSE of LT
Action: NA
Procedure: Application Selection with PSE phase is performed with LT for all
conditions.
Pass Criteria: The LT shall receive a READ RECORD command for the SFI tested
corresponding to the Directory File
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 28
2CA.013.00 Processing DOLs: unknown tag
Test No: 2CA.013.00 - Revision 10 - Number of sub cases: 4
Objective: To verify that whenever the tag of any data object identified in the DOL
is unknown to the terminal, the IUT provides a data element with the
length specified and a value of all hexadecimal zeroes.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Case 01: The PDOL of LT contains a Data Object with an
unknown tag to the terminal
•
Case 02: The CDOL1 of LT contains a Data Object with an
unknown tag to the terminal
•
Case 03: The CDOL2 of LT contains a Data Object with an
unknown tag to the terminal and LT request ARQC on first
Generate AC
•
Case 04: The TDOL of LT contains a Data Object with an
unknown tag to the terminal
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing
the Data Object filled with hexadecimal zeroes (portion has the same
length as the Data Object in DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 29
2CA.013.01 Processing DOLs: unknown tag (2)
Test No: 2CA.013.01 - Revision 10a - Number of sub cases: 0
Objective: To verify that whenever the tag of any data object identified in the DOL
is unknown to the terminal, the IUT provides a data element with the
length specified and a value of all hexadecimal zeroes.
For Dynamic Data Authentication.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions: The DDOL of LT contains a Data Object with an unknown tag to the
terminal
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The terminal shall return an INTERNAL AUTH command to the LT with
portion of the DOL field representing the Data Object filled with
hexadecimal zeroes (portion has the same length as the Data Object in
DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 30
2CA.014.00 Processing DOLs: constructed tag
Test No: 2CA.014.00 - Revision 10 - Number of sub cases: 4
Objective: To verify that whenever the tag of any data object identified in the DOL
represents a constructed data object, the IUT provides a data element
with the length specified and a value of all hexadecimal zeroes.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Case 01: The PDOL of LT contains a constructed Data Object
•
Case 02: The CDOL1 of LT contains a constructed Data Object
•
Case 03: The CDOL2 of LT contains a constructed Data Object
and LT request ARQC on first Generate AC
•
Case 04: The TDOL of LT contains a constructed Data Object
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing
the Data Object filled with hexadecimal zeroes (portion has the same
length as the Data Object in DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 31
2CA.014.01 Processing DOLs: constructed tag (2)
Test No: 2CA.014.01 - Revision 10 - Number of sub cases: 0
Objective: To verify that whenever the tag of any data object identified in the DOL
represents a constructed data object, the IUT provides a data element
with the length specified and a value of all hexadecimal zeroes when
using Dynamic Data Authentication.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions: The DDOL of LT contains a constructed Data Object
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The terminal shall return an INTERNAL AUTH command to the LT with
portion of the DOL field representing the Data Object filled with
hexadecimal zeroes (portion has the same length as the Data Object in
DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 32
2CA.015.00 Processing DOLs: data absent from ICC
Test No: 2CA.015.00 - Revision 11 - Number of sub cases: 3
Objective: To verify that whenever a data object is in the list and is meaningful to
the IUT but represents optional static data absent from the ICC, the
portion of the command field corresponding is filled with hexadecimal
zeroes
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Case 01: The CDOL1 of LT requests an optional ICC static data
that is absent from the LT (for example the Issuer Action Code –
Default, tag ‘9F0D’)
•
Case 02: The CDOL2 of LT requests an optional ICC static data
that is absent from the LT and LT request ARQC on first
GENERATE AC (for example the Issuer Action Code – Default,
tag ‘9F0D’)
•
Case 03: The TDOL of LT requests an optional ICC static data
that is absent from the LT (for example the Issuer Action Code –
Default, tag ‘9F0D’)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing
the Data Object filled with hexadecimal zeroes (portion has the same
length as the Data Object in DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 33
2CA.015.01 Processing DOLs: data absent from ICC (2)
Test No: 2CA.015.01 - Revision 11 - Number of sub cases: 0
Objective: To verify that whenever a data object is in the list and is meaningful to
the IUT but represents optional static data absent from the ICC, the
portion of the command field corresponding is filled with hexadecimal
zeroes.
By using Dynamic Data Authentication.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions: The DDOL of LT requests an optional ICC static data that is absent from
the LT (for example the Issuer Action Code – Default, tag ‘9F0D’)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The terminal shall return an INTERNAL AUTH command to the LT with
portion of the DOL field representing the Data Object filled with
hexadecimal zeroes (portion has the same length as the Data Object in
DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 34
2CA.016.00 Processing DOLs: shorter data object length, numeric
format
Test No: 2CA.016.00 - Revision 10 - Number of sub cases: 4
Objective: To verify that whenever the length specified in the DOL entry is less than
the length of the actual data object, leftmost bytes of the data element
are truncated if the data object has numeric format.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Case 01: The PDOL of LT contains a data object which has
numeric format and a length shorter than actual Data Object
Length
•
Case 02: The CDOL1 of LT contains a data object which has
numeric format and a length shorter than actual Data Object
Length
•
Case 03: The CDOL2 of LT contains a data object which has
numeric format and a length shorter than actual Data Object
Length. LT request an ARQC on First GENERATE AC
•
Case 04: The TDOL of LT contains a data object which has
numeric format and a length shorter than actual Data Object
Length
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing
the Data Object correctly truncated (portion has the same length as the
Data Object in DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 35
2CA.016.01 Processing DOLs: shorter data object length, numeric
format (2)
Test No: 2CA.016.01 - Revision 12 - Number of sub cases: 0
Objective: To verify that whenever the length specified in the DOL entry is less than
the length of the actual data object, leftmost bytes of the data element
are truncated if the data object has numeric format.
By using Dynamic Data Authentication.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions: The DDOL of LT contains a data object, Application Expiration Date (tag
‘5F24’), with a length shorter than actual Data Object Length
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The terminal shall return an INTERNAL AUTH command to the LT with
portion of the DOL field representing the Data Object with the leftmost
bytes truncated (portion has the same length as the Data Object in DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 36
2CA.017.00 Processing DOLs: shorter data object length, other
format
Test No: 2CA.017.00 - Revision 10a - Number of sub cases: 4
Objective: To verify that whenever the length specified in the DOL entry is less than
the length of the actual data object, rightmost bytes of the data element
are truncated if the data object has any other format (including
compressed numeric) than numeric.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Case 01: The PDOL of LT contains data objects which has
format an, ans and b and lengths shorter than actual Data
Objects Length
•
Case 02: The CDOL1 of LT contains data objects which has
format an, ans, cn and b and lengths shorter than actual Data
Objects Length
•
Case 03: The CDOL2 of LT contains data objects which has
format an, ans, cn and b and lengths shorter than actual Data
Objects Length. LT request an ARQC on first GENERATE AC
•
Case 04: The TDOL of LT contains data objects which has
format an, ans, cn and b and lengths shorter than actual Data
Objects Length
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing
the Data Object correctly truncated (portion has the same length as the
Data Object in DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 37
2CA.017.01 Processing DOLs: shorter data object length, other
format (2)
Test No: 2CA.017.01 - Revision 11 - Number of sub cases: 0
Objective: To verify that whenever the length specified in the DOL entry is less than
the length of the actual data object, rightmost bytes of the data element
are truncated if the data object has any other format (including
compressed numeric) than numeric.
By using Dynamic Data Authentication.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions: The DDOL of LT contains data objects which has format an, ans, cn and
b and lengths shorter than actual Data Objects Length
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The terminal shall return an INTERNAL AUTH command to the LT with
portion of the DOL field representing the Data Object with the rightmost
bytes truncated (portion has the same length as the Data Object in DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 38
2CA.018.00 Processing DOLs: longer data object length, numeric
format
Test No: 2CA.018.00 - Revision 10 - Number of sub cases: 4
Objective: To verify that whenever the length specified in the DOL entry is greater
than the length of the actual data object, the actual data is padded with
leading hexadecimal zeroes if the data object has numeric format.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Case 01: The PDOL of LT contains a data object which has
numeric format and a length longer than actual Data Object
Length
•
Case 02: The CDOL1 of LT contains a data object which has
numeric format and a length longer than actual Data Object
Length
•
Case 03: The CDOL2 of LT contains a data object which has
numeric format and a length longer than actual Data Object
Length. LT request an ARQC on first GENERATE AC
•
Case 04: The TDOL of LT contains a data object which has
numeric format and a length longer than actual Data Object
Length
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing
the Data Object correctly padded with leading hexadecimal zeroes
(portion has the same length as the Data Object in DOL)
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 39
2CA.018.01 Processing DOLs: longer data object length, numeric
format (2)
Test No: 2CA.018.01 - Revision 4.3c - Number of sub cases: 0
Objective: To verify that whenever the length specified in the DOL entry is greater
than the length of the actual data object, the actual data is padded with
leading hexadecimal zeroes if the data object has numeric format.
By using Dynamic Data Authentication.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions: The DDOL of LT contains a data object, Application Expiration Date (tag
‘5F24’), with a length longer than actual Data Object Length
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The terminal shall return an INTERNAL AUTH command to the LT with
portion of the DOL field representing the Data Object correctly padded
with hexadecimal zeroes (portion has the same length as the Data
Object in DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 40
2CA.019.00 Processing DOLs: longer data object length,
compressed numeric format
Test No: 2CA.019.00 - Revision 10f - Number of sub cases: 2
Objective: To verify that whenever the length specified in the DOL entry is greater
than the length of the actual data object, the actual data is padded with
trailing hexadecimal FF's if the data has a compressed numeric format.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Case 01: The CDOL1 of LT contains a data object which has
compressed numeric format and a length longer than actual
Data Object Length
•
Case 02: The CDOL2 of LT contains a data object which has
compressed numeric format and a length longer than actual
Data Object Length. LT request an ARQC on first GENERATE
AC
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing
the Data Object correctly padded with trailing hexadecimal FF's (portion
has the same length as the Data Object in DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 41
2CA.019.01 Processing DOLs: longer data object length,
compressed numeric format (2)
Test No: 2CA.019.01 - Revision 43e - Number of sub cases: 0
Objective: To verify that whenever the length specified in the DOL entry is greater
than the length of the actual data object, the actual data is padded with
trailing hexadecimal FF's if the data has a compressed numeric format.
By using Dynamic Data Authentication.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions: The DDOL of LT contains a data object which has compressed numeric
format and a length longer than actual Data Object Length
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The terminal shall return an INTERNAL AUTH command to the LT with
portion of the DOL field representing the Data Object correctly padded
with hexadecimal FF’s (portion has the same length as the Data Object
in DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 42
2CA.020.00 Processing DOLs: longer data object length, other
format
Test No: 2CA.020.00 - Revision 15 - Number of sub cases: 5
Objective: To verify that whenever the length specified in the DOL entry is greater
than the length of the actual data object, the actual data is padded with
trailing hexadecimal zeroes for any other format than numeric or
compressed numeric.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Case 01: The PDOL of LT contains data objects which has
format an (IFD Serial Number, ‘9F1E’), ans (Merchant Identifier,
‘9F16’) and b (Additional Terminal Capabilities, ‘9F40’) and
lengths longer than actual Data Objects Length.
•
Case 02: The CDOL1 of LT data objects which has format an
(IFD Serial Number, ‘9F1E’), ans (Merchant Identifier, ‘9F16’)
and b (Transaction Status Information, ‘9B’).
•
Case 03: The CDOL2 of LT contains data objects which has
format an (IFD Serial Number, ‘9F1E’), ans (Merchant Identifier,
‘9F16’) and b (Transaction Status Information, ‘9B’).
•
Case 04: The TDOL of LT contains data objects which has
format an (IFD Serial Number, ‘9F1E’), ans (Merchant Identifier,
‘9F16’) and b (Transaction Status Information, ‘9B’).
•
Case 05: The CDOL2 of LT contains Issuer Authentication Data
Object with a length longer than actual Data Object Length (for
example: Issuer Authentication Data has a length of 12 bytes
and length declared in CDOL2 is 14).
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing
the Data Object correctly padded with trailing hexadecimal zeroes
(portion has the same length as the Data Object in DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 43
2CA.020.01 Processing DOLs: longer data object length, other
format (2)
Test No: 2CA.020.01 - Revision 11 - Number of sub cases: 0
Objective: To verify that whenever the length specified in the DOL entry is greater
than the length of the actual data object, the actual data is padded with
trailing hexadecimal zeroes for any other format than numeric or
compressed numeric.
By using Dynamic Data Authentication.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions: The DDOL of LT contains data objects which has format an, ans and b
and lengths longer than actual Data Objects Length
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The terminal shall return an INTERNAL AUTH command to the LT with
portion of the DOL field representing the Data Object correctly padded
with hexadecimal zeroes (portion has the same length as the Data
Object in DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 44
2CA.021.00 Processing DOLs: data not applicable
Test No: 2CA.021.00 - Revision 11 - Number of sub cases: 4
Objective: To verify that whenever a data object is in the list and is meaningful to
the Terminal but is not applicable to the current transaction, the portion
of the command field corresponding is filled with hexadecimal zeroes
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
LCOLL and UCOLL are not present in LT
•
Case 01: The PDOL of LT requests the LATC
•
Case 02: The CDOL1 of LT requests the LATC
•
Case 03: The CDOL2 of LT requests the LATC
•
Case 04: The TDOL of LT requests the LATC
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The LT shall receive the DOL with portion of the DOL field representing
the Data Object filled with hexadecimal zeroes (portion has the same
length as the Data Object in DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 45
2CA.021.01 Processing DOLs: data not applicable (2)
Test No: 2CA.021.01 - Revision 11 - Number of sub cases: 0
Objective: To verify that whenever a data object is in the list and is meaningful to
the Terminal but is not applicable to the current transaction, the portion
of the command field corresponding is filled with hexadecimal zeroes.
By using Dynamic Data Authentication.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
LCOLL and UCOLL are not present in LT
•
The DDOL of LT request the LATC
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT (in
particular the DOL processing).
Pass Criteria: The terminal shall return an INTERNAL AUTH command to the LT with
portion of the DOL field representing the Data Object filled with
hexadecimal zeroes (portion has the same length as the Data Object in
DOL).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 46
2CA.022.00 Data Object List consistency (1)
Test No: 2CA.022.00 - Revision 13 - Number of sub cases: 0
Objective: Data objects requested by PDOL are available during Initiate Application
Processing, and remain consistent throughout the transaction
Reference Book 2 - Section 8.1 - Application Cryptogram Generation
EMV 4.3:
Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
Book 3 - Section 10.1 - Initiate Application Processing
Terminal NA
Configuration:
Conditions:
•
The PDOL of LT contains the following:
-
•
Terminal Country Code
Transaction Date
In addition to the default values the CDOL1 & CDOL2 of LT
contain the following:
-
Terminal Country Code
Transaction Date
•
Terminal Action Analysis results in a 1st GENERATE AC request
of TC or ARQC.
•
LT responds with an ARQC to the 1st GENERATE AC
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The GET PROCESSING OPTIONS command shall transmit
meaningful values for: Terminal Country Code & Transaction
Date
•
The first GENERATE AC command shall transmit identical
values with the GET PROCESSING OPTIONS command for:
Terminal Country Code & Transaction Date
•
The second GENERATE AC command shall transmit identical
values with the GET PROCESSING OPTIONS & first
GENERATE AC commands for: Terminal Country Code &
Transaction Date
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 47
2CA.023.00 Data Object List consistency (2)
Test No: 2CA.023.00 - Revision 4.2b - Number of sub cases: 0
Objective: Data objects requested by PDOL are available during Initiate Application
Processing, and remain consistent throughout the transaction
Reference Book 2 - Section 8.1 - Application Cryptogram Generation
EMV 4.3:
Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
Book 3 - Section 10.1 - Initiate Application Processing
Terminal NA
Configuration:
Conditions: •
The PDOL of LT contains the following:
- Additional Terminal Capabilities
- Interface device (IFD) Serial Number
- Terminal Capabilities
- Terminal Country Code
- Terminal Type
- Transaction Sequence Counter
- Transaction Time
- Transaction Date
- Terminal AID
•
In addition to the default values the CDOL1 & CDOL2 of LT
contain the following:
-
Additional Terminal Capabilities
Interface device (IFD) Serial Number
Terminal Capabilities
Terminal Country Code
Terminal Type
Transaction Sequence Counter
Transaction Time
Transaction Date
Terminal AID
•
Terminal Action Analysis results in a 1st GENERATE AC request
of TC or ARQC.
•
LT responds with an ARQC to the 1st GENERATE AC
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 48
2CA.023.00 Data Object List consistency (2)
•
The GET PROCESSING OPTIONS command shall transmit
meaningful values for:
-
•
The first GENERATE AC command shall transmit identical
values with the GET PROCESSING OPTIONS command for:
-
•
Additional Terminal Capabilities
Interface device (IFD) Serial Number
Terminal Capabilities
Terminal Country Code
Terminal Type
Transaction Sequence Counter
Transaction Time
Transaction Date
Terminal AID
Additional Terminal Capabilities
Interface device (IFD) Serial Number
Terminal Capabilities
Terminal Country Code
Terminal Type
Transaction Sequence Counter
Transaction Time (equal to the value transmitted in GET
PROCESSING OPTIONS)
Transaction Date
Terminal AID
The second GENERATE AC command shall transmit identical
values with the GET PROCESSING OPTIONS & first
GENERATE AC commands for:
-
Additional Terminal Capabilities
Interface device (IFD) Serial Number
Terminal Capabilities
Terminal Country Code
Terminal Type
Transaction Sequence Counter
Transaction Time (equal to the value transmitted in GET
PROCESSING OPTIONS)
Transaction Date
Terminal AID
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 49
2CA.025.00 Normal Processing for EXTERNAL AUTHENTICATE Functions specified in the AIP: Issuer Authentication
Test No: 2CA.025.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal accepts a valid status '90 00' in response to
EXTERNAL AUTHENTICATE command and understands it as normal
processing.
To ensure that the terminal expects no response in the returned data
field message of the EXTERNAL AUTHENTICATE command.
To ensure that the terminal sets the 'Issuer authentication was
performed' bit in the TSI to 1b, if the EXTERNAL AUTHENTICATE is
command is sent to the card.
To ensure that the terminal performs Issuer Authentication if supported
in AIP
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 6.5.4.4 - Data Field Returned in the Response Message
Book 3 - Section 8 - Transaction Flow
Book 3 - Section 10.9 - Online Processing
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
LT parameters are set so that transaction is performed on-line.
•
AIP of LT indicates Issuer Authentication is supported (AIP byte
1 bit 3 = 1).
•
Issuer Authentication Data is sent back to the terminal in the
emulated response from Issuer.
•
LT shall return status '90 00' in response to EXTERNAL
AUTHENTICATE command without returned data field
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular on-line processing and Issuer Authentication processing).
Pass Criteria:
•
The terminal shall process the transaction until completion.
•
The LT shall receive an EXTERNAL AUTHENTICATE
command following the First GENERATE AC.
•
TVR byte 5, bit 7 = '0' (ie Issuer Authentication Successful)
received at 2nd GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 50
2CA.025.00 Normal Processing for EXTERNAL AUTHENTICATE Functions specified in the AIP: Issuer Authentication
•
TSI byte 1, bit 5='1' (ie Issuer authentication was performed)
received at 2nd GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 51
2CA.025.01 ARC checking for contrary response when declining
Test No: 2CA.025.01 - Revision 10 - Number of sub cases: 0
Objective: To ensure that the terminal bases its cryptogram request on the
Authorisation Response Code received from the authorisation or
financial transaction response, not on any other data that may be present
in Issuer Authentication Data
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
LT parameters are set so that transaction is performed on-line
•
AIP of LT indicates Issuer Authentication is supported
•
Host Source shall return a decline in the authorization or
financial response
•
Emulated Issuer Authentication Data is transmitted to the
terminal formatted as follows: a valid 8 byte ARPC and a 2 byte
proprietary Authorisation Response Code indicating an approval
•
EXTERNAL AUTHENTICATE command is transmitted with the
Issuer Authentication Data described above
•
LT shall return status ‘90 00’ in response to EXTERNAL
AUTHENTICATE command.
•
CDOL2 requests Authorisation Response Code (tag 8A)
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular on-line processing and Issuer Authentication processing).
Pass Criteria:
•
The terminal shall process the transaction until completion.
•
TVR byte 5, bit 7 = ‘0’ (ie Issuer Authentication Successful)
received at 2nd GENERATE AC.
•
TSI byte 1, bit 5=’1’ (ie Issuer authentication was performed)
received at 2nd GENERATE AC.
•
The terminal issues a second GENERATE AC requesting AAC
•
The Authorisation Response Code shall be the same as the one
transmitted by the host source
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 52
2CA.025.02 ARC checking for contrary response when approving
Test No: 2CA.025.02 - Revision 10 - Number of sub cases: 0
Objective: To ensure that the terminal bases its cryptogram request on the
Authorisation Response Code received from the authorisation or
financial transaction response, not on any other data that may be present
in the Issuer Application Data
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
LT parameters are set so that transaction is performed on-line
•
AIP of LT indicates Issuer Authentication is supported
•
Host Source shall return an approval in the authorization or
financial response
•
Emulated Issuer Authentication Data is transmitted to the
terminal formatted as follows: a valid 8 byte ARPC and a 2 byte
proprietary Authorisation Response Code indicating a decline
•
EXTERNAL AUTHENTICATE command is transmitted with the
Issuer Authentication Data described above
•
LT shall return status ‘90 00’ in response to EXTERNAL
AUTHENTICATE command.
•
CDOL2 requests Authorisation Response Code (tag 8A)
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular on-line processing and Issuer Authentication processing).
Pass Criteria:
•
The terminal shall process the transaction until completion.
•
TVR byte 5, bit 7 = ‘0’ (ie Issuer Authentication Successful)
received at 2nd GENERATE AC.
•
TSI byte 1, bit 5=’1’ (ie Issuer authentication was performed)
received at 2nd GENERATE AC.
•
The terminal issues a second GENERATE AC requesting TC
•
The Authorisation Response Code shall be the same as the one
transmitted by the host source
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 53
2CA.025.03 ARC checking for contrary response when issuing a
referral
Test No: 2CA.025.03 - Revision 11 - Number of sub cases: 0
Objective: To ensure that the terminal bases its cryptogram request on the
Authorisation Response Code received from the authorisation or
financial transaction response, not on any other data that may be present
in the Issuer Application Data
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal ([Online Only or Offline/Online capable] supported AND [Issuer Referral]
Configuration: supported)
Conditions:
•
LT parameters are set so that transaction is performed on-line
•
AIP of LT indicates Issuer Authentication is supported
•
Host Source shall return a referral in the authorization or
financial response
•
Emulated Issuer Authentication Data is transmitted to the
terminal formatted as follows: a valid 8 byte ARPC and a 2 byte
proprietary Authorisation Response Code indicating an approval
•
EXTERNAL AUTHENTICATE command is transmitted with the
Issuer Authentication Data described above
•
LT shall return status ‘90 00’ in response to EXTERNAL
AUTHENTICATE command.
•
CDOL2 requests Authorisation Response Code (tag 8A)
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular on-line processing and Issuer Authentication processing).
Pass Criteria:
•
The terminal shall process the transaction until completion.
•
TVR byte 5, bit 7 = ‘0’ (ie Issuer Authentication Successful)
received at 2nd GENERATE AC.
•
TSI byte 1, bit 5=’1’ (ie Issuer authentication was performed)
received at 2nd GENERATE AC.
•
The terminal shall display the “call your bank” message and
perform a referral.
•
The Authorisation Response Code shall be the same as the one
transmitted by the host source
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 54
2CA.025.04 Terminal Processing when Issuer Authentication is not
present
Test No: 2CA.025.04 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal does not decline the transaction when
transaction is approved by the Issuer and Issuer Authentication is not
present.
Reference Book 3 - Section 10.9 Online Processing
EMV 4.3:
Book 3 - Section 10.7 Terminal Action Analysis
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
LT parameters are set so that transaction is performed on-line
•
LT parameters are set so an ARQC is returned at first GenAC
•
In response to online processing, the issuer must approve the
transaction (Authorisation Response Code = transaction
accepted)
•
Issuer Authentication Data is not present in Issuer response
•
All bits of TAC and IAC are set to ‘0’
•
AIP of LT indicates Issuer Authentication is supported (AIP byte
1 bit 3 = 1).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular on-line processing and Issuer Authentication processing).
Pass Criteria:
•
The terminal shall process until completion by approving the
transaction.
•
TVR byte 5, bit 7 = '0' (ie Issuer Authentication not used)
received at 2nd GENERATE AC.
•
TSI byte 1, bit 5='0' (ie Issuer authentication was not performed)
received at 2nd GENERATE AC..
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 55
2CA.026.00 Status Word Processing for EXTERNAL
AUTHENTICATE
Test No: 2CA.026.00 - Revision 4.2b - Number of sub cases: 12
Objective: To ensure that the terminal accepts a failed status in response to
EXTERNAL AUTHENTICATE command different from '90 00' and '69
85', understands it as failed processing and sets the 'Issuer
authentication was unsuccessful' bit' in the TVR to 1b.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 8.1 - Exception Handling
Book 3 - Section 10.9 - Online Processing
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
LT parameters are set so that transaction is performed on-line.
•
AIP of LT indicates Issuer Authentication is supported (AIP byte
1 bit 3 = 1).
•
LT parameters are set so that the card responds with a TC at
Second GENERATE AC
•
Issuer Authentication Data is sent back to the terminal in the
emulated response from Issuer
•
Case 01: LT returns status value '62 83' in response to
EXTERNAL AUTHENTICATE
•
Case 02: LT returns status value '63 00' in response to
EXTERNAL AUTHENTICATE
•
Case 03: LT returns status value '63 Cx' in response to
EXTERNAL AUTHENTICATE
•
Case 04: LT returns status value '69 83' in response to
EXTERNAL AUTHENTICATE
•
Case 05: LT returns status value '69 84' in response to
EXTERNAL AUTHENTICATE
•
Case 06: LT returns status value '6A 81' in response to
EXTERNAL AUTHENTICATE
•
Case 07: LT returns status value '6A 82' in response to
EXTERNAL AUTHENTICATE
•
Case 08: LT returns status value '6A 83' in response to
EXTERNAL AUTHENTICATE
•
Case 09: LT returns status value '6A 88' in response to
EXTERNAL AUTHENTICATE
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 56
2CA.026.00 Status Word Processing for EXTERNAL
AUTHENTICATE
•
Case 10: LT returns status value '90 01' in response to
EXTERNAL AUTHENTICATE
•
Case 11: LT returns status value '64 00' in response to
EXTERNAL AUTHENTICATE
•
Case 12: LT returns status value '65 00' in response to
EXTERNAL AUTHENTICATE
Action: NA
Procedure: Application in LT is selected and transaction is started with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion with
an approval.
•
TVR byte 5, bit 7 = '1' (ie Issuer Authentication Unsuccessful)
received at 2nd GENERATE AC.
•
TSI byte 1, bit 5='1' (ie Issuer authentication was performed)
received at 2nd GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 57
2CA.026.01 Status Word Processing for EXTERNAL
AUTHENTICATE
Test No: 2CA.026.01 - Revision 4.2b - Number of sub cases: 12
Objective: To ensure that the terminal accepts a failed status in response to
EXTERNAL AUTHENTICATE command different from '90 00' and '69
85', understands it as failed processing and sets the 'Issuer
authentication was unsuccessful' bit' in the TVR to 1b.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 8.1 - Exception Handling
Book 3 - Section 10.9 - Online Processing
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
LT parameters are set so that transaction is performed on-line.
•
AIP of LT indicates Issuer Authentication is supported (AIP byte
1 bit 3 = 1).
•
Issuer Authentication Data is sent back to the terminal in the
emulated response from Issuer
•
LT response to the second GENERATE AC an AAC
•
Case 01: LT returns status value '62 83' in response to
EXTERNAL AUTHENTICATE
•
Case 02: LT returns status value '63 00' in response to
EXTERNAL AUTHENTICATE
•
Case 03: LT returns status value '63 Cx' in response to
EXTERNAL AUTHENTICATE
•
Case 04: LT returns status value '69 83' in response to
EXTERNAL AUTHENTICATE
•
Case 05: LT returns status value '69 84' in response to
EXTERNAL AUTHENTICATE
•
Case 06: LT returns status value '6A 81' in response to
EXTERNAL AUTHENTICATE
•
Case 07: LT returns status value '6A 82' in response to
EXTERNAL AUTHENTICATE
•
Case 08: LT returns status value '6A 83' in response to
EXTERNAL AUTHENTICATE
•
Case 09: LT returns status value '6A 88' in response to
EXTERNAL AUTHENTICATE
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 58
2CA.026.01 Status Word Processing for EXTERNAL
AUTHENTICATE
•
Case 10: LT returns status value '90 01' in response to
EXTERNAL AUTHENTICATE
•
Case 11: LT returns status value '64 00' in response to
EXTERNAL AUTHENTICATE
•
Case 12: LT returns status value '65 00' in response to
EXTERNAL AUTHENTICATE
Action: NA
Procedure: Application in LT is selected and transaction is started with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion with
a decline.
•
TVR byte 5, bit 7 = '1' (ie Issuer Authentication Unsuccessful)
received at 2nd GENERATE AC.
•
TSI byte 1, bit 5='1' (ie Issuer authentication was performed)
received at 2nd GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 59
2CA.027.00 Normal Processing for GENERATE AC
Test No: 2CA.027.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal accepts a valid status '90 00' in response to
GENERATE AC command and understands it as normal processing
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal NA
Configuration:
Conditions: LT returns status '90 00' in response to GENERATE AC as well as a
valid response
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal shall process the transaction until completion, by requesting
a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 60
2CA.028.00 Normal Processing for GET CHALLENGE
Test No: 2CA.028.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal accepts a valid status '90 00' in response to
GET CHALLENGE command and understands it as normal processing
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
LT returns status '90 00' in response to GET CHALLENGE as
well as a valid response
•
CVM is 'Enciphered offline PIN verification, always' (04 00)
•
CDOL1 requests TSI and TVR
Action: The cardholder enter a valid PIN.
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '0' (ie Cardholder verification was
successful) received at 1st GENERATE AC.
•
TSI byte 1, bit 7 ='1' (ie Cardholder Verification was performed)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 61
2CA.029.04 Failed Processing for GET DATA
Test No: 2CA.029.04 - Revision 11 - Number of sub cases: 2
Objective: To ensure that the terminal accepts a failed status '6A81' or '6A 88' in
response to GET DATA command and understands it as failed
processing when Terminal Velocity Checking is performed.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal [Velocity Checking] supported
Configuration:
Conditions:
•
AIP of LT indicates TRM to be performed (byte 1 bit 4 =‘1’).
•
LT returns tags '9F 14' and '9F 23' during Read Application Data
•
The following status word are returned on GET DATA for ATC
•
Case 01: LT returns status '6A81' in response to GET DATA
command
•
Case 02: LT returns status '6A88' in response to GET DATA
command
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 6 ='1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 4, bit 7 ='1' (ie Lower consecutive offline limit
exceeded) received at 1st GENERATE AC.
•
TVR byte 4, bit 6= '1' (ie Upper consecutive offline limit
exceeded) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 62
2CA.029.05 Failed Processing for GET DATA (1)
Test No: 2CA.029.05 - Revision 11 - Number of sub cases: 2
Objective: To ensure that the terminal accepts a failed status '6A81' or '6A 88' in
response to GET DATA command and understands it as failed
processing when Terminal Velocity Checking is performed.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal [Velocity Checking] supported
Configuration:
Conditions:
•
AIP of LT indicates TRM to be performed (byte 1 bit 4 =‘1’).
•
LT returns tags '9F 14' and '9F 23' during Read Application Data
•
The following status word are returned on GET DATA for
LOATC
•
Case 01: LT returns status '6A81' in response to GET DATA
command
•
Case 02: LT returns status '6A88' in response to GET DATA
command
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 6 ='1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 4, bit 7 ='1' (ie Lower consecutive offline limit
exceeded) received at 1st GENERATE AC.
•
TVR byte 4, bit 6= '1' (ie Upper consecutive offline limit
exceeded) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 63
2CA.029.06 Failed Processing for GET DATA (2)
Test No: 2CA.029.06 - Revision 10g - Number of sub cases: 2
Objective: To ensure that the terminal accepts a failed status '6A81' or '6A 88' in
response to GET DATA command and understands it as failed
processing and proceeds with PIN Verification processing.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal ([Offline Plaintext PIN] supported AND [Get Data for PIN Try Counter]
Configuration: supported)
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List requests 'Plaintext PIN, if terminal supports' (01 03)
•
the following status word are returned on GET DATA for PTC
•
Case 01: LT returns status '6A81' in response to GET DATA
command
•
Case 02: LT returns status '6A88' in response to GET DATA
command
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The terminal performs PIN processing
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 64
2CA.029.07 Failed Processing for GET DATA (3)
Test No: 2CA.029.07 - Revision 10g - Number of sub cases: 2
Objective: To ensure that the terminal accepts a failed status '6A81' or '6A 88' in
response to GET DATA command and understands it as failed
processing and proceeds with Enciphered PIN Verification processing.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal ([Offline Enciphered PIN] supported AND [Get Data for PIN Try Counter]
Configuration: supported)
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List requests 'Enciphered PIN, if terminal supports' (04 03)
•
the following status word are returned on GET DATA for PTC
•
Case 01: LT returns status '6A81' in response to GET DATA
command
•
Case 02: LT returns status '6A88' in response to GET DATA
command
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The terminal performs enciphered PIN processing
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 65
2CA.029.08 Status Word Processing for GET DATA
Test No: 2CA.029.08 - Revision 12 - Number of sub cases: 12
Objective: To ensure that the terminal processes transaction normally if status in
response to GET DATA command is different from '90 00', '6A81' or '6A
88' during Velocity checking.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal [Velocity Checking] supported
Configuration:
Conditions:
•
AIP of LT indicates TRM to be performed (byte 1 bit 4 =‘1’).
•
LT returns tags '9F 14' and '9F 23' during Read Application Data
•
the following status word are returned on GET DATA for ATC
•
Case 01: LT returns status '62 83' in response to GET DATA
command
•
Case 02: LT returns status '63 00' in response to GET DATA
command
•
Case 03: LT returns status '63 Cx' in response to GET DATA
command
•
Case 04: LT returns status '69 83' in response to GET DATA
command
•
Case 05: LT returns status '69 84' in response to GET DATA
command
•
Case 06: LT returns status '69 85' in response to GET DATA
command
•
Case 07: LT returns status '6A 82' in response to GET DATA
command
•
Case 08: LT returns status '6A 83' in response to GET DATA
command
•
Case 09: LT returns status '64 00' in response to GET DATA
command
•
Case 10: LT returns status '65 00' in response to GET DATA
command
•
Case 11: LT returns status '90 01' in response to GET DATA
command
•
Case 12: LT returns status '6D 00' in response to GET DATA
command
Action: NA
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 66
2CA.029.08 Status Word Processing for GET DATA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal shall continue the transaction until completion.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 67
2CA.029.09 Status Word Processing for GET DATA (2)
Test No: 2CA.029.09 - Revision 15 - Number of sub cases: 12
Objective: To ensure that the terminal processes transaction normally if status in
response to GET DATA command is different from '90 00', '6A81' or '6A
88' during Velocity checking.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal [Velocity Checking] supported
Configuration:
Conditions:
•
AIP of LT indicates TRM to be performed (byte 1 bit 4 =‘1’).
•
LT returns tags '9F 14' and '9F 23' during Read Application Data
•
the following status word are returned on GET DATA for LOATC
•
Case 01: LT returns status '62 83' in response to GET DATA
command
•
Case 02: LT returns status '63 00' in response to GET DATA
command
•
Case 03: LT returns status '63 Cx' in response to GET DATA
command
•
Case 04: LT returns status '69 83' in response to GET DATA
command
•
Case 05: LT returns status '69 84' in response to GET DATA
command
•
Case 06: LT returns status '69 85' in response to GET DATA
command
•
Case 07: LT returns status '6A 82' in response to GET DATA
command
•
Case 08: LT returns status '6A 83' in response to GET DATA
command
•
Case 09: LT returns status '64 00' in response to GET DATA
command
•
Case 10: LT returns status '65 00' in response to GET DATA
command
•
Case 11: LT returns status '90 01' in response to GET DATA
command
•
Case 12: LT returns status '6D 00' in response to GET DATA
command
Action: NA
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 68
2CA.029.09 Status Word Processing for GET DATA (2)
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal shall continue the transaction until completion.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 69
2CA.029.10 Status Word Processing for GET DATA (3)
Test No: 2CA.029.10 - Revision 15 - Number of sub cases: 13
Objective: To ensure that the terminal accepts the transaction if status in response
to GET DATA command is different from '90 00', '6A81' or '6A 88' during
PIN Verification processing.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal ([Get Data for PIN Try Counter] supported AND [Offline Plaintext PIN]
Configuration: supported)
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List requests 'Plaintext PIN, if terminal supports' (01 03)
•
the following status word are returned on GET DATA for PTC
•
Case 01: LT returns status '62 83' in response to GET DATA
command
•
Case 02: LT returns status '63 00' in response to GET DATA
command
•
Case 03: LT returns status '63 Cx' in response to GET DATA
command
•
Case 04: LT returns status '69 83' in response to GET DATA
command
•
Case 05: LT returns status '69 84' in response to GET DATA
command
•
Case 06: LT returns status '69 85' in response to GET DATA
command
•
Case 07: LT returns status '6A 82' in response to GET DATA
command
•
Case 08: LT returns status '6A 83' in response to GET DATA
command
•
Case 09: LT returns status '64 00' in response to GET DATA
command
•
Case 10: LT returns status '65 00' in response to GET DATA
command
•
Case 11: LT returns status '90 01' in response to GET DATA
command
•
Case 12: LT returns status '6D 00' in response to GET DATA
command
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 70
2CA.029.10 Status Word Processing for GET DATA (3)
•
Case 13: LT returns status '6E 00' in response to GET DATA
command
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal shall continue the transaction until completion.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 71
2CA.029.11 Status Word Processing for GET DATA (4)
Test No: 2CA.029.11 - Revision 16 - Number of sub cases: 13
Objective: To ensure that the terminal continue the transaction if status in response
to GET DATA command is different from '90 00', '6A81' or '6A 88' during
PIN Verification processing.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal ([Get Data for PIN Try Counter] supported AND [Offline Enciphered PIN]
Configuration: supported)
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List requests 'Enciphered PIN, if terminal supports' (04 03)
•
the following status word are returned on GET DATA for PTC
•
Case 01: LT returns status '62 83' in response to GET DATA
command
•
Case 02: LT returns status '63 00' in response to GET DATA
command
•
Case 03: LT returns status '63 Cx' in response to GET DATA
command
•
Case 04: LT returns status '69 83' in response to GET DATA
command
•
Case 05: LT returns status '69 84' in response to GET DATA
command
•
Case 06: LT returns status '69 85' in response to GET DATA
command
•
Case 07: LT returns status '6A 82' in response to GET DATA
command
•
Case 08: LT returns status '6A 83' in response to GET DATA
command
•
Case 09: LT returns status '64 00' in response to GET DATA
command
•
Case 10: LT returns status '65 00' in response to GET DATA
command
•
Case 11: LT returns status '90 01' in response to GET DATA
command
•
Case 12: LT returns status '6D 00' in response to GET DATA
command
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 72
2CA.029.11 Status Word Processing for GET DATA (4)
•
Case 13: LT returns status '6E 00' in response to GET DATA
command
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal shall continue the transaction until completion.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 73
2CA.030.00 Normal Processing for GET PROCESSING OPTIONS
Test No: 2CA.030.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal accepts a valid status '90 00' in response to
GET PROCESSING OPTIONS command and understands it as normal
processing.
To ensure that the terminal sends the GET PROCESSING OPTIONS
command immediately after the application selection function.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 10.1 - Initiate Application Processing
Terminal NA
Configuration:
Conditions: LT returns status '90 00' in response to GET PROCESSING OPTIONS
as well as a valid response
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
LT shall receive a GET PROCESSING OPTIONS command
following final selection process.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 74
2CA.030.05 Failed Processing for GET PROCESSING OPTIONS
Test No: 2CA.030.05 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that the terminal accepts a failed status '6985' in response to
GET PROCESSING OPTIONS command, and understands it as failed
processing and the terminal switches back to the application selection
phase
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 10.1 - Initiate Application Processing
Book 4 - Section 6.3.1 - Initiate Application Processing
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] supported
Configuration:
Conditions:
•
Terminal supports three AIDs (mutually supported by LT)
•
LT have three mutually supported applications
•
LT AIDs have: Application 1 has the Application Priority
Indicator b8 set to ‘1’, Application 2 has the Application Priority
Indicator b8 set to ‘1’ and Application 3 has the Application
Priority Indicator b8 set to ‘0’
•
LT returns status '6985' in response to GET PROCESSING
OPTIONS of the first selected application (application 1)
Action: Cardholder selects Application 3 when list is displayed
Procedure: The first application in the candidate list is selected (application 1), then
removed and the terminal initiate the selection of the second mutually
supported application.
Pass Criteria:
•
The terminal returns to the final selection process after the GET
PROCESSING OPTIONS '69 85' response
•
Application 2 & Application 3 are the only two remaining
applications in the candidate list, and these are displayed for
cardholder selection and confirmation.
•
The terminal shall process the transaction with Application 2 or
Application 3, until completion by requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 75
2CA.030.06 Failed Processing for GET PROCESSING OPTIONS (2)
Test No: 2CA.030.06 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal accepts a failed status '6985' in response to
GET PROCESSING OPTIONS command, and understands it as failed
processing and the terminal switches back to the application selection
phase
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 10.1 - Initiate Application Processing
Book 4 - Section 6.3.1 - Initiate Application Processing
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] not supported
Configuration:
Conditions:
•
Terminal supports three AIDs (mutually supported by LT)
•
LT have three mutually supported applications
•
LT Applications have: Application 1 has the Application Priority
Indicator b8 set to ‘1’, Application 2 has the Application Priority
Indicator b8 set to ‘0’ and Application 3 has the Application
Priority Indicator b8 set to ‘0’
•
Application 2 of LT has a priority greater than Application 3
•
LT returns status '6985' in response to GET PROCESSING
OPTIONS of the application 2
Action: NA
Procedure: Application Selection is performed and and transaction is processed with
LT.
Pass Criteria:
•
The terminal returns to the final selection process after the GET
PROCESSING OPTIONS '69 85' response
•
The terminal shall process the transaction with Application 3,
until completion by requesting a TC.
•
No Cardholder Selection or Confirmation is requested by the
terminal.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 76
2CA.031.00 Normal Processing for Internal Authenticate
Test No: 2CA.031.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal accepts a valid status '90 00' in response to
INTERNAL AUTHENTICATE command and understands it as normal
processing.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
LT returns status '90 00' in response to INTERNAL
AUTHENTICATE as well as a valid response
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
not failed) received at 1st GENERATE AC.
•
TSI byte 1, bit 8='1' (ie Offline data authentication was
performed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 77
2CA.031.01 Status Word Processing for Internal Authenticate
Test No: 2CA.031.01 - Revision 15 - Number of sub cases: 17
Objective: To ensure that the terminal rejects transaction if status in response to
INTERNAL AUTHENTICATE command is different from '90 00'
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 8.1 - Exception Handling
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Case 01: LT returns status value '62 83' in response to
INTERNAL AUTHENTICATE
•
Case 02: LT returns status value '63 00' in response to
INTERNAL AUTHENTICATE
•
Case 03: LT returns status value '63 Cx' in response to
INTERNAL AUTHENTICATE
•
Case 04: LT returns status value '69 83' in response to
INTERNAL AUTHENTICATE
•
Case 05: LT returns status value '69 84' in response to
INTERNAL AUTHENTICATE
•
Case 06: LT returns status value '69 85' in response to
INTERNAL AUTHENTICATE
•
Case 07: LT returns status value '6A 81' in response to
INTERNAL AUTHENTICATE
•
Case 08: LT returns status value '6A 82' in response to
INTERNAL AUTHENTICATE
•
Case 09: LT returns status value '6A 83' in response to
INTERNAL AUTHENTICATE
•
Case 10: LT returns status value '6A 88' in response to
INTERNAL AUTHENTICATE
•
Case 11: LT returns status value '64 00' in response to
INTERNAL AUTHENTICATE
•
Case 12: LT returns status value '65 00' in response to
INTERNAL AUTHENTICATE
•
Case 13: LT returns status value '90 01' in response to
INTERNAL AUTHENTICATE
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 78
2CA.031.01 Status Word Processing for Internal Authenticate
•
Case 14: LT returns status value '6D 00' in response to
INTERNAL AUTHENTICATE
•
Case 15: LT returns status value '6E 00' in response to
INTERNAL AUTHENTICATE
•
Case 16: LT returns status value '6A 86' in response to
INTERNAL AUTHENTICATE
•
Case 17: LT returns status value '67 00' in response to
INTERNAL AUTHENTICATE
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall terminate the transaction
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 79
2CA.032.00 Normal Processing for READ RECORD
Test No: 2CA.032.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal accepts a valid status '90 00' in response to
READ RECORD command and understands it as normal processing
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal NA
Configuration:
Conditions: LT returns status '90 00' in response to READ RECORD as well as a
valid response
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular the Read Application Data phase).
Pass Criteria: The terminal shall process the transaction until completion, by requesting
a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 80
2CA.033.00 Normal Processing for Select
Test No: 2CA.033.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal accepts a valid status '90 00' in response to
SELECT command and understands it as normal processing
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Terminal NA
Configuration:
Conditions: LT returns status '90 00' in response to SELECT as well as a valid
response
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal shall process the transaction until completion, by requesting
a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 81
2CA.033.01 Failed Processing for Select ADF
Test No: 2CA.033.01 - Revision 10f - Number of sub cases: 0
Objective: To ensure that the terminal accepts a status '62 83' in response to
SELECT ADF command and understands it as failed processing during
selection by AID.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Book 3 - Section 6.3.5 - Coding of the Status Bytes
Terminal NA
Configuration:
Conditions:
•
Terminal supports the LT applications
•
LT does not support a PSE
•
LT supports three applications
•
LT returns status value '62 83' in response to SELECT of the
first ADF supported by LT
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal shall select one of the two others application.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 82
2CA.033.02 Status Word Processing for SELECT PSE
Test No: 2CA.033.02 - Revision 10g - Number of sub cases: 12
Objective: To ensure that the terminal use the AID List selection method if status in
response to SELECT PSE command is different from '90 00' and '6A 81'
Reference Book 1 - Section 12.3.2 - Using the PSE
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
Case 01: LT returns status value '63 00' in response to SELECT
PSE
•
Case 02: LT returns status value '63 Cx' in response to
SELECT PSE
•
Case 03: LT returns status value '69 83' in response to SELECT
PSE
•
Case 04: LT returns status value '69 84' in response to SELECT
PSE
•
Case 05: LT returns status value '69 85' in response to SELECT
PSE
•
Case 06: LT returns status value '6A 83' in response to
SELECT PSE
•
Case 07: LT returns status value '6A 88' in response to
SELECT PSE
•
Case 08: LT returns status value '62 83' in response to SELECT
PSE
•
Case 09: LT returns status value '64 00' in response to SELECT
PSE
•
Case 10: LT returns status value '65 00' in response to SELECT
PSE
•
Case 11: LT returns status value '90 01' in response to SELECT
PSE
•
Case 12: LT returns status value '6A 82' in response to
SELECT PSE
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall start the selection by PSE
•
The terminal shall switch to List of AIDs selection
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 83
2CA.033.02 Status Word Processing for SELECT PSE
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 84
2CA.033.04 Failed Processing for Select ADF (2)
Test No: 2CA.033.04 - Revision 11 - Number of sub cases: 0
Objective: To ensure that the terminal accepts a status '6A 81' in response to the
first SELECT ADF command and understands it as failed processing
during selection by AID.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Book 3 - Section 6.3.5 - Coding of the Status Bytes
Terminal NA
Configuration:
Conditions:
•
LT does not support a PSE
•
LT returns status value '6A 81' in response to the first SELECT
of an ADF
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal shall terminate the transaction
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 85
2CA.034.02 Failed Processing for VERIFY
Test No: 2CA.034.02 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal accepts a status '63 Cx' in response to
VERIFY command and understands it as counter provided by 'x'.
To ensure that the terminal displays a specific message and prompts for
another PIN entry if the VERIFY command returns 63 Cx and x is greater
than 0
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 10.5.1 - Offline PIN Processing
Terminal [Offline Plaintext PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Plaintext PIN verification by ICC' (01 00)
•
LT returns status ''63C2" in response to the first Verify
command.
•
LT returns status "63C1" in response to the second Verify
command.
•
LT returns status "63C0" in response to the third Verify
command.
Action: Cardholder enters an invalid PIN three times.
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
Terminal shall display a specific message and shall prompt for
PIN entry for second and third tries
•
The terminal understands there is no more PIN try left and stops
sending verify commands after the third one.
•
TVR byte 3, bit 6='1' (ie PIN Try Limited exceeded) received at
1st GENERATE AC.
•
TSI byte 1, bit 7='1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 86
2CA.034.05 Failed Processing for VERIFY (2)
Test No: 2CA.034.05 - Revision 10g - Number of sub cases: 2
Objective: To ensure that the terminal accepts a failed status '69 83' and '69 84' in
response to VERIFY command and understands it as failed processing.
To ensure that the terminal sets the 'PIN Try Limit exceeded' bit in the
TVR to 1b, if an offline PIN is the selected CVM and the PIN is blocked
upon initial use of the VERIFY command.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 10.5.1 - Offline PIN Processing
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM list is 'Enciphered PIN verification performed by ICC' (04
00)
•
Case 01: LT returns status ''6983" in response to the Verify
Command
•
Case 02: LT returns status ''6984" in response to the Verify
Command
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 6 = '1' (ie PIN Try limit exceeded) received at 1st
GENERATE AC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification was not
successful) received at 1st GENERATE AC.
•
TSI byte 1, bit 7='1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 87
2CA.034.06 Failed Processing for VERIFY (3)
Test No: 2CA.034.06 - Revision 11 - Number of sub cases: 0
Objective: To ensure that the terminal accepts a status '63 Cx' in response to
VERIFY command and understands it as counter provided by 'x'.
If the terminal receives in response to VERIFY command a status '63 Cx'
during PIN encryption, and in case the terminal make another PIN
attempts, it goes back to step 1 of section 7.2 Book 2.
To ensure that the terminal displays a specific message and prompts for
another PIN entry if the VERIFY command returns 63 Cx and x is greater
than 0
Reference Book 2 - Section 7.2 - PIN Encipherment and Verification
EMV 4.3:
Book 3 - Section 6.3.5 - Coding of the Status Bytes
Book 3 - Section 10.5.1 - Offline PIN Processing
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM list is 'Enciphered PIN verification performed by ICC' (04
00)
•
LT returns status ''63C2" in response to the first Verify
command.
•
LT returns status "63C1" in response to the second Verify
command.
•
LT returns status "63C0" in response to the third Verify
command.
Action: Cardholder enters an invalid PIN three times.
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
Terminal shall display a specific message and shall prompt for
PIN entry for second and third tries
•
LT receives a second Get Challenge after the first Verify
command
•
The terminal understands there is no more PIN try left and stops
sending VERIFY commands after the third one.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 88
2CA.034.06 Failed Processing for VERIFY (3)
•
TVR byte 3, bit 6='1' (ie PIN Try Limited exceeded) received at
1st GENERATE AC.
•
TSI byte 1, bit 7='1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 89
2CA.034.07 Failed Processing for VERIFY (4)
Test No: 2CA.034.07 - Revision 11 - Number of sub cases: 2
Objective: To ensure that the terminal accepts a failed status '69 83' and '69 84' in
response to VERIFY command and understands it as failed processing.
To ensure that the terminal sets the 'PIN Try Limit exceeded' bit in the
TVR to 1b, if an offline PIN is the selected CVM and the PIN is blocked
upon initial use of the VERIFY command
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 10.5.1 - Offline PIN Processing
Terminal [Offline Plaintext PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Plaintext PIN verification by ICC' (01 00)
•
Case 01: LT returns status ''6983" in response to the Verify
Command
•
Case 02: LT returns status ''6984" in response to the Verify
Command
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 6 = '1' (ie PIN Try limit exceeded) received at 1st
GENERATE AC.
•
TSI byte 1, bit 7='1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 90
2CA.035.00 Status Word Processing for GENERATE AC
Test No: 2CA.035.00 - Revision 15 - Number of sub cases: 17
Objective: To ensure that the terminal rejects transaction if status in response to
GENERATE AC command is different from '90 00'
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 8.1 - Exception Handling
Terminal NA
Configuration:
Conditions:
•
Case 01: LT returns status value '62 83' in response to
GENERATE AC
•
Case 02: LT returns status value '63 00' in response to
GENERATE AC
•
Case 03: LT returns status value '63 Cx' in response to
GENERATE AC
•
Case 04: LT returns status value '69 83' in response to
GENERATE AC
•
Case 05: LT returns status value '69 84' in response to
GENERATE AC
•
Case 06: LT returns status value '69 85' in response to
GENERATE AC
•
Case 07: LT returns status value '6A 81' in response to
GENERATE AC
•
Case 08: LT returns status value '6A 82' in response to
GENERATE AC
•
Case 09: LT returns status value '6A 83' in response to
GENERATE AC
•
Case 10: LT returns status value '6A 88' in response to
GENERATE AC
•
Case 11: LT returns status value '90 01' in response to
GENERATE AC
•
Case 12: LT returns status value '64 00' in response to
GENERATE AC
•
Case 13: LT returns status value '65 00' in response to
GENERATE AC
•
Case 14: LT returns status value '6D 00' in response to
GENERATE AC
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 91
2CA.035.00 Status Word Processing for GENERATE AC
•
Case 15: LT returns status value '6E 00' in response to
GENERATE AC
•
Case 16: LT returns status value '6A 86' in response to
GENERATE AC
•
Case 17: LT returns status value '67 00' in response to
GENERATE AC
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal shall terminate the transaction.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 92
2CA.036.00 Status Word Processing for GET CHALLENGE
Test No: 2CA.036.00 - Revision 15 - Number of sub cases: 16
Objective: To ensure that the terminal continues to process the transaction if status
in response to GET CHALLENGE command is different from '90 00'.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 8.1 - Exception Handling
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM is 'Enciphered offline PIN verification, always' (04 00)
•
Case 01: LT returns status value '62 83' in response to GET
CHALLENGE
•
Case 02: LT returns status value '63 00' in response to GET
CHALLENGE
•
Case 03: LT returns status value '63 Cx' in response to GET
CHALLENGE
•
Case 04: LT returns status value '69 83' in response to GET
CHALLENGE
•
Case 05: LT returns status value '69 84' in response to GET
CHALLENGE
•
Case 06: LT returns status value '69 85' in response to GET
CHALLENGE
•
Case 07: LT returns status value '6A 81' in response to GET
CHALLENGE
•
Case 08: LT returns status value '6A 82' in response to GET
CHALLENGE
•
Case 09: LT returns status value '6A 83' in response to GET
CHALLENGE
•
Case 10: LT returns status value '6A 88' in response to GET
CHALLENGE
•
Case 11: LT returns status value '90 01' in response to GET
CHALLENGE
•
Case 12: LT returns status value '64 00' in response to GET
CHALLENGE
•
Case 13: LT returns status value '65 00' in response to GET
CHALLENGE
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 93
2CA.036.00 Status Word Processing for GET CHALLENGE
•
Case 14: LT returns status value '6D 00' in response to GET
CHALLENGE
•
Case 15: LT returns status value '6E 00' in response to GET
CHALLENGE
•
Case 16: LT returns status value '6A 86' in response to GET
CHALLENGE
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification was not
successful)
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 94
2CA.037.00 Status Word Processing for GET PROCESSING
OPTIONS
Test No: 2CA.037.00 - Revision 15 - Number of sub cases: 15
Objective: To ensure that the terminal terminates transaction if status in response
to GET PROCESSING OPTIONS command is different from '90 00' and
'69 85'.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 8.1 - Exception Handling
Terminal NA
Configuration:
Conditions:
•
Case 01: LT returns status value '62 83' in response to GET
PROCESSING OPTIONS
•
Case 02: LT returns status value '63 00' in response to GET
PROCESSING OPTIONS
•
Case 03: LT returns status value '63 Cx' in response to GET
PROCESSING OPTIONS
•
Case 04: LT returns status value '69 83' in response to GET
PROCESSING OPTIONS
•
Case 05: LT returns status value '69 84' in response to GET
PROCESSING OPTIONS
•
Case 06: LT returns status value '90 01' in response to GET
PROCESSING OPTIONS
•
Case 07: LT returns status value '6A 81' in response to GET
PROCESSING OPTIONS
•
Case 08: LT returns status value '6A 82' in response to GET
PROCESSING OPTIONS
•
Case 09: LT returns status value '6A 83' in response to GET
PROCESSING OPTIONS
•
Case 10: LT returns status value '6A 88' in response to GET
PROCESSING OPTIONS
•
Case 11: LT returns status value '65 00' in response to GET
PROCESSING OPTIONS
•
Case 12: LT returns status value '64 00' in response to GET
PROCESSING OPTIONS
•
Case 13: LT returns status value '6D 00' in response to GET
PROCESSING OPTIONS
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 95
2CA.037.00 Status Word Processing for GET PROCESSING
OPTIONS
•
Case 14: LT returns status value '6E 00' in response to GET
PROCESSING OPTIONS
•
Case 15: LT returns status value '67 00' in response to GET
PROCESSING OPTIONS
Action: NA
Procedure: Application in LT is selected and transaction is started with LT.
Pass Criteria: The terminal shall terminate the transaction.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 96
2CA.039.00 Status Word Processing for READ RECORD
Test No: 2CA.039.00 - Revision 15 - Number of sub cases: 16
Objective: To ensure that the terminal reject the transaction if status in response to
READ RECORD command sent outside application selection is different
from '90 00'
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 8.1 - Exception Handling
Terminal NA
Configuration:
Conditions:
•
LT returns the following status value in response to READ
RECORD during the Read Application Data phase:
•
Case 01: LT returns status value '6283' in response to READ
RECORD
•
Case 02: LT returns status value '63 00' in response to READ
RECORD
•
Case 03: LT returns status value '63 Cx' in response to READ
RECORD
•
Case 04: LT returns status value '69 83' in response to READ
RECORD
•
Case 05: LT returns status value '69 84' in response to READ
RECORD
•
Case 06: LT returns status value '69 85' in response to READ
RECORD
•
Case 07: LT returns status value '6A 81' in response to READ
RECORD
•
Case 08: LT returns status value '6A 82' in response to READ
RECORD
•
Case 09: LT returns status value '6A 88' in response to READ
RECORD
•
Case 10: LT returns status value '6A 83' in response to READ
RECORD
•
Case 11: LT returns status value '64 00' in response to READ
RECORD
•
Case 12: LT returns status value '65 00' in response to READ
RECORD
•
Case 13: LT returns status value '90 01' in response to READ
RECORD
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 97
2CA.039.00 Status Word Processing for READ RECORD
•
Case 14: LT returns status value '6D 00' in response to READ
RECORD
•
Case 15: LT returns status value '6E 00' in response to READ
RECORD
•
Case 16: LT returns status value '6A 86' in response to READ
RECORD
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT up to
the Read Application Data phase.
Pass Criteria: The terminal shall terminate the transaction.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 98
2CA.040.00 Status Word Processing for VERIFY
Test No: 2CA.040.00 - Revision 15 - Number of sub cases: 12
Objective: To ensure that the terminal rejects transaction if status in response to
VERIFY command is different from '90 00' and '63 Cx' '69 83' and '69
84'.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 8.1 - Exception Handling
Terminal ([Offline Plaintext
Configuration: supported)
Conditions:
PIN] supported OR [Offline Enciphered PIN]
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT supports Offline PIN verification.
•
Case 01: LT returns status value '62 83' in response to VERIFY
•
Case 02: LT returns status value '63 00' in response to VERIFY
•
Case 03: LT returns status value '69 85' in response to VERIFY
•
Case 04: LT returns status value '6A 81' in response to VERIFY
•
Case 05: LT returns status value '6A 82' in response to VERIFY
•
Case 06: LT returns status value '6A 83' in response to VERIFY
•
Case 07: LT returns status value '6A 88' in response to VERIFY
•
Case 08: LT returns status value '90 01' in response to VERIFY
•
Case 09: LT returns status value '64 00' in response to VERIFY
•
Case 10: LT returns status value '65 00' in response to VERIFY
•
Case 11: LT returns status value '6D 00' in response to VERIFY
•
Case 12: LT returns status value '6E 00' in response to VERIFY
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Cardholder verification).
Pass Criteria: The terminal shall terminate the transaction.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 99
2CA.041.00 Coding of Bits and Bytes RFU
Test No: 2CA.041.00 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that the terminal sets to zeroes data (bits and bytes) indicated
as RFU, unless otherwise stated. This applies particularly to TVR, TSI,
Terminal capabilities, additional capabilities, GENERATE AC reference
control parameter
Reference Book 3 - Section 6.3.6 - Coding of RFU Data
EMV 4.3:
Book 3 - Section 6.5.5.2 - Command Message
Book 4 - Section A2 - Terminal Capabilities
Book 4 - Section A3 - Additional Terminal Capabilities
Terminal NA
Configuration:
Conditions: NA
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
TVR : byte 1 - bits 2 to 1, byte 2 - bits 3 to 1, byte 3 - bits 2 to 1,
byte 4 - bits 3 to 1are set to ‘0’, received at 1st GENERATE AC.
•
TSI : byte 1 - bits 2 to 1, byte 2 - bits 8 to 1 are set to ‘0’,
received at 1st GENERATE AC.
•
Terminal Capabilities : byte 1 - bits 5 to 1, byte 2 - bits 3 to 1,
byte 3 - bits 3 to 1 and bit 5 are set to ‘0’, received at 1st
GENERATE AC.
•
Terminal Additional Capabilities : byte 2 - bits 7 to 1, byte 3 bits 4 to 1, byte 4 - bits 4 to 3 are set to ‘0’, received at 1st
GENERATE AC.
•
Reference control parameter of GENERATE AC received by LT
shall have bits 1, 2, 3, 4 and 6 set to ‘0’
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 100
2CA.041.01 Coding of Bits and Bytes RFU (2)
Test No: 2CA.041.01 - Revision 11 - Number of sub cases: 0
Objective: To ensure that the terminal sets to zeroes data (bits and bytes) indicated
as RFU, unless otherwise stated. This applies to VERIFY qualifier of the
Reference Data
Reference Book 3 - Section 6.3.6 - Coding of RFU Data
EMV 4.3:
Terminal [Offline Plaintext PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM is plaintext PIN always (01 00)
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Cardholder verification).
Pass Criteria:
•
VERIFY qualifier of the Reference Data received by the LT shall
have bits 4 to 1 set to ‘0’
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 101
2CA.041.02 Coding of Bits and Bytes RFU (3)
Test No: 2CA.041.02 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal sets to zeroes data (bits and bytes) indicated
as RFU, unless otherwise stated. This applies to VERIFY qualifier of the
Reference Data
Reference Book 3 - Section 6.3.6 - Coding of RFU Data
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM is enciphered PIN always (04 00)
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Cardholder verification).
Pass Criteria:
•
VERIFY qualifier of the Reference Data received by the LT shall
have bits 2 to 1 set to ‘0’
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 102
2CA.041.03 Coding of Bits and Bytes RFU (4)
Test No: 2CA.041.03 - Revision 4.1e - Number of sub cases: 0
Objective: To ensure that the terminal sets to zeroes data (bits and bytes) indicated
as RFU, and also understand LT data with RFU bits set to zeroes. This
applies to IAC and TAC.
Reference Book 3 - Section 6.3.6 - Coding of RFU Data
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
IACs and TACs RFU bits are set to '0'
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: Terminal shall not terminate the transaction and shall follow the IAC and
TAC setting and process the transaction until completion, by requesting
a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 103
2CA.041.04 Coding of Bits and Bytes RFU (5) (Implied)
Test No: 2CA.041.04 - Revision 10d - Number of sub cases: 0
Objective: To ensure that the terminal does not use the RFU bits, even when set to
'1'. This applies to IAC.
Reference Book 3 - Section 6.3.6 - Coding of RFU Data
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
IACs RFU bits are set to '1'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: Terminal shall ignore RFU bits set to ‘1’ and continue to process the
transaction as normal
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 104
2CA.041.05 Coding of Bits and Bytes RFU (5)
Test No: 2CA.041.05 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal understand LT data with RFU bits set to
zeroes. This applies to AFL.
Reference Book 3 - Section 6.3.6 - Coding of RFU Data
EMV 4.3:
Book 3 – Section 10.2 – Read Application Data
Book Bulletin – Section SB 140 – Clarification on the Format of AFL,
Byte 1
Terminal NA
Configuration:
Conditions:
•
The three least significant bits of the first byte of all AFL are set
to '0'
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal process the transaction until completion, by requesting a
TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 105
2CA.041.06 Coding of Bits and Bytes RFU (5)
Test No: 2CA.041.06 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal does not use the RFU bits, even when set to
'1'. This applies to AFL.
Reference Book 3 - Section 6.3.6 - Coding of RFU Data
EMV 4.3:
Book 3 – Section 10.2 – Read Application Data
Book Bulletin – Section SB 140 – Clarification on the Format of AFL,
Byte 1
Terminal NA
Configuration:
Conditions:
•
The three least significant bits of the first byte of all AFL are set
to '1'
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal process the transaction until completion, by requesting a
TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 106
2CA.054.00 Syntax of GENERATE AC returned Data Field (Format 1)
Test No: 2CA.054.00 - Revision 14 - Number of sub cases: 3
Objective: To ensure that the terminal is able to recognize the data field returned
by GENERATE AC command, encoded according to format 1 syntax and
in particular the order of the value field of Data Object included in the
returned Data field.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Case 01: Response to GENERATE AC includes only the
mandatory Data Objects and shall be encoded with format 1
(Template 80)
•
Case 02: Response to GENERATE AC includes the mandatory
Data Objects and the Issuer Application Data and shall be
encoded with format 1 (Template 80).
•
Case 03: Response to GENERATE AC includes the mandatory
Data Objects and the Issuer Application Data and shall be
encoded with format 1 (Template 80). Tag ‘80’ length is coded
on 2 bytes (81 xx).
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and interpret correctly the
format 1 syntax.
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
Values for Cryptogram Information Data, ATC, Application
Cryptogram, Issuer Application Data managed by the terminal
and included in authorization or financial requests or batch data
capture shall be in accordance with values sent back by the LT
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 107
2CA.054.01 Syntax of GENERATE AC returned Data Field (Format 1)
(2)
Test No: 2CA.054.01 - Revision 4.2b - Number of sub cases: 0
Objective: To ensure that the terminal terminates the transaction if data returned in
format 1 GENERATE AC response exceeds maximum length allowed.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Book Bulletin – Section SU 69 – Padding of BER-TLV Encoded
Constructed Data Objects
Terminal NA
Configuration:
Conditions:
•
Response to GENERATE AC includes the mandatory Data
Objects and the Issuer Application Data (32 bytes long) and
shall be encoded with format 1 (Template 80) with 5 bytes of
padding before the data objects.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall terminate the transaction.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 108
2CA.055.00 Syntax of GENERATE AC returned Data Field (Format 2)
Test No: 2CA.055.00 - Revision 14 - Number of sub cases: 4
Objective: To ensure that the terminal is able to recognize the data field returned
by GENERATE AC command, encoded according to format 2 syntax.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Case 01: Response to GENERATE AC includes only the
mandatory Data Objects and shall be encoded with format 2
(Template 77).
•
Case 02: Response to GENERATE AC includes the mandatory
Data Objects and the Issuer Application Data and shall be
encoded with format 2 (Template 77).
•
Case 03: Response to GENERATE AC includes the mandatory
Data Objects and the Issuer Application Data and shall be
encoded with format 2 (Template 77). Tag ‘77’ length is coded
on 2 bytes (81 xx).
•
Case 04: Response to GENERATE AC includes the mandatory
Data Objects, the Issuer Application Data and a proprietary
data object with a length such that the response length is
greater than 150 bytes and shall be encoded with format 2
(Template 77). Tag ‘77’ length is coded on 2 bytes (81 xx).
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and interpret correctly the
format 2 syntax.
•
The terminal shall run the transaction to completion according to
the LT's response to the GENERATE AC command.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 109
2CA.055.01 Syntax of GENERATE AC returned Data Field (Format 2)
Test No: 2CA.055.01 - Revision 4.1e - Number of sub cases: 4
Objective: To ensure that the terminal is able to recognize the data field returned
by GENERATE AC command, encoded according to format 2 syntax
with padding bytes 0x00 between 2 Data Elements in the Template.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Book Bulletin – Section SU 69 – Padding of BER-TLV Encoded
Constructed Data Objects
Terminal NA
Configuration:
Conditions:
•
Case 01: Response to GENERATE AC includes only the
mandatory Data Objects and shall be encoded with format 2
(Template 77) with a ‘00’ padding of 50 bytes between two data
•
Case 02: Response to GENERATE AC includes the mandatory
Data Objects and the Issuer Application Data and shall be
encoded with format 2 (Template 77) with a ‘00’ padding of 50
bytes after the last data.
•
Case 03: Response to GENERATE AC includes the mandatory
Data Objects and the Issuer Application Data and shall be
encoded with format 2 (Template 77). Tag ‘77’ length is coded
on 2 bytes (81 xx) with a ‘00’ padding of 50 bytes between two
data.
•
Case 04: Response to GENERATE AC includes the mandatory
Data Objects, the Issuer Application Data and a proprietary
data object with a length such that the response length is
greater than 150 bytes and shall be encoded with format 2
(Template 77). Tag ‘77’ length is coded on 2 bytes (81 xx) with
a ‘00’ padding of 50 bytes after the last data.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and interpret correctly the
format 2 syntax.
•
The terminal shall run the transaction to completion according to
the LT's response to the GENERATE AC command.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 110
2CA.056.00 Proprietary Data Object transmitted in Response to
GENERATE AC: Format 2
Test No: 2CA.056.00 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal ignores proprietary data object contained in
the response to the GENERATE AC command when response has
format 2.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal NA
Configuration:
Conditions: Response to GENERATE AC includes additionally 50 proprietary tags
including Tag DF09, DF10, DF11 and DF21 and shall be encoded with
format 2 (Template 77)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and ignore the format 2
proprietary data object in the response to the GENERATE AC
command.
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 111
2CA.058.00 Application Transaction Counter
Test No: 2CA.058.00 - Revision 11 - Number of sub cases: 0
Objective: To ensure that the terminal accepts the presence of a valid format of
Application Transaction Counter in response to the GENERATE AC
command.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
CDOL2 requests Application Transaction Counter
•
LT responds with ARQC to First GENERATE AC.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal process the transaction until completion.
•
The terminal will return the correct value of the ATC during
Second GENERATE AC as returned by the LT during First
GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 112
2CA.059.00 Application Cryptogram
Test No: 2CA.059.00 - Revision 11 - Number of sub cases: 0
Objective: To ensure that the terminal accepts the presence of a valid format of
Application Cryptogram in response to the GENERATE AC command.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Application Cryptogram can be a live data or test data
•
CDOL2 requests Application Cryptogram
•
LT to responds with ARQC to First GENERATE AC.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion.
•
The terminal will return the correct value of the Application
Cryptogram during Second GENERATE AC as returned by the
LT during First GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 113
2CA.060.00 Issuer Application Data
Test No: 2CA.060.00 - Revision 11 - Number of sub cases: 0
Objective: To ensure that the terminal accepts the presence of a valid format of
Issuer Application Data in response to the GENERATE AC command.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Response to GENERATE AC includes Issuer Application Data
•
CDOL2 requests Issuer Application Data
•
LT to responds with ARQC to First GENERATE AC.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion.
•
The terminal will return the correct value of the Issuer
Application Data during Second GENERATE AC as returned by
the LT during First GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 114
2CA.061.00 Cryptogram Information Data: AAC
Test No: 2CA.061.00 - Revision 11 - Number of sub cases: 4
Objective: To verify that the terminal interprets correctly answer to a GENERATE
AC command requesting the ICC to return an AAC.
To ensure that the terminal accepts the presence of a valid Cryptogram
Information Data in response to the GENERATE AC command.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
The LT response to the first GENERATE AC:
•
Case 01: LT responses an AAC without advice (00)
•
Case 02: LT responses an AAC with advice and no reason (08)
•
Case 03: LT responses an AAC with advice and reason is PIN
Try Limit exceeded (0A)
•
Case 04: LT responses an AAC with advice and reason is
Issuer authentication failed (0B)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT until
completion.
Pass Criteria: The terminal shall decline the transaction
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 115
2CA.062.00 Cryptogram Information Data: TC
Test No: 2CA.062.00 - Revision 11 - Number of sub cases: 4
Objective: To verify that the terminal interprets correctly answer to a GENERATE
AC command requesting the ICC to return a TC.
To ensure that the terminal accepts the presence of a valid Cryptogram
Information Data in response to the GENERATE AC command.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal [Offline Only or Offline/Online capable] supported
Configuration:
Conditions:
•
LT response to the first GENERATE AC:
•
Case 01: LT responses a TC without advice (40)
•
Case 02: LT responses a TC with advice and no reason (48)
•
Case 03: LT responses a TC with advice and reason is PIN Try
Limit exceeded (4A)
•
Case 04: LT responses a TC with advice and reason is Issuer
authentication failed (4B)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT until
completion.
Pass Criteria: The terminal shall approve the transaction offline
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 116
2CA.062.01 Cryptogram Information Data: TC (2)
Test No: 2CA.062.01 - Revision 11 - Number of sub cases: 4
Objective: To verify that the terminal interprets correctly answer to a GENERATE
AC command requesting the ICC to return a TC.
To ensure that the terminal accepts the presence of a valid Cryptogram
Information Data in response to the GENERATE AC command.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
LT response to the second GENERATE AC;
•
Case 01: LT responses a TC without advice (40)
•
Case 02: LT responses a TC with advice and no reason (48)
•
Case 03: LT responses a TC with advice and reason is PIN Try
Limit exceeded (4A)
•
Case 04: LT responses a TC with advice and reason is Issuer
authentication failed (4B)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT until
completion.
Pass Criteria: The terminal shall approve the transaction online
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 117
2CA.063.00 Cryptogram Information Data: ARQC
Test No: 2CA.063.00 - Revision 11 - Number of sub cases: 4
Objective: To verify that the terminal interprets correctly answer to a GENERATE
AC command requesting the ICC to return an ARQC
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
LT response to the first GENERATE AC:
•
Case 01: LT responses an ARQC without advice (80)
•
Case 02: LT responses an ARQC with advice and no reason
(88)
•
Case 03: LT responses an ARQC with advice and reason is PIN
Try Limit exceeded (8A)
•
Case 04: LT responses an ARQC with advice and reason is
Issuer authentication failed (8B)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT until
completion.
Pass Criteria: The terminal shall complete the transaction on line
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 118
2CA.064.00 Cryptogram Information Data: AAR
Test No: 2CA.064.00 - Revision 12 - Number of sub cases: 4
Objective: To verify that the terminal treats an answer to a GENERATE AC
command requesting the ICC to return an AAR as a logical error and
terminates the transaction
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005)
Terminal NA
Configuration:
Conditions: LT response to the first GENERATE AC:
•
Case 01: LT responses an AAR without advice (C0)
•
Case 02: LT responses an AAR with advice and no reason (C8)
•
Case 03: LT responses an AAR with advice and reason is PIN
Try Limit exceeded (CA)
•
Case 04: LT responses an AAR with advice and reason is
Issuer authentication failed (CB)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria: The terminal shall terminate the transaction
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 119
2CA.067.00 Cryptogram Information Data: PIN try limit exceeded
Test No: 2CA.067.00 - Revision 10 - Number of sub cases: 0
Objective: To verify that the terminal interprets correctly answer to a GENERATE
AC command requiring an Advice and indicating a PIN try limit
exceeded.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal [Advice] supported
Configuration:
Conditions:
•
The LT requests an AAC and requires an Advice in response to
the first GENERATE AC.
•
Reason indicated by LT is PIN try limit exceeded.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT until
completion.
Pass Criteria:
•
The terminal shall either transmit an on line advice or create an
offline advice.
•
Reason for decline included in Advice shall be PIN try limit
exceeded
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 120
2CA.068.00 Advice requested in the CID and unable to go online
Test No: 2CA.068.00 - Revision 13a - Number of sub cases: 2
Objective: When unable to go online, the transaction is not captured and the ICC
has requested Advice in the CID, the terminal terminates the transaction.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Book 4 - Section 12.2.5 - Advice Incidents
Terminal [Advice] supported AND [Online Data Capture] supported AND [Batch
Configuration: Data Capture] not supported
Conditions:
•
The terminal requests a TC or ARQC in the 1st GENERATE AC
•
Case 01: The LT responds with an ARQC requesting an advice
and no reason (CID = '88')
•
Case 02: LT responds with an ARQC requesting advice and
reason is PIN Try Limit exceeded (CID = '8A')
•
The terminal is unable to go online
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT until
completion.
Pass Criteria:
•
The terminal shall terminate the transaction
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 121
2CA.069.00 Advice requested in the CID and advice is unsupported
Test No: 2CA.069.00 - Revision 13 - Number of sub cases: 2
Objective: When advice is not supported, and the ICC has requested Advice in the
CID, the terminal ignores the advice request.
Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response Message
EMV 4.3:
Book 4 - Section 12.2.5 - Advice Incidents
Terminal [Advice] not supported
Configuration:
Conditions:
•
The terminal requests a TC or ARQC in the 1st GENERATE AC
•
Case 01: The LT responds with an ARQC requesting an advice
and no reason (CID = '88')
•
Case 02: LT responds with an ARQC requesting advice and
reason is PIN Try Limit exceeded (CID = '8A')
•
The terminal is unable to go online
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT until
completion.
Pass Criteria:
•
The terminal shall ignore the advice request and complete the
transaction
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 122
2CA.070.00 Syntax of GET DATA returned Data Field (ATC)
Test No: 2CA.070.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal is able to recognize the GET DATA when
ATC is requested during Terminal Risk Management.
To ensure that the terminal retrieves the ATC using the GET DATA
command when Lower and Upper consecutive Offline limits are present
in the card
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 6.5.7.1 - Definition and Scope
Book 3 - Section 7.3 - Data Retrievable by GET DATA Command
Terminal [Velocity Checking] supported
Configuration:
Conditions:
•
AIP of LT indicates TRM to be performed (AIP byte 1 bit 4 =‘1’).
•
LT contains Lower and Upper consecutive offline limits (for ATC
retrieval).
•
LT returns status '90 00' in response to GET DATA as well as a
valid response (ATC)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until the end
•
LT shall receive a GET DATA command (80 CA 9F 36)
•
TVR byte 1, bit 6 = '0' (ie ICC Data not Missing) received at 1st
GENERATE AC.
•
TSI Byte 1, bit 4=1 (ie Terminal risk Management was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 123
2CA.071.00 Syntax of GET DATA returned Data Field (LOATC)
Test No: 2CA.071.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal is able to recognize the data field returned
by GET DATA command when LOATC is requested during Terminal
Risk Management.
To ensure that the terminal retrieves the ATC using the GET DATA
command.
Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes
EMV 4.3:
Book 3 - Section 6.5.7.1 - Definition and Scope
Book 3 - Section 7.3 - Data Retrievable by GET DATA Command
Terminal [Velocity Checking] supported
Configuration:
Conditions:
•
AIP of LT indicates TRM to be performed (AIP byte 1 bit 4 =‘1’).
•
LT contains Lower and Upper consecutive offline limits (for
LOATC retrieval).
•
LT returns status '90 00' in response to GET DATA as well as a
valid response (LOATC)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until the end
•
LT shall receive a GET DATA command (80 CA 9F 13)
•
TVR byte 1, bit 6 = '0' (ie ICC Data not Missing) received at 1st
GENERATE AC.
•
TSI Byte 1, bit 4=1 (ie Terminal risk Management was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 124
2CA.072.00 Syntax of GET DATA returned Data Field (PIN try limit) Terminal Behaviour When PIN Try Counter Equals 0
Test No: 2CA.072.00 - Revision 12 - Number of sub cases: 0
Objective: To ensure that the terminal is able to recognize the data field returned
by GET DATA command when PIN try limit is requested during Offline
plaintext PIN verification.
To ensure that the terminal sets the 'PIN Try Limit exceeded' in the TVR
to 1b, and continue the processing of CVM, if PIN Try counter returned
by GET DATA is 0
Reference Book 3 - Section 6.5.7.1 - Definition and Scope
EMV 4.3:
Book 4 - Section 6.3.4.1 - Offline CVM
Terminal ([Get Data for PIN Try Counter] supported AND [Offline Plaintext PIN]
Configuration: supported)
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Plaintext PIN verification by ICC' (41 00) followed
by 'Fail CVM, always' (00 00).
•
PIN try counter = 0
•
LT returns status '90 00' in response to GET DATA as well as a
valid response (PIN try Counter)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC or an AAC.
•
Terminal shall not display any specific message regarding the
PIN Try counter.
•
TVR byte 3, bit 6 = '1' (ie PIN Try limit exceeded) received at 1st
GENERATE AC.
•
TSI Byte 1, bit 7=1 (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
CVM Results show 'Fail CVM, always, process is failed' as the
last CVM processed ('00 00 01'), received at 1st GENERATE
AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 125
2CA.072.01 Syntax of GET DATA returned Data Field (PIN try limit) Terminal Behaviour When PIN Try Counter Equals 0 (2)
Test No: 2CA.072.01 - Revision 12 - Number of sub cases: 0
Objective: To ensure that the terminal is able to recognize the data field returned
by GET DATA command when PIN try limit is requested during Offline
enciphered PIN verification.
To ensure that the terminal sets the 'PIN Try Limit exceeded' in the TVR
to 1b, and continue the processing of CVM, if PIN Try counter returned
by GET DATA is 0
Reference Book 3 - Section 6.5.7.1 - Definition and Scope
EMV 4.3:
Book 4 - Section 6.3.4.1 - Offline CVM
Terminal ([Get Data for PIN Try Counter] supported AND [Offline Enciphered PIN]
Configuration: supported)
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN verification performed by ICC
always' (44 00) followed by 'Fail CVM, always' (00 00).
•
PIN try counter = 0
•
LT returns status '90 00' in response to GET DATA as well as a
valid response (PIN try Counter)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC or an AAC.
•
Terminal shall not display any specific message regarding the
PIN Try counter.
•
TVR byte 3, bit 8 = ‘1’ (ie Cardholder verification was not
successful)
•
TVR byte 3, bit 6 = '1' (ie PIN Try limit exceeded) received at 1st
GENERATE AC.
•
TSI Byte 1, bit 7=1 (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
CVM Results show 'Fail CVM, always, process is failed' as the
last CVM processed ('00 00 01'), received at 1st GENERATE
AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 126
2CA.074.00 Syntax of GET PROCESSING OPTIONS Data Field
(PDOL)
Test No: 2CA.074.00 - Revision 10c - Number of sub cases: 3
Objective: To ensure that the terminal issues a GET PROCESSING OPTIONS
command if PDOL is present in the FCI of the Application Definition File
of the card with a data field populated with a constructed data object with
a tag of '83', a length field with appropriate length and, a value field of
concatenated data elements coded according to the PDOL.
To ensure that the terminal supports valid PDOL.
Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
EMV 4.3:
Book 3 - Section 6.5.8.3 - Data Field Sent in the Command Message
Book 3 - Section 10.1 - Initiate Application Processing
Terminal NA
Configuration:
Conditions:
•
Case 01: PDOL contains TVR and TSI
•
Case 02: PDOL returned by LT contains TVR, TSI and Terminal
capabilitie
•
Case 03: PDOL returned by LT contains Terminal serial number
and TVR
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The LT shall receive a GET PROCESSING OPTIONS data field
(associated to the GET PROCESSING OPTIONS command field) with
the correct syntax: data object containing value fields of Data Object
requested introduced by Tag '83'
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 127
2CA.075.00 Syntax of GET PROCESSING OPTIONS Data Field (no
PDOL)
Test No: 2CA.075.00 - Revision 10c - Number of sub cases: 0
Objective: To ensure that if PDOL is not present in the FCI of selected ADF, the
terminal sends the GET PROCESSING OPTIONS command with a data
field populated with a constructed data object with a tag of '83', and a
length 0
Reference Book 3 - Section 6.5.8.3 - Data Field Sent in the Command Message
EMV 4.3:
Book 3 - Section 10.1 - Initiate Application Processing
Terminal NA
Configuration:
Conditions: PDOL is not returned in the FCI of the selected ADF
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The LT shall receive a GET PROCESSING OPTIONS data field
(associated to the GET PROCESSING OPTIONS command field) with
the correct syntax: data object with length = 0 and Tag '83'
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 128
2CA.076.00 Syntax of GET PROCESSING OPTIONS Data Field:
PDOL empty (implied)
Test No: 2CA.076.00 - Revision 10c - Number of sub cases: 0
Objective: To ensure that if PDOL is empty in the FCI of selected ADF, the terminal
sends the GET PROCESSING OPTIONS command with a data field
populated with a constructed data object with a tag of '83', and a length
0
Reference Book 3 - Section 6.5.8.3 - Data Field Sent in the Command Message
EMV 4.3:
Book 3 - Section 10.1 - Initiate Application Processing
Terminal NA
Configuration:
Conditions: PDOL is returned in the FCI of the selected ADF and is empty
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The LT shall receive a GET PROCESSING OPTIONS data field
(associated to the GET PROCESSING OPTIONS command field) with
the correct syntax: data object with length = 0 and Tag '83'
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 129
2CA.077.00 Syntax of GPO returned Data Field: Format 1
Test No: 2CA.077.00 - Revision 14 - Number of sub cases: 3
Objective: To ensure that the terminal is able to recognize the data field returned
by GET PROCESSING OPTIONS command, encoded according to
format 1.
Reference Book 3 - Section 6.5.8.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
CDOL 1 requests AIP
•
Case 01: Response to GET PROCESSING OPTIONS contains
valid AIP and AFL encoded with format 1 (Template 80).
•
Case 02: Response to GET PROCESSING OPTIONS contains
valid AIP and AFL encoded with format 1 (Template 80), Tag
‘80’ length is coded on 2 bytes (81 xx).
•
Case 03: Response to GET PROCESSING OPTIONS contains
valid AIP and AFL encoded with format 1 (Template 80), Tag
‘80’ length is coded on 2 bytes (81 xx). AFL as a length such
that total length is greater than 150 bytes.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC or an AAC.
•
Value of AIP in GENERATE AC command shall be in
accordance with the value sent back by the LT.
•
LT shall receive READ RECORD commands in accordance to
AFL
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 130
2CA.077.01 Syntax of GPO returned Data Field: Format 1 (2)
Test No: 2CA.077.01 - Revision 4.1e - Number of sub cases: 2
Objective: To ensure that the terminal is able to recognize the data field returned
by GET PROCESSING OPTIONS command, encoded according to
format 1 and that a terminal terminates transaction, if there are padding
with bytes 0x00 between 2 Data Elements in the Template.
Reference Book 3 - Section 6.5.8.4 - Data Field Returned in the Response Message
EMV 4.3:
Book Bulletin – Section SU 69 – Padding of BER-TLV Encoded
Constructed Data Objects
Terminal NA
Configuration:
Conditions:
•
Case 01: Response to GET PROCESSING OPTIONS contains
valid AIP and AFL encoded with format 1 (Template 80),
followed by 5 bytes of ‘00’ value padding (within ‘80’ template).
•
Case 02: Response to GET PROCESSING OPTIONS contains
valid AIP and AFL encoded with format 1 (Template 80), with 5
bytes of ‘00’ value padding between AIP and AFL.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall terminate the transaction.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 131
2CA.078.00 Syntax of GPO returned Data Field: Format 2
Test No: 2CA.078.00 - Revision 4.1e - Number of sub cases: 6
Objective: To ensure that the terminal is able to recognize the data field returned
by GET PROCESSING OPTIONS command, encoded according to
format 2.
Reference Book 3 - Section 6.5.8.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
CDOL 1 requests AIP
•
Case 01: Response to GET PROCESSING OPTIONS contains
valid AIP and AFL encoded with format 2 (Template 77).
•
Case 02: Response to GET PROCESSING OPTIONS contains
valid AIP and AFL encoded with format 2 (Template 77). Tag
‘77’ length is coded on 2 bytes (81 xx).
•
Case 03: Response to GET PROCESSING OPTIONS contains
valid AIP and AFL encoded with format 2 (Template 77). Tag
‘77’ length is coded on 2 bytes (81 xx). AFL as a length such
that total length is greater than 150 bytes.
•
Case 04: Response to GET PROCESSING OPTIONS contains
valid AIP, AFL and reserved EMV data (tag ‘9F30’, with a length
of 10 bytes) encoded with format 2 (Template 77).
•
Case 05: Response to GET PROCESSING OPTIONS contains
valid AIP, AFL and reserved EMV data (tag ‘9F24’, with a length
of 50 bytes) encoded with format 2 (Template 77). Tag ‘77’
length is coded on 2 bytes (81 xx).
•
Case 06: Response to GET PROCESSING OPTIONS contains
valid AIP, AFL and reserved EMV data (tag ‘9F28’, with a length
of 150 bytes) encoded with format 2 (Template 77). Tag ‘77’
length is coded on 2 bytes (81 xx).
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC or an AAC.
•
Value of AIP in GENERATE AC command shall be in
accordance with the value sent back by the LT.
•
LT shall receive READ RECORD commands in accordance to
AFL
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 132
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 133
2CA.078.01 Syntax of GPO returned Data Field: Format 2 (2)
Test No: 2CA.078.01 - Revision 4.1e - Number of sub cases: 2
Objective: To ensure that the terminal is able to recognize the data field returned
by GET PROCESSING OPTIONS command, encoded according to
format 2 and that a terminal ignores the padding, if there are padding
with bytes 0x00 between 2 Data Elements.
Reference Book 3 - Section 6.5.8.4 - Data Field Returned in the Response Message
EMV 4.3:
Book Bulletin – Section SU 69 – Padding of BER-TLV Encoded
Constructed Data Objects
Terminal NA
Configuration:
Conditions:
•
Case 01: Response to GET PROCESSING OPTIONS contains
valid AIP and AFL encoded with format 2 (Template 77),
followed by 10 bytes of ‘00’ value padding (within ‘77’ template).
•
Case 02: Response to GET PROCESSING OPTIONS contains
valid AIP and AFL encoded with format 2 (Template 77), with 50
bytes of ‘00’ value padding between AIP and AFL..
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC or an AAC.
•
Value of AIP in GENERATE AC command shall be in
accordance with the value sent back by the LT.
•
LT shall receive READ RECORD commands in accordance to
AFL
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 134
2CA.082.00 Syntax of INTERNAL AUTHENTICATE Data Field
Test No: 2CA.082.00 - Revision 10 - Number of sub cases: 0
Objective: To ensure that the terminal issues an INTERNAL AUTHENTICATE
command with a Dynamic Data Authentication Data Object List (DDOL)
Reference Book 3 - Section 6.5.9.3 - Data Field Sent in the Command Message
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
LT contains DDOL and all data needed for Dynamic Data
Authentication as defined in Book 2
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The LT shall receive an INTERNAL AUTHENTICATE data field
(associated to the INTERNAL AUTHENTICATE command field) with the
correct syntax: data object containing value fields of Data Object
requested in DDOL
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 135
2CA.083.00 Syntax of INTERNAL AUTHENTICATE returned Data
Field: Format 1
Test No: 2CA.083.00 - Revision 14 - Number of sub cases: 3
Objective: To ensure that the terminal is able to recognize the data field returned
by INTERNAL AUTHENTICATE command, encoded according to format
1
Reference Book 3 - Section 6.5.9.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
LT contains DDOL and all data needed for Dynamic Data
Authentication as defined in Book 2.
•
Case 01: LT response to INTERNAL AUTHENTICATE shall be
a correct cryptogram encoded with format 1 (template 80).
•
Case 02: LT response to INTERNAL AUTHENTICATE shall be
a correct cryptogram encoded with format 1 (template 80). Tag
‘80’ length is coded on 2 bytes (81 xx).
•
Case 03: LT response to INTERNAL AUTHENTICATE shall be
a correct cryptogram encoded with format 1 (template 80). Tag
‘80’ length is coded on 2 bytes (81 xx). ICC public key has a
length longer then 150 bytes.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 136
2CA.084.00 Syntax of INTERNAL AUTHENTICATE returned Data
Field: Format 2
Test No: 2CA.084.00 - Revision 4.1e - Number of sub cases: 6
Objective: To ensure that the terminal is able to recognize the data field returned
by INTERNAL AUTHENTICATE command, encoded according to format
2
Reference Book 3 - Section 6.5.9.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
LT contains DDOL and all data needed for Dynamic Data
Authentication as defined in Book 2
•
Case 01: LT response to INTERNAL AUTHENTICATE is a
correct cryptogram encoded with format 2 (template 77).
•
Case 02: LT response to INTERNAL AUTHENTICATE shall be
a correct cryptogram encoded with format 2 (template 77). Tag
‘77’ length is coded on 2 bytes (81 xx).
•
Case 03: LT response to INTERNAL AUTHENTICATE shall be
a correct cryptogram encoded with format 2 (template 77). Tag
‘77’ length is coded on 2 bytes (81 xx). ICC public key has a
length longer then 150 bytes.
•
Case 04: LT response to INTERNAL AUTHENTICATE is a
correct cryptogram and reserved EMV data (tag ‘9F30’, with a
length of 10 bytes) encoded with format 2 (template 77).
•
Case 05: LT response to INTERNAL AUTHENTICATE shall be
a correct cryptogram and reserved EMV data (tag ‘9F24’, with a
length of 50 bytes) encoded with format 2 (template 77). Tag
‘77’ length is coded on 2 bytes (81 xx).
•
Case 06: LT response to INTERNAL AUTHENTICATE shall be
a correct cryptogram and reserved EMV data (tag ‘9F28’, with a
length of 50 bytes) encoded with format 2 (template 77). Tag
‘77’ length is coded on 2 bytes (81 xx). ICC public key has a
length longer then 150 bytes.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 137
2CA.084.00 Syntax of INTERNAL AUTHENTICATE returned Data
Field: Format 2
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 138
2CA.084.01 Syntax of INTERNAL AUTHENTICATE returned Data
Field: Format 2 (2)
Test No: 2CA.084.01 - Revision 4.1e - Number of sub cases: 2
Objective: To ensure that the terminal is able to recognize the data field returned
by INTERNAL AUTHENTICATE command, encoded according to format
2 and that a terminal ignores the padding, if there are padding with bytes
0x00 between 2 Data Elements in a Template containing ‘00’ of padding.
Reference Book 3 - Section 6.5.9.4 - Data Field Returned in the Response Message
EMV 4.3:
Book Bulletin – Section SU 69 – Padding of BER-TLV Encoded
Constructed Data Objects
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
LT contains DDOL and all data needed for Dynamic Data
Authentication as defined in Book 2
•
Case 01: LT response to INTERNAL AUTHENTICATE is a
correct cryptogram encoded with format 2 (template 77)
followed by 10 bytes of ‘00’ value padding (within ‘77’ template).
•
Case 02: LT response to INTERNAL AUTHENTICATE is a
correct cryptogram encoded with format 2 (template 77)
followed by 50 bytes of ‘00’ value padding (within ‘77’ template)
and followed by a proprietary data.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 139
2CA.089.00 Syntax of READ RECORD returned Data Field
Test No: 2CA.089.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal is able to recognize the data field returned
by READ RECORD command.
Reference Book 1 - Section 11.2.4 - Data Field Returned in the Response Message
EMV 4.3:
Book 3 - Section 6.5.11.4 - Data Field Returned in the Response
Message
Terminal NA
Configuration:
Conditions:
•
AFL is not empty.
•
CDOL1 requests PAN and Application Expiration date.
•
All mandatory data objects are present in the LT.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC or an AAC.
•
Values of PAN and Application Expiration date shall be in
accordance of the value returned by the LT.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 140
2CA.092.00 Syntax of SELECT Data Field
Test No: 2CA.092.00 - Revision 10g - Number of sub cases: 0
Objective: To verify that the terminal is able to transmit a proper encoding of the
SELECT data field
Reference Book 1 - Section 11.3.3 - Data Field Sent in the Command Message
EMV 4.3:
Terminal NA
Configuration:
Conditions: No specific conditions
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria: The LT shall receive a SELECT data field (associated to the SELECT
command field) containing the AID of selected application
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 141
2CA.093.00 Syntax of SELECT PSE returned Data Field
Test No: 2CA.093.00 - Revision 11 - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, it is able to
recognize the FCI returned Data field of the SELECT PSE command
Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
LT contains a PSE
•
FCI of PSE contains all mandatory data field: FCI Template
(‘6F’), DF Name (‘84’), FCI Proprietary Template ‘A5’, SFI of the
Directory File (‘88’)
•
FCI of PSE contains all optional data objects: Language
Preference (‘5F 2D’), Issuer Code Table Index (‘9F 11’), FCI
Issuer discretionary Data (tag BF0C) of PSE contains data
fields: '5F54' Bank Identifier Code (BIC), '5F53' International
Bank Account Number (IBAN), '5F55' Issuer Country Code
(alpha 2), '5F56' Issuer Country Code (alpha 3) and '42' Issuer
Identifier Number.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC or an AAC.
•
LT shall receive a READ RECORD command with SFI coded
according to data returned in FCI
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 142
2CA.094.00 Syntax of SELECT PSE returned Data Field: no optional
data
Test No: 2CA.094.00 - Revision 11 - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, it accepts PSE
with no optional data objects returned.
Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
LT contains a PSE
•
FCI of PSE contains all mandatory but no optional data fields:
FCI Template (‘6F’), DF Name (‘84’), FCI Proprietary Template
‘A5’, SFI of the Directory File (‘88’)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC or an AAC.
•
The terminal shall either propose a choice of supported
languages or use the default language if it supports only one
•
LT shall receive a READ RECORD command with SFI coded
according to data returned in FCI
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 143
2CA.097.00 Syntax of SELECT ADF returned Data Field
Test No: 2CA.097.00 - Revision 4.2a - Number of sub cases: 0
Objective: To ensure that the terminal is able to recognize the data field returned
by SELECT ADF command.
Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response
EMV 4.3: Messagebul
Terminal NA
Configuration:
Conditions:
•
LT contains an ADF
•
FCI of ADF contains all mandatory fields:FCI template (‘6F’), DF
Name (‘84’), FCI Proprietary Template (‘A5’), Application Label
(‘50’)
•
FCI of ADF contains all optional data objects: Application
Priority Indicator (‘87’), PDOL (‘9F38’), Language Preference
(‘5F 2D’), Issuer Code Table Index (‘9F 11’), Application
Preferred Name (‘9F 12’) and FCI issuer Discretionary Data
(‘BF 0C’) containing: ‘9F 4D’ '5F54' Bank Identifier Code (BIC),
'5F53' International Bank Account Number (IBAN), '5F55' Issuer
Country Code (alpha 2), '5F56' Issuer Country Code (alpha 3),
and '42' Issuer Identifier Number.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 144
2CA.098.00 Syntax of SELECT ADF returned Data Field: optional
data
Test No: 2CA.098.00 - Revision 4.2a - Number of sub cases: 0
Objective: To ensure that the terminal accepts the absence of optional data objects
in the data field returned by SELECT ADF command.
Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
LT contains an ADF
•
FCI of ADF contains all mandatory but no optional data fields:
FCI template (‘6F’), DF Name (‘84’), FCI Proprietary Template
with Application Label
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria: The terminal shall accept the card and process the transaction until
completion, by requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 145
2CA.099.00 Response to Proprietary Data in FCI from a SELECT
ADF
Test No: 2CA.099.00 - Revision 4.2b - Number of sub cases: 4
Objective: To ensure that the terminal ignores the presence of proprietary data
objects in the data field returned by SELECT ADF command.
Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
LT contains an ADF
•
Case 01: FCI (tag 6F) of ADF contains additional proprietary
data fields within the FCI template
•
Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF
contains proprietary data field: tag 9F 7E with max length and
any value
•
Case 03: FCI (tag 6F) of ADF contains Issuer Country Code
data object
•
Case 04: FCI Issuer discretionary Data (tag BF0C) of ADF
contains Issuer Country Code data object (tag 5F55)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall ignore the unrecognised or additional EMV
data objects
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 146
2CA.099.01 Response to Proprietary Data in FCI from a SELECT
PSE
Test No: 2CA.099.01 - Revision 4.2b - Number of sub cases: 5
Objective: To ensure that if the terminal supports selection with PSE, the terminal
ignores the presence of proprietary data objects in the data field returned
by SELECT PSE command.
Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
LT contains a PSE.
•
Case 01: FCI (tag 6F) of PSE contains additional proprietary
data fields.
•
Case 02: FCI Issuer discretionary Data (tag BF0C) of PSE
contains proprietary data field: tag 5F 50 with any length and
any value.
•
Case 03: FCI (tag 6F) of PSE contains Issuer Country Code
data object.
•
Case 04: FCI Issuer discretionary Data (tag BF0C) of PSE
contains Issuer Country Code data object (tag 5F55).
•
Case 05: FCI Issuer discretionary Data (tag BF0C) of PSE
contains data fields: '5F54' Bank Identifier Code (BIC), '5F53'
International Bank Account Number (IBAN), '5F55' Issuer
Country Code', '5F56' Issuer Country Code, and '42' Issuer
Identifier Number.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall ignore the unrecognised or additional EMV
data objects.
•
The terminal shall perform the application selection process with
PSE and process the transaction until completion, by requesting
a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 147
2CA.100.01 Additional data object facilitating domestic processing
in selection with PSE
Test No: 2CA.100.01 - Revision 4.2b - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, the terminal
ignores or uses the presence of Additional data objects facilitating
domestic processing in the selection by PSE.
Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response Message
EMV 4.3:
Book 1 - Section 12.2.3 - Coding of a Payment System Directory
Terminal [PSE] supported
Configuration:
Conditions:
•
LT contains a PSE.
•
Directory Discretionary template (‘73’ template) of the ADF entry
contains data fields: '5F54' Bank Identifier Code (BIC), '5F53'
International Bank Account Number (IBAN), '5F55' Issuer
Country Code', '5F56' Issuer Country Code, '42' Issuer Identifier
Number.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall perform the application selection process with
PSE and process the transaction until completion, by requesting
a TC or an AAC.
•
Additional data objects facilitating domestic processing are
either ignored or used by the terminal.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 148
2CA.103.00 Syntax of VERIFY Data Field for option plaintext offline
PIN
Test No: 2CA.103.00 - Revision 10g - Number of sub cases: 9
Objective: To ensure that the terminal issues a VERIFY command with a Plain Text
Offline PIN Block in the data field when CVM option is Plaintext PIN.
To ensure that the terminal issues a VERIFY command with value field
of tag 99 in the data field.
Reference Book 3 - Section 6.5.12.2 - Command Message
EMV 4.3:
Book 3 - Section 6.5.12.3 - Data Field Sent in the Command Message
Terminal [Offline Plaintext PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT support Offline PIN Verification.
•
CVM in LT is 'Plaintext PIN verification performed by ICC,
always' (01 00).
•
Case 01: PIN length is 4.
•
Case 02: PIN length is 5.
•
Case 03: PIN length is 6.
•
Case 04: PIN length is 7.
•
Case 05: PIN length is 8.
•
Case 06: PIN length is 9.
•
Case 07: PIN length is 10.
•
Case 08: PIN length is 11.
•
Case 09: PIN length is 12.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT for all
PIN lengths tested.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The LT shall receive a VERIFY data field (associated to the
VERIFY command field) with the correct syntax as defined in
Book 3 Section 2.5.12.2 with the value field of tag 99 (without
Tag and Length).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 149
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 150
2CA.103.01 Syntax of VERIFY Data Field for Enciphered offline PIN
Test No: 2CA.103.01 - Revision 10g - Number of sub cases: 9
Objective: To ensure that the terminal issues a VERIFY command with the
Enciphered PIN Data (as specified in Table 21, Book 2) in the data field
when CVM option is Enciphered PIN.
To ensure that if the terminal supports offline PIN encryption, it is able to
encrypt the PIN data using the recovery function specified in Book 2.
To ensure that the terminal issues a VERIFY command with value field
of tag 99 in the data field
Reference Book 2 - Section 7.2 - PIN Encipherment and Verification
EMV 4.3:
Book 3 - Section 6.5.12.2 - Command Message
Book 3 - Section 6.5.12.3 - Data Field Sent in the Command Message
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT support Enciphered PIN Verification.
•
CVM is 'Offline Enciphered PIN Verification, always' (04 00).
•
Case 01: PIN length is 4.
•
Case 02: PIN length is 5.
•
Case 03: PIN length is 6.
•
Case 04: PIN length is 7.
•
Case 05: PIN length is 8.
•
Case 06: PIN length is 9.
•
Case 07: PIN length is 10.
•
Case 08: PIN length is 11.
•
Case 09: PIN length is 12.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT for all
PIN lengths tested.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The LT shall receive a VERIFY data field (associated to the
VERIFY command field) with the correct syntax as defined in
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 151
2CA.103.01 Syntax of VERIFY Data Field for Enciphered offline PIN
Book 3 Section 2.5.12.2 and Book 2 Table 21 with the value
field of tag 99 (without Tag and Length).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 152
2CA.108.00 Syntax of GET CHALLENGE returned Data Field
Test No: 2CA.108.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal is able to recognize the data field returned
by GET CHALLENGE command.
Reference Book 3 - Section 6.5.6.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT supports Offline enciphered PIN Verification.
•
CVM is 'Offline enciphered PIN Verification, always' (04 00).
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC or an AAC.
•
Terminal issues GET CHALLENGE command prior to issuing
VERIFY command.
•
The LT shall receive a VERIFY command containing, once
decrypted by LT, unpredictable number sent previously through
the GET CHALLENGE command.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 153
2CA.109.00 Maximum Data Length
Test No: 2CA.109.00 - Revision 4.1e - Number of sub cases: 0
Objective: To ensure that the terminal is able to support the maximum data length
of each data as specified in Book 3 annex A.
Reference Book 3 - Section Annex A – Data Elements Dictionary
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
All terminal data have their maximum length
•
FCI template has the maximum Length (252 bytes), containing
all mandatory and optional data (excluding FCI Issuer
discretionary data):
o AID of LT is 16 bytes,
o Application preferred name is 16 bytes,
o Application Label is 16 bytes,
o LT contains 4 languages preferences in tag ‘5F2D’
o PDOL has a length so that the FCI Proprietary Template
reach the maximum length and that the length of the
data to be send in the GET PROCESSING OPTIONS
is > 128 bytes.
•
CDOL1 requests all terminal data and other data (if any needed)
to reach the maximum length (255 bytes) to send in
.GENERATE AC command.
•
Each record contain a single data element (one record one
data) and all optional data must present.
•
All others card data (one by record) with variable length must be
such that they reach the maximum length and that the record is
‘00’ padded to reach 254 bytes.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 154
2CA.110.00 Maximum Data Length: CVM List
Test No: 2CA.110.00 - Revision 4.1e - Number of sub cases: 0
Objective: To ensure that the terminal is able to support the maximum data length
of each data as specified in Book 3 annex A.
Reference Book 3 - Section Annex A – Data Elements Dictionary
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
All terminal data have their maximum length
•
FCI template has the maximum Length (252 bytes), containing
all mandatory and optional data (excluding FCI Issuer
discretionary data):
o AID of LT is 16 bytes,
o Application preferred name is 16 bytes,
o Application Label is 16 bytes,
o LT contains 4 languages preferences in tag ‘5F2D’
o PDOL has a length so that the FCI Proprietary Template
reach the maximum length and that the length of the
data to be send in the GET PROCESSING OPTIONS
is > 128 bytes.
•
CDOL1 requests all terminal data and other data (if any needed)
to reach the maximum length (255 bytes) to send in
.GENERATE AC command
•
Each record contain a single data element (one record one
data) and all optional data must present.
•
CVM list length is 248 bytes (120 rules), where the last rule
apply.
•
All others card data (one by record) with variable length must be
such that they reach the maximum length and that the record is
‘00’ padded to reach 254 bytes.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 155
2CA.111.00 Maximum Data Length: Issuer Script Commands
Test No: 2CA.111.00 - Revision 4.1e - Number of sub cases: 0
Objective: To ensure that the terminal is able to support the maximum data length
of each data as specified in Book 3 annex A, in particular an Issuer Script
Command
Reference Book 3 - Section Annex A – Data Elements Dictionary
EMV 4.3:
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
FCI template has the maximum Length (252 bytes), containing
all mandatory and optional data (excluding FCI Issuer
discretionary data):
o AID of LT is 16 bytes,
o Application preferred name is 16 bytes,
o Application Label is 16 bytes,
o LT contains 4 languages preferences in tag ‘5F2D’
o PDOL has a length so that the FCI Proprietary Template
reach the maximum length and that the length of the
data to be send in the GET PROCESSING OPTIONS
is > 128 bytes.
•
CDOL1 requests all terminal data and other data (if any needed)
to reach the maximum length (255 bytes) to send in
.GENERATE AC command
•
Each record contain a single data element (one record one
data) and all optional data must present..
•
All others card data (one by record) with variable length must be
such that they reach the maximum length and that the record is
‘00’ padded to reach 254 bytes.
•
LT returns an ARQC in response to first GENERATE AC.
•
Authorization response message contains one Issuer script with
tag ’71’ containing one command where the length = Maximum
Script length supported by the device (minimum 128 bytes) –
script header(tags and Length). With a maximum of 261 bytes.
•
LT returns '90 00' to script command
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 156
2CA.111.00 Maximum Data Length: Issuer Script Commands
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The LT shall receive the script command according to the script
contained in the authorization response before the second
GENERATE AC.
•
TVR byte 5, bit 6 = '0' (ie Script processing succeeded before
final GENERATE AC) received at 2nd GENERATE AC.
•
TVR byte 5, bit 5 = '0' (ie Script processing after final
GENERATE AC not used) contained in Financial Confirmation
message or Batch Data Capture message
•
TSI byte 1, bit 3 = '1' (ie Script processing was performed)
received at 2nd GENERATE AC.
•
Issuer Script Results for 1st script with Tag 71, Byte 1 shall be
set to '20', script processing successful, contained in Financial
Confirmation message or Batch Data Capture message
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 157
2CA.112.00 Maximum Data Length: Issuer Script
Test No: 2CA.112.00 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal is able to manage and perform scripts if it
receives one or several scripts with the total length is less than or equal
to 128 bytes (or device limit if above 128 bytes) in authorization or
financial response
Reference Book 3 - Section Annex A – Data Elements Dictionary
EMV 4.3:
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
FCI template has the maximum Length (252 bytes), containing
all mandatory and optional data (excluding FCI Issuer
discretionary data):
o AID of LT is 16 bytes,
o Application preferred name is 16 bytes,
o Application Label is 16 bytes,
o LT contains 4 languages preferences in tag ‘5F2D’
o PDOL has a length so that the FCI Proprietary Template
reach the maximum length and that the length of the
data to be send in the GET PROCESSING OPTIONS
is > 128 bytes.
•
CDOL1 requests all terminal data and other data (if any needed)
to reach the maximum length (255 bytes) to send in
.GENERATE AC command
•
Each record contain a single data element (one record one
data) and all optional data must present..
•
All others card data (one by record) with variable length must be
such that they reach the maximum length and that the record is
‘00’ padded to reach 254 bytes.
•
LT parameters are set so that transaction is performed on-line
•
Issuer Response contains three '71' scripts where the total
length of these constructed data objects is the limit device
defined in ICS.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 158
2CA.112.00 Maximum Data Length: Issuer Script
•
The LT shall receive APDU commands according to the scripts
sent in the response
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 159
2CA.113.00 Maximum Data Length: Issuer Script (2)
Test No: 2CA.113.00 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal is able to manage and perform scripts if it
receives one or several scripts with the total length is less than or equal
to 128 bytes (or device limit if above 128 bytes) in authorization or
financial response
Reference Book 3 - Section Annex A – Data Elements Dictionary
EMV 4.3:
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
FCI template has the maximum Length (252 bytes), containing
all mandatory and optional data (excluding FCI Issuer
discretionary data):
o AID of LT is 16 bytes,
o Application preferred name is 16 bytes,
o Application Label is 16 bytes,
o LT contains 4 languages preferences in tag ‘5F2D’
o PDOL has a length so that the FCI Proprietary Template
reach the maximum length and that the length of the
data to be send in the GET PROCESSING OPTIONS
is > 128 bytes.
•
CDOL1 requests all terminal data and other data (if any needed)
to reach the maximum length (255 bytes) to send in
.GENERATE AC command
•
Each record contain a single data element (one record one
data) and all optional data must present..
•
All others card data (one by record) with variable length must be
such that they reach the maximum length and that the record is
‘00’ padded to reach 254 bytes.
•
LT parameters are set so that transaction is performed on-line
•
Issuer Response contains three '72' scripts where the total
length of these constructed data objects is the limit device
defined in ICS.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 160
2CA.113.00 Maximum Data Length: Issuer Script (2)
•
The LT shall receive APDU commands according to the scripts
sent in the response
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 161
2CA.114.00 Maximum Data Length: Issuer Script Commands (2)
Test No: 2CA.114.00 - Revision 4.1e - Number of sub cases: 0
Objective: To ensure that the terminal is able to support the maximum data length
of each data as specified in Book 3 annex A, in particular an Issuer Script
Command
Reference Book 3 - Section Annex A – Data Elements Dictionary
EMV 4.3:
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
FCI template has the maximum Length (252 bytes), containing
all mandatory and optional data (excluding FCI Issuer
discretionary data):
o AID of LT is 16 bytes,
o Application preferred name is 16 bytes,
o Application Label is 16 bytes,
o LT contains 4 languages preferences in tag ‘5F2D’
o PDOL has a length so that the FCI Proprietary Template
reach the maximum length and that the length of the
data to be send in the GET PROCESSING OPTIONS
is > 128 bytes.
•
CDOL1 requests all terminal data and other data (if any needed)
to reach the maximum length (255 bytes) to send in
.GENERATE AC command
•
Each record contain a single data element (one record one
data) and all optional data must present..
•
All others card data (one by record) with variable length must be
such that they reach the maximum length and that the record is
‘00’ padded to reach 254 bytes.
•
LT returns an ARQC in response to first GENERATE AC.
•
Authorization response message contains one Issuer script with
tag ’72’ containing one command where the length = Maximum
Script length supported by the device (minimum 128 bytes) –
script header(tags and Length). With a maximum of 261 bytes.
•
LT returns '90 00' to script command
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 162
2CA.114.00 Maximum Data Length: Issuer Script Commands (2)
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The LT shall receive a sequence of commands according to the
script contained in the authorization response after the second
GENERATE AC.
•
TVR byte 5, bit 5 = '0' (ie Script processing succeeded after final
GENERATE AC) contained in Financial Confirmation message
or Batch Data Capture message
•
TVR byte 5, bit 6 = '0' (ie Script processing before final
GENERATE AC not used) received at 2nd GENERATE AC.
•
TSI byte 1, bit 3 = '1' (ie Script processing was performed),
contained in Financial Confirmation message or Batch Data
Capture message
•
Issuer Script Results for 1st script with Tag 72, Byte 1 shall be
set to '20', script processing successful, contained in Financial
Confirmation message or Batch Data Capture message
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 163
2CA.115.00 Terminal or Issuer sourced data
Test No: 2CA.115.00 - Revision 4.2b - Number of sub cases: 15
Objective: To ensure that the terminal does not replace the amount authorized by
the card’s amount authorized when present in record file
Reference Book 3 - Section 5 – Data Elements and Files
EMV 4.3:
Book 3 - Section 7.5 – Erroneous or Missing Data in the ICC
Terminal NA
Configuration:
Conditions:
•
CDOL1 requests all data listed in below subcases
•
In the below subcases: values returned by the card in read
records for Terminal or Issuer data requested in CDOL1 are
different from values provided by Terminal or Issuer
•
Case 01: A record file of the LT contains the tag ‘Amount
Authorized’ (Numeric)
•
Case 02: A record file of the LT contains the tag Amount
Authorized’ (binary) Type’.
•
Case 03: A record file of the LT contains the tag ‘Terminal AID’.
•
Case 04: A record file of the LT contains the tag ’CVM result’.
•
Case 05: A record file of the LT contains the tag ’Merchant
Category Code’.
•
Case 06: A record file of the LT contains the tag ’Merchant
Identifier’.
•
Case 07: A record file of the LT contains the tag ’Merchant
Name and Location’.
•
Case 08: A record file of the LT contains the tag ’POS Entry
Mode’.
•
Case 09: A record file of the LT contains the tag ’Terminal
Identifier’.
•
Case 10: A record file of the LT contains the tag ’Terminal
Capabilities’.
•
Case 11: A record file of the LT contains the tag ’Terminal
Verification Results’.
•
Case 12: A record file of the LT contains the tag ‘Transaction
Date’.
•
Case 13: A record file of the LT contains the tag ’Transaction
Type’.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 164
2CA.115.00 Terminal or Issuer sourced data
•
Case 14: A record file of the LT contains the tag ’Transaction
Status Information’.
•
Case 15: A record file of the LT contains the tag ‘Unpredictable
Number’.
Action:
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC
•
The First GENERATE AC must be send to LT with the data
element provided by the terminal (value not replaced by the
equivalent data returned by the card).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 165
2CA.115.01 Terminal or Issuer sourced data (2)
Test No: 2CA.115.01 - Revision 4.2b - Number of sub cases: 2
Objective: To ensure that the terminal does not replace a Terminal or Issuer data
by the same data provided by the card in a record file
Reference Book 3 - Section 5 – Data Elements and Files
EMV 4.3:
Book 3 - Section 7.5 – Erroneous or Missing Data in the ICC
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
LT parameters are set so that transaction is performed on-line
•
CDOL2 requests all data listed in below subcases
•
In the below subcases: values returned by the card in read
records for Terminal or Issuer data requested in CDOL2 are
different from values provided by Terminal or Issuer
•
Case 01: A record file of the LT contains the tag Issuer
Authentication Data’
•
Case 02: A record file of the LT contains the tag ‘Authorisation
Response Code’
Action:
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC
•
The Second GENERATE AC must be send to LT with the data
element provided by the Issuer (value not replaced by the
equivalent data returned by the card).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 166
2CA.116.00 Issuer-Approved Transaction
Test No: 2CA.116.00 - Revision 4.2a - Number of sub cases: 3
Objective: To verify that the terminal accept issuer-approved transactions when
issuer authentication fails and the card returns an approval (TC) in the
second GEN AC response.
Reference
EMV 4.3:
•
Book 3 - Section 8.1 - Exception Handling
•
Book 3 - Section 10.9 - Online Processing
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
LT parameters are set so that transaction is performed on-line.
•
AIP of LT indicates Issuer Authentication is supported (AIP byte
1 bit 3 = 1).
•
Host Source shall return an approval in the authorization or
financial response
•
Emulated Issuer Authentication Data is transmitted to the
terminal formatted as follows: a valid 8 byte ARPC and a 2 byte
proprietary Authorisation Response Code indicating an approval
•
LT returns status value '63 00' in response to EXTERNAL
AUTHENTICATE.
•
LT response to the second GENERATE AC:
•
Case 01: LT responses a TC without advice (40)
•
Case 02: LT responses a TC with advice and no reason (48)
•
Case 03: LT responses a TC with advice and reason is Issuer
authentication failed (4B)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT until
completion.
Pass Criteria: terminal shall process the transaction until completion with an approval
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 167
2CA.117.00 Issuer-Approved Transaction (2)
Test No: 2CA.117.00 - Revision 4.2a - Number of sub cases: 3
Objective: To verify that the terminal decline issuer-approved transactions when
issuer authentication fails and the card returns a decline (AAC) in the
second GEN AC response.
Reference
EMV 4.3:
•
Book 3 - Section 8.1 - Exception Handling
•
Book 3 - Section 10.9 - Online Processing
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
LT parameters are set so that transaction is performed on-line.
•
AIP of LT indicates Issuer Authentication is supported (AIP byte
1 bit 3 = 1).
•
Host Source shall return an approval in the authorization or
financial response
•
Emulated Issuer Authentication Data is transmitted to the
terminal formatted as follows: a valid 8 byte ARPC and a 2 byte
proprietary Authorisation Response Code indicating an approval
•
LT returns status value '63 00' in response to EXTERNAL
AUTHENTICATE.
•
LT response to the second GENERATE AC:
•
Case 01: LT responses an AAC without advice (00)
•
Case 02: LT responses an AAC with advice and no reason (08)
•
Case 03: LT responses an AAC with advice and reason is
Issuer authentication failed (0B)
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT until
completion.
Pass Criteria: terminal shall process the transaction until completion with a decline
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 168
2CA.118.00 Syntax of SELECT PSE returned Data Field with data
order not as given in EMV Specifications
Test No: 2CA.118.00 - Revision 4.2c - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, it is able to
recognize the FCI returned Data field of the SELECT PSE command,
even if data order is not as given in EMV Specifications
Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response Message
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
LT contains a PSE
•
FCI of PSE contains all mandatory data field: FCI Template
(‘6F’), FCI Proprietary Template ‘A5’, SFI of the Directory File
(‘88’), DF Name (‘84’),
•
FCI of PSE contains all optional data objects in this order:
Issuer Code Table Index (‘9F 11’), Language Preference (‘5F
2D’).
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC or an AAC.
•
LT shall receive a READ RECORD command with SFI coded
according to data returned in FCI
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 169
2CA.118.01 Syntax of SELECT PSE returned Data Field with
unexpected data element in templates '6F' or 'A5'
Test No: 2CA.118.01 - Revision 4.2c - Number of sub cases: 02
Objective: To ensure that if the terminal supports selection with PSE, it is able to
recognize the FCI returned Data field of the SELECT PSE command
without taken into account unexpected data element in templates '6F'
or 'A5'.
Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response
EMV 4.3: Message
Terminal [PSE] supported
Configuration:
Conditions:
•
LT contains a PSE
•
Case 1: FCI of PSE contains all mandatory data field: FCI
Template (‘6F’), DF Name (‘84’), Application Label (‘50’), FCI
Proprietary Template ‘A5’, SFI of the Directory File (‘88’).
•
Case 2: FCI of PSE contains all mandatory data field: FCI
Template (‘6F’), DF Name (‘84’), FCI Proprietary Template
‘A5’, SFI of the Directory File (‘88’), Application Label (‘50’).
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC or an AAC.
•
LT shall receive a READ RECORD command with SFI coded
according to data returned in FCI
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 170
2CA.118.01 Syntax of SELECT PSE returned Data Field with
unexpected data element in templates '6F' or 'A5'
2CA.119.00 Data order in template for Select ADF
Test No: 2CA.119.00 - Revision 4.2c - Number of sub cases: 0
Objective: To ensure that the terminal accepts a response to SELECT ADF command
with data stored in an order different from example given in EMV
Specifications.
Reference Book 1 - Section 11.3.4 Data Field Returned in the Response Message
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Terminal supports one LT application
•
LT does not support a PSE
•
LT returns data in response to SELECT ADF in that order: FCI
Template ‘6F’, FCI Proprietary template ‘A5’, Application priority
indicator ‘87’, Application Label ‘50’, Application preferred name
‘9F12’, DF Name ‘84’
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal shall select the application and continue the transaction.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 171
2CA.119.01 Data order in template for Select PSE
Test No: 2CA.119.01 - Revision 4.2c - Number of sub cases: 0
Objective: To ensure that the terminal accepts
a response to SELECT PSE
command with data stored in an order different from example given in
EMV Specifications.
Reference Book 1 - Section 11.3.4 Data Field Returned in the Response Message
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
Terminal supports one LT application
•
LT returns data in response to SELECT PSE in that order: FCI
Template ‘6F’, FCI Proprietary template ‘A5’, Language
Preference ‘5F2D’, Issuer Code Table Index ‘9F11’, SFI of the
Directory Elementary File ‘88’, DF Name ‘84’
Action: NA
Procedure: PSE in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal shall select the application referred in PSE and continue
the transaction.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 172
2CA.119.01 Data order in template for Select PSE
2CA.119.02 Data order in template for GET PROCESSING
OPTIONS (Format 2)
Test No: 2CA.119.02 - Revision 4.2c - Number of sub cases: 0
Objective: To ensure that the terminal accepts
a response to GET
PROCESSING OPTIONS command (format 2) in an order different
from example given in EMV Specifications.
Reference Book 3 - Section 6.5.8.4 Data Field Returned in the Response
EMV 4.3: Message
Terminal NA
Configuration:
Conditions: LT returns data in response to GET PROCESSING OPTION in
that order (format 2): AFL ‘94’, AIP ‘82’
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT
Pass Criteria: The terminal shall perform the transaction until completion.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 173
2CA.119.03 Data order in template for First GENERATE AC
Command (format 2) without CDA
Test No: 2CA.119.03 - Revision 4.2c - Number of sub cases: 0
Objective: To ensure that the terminal accepts a response to GENERATE AC
command in an order different from example given in EMV
Specifications.
Reference Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
AIP of LT indicates CDA is not supported (AIP byte 1 bit 1 = ‘0’).
•
LT returns data in response to first GENERATE AC command in
that order (format 2): Application cryptogram ‘9F26’, Cryptogram
Information Data ‘9F27’, Issuer Application Data ‘9F10’,
Application transaction Counter ‘9F36’
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal shall select the application and continue the transaction
until completion.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 174
2CA.119.04 Data order in template for Second GENERATE AC
Command (format 2) without CDA
Test No: 2CA.119.04 - Revision 4.2c - Number of sub cases: 0
Objective: To ensure that the terminal accepts a response to GENERATE AC
command in an order different from example given in EMV
Specifications.
Reference Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message
EMV 4.3:
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is not supported (AIP byte 1 bit 1 = ‘0’).
•
LT parameters are set so that transaction is performed on-line
•
LT returns data in response to second GENERATE AC
command in that order (format 2): Application transaction
Counter ‘9F36’, Application cryptogram ‘9F26’, Cryptogram
Information Data ‘9F27’, Issuer Application Data ‘9F10’
Action: NA
Procedure: Application in LT is selected and transaction is processed online with LT.
Pass Criteria: The terminal shall select the application and continue the transaction
until completion.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 175
2CA.119.05 Data order in template for First GENERATE AC
Command (format 2) with CDA
Test No: 2CA.119.05 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal accepts a response to GENERATE AC
command in an order different from example given in EMV
Specifications.
Reference Book 2 - Section 6.6.1 Dynamic Signature Generation
EMV 4.3:
Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message
Terminal [CDA] AND ([Offline Only] OR [Offline/Online capable]) supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that TC is requested at first Gen AC
•
LT returns data in response to first GENERATE AC command in
that order (format 2): Issuer Application Data ‘9F10’, Signed
Dynamic Application data ‘9F4B’ (if CDA is requested),
Application cryptogram ‘9F26’ (if CDA is not requested),
Cryptogram Information Data ‘9F27’, Application transaction
Counter ‘9F36’
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
The terminal must request a TC with CDA at first GENERATE
AC
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 176
2CA.119.06 Data order in template for Second GENERATE AC
Command (format 2) with CDA
Test No: 2CA.119.06 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal accepts a response to GENERATE AC
command in an order different from example given in EMV
Specifications.
Reference Book 2 - Section 6.6.1 Dynamic Signature Generation
EMV 4.3:
Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message
Terminal ([CDA Mode1] OR [CDA Mode4]) AND [Online Only or Offline/Online
Configuration: capable] supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC and a TC at Second Gen AC
•
In response to online processing, the issuer must approve the
transaction
•
LT returns data in response to second GENERATE AC
command in that order (format 2): Signed Dynamic Application
data ‘9F4B’, Application cryptogram, Application transaction
Counter ‘9F36’, Cryptogram Information Data ‘9F27’, Issuer
Application Data ‘9F10’
Action: NA
Procedure: Application in LT is selected and transaction is processed online with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
The terminal must request a TC with CDA at second
GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 177
2CA.119.07 Data order in template for Reading a Payment System
Directory
Test No: 2CA.119.07 - Revision 4.2c - Number of sub cases: 0
Objective: To ensure that the terminal accepts a response to READ RECORD on a
Payment System Directory File with data stored in an order different from
example given in EMV Specifications.
Reference Book 1 - Section 12.2.3 Coding a Payment System Directory
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
Terminal supports one LT application
•
LT returns ADF Entry Format data in response to READ
RECORD of the Payment System Directory in that order: ‘50’
Application Label, ‘9F12’ Application Preferred Name, ‘4F’ ADF
Name and ‘87’ Application Priority Indicator
Action: NA
Procedure: PSE in LT is selected and transaction is processed with LT until Approval
Pass Criteria:
•
The terminal shall perform the selection with PSE without
switching to selection by AID list.
•
the transaction shall be performed until approval
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 178
2CA.119.08 Data order in template for First GENERATE AC
Command (format 2) with CDA (2)
Test No: 2CA.119.08 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal accepts a response to GENERATE AC
command in an order different from example given in EMV
Specifications.
Reference Book 2 - Section 6.6.1 Dynamic Signature Generation
EMV 4.3:
Book 3 - Section 6.5.5.4 - Data Field Sent in the Command Message
Terminal ([CDA Mode1] OR [CDA Mode2]) AND [Online Only] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC
•
LT returns data in response to first GENERATE AC command in
that order (format 2): Issuer Application Data ‘9F10’, Signed
Dynamic Application data ‘9F4B’, Cryptogram Information Data
‘9F27’, Application transaction Counter ‘9F36’
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
The terminal must request a ARQC with CDA at first
GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 179
2CA.120.00 Padding in response to SELECT PSE
Test No: 2CA.120.00 - Revision 4.2c - Number of sub cases: 3
Objective: To ensure that the terminal continue the selection process when padding
is used in response to SELECT PSE
Reference Book 1 - 11.3.4 Data Field Returned in the Response Message, table 45
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
Case 01 (Padding in ‘BF0C’ template, before the data): LT
returns data as hereafter in response to SELECT PSE
Command:
6F(
84 ( data )
A5 (
88 ( data )
5F2D ( data )
9F11 ( data )
BF0C (
00 00 00
// padding bytes
E5 (
// proprietary template
C1 ( data )
)
)
)
)
•
Case 02 (Padding in ‘BF0C’ template, after the data): LT returns
data as hereafter in response to SELECT PSE Command:
6F(
84 ( data )
A5 (
88 ( data )
5F2D ( data )
9F11 ( data )
BF0C (
E5 (
// proprietary template
C1 ( data )
)
00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 180
2CA.120.00 Padding in response to SELECT PSE
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00
// padding bytes
)
)
)
•
Case 03 (Padding in ‘BF0C’ template, Pad in between, mixture
of Primitive and constructive ): LT returns data as hereafter in
response to SELECT PSE Command:
6F(
84 ( data )
A5 (
88 ( data )
9F38 ( PDOL )
5F2D ( data )
9F11 ( data )
BF0C (
E5 (
)
00
E6 (
// proprietary template1
C1 ( data )
// padding bytes
//
proprietary
template2
C2 ( data )
)
)
)
)
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT until
approval.
Pass Criteria:
•
The terminal shall perform the selection with PSE without
switching to selection by AID list.
•
the transaction shall be performed until approval
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 181
2CA.120.01 Padding in response to PSE Payment System Directory
selection
Test No: 2CA.120.01 - Revision 4.2c - Number of sub cases: 3
Objective: To ensure that the terminal continue the selection process when padding
is used in response to PSE Payment System Directory selection
Reference Book 1 - 12.2.3 Coding of a Payment System Directory
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
Case 01 (before the first template ‘61’): LT returns data as
hereafter in response to PSE Payment System Directory
selection:
70(
00 00 00 00 00
61 (
4F(data)
50(data)
)
)
•
// padding bytes
Case 02 (between two templates ‘61’): LT returns data as
hereafter in response to PSE Payment System Directory
selection:
70(
61 (
4F(data)
50(data)
)
00 00 00 00 00
61 (
4F(data)
50(data)
)
// padding bytes
)
•
Case 03 (after the last template ‘61’): LT returns data as
hereafter in response to PSE Payment System Directory
selection:
70(
61 (
4F(data)
50(data)
)
00 00 00 00 00
// padding bytes
)
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 182
2CA.120.01 Padding in response to PSE Payment System Directory
selection
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall perform the selection with PSE without
switching to selection by AID list.
•
the transaction shall be performed until approval
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 183
2CA.121.00 Minimum Data Length
Test No: 2CA.121.00 - Revision 4.3b - Number of sub cases: 0
Objective: To ensure that the terminal is able to support the minimum data length
of each data as specified in Book 3 annex A.
Reference Book 3 - Section Annex A – Data Elements Dictionary
EMV 4.3:
Terminal [Offline Only] supported
Configuration:
Conditions:
•
All terminal data have their minimum length
•
IAC/TAC are set so that transaction is approved.
•
FCI template contain:
o AID of LT is 5 bytes,
o Application preferred name is 1 byte,
o Application Label is 1 byte,
o LT contains 1 language preference in tag ‘5F2D’
o PDOL is empty.
•
CVM with minimum length (one CV Rules).
•
All others card data with variable length must be such that they
reach the minimum length defined in Annex A Book 3.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT until
Approval
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 184
2CA.121.01 Minimum Data Length (2)
Test No: 2CA.121.01 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal is able to support the minimum data length
of each data as specified in Book 3 annex A.
Reference Book 3 - Section Annex A – Data Elements Dictionary
EMV 4.3:
Terminal [Online Only or Offline/Online capable] supported
Configuration:
Conditions:
•
All terminal data have their minimum length
•
IAC/TAC are set so that transaction goes online and is
approved.
•
FCI template contain:
o AID of LT is 5 bytes,
o Application preferred name is 1 byte,
o Application Label is 1 byte,
o LT contains 1 language preference in tag ‘5F2D’
o PDOL is empty.
•
CVM with minimum length (one CV Rules).
•
In GENERATE AC 1 command response: Issuer Application
Data empty,
•
PAN length is 4 bytes,
•
All others card data with variable length must be such that they
reach the minimum length defined in Annex A Book 3.
Action: NA
Procedure: Application in LT is selected and transaction is performed online with LT
until Approval
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 185
2CA.122.00 Payment System reserved Data objects processing
Test No: 2CA.122.00 - Revision 43e - Number of sub cases: 9
Objective: To ensure that the terminal ignores Payment System reserved Data
Objects.
Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF
contains additionally all reserved tags in the range '9F50' to
'9F7F'
•
Case 03: Response to GENERATE AC contains all reserved
tags in the range '9F50' to '9F7F' and shall be encoded in
Template 77 and LT request ARQC on first Generate AC.
•
Case 04: Records contains all reserved tags in the range '9F50'
to '9F7F' (splitted over SFI 1 to 10).
•
Case 05: Response to GET PROCESSING OPTIONS contains
all reserved tags in the range '9F50' to '9F7F' and shall be
encoded in template 77
•
Case 06: The PDOL of LT contains all reserved tags in the
range '9F50' to '9F7F'
•
Case 07: The CDOL1 of LT contains all reserved tags in the
range '9F50' to '9F7F'
•
Case 08: The CDOL2 of LT contains all reserved tags in the
range '9F50' to '9F7F' and LT request ARQC on first Generate
AC
•
Case 09: The TDOL of LT contains all reserved tags in the range
'9F50' to '9F7F'
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT until
approval.
Pass Criteria: The terminal shall accept the card and process the transaction until
completion, by requesting a TC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 186
2CA.122.01 Payment System reserved Data objects processing (2)
Test No: 2CA.122.01 - Revision 43e - Number of sub cases: 3
Objective: To ensure that the terminal ignores Payment System reserved Data
Objects.
Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
PSE contains a directory file with entries for ADF.
•
Case 01: FCI Issuer discretionary Data (tag BF0C) of PSE
contains additionally all reserved tags in the range '9F50' to
'9F7F'.
•
Case 02: FCI (tag 6F) of PSE contains additionally all reserved
tags in the range '9F50' to '9F7F'.
•
Case 03: Template '73' of ADF Directory Entry contains
additionally all reserved tags in the range '9F50' to '9F7F.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT until
approval.
Pass Criteria: The terminal shall accept the card and process the transaction until
completion, by requesting a TC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 187
2CA.122.02 EMV reserved Data objects processing (1)
Test No: 2CA.122.00 – Revision 43e – Number of sub cases: 9
Objective: To ensure that the terminal ignores EMV reserved Data Objects (not
used by EMV).
Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Response to GENERATE AC contains all EMV primitve tags
reseved but not used in the EMV specification, (for example
‘9F0C’, ‘9F19’, ‘9F25’, ‘9F28’and ‘9F29’, …) in the range ‘80’ to
‘9E’ and ‘9F00’ to ‘9F4F’ and shall be encoded in template 77
•
Case 01: FCI (tag 6F) of ADF contains additionally all EMV
primitve tags reseved but not used in the EMV specification, (for
example ‘9F0C’, ‘9F19’, ‘9F25’, ‘9F28’and ‘9F29’, …) in the
range ‘80’ to ‘9E’ and ‘9F00’ to ‘9F4F’ within the FCI template
•
Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF
contains additionally all EMV primitve tags (reseved but not
used in the EMV specification, (for example ‘9F0C’, ‘9F19’,
‘9F25’, ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F00’
to ‘9F4F’
•
Case 03: Response to GENERATE AC contains all EMV
primitve tags reseved but not used in the EMV specification, (for
example ‘9F0C’, ‘9F19’, ‘9F25’, ‘9F28’and ‘9F29’, …) in the
range ‘80’ to ‘9E’ and ‘9F00’ to ‘9F4F’ and shall be encoded in
template 77 and LT request ARQC on first Generate AC
•
Case 04: Records contains: all EMV primitve tags reseved but
not used in the EMV specification, (for example ‘9F0C’, ‘9F19’,
‘9F25’, ‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F00’
to ‘9F4F’ (splitted over SFI 1 to 10).
•
Case 05: Response to GET PROCESSING OPTIONS contains
all EMV primitve tags reseved but not used in the EMV
specification, (for example ‘9F0C’, ‘9F19’, ‘9F25’, ‘9F28’and
‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F00’ to ‘9F4F’ and shall
be encoded in template 77
•
Case 06: The PDOL of LT contains all EMV primitve tags
reseved but not used in the EMV specification, (for example
‘9F0C’, ‘9F19’, ‘9F25’, ‘9F28’and ‘9F29’, …) in the range ‘80’ to
‘9E’ and ‘9F00’ to ‘9F4F’
•
Case 07: The CDOL1 of LT contains all EMV primitve tags
reseved but not used in the EMV specification, (for example
‘9F0C’, ‘9F19’, ‘9F25’, ‘9F28’and ‘9F29’, …) in the range ‘80’ to
‘9E’ and ‘9F00’ to ‘9F4F’
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 188
2CA.122.02 EMV reserved Data objects processing (1)
•
Case 08: The CDOL2 of LT contains all EMV primitve tags
reseved but not used in the EMV specification, (for example
‘9F0C’, ‘9F19’, ‘9F25’, ‘9F28’and ‘9F29’, …) in the range ‘80’ to
‘9E’ and ‘9F00’ to ‘9F4F’ and LT request ARQC on first
Generate AC
•
Case 09: The TDOL of LT contains all EMV primitve tags
reseved but not used in the EMV specification, (for example
‘9F0C’, ‘9F19’, ‘9F25’, ‘9F28’and ‘9F29’, …) in the range ‘80’ to
‘9E’ and ‘9F00’ to ‘9F4F’
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT until
approval.
Pass Criteria: The terminal shall accept the card and process the transaction until
completion, by requesting a TC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 189
2CA.122.03 EMV reserved Data objects processing (2)
Test No: 2CA.122.03 - Revision 43e - Number of sub cases: 3
Objective: To ensure that the terminal ignores EMV reserved Data Objects (not
used by EMV).
Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
PSE contains a directory file with entries for ADF.
•
Case 01: FCI Issuer discretionary Data (tag BF0C) of PSE
contains additionally all EMV primitve tags reseved but not used
in the EMV specification, (for example ‘9F0C’, ‘9F19’, ‘9F25’,
‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F00’ to
‘9F4F’'.
•
Case 02: FCI (tag 6F) of PSE contains additionally all EMV
primitve tags reseved but not used in the EMV specification,
(for example ‘9F0C’, ‘9F19’, ‘9F25’, ‘9F28’and ‘9F29’, …) in the
range ‘80’ to ‘9E’ and ‘9F00’ to ‘9F4F’.
•
Case 03: Template '73' of ADF Directory Entry contains:
additionally all EMV primitve tags reseved but not used in the
EMV specification, (for example ‘9F0C’, ‘9F19’, ‘9F25’,
‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F00’ to
‘9F4F’.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT until
approval.
Pass Criteria: The terminal shall accept the card and process the transaction until
completion, by requesting a TC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 190
2CA.122.04 Proprietary Data objects processing (1)
Test No: 2CA.122.04 - Revision 43e - Number of sub cases: 7
Objective: To ensure that the terminal ignores Proprietary Data Objects.
Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Case 01: FCI (tag 6F) of ADF contains additionally 50
proprietary tags including Tag DF09, DF10, DF11 and DF21
within the FCI template
•
Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF
contains additionally 50 proprietary tags including Tag DF09,
DF10, DF11 and DF21
•
Case 03: Response to GET PROCESSING OPTIONS contains
additionally 50 proprietary tags including Tag DF09, DF10,
DF11 and DF21and shall be encoded in template 77
•
Case 04: The PDOL of LT contains additionally 50 proprietary
tags including Tag DF09, DF10, DF11 and DF21
•
Case 05: The CDOL1 of LT contains additionally 50
proprietary tags including Tag DF09, DF10, DF11 and DF21
•
Case 06: The CDOL2 of LT contains additionally 50
proprietary tags including Tag DF09, DF10, DF11 and
DF21and LT request ARQC on first Generate AC
•
Case 07: The TDOL of LT contains additionally 50 proprietary
tags including Tag DF09, DF10, DF11 and DF21
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT until
approval.
Pass Criteria: The terminal shall accept the card and process the transaction until
completion, by requesting a TC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 191
2CA.123.00 Payment System reserved Data objects processing
Test No: 2CA.123.00 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal ignores Payment System reserved Data
Objects.
Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
Case 01: Response to INTERNAL AUTHENTICATE contains all
reserved tags in the range '9F50' to '9F7F' (It can be splitted
over 2 tests if needed) and shall be encoded with format 2
(Template 77)
•
Case 02: The DDOL of LT contains all reserved tags in the
range '9F50' to '9F7F'
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT until
approval.
Pass Criteria: The terminal shall accept the card and process the transaction until
completion, by requesting a TC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 192
2CA.123.01 EMV reserved Data objects processing
Test No: 2CA.123.01 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal ignores EMV reserved Data Objects.
Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
Case 01: Response to INTERNAL AUTHENTICATE contains all
EMV primitve tags reseved but not used in the
EMV
specification, (for example ‘9F’, ‘9F0C’, ‘9F19’, ‘9F25’,
‘9F28’and ‘9F29’, …) in the range ‘80’ to ‘9E’ and ‘9F00’ to
‘9F4F’ and shall be encoded in template 77
•
Case 02: The DDOL of LT contains all EMV primitve tags
reseved but not used in the EMV specification, (for example
‘9F’, ‘9F0C’, ‘9F19’, ‘9F25’, ‘9F28’and ‘9F29’, …) in the range
‘80’ to ‘9E’ and ‘9F00’ to ‘9F4F’
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT until
approval.
Pass Criteria: The terminal shall accept the card and process the transaction until
completion, by requesting a TC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 193
2CA.123.02 Proprietary Data objects processing
Test No: 2CA.123.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal ignores Proprietary Data Objects.
Reference Book 3 – Annex B1 Coding of the Tag Field of BER-TLV Data Objects
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
Case 01: Response to INTERNAL AUTHENTICATE contains
additionally 50 proprietary tags including Tag DF09, DF10,
DF11 and DF21 and shall be encoded in template 77
•
Case 02: The DDOL of LT contains additionally 50 proprietary
tags including Tag DF09, DF10, DF11 and DF21
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT until
approval.
Pass Criteria: The terminal shall accept the card and process the transaction until
completion, by requesting a TC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 194
2CA.124.00 Application Version Number assigned by the payment
system
Test No: 2CA.124.00 - Revision 43e - Number of sub cases: 6
Objective: To ensure that the terminal maintains the Application Dependent Data
for each supported AID(s) assigned by the payment system.
Reference Book 4 - Section 10.2 - Application Dependent Data
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Terminal is configured at the same time with up to 6 different
AID and each of them have a set of different data according to
table 7 of section 10.2, Book 4 and for each AID the data values
are different.
•
The number of AID configured in the Terminal and the number
of subcase to run depends on the response of the ICS question:
‘Maximum supported AIDs’. If value is 6 or above, then all 6 AID
are configured and the 6 sub cases are run, if value is below,
the AID and subcases are according to the ICS response.
•
For AID 1: Terminal Action Code – Default, Denial and Online
are set to 0
•
For AID 2 Terminal Action Code – Default, and Online are set to
‘0’ Terminal Action Code – Denial are set to 00 80 00 00 00.
•
For AID 3 Terminal Action Code – Default, and Online are set to
‘0’ Terminal Action Code – Denial are set to 00 00 40 00 00.
•
For AID 4 Terminal Action Code – Default, and Online are set to
‘0’ Terminal Action Code – Denial are set to 0.
•
For AID 5 Terminal Action Code – Default, and Online are set to
‘0’ Terminal Action Code – Denial are set to 00 20 00 00 00.
•
For AID 6 Terminal Action Code – Default, and Online are set to
‘0’ Terminal Action Code – Denial are set to 20 00 00 00 00.
•
CDOL1 requests all data element identified with Tags of the
Table 7 except AID and CA PK Index (9F22): Acquirer Identifier,
Merchant Category Code, Merchant Identifier, Merchant Name
and Location, Terminal Floor Limit, Terminal Identification,
Transaction Currency Code, Transaction Currency Exponent,
Transaction Reference Currency Code, Transaction Reference
Currency Exponent and also the TVR.
•
Case 01: AID 1 is selected
•
Case 02: AID 2 is selected and ICC Application Version Number
does not match Terminal Application Version Number.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 195
2CA.124.00 Application Version Number assigned by the payment
system
•
Case 03: AID 3 is selected and CVM list contain only one rule
which is an ‘Unrecognised CVM’.
•
Case 04: AID 4 is selected.
•
Case 05: AID 5 is selected and Application is not yet effective in
Card.
•
Case 06: AID 6 is selected and CVM list not present in Card
and AIP indicates cardholder verification is supported.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
LT shall received the appropriate unique value of each data
from CDOL1 for the selected AID.
•
Case 01 & 04: The terminal shall process the transaction until
completion with Approval.
•
Case 02, 03, 05 and 06: The terminal shall process the
transaction until completion with Decline.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 196
2CA.124.01 Application Version Number assigned by the payment
system
Test No: 2CA.124.01 - Revision 43e - Number of sub cases: 6
Objective: To ensure that the terminal maintains the Application Dependent Data
for each supported AID(s) assigned by the payment system.
Reference Book 4 - Section 10.2 - Application Dependent Data
EMV 4.3:
Terminal [Offline Only] supported
Configuration:
Conditions:
•
Terminal is configured at the same time with up to 6 different
AID and each of them have a set of different TAC as described
below:
•
The number of AID configured in the Terminal and the number
of subcase to run depends on the response of the ICS question:
‘Maximum supported AIDs’. If value is 6 or above, then all 6 AID
are configured and the 6 sub cases are run, if value is below,
the AID and subcases are according to the ICS response.
•
For AID 1: Terminal Action Code – Default, Denial and Online
are set to 0
•
For AID 2: Terminal Action Code – Online, and Denial are set to
‘0’ Terminal Action Code – Default are set to 20 00 00 00 00.
•
For AID 3: Terminal Action Code – Online, and Denial are set to
‘0’ Terminal Action Code – Default are set to 00 80 00 00 00.
•
For AID 4: Terminal Action Code – Online, and Denial are set to
‘0’ Terminal Action Code – Default are set to 00 00 40 00 00.
•
For AID 5: Terminal Action Code – Online, and Denial are set to
‘0’ Terminal Action Code – Default are set to 00 40 00 00 00.
•
For AID 6: Terminal Action Code – Online, and Denial are set to
‘0’ Terminal Action Code – Default are set to 00 20 00 00 00.
•
Case 01: AID 1 is selected
•
Case 02: AID 2 is selected and CVM List not present in Card
and AIP indicates cardholder verification is supported.
•
Case 03: AID 3 is selected and ICC Application Version Number
does not match Terminal Application Version Number.
•
Case 04: AID 4 is selected and CVM list contain only one rules
which is an ‘Unrecognised CVM’.
•
Case 05: AID 5 is selected and Application is expired in Card.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 197
2CA.124.01 Application Version Number assigned by the payment
system
•
Case 06: AID 6 is selected and Application is not yet effective in
Card.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
Case 01: The terminal shall process the transaction until
completion with Approval.
•
Case 02 to 06: The terminal shall process the transaction until
completion with Decline.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 198
2CA.124.02 Application Version Number assigned by the payment
system
Test No: 2CA.124.02 - Revision 43e - Number of sub cases: 6
Objective: To ensure that the terminal maintains the Application Dependent Data
for each supported AID(s) assigned by the payment system.
Reference Book 4 - Section 10.2 - Application Dependent Data
EMV 4.3:
Terminal [Offline/Online Capable] supported
Configuration:
Conditions:
•
Terminal is configured at the same time with up to 6 different
AID and each of them have a set of different TAC as described
below:
•
The number of AID configured in the Terminal and the number
of subcase to run depends on the response of the ICS question:
‘Maximum supported AIDs’. If value is 6 or above, then all 6 AID
are configured and the 6 sub cases are run, if value is below,
the AID and subcases are according to the ICS response.
•
For AID 1: Terminal Action Code – Default, Denial and Online
are set to 0
•
For AID 2: Terminal Action Code – Default, and Denial are set
to ‘0’ Terminal Action Code – Online are set to 00 20 00 00 00.
•
For AID 3: Terminal Action Code – Default, and Denial are set
to ‘0’ Terminal Action Code – Online are set to 20 00 00 00 00.
•
For AID 4: Terminal Action Code – Default, and Denial are set
to ‘0’ Terminal Action Code – Online are set to 00 80 00 00 00.
•
For AID 5: Terminal Action Code – Default, and Denial are set
to ‘0’ Terminal Action Code – Online are set to 00 00 40 00 00.
•
For AID 6: Terminal Action Code – Default, and Denial are set
to ‘0’ Terminal Action Code – Online are set to 00 40 00 00 00.
•
Case 01: AID 1 is selected
•
Case 02: AID 2 is selected and Application is not yet effective in
Card.
•
Case 03: AID 3 is selected and CVM List not present in Card
and AIP indicates cardholder verification is supported.
•
Case 04: AID 4 is selected and ICC Application Version Number
does not match Terminal Application Version Number.
•
Case 05: AID 5 is selected and CVM list contain only one rules
which is an ‘Unrecognised CVM’.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 199
2CA.124.02 Application Version Number assigned by the payment
system
•
Case 06: AID 6 is selected and Application is expired in Card.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
Case 01: The terminal shall process the transaction offline until
completion with Approval.
•
Case 02 to 06: The terminal shall process the transaction online
until completion with Approval.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 200
2CA.124.03 Application Version Number assigned by the payment
system
Test No: 2CA.124.03 - Revision 43e - Number of sub cases: 6
Objective: To ensure that the terminal maintains the Application Dependent Data
for each supported AID(s) assigned by the payment system.
Reference Book 4 - Section 10.2 - Application Dependent Data
EMV 4.3:
Terminal [Offline/Online capable] supported OR [Online Only AND Normal Default
Configuration: Action processing] supported
Conditions:
•
Terminal is configured at the same time with up to 6 different
AID and each of them have a set of different TAC as described
below:
•
The number of AID configured in the Terminal and the number
of subcase to run depends on the response of the ICS question:
‘Maximum supported AIDs’. If value is 6 or above, then all 6 AID
are configured and the 6 sub cases are run, if value is below,
the AID and subcases are according to the ICS response.
•
For AID 1: Terminal Action Code – Default, Denial and Online
are set to 0
•
For AID 2: Terminal Action Code – Online, and Denial are set to
‘0’ Terminal Action Code – Default are set to 20 00 00 00 00.
•
For AID 3: Terminal Action Code – Online, and Denial are set to
‘0’ Terminal Action Code – Default are set to 00 80 00 00 00.
•
For AID 4: Terminal Action Code – Online, and Denial are set to
‘0’ Terminal Action Code – Default are set to 00 00 40 00 00.
•
For AID 5: Terminal Action Code – Online, and Denial are set to
‘0’ Terminal Action Code – Default are set to 00 40 00 00 00.
•
For AID 6: Terminal Action Code – Online, and Denial are set to
‘0’ Terminal Action Code – Default are set to 00 20 00 00 00.
•
Terminal is unable to go online
•
Case 01: AID 1 is selected
•
Case 02: AID 2 is selected and CVM List not present in Card
and AIP indicates cardholder verification is supported.
•
Case 03: AID 3 is selected and ICC Application Version Number
does not match Terminal Application Version Number.
•
Case 04: AID 4 is selected and CVM list contain only one rules
which is an ‘Unrecognised CVM’
•
Case 05: AID 5 is selected and Application is expired in Card.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 201
2CA.124.03 Application Version Number assigned by the payment
system
•
Case 06: AID 6 is selected and Application is not yet effective in
Card.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
Case 01: The terminal shall process the transaction until
completion with Approval.
•
Case 02 to 06: The terminal shall process the transaction until
completion with Decline.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 202
2CA.125.00 Coding of AIP reserved Bits for Contactless
Test No: 2CA.125.00 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that the terminal does not understand or react on the setting
of the AIP reserved bits.
Reference Book Bulletin – Section DSB 161 – Reserved TVR and AIP bits for
EMV 4.3: Contactless Specifications
Terminal NA
Configuration:
Conditions:
•
The AIP Byte 2, bit 1 and bit 6 are set to '0'
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal process the transaction until completion, by requesting a
TC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 203
2CA.125.01 Coding of AIP reserved Bits for Contactless (2)
Test No: 2CA.125.01 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that the terminal does not understand or react on the setting
of the AIP reserved bits.
Reference Book Bulletin – Section DSB 161 – Reserved TVR and AIP bits for
EMV 4.3: Contactless Specifications
Terminal NA
Configuration:
Conditions:
•
The AIP Byte 2, bit 1 and bit 6 are set to '1'
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria: The terminal process the transaction until completion, by requesting a
TC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 204
2CA.126.00 Coding of TVR reserved Bits for Contactless
Test No: 2CA.126.00 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that the terminal sets to zeroes data (bits) indicated as
Reserved for Contactless Specifications in TVR.
Reference Book Bulletin – Section DSB 161 – Reserved TVR and AIP bits for
EMV 4.3: Contactless Specifications
Terminal NA
Configuration:
Conditions: NA
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
TVR : byte 5 - bits 4 to 1 are set to ‘0’, received at 1st
GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 205
2CA.127.00 ASRPD Data in FCI from a SELECT ADF
Test No: 2CA.127.00 - Revision 43e - Number of sub cases: 5
Objective: To ensure that the presence of ASRPD data object in the data field
returned by SELECT ADF command is ignored when the terminal does not
support it, or accepts when the terminal support it.
Reference
EMV 4.3: Book Bulletins - Section SB 175 - Bulletin n°175, Application Selection
Registered Proprietary Data (February 2016)
Terminal NA
Configuration:
Conditions:
•
LT contains an ADF
•
Case 01: FCI Issuer discretionary Data (tag BF0C) of ADF
contains ASRPD data field: tag 9F 0A correctly formatted with a
single instance (ID L V).
•
Case 02: FCI Issuer discretionary Data (tag BF0C) of ADF
contains ASRPD data field: tag 9F 0A correctly formatted with
multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3 V3) where ID1
=00 01.
•
Case 03: FCI Issuer discretionary Data (tag BF0C) of ADF
contains ASRPD data field: tag 9F 0A correctly formatted with
multiple instances (ID1 L1 V1, ID2 L2 V2,…, IDn Ln Vn) reaching
the max length possible (with Application Label = 1 byte length)
where ID1 =00 01
•
Case 04: FCI Issuer discretionary Data (tag BF0C) of ADF
contains ASRPD data field: tag 9F 0A correctly formatted with a
single empty instance (ID L where L = 00).
•
Case 05: FCI Issuer discretionary Data (tag BF0C) of ADF
contains ASRPD data field: tag 9F 0A correctly formatted with
multiple instances (ID1 L1 V1, ID2 L2, ID3 L3 V3 where L2=00)
where ID1 =00 01.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC on first GENERATE AC or
Second GENERATE AC
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 206
2CA.128.00 ASRPD Data in Directory Entry
Test No: 2CA.128.00 - Revision 43e - Number of sub cases: 12
Objective: To ensure that the presence of ASRPD data object in PSE directory entry
is ignored when the terminal does not support it, or accepts when the
terminal support it.
Reference Book Bulletins - Section SB 175 - Bulletin n°175, Application Selection
EMV 4.3: Registered Proprietary Data (February 2016)
Terminal [PSE] supported
Configuration:
Conditions:
•
LT contains a PSE.
•
Case 01: Directory Discretionary Template (’73’) of the ADF
Directory Entry in the Payment System Directory contains ASRPD
data field: tag 9F 0A correctly formatted with a single instance (ID
L V).
•
Case 02: Directory Discretionary Template (’73’) of the ADF
Directory Entry in the Payment System Directory contains ASRPD
data field: tag 9F 0A correctly formatted with multiple instances
(ID1 L1 V1, ID2 L2 V2, ID3 L3 V3, where ID1 =00 01).
•
Case 03: Directory Discretionary Template (’73’) of the ADF
Directory Entry in the Payment System Directory contains ASRPD
data field: tag 9F 0A correctly formatted with multiple instances
(ID1 L1 V1, ID2 L2 V2,…, IDn Ln Vn) reaching the max length
possible of the data 9F 0A in the template 73 (no other data
present in template 73)
•
Case 04: Directory Discretionary Template (’73’) of the ADF
Directory Entry in the Payment System Directory contains ASRPD
data field: tag 9F 0A correctly formatted with a single instance
(ID1 L V). FCI Issuer discretionary Data (tag BF0C) of ADF
contains ASRPD data field: tag 9F 0A correctly formatted with a
single instance (ID2 L V).
•
Case 05: Directory Discretionary Template (’73’) of the ADF
Directory Entry in the Payment System Directory contains ASRPD
data field: tag 9F 0A correctly formatted with a single instance
(ID1 L V1). FCI Issuer discretionary Data (tag BF0C) of ADF
contains ASRPD data field: tag 9F 0A correctly formatted with a
single instance (ID1 L V1) with same ID1 = 00 01 and value V1 as
in Directory Discretionary Template (’73’) of the ADF Directory
Entry.
•
Case 06: Directory Discretionary Template (’73’) of the ADF
Directory Entry in the Payment System Directory contains ASRPD
data field: tag 9F 0A correctly formatted with a single instance
(ID1 L V1). FCI Issuer discretionary Data (tag BF0C) of ADF
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 207
2CA.128.00 ASRPD Data in Directory Entry
contains ASRPD data field: tag 9F 0A correctly formatted with a
single instance (ID1 L V2) with same ID1 = 00 01 (as in the
Directory Discretionary Template (’73’) of the ADF Directory Entry)
but different value.
•
Case 07: Directory Discretionary Template (’73’) of the ADF
Directory Entry in the Payment System Directory contains ASRPD
data field: tag 9F 0A correctly formatted with multiple instances
(ID1 L1 V1, ID2 L2 V2, ID3 L3 V3 where ID1 = 00 01). FCI Issuer
discretionary Data (tag BF0C) of ADF contains ASRPD data field:
tag 9F 0A correctly formatted with multiple instances (ID4 L4 V4,
ID5 L5 V5, ID6 L6 V6).
•
Case 08: Directory Discretionary Template (’73’) of the ADF
Directory Entry in the Payment System Directory contains ASRPD
data field: tag 9F 0A correctly formatted with multiple instances
(ID1 L1 V1, ID2 L2 V2, ID3 L3 V3 where ID1 =00 01). FCI Issuer
discretionary Data (tag BF0C) of ADF contains ASRPD data field:
tag 9F 0A correctly formatted with multiple instances (ID4 L4 V4,
ID2 L2 V2, ID6 L6 V6) where ID2 is the same (with same value
V2) as in the Directory Discretionary Template (’73’) of the ADF
Directory Entry.
•
Case 09: Directory Discretionary Template (’73’) of the ADF
Directory Entry in the Payment System Directory contains ASRPD
data field: tag 9F 0A correctly formatted with multiple instances
(ID1 L1 V1, ID2 L2 V2, ID3 L3 V3 where ID1 =00 01). FCI Issuer
discretionary Data (tag BF0C) of ADF contains ASRPD data field:
tag 9F 0A correctly formatted with multiple instances (ID4 L4 V4,
ID2 L7 V7, ID6 L6 V6) where ID2 is the same (with different length
and value) as in the Directory Discretionary Template (’73’) of the
ADF Directory Entry.
•
Case 10: Directory Discretionary Template (’73’) of the ADF
Directory Entry in the Payment System Directory contains ASRPD
data field: tag 9F 0A correctly formatted with multiple instances
(ID1 L1 V1, ID2 L2 V2,…, IDn Ln Vn where ID1 =00 01) reaching
the max length possible of the data 9F 0A in the template 73. FCI
Issuer discretionary Data (tag BF0C) of ADF contains ASDPR
data correctly formatted with a single instance (ID1 L1 V1 where
ID1 =00 01) with same ID1 and value V1 as in the Directory
Discretionary Template (’73’) of the ADF Directory Entry.
•
Case 11: Directory Discretionary Template (’73’) of the ADF
Directory Entry in the Payment System Directory contains ASRPD
data field: tag 9F 0A correctly formatted with a single empty
instance (ID L) where L=00. FCI Issuer discretionary Data (tag
BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly
formatted with multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3
V3 where ID1 =00 01).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 208
2CA.128.00 ASRPD Data in Directory Entry
•
Case 12: Directory Discretionary Template (’73’) of the ADF
Directory Entry in the Payment System Directory contains ASRPD
data field: tag 9F 0A correctly formatted with multiple instances
(ID1 L1, ID2 L2 V2, ID3 L3 V3) where ID1 =00 01, L1=00. FCI
Issuer discretionary Data (tag BF0C) of ADF contains ASRPD
data field: tag 9F 0A correctly formatted with multiple instances
(ID4 L4 V4, ID2 L2 V2, ID6 L6 V6) where ID2 is the same (with
same value V2) as in the Directory Discretionary Template (’73’)
of the ADF Directory Entry.
Action: NA
Procedure: Application in LT is selected and transaction is performed with LT.
Pass Criteria:
•
The terminal shall perform the application selection process with
PSE and process the transaction until completion, by requesting a
TC on first GENERATE AC or Second GENERATE AC
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 209
2CA.129.00 PAR Data in Authorisation or in Financial Request
Test No: 2CA.129.00 - Revision 43e - Number of sub cases: 5
Objective: To ensure that the presence of PAR Data Object in the data field returned
by LT command is transmitted in the Authorisation Request or in Financial
Transaction Request.
Reference
EMV 4.3: Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data
Objects – Payment Account Reference (PAR) (April 2016)
Terminal ([Online Only] OR [Offline/Online capable]) supported
Configuration:
Conditions:
•
IAC’s and TAC’s are set so that ARQC is requested at first
GENERATE AC.
•
LT returns ARQC at first GENERATE AC
•
Case 01: Response to GET PROCESSING OPTIONS contains
PAR Data Object (tag 9F24) and shall be encoded in template 77
•
Case 02: Response to First GENERATE AC contains PAR Data
Object (tag 9F24) and shall be encoded in template 77
•
Case 03: An EMV Record (in the SFI range 1 to 10) to be read
contains PAR Data Object (tag 9F24)
•
Case 04: An EMV Record (in the SFI range 11 to 20) to be read
contains PAR Data Object (tag 9F24)
•
Case 05: An EMV Record (in the SFI range 21 to 30) to be read
contains PAR Data Object (tag 9F24)
Action: NA
Procedure: Application in LT is selected and transaction is performed online with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC at Second GENERATE AC
•
The Authorisation Request or Financial Transaction Request shall
contains the PAR Data Object with same value as contained in
LT.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 210
2CA.130.00 PAR Data in Authorisation or in Financial Request (2)
Test No: 2CA.130.00 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the presence of PAR Data Object in the data field returned
by INTERNAL AUTHENTICATE command is transmitted in the
Authorisation Request or the Financial Transaction Request.
Reference
EMV 4.3: Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data
Objects – Payment Account Reference (PAR) (April 2016)
Terminal [DDA] AND ([Online Only] OR [Offline/Online capable]) supported
Configuration:
Conditions:
•
IAC’s and TAC’s are set so that ARQC is requested at first
GENERATE AC.
•
LT returns ARQC at first GENERATE AC
•
Response to INTERNAL AUTHENTICATE contains PAR Data
Object (tag 9F24) and shall be encoded in template 77
Action: NA
Procedure: Application in LT is selected and transaction is performed online with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC at Second GENERATE AC
•
The Authorisation Request or Financial Transaction Request shall
contains the PAR Data Object with same value as contained in LT
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 211
2CA.131.00 PAR Data in Authorisation or in Financial Request and
Response
Test No: 2CA.131.00 - Revision 43e - Number of sub cases: 5
Objective: To ensure that the presence of PAR Data Object in the data field returned
by LT command is transmitted in the Authorisation Request and Response
or in the Financial Transaction Request and Response.
Reference
EMV 4.3: Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data
Objects – Payment Account Reference (PAR) (April 2016)
Terminal ([Online Only] OR [Offline/Online capable]) supported
Configuration:
Conditions:
•
IAC’s and TAC’s are set so that ARQC is requested at first
GENERATE AC.
•
LT returns ARQC at first GENERATE AC
•
The Authorisation Response (or Financial Transaction Response)
contains the PAR Data Object.
•
Case 01: Response to GET PROCESSING OPTIONS contains
PAR Data Object (tag 9F24) and shall be encoded in template 77
•
Case 02: Response to First GENERATE AC contains PAR Data
Object (tag 9F24) and shall be encoded in template 77
•
Case 03: An EMV Record (in the SFI range 1 to 10) to be read
contains PAR Data Object (tag 9F24)
•
Case 04: An EMV Record (in the SFI range 11 to 20) to be read
contains PAR Data Object (tag 9F24)
•
Case 05: An EMV Record (in the SFI range 21 to 30) to be read
contains PAR Data Object (tag 9F24)
Action: NA
Procedure: Application in LT is selected and transaction is performed online with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC at Second GENERATE AC
•
The Authorisation Request or the Financial Transaction Request
shall contains the PAR Data Object with same value as contained
in LT
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 212
2CA.132.00 PAR Data in Authorisation or in Financial Request and
Response (2)
Test No: 2CA.132.00 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the presence of PAR Data Object in the data field returned
by INTERNAL AUTHENTICATE command is transmitted in the
Authorisation Request and Response.
Reference
EMV 4.3: Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data
Objects – Payment Account Reference (PAR) (April 2016)
Terminal [DDA] AND ([Online Only] OR [Offline/Online capable]) supported
Configuration:
Conditions:
•
IAC’s and TAC’s are set so that ARQC is requested at first
GENERATE AC.
•
LT returns ARQC at first GENERATE AC
•
The Authorisation Response (or the Financial Transaction
Response) contains the PAR Data Object
•
Response to INTERNAL AUTHENTICATE contains PAR Data
Object (tag 9F24) and shall be encoded in template 77
Action: NA
Procedure: Application in LT is selected and transaction is performed online with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC at Second GENERATE AC
•
The Authorisation Request or the Financial Transaction Request
shall contains the PAR Data Object with same value as contained
in LT.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 213
2CA.133.00 PAR Data in Batch Data Capture
Test No: 2CA.133.00 - Revision 43e - Number of sub cases: 5
Objective: To ensure that the presence of PAR Data Object in the data field returned
by LT command is transmitted in the Batch Data Capture.
Reference
EMV 4.3: Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data
Objects – Payment Account Reference (PAR) (April 2016)
Terminal [Batch Data Capture] supported
Configuration:
Conditions:
•
Case 01: Response to GET PROCESSING OPTIONS contains
PAR Data Object (tag 9F24) and shall be encoded in template 77
•
Case 02: Response to First GENERATE AC contains PAR Data
Object (tag 9F24) and shall be encoded in template 77
•
Case 03: An EMV Record (in the SFI range 1 to 10) to be read
contains PAR Data Object (tag 9F24)
•
Case 04: An EMV Record (in the SFI range 11 to 20) to be read
contains PAR Data Object (tag 9F24)
•
Case 05: An EMV Record (in the SFI range 21 to 30) to be read
contains PAR Data Object (tag 9F24)
Action: NA
Procedure: Application in LT is selected and transaction is performed online with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC at First or Second
GENERATE AC
•
The Batch Data Capture shall contains the PAR Data Object with
same value as contained in LT
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 214
2CA.134.00 PAR Data in Batch Data Capture (2)
Test No: 2CA.134.00 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the presence of PAR Data Object in the data field returned
by INTERNAL AUTHENTICATE command is transmitted in the Batch Data
Capture.
Reference
EMV 4.3: Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data
Objects – Payment Account Reference (PAR) (April 2016)
Terminal [Batch Data Capture] AND [DDA] supported
Configuration:
Conditions:
•
Response to INTERNAL AUTHENTICATE contains PAR Data
Object (tag 9F24) and shall be encoded in template 77
Action: NA
Procedure: Application in LT is selected and transaction is performed online with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC at First or Second
GENERATE AC
•
The Batch Data Capture shall contains the PAR Data Object with
same value as contained in LT.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 215
2CA.135.00 PAR Data in Reserval
Test No: 2CA.135.00 - Revision 43e - Number of sub cases: 5
Objective: To ensure that the presence of PAR Data Object in the data field returned
by LT command is transmitted in the Reversal.
Reference
EMV 4.3: Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data
Objects – Payment Account Reference (PAR) (April 2016)
Terminal [Online Data Capture] AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
IAC’s and TAC’s are set so that ARQC is requested at first
GENERATE AC.
•
LT returns ARQC at first GENERATE AC
•
Transactions are captured online (financial message)
•
Authorization Response Code returned is 'online approved'
•
LT returns AAC to second GENERATE AC.
•
Case 01: Response to GET PROCESSING OPTIONS contains
PAR Data Object (tag 9F24) and shall be encoded in template 77
•
Case 02: Response to First GENERATE AC contains PAR Data
Object (tag 9F24) and shall be encoded in template 77
•
Case 03: An EMV Record (in the SFI range 1 to 10) to be read
contains PAR Data Object (tag 9F24)
•
Case 04: An EMV Record (in the SFI range 11 to 20) to be read
contains PAR Data Object (tag 9F24)
•
Case 05: An EMV Record (in the SFI range 21 to 30) to be read
contains PAR Data Object (tag 9F24)
Action: NA
Procedure: Application in LT is selected and transaction is performed online with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion
•
The Terminal shall format and transmit a Reversal Message in
real time containing the PAR Data Object
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 216
2CA.136.00 PAR Data in Reserval (2)
Test No: 2CA.136.00 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the presence of PAR Data Object in the data field returned
by INTERNAL AUTHENTICATE command is transmitted in the Reversal.
Reference
EMV 4.3: Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data
Objects – Payment Account Reference (PAR) (April 2016)
Terminal [Online Data Capture] AND [DDA] AND ([Online Only] OR [Offline/Online
Configuration: capable]) supported
Conditions:
•
IAC’s and TAC’s are set so that ARQC is requested at first
GENERATE AC.
•
LT returns ARQC at first GENERATE AC
•
Transactions are captured online (financial message)
•
Authorization Response Code returned is 'online approved'
•
LT returns AAC to second GENERATE AC.
•
Response to INTERNAL AUTHENTICATE contains PAR Data
Object (tag 9F24) and shall be encoded in template 77
Action: NA
Procedure: Application in LT is selected and transaction is performed online with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion
•
The Terminal shall format and transmit a Reversal Message in
real time containing the PAR Data Object
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 217
2CA.137.00 PAR Data in Online Advice
Test No: 2CA.137.00 - Revision 43e - Number of sub cases: 5
Objective: To ensure that the presence of PAR Data Object in the data field returned
by LT command is transmitted in the Online Advice.
Reference
EMV 4.3: Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data
Objects – Payment Account Reference (PAR) (April 2016)
Terminal [Online Data Capture] AND [Advice] AND ([Online Only] OR [Offline/Online
Configuration: capable]) supported
Conditions:
•
LT requests an Advice in response to First GENERATE AC.
•
LT returns AAC at first GENERATE AC
•
Case 01: Response to GET PROCESSING OPTIONS contains
PAR Data Object (tag 9F24) and shall be encoded in template 77
•
Case 02: Response to First GENERATE AC contains PAR Data
Object (tag 9F24) and shall be encoded in template 77
•
Case 03: An EMV Record (in the SFI range 1 to 10) to be read
contains PAR Data Object (tag 9F24)
•
Case 04: An EMV Record (in the SFI range 11 to 20) to be read
contains PAR Data Object (tag 9F24)
•
Case 05: An EMV Record (in the SFI range 21 to 30) to be read
contains PAR Data Object (tag 9F24)
Action: NA
Procedure: Application in LT is selected and transaction is performed online with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion
•
The Terminal shall format and transmit a Advice in real time
containing the PAR Data Object
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 218
2CA.138.00 PAR Data in Online Advice (2)
Test No: 2CA.138.00 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the presence of PAR Data Object in the data field returned
by INTERNAL AUTHENTICATE command is transmitted in the Online
Advice.
Reference
Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data
EMV 4.3:
Objects – Payment Account Reference (PAR) (April 2016)
Terminal [Online Data Capture] AND [Advice] AND [DDA] AND ([Online Only] OR
Configuration: [Offline/Online capable]) supported
Conditions:
•
LT requests an Advice in response to First GENERATE AC.
•
LT returns AAC at first GENERATE AC
•
Response to INTERNAL AUTHENTICATE contains PAR Data
Object (tag 9F24) and shall be encoded in template 77
Action: NA
Procedure: Application in LT is selected and transaction is performed online with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion
•
The Terminal shall format and transmit a Advice in real time
containing the PAR Data Object
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 219
2CA.139.00 PAR Data supported
Test No: 2CA.139.00 - Revision 43e - Number of sub cases: 5
Objective: To ensure that the presence of PAR data object in the data field returned
by LT command is ignored when the terminal does not use it, or accepts
when the terminal use it.
Reference
EMV 4.3: Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data
Objects – Payment Account Reference (PAR) (April 2016)
Terminal NA
Configuration:
Conditions:
•
Case 01: Response to GET PROCESSING OPTIONS contains
PAR Data Object (tag 9F24) and shall be encoded in template 77
•
Case 02: Response to First GENERATE AC contains PAR Data
Object (tag 9F24) and shall be encoded in template 77
•
Case 03: An EMV Record (in the SFI range 1 to 10) to be read
contains PAR Data Object (tag 9F24)
•
Case 04: An EMV Record (in the SFI range 11 to 20) to be read
contains PAR Data Object (tag 9F24)
•
Case 05: An EMV Record (in the SFI range 21 to 30) to be read
contains PAR Data Object (tag 9F24)
Action: NA
Procedure: Application in LT is selected and transaction is performed online with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC on first GENERATE AC or
Second GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 220
2CA.140.00 PAR Data supported (2)
Test No: 2CA.140.00 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the presence of PAR data object in the data field returned
by INTERNAL AUTHENTICATE command is ignored when the terminal
does not use it, or accepts when the terminal use it.
Reference
EMV 4.3: Book Bulletins - Section SB 178 - Bulletin n°178, Tokenisation Data
Objects – Payment Account Reference (PAR) (April 2016)
Terminal [DDA] supported
Configuration:
Conditions:
•
Response to INTERNAL AUTHENTICATE contains PAR Data
Object (tag 9F24) and shall be encoded in template 77
Action: NA
Procedure: Application in LT is selected and transaction is performed online with LT.
Pass Criteria:
•
The terminal shall accept the card and process the transaction
until completion, by requesting a TC on first GENERATE AC or
Second GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 221
7.2 Application Selection
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 222
2CB.002.00 Definition of PSE
Test No: 2CB.002.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, it understands
PSE format and in particular recognize the FCI of the PSE and optional
data objects.
Reference Book 1 - Section 11.3.3 - Data Field Sent in the Command Message
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions: NA
Action: NA
Procedure: Application Selection with PSE process is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
LT shall received a READ RECORD command with SFI coded
according to SFI returned in FCI.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 223
2CB.004.00 Definition of a Record in Payment Systems Directory
Test No: 2CB.004.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, it understands
the format of records contained in the Directory file of PSE and in
particular records with several entries.
Reference Book 1 - Section 12.2.3 - Coding of a Payment System Directory
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
PSE contains a directory file with entries for ADF.
•
The first record of the directory contains three entries for ADF.
Action: NA
Procedure: Application Selection with PSE process is performed for all supported
priority hierarchies.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
LT shall receive a second READ RECORD command with SFI
coded according to SFI returned in FCI of the SELECT PSE
command.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 224
2CB.005.00 Definition of Directory Entry Format
Test No: 2CB.005.00 - Revision 4.2a - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, it ignores
unexpected Tags that would appear in directory entry and any data
objects not encapsulated in an Application Template which appear in the
directory record.
Reference Book 1 - Section 12.2.3 - Coding of a Payment System Directory
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
PSE contains a directory file with entries for ADF.
•
first record of directory file contains:
•
Template '73' contains: Proprietary tag '5F 50' with max length
and any value.
Action: NA
Procedure: Application Selection with PSE process is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
LT shall receive a second READ RECORD command with SFI
coded according to SFI returned in FCI of the SELECT PSE
command.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 225
2CB.007.00 Terminal's List of Supported Applications
Test No: 2CB.007.00 - Revision 10g - Number of sub cases: 0
Objective: To verify that the terminal maintains a list of applications with their AIDs.
Reference Book 1 - Section 12.3 - Building the Candidate List
EMV 4.3:
Terminal NA
Configuration:
Conditions: LT does not support PSE selection in order to force the terminal to apply
another selection technique ( by using its list of AID's ).
Action: NA
Procedure: Application Selection with AID is performed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The terminal generates SELECT command for each AID stored
within the terminal.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 226
2CB.010.00 Matching AIDS: « same AID » criteria supported
Test No: 2CB.010.00 - Revision 4.3d - Number of sub cases: 2
Objective: To ensure that the terminal keeps for each application an indication of
which matching criteria to use, and in particular that the terminal is able
to support « AID match AID kept in terminal » criteria.
Reference Book 1 - Section 12.3.1 - Matching Terminal Applications to ICC
EMV 4.3: Applications
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] supported
Configuration:
Conditions:
•
LT contains an application with AID matching AID kept in
terminal.
•
Terminal supports « AID match AID kept in terminal » criteria for
this application.
•
A list is presented to the cardholder.
•
Case 01: LT does not contains other applications.
•
Case 02: LT contains other applications supported by the
Terminal.
Action: Cardholder selects an Application in the list when displayed by the
terminal
Procedure: Application Selection using list of AID is performed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC with the Application selected by the
Cardholder.
•
Terminal shall display to cardholder which applications can be
selected.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 227
2CB.010.01 Matching AIDS: « same AID » criteria supported (2)
Test No: 2CB.010.01 - Revision 4.3d - Number of sub cases: 2
Objective: To ensure that the terminal keeps for each application an indication of
which matching criteria to use, and in particular that the terminal is able
to support « AID match AID kept in terminal » criteria.
Reference Book 1 - Section 12.3.1 - Matching Terminal Applications to ICC
EMV 4.3: Applications
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] not supported
Configuration:
Conditions:
•
LT contains an application with AID matching AID kept in
terminal with the highest priority.
•
Terminal supports « AID match AID kept in terminal » criteria for
this application.
•
Case 01: LT does not contains other applications.
•
Case 02: LT contains other applications supported by the
Terminal.
Action: NA
Procedure: Application Selection using list of AID is performed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
Terminal shall select the application with the highest priority.
•
No Cardholder Selection or Confirmation is requested by the
terminal.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 228
2CB.011.00 Matching AIDs: « AID beginning with Terminal AID »
criteria supported
Test No: 2CB.011.00 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that the terminal keeps for each application an indication of
which matching criteria to use, and in particular that the terminal is able
to support « AID beginning with terminal AID» criteria.
Reference Book 1 - Section 12.3.1 - Matching Terminal Applications to ICC
EMV 4.3: Applications
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] supported
Configuration:
Conditions:
•
Terminal supports three AIDs but one of the supported AIDs
has a value matching the beginning of all AIDs in LT. All AIDs
have ASI indicating partial match is accepted.
•
LT contains three applications. The beginning of the AID of
these applications is identical and match the beginning of one of
the AIDs kept in terminal.
•
Applications in the LT have different priorities.
•
A list is presented to the cardholder.
Action: Cardholder selects an Application in the list when displayed by the
terminal
Procedure: Application Selection using list of AID is performed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC with the Application selected by the
Cardholder.
•
Terminal shall display to cardholder which applications can be
selected.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 229
2CB.011.01 Matching AIDs: « AID beginning with Terminal AID »
criteria supported (2)
Test No: 2CB.011.01 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that the terminal keeps for each application an indication of
which matching criteria to use, and in particular that the terminal is able
to support « AID beginning with terminal AID» criteria.
Reference Book 1 - Section 12.3.1 - Matching Terminal Applications to ICC
EMV 4.3: Applications
Terminal [Cardholder Confirmation] not supported
Configuration:
Conditions:
•
Terminal supports three AIDs but one of the supported AIDs
has a value matching the beginning of all AIDs in LT. All AIDs
have ASI indicating partial match is accepted.
•
LT contains three applications. The beginning of the AIDs of
these applications is identical and match the beginning of one of
the AIDs kept in terminal.
•
Applications in the LT have different priorities.
Action: NA
Procedure: Application Selection using list of AIDs is performed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
Terminal shall select the application with the highest priority.
•
No Cardholder Selection or Confirmation is requested by the
terminal.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 230
2CB.012.00 Selection Using the Payment Systems Directory:
SELECT PSE
Test No: 2CB.012.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, it sends a
SELECT '1PAY.SYS.DDF01' command.
Reference Book 1 - Section 12.3.2 - Using the PSE
EMV 4.3:
Book 3 - Section 6.3.5 - Coding of the Status Bytes
Terminal [PSE] supported
Configuration:
Conditions:
•
LT response to select PSE is '90 00' with response data.
Action: NA
Procedure: Application Selection with PSE process is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
LT shall receive a SELECT '1PAY.SYS.DDF01' command.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 231
2CB.013.00 Selection Using the Payment Systems Directory: Card
Blocked or Command Not Supported
Test No: 2CB.013.00 - Revision 10d - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, and card
returns '6A 81' in response to the SELECT PSE command, the terminal
terminates the transaction.
Reference Book 1 - Section 12.3.2 - Using the PSE
EMV 4.3:
Book 3 - Section 6.3.5 - Coding of the Status Bytes
Terminal [PSE] supported
Configuration:
Conditions: LT returns '6A 81' to SELECT PSE command.
Action: NA
Procedure: Application Selection with PSE process is performed.
Pass Criteria: The terminal shall terminate the transaction.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 232
2CB.016.00 Indicating end of record
Test No: 2CB.016.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, the terminal
selects PSE and sends READ RECORD commands until card responds
with '6A 83'.
Reference Book 1 - Section 12.3.2 - Using the PSE
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
LT contains a PSE directory file with three entries in two
records.
Action: NA
Procedure: Application Selection with PSE process is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
LT shall receive a sequence of READ RECORD commands
until the LT answers with '6A 83'.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 233
2CB.017.00 Directory entry does not exist
Test No: 2CB.017.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, and the card
answers '6A 83' to a READ RECORD for record number 1, the terminal
switches to the list of applications method.
Reference Book 1 - Section 12.3.2 - Using the PSE
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
LT answers '6A 83' to a READ RECORD of the PSE directory
file for record number 1.
Action: NA
Procedure: Application Selection with PSE process is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
LT shall receive a sequence of SELECT 'AID' commands after
the LT returns '6A 83' to READ RECORD of the PSE directory
file for record number 1.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 234
2CB.018.00 Directory entry processing
Test No: 2CB.018.00 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, the terminal
begins with the first entry of first record of the directory file and processes
each entry in turn.
Reference Book 1 - Section 12.3.2 - Using the PSE
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal (([PSE] supported AND [Cardholder Confirmation] supported) AND
Configuration: [Preferred Order] not supported)
Conditions:
•
Terminal supports all ADFs listed in the directory of the LT (for
selection process only).
•
LT contains a Directory file with three entries in one record.
•
All applications in the LT have no priorities.
Action: Cardholder selects an Application in the list when displayed by the
terminal
Procedure: Application Selection with PSE process is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC with the Application selected by the
Cardholder.
•
All mutually supported applications shall be displayed to the
Cardholder.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 235
2CB.019.01 Candidate list with exact match (2)
Test No: 2CB.019.01 - Revision 4.3d - Number of sub cases: 3
Objective: To ensure that if the terminal supports selection with PSE the terminal
adds the application to the 'candidate list' whenever an entry in directory
file exactly matches the name of one of the applications supported by
the terminal.
Reference Book 1 - Section 12.3.2 - Using the PSE
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal ([PSE] supported AND [Cardholder Confirmation] supported)
Configuration:
Conditions:
•
Terminal supports all ADFs listed in the directories of the LT (for
selection process only).
•
LT contains a PSE Directory file with entries for application 1,
applications 2 and 3.
•
LT contains the 3 applications (ADF) (all listed in the PSE
Directory file).
•
All AIDs of the LT applications exactly match the ones
supported by the terminal.
•
Case 01: in Directory file all entries have priorities and the
highest priority is on the first entry.
•
Case 02: in Directory file all entries have priorities and the
highest priority is on the second entry.
•
Case 03: in Directory file all entries have priorities and the
highest priority is on the third entry.
Action: Cardholder selects an Application in the list when displayed by the
terminal
Procedure: Application Selection with PSE process is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC with the Application selected by the
Cardholder.
•
all applications are in the list displayed to the cardholder.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 236
2CB.019.02 Candidate list with exact match (3)
Test No: 2CB.019.02 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSEthe terminal
adds the application to the 'candidate list' whenever an entry in directory
file exactly matches the name of one of the applications supported by
the terminal.
Reference Book 1 - Section 12.3.2 - Using the PSE
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal ([PSE] supported AND [Cardholder Confirmation] not supported)
Configuration:
Conditions:
•
Terminal supports all ADFs listed in the directories of the LT (for
the selection process).
•
LT contains a PSE Directory file with entries for application 1,
applications 2 and 3.
•
LT contains the 3 applications (ADF) (all listed in the PSE
Directory file).
•
Application 3 has the highest priority.
•
All AIDs of the LT application exactly match the ones supported
by the terminal.
Action: NA
Procedure: Application Selection with PSE process is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
The terminal select the application with the highest priority.
•
No Cardholder Selection or Confirmation is requested by the
terminal.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 237
2CB.019.04 Candidate list with partial match (2)
Test No: 2CB.019.04 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE the terminal
adds the application to the 'candidate list' whenever an entry in directory
file partially matches the name of one of the applications supported by
the terminal and the ASI supports partial match.
Reference Book 1 - Section 12.3.2 - Using the PSE
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal ([PSE] supported AND [Cardholder Confirmation] supported)
Configuration:
Conditions:
•
Terminal supports all ADFs listed in the directory of the LT (for
selection process only).
•
ASI supports partial name match.
•
LT contains a PSE Directory file with entries for application 1,
applications 2 and 3.
•
LT contains the 3 applications (ADF) (all listed in the PSE
Directory file).
•
All AIDs of LT applications partially match the ones supported
by the terminal.
Action: Cardholder selects an Application in the list when displayed by the
terminal
Procedure: Application Selection with PSE process is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC with the Application selected by the
Cardholder.
•
All threeapplications, are in the list displayed to the cardholder.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 238
2CB.019.05 Candidate list with partial match (3)
Test No: 2CB.019.05 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, the terminal
adds the application to the 'candidate list' whenever an entry in directory
file partially matches the name of one of the applications supported by
the terminal and the ASI supports partial match.
Reference Book 1 - Section 12.3.2 - Using the PSE
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal ([PSE] supported AND [Cardholder Confirmation] not supported)
Configuration:
Conditions:
•
Terminal supports all ADFs listed in the directory of the LT (for
selection process only).
•
ASI supports partial match name.
•
LT contains a PSE Directory file with entries for application 1,
applications 2 and 3.
•
LT contains the 3 applications (ADF) (all listed in the PSE
Directory file).
•
Application 3 has the highest priority.
•
All AIDs of the LT applications partially match the ones
supported by the terminal.
Action: NA
Procedure: Application Selection with PSE process is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
The terminal selects the application with the highest priority.
•
No Cardholder Selection or Confirmation is requested by the
terminal.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 239
2CB.023.00 Candidate List empty after selection with PSE
Test No: 2CB.023.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports selection with PSE, and if
processing yields no directory entries that match applications supported
by the terminal, the terminal switches to the list of applications method.
Reference Book 1 - Section 12.3.2 - Using the PSE
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions: No directory entries match applications supported by the terminal during
SELECT PSE processing.
Action: NA
Procedure: Application Selection with PSE process is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The terminal shall switch to the AID list method.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 240
2CB.023.01 Failed Processing for READ RECORD in selection by
PSE
Test No: 2CB.023.01 - Revision 11 - Number of sub cases: 11
Objective: To ensure if a status word error occurs (ie not ’90 00’ or ‘6A 83’) in PSE
Application Selection, READ RECORD the terminal clears the candidate
list and switches to List of AIDs selection.
Reference Book 1 - Section 12.3.2 - Using the PSE
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
LT contains PSE.
•
LT and terminal contain 3 mutually supported applications
•
The 2nd READ RECORD command for PSE Application
Selection returns the following status value
•
Case 01: LT returns status value '63 00' in response to READ
RECORD
•
Case 02: LT returns status value '63 Cx' in response to READ
RECORD
•
Case 03: LT returns status value '69 83' in response to READ
RECORD
•
Case 04: LT returns status value '69 84' in response to READ
RECORD
•
Case 05: LT returns status value '69 85' in response to READ
RECORD
•
Case 06: LT returns status value '6A 81' in response to READ
RECORD
•
Case 07: LT returns status value '6A 82' in response to READ
RECORD
•
Case 08: LT returns status value '6A 88' in response to READ
RECORD
•
Case 09: LT returns status value '64 00' in response to READ
RECORD
•
Case 10: LT returns status value '65 00' in response to READ
RECORD
•
Case 11: LT returns status value '90 01' in response to READ
RECORD
Action: NA
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 241
2CB.023.01 Failed Processing for READ RECORD in selection by
PSE
Procedure: The first application in the candidate list in selected, then removed and
the terminal initiate the selection of the second mutually supported
application.
Pass Criteria:
•
In response to the status words, the terminal shall terminate
PSE processing and return to the application selection function
using the list of AID
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 242
2CB.024.00 Selection using a list of AIDs
Test No: 2CB.024.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal is able to manage a selection using a list of
AIDs.
To ensure that if the terminal uses the list of AID method, it issues the
first SELECT command using the first AID in the list.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Terminal NA
Configuration:
Conditions: Terminal supports several Applications
Action: NA
Procedure: Application Selection using list of AID is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
LT shall receive the first SELECT 'AID' command with the first
AID contained in the terminal's AID list.
•
LT shall receive a SELECT 'AID' command for each application
supported by the terminal.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 243
2CB.025.06 DF name and AID identical & SELECT command
successful
Test No: 2CB.025.06 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the DF name and the AID are identical, and SELECT
command is successful (SW1 SW2 = '9000'), the terminal adds the FCI
information from the selected file to the candidate list and issues another
SELECT command using the next AID in its list.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Terminal supports selection by AID.
•
Terminal supports at least two applications.
•
LT supports at least the first application specified in the first
SELECT command (AID and DF name are identical).
•
The LT answers with '90 00" to the first SELECT command.
Action: NA
Procedure: Application selection with the list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The terminal shall issue at least three SELECT commands
including a "final" SELECT command.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 244
2CB.026.05 DF name and AID identical & application blocked
Test No: 2CB.026.05 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the DF name and the AID are identical, and application
is blocked (SW1 SW2 = '6283'), the terminal issues another SELECT
command using the next AID in its list, without adding the DF name to
the candidate list.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Terminal supports selection by AID.
•
Terminal supports at least two applications.
•
The LT answers with '62 83" to the first SELECT command
Action: NA
Procedure: Application selection with the list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The terminal shall issue at least two SELECT commands.
•
The first AID that responded with '62 83' during selection shall
not be a part of the candidate list for final select.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 245
2CB.028.00 Selection using a list of AIDs
Test No: 2CB.028.00 - Revision 10g - Number of sub cases: 11
Objective: To ensure that the terminal proceeds to SELECT the next application in
its AID list following a status different from '90 00' or '6A 81' or '62 83'
returned by the card and does not add the AID in the candidate list.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Book 3 - Section 6.3.5 - Coding of the Status Bytes
Terminal NA
Configuration:
Conditions:
•
Terminal supports at least 3 AIDs mutually supported by LT.
•
The LT answers with the following status to SELECT
Application command for one of the AIDs mutually supported:
•
Case 01: LT returns status value of '63 00' in response to
SELECT Application.
•
Case 02: LT returns status value of '63 Cx' in response to
SELECT Application.
•
Case 03: LT returns status value of '69 83' in response to
SELECT Application.
•
Case 04: LT returns status value of '69 84' in response to
SELECT Application.
•
Case 05: LT returns status value of '69 85' in response to
SELECT Application.
•
Case 06: LT returns status value of '6A 82' in response to
SELECT Application.
•
Case 07: LT returns status value of '6A 83' in response to
SELECT Application.
•
Case 08: LT returns status value of '6A 88' in response to
SELECT Application.
•
Case 09: LT returns status value of '90 01' in response to
SELECT Application.
•
Case 10: LT returns status value of '64 00' in response to
SELECT Application.
•
Case 11: LT returns status value of '65 00' in response to
SELECT Application.
Action: NA
Procedure: Application Selection using list of AIDs is performed.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 246
2CB.028.00 Selection using a list of AIDs
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
After having sent status values different from '90 00' or '6A 81'
or '62 83' in answer to SELECT of the specific AID above, the
LT shall receive SELECT 'AID' with AID of next application in
the terminal AID list.
•
Terminal shall indicate to cardholder which applications can be
selected or select one of the two other mutually supported
applications.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 247
2CB.029.00 Selection using a list of AIDs: candidate list completion
Test No: 2CB.029.00 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that the terminal completes the candidate list when there are
no more AIDs to select in the terminal list.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] supported AND [PSE] not supported
Configuration:
Conditions:
•
Terminal supports at least 2 AIDs also supported by the LT
•
The LT contains one AID not supported by the terminal.
Action: Cardholder selects an Application in the list when displayed by the
terminal
Procedure: Application Selection using list of AID is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC with the Application selected by the
Cardholder.
•
The LT shall receive SELECT AID commands for all AIDs in the
terminal list.
•
Terminal shall display to cardholder which applications can be
selected.
•
Terminal shall not display the AID not supported
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 248
2CB.031.00 Application Selection Indicator: One Occurrence
Permitted
Test No: 2CB.031.00 - Revision 4.2b - Number of sub cases: 0
Objective: To ensure that if the DFNAME in the ICC is longer than that of the AID
in the terminal, but they are identical up to and including the last
character in the terminal AID, the terminal shall check the Application
Selection indicator.
If the indicator says only one occurrence is allowed the terminal does not
add the AID to the candidate list and issue another SELECT command
using the next AID.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
DF Name contained in FCI returned by the LT for first AID
selection is longer than that of terminal AID used for selection,
but they are identical up to and including the last character in
the terminal AID.
•
Terminal Application Selection Indicator only allows one
occurrence for selected AID.
•
LT shall contain another DF Name exactly matching the
terminal AID.
Action: NA
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
After SELECT AID command, the LT shall:
- either receive SELECT 'AID' with P2 option set to 'next ' until LT answer
is '6A 82',
- or receive an SELECT 'AID' command but with the next AID name.
•
The terminal will not store the first AID as a selectable
application.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 249
2CB.031.06 DF name longer than AID & multiple occurrence &
application not blocked
Test No: 2CB.031.06 - Revision 4.2b - Number of sub cases: 3
Objective: To ensure that if the DF name in the ICC is longer than that of the AID in
the terminal but are identical up to and including the last character in the
terminal AID, the terminal shall check the Application Selection indicator.
If the Application Selection Indicator indicates that multiple occurrence
are permitted and if the application is not blocked, the terminal adds the
AID to the candidate list and repeats the SELECT command using the
same command data as before, but changes P2 in the command to '02'.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Terminal supports at least the three AID’s of LT.
•
Terminal Application Selection Indicator allows multiple
occurrences for selected AID.
•
LT contain three ADF’s
•
DF Names returned in FCI by the LT for all AID selections are
longer than terminal AIDs used for selection, but they are
identical up to and including the last character in the terminal
AID.
•
Application Priority Indicator of the three AIDs are different and
in such a way that the AID with highest priority is the one
returned on the last SELECT NEXT command.
•
LT answers '90 00' to the first SELECT NEXT command.
•
Case 01: LT answers '6A 82 ' to the second SELECT NEXT
command.
•
Case 02: LT answers '90 00 ' to the second SELECT NEXT
command and '6A 82' to the third SELECT NEXT command.
•
Case 03: LT answers '90 00 ' to the second and third SELECT
NEXT command and '6A 82' to the fourth SELECT NEXT
command.
Action: NA
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 250
2CB.031.06 DF name longer than AID & multiple occurrence &
application not blocked
•
After the first SELECT AID command, the LT shall receive
several SELECT 'AIDs' with P2 option set to 'next'.
•
The terminal shall select the full AID with the highest priority as
provided by the LT successful SELECT NEXT response (SW1
SW2 = ’90 00’) and process the transaction using that full AID .
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 251
2CB.031.07 DF name longer than AID & multiple occurrence &
application blocked
Test No: 2CB.031.07 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the DF name in the ICC is longer than the AID in the
terminal, but they are identical up to and including the last character in
the terminal AID, the terminal shall check the Application Selection
indicator.
If the Application Selection Indicator indicates that multiple occurrence
are permitted and if the application is blocked, the terminal does not add
the AID to the candidate list and repeats the SELECT command using
the same command data as before, but changes P2 in the command to
'02'.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Terminal supports at least one AID.
•
Terminal Application Selection Indicator allows multiple
occurrences for selected AIDs.
•
DF Name contained in FCI returned by the LT for first AID
selection is longer than that of terminal AID used for selection
but they are identical up to and including the last character in
the terminal AID.
•
LT answers '62 83' to the first SELECT command.
Action: NA
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
After SELECT AID command, the LT shall receive SELECT
'AID' commands with P2 option set to 'next ' until LT answers
'6A 82'.
•
The terminal shall not store the first AID as a selectable
application.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 252
2CB.031.08 DF name longer than AID & multiple occurrence
Test No: 2CB.031.08 - Revision 4.3d - Number of sub cases: 3
Objective: To ensure that if several AID are mutually supported and terminal
provides for cardholder confirmation, the terminal select the application
that the cardholder has confirmed/selected during a selection with partial
Name.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] supported
Configuration:
Conditions:
•
There are three matching AID between LT and Terminal (value
5 bytes).
•
Terminal Application Selection Indicator allows multiple
occurrences for selected AID.
•
LT contain three ADF’s
•
DF Names returned in FCI by the LT for all AID selections are
longer than terminal AIDs used for selection, but they are
identical up to and including the last character in the terminal
AID. Remaining bytes of the DF Names are for AID 1: 10 10 01,
for AID 2: 10 10 02 and for AID 3: 10 10 03,
•
LT answers '90 00' to the first, second and third SELECT NEXT
command and '6A 82' to the fourth SELECT NEXT command.
•
Case 01: Cardholder select AID 1
•
Case 02: Cardholder select AID 2
•
Case 03: Cardholder select AID 3
Action: Cardholder select the AID as described in subcases when displayed by
the terminal
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC with the Application selected by the
Cardholder.
•
After the first SELECT AID command, the LT shall receive
several SELECT 'AIDs' with P2 option set to 'next'.
•
The terminal shall display the 3 application and request
confirmation/selection from the cardholder and shall generate a
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 253
2CB.031.08 DF name longer than AID & multiple occurrence
final SELECT AID command on the selected AID (AID 1 for
Case 01, AID 2 for Case 02 and AID 3 for Case 03)
•
AID contained in the Final SELECT command matches ADF
returned by the LT
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 254
2CB.032.00 DFNAME is different from AID
Test No: 2CB.032.00 - Revision 11 - Number of sub cases: 2
Objective: To ensure that the terminal does not repeat a SELECT command using
partial name option if the DF Name returned in FCI is different or shorter
than that of terminal AID used for selection, but continues processing
with next AID in the terminal list.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Terminal supports at least 2 AIDs
•
Case 01: DF Name contained in FCI returned by the LT for first
AID selection is shorter than that of terminal AID used for
selection.
•
Case 02 DF Name contained in FCI returned by the LT for first
AID selection is different than that of terminal AID used for
selection.
Action: NA
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
After having responded '90 00' and returned FCI with bad DF
Name to first SELECT AID, the LT shall receive SELECT 'AID'
with AID of next application in the terminal AID list.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 255
2CB.034.00 Multiple occurrence of application: next option
supported: 90 00
Test No: 2CB.034.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that, if the card returns '90 00' to a SELECT command with
'next' option, the terminal adds the DFNAME from the FCI of the selected
file to the candidate list and continues Application selection process.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Terminal's Application Selection Indicator allows multiple
occurrences for the AID.
•
Terminal supports at least 2 AIDs.
•
DF Name contained in FCI returned by the LT for first AID
selection is longer than that of terminal AID used for selection
but they are identical up to and including the last character in
the terminal AID.
•
LT returns '90 00' to a SELECT command with 'next' option (3
applications with same beginning of AID in LT).
Action: NA
Procedure: Application Selection using list of AID is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The LT shall receive a sequence of SELECT 'AIDs' with P2
option set to 'next ' until LT answer is '6A 82'. After this
sequence, the LT shall receive SELECT 'AID' with AID of next
application in the terminal AID list.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 256
2CB.035.00 Multiple occurrence of application: next option failed:
62 83
Test No: 2CB.035.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal does not add the AID in the candidate list if
the card returns '62 83' to a SELECT command with 'next' option, and
proceeds to check for the possibility of multiple occurrences of the
application in the ICC before selecting the next AID from the list.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Terminal supports at least 2 AIDs
•
DF Name contained in FCI returned by the LT for first AID
selection is longer than that of terminal AID used for selection
but they are identical up to and including the last character in
the terminal AID.
•
LT returns '62 83' to first SELECT command with 'next' option.
•
LT returns '6A 82' to following SELECT command with 'next'
option.
Action: NA
Procedure: Application Selection using list of AID is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
After having sent status '62 83' in answer to SELECT of the
specific AID above, the LT shall receive SELECT 'AID'
command with 'next' option and same value for AID.
•
The candidate list shall not contain the AID returning '62 83' as
response to SELECT.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 257
2CB.036.00 Multiple occurrence of application: next option failed:
other
Test No: 2CB.036.00 - Revision 10g - Number of sub cases: 12
Objective: To ensure that the terminal proceeds to SELECT the next application in
its AID list, if the card returns status values different from '90 00' or '62
83' to a SELECT command with 'next' option.
Reference Book 1 - Section 12.3.3 - Using a List of AIDs
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
Terminal supports at least 2 AIDs
•
DF Name contained in FCI returned by the LT for first AID
selection is longer than that of terminal AID used for selection
but they are identical up to and including the last character in
the terminal AID.
•
Case 01: LT returns status '63 00' to a SELECT command with
'next' option.
•
Case 02: LT returns status '63 Cx' to a SELECT command with
'next' option.
•
Case 03: LT returns status '69 83' to a SELECT command with
'next' option.
•
Case 04: LT returns status '69 84' to a SELECT command with
'next' option.
•
Case 05: LT returns status '69 85' to a SELECT command with
'next' option.
•
Case 06: LT returns status '6A 81' to a SELECT command with
'next' option.
•
Case 07: LT returns status '6A 82 ' to a SELECT command with
'next' option.
•
Case 08: LT returns status '6A 83' to a SELECT command with
'next' option.
•
Case 09: LT returns status '6A 88' to a SELECT command with
'next' option.
•
Case 10: LT returns status '64 00' to a SELECT command with
'next' option.
•
Case 11: LT returns status '65 00' to a SELECT command with
'next' option.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 258
2CB.036.00 Multiple occurrence of application: next option failed:
other
•
Case 12: LT returns status '90 01' to a SELECT command with
'next' option.
Action: NA
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
After having sent status values different from '90 00'or '62 83' in
answer to SELECT of the specific AID above, the LT shall
receive a SELECT 'AID' with AID of next application in the
terminal AID list.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 259
2CB.037.00 Final Selection: no mutually supported application
Test No: 2CB.037.00 - Revision 11 - Number of sub cases: 0
Objective: To ensure that the terminal terminates the transaction if there are no
mutually supported applications (candidate list empty).
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
LT does not support PSE
•
There are no matching AIDs between LT and Terminal.
Action: NA
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria: The terminal shall terminate the transaction.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 260
2CB.038.00 Final Selection: one mutually supported application
Test No: 2CB.038.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if only one AID is mutually supported and b8 of Application
priority indicator equals 0, the terminal selects this AID.
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
There is one matching AID between LT and Terminal.
•
b8 of Application Indicator returned by LT equals 0.
Action: NA
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The terminal shall select the mutually supported AID.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 261
2CB.038.01 Final Selection: Terminal AID match DF Name and Card
AID
Test No: 2CB.038.01 - Revision 10g - Number of sub cases: 4
Objective: To ensure if AID used by the terminal in the final SELECT command
matches the DF Name (tag '84') returned by the ICC in the FCI), the
terminal shall set the value of the terminal data element ‘Application
Identifier (AID) – terminal’ (tag '9F06') to the same value as the ‘DF
Name’ (tag '84') returned in the FCI.’
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
There is one matching AID between LT and Terminal.
•
The DF Name and Card AID have the same value
•
b8 of Application Indicator returned by LT equals 0.
•
The PDOL of LT contains the Terminal AID
•
Case 01: AID has a 5 bytes length
•
Case 02 AID has 7 bytes length
•
Case 03: AID has 8 bytes length
•
Case 04: AID has 16 bytes length
Action: NA
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC .
•
The terminal shall select the mutually supported AID.
•
Terminal AID (tag 9F06) populated in GPO command shall be
the same as DF name (tag 84) returned in FCI
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 262
2CB.039.00 Final Selection: cardholder confirmation
Test No: 2CB.039.00 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that if only one AID is mutually supported, b8 of Application
priority indicator equals 1 and terminal provides for cardholder
confirmation, the terminal requests confirmation and selects the
application if the cardholder approves.
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] supported
Configuration:
Conditions:
•
There is one matching AID between LT and Terminal.
•
b8 of Application Indicator returned by LT equals 1.
Action: Cardholder approves the selection.
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
The terminal shall request confirmation from the cardholder and
shall generate a SELECT AID command as response to that
confirmation.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 263
2CB.039.01 Final Selection: cardholder confirmation (2)
Test No: 2CB.039.01 - Revision 4.3d - Number of sub cases: 3
Objective: To ensure that if several AID are mutually supported and terminal
provides for cardholder confirmation, the terminal select the application
that the cardholder has confirmed/selcted.
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] supported
Configuration:
Conditions:
•
There are three matching AID between LT and Terminal: AID 1
has the value xx xx xx xx xx 10 10 01, AID 2 has the value xx xx
xx xx xx 10 10 02 and AID 3 has the value xx xx xx xx xx 10 10
03, where xx xx xx xx xx is identical for the three AID.
•
Case 01: Cardholder select AID 1
•
Case 02: Cardholder select AID 2
•
Case 03: Cardholder select AID 3
Action: Cardholder select the AID as described in subcases when displayed by
the terminal
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC with the Application selected by the
Cardholder.
•
The terminal shall display the 3 application and request
confirmation/selection from the cardholder and shall generate a
final SELECT AID command on the selected AID (AID 1 for
Case 01, AID 2 for Case 02 and AID 3 for Case 03)
•
AID contained in the Final SELECT command matches ADF
returned by the LT
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 264
2CB.040.00 Final Selection: no cardholder confirmation
Test No: 2CB.040.00 - Revision 11 - Number of sub cases: 0
Objective: To ensure that if only one AID is mutually supported, b8 of Application
priority indicator equals 1, and terminal does not provide for cardholder
confirmation, the terminal terminates the transaction.
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Terminal [Cardholder Confirmation] not supported
Configuration:
Conditions:
•
There is one matching AID between LT and Terminal.
•
b8 of Application Indicator returned by LT equals 1.
Action: NA
Procedure: Application Selection using list of AIDs or PSE method.
Pass Criteria: The terminal shall terminate the transaction.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 265
2CB.041.00 Final Selection: cardholder does not approve
Test No: 2CB.041.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if only one AID is mutually supported, b8 of Application
priority indicator equals 1, and terminal provides for cardholder
confirmation but cardholder does not approve, the terminal terminates
the transaction.
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Terminal [Cardholder Confirmation] supported
Configuration:
Conditions:
•
There is one matching AID between LT and Terminal.
•
b8 of Application Indicator returned by LT equals 1.
Action: Cardholder does not approve the selection.
Procedure: Application Selection using list of AIDs or PSE method.
Pass Criteria: The terminal shall terminate the transaction.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 266
2CB.042.00 Displaying Application to Cardholder: priority sequence
Test No: 2CB.042.00 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that if multiple applications are mutually supported and list
display is supported, the terminal displays a list in priority sequence.
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] supported
Configuration:
Conditions:
•
There are three matching AIDs between LT and Terminal.
•
Applications have different priorities.
Action: Cardholder selects the 2nd Application in the displayed list
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC with the Application selected by the
Cardholder.
•
•
The terminal shall display a list of applications ordered in priority
sequence (highest priority first).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 267
2CB.042.01 Displaying Application to Cardholder when cardholder
confirmation is supported
Test No: 2CB.042.01 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that if multiple applications are mutually supported and
cardholder confirmation is supported, the terminal proposes all the
mutually supported applications to the cardholder.
Reference Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
EMV 4.3: Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] supported
Configuration:
Conditions:
•
There are three matching AIDs between LT and Terminal.
Action: Cardholder selects an Application in the list when displayed by the
terminal
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC with the Application selected by the
Cardholder.
•
The terminal shall display a complete list of mutually supported
applications (Three Applications).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 268
2CB.049.00 Terminal Selection of Application without Cardholder
Assistance
Test No: 2CB.049.00 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that if multiple applications are mutually supported, there is
priority sequence and no confirmation is required, the terminal selects
the application with highest priority.
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] not supported
Configuration:
Conditions:
•
There are three matching AIDs between LT and Terminal.
•
Applications have different priorities.
•
No confirmation is required in Application priority indicator.
Action: NA
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
The terminal shall select the application with highest priority and
shall generate the SELECT AID command (with AID=application
with highest priority).
•
No Cardholder Selection or Confirmation is requested by the
terminal
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 269
2CB.050.00 Terminal Selection of Application without Cardholder
Assistance: confirmation required
Test No: 2CB.050.00 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that if multiple applications are mutually supported, list display
is not supported, there is a priority sequence and confirmation is required
for some applications, the terminal selects the application with highest
priority excluding application requiring confirmation.
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] not supported
Configuration:
Conditions:
•
There are three matching AIDs between LT and Terminal.
•
Applications have different priorities.
•
Application with highest priority requires cardholder
confirmation.
Action: NA
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
The terminal shall select the application with highest priority
(excluding application requiring cardholder confirmation) and
shall generate the SELECT AID command (with AID =
application with highest priority excluding application requiring
confirmation).
•
No Cardholder Selection or Confirmation is requested by the
terminal
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 270
2CB.053.00 Final Selection of Application from Candidate List: list
of AID
Test No: 2CB.053.00 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that once an application is selected the terminal issues a
SELECT command using the DF Name read in FCI (if selection was
performed using list of AIDs).
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] not supported
Configuration:
Conditions:
•
There are three matching AIDs between LT and Terminal.
•
Applications have different priorities.
•
Terminal uses selection using list of AIDs process.
Action: NA
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
After having received a SELECT command for all AIDs in the
terminal list, the LT shall receive a SELECT command with
DFNAME of the application with the highest priority.
•
No Cardholder Selection or Confirmation is requested by the
terminal
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 271
2CB.053.01 Final Selection of Application from Candidate List: list
of AID (2)
Test No: 2CB.053.01 - Revision 4.3d - Number of sub cases: 0
Objective: To ensure that once an application is selected the terminal issues a
SELECT command using the DF Name read in FCI (if selection was
performed using list of AIDs).
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Book Bulletins - Section SB 151 - Bulletin n°151, Clarification on
Cardholder Selection & Confirmation (October 2014)
Terminal [Cardholder Confirmation] supported
Configuration:
Conditions:
•
There are three matching AIDs between LT and Terminal.
•
Applications have different priorities.
•
Terminal uses selection using list of AIDs process.
Action: Cardholder selects Application 1 in the list when displayed by the
terminal
Procedure: Application Selection using list of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
After having received a SELECT command for all AIDs in the
terminal list, the LT shall receive a SELECT command with
DFNAME of the application selected by the cardholder.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 272
2CB.054.00 Final Selection of Application from Candidate List: PSE
Test No: 2CB.054.00 - Revision 11 - Number of sub cases: 0
Objective: To ensure that if the Terminal supports and performs selection with PSE,
once the application to be run is determined, it issues a SELECT
command using the ADF Name read in directory.
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Terminal [PSE] supported
Configuration:
Conditions:
•
LT supports PSE.
•
There are three matching AIDs between LT and Terminal.
•
Applications have different priorities.
•
Terminal uses selection using PSE process.
Action: When supporting Cardholder confirmation, Operator must select the
application with the highest priority
Procedure: Application Selection using PSE is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
After having received READ RECORD for all records of the card
directory, the LT shall receive a SELECT command with
ADFName of the application with highest priority.
•
Terminal shall select the application.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 273
2CB.055.00 Final Selection of Application from Candidate List:
SELECT status different from 90 00
Test No: 2CB.055.00 - Revision 10g - Number of sub cases: 13
Objective: To ensure that if the card returns a status different from '90 00' to the
SELECT command of chosen application, the terminal removes the
application from the list of mutually supported applications and switches
back to the final application selection process.
Reference Book 1 - Section 12.4 - Final Selection
EMV 4.3:
Terminal NA
Configuration:
Conditions:
•
There are three matching AIDs between LT and Terminal.
•
Applications have different priorities.
•
LT returns status different from '90 00' after final selection.
•
Case 01: LT returns status value of '62 83' in response to
SELECT on final selection.
•
Case 02: LT returns status value of '63 00' in response to
SELECT on final selection.
•
Case 03: LT returns status value of '63 Cx' in response to
SELECT on final selection.
•
Case 04: LT returns status value of '69 83' in response to
SELECT on final selection.
•
Case 05: LT returns status value of '69 84' in response to
SELECT on final selection.
•
Case 06: LT returns status value of '69 85' in response to
SELECT on final selection.
•
Case 07: LT returns status value of '6A 81' in response to
SELECT on final selection.
•
Case 08: LT returns status value of '6A 82' in response to
SELECT on final selection.
•
Case 09: LT returns status value of '6A 83' in response to
SELECT on final selection.
•
Case 10: LT returns status value of '6A 88' in response to
SELECT on final selection.
•
Case 11: LT returns status value of '90 01' in response to
SELECT on final selection.
•
Case 12: LT returns status value of '64 00' in response to
SELECT on final selection.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 274
2CB.055.00 Final Selection of Application from Candidate List:
SELECT status different from 90 00
•
Case 13: LT returns status value of '65 00' in response to
SELECT on final selection.
Action: NA
Procedure: Application Selection using PSE or List of AIDs is performed.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
Terminal shall remove the application from the candidate list
and shall switch back to the final selection process after the
card responded to final SELECT with status different from '90
00'.
•
The candidate list generated during the second selection
process shall no longer contain the application used during the
above final SELECT.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 275
7.3 Security Aspects
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 276
2CC.003.00 Terminal shall be able to store 6 CA Index per RID
Test No: 2CC.003.00 - Revision 12 - Number of sub cases: 18
Objective: To ensure that if the terminal supports Static Data Authentication, it is
able to store 6 Certification Authority Public Keys and the key-related
information to be used with the key and it is able, given RID and
Certification Authority Public Key Index, to locate such key.
Reference Book 2 - Section 5 - Static Data Authentication (SDA)
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Terminal supports three RIDs (RID 1, RID 2 and RID 3).
•
Terminal is loaded with 6 Certification Authority Public Keys
(from Key index 00 to 05) per RID.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
Case 01: LT contains proper static signature and associated
data based on the Certification Authority Public Index 00 and
RID 1.
•
Case 02: LT contains proper static signature and associated
data based on the Certification Authority Public Index 01 and
RID 1.
•
Case 03: LT contains proper static signature and associated
data based on the Certification Authority Public Index 02 and
RID 1.
•
Case 04: LT contains proper static signature and associated
data based on the Certification Authority Public Index 03 and
RID 1.
•
Case 05: LT contains proper static signature and associated
data based on the Certification Authority Public Index 04 and
RID 1.
•
Case 06: LT contains proper static signature and associated
data based on the Certification Authority Public Index 05 and
RID 1.
•
Case 07: LT contains proper static signature and associated
data based on the Certification Authority Public Index 00 and
RID 2.
•
Case 08: LT contains proper static signature and associated
data based on the Certification Authority Public Index 01 and
RID 2.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 277
2CC.003.00 Terminal shall be able to store 6 CA Index per RID
•
Case 09: LT contains proper static signature and associated
data based on the Certification Authority Public Index 02 and
RID 2.
•
Case 10: LT contains proper static signature and associated
data based on the Certification Authority Public Index 03 and
RID 2.
•
Case 11: LT contains proper static signature and associated
data based on the Certification Authority Public Index 04 and
RID 2.
•
Case 12: LT contains proper static signature and associated
data based on the Certification Authority Public Index 05 and
RID 2.
•
Case 13: LT contains proper static signature and associated
data based on the Certification Authority Public Index 00 and
RID 3.
•
Case 14: LT contains proper static signature and associated
data based on the Certification Authority Public Index 01 and
RID 3.
•
Case 15: LT contains proper static signature and associated
data based on the Certification Authority Public Index 02 and
RID 3.
•
Case 16: LT contains proper static signature and associated
data based on the Certification Authority Public Index 03 and
RID 3.
•
Case 17: LT contains proper static signature and associated
data based on the Certification Authority Public Index 04 and
RID 3.
•
Case 18: LT contains proper static signature and associated
data based on the Certification Authority Public Index 05 and
RID 3.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 278
2CC.003.00 Terminal shall be able to store 6 CA Index per RID
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 279
2CC.004.00 Algorithm For SDA
Test No: 2CC.004.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal supports reversible algorithm for Static Data
Authentication as specified in Book 2, A2.1.
To ensure that the terminal supports Issuer Public Key Algorithm value
equal to '01' with Static Data Authentication.
To ensure that the terminal supports Hash Algorithm Indicator value
equal to '01' with Static Data Authentication.
Reference Book 2 - Section 5 - Static Data Authentication (SDA)
EMV 4.3:
Book 2 - Section B2.1 - RSA Algorithm
Book 2 - Section B3.1 - Secure Hash Algorithm (SHA-1)
Terminal [SDA] supported
Configuration:
Conditions:
•
Static signature in LT is good (it is calculated using the
reversible algorithm).
•
Issuer Public Key Certificate in LT is calculated with Issuer
Public Key Algorithm value equal to '01'.
•
Issuer Public Key Certificate in LT is calculated with Hash
Algorithm Indicator value equal to '01'.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 280
2CC.006.00 Bit Length of all Moduli
Test No: 2CC.006.00 - Revision 10g - Number of sub cases: 2
Objective: To ensure that the terminal supports Moduli with a bit length which is a
multiple of 8 for Static Data Authentication.
Reference Book 2 - Section 5.1 - Keys and Certificates
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Static signature in LT is valid.
•
length of moduli used are multiple of 8.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
Case 01: Test is made for the CA key.
•
Case 02: Test is made for the Issuer key.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 281
2CC.007.00 Value of Certification Authority Public Key Exponent
Test No: 2CC.007.00 - Revision 4.3d - Number of sub cases: 2
Objective: To ensure that the terminal supports values 3 and 2^16 + 1 as exponent
for Certification Authority Public Key for Static Data Authentication.
Reference Book 2 - Section 5.1 - Keys and Certificates
EMV 4.3:
Book Bulletins - Section SB 147 - Bulletin n°147, Clarification on the
Format of Exponent Data Elements (September 2014)
Terminal [SDA] supported
Configuration:
Conditions:
•
Static signature in LT is valid.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
Case 01: Exponent of Certification Authority Public Key is 3,
Certification Authority Exponent Length is coded on 1 byte.
•
Case 02: Exponent of Certification Authority Public Key is 2^16
+ 1, Certification Authority Exponent Length is coded on 3
bytes.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 282
2CC.008.00 Value of Issuer Public Key Exponent
Test No: 2CC.008.00 - Revision 4.3d - Number of sub cases: 3
Objective: To ensure that the terminal supports values 3 and 2^16 + 1 as exponent
for Issuer Public Key used in Static Data Authentication.
Reference Book 2 - Section 5.1 - Keys and Certificates
EMV 4.3:
Book Bulletins - Section SB 147 - Bulletin n°147, Clarification on the
Format of Exponent Data Elements (September 2014)
Terminal [SDA] supported
Configuration:
Conditions:
•
Static signature in LT is valid.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
Case 01: Exponent of Issuer Public Key is 3, Issuer Public
Exponent Length is coded on 1 byte.
•
Case 02: Exponent of Issuer Public Key is 2^16 + 1, Issuer
Public Exponent Length is coded on 3 byte.
•
Case 03: Exponent of Issuer Public Key is 3; Issuer Public
Exponent Length is coded on 3 bytes (the full 3-bytes 000003
are included in the hash of the certificate).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 283
2CC.009.00 Data missing: CA Public Key Index
Test No: 2CC.009.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the Certification Authority Public Key index is missing
in ICC, the terminal fails the Static Data Authentication.
To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b if
Offline Static Data Authentication is supported in AIP and Certification
Authority Public Key Index is missing in the card.
Reference Book 2 - Section 5.2 - Retrieval of Certification Authority Public Key
EMV 4.3:
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Terminal [SDA] supported
Configuration:
Conditions:
•
Index of Certification Authority Public Key is missing in ICC.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 284
2CC.010.00 Data missing: Issuer PK Certificate
Test No: 2CC.010.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the Issuer Public key Certificate is missing in ICC, the
terminal fails Static Data Authentication.
Reference Book 2 - Section 5.1 - Keys and Certificates
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Issuer Public Key Certificate is missing in LT.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 285
2CC.011.00 Data missing: Issuer PK Exponent
Test No: 2CC.011.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the Issuer Public key Exponent is missing in ICC, the
terminal fails Static Data Authentication.
Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Issuer Public key Exponent is missing in LT.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 286
2CC.012.00 Data missing: Signed Static Application data
Test No: 2CC.012.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the Signed Static Application Data is missing in ICC,
the terminal fails Static Data Authentication.
To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b,
if Offline Static Data Authentication is supported in AIP and Signed Static
Application Data is missing in the card.
Reference Book 2 - Section 5.1 - Keys and Certificates
EMV 4.3:
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Terminal [SDA] supported
Configuration:
Conditions:
•
Signed Static Application Data is missing in LT.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 287
2CC.014.00 Retrieving CA Public Key used to Perform SDA: Key
absent
Test No: 2CC.014.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports Static Data Authentication, if no
Certification Authority Public Keys is available for a given RID and
Certification Authority Public Key Index, the terminal fails Static Data
Authentication.
Reference Book 2 - Section 5.2 - Retrieval of Certification Authority Public Key
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Terminal does not contain the Certification Authority Public Key
referenced in LT.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 288
2CC.014.01 Retrieving CA Public Key used to Perform DDA: Key
absent
Test No: 2CC.014.01 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports Dynamic Data Authentication, and
if no Certification Authority Public Keys is available for a given RID and
Certification Authority Public Key Index, the terminal fails the Dynamic
Data Authentication process.
Reference Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
Terminal does not contain the Certification Authority Public Key
referenced in LT.
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 289
2CC.014.02 Retrieving CA Public Key used to Perform Combined
DDA/AC: Key absent
Test No: 2CC.014.02 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that if the terminal supports Combined DDA/AC Data
Authentication, and if no Certification Authority Public Keys is available
for a given RID and Certification Authority Public Key Index, the terminal
fails the Combined DDA/AC Data Authentication process.
Reference Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
Terminal does not contain the Certification Authority Public Key
referenced in LT.
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that TC is requested at first Gen AC.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 290
2CC.014.03 Retrieving CA Public Key used to Perform PIN
Encryption: Key absent
Test No: 2CC.014.03 - Revision 43e - Number of sub cases: 0
Objective: To ensure that if the terminal supports Offline PIN Encryption, and if no
Certification Authority Public Keys is available for a given RID and
Certification Authority Public Key Index, the terminal fails the PIN
Encryption process.
Reference Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
Terminal does not contain the Certification Authority Public Key
referenced in LT.
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification was not
successful) received at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 291
2CC.014.08 Retrieving CA Public Key used to Perform Combined
DDA/AC: Key absent (9)
Test No: 2CC.014.08 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that if the terminal supports Combined DDA/AC Data
Authentication, and if no Certification Authority Public Keys is available
for a given RID and Certification Authority Public Key Index, the terminal
fails the Combined DDA/AC Data Authentication process.
Reference Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
Terminal does not contain the Certification Authority Public Key
referenced in LT.
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online approved.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 292
2CC.014.09 Retrieving CA Public Key used to Perform Combined
DDA/AC: Key absent (10)
Test No: 2CC.014.09 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that if the terminal supports Combined DDA/AC Data
Authentication, and if no Certification Authority Public Keys is available
for a given RID and Certification Authority Public Key Index, the terminal
fails the Combined DDA/AC Data Authentication process.
Reference Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
Terminal does not contain the Certification Authority Public Key
referenced in LT.
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online declined.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting an AAC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 293
2CC.015.00 Length of Issuer Public Key Certificate
Test No: 2CC.015.00 - Revision 11 - Number of sub cases: 2
Objective: To ensure that if the terminal supports Static Data Authentication, and if
Issuer Public Key Certificate has a length different from Certification
Authority Public Key Modulus, the terminal fails the Static Data
Authentication process.
Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
Case 01: Issuer Public Key Certificate in LT is greater than
Certification Authority Public Key Modulus.
•
Case 02: Issuer Public Key Certificate in LT is less than
Certification Authority Public Key Modulus.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 294
2CC.017.00 Recovered Data Trailer not equal to 'BC'
Test No: 2CC.017.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Static Data Authentication process
if the Data Trailer recovered from the Issuer Public Key Certificate does
not equal 'BC'.
Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Issuer Public Key Certificate in LT is calculated with a Data
Trailer different from 'BC'.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 295
2CC.018.00 Recovered Data Header not equal to '6A'
Test No: 2CC.018.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Static Data Authentication process
if the Data Header recovered from the Issuer Public Key Certificate does
not equal '6A'.
Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Issuer Public Key Certificate in LT is calculated with a Data
Header different from '6A'.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 296
2CC.019.00 Certificate Format not equal to '02'
Test No: 2CC.019.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Static Data Authentication process
if the Certificate Format recovered from Issuer Public Key Certificate
does not equal '02'.
Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Issuer Public Key Certificate in LT is calculated with a
Certificate Format different from '02'.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 297
2CC.020.00 Difference between calculated Hash Result and
recovered Hash Result
Test No: 2CC.020.00 - Revision 10g - Number of sub cases: 2
Objective: To ensure that the terminal fails the Static Data Authentication process
if the calculated Hash Result is different from the Hash Result recovered
from the Issuer Public Key Certificate.
Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Issuer Public Key Certificate in LT is calculated with a bad Hash
value.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
Case 01: Error is on the first byte of the Hash.
•
Case 02: Error is on the last byte of the Hash.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 298
2CC.021.00 Issuer Identifier does not match leftmost 3-8 PAN digits
Test No: 2CC.021.00 - Revision 10g - Number of sub cases: 3
Objective: To ensure that the terminal fails the Static Data Authentication process
if the Recovered Issuer Identifier does not match the leftmost 3-8 PAN
digits.
Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
Case 01: Issuer Public Key Certificate in LT is calculated with
Issuer Identifier different from leftmost 3-8 PAN digits: difference
is on digit 3.
•
Case 02: Issuer Public Key Certificate in LT is calculated with
Issuer Identifier different from leftmost 3-8 PAN digits: difference
is on digit 8.
•
Case 03: Issuer Public Key Certificate in LT is calculated with
Issuer Identifier different from leftmost 3-8 PAN digits: difference
is on all 3-8 digits.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 299
2CC.022.00 Certificate Expiration Date earlier than today's date
Test No: 2CC.022.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Static Data Authentication process
if the Certificate Expiration Date has expired.
Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Issuer Public Key Certificate in LT is calculated with Certificate
Expiration Date earlier than the current date.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 300
2CC.023.00 RID, CA Public Key Index and Certificate Serial Number
not valid, SDA
Test No: 2CC.023.00 - Revision 13 - Number of sub cases: 3
Objective: To ensure that the terminal fails the Static Data Authentication process
if the concatenation of RID, CA Public Key Index and Certificate Serial
Number indicates a revoked Certificate.
Reference Book 2 - Section 5.1.2 - Certification Revocation List
EMV 4.3:
Book 2 - Section 5.3 - Retrieval of Issuer Public Key
Terminal ([SDA] supported AND [Key Revocation] supported)
Configuration:
Conditions:
•
Terminal supports three RIDs
•
Terminal is loaded with 30 CRL entries (formatted according to
ICS defined format) per RID. 29 of these entries per RID are
based on Certificate Serial Numbers which are not signed (i.e.
dummy test data)
•
Issuer Public Key Certificate in LT is calculated with RID, CA
Public Key Index and Certificate Serial Number such that the
certificate correspond to the signed CRL entry in the revocation
list of the terminal.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
Case 01 - The terminal is loaded with the 30 CRL entries,
specified above, for RID 1.
•
Case 02 - The terminal is loaded with the 30 CRL entries,
specified above, for RID 2.
•
Case 03 - The terminal is loaded with the 30 CRL entries,
specified above, for RID 3.
Action: NA
Procedure: Application in LT is selected, for each RID as specified in each case, and
transaction is processed
Authentication).
Pass Criteria:
with
LT
(in
particular
Static
Data
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 301
2CC.023.00 RID, CA Public Key Index and Certificate Serial Number
not valid, SDA
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 302
2CC.023.01 Certification Revocation List update, removal
Test No: 2CC.023.01 - Revision 13 - Number of sub cases: 0
Objective: To ensure that the terminal is be able to update the Certification
Revocation List by deleting an entry.
Reference Book 2 - Section 5.1.2 - Certification Revocation List
EMV 4.3:
Terminal ([SDA] supported AND [Key Revocation] supported)
Configuration:
Terminal has been loaded with 30 CRL entries as described in
2CC.023.00
Conditions:
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
AIP of LT indicates that other data authentication methods are
not supported (AIP byte 1 bit 6 = ‘0’, byte 1 bit 5 = ‘0’, and byte
1 bit 1 = ‘0’)
•
The CRL update process is completed before undertaking an
EMV transaction.
•
A valid CRL entry is removed from the device, where the LT
Issuer Public Key Certificate is calculated with RID, CA Public
Key Index and Certificate Serial Number corresponding to this
valid entry.
Action: NA
Procedure: A default acquirer process as documented by the device vendor is
performed to update the CRL.
Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication
succesful) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 303
2CC.023.02 Certification Revocation List update, addition
Test No: 2CC.023.02 - Revision 13 - Number of sub cases: 0
Objective: To ensure that the terminal is able to update the Certification Revocation
List by adding an entry.
Reference Book 2 - Section 5.1.2 - Certification Revocation List
EMV 4.3:
Terminal ([SDA] supported AND [Key Revocation] supported)
Configuration:
Terminal is loaded with 29 CRL entries and 2CC.023.01 has been
performed before this test
Conditions:
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
AIP of LT indicates that other data authentication methods are
not supported (AIP byte 1 bit 6 = ‘0’, byte 1 bit 5 = ‘0’, and byte
1 bit 1 = ‘0’)
•
The CRL update process is completed before undertaking an
EMV transaction.
•
A valid CRL entry is loaded to the device, where the LT Issuer
Public Key Certificate is calculated with RID, CA Public Key
and Certificate Serial Number corresponding to this valid entry.
Action: NA
Procedure: A default acquirer process as documented by the device vendor is
performed to update the CRL.
Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Please note: 2CC.023.01 - Certification Revocation List update, removal
must be performed before this test
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 304
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 305
2CC.024.00 Issuer Public Key Algorithm not recognized
Test No: 2CC.024.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Static Data Authentication process
if the Issuer Public Key Algorithm is not supported (different from '01').
Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Issuer Public Key Certificate in LT is calculated with Issuer
Public Key Algorithm value different from '01'.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 306
2CC.026.00 Signed Static Application Data Length not OK
Test No: 2CC.026.00 - Revision 11 - Number of sub cases: 2
Objective: To ensure that if the terminal supports Static Data Authentication, and if
Signed Static Application Data has a length different from Issuer Public
Key Modulus, the terminal fails the Static Data Authentication process.
Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
Case 01: Signed Static Application Data is greater than Issuer
Public Key Modulus in LT.
•
Case 02: Signed Static Application Data is less than Issuer
Public Key Modulus in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 307
2CC.028.00 Recovered Data Trailer not equal to 'BC'
Test No: 2CC.028.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Static Data Authentication process
if the Data Trailer recovered from Signed Static Application Data does
not equal 'BC'.
Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Signed Static Application Data in LT is calculated with a Data
Trailer different from 'BC'.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 308
2CC.029.00 Recovered Data Header not equal to '6A'
Test No: 2CC.029.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Static Data Authentication process
if the Data Header recovered from the Signed Static Application Data
does not equal '6A'.
Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Signed Static Application Data in LT is calculated with a Data
Header different from '6A'.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 309
2CC.030.00 Certificate Format not equal to '03'
Test No: 2CC.030.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Static Data Authentication process
if the Certificate Format recovered from Signed Static Application Data
does not equal '03'.
Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Signed Static Application Data in LT is calculated with a
Certificate Format different from '03'.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 310
2CC.031.00 Difference between calculated Hash Result and
recovered Hash Result
Test No: 2CC.031.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Static Data Authentication process
if the calculated Hash Result is different from the Hash Result recovered
from Signed Static Application Data.
Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
Signed Static Application Data in LT is calculated with a bad
Hash value.
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline Static Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 311
2CC.032.00 SDA Tag List in Static Data Authentication
Test No: 2CC.032.00 - Revision 10g - Number of sub cases: 2
Objective: To ensure that the terminal checks that SDA Tag List contains only AIP
in SDA.
Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
Case 01: SDA Tag List contains AFL
•
Case 02: SDA Tag List contains AFL and AIP
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '1' (ie Offline SDA failed) received at 1st
GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 312
2CC.032.01 SDA Tag List in Static Data Authentication (2)
Test No: 2CC.032.01 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal checks that SDA Tag List contains only AIP
in SDA.
Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
SDA Tag List contains tag '82' (AIP).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '0' (ie Offline SDA succeeded) received at
1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 313
2CC.033.00 Data Authentication Code Stored
Test No: 2CC.033.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal stores the Data Authentication Code in tag
'9F 45' when using Static Data Authentication.
Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
CDOL1 requests Tag '9F 45'.
•
Data Authentication Code is 'DA C0'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Static Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '0' (ie Offline SDA succeeded) received at
1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
•
Value of Tag '9F 45' is 'DA C0' received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 314
2CC.036.00 Terminal shall be able to store 6 CA Index per RID
Test No: 2CC.036.00 - Revision 11 - Number of sub cases: 6
Objective: To ensure that if the terminal supports Dynamic Data Authentication, it
is able to store 6 Certification Authority Public Keys as well as key-related
information to be used with the key and it is able, given RID and
Certification Authority Public Key Index, to locate such key.
Reference Book 2 - Section 6 - Offline Dynamic Data Authentication
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
Terminal supports two RIDs (RIDs 1 and RIDs 2).
•
Terminal is loaded with 6 Certification Authority Public Keys
(from Key index 00 to 05) per RID.
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Case 01: LT generates proper good dynamic signature and
associated data based on the Certification Authority Public
Index 01 and RID 1.
•
Case 02: LT generates proper good dynamic signature and
associated data based on the Certification Authority Public
Index 03 and RID 1.
•
Case 03: LT generates proper good dynamic signature and
associated data based on the Certification Authority Public
Index 04 and RID 1.
•
Case 04: LT generates proper good dynamic signature and
associated data based on the Certification Authority Public
Index 01 and RID 2.
•
Case 05: LT generates proper good dynamic signature and
associated data based on the Certification Authority Public
Index 03 and RID 2.
•
Case 06: LT generates proper good dynamic signature and
associated data based on the Certification Authority Public
Index 04 and RID 2.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 315
2CC.036.00 Terminal shall be able to store 6 CA Index per RID
•
TVR byte 1, bit 4= '0' (ie Offline Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 316
2CC.036.01 Terminal shall be able to store 6 CA Index per RID (2)
Test No: 2CC.036.01 - Revision 4.2b - Number of sub cases: 6
Objective: To ensure that if the terminal supports Combined DDA/AC Data
Authentication, it is able to store 6 Certification Authority Public Keys as
well as the key-related information to be used with the key and it is able,
given RID and Certification Authority Public Key Index, to locate such
key.
Reference Book 2 - Section 6 - Offline Dynamic Data Authentication
EMV 4.3:
Terminal [CDA] supported
Configuration:
Conditions:
•
Terminal supports two RIDs (RIDs 1 and RIDs 2).
•
Terminal is loaded with the same 6 Certification Authority Public
Keys (from Key index 00 to 05) per RID as in test 2CC.036.00.
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Case 01: LT generates proper good dynamic signature and
associated data based on the Certification Authority Public
Index 00 and RID 1.
•
Case 02: LT generates proper good dynamic signature and
associated data based on the Certification Authority Public
Index 02 and RID 1.
•
Case 03: LT generates proper good dynamic signature and
associated data based on the Certification Authority Public
Index 05 and RID 1.
•
Case 04: LT generates proper good dynamic signature and
associated data based on the Certification Authority Public
Index 00 and RID 2.
•
Case 05: LT generates proper good dynamic signature and
associated data based on the Certification Authority Public
Index 02 and RID 2.
•
Case 06: LT generates proper good dynamic signature and
associated data based on the Certification Authority Public
Index 05 and RID 2.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 317
2CC.036.01 Terminal shall be able to store 6 CA Index per RID (2)
•
TVR byte 1, bit 3 = '0' (ie Offline Combined DDA/AC Data
Authentication succeeded) contained in Financial Confirmation
message or Batch Data Capture message.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message (this pass criteria apply only if
CDA is requested).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 318
2CC.036.02 Terminal shall be able to store 6 CA Index per RID (3)
Test No: 2CC.036.02 - Revision 11 - Number of sub cases: 12
Objective: To ensure that if the terminal supports Enciphered offline PIN
verification, it is able to store 6 Certification Authority Public Keys as well
as the key-related information to be used with the key and it is able, given
RID and Certification Authority Public Key Index, to locate such key.
Reference Book 2 - Section 6 - Offline Dynamic Data Authentication
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
Terminal supports two RIDs (RIDs 1 and RIDs 2).
•
Terminal is loaded with 6 Certification Authority Public Keys
(from Key index 00 to 05) per RID.
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT supports Offline PIN Verification.
•
CVM is 'Enciphered offline PIN verification, always' (04 00).
•
Case 01: LT contains associated data based on the Certification
Authority Public Index 00 and RID 1.
•
Case 02: LT contains associated data based on the Certification
Authority Public Index 01 and RID 1.
•
Case 03: LT contains associated data based on the Certification
Authority Public Index 02 and RID 1.
•
Case 04: LT contains associated data based on the Certification
Authority Public Index 03 and RID 1.
•
Case 05: LT contains associated data based on the Certification
Authority Public Index 04 and RID 1.
•
Case 06: LT contains associated data based on the Certification
Authority Public Index 05 and RID 1.
•
Case 07: LT contains associated data based on the Certification
Authority Public Index 00 and RID 2.
•
Case 08: LT contains associated data based on the Certification
Authority Public Index 01 and RID 2.
•
Case 09: LT contains associated data based on the Certification
Authority Public Index 02 and RID 2.
•
Case 10: LT contains associated data based on the Certification
Authority Public Index 03 and RID 2.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 319
2CC.036.02 Terminal shall be able to store 6 CA Index per RID (3)
•
Case 11: LT contains associated data based on the Certification
Authority Public Index 04 and RID 2.
•
Case 12: LT contains associated data based on the Certification
Authority Public Index 05 and RID 2.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '0' (ie Cardholder verification was
successful) received at 1st GENERATE AC.
•
TSI byte 1, bit 7 ='1' (ie Cardholder Verification was performed)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 320
2CC.037.00 Algorithm for DDA
Test No: 2CC.037.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal supports reversible algorithm for Dynamic
Data Authentication as specified in Book 2, A2.1.
To ensure that the terminal supports Issuer Public Key Algorithm value
equal to '01' for Dynamic Data Authentication.
To ensure that the terminal supports ICC Public Key Algorithm value
equal to '01' for Dynamic Data Authentication.
To ensure that the terminal supports Hash Algorithm Indicator value
equal to '01' with Dynamic Data Authentication.
Reference Book 2 - Section A2.1 - Digital Signature Scheme Giving Message
EMV 4.3: Recovery
Book 2 - Section B2.1 - RSA Algorithm
Book 2 - Section B3.1 - Secure Hash Algorithm (SHA-1)
Terminal [DDA] supported
Configuration:
Conditions:
•
Dynamic signature computed by LT is valid (it is calculated
using the reversible algorithm).
•
Issuer Public Key Certificate in LT is calculated with Issuer
Public Key Algorithm value equal to '01'.
•
ICC Public Key Certificate in LT is calculated with ICC Public
Key Algorithm value equal to '01'.
•
Issuer Public Key Certificate in LT is calculated with Hash
Algorithm Indicator value equal to '01'.
•
ICC Public Key Certificate in LT is calculated with Hash
Algorithm Indicator value equal to '01'.
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 321
2CC.037.00 Algorithm for DDA
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 322
2CC.037.01 Algorithm for DDA (2)
Test No: 2CC.037.01 - Revision 4.2b - Number of sub cases: 0
Objective: To ensure that the terminal supports reversible algorithm for Combined
DDA/AC Data Authentication as specified in Book 2, A2.1.
To ensure that the terminal supports Issuer Public Key Algorithm value
equal to '01' in Combined DDA/AC Data Authentication.
To ensure that the terminal supports ICC Public Key Algorithm value
equal to '01' in Combined DDA/AC Data Authentication.
To ensure that the terminal supports Hash Algorithm Indicator value
equal to '01' with Combined DDA/AC Data Authentication.
Reference Book 2 - Section A2.1 - Digital Signature Scheme Giving Message
EMV 4.3: Recovery
Book 2 - Section B2.1 - RSA Algorithm
Book 2 - Section B3.1 - Secure Hash Algorithm (SHA-1)
Terminal [CDA] supported
Configuration:
Conditions:
•
Dynamic signature computed by LT is valid (it is calculated
using the reversible algorithm).
•
Issuer Public Key Certificate in LT is calculated with Issuer
Public Key Algorithm value equal to '01'.
•
ICC Public Key Certificate in LT is calculated with ICC Public
Key Algorithm value equal to '01'.
•
Issuer Public Key Certificate in LT is calculated with Hash
Algorithm Indicator value equal to '01'.
•
ICC Public Key Certificate in LT is calculated with Hash
Algorithm Indicator value equal to '01'.
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 3 = '0' 'ie Offline Combined DDA/AC Data
Authentication succeeded) contained in Financial Confirmation
message or Batch Data Capture message.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 323
2CC.037.01 Algorithm for DDA (2)
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' 'ie Dynamic Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message (this pass criteria apply only if
CDA is requested).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 324
2CC.039.00 Bit Length of All Moduli
Test No: 2CC.039.00 - Revision 11 - Number of sub cases: 0
Objective: To ensure that the terminal supports Moduli with a bit length which is a
multiple of 8 for Dynamic Data Authentication.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
Dynamic signature computed by LT is valid.
•
length of moduli used are multiples of 8 for the CA key, Issuer
key and ICC key.
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 325
2CC.039.01 Bit Length of All Moduli (2)
Test No: 2CC.039.01 - Revision 4.2b - Number of sub cases: 0
Objective: To ensure that the terminal supports Moduli with a bit length which is a
multiple of 8 for Combined Dynamic Data Authentication
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Terminal [CDA] supported
Configuration:
Conditions:
•
Dynamic signature computed by LT is valid.
•
length of moduli used are multiples of 8 for the CA key, Issuer
key and ICC key.
•
AIP of LT indicates Combined DDA/AC Data Authentication is
supported (AIP byte 1 bit 1 = ‘1’).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Combined Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 3 = '0' (ie Offline Combined DDA/AC Data
Authentication succeeded) contained in Financial Confirmation
message or Batch Data Capture message.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message (this pass criteria apply only if
CDA is requested).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 326
2CC.039.02 Bit Length of All Moduli (3)
Test No: 2CC.039.02 - Revision 10g - Number of sub cases: 2
Objective: To ensure that the terminal supports Moduli with a bit length which is a
multiple of 8 for Offline Enciphered PIN verification.
Reference Book 2 - Section 7.1 - Keys and Certificates
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM is 'Enciphered offline PIN verification, always' (04 00).
•
length of moduli used are multiples of 8 for the CA key and
Issuer key.
•
Case 01: Test is made for the ICC Public key.
•
Case 02: Test is made for the Issuer key.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '0' (ie Cardholder verification succeeded)
received at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 327
2CC.040.00 Value of CA Public Key Exponent
Test No: 2CC.040.00 - Revision 4.3d - Number of sub cases: 2
Objective: To ensure that the terminal supports value 3 and 2^16 + 1 as exponent
for Certification
Authentication.
Authority
Public
Key
used
in
Dynamic
Data
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book Bulletins - Section SB 147 - Bulletin n°147, Clarification on the
Format of Exponent Data Elements (September 2014)
Terminal [DDA] supported
Configuration:
Conditions:
•
Dynamic signature computed by LT is valid.
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Case 01: Exponent of Certification Authority Public Key is 3,
Certification Authority Exponent Length is coded on 1 byte.
•
Case 02: Exponent of Certification Authority Public Key is 2^16
+ 1, Certification Authority Exponent Length is coded on 3
bytes.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 328
2CC.040.01 Value of CA Public Key Exponent (2)
Test No: 2CC.040.01 - Revision 4.3d - Number of sub cases: 2
Objective: To ensure that the terminal supports value 3 and 2^16 + 1 as exponent
for Certification Authority Public Key used in Combined DDA/AC Data
Authentication.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book Bulletins - Section SB 147 - Bulletin n°147, Clarification on the
Format of Exponent Data Elements (September 2014)
Terminal [CDA] supported
Configuration:
Conditions:
•
Dynamic signature computed by LT is valid.
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Case 01: Exponent of Certification Authority Public Key is 3,
Certification Authority Exponent Length is coded on 1 byte.
•
Case 02: Exponent of Certification Authority Public Key is 2^16
+ 1, Certification Authority Exponent Length is coded on 3
bytes.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 3 = '0' (ie Offline Combined DDA/AC Data
Authentication succeeded) contained in Financial Confirmation
message or Batch Data Capture message.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message (this pass criteria apply only if
CDA is requested).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 329
2CC.040.02 Value of CA Public Key Exponent (3)
Test No: 2CC.040.02 - Revision 4.3d - Number of sub cases: 2
Objective: To ensure that the terminal supports value 3 and 2^16 + 1 as exponent
for Certification Authority Public Key used in Offline PIN Encryption.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book Bulletins - Section SB 147 - Bulletin n°147, Clarification on the
Format of Exponent Data Elements (September 2014)
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
LT supports Offline PIN encryption.
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Case 01: Exponent of Certification Authority Public Key is 3,
Certification Authority Exponent Length is coded on 1 byte.
•
Case 02: Exponent of Certification Authority Public Key is 2^16
+ 1, Certification Authority Exponent Length is coded on 3
bytes.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '0' (ie Cardholder verification succeeded)
received at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 330
2CC.041.00 Value of Issuer Public Key Exponent
Test No: 2CC.041.00 - Revision 4.3d - Number of sub cases: 3
Objective: To ensure that the terminal supports value 3 and 2^16 + 1 as exponent
for Issuer Public Key used in Dynamic Data Authentication.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book Bulletins - Section SB 147 - Bulletin n°147, Clarification on the
Format of Exponent Data Elements (September 2014)
Terminal [DDA] supported
Configuration:
Conditions:
•
Dynamic signature computed by LT is valid.
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Case 01: Exponent of Issuer Public Key is 3, Issuer Public
Exponent Length is coded on 1 byte.
•
Case 02: Exponent of Issuer Public Key is 2^16 + 1, Issuer
Public Exponent Length is coded on 3 bytes.
•
Case 03: Exponent of Issuer Public Key is 3, Issuer Public
Exponent Length is coded on 3 bytes (the full 3-bytes 000003
are included in the hash of the certificate).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 331
2CC.041.01 Value of Issuer Public Key Exponent (2)
Test No: 2CC.041.01 - Revision 4.3d - Number of sub cases: 3
Objective: To ensure that the terminal supports value 3 and 2^16 + 1 as exponent
for Issuer Public Key used in Combined DDA/AC Data Authentication.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book Bulletins - Section SB 147 - Bulletin n°147, Clarification on the
Format of Exponent Data Elements (September 2014)
Terminal [CDA] supported
Configuration:
Conditions:
•
Dynamic signature computed by LT is valid.
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Case 01: Exponent of Issuer Public Key is 3, Issuer Public
Exponent Length is coded on 1 byte.
•
Case 02: Exponent of Issuer Public Key is 2^16 + 1, Issuer
Public Exponent Length is coded on 3 bytes.
•
Case 03: Exponent of Issuer Public Key is 3, Issuer Public
Exponent Length is coded on 3 bytes (the full 3-bytes 000003
are included in the hash of the certificate).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 3 = '0' (ie Offline Combined DDA/AC Data
Authentication succeeded) contained in Financial Confirmation
message or Batch Data Capture message.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message (this pass criteria apply only if
CDA is requested).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 332
2CC.041.02 Value of Issuer Public Key Exponent (3)
Test No: 2CC.041.02 - Revision 4.3d - Number of sub cases: 3
Objective: To ensure that the terminal supports value 3 and 2^16 + 1 as exponent
for Issuer Public Key used in Offline PIN Encryption.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Book Bulletins - Section SB 147 - Bulletin n°147, Clarification on the
Format of Exponent Data Elements (September 2014)
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
LT supports Offline PIN encryption.
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Case 01: Exponent of Issuer Public Key is 3, Issuer Public
Exponent Length is coded on 1 byte.
•
Case 02: Exponent of Issuer Public Key is 2^16 + 1, Issuer
Public Exponent Length is coded on 3 bytes.
•
Case 03: Exponent of Issuer Public Key is 3, Issuer Public
Exponent Length is coded on 3 bytes (the full 3-bytes 000003
are included in the hash of the certificate).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '0' (ie Cardholder verification succeeded)
received at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 333
2CC.042.00 Value of ICC Public Key Exponent
Test No: 2CC.042.00 - Revision 4.3d - Number of sub cases: 3
Objective: To ensure that the terminal supports value 3 and 2^16 + 1 as exponent
for ICC Public Key used in Dynamic Data Authentication.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book Bulletins - Section SB 147 - Bulletin n°147, Clarification on the
Format of Exponent Data Elements (September 2014)
Terminal [DDA] supported
Configuration:
Conditions:
•
Dynamic signature computed by LT is valid.
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Case 01: Exponent of ICC Public Key is 3, ICC Public Exponent
Length is coded on 1 byte.
•
Case 02: Exponent of ICC Public Key is 2^16 + 1, ICC Public
Exponent Length is coded on 3 bytes.
•
Case 03: Exponent of ICC Public Key is 3, ICC Public Exponent
Length is coded on 3 bytes (the full 3-bytes 000003 are included
in the hash of the certificate).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 334
2CC.042.01 Value of ICC Public Key Exponent (2)
Test No: 2CC.042.01 - Revision 4.3d - Number of sub cases: 3
Objective: To ensure that the terminal supports value 3 and 2^16 + 1 as exponent
for ICC Public Key used in Combined DDA/AC Data Authentication.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book Bulletins - Section SB 147 - Bulletin n°147, Clarification on the
Format of Exponent Data Elements (September 2014)
Terminal [CDA] supported
Configuration:
Conditions:
•
Dynamic signature computed by LT is valid.
•
AIP of LT indicates Combined DDA/AC Data Authentication is
supported (AIP byte 1 bit 1 = ‘1’).
•
Case 01: Exponent of ICC Public Key is 3, ICC Public Exponent
Length is coded on 1 byte.
•
Case 02: Exponent of ICC Public Key is 2^16 + 1, ICC Public
Exponent Length is coded on 3 bytes.
•
Case 03: Exponent of ICC Public Key is 3, ICC Public Exponent
Length is coded on 3 bytes (the full 3-bytes 000003 are included
in the hash of the certificate).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 3 = '0' (ie Offline Combined DDA/AC Data
Authentication succeeded) contained in Financial Confirmation
message or Batch Data Capture message.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message (this pass criteria apply only if
CDA is requested).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 335
2CC.043.00 Data missing: CA Public Key Index
Test No: 2CC.043.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the Certification Authority Public Key index is missing
in ICC, the terminal fails the Dynamic Data Authentication process.
To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b if
Offline Dynamic Data Authentication is supported in AIP and Certification
Authority Public Key Index is missing in the card.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Index of Certification Authority Public Key is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 336
2CC.043.01 Data missing: CA Public Key Index (2)
Test No: 2CC.043.01 – Revision 4.3c - Number of sub cases: 0
Objective: To ensure that if the Certification Authority Public Key index is missing
in ICC, the terminal fails the Combined DDA/AC Data Authentication
process.
To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b if
Offline Combined DDA/AC Data Authentication is supported in AIP and
Certification Authority Public Key Index is missing in the card.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 2 - Section 6.6 - Combined DDA/Application Cryptogram
Generation (CDA)
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Book 4 - Section 6.3.2 - Offline Data Authentication
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Index of Certification Authority Public Key is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 337
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 338
2CC.044.00 Data missing: Issuer Public Key Certificate
Test No: 2CC.044.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the Issuer Public key Certificate is missing in ICC, the
terminal fails the Dynamic Data Authentication process.
To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b if
Offline Dynamic Data Authentication is supported in AIP and Issuer
Public Key Certificate is missing in the card.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Issuer Public Key Certificate is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 339
2CC.044.01 Data missing: Issuer Public Key Certificate (2)
Test No: 2CC.044.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that if the Issuer Public key Certificate is missing in ICC, the
terminal fails the Combined DDA/AC Data Authentication process.
To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b if
Offline Combined DDA/AC Data Authentication is supported in AIP and
Issuer Public Key Certificate is missing in the card.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that TC is requested at first Gen AC.
•
Issuer Public Key Certificate is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 340
2CC.044.06 Data missing: Issuer Public Key Certificate (7)
Test No: 2CC.044.06 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that if the Issuer Public key Certificate is missing in ICC, the
terminal fails the Combined DDA/AC Data Authentication process.
To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b if
Offline Combined DDA/AC Data Authentication is supported in AIP and
Issuer Public Key Certificate is missing in the card.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online approved.
•
Issuer Public Key Certificate is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 341
2CC.044.06 Data missing: Issuer Public Key Certificate (7)
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 342
2CC.044.07 Data missing: Issuer Public Key Certificate (8)
Test No: 2CC.044.07 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that if the Issuer Public key Certificate is missing in ICC, the
terminal fails the Combined DDA/AC Data Authentication process.
To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b if
Offline Combined DDA/AC Data Authentication is supported in AIP and
Issuer Public Key Certificate is missing in the card.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online declined.
•
Issuer Public Key Certificate is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting an AAC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 343
2CC.044.07 Data missing: Issuer Public Key Certificate (8)
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 344
2CC.045.00 Data missing: Issuer PK Exponent
Test No: 2CC.045.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the Issuer Public key Exponent is missing in ICC, the
terminal fails the Dynamic Data Authentication process.
To ensure that terminal sets 'ICC data missing' bit in the TVR to 1b if
Offline Dynamic Data Authentication is supported in AIP and Issuer
Public Key Exponent is missing in the card.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Issuer Public key Exponent is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 345
2CC.045.01 Data missing: Issuer PK Exponent (2)
Test No: 2CC.045.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that if the Issuer Public key Exponent is missing in ICC, the
terminal fails the Combined DDA/AC Data Authentication process.
To ensure that terminal sets 'ICC data missing' bit in the TVR to 1b if
Offline Combined DDA/AC Data Authentication is supported in AIP and
Issuer Public Key Exponent is missing in the card.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Issuer Public key Exponent is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 346
2CC.046.00 Data missing: ICC Public Key Certificate
Test No: 2CC.046.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the ICC Public key Certificate is missing in ICC, the
terminal fails the Dynamic Data Authentication process.
To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b,
if Offline Dynamic Data Authentication is supported in AIP and ICC
Public Key Certificate is missing in the card.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
ICC Public Key Certificate is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 347
2CC.046.01 Data missing: ICC Public Key Certificate (2)
Test No: 2CC.046.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that if the ICC Public key Certificate is missing in ICC, the
terminal fails the Combined DDA/AC Data Authentication process.
To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b,
if Offline Combined DDA/AC Data Authentication is supported in AIP and
ICC Public Key Certificate is missing in the card.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
ICC Public Key Certificate is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 348
2CC.046.02 Data missing: ICC Public Key Certificate (3)
Test No: 2CC.046.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that if the ICC Public key Certificate is missing in ICC, the
terminal fails the Offline PIN Encryption process.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
ICC Public Key Certificate is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 349
2CC.046.03 Data missing: ICC PIN Encryption Public Key Certificate
Test No: 2CC.046.03 - Revision 43e - Number of sub cases: 0
Objective: To ensure that if the ICC PIN Encipherment Public Key Certificate is
missing in ICC, the terminal fails the Offline PIN Encryption process.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
ICC PIN Encipherment Public Key Certificate is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 350
2CC.047.00 Data missing: ICC Public Key Exponent
Test No: 2CC.047.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the ICC Public key Exponent is missing in ICC, the
terminal fails the Dynamic Data Authentication process.
To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b,
if Offline Dynamic Data Authentication is supported in AIP and ICC
Public Key Exponent is missing in the card.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
ICC Public key Exponent is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 351
2CC.047.01 Data missing: ICC Public Key Exponent (2)
Test No: 2CC.047.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that if the ICC Public key Exponent is missing in ICC, the
terminal fails the Combined DDA/AC Data Authentication process.
To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b,
if Offline Combined DDA/AC Data Authentication is supported in AIP and
ICC Public Key Exponent is missing in the card.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
ICC Public key Exponent is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 1st
GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 352
2CC.047.02 Data missing: ICC Public Key Exponent (3)
Test No: 2CC.047.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that if the ICC Public key Exponent is missing in ICC, the
terminal fails the Offline PIN Encryption process.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
ICC Public key Exponent is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 353
2CC.047.03 Data missing: ICC PIN Encryption Public Key Exponent
Test No: 2CC.047.03 - Revision 43e - Number of sub cases: 0
Objective: To ensure that if the ICC PIN Encipherment Public Key Exponent is
missing in ICC, the terminal fails the Offline PIN Encryption process.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
ICC PIN Encipherment Public Key Exponent is missing in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 354
2CC.050.00 Length of Issuer Public Key Certificate
Test No: 2CC.050.00 - Revision 11 - Number of sub cases: 2
Objective: To ensure that if the terminal supports Dynamic Data Authentication, and
if Issuer Public Key Certificate has a length different from Certification
Authority Public Key Modulus, the terminal fails the Dynamic Data
Authentication process.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Case 01: Issuer Public Key Certificate in LT is greater than
Certification Authority Public Key Modulus.
•
Case 02: Issuer Public Key Certificate in LT is less than
Certification Authority Public Key Modulus.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication)
failed received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 355
2CC.050.01 Length of Issuer Public Key Certificate (2)
Test No: 2CC.050.01 - Revision 4.3c - Number of sub cases: 2
Objective: To ensure that if the terminal supports Combined DDA/AC Data
Authentication, and if Issuer Public Key Certificate has a length different
from Certification Authority Public Key Modulus, the terminal fails the
Dynamic Data Authentication process.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that TC is requested at first Gen AC.
•
Case 01: Issuer Public Key Certificate in LT is greater than
Certification Authority Public Key Modulus.
•
Case 02: Issuer Public Key Certificate in LT is less than
Certification Authority Public Key Modulus.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 356
2CC.050.02 Length of Issuer Public Key Certificate (3)
Test No: 2CC.050.02 - Revision 43e - Number of sub cases: 2
Objective: To ensure that if the terminal supports Offline PIN Encryption, and if
Issuer Public Key Certificate has a length different from Certification
Authority Public Key Modulus, the terminal fails the PIN Encryption
process.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Case 01: Issuer Public Key Certificate in LT is greater than
Certification Authority Public Key Modulus.
•
Case 02: Issuer Public Key Certificate in LT is less than
Certification Authority Public Key Modulus.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byt 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 357
2CC.050.07 Length of Issuer Public Key Certificate (8)
Test No: 2CC.050.07 - Revision 4.3c - Number of sub cases: 2
Objective: To ensure that if the terminal supports Combined DDA/AC Data
Authentication, and if Issuer Public Key Certificate has a length different
from Certification Authority Public Key Modulus, the terminal fails the
Dynamic Data Authentication process.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online approved.
•
Case 01: Issuer Public Key Certificate in LT is greater than
Certification Authority Public Key Modulus.
•
Case 02: Issuer Public Key Certificate in LT is less than
Certification Authority Public Key Modulus.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 358
2CC.050.08 Length of Issuer Public Key Certificate (9)
Test No: 2CC.050.08 - Revision 4.3c - Number of sub cases: 2
Objective: To ensure that if the terminal supports Combined DDA/AC Data
Authentication, and if Issuer Public Key Certificate has a length different
from Certification Authority Public Key Modulus, the terminal fails the
Dynamic Data Authentication process.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online declined.
•
Case 01: Issuer Public Key Certificate in LT is greater than
Certification Authority Public Key Modulus.
•
Case 02: Issuer Public Key Certificate in LT is less than
Certification Authority Public Key Modulus.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting an AAC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 359
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 360
2CC.052.00 Recovered Data Trailer not equal to 'BC'
Test No: 2CC.052.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Data Trailer recovered from the Issuer Public Key
Certificate does not equal 'BC'.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Issuer Public Key Certificate in LT is calculated with a Data
Trailer different from 'BC'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 361
2CC.052.01 Recovered Data Trailer not equal to 'BC' (2)
Test No: 2CC.052.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Data Trailer recovered from the Issuer
Public Key Certificate does not equal 'BC'.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that TC is requested at first Gen AC.
•
Issuer Public Key Certificate in LT is calculated with a Data
Trailer different from 'BC'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 362
2CC.052.02 Recovered Data Trailer not equal to 'BC' (3)
Test No: 2CC.052.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Data Trailer recovered from the Issuer Public Key Certificate does
not equal 'BC'.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Issuer Public Key Certificate in LT is calculated with a Data
Trailer different from 'BC'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 363
2CC.052.07 Recovered Data Trailer not equal to 'BC' (8)
Test No: 2CC.052.07 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Data Trailer recovered from the Issuer
Public Key Certificate does not equal 'BC'.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online approved.
•
Issuer Public Key Certificate in LT is calculated with a Data
Trailer different from 'BC'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 364
2CC.052.08 Recovered Data Trailer not equal to 'BC' (9)
Test No: 2CC.052.08 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Data Trailer recovered from the Issuer
Public Key Certificate does not equal 'BC'.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online declined.
•
Issuer Public Key Certificate in LT is calculated with a Data
Trailer different from 'BC'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting an AAC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 365
2CC.053.00 Recovered Data Header not equal to '6A'
Test No: 2CC.053.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Data Header recovered from the Issuer Public Key
Certificate does not equal '6A'.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Issuer Public Key Certificate in LT is calculated with a Data
Header different from '6A'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 366
2CC.053.01 Recovered Data Header not equal to '6A' (2)
Test No: 2CC.053.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Data Header recovered from the Issuer
Public Key Certificate does not equal '6A'.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Issuer Public Key Certificate in LT is calculated with a Data
Header different from '6A'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 367
2CC.053.02 Recovered Data Header not equal to '6A' (3)
Test No: 2CC.053.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Data Header recovered from the Issuer Public Key Certificate does
not equal '6A'.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Issuer Public Key Certificate in LT is calculated with a Data
Header different from '6A'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 368
2CC.054.00 Certificate Format not equal to '02'
Test No: 2CC.054.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Certificate Format recovered from Issuer Public Key
Certificate does not equal '02'.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Issuer Public Key Certificate in LT is calculated with a
Certificate Format different from '02'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 369
2CC.054.01 Certificate Format not equal to '02' (2)
Test No: 2CC.054.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Certificate Format recovered from Issuer
Public Key Certificate does not equal '02'.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Issuer Public Key Certificate in LT is calculated with a
Certificate Format different from '02'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 370
2CC.054.02 Certificate Format not equal to '02' (3)
Test No: 2CC.054.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Certificate Format recovered from Issuer Public Key Certificate does
not equal '02'.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Issuer Public Key Certificate in LT is calculated with a
Certificate Format different from '02'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 371
2CC.055.00 Difference between calculated Hash Result and
recovered Hash Result
Test No: 2CC.055.00 - Revision 10g - Number of sub cases: 2
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the calculated Hash Result is different from the Hash Result
recovered from the Issuer Public Key Certificate.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Issuer Public Key Certificate in LT is calculated with a bad Hash
value.
•
Case 01: Error is on the first byte of the Hash.
•
Case 02: Error is on the last byte of the Hash.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 372
2CC.055.01 Difference between calculated Hash Result and
recovered Hash Result (2)
Test No: 2CC.055.01 - Revision 4.3c - Number of sub cases: 2
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the calculated Hash Result is different from the
Hash Result recovered from the Issuer Public Key Certificate.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that TC is requested at first Gen AC.
•
Issuer Public Key Certificate in LT is calculated with a bad Hash
value.
•
Case 01: Error is on the first byte of the Hash.
•
Case 02: Error is on the last byte of the Hash.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 373
2CC.055.02 Difference between calculated Hash Result and
recovered Hash Result (3)
Test No: 2CC.055.02 - Revision 43e - Number of sub cases: 2
Objective: To ensure that the terminal fails Offline PIN Encryption process, if the
calculated Hash Result is different from the Hash Result recovered from
the Issuer Public Key Certificate.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Issuer Public Key Certificate in LT is calculated with a bad Hash
value.
•
Case 01: Error is on the first byte of the Hash.
•
Case 02: Error is on the last byte of the Hash.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 374
2CC.055.07 Difference between calculated Hash Result and
recovered Hash Result (8)
Test No: 2CC.055.07 - Revision 4.3c - Number of sub cases: 2
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the calculated Hash Result is different from the
Hash Result recovered from the Issuer Public Key Certificate.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Issuer Public Key Certificate in LT is calculated with a bad Hash
value.
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online approved.
•
Case 01: Error is on the first byte of the Hash.
•
Case 02: Error is on the last byte of the Hash.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 375
2CC.055.08 Difference between calculated Hash Result and
recovered Hash Result (9)
Test No: 2CC.055.08 - Revision 4.3c - Number of sub cases: 2
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the calculated Hash Result is different from the
Hash Result recovered from the Issuer Public Key Certificate.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Issuer Public Key Certificate in LT is calculated with a bad Hash
value.
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online declined
•
Case 01: Error is on the first byte of the Hash.
•
Case 02: Error is on the last byte of the Hash.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting an AAC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 376
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 377
2CC.056.00 Issuer Identifier does not match leftmost 3-8 PAN digits
Test No: 2CC.056.00 - Revision 10g - Number of sub cases: 3
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Recovered Issuer Identifier does not match the leftmost
3-8 PAN digits.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Case 01: Issuer Public Key Certificate in LT is calculated with
Issuer Identifier different from leftmost 3-8 PAN digits: difference
is on digit 3.
•
Case 02: Issuer Public Key Certificate in LT is calculated with
Issuer Identifier different from leftmost 3-8 PAN digits: difference
is on digit 8.
•
Case 03: Issuer Public Key Certificate in LT is calculated with
Issuer Identifier different from leftmost 3-8 PAN digits: difference
is on all 3-8 digits.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 378
2CC.056.01 Issuer Identifier does not match leftmost 3-8 PAN digits
(2)
Test No: 2CC.056.01 - Revision 4.3c - Number of sub cases: 3
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Recovered Issuer Identifier does not match
the leftmost 3-8 PAN digits.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Case 01: Issuer Public Key Certificate in LT is calculated with
Issuer Identifier different from leftmost 3-8 PAN digits: difference
is on digit 3.
•
Case 02: Issuer Public Key Certificate in LT is calculated with
Issuer Identifier different from leftmost 3-8 PAN digits: difference
is on digit 8.
•
Case 03: Issuer Public Key Certificate in LT is calculated with
Issuer Identifier different from leftmost 3-8 PAN digits: difference
is on all 3-8 digits.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 379
2CC.056.02 Issuer Identifier does not match leftmost 3-8 PAN digits
(3)
Test No: 2CC.056.02 - Revision 43e - Number of sub cases: 3
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Recovered Issuer Identifier does not match the leftmost 3-8 PAN
digits.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Case 01: Issuer Public Key Certificate in LT is calculated with
Issuer Identifier different from leftmost 3-8 PAN digits: difference
is on digit 3.
•
Case 02: Issuer Public Key Certificate in LT is calculated with
Issuer Identifier different from leftmost 3-8 PAN digits: difference
is on digit 8.
•
Case 03: Issuer Public Key Certificate in LT is calculated with
Issuer Identifier different from leftmost 3-8 PAN digits: difference
is on all 3-8 digits.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 380
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 381
2CC.057.00 Certificate Expiration Date earlier than today's date
Test No: 2CC.057.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Certificate Expiration Date is earlier than the current date.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Issuer Public Key Certificate in LT is calculated with Certificate
Expiration Date earlier than the current date.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 382
2CC.057.01 Certificate Expiration Date earlier than today's date (2)
Test No: 2CC.057.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Certificate Expiration Date is earlier than
the current date.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that TC is requested at first Gen AC.
•
Issuer Public Key Certificate in LT is calculated with Certificate
Expiration Date earlier than the current date.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' 'ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 383
2CC.057.02 Certificate Expiration Date earlier than today's date (3)
Test No: 2CC.057.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Certificate Expiration Date is earlier than the current date.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Issuer Public Key Certificate in LT is calculated with Certificate
Expiration Date earlier than the current date.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 384
2CC.057.07 Certificate Expiration Date earlier than today's date (8)
Test No: 2CC.057.07 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Certificate Expiration Date is earlier than
the current date.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online approved.
•
Issuer Public Key Certificate in LT is calculated with Certificate
Expiration Date earlier than the current date.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' 'ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 385
2CC.057.08 Certificate Expiration Date earlier than today's date (9)
Test No: 2CC.057.08 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Certificate Expiration Date is earlier than
the current date.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online declined.
•
Issuer Public Key Certificate in LT is calculated with Certificate
Expiration Date earlier than the current date.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting an AAC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' 'ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 386
2CC.058.00 RID, CA Public Key Index and Certificate Serial Number
not valid, DDA
Test No: 2CC.058.00 - Revision 13 - Number of sub cases: 3
Objective: To ensure that when supporting Certification Revocation List (CRL),
thirty entries per RID are supported, and when the terminal fails the
Dynamic Data Authentication process if the concatenation of RID, CA
Public Key Index and Certificate Serial Number and any additional data
indicates a revoked certificate.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book 2 - Section 6.1.2 - Certification Revocation List
Terminal [DDA] supported AND [Key Revocation] supported
Configuration:
Conditions:
•
Terminal supports three RIDs
•
Terminal is loaded with 30 CRL entries (formatted according to
ICS defined format) per RID. 29 of these entries per RID are
based on Certificate Serial Numbers which are not signed (i.e.
dummy test data)
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Case 01 - The terminal is loaded with the 30 CRL entries,
specified above, for RID 1.
•
Case 02 - The terminal is loaded with the 30 CRL entries,
specified above, for RID 2.
•
Case 03 - The terminal is loaded with the 30 CRL entries,
specified above, for RID 3.
•
Issuer Public Key Certificate in LT is calculated with RID, CA
Public Key Index and Certificate Serial Number such that the
certificate correspond to the signed CRL entry in the revocation
list of the terminal.
Action: NA
Procedure: Application in LT is selected, for each RID as specified in each case, and
transaction is processed with LT (in particular Dynamic Data
Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 387
2CC.058.00 RID, CA Public Key Index and Certificate Serial Number
not valid, DDA
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 388
2CC.058.01 RID, CA Public Key Index and Certificate Serial Number
not valid, CDA (2)
Test No: 2CC.058.01 - Revision 4.3c - Number of sub cases: 3
Objective: To ensure that when supporting Certification Revocation List (CRL),
thirty entries per RID are supported, and when the terminal fails the
Combined DDA/AC Data Authentication process if the concatenation of
RID, CA Public Key Index and Certificate Serial Number and any
additional data indicates a revoked certificate.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins – Section SU 44 – Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book 2 - Section 6.1.2 - Certification Revocation List
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND [Key Revocation] supported
Configuration:
Conditions:
•
Terminal supports three RIDs
•
Terminal is loaded with 30 CRL entries (formatted according to
ICS defined format) per RID. 29 of these entries are based on
Certificate Serial Numbers which are not signed (i.e. dummy
test data)AIP of LT indicates CDA is supported (AIP byte 1 bit 1
= ‘1’).
•
Issuer Public Key Certificate in LT is calculated with RID, CA
Public Key Index and Certificate Serial Number such that the
certificate correspond to the signed CRL entry in the revocation
list of the terminal.
•
Case 01 - The terminal is loaded with the 30 CRL entries,
specified above, for RID 1.
•
Case 02 - The terminal is loaded with the 30 CRL entries,
specified above, for RID 2.
•
Case 03 - The terminal is loaded with the 30 CRL entries,
specified above, for RID 3.
Action: NA
Procedure: Application in LT is selected , for each RID as specified in each case,
and transaction is processed with LT (in particular Combined
DDA/Application Cryptogram Generation)
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 389
2CC.058.01 RID, CA Public Key Index and Certificate Serial Number
not valid, CDA (2)
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 390
2CC.058.02 RID, CA Public Key Index and Certificate Serial Number
not valid, Offline Enciphered PIN
Test No: 2CC.058.02 - Revision 43e - Number of sub cases: 3
Objective: To ensure that when supporting Certification Revocation List (CRL),
thirty entries per RID are supported, and when the terminal fails the
Offline PIN Encryption process if the concatenation of RID, CA Public
Key Index and Certificate Serial Number and any additional data
indicates a revoked certificate.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported AND [Key Revocation] supported
Configuration:
Conditions:
•
Terminal supports three RIDs
•
Terminal is loaded with 30 CRL entries (formatted according to
ICS defined format) per RID. 29 of these entries are based on
Certificate Serial Numbers which are not signed (i.e. dummy
test data)
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Case 01 - The terminal is loaded with the 30 CRL entries,
specified above, for RID 1.
•
Case 02 - The terminal is loaded with the 30 CRL entries,
specified above, for RID 2.
•
Case 03 - The terminal is loaded with the 30 CRL entries,
specified above, for RID 3.
•
Issuer Public Key Certificate in LT is calculated with RID, CA
Public Key Index and Certificate Serial Number such that the
certificate correspond to the signed CRL entry in the revocation
list of the terminal.
Action: NA
Procedure: Application in LT is selected, for each RID as specified in each case, and
transaction is processed with LT (in particular offline PIN encryption)
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 391
2CC.058.02 RID, CA Public Key Index and Certificate Serial Number
not valid, Offline Enciphered PIN
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 392
2CC.058.04 Certification Revocation List update, removal (2)
Test No: 2CC.058.04 - Revision 13 - Number of sub cases: 0
Objective: To ensure that the terminal is be able to update the Certification
Revocation List by deleting an entry.
Reference Book 2 - Section 5.1.2 - Certification Revocation List
EMV 4.3:
Terminal [DDA] supported AND [Key Revocation] supported
Configuration:
Conditions:
•
Terminal has been loaded with 30 CRL entries as described in
2CC.058.00
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
AIP of LT indicates that other data authentication methods are
not supported (AIP byte 1 bit 7 = ‘0’, byte 1 bit 5 = ‘0’, and byte
1 bit 1 = ‘0’)
•
The CRL update process is completed before undertaking an
EMV transaction.
•
A valid CRL entry is removed from the device, where the LT
Issuer Public Key Certificate in LT is calculated with RID, CA
Public Key Index and Certificate Serial Number to correspond to
this valid entry.
Action: NA
Procedure: A default acquirer process as documented by the device vendor is
performed to update the CRL.
Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:r
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
succesful) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 393
2CC.058.05 Certification Revocation List update, addition (2)
Test No: 2CC.058.05 - Revision 13 - Number of sub cases: 0
Objective: To ensure that the terminal is able to update the Certification Revocation
List by adding an entry.
Reference Book 2 - Section 5.1.2 - Certification Revocation List
EMV 4.3:
Terminal [DDA] supported AND [Key Revocation] supported
Configuration:
Conditions:
•
Terminal is loaded with 29 CRL entries and 2CC.058.04 has
been performed before this test
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
AIP of LT indicates that other data authentication methods are
not supported (AIP byte 1 bit 7 = ‘0’, byte 1 bit 5 = ‘0’, and byte
1 bit 1 = ‘0’)
•
The CRL update process is completed before undertaking an
EMV transaction.
•
A valid CRL entry is loaded to the device, where the LT Issuer
Public Key Certificate is calculated with RID, CA Public Key
and Certificate Serial Number corresponding to this valid entry.
Action: NA
Procedure: A default acquirer process as documented by the device vendor is
performed to update the CRL.
Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Please note: 2CC.058.04 - Certification Revocation List update, removal
must be performed before this test
Pass Criteria
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '1' (ie Dynamic Data Authentication failed)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 394
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 395
2CC.058.06 Certification Revocation List update, removal (3)
Test No: 2CC.058.06 - Revision 4.3a - Number of sub cases: 0
Objective: To ensure that the terminal is be able to update the Certification
Revocation List by deleting an entry.
Reference Book 2 - Section 5.1.2 - Certification Revocation List
EMV 4.3:
Terminal [CDA] supported AND [Key Revocation] supported
Configuration:
Conditions:
•
Terminal has been loaded with 30 CRL entries as described in
2CC.058.01
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
AIP of LT indicates that other data authentication methods are
not supported (AIP byte 1 bit 7 = ‘0’, byte 1 bit 5 = ‘0’, and byte
1 bit 6 = ‘0’)
•
The CRL update process is completed before undertaking an
EMV transaction.
•
A valid CRL entry is removed from the device, where the LT
Issuer Public Key Certificate in LT is calculated with RID, CA
Public Key Index and Certificate Serial Number to correspond to
this valid entry.
Action: NA
Procedure: A default acquirer process as documented by the device vendor is
performed to update the CRL.
Application in LT is selected and transaction is processed with LT (in
particular Combined Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication
succesful) contained in Financial confirmation messages or
Batch Data Capture message.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) contained in Financial confirmation messages or Batch
Data Capture message.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 396
2CC.058.06 Certification Revocation List update, removal (3)
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial confirmation messages or
Batch Data Capture message.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 397
2CC.058.07 Certification Revocation List update, addition (3)
Test No: 2CC.058.07 - Revision 4.1e - Number of sub cases: 0
Objective: To ensure that the terminal is be able to update the Certification
Revocation List by adding an entry.
Reference Book 2 - Section 5.1.2 - Certification Revocation List
EMV 4.3:
Terminal [CDA] supported AND [Key Revocation] supported
Configuration:
Conditions:
•
Terminal is loaded with 29 CRL entries and 2CC.058.06 has
been performed before this test
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
AIP of LT indicates that other data authentication methods are
not supported (AIP byte 1 bit 7 = ‘0’, byte 1 bit 5 = ‘0’, and byte
1 bit 6 = ‘0’)
•
The CRL update process is completed before undertaking an
EMV transaction.
•
A valid CRL entry is loaded to the device, where the LT Issuer
Public Key Certificate in LT is calculated with RID, CA Public
Key Index and Certificate Serial Number to correspond to this
valid entry.
Action: NA
Procedure: A default acquirer process as documented by the device vendor is
performed to update the CRL.
Application in LT is selected and transaction is processed with LT (in
particular Combined Data Authentication).
Please note: 2CC.058.06 - Certification Revocation List update, removal
must be performed before this test
Pass Criteria
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed)
contained in Financial confirmation messages or Batch Data
Capture message (this pass criteria apply only if the terminal
has the capability to store declined transaction).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 398
2CC.058.08 Certification Revocation List update, removal (4)
Test No: 2CC.058.08 - Revision 13a - Number of sub cases: 0
Objective: To ensure that the terminal is able to update the Certification Revocation
List as requested by deleting an entry.
Reference Book 2 - Section 5.1.2 - Certification Revocation List
EMV 4.3:
Terminal [Offline Enciphered PIN ] supported AND [Key Revocation] supported
Configuration:
Conditions:
•
Terminal has been loaded with 30 CRL entries as described in
2CC.058.02
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
AIP of LT indicates that other data authentication methods are
not supported (AIP byte 1 bit 7 = ‘0’, byte 1 bit 1 = ‘0’, and byte
6 bit 1 = ‘0’)
•
The CRL update process is completed before undertaking an
EMV transaction.
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
A valid CRL entry is removed from the device, where the LT .
Issuer Public Key Certificate is calculated with RID, CA Public
Key Index and Certificate Serial Number corresponding to this
valid entry.
Action: NA
Procedure: A default acquirer process as documented by the device vendor
is
performed to update the CRL.
Application in LT is selected and transaction is processed with LT
Pass Criteria
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '0' (ie Cardholder verification succesful)
received at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 399
2CC.058.09 Certification Revocation List update, addition (4)
Test No: 2CC.058.09 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal is able to update the Certification Revocation
List by adding an entry.
Reference Book 2 - Section 5.1.2 - Certification Revocation List
EMV 4.3:
Terminal [Offline Enciphered PIN ] supported AND [Key Revocation] supported
Configuration:
Conditions:
•
Terminal is loaded with 29 CRL entries and 2CC.058.08 has
been performed before this test
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
AIP of LT indicates that other data authentication methods are
not supported (AIP byte 1 bit 7 = ‘0’, byte 1 bit 1 = ‘0’, and byte
1 bit 6 = ‘0’)
•
The CRL update process is completed before undertaking an
EMV transaction.
•
A valid CRL entry is loaded to the device, where the LT Issuer
Public Key Certificate is calculated with RID, CA Public Key
Index and Certificate Serial Number corresponding to this valid
entry.
Action: NA
Procedure: A default acquirer process must be performed to update the CRL.
Application in LT is selected and transaction is processed with LT.
Pass Criteria
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 400
2CC.058.09 Certification Revocation List update, addition (4)
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 401
2CC.059.00 Issuer Public Key Algorithm not recognized
Test No: 2CC.059.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Issuer Public Key Algorithm is not supported (different
from '01').
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Issuer Public Key Certificate in LT is calculated with Issuer
Public Key Algorithm value different from '01'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 402
2CC.059.01 Issuer Public Key Algorithm not recognized (2)
Test No: 2CC.059.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Issuer Public Key Algorithm is not
supported (different from '01').
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Issuer Public Key Certificate in LT is calculated with Issuer
Public Key Algorithm value different from '01'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 403
2CC.059.02 Issuer Public Key Algorithm not recognized (3)
Test No: 2CC.059.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Issuer Public Key Algorithm is not supported (different from '01').
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Issuer Public Key Certificate in LT is calculated with Issuer
Public Key Algorithm value different from '01'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 404
2CC.060.00 Issuer Identifier with length between 3 to 8 digits
Test No: 2CC.060.00 - Revision 10g - Number of sub cases: 3
Objective: To
ensure that the terminal correctly processes Static Data
Authentication, if the Recovered Issuer Identifier has a length between 3
to 8 digits.
Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [SDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Static Data Authentication is supported (AIP
byte 1 bit 7 = ‘1’).
•
Case 01: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 3 digits and right padded with 'F'
up to a length of 8 digits.
•
Case 02: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 6 digits and right padded with 'F'
up to a length of 8 digits.
•
Case 03: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 8 digits.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
not used) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication succeeded)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 405
2CC.060.01 Issuer Identifier with length between 3 to 8 digits (2)
Test No: 2CC.060.01 - Revision 10g - Number of sub cases: 3
Objective: To ensure that the terminal correctly processes the Dynamic Data
Authentication, if the Recovered Issuer Identifier has a length between 3
and 8 digits.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6= 1).
•
Case 01: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 3 digits and right padded with 'F'
up to a length of 8 digits.
•
Case 02: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 6 digits and right padded with 'F'
up to a length of 8 digits.
•
Case 03: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 8 digits.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 406
2CC.060.02 Issuer Identifier with length between 3 to 8 digits (2)
Test No: 2CC.060.02 - Revision 4.1e - Number of sub cases: 3
Objective: To ensure that the terminal correctly processes the Enhanced Combined
Data Authentication, if the Recovered Issuer Identifier has a length
between 3 and 8 digits.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal ([Offline Only] OR [Offline/Online Capable]) AND [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
TAC/IAC set to request a TC in the 1st GENERATE AC, and LT
responds TC
•
Case 01: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 3 digits and right padded with 'F'
up to a length of 8 digits.
•
Case 02: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 6 digits and right padded with 'F'
up to a length of 8 digits.
•
Case 03: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 8 digits.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
not used) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication
succeeded) received at 1st GENERATE AC, in Financial
message or Batch Data Capture message.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 407
2CC.060.03 Issuer Identifier with length between 3 to 8 digits (3)
Test No: 2CC.060.03 - Revision 12 - Number of sub cases: 3
Objective: To ensure that the terminal correctly processes the Enciphered PIN
verification Offline, if the Recovered Issuer Identifier has a length
between 3 and 8 digits.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
AIP of LT indicates data authentication is not supported (AIP
B1b7=0, B1b6=0, B1b1=1).
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Case 01: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 3 digits and right padded with 'F'
up to a length of 8 digits.
•
Case 02: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 6 digits and right padded with 'F'
up to a length of 8 digits.
•
Case 03: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 8 digits.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
not used) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = ‘0’ (ie Offline Data Authentication not
performed) received at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder Verification was performed)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 408
2CC.060.04 Issuer Identifier with length between 3 to 8 digits (4)
Test No: 2CC.060.04 - Revision 43e - Number of sub cases: 3
Objective: To ensure that the terminal correctly processes the Enhanced Combined
Data Authentication, if the Recovered Issuer Identifier has a length
between 3 and 8 digits.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [Online Only] AND ([CDA Mode1] OR [CDA Mode2] OR [CDA Mode4])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
LT returns an ARQC to the first GENERATE AC
•
IAC’s and TAC’s are set so that an ARQC is requested at first
GENERATE AC and a TC at second GENERATE AC.
•
Case 01: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 3 digits and right padded with 'F'
up to a length of 8 digits.
•
Case 02: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 6 digits and right padded with 'F'
up to a length of 8 digits.
•
Case 03: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 8 digits.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
The terminal must request a CDA at first or second GENERATE
AC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
not used) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication
succeeded) contained in Financial Confirmation message or
Batch Data Capture message.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 409
2CC.060.04 Issuer Identifier with length between 3 to 8 digits (4)
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 410
2CC.060.05 Issuer Identifier with length between 3 to 8 digits (5)
Test No: 2CC.060.05 - Revision 15 - Number of sub cases: 3
Objective: To ensure that the terminal correctly processes the Enhanced Combined
Data Authentication, if the Recovered Issuer Identifier has a length
between 3 and 8 digits.
Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [Online Only] AND [CDA] supported AND [Normal Default Action Code
Configuration: processing]
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
LT returns an ARQC to the first GENERATE AC
•
IAC’s and TAC’s are set so that an ARQC is requested at first
GENERATE AC and a TC at second GENERATE AC.
•
Terminal is unable to go online
•
Case 01: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 3 digits and right padded with 'F'
up to a length of 8 digits.
•
Case 02: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 6 digits and right padded with 'F'
up to a length of 8 digits.
•
Case 03: Issuer Public Key Certificate in LT is calculated using
Issuer Identifier with length of 8 digits.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
not used) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication
succeeded) contained in Financial Confirmation message or
Batch Data Capture message.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 411
2CC.060.05 Issuer Identifier with length between 3 to 8 digits (5)
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 412
2CC.061.00 Length of ICC Public Key Certificate
Test No: 2CC.061.00 - Revision 11 - Number of sub cases: 2
Objective: To ensure that if the terminal supports Dynamic Data Authentication, and
if ICC Public Key Certificate has a length different from Issuer Public Key
Modulus, the terminal fails the Dynamic Data Authentication process.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Case 01: ICC Public Key Certificate in LT is greater than Issuer
Public Key Modulus.
•
Case 02: ICC Public Key Certificate in LT is less than Issuer
Public Key Modulus.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 413
2CC.061.01 Length of ICC Public Key Certificate (2)
Test No: 2CC.061.01 - Revision 4.3c - Number of sub cases: 2
Objective: To ensure that if the terminal supports Combined DDA/AC Data
Authentication, and if ICC Public Key Certificate has a length different
from that of Issuer Public Key Modulus, the terminal fails the Dynamic
Data Authentication process.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that TC is requested at first Gen AC.
•
Case 01: ICC Public Key Certificate in LT is greater than Issuer
Public Key Modulus.
•
Case 02: ICC Public Key Certificate in LT is less than Issuer
Public Key Modulus.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 414
2CC.061.02 Length of ICC Public Key Certificate (3)
Test No: 2CC.061.02 - Revision 43e - Number of sub cases: 2
Objective: To ensure that if the terminal supports Offline PIN Encryption, and if ICC
Public Key Certificate has a length different from that of Issuer Public
Key Modulus, the terminal fails the PIN Encryption process.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
Case 01: ICC Public Key Certificate in LT is greater than Issuer
Public Key Modulus.
•
Case 02: ICC Public Key Certificate in LT is less than Issuer
Public Key Modulus.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 415
2CC.061.03 Length of ICC PIN Encipherment Public Key Certificate
Test No: 2CC.061.03 - Revision 43e - Number of sub cases: 2
Objective: To ensure that if the terminal supports Offline PIN Encryption, and if ICC
PIN Encipherment Public Key Certificate has a length different from that
of Issuer Public Key Modulus, the terminal fails the PIN Encryption
process.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
Case 01: ICC PIN Encipherment Public Key Certificate in LT is
greater than Issuer Public Key Modulus.
•
Case 02: ICC PIN Encipherment Public Key Certificate in LT is
less than Issuer Public Key Modulus.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 416
2CC.061.08 Length of ICC Public Key Certificate (9)
Test No: 2CC.061.08 - Revision 4.3c - Number of sub cases: 2
Objective: To ensure that if the terminal supports Combined DDA/AC Data
Authentication, and if ICC Public Key Certificate has a length different
from that of Issuer Public Key Modulus, the terminal fails the Dynamic
Data Authentication process.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online approved.
•
Case 01: ICC Public Key Certificate in LT is greater than Issuer
Public Key Modulus.
•
Case 02: ICC Public Key Certificate in LT is less than Issuer
Public Key Modulus.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 417
2CC.061.08 Length of ICC Public Key Certificate (9)
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 418
2CC.061.09 Length of ICC Public Key Certificate (10)
Test No: 2CC.061.09 - Revision 4.3c - Number of sub cases: 2
Objective: To ensure that if the terminal supports Combined DDA/AC Data
Authentication, and if ICC Public Key Certificate has a length different
from that of Issuer Public Key Modulus, the terminal fails the Dynamic
Data Authentication process.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online declined.
•
Case 01: ICC Public Key Certificate in LT is greater than Issuer
Public Key Modulus.
•
Case 02: ICC Public Key Certificate in LT is less than Issuer
Public Key Modulus.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting an AAC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 419
2CC.061.09 Length of ICC Public Key Certificate (10)
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 420
2CC.063.00 Recovered Data Trailer not equal to 'BC'
Test No: 2CC.063.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Data Trailer recovered from the ICC Public Key Certificate
does not equal 'BC'.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
ICC Public Key Certificate in LT is calculated with a Data Trailer
different from 'BC'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 421
2CC.063.01 Recovered Data Trailer not equal to 'BC' (2)
Test No: 2CC.063.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Data Trailer recovered from the ICC Public
Key Certificate does not equal 'BC'.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
ICC Public Key Certificate in LT is calculated with a Data Trailer
different from 'BC'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 422
2CC.063.02 Recovered Data Trailer not equal to 'BC' (3)
Test No: 2CC.063.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Data Trailer recovered from the ICC Public Key Certificate does not
equal 'BC'.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
ICC Public Key Certificate in LT is calculated with a Data Trailer
different from 'BC'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 423
2CC.063.03 Recovered Data Trailer not equal to 'BC' (4)
Test No: 2CC.063.03 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Data Trailer recovered from the ICC PIN Encipherment Public Key
Certificate does not equal 'BC'.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
ICC PIN Encipherment Public Key Certificate in LT is calculated
with a Data Trailer different from 'BC'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 424
2CC.064.00 Recovered Data Header not equal to '6A'
Test No: 2CC.064.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Data Header recovered from the ICC Public Key
Certificate does not equal '6A'.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
ICC Public Key Certificate in LT is calculated with a Data
Header different from '6A'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 425
2CC.064.01 Recovered Data Header not equal to '6A' (2)
Test No: 2CC.064.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Data Header recovered from the ICC
Public Key Certificate does not equal '6A'.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
ICC Public Key Certificate in LT is calculated with a Data
Header different from '6A'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 426
2CC.064.02 Recovered Data Header not equal to '6A' (3)
Test No: 2CC.064.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Data Header recovered from the ICC Public Key Certificate does not
equal '6A'.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
ICC Public Key Certificate in LT is calculated with a Data
Header different from '6A'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 427
2CC.064.03 Recovered Data Header not equal to '6A' (4)
Test No: 2CC.064.03 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Data Header recovered from the ICC PIN Encipherment Public Key
Certificate does not equal '6A'.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
ICC PIN Encipherment Public Key Certificate in LT is calculated
with a Data Header different from '6A'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 428
2CC.065.00 Certificate Format not equal to '04'
Test No: 2CC.065.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Certificate Format recovered from ICC Public Key
Certificate does not equal '04'.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
ICC Public Key Certificate in LT is calculated with a Certificate
Format different from '04'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 429
2CC.065.01 Certificate Format not equal to '04' (2)
Test No: 2CC.065.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Certificate Format recovered from ICC
Public Key Certificate does not equal '04'.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
ICC Public Key Certificate in LT is calculated with a Certificate
Format different from '04'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 430
2CC.065.02 Certificate Format not equal to '04' (3)
Test No: 2CC.065.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Certificate Format recovered from ICC Public Key Certificate does
not equal '04'.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Card verification is supported (AIP byte 1 bit
5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
ICC Public Key Certificate in LT is calculated with a Certificate
Format different from '04'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 431
2CC.065.03 Certificate Format not equal to '04' (4)
Test No: 2CC.065.03 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Certificate Format recovered from ICC PIN Encipherment Public Key
Certificate does not equal '04'.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Card verification is supported (AIP byte 1 bit
5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
ICC PIN Encipherment Public Key Certificate in LT is calculated
with a Certificate Format different from '04'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 432
2CC.066.00 Difference between calculated Hash Result and
recovered Hash Result
Test No: 2CC.066.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the calculated Hash Result is different from the Hash Result
recovered from the ICC Public Key Certificate.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
ICC Public Key Certificate in LT is calculated with a bad Hash
value.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 433
2CC.066.01 Difference between calculated Hash Result and
recovered Hash Result (2)
Test No: 2CC.066.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the calculated Hash Result is different from the
Hash Result recovered from the ICC Public Key Certificate.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that TC is requested at first Gen AC.
•
ICC Public Key Certificate in LT is calculated with a bad Hash
value.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 434
2CC.066.02 Difference between calculated Hash Result and
recovered Hash Result (3)
Test No: 2CC.066.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the calculated Hash Result is different from the Hash Result recovered
from the ICC Public Key Certificate.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
ICC Public Key Certificate in LT is calculated with a bad Hash
value.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 435
2CC.066.03 Difference between calculated Hash Result and
recovered Hash Result (4)
Test No: 2CC.066.03 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the calculated Hash Result is different from the Hash Result recovered
from the ICC PIN Encipherment Public Key Certificate
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
ICC PIN Encipherment Public Key Certificate in LT is calculated
with a bad Hash value.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 436
2CC.066.08 Difference between calculated Hash Result and
recovered Hash Result (9)
Test No: 2CC.066.08 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the calculated Hash Result is different from the
Hash Result recovered from the ICC Public Key Certificate.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online approved.
•
ICC Public Key Certificate in LT is calculated with a bad Hash
value.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 437
2CC.066.09 Difference between calculated Hash Result and
recovered Hash Result (10)
Test No: 2CC.066.09 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the calculated Hash Result is different from the
Hash Result recovered from the ICC Public Key Certificate.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online declined.
•
ICC Public Key Certificate in LT is calculated with a bad Hash
value.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting an AAC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 438
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 439
2CC.067.00 Recovered PAN is not equal to read PAN
Test No: 2CC.067.00 - Revision 4.1e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Recovered PAN does not match the PAN digits recovered
from the LT.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
ICC Public Key Certificate in LT is calculated with PAN different
from PAN in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 440
2CC.067.01 Recovered PAN is not equal to read PAN (2)
Test No: 2CC.067.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Recovered PAN does not match the PAN
digits recovered from the LT.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
ICC Public Key Certificate in LT is calculated with Issuer ID
different from PAN in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 441
2CC.067.02 Recovered PAN is not equal to read PAN (3)
Test No: 2CC.067.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Recovered PAN does not match the PAN digits recovered from the
LT.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
Issuer Public Key Certificate in LT is calculated with Issuer ID
different from PAN in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 442
2CC.067.03 Recovered PAN is not equal to read PAN (4)
Test No: 2CC.067.03 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Recovered PAN does not match the PAN digits from the ICC PIN
Encipherment Public Key Certificate.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
ICC PIN Encipherment Public Key Certificate in LT is calculated
with application PAN different from PAN in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 443
2CC.068.00 Certificate Expiration Date earlier than today's date
Test No: 2CC.068.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Certificate Expiration Date is earlier than the current date.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
ICC Public Key Certificate in LT is calculated with Certificate
Expiration Date earlier than the current date.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 444
2CC.068.01 Certificate Expiration Date earlier than today's date (2)
Test No: 2CC.068.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the Certificate Expiration Date is earlier than
the current date.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
ICC Public Key Certificate in LT is calculated with Certificate
Expiration Date earlier than the current date.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 445
2CC.068.02 Certificate Expiration Date earlier than today's date (3)
Test No: 2CC.068.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Certificate Expiration Date is earlier than the current date.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
ICC Public Key Certificate in LT is calculated with Certificate
Expiration Date earlier than the current date.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 446
2CC.068.03 Certificate Expiration Date earlier than today's date (4)
Test No: 2CC.068.03 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the Certificate Expiration Date in the ICC PIN Encipherment Public Key
Certificate is earlier than the current date.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
ICC PIN Encipherment Public Key Certificate in LT is calculated
with Certificate Expiration Date earlier than the current date.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 447
2CC.069.00 ICC Public Key Algorithm not recognized
Test No: 2CC.069.00 - Revision 15 - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the ICC Public Key Algorithm used is not supported (different
from '01').
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
ICC Public Key Certificate in LT is calculated with ICC Public
Key Algorithm value different from '01'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 448
2CC.069.01 ICC Public Key Algorithm not recognized (2)
Test No: 2CC.069.01 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the ICC Public Key Algorithm used is not
supported (different from '01').
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that TC is requested at first Gen AC.
•
ICC Public Key Certificate in LT is calculated with ICC Public
Key Algorithm value different from '01'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 449
2CC.069.02 ICC Public Key Algorithm not recognized (3)
Test No: 2CC.069.02 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the ICC Public Key Algorithm used is not supported (different from '01').
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
ICC Public Key Certificate in LT is calculated with ICC Public
Key Algorithm value different from '01'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 450
2CC.069.03 ICC Public Key Algorithm not recognized (4)
Test No: 2CC.069.03 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal fails the Offline PIN Encryption process, if
the ICC PIN Encipherment Public Key Algorithm used is not supported
(different from '01').
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book 2 - Section 7.1 - Keys and Certificates
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
CVM List is 'Enciphered PIN, if terminal supports' (04 03)
•
ICC PIN Encipherment Public Key Certificate in LT is calculated
with ICC PIN Encipherment Public Key Algorithm value different
from '01'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received
at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 451
2CC.069.08 ICC Public Key Algorithm not recognized (9)
Test No: 2CC.069.08 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the ICC Public Key Algorithm used is not
supported (different from '01').
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online approved.
•
ICC Public Key Certificate in LT is calculated with ICC Public
Key Algorithm value different from '01'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 452
2CC.069.09 ICC Public Key Algorithm not recognized (10)
Test No: 2CC.069.09 - Revision 4.3c - Number of sub cases: 0
Objective: To ensure that the terminal fails the Combined DDA/AC Data
Authentication process, if the ICC Public Key Algorithm used is not
supported (different from '01').
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section AN 41 – Application Note N° 41,
recommendation for CDA terminals (November 2008)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online declined.
•
ICC Public Key Certificate in LT is calculated with ICC Public
Key Algorithm value different from '01'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT.
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting an AAC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data
Authentication failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 453
2CC.071.00 Dynamic Signature generation
Test No: 2CC.071.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal supports a valid DDOL.
To ensure that if Dynamic Data Authentication is supported, the terminal
is able to issue an INTERNAL AUTHENTICATE command including data
elements specified in DDOL.
Reference Book 2 - Section 6.5.1 - Dynamic Signature Generation
EMV 4.3:
Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL)
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
DDOL is present in LT.
•
Dynamic signature computed by LT is correct.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
The LT shall receive an INTERNAL AUTHENTICATE command
with concatenation of data in DDOL according to rule described
in Book 3 Section 1.4.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 454
2CC.072.00 Default DDOL
Test No: 2CC.072.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if Dynamic Data Authentication is supported, and card
does not contain DDOL, the terminal is able to use its default DDOL.
Reference Book 2 - Section 6.5.1 - Dynamic Signature Generation
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
Default DDOL is present in terminal.
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
DDOL is absent in LT.
•
Dynamic signature computed by LT is correct.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
The LT shall receive an INTERNAL AUTHENTICATE command
with concatenation of data in default DDOL according to rule
described in Book 3 Section1.4.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 455
2CC.074.00 Source of Unpredictable Number
Test No: 2CC.074.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if Dynamic Data Authentication is supported and the
DDOL requests an unpredictable Number, the terminal send an
INTERNAL AUTHENTICATE command containing this number on 4
bytes.
Reference Book 2 - Section 6.5.1 - Dynamic Signature Generation
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
DDOL requests unpredictable number (9F 37) on 4 bytes.
•
Dynamic signature computed by LT is correct.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
The LT shall receive an INTERNAL AUTHENTICATE command
with unpredictable Number contained in the data field.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 456
2CC.075.00 DDOL does not contain unpredictable Number
Test No: 2CC.075.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if Dynamic Data Authentication is supported and the
DDOL in card does not request an unpredictable Number, the terminal
fails the Dynamic Data Authentication process.
Reference Book 2 - Section 6.5.1 - Dynamic Signature Generation
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
Default DDOL in terminal requests unpredictable number (9F
37).
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
DDOL in LT does not request unpredictable number (9F 37).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 457
2CC.076.00 Default DDOL does not contain unpredictable Number
Test No: 2CC.076.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if Dynamic Data Authentication is supported, the card
does not contain DDOL and the default DDOL in terminal does not
request an unpredictable Number, the terminal fails the Dynamic Data
Authentication process.
Reference Book 2 - Section 6.5.1 - Dynamic Signature Generation
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
DDOL is absent in LT.
•
default DDOL in terminal does not request unpredictable
number (9F 37).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 458
2CC.078.00 Signed Dynamic Application Data Length not OK
Test No: 2CC.078.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports Dynamic Data Authentication, and
if Signed Dynamic Application Data has a length different from ICC
Public Key Modulus, the terminal fails the Dynamic Data Authentication
process.
Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Signed Dynamic Application Data computed by LT has a length
different from that of ICC Public Key Modulus.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 459
2CC.079.00 Recovery Function
Test No: 2CC.079.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal is able to perform the recovery function on
the Signed Dynamic Application Data for Dynamic Data Authentication
as specified in Book 2, A2.1.
Reference Book 2 - Section A2.1 - Digital Signature Scheme Giving Message
EMV 4.3: Recovery
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Signed Dynamic Application Data computed by LT is correct.
•
Issuer Public Key Certificate is valid.
•
ICC public Certificate is valid.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication
succeeded) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 460
2CC.080.00 Recovered Data Trailer not equal to 'BC'
Test No: 2CC.080.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Data Trailer recovered from the Signed Dynamic
Application Data does not equal 'BC'.
Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Signed Dynamic Application Data is calculated by LT with a
Data Trailer different from 'BC'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria: The terminal shall process the transaction until completion, by requesting
a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 461
2CC.081.00 Recovered Data Header not equal to '6A'
Test No: 2CC.081.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Data Header recovered from the Signed Dynamic
Application Data does not equal '6A'.
Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Signed Dynamic Application Data is calculated by LT with a
Data Header different from '6A'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 462
2CC.082.00 Certificate Format not equal to '05'
Test No: 2CC.082.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the Certificate Format recovered from Signed Dynamic
Application Data does not equal '05'.
Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Signed Dynamic Application Data is calculated by LT with a
Certificate Format different from '05'.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 463
2CC.083.00 Difference between calculated Hash Result and
recovered Hash Result
Test No: 2CC.083.00 - Revision 10g - Number of sub cases: 3
Objective: To ensure that the terminal fails the Dynamic Data Authentication
process, if the calculated Hash Result is different from the Hash Result
recovered from the Signed Dynamic Application Data.
Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Signed Dynamic Application Data is calculated by LT with a bad
Hash value.
•
Case 01: Error is on the 11th byte of the Hash.
•
Case 02: Error is on the first byte of the Hash.
•
Case 03: Error is on the last byte of the Hash.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication
failed) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 464
2CC.085.00 SDA Tag List in Dynamic Data Authentication
Test No: 2CC.085.00 - Revision 10g - Number of sub cases: 2
Objective: To ensure that the terminal checks that SDA Tag List contains only AIP
while executing DDA process.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
Case 01: SDA Tag List contains AFL, certificate and hash are
calculated with the AFL value.
•
Case 02: SDA Tag List contains AFL and AIP, certificate and
hash are calculated with the AFL and AIP values.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '1' (ie Offline DDA failed) received at 1st
GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 465
2CC.085.01 SDA Tag List in Dynamic Data Authentication (1)
Test No: 2CC.085.01 - Revision 4.3c - Number of sub cases: 2
Objective: To ensure that the terminal checks that SDA Tag List contains only AIP
while performing Combined DDA/AC process.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that TC is requested at first Gen AC.
•
Case 01: SDA Tag List contains AFL, certificate and hash are
calculated with the AFL value.
•
Case 02: SDA Tag List contains AFL and AIP, certificate and
hash are calculated with the AFL and AIP values.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The Terminal shall not request CDA for the GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC according to TAC and IAC setting.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC failed,)
received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 466
2CC.085.02 SDA Tag List in Dynamic Data Authentication (3)
Test No: 2CC.085.02 - Revision 11 - Number of sub cases: 0
Objective: To ensure that the terminal checks that SDA Tag List contains only AIP
while performing DDA process.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
SDA Tag List contains AIP.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline DDA succeeded) received at
1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 467
2CC.085.03 SDA Tag List in Dynamic Data Authentication (4)
Test No: 2CC.085.03 - Revision 4.2b - Number of sub cases: 0
Objective: To ensure that the terminal checks that SDA Tag List contains only AIP
while performing Combined DDA/AC process.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Terminal [CDA] supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
SDA Tag List contains AIP.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 3 = '0' (ie Offline Combined DDA/AC
succeeded) contained in Financial Confirmation message or
Batch Data Capture message.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message (this pass criteria apply only if
CDA is requested).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 468
2CC.085.08 SDA Tag List in Dynamic Data Authentication (9)
Test No: 2CC.085.08 - Revision 4.3c - Number of sub cases: 2
Objective: To ensure that the terminal checks that SDA Tag List contains only AIP
while performing Combined DDA/AC process.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online approved.
•
Case 01: SDA Tag List contains AFL, certificate and hash are
calculated with the AFL value.
•
Case 02: SDA Tag List contains AFL and AIP, certificate and
hash are calculated with the AFL and AIP values.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC failed,)
received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 469
2CC.085.09 SDA Tag List in Dynamic Data Authentication (10)
Test No: 2CC.085.09 - Revision 4.3c - Number of sub cases: 2
Objective: To ensure that the terminal checks that SDA Tag List contains only AIP
while performing Combined DDA/AC process.
Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Book Bulletins - Section SB 137 - Bulletin n°137, CDA (First Edition)
Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first Gen
AC.
•
Transaction is online declined.
•
Case 01: SDA Tag List contains AFL, certificate and hash are
calculated with the AFL value.
•
Case 02: SDA Tag List contains AFL and AIP, certificate and
hash are calculated with the AFL and AIP values.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The Terminal shall not request CDA for the 1st and 2nd
GENERATE AC
•
The terminal shall process the transaction until completion, by
requesting an AAC.
•
TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC failed,)
received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 470
2CC.086.00 ICC Dynamic Number Stored
Test No: 2CC.086.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that the terminal stores the ICC Dynamic Number in Tag '9F
4C' during Dynamic Data Authentication process.
Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification
EMV 4.3:
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
CDOL1 requests an ICC Dynamic number (Tag '9F 4C').
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 4 = '0' (ie Offline DDA succeeded) received at
1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
•
Value of Tag '9F 4C' shall be the same as that used in DDA
process (received at 1st GENERATE AC).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 471
2CC.086.01 ICC Dynamic Data
Test No: 2CC.086.01 - Revision 4.2a - Number of sub cases: 9
Objective: To ensure that the terminal support ICC Dynamic Data containing the
ICC Dynamic Number with variable length (2-8 bytes) and optionally
Additional Dynamic Data with a total length LDD ≤ Nic-25, during the
Dynamic Data Authentication process.
Reference Book 2 - Section 6.5.1 - Dynamic Signature Generation
EMV 4.3:
Book 2 - Section 6.5.2 - Dynamic Signature Verification
Terminal [DDA] supported
Configuration:
Conditions:
•
AIP of LT indicates Dynamic Data Authentication is supported
(AIP byte 1 bit 6 = ‘1’).
•
CDOL1 requests an ICC Dynamic Number (Tag '9F 4C').
•
Length NIC = 247 bytes, length NI = 247 bytes, length NCA =
248 bytes
•
Case 01: ICC Dynamic Data used in dynamic signature
computation = ICC Dynamic Number (length = 2) without
Additional Dynamic Data (LDD = 3)
•
Case 02: ICC Dynamic Data used in dynamic signature
computation = ICC Dynamic Number (length = 8) without
Additional Dynamic Data (LDD = 9)
•
Case 03: ICC Dynamic Data used in dynamic signature
computation = ICC Dynamic Number (length = 8) + Additional
Dynamic Data (length = 213 bytes, value = AA…AA), no
padding (LDD = 222)
•
Case 04: ICC Dynamic Data used in dynamic signature
computation = ICC Dynamic Number (length = 2) + Additional
Dynamic Data (length = 219 bytes, value = AA…AA), no
padding (LDD = 222)
•
Case 05: ICC Dynamic Data used in dynamic signature
computation = ICC Dynamic Number (length = 4) + Additional
Dynamic Data (length = 4 bytes, value = 12 34 56 78) (LDD = 9)
•
Case 06: ICC Dynamic Data used in dynamic signature
computation = ICC Dynamic Number (length = 4) + Additional
Dynamic Data (length = 9 bytes, value = 11 22 33 44 55 66 77
8F FF) (LDD = 14)
•
Case 07: ICC Dynamic Data used in dynamic signature
computation = ICC Dynamic Number (length = 8) + Additional
Dynamic Data (length = 8 bytes, value = TLV data with
proprietary tag: 5F 50 81 04 AA BB CC DD) (LDD = 17)
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 472
2CC.086.01 ICC Dynamic Data
•
Case 08: ICC Dynamic Data used in dynamic signature
computation = ICC Dynamic Number (length = 4) + Additional
Dynamic Data (length = 4 bytes, value = 12 34 BB BB) (LDD = 9)
•
Case 09: ICC Dynamic Data used in dynamic signature
computation = ICC Dynamic Number (length = 8) + Additional
Dynamic Data (length = 6 bytes, value = TLV ‘Expiration Date’
data: ‘5F 24 03 40 01 01’(LDD = 15)
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 4 = '0' (ie Offline DDA succeeded) received at
1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 1st GENERATE AC.
•
Value of Tag '9F 4C' shall be the same as that used in DDA
process (received at 1st GENERATE AC).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 473
2CC.086.02 ICC Dynamic Data (2)
Test No: 2CC.086.02 - Revision 4.2a - Number of sub cases: 9
Objective: To ensure that the terminal support ICC Dynamic Data containing the
ICC Dynamic Number with variable length (2-8 bytes) and optionally
Additional Dynamic Data with a total length LDD ≤ Nic-25, during the
Combined Data Authentication process.
Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation
EMV 4.3:
Book 2 - Section 6.6.2 - Dynamic Signature Verification
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that TC is requested at first GenAC
•
LT returns a TC to the first GEN AC.
•
Length NIC = 238 bytes, length NI = 247 bytes, length NCA =
248 bytes.
•
Case 01: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 2) without Additional Dynamic Data (LDD = 32)
•
Case 02: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) without Additional Dynamic Data (LDD = 38)
•
Case 03: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) + Additional Dynamic Data (length = 175 bytes,
value = AA…AA), no padding (LDD = 213)
•
Case 04: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 2) + Additional Dynamic Data (length = 181 bytes,
value = AA…AA), no padding (LDD = 213)
•
Case 05: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 4) + Additional Dynamic Data (length = 4 bytes, value
= 12 34 56 78) (LDD = 38)
•
Case 06: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 4) + Additional Dynamic Data (length = 9 bytes, value
= 11 22 33 44 55 66 77 8F FF) (LDD = 43)
•
Case 07: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) + Additional Dynamic Data (length = 8 bytes, value
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 474
2CC.086.02 ICC Dynamic Data (2)
= TLV data with proprietary tag: 5F 50 81 04 AA BB CC DD)
(LDD = 46)
•
Case 08: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 4) + Additional Dynamic Data (length = 4 bytes, value
= 12 34 BB BB) (LDD = 38)
•
Case 09: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) + Additional Dynamic Data (length = 6 bytes, value
= TLV ‘Expiration Date’ data: ‘5F 24 03 40 01 01’(LDD = 44)
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication
successful) contained in Financial Confirmation message or
Batch Data Capture message
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 475
2CC.086.03 ICC Dynamic Data (3)
Test No: 2CC.086.03 - Revision 43e - Number of sub cases: 9
Objective: To ensure that the terminal support ICC Dynamic Data containing the
ICC Dynamic Number with variable length (2-8 bytes) and optionally
Additional Dynamic Data with a total length LDD ≤ Nic-25, during the
Combined Data Authentication process.
Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation
EMV 4.3:
Book 2 - Section 6.6.2 - Dynamic Signature Verification
Terminal ([Offline/Online capable] OR [Online Only]) AND ([CDA Mode1] OR
Configuration: [CDA Mode2]) supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first
GenAC
•
LT returns an ARQC to the first GEN AC.
•
CDOL2 requests an ICC Dynamic Number (Tag '9F 4C').
•
Length NIC = 238 bytes, length NI = 247 bytes, length NCA =
248 bytes.
•
Case 01: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 2) without Additional Dynamic Data (LDD = 32)
•
Case 02: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) without Additional Dynamic Data (LDD = 38)
•
Case 03: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) + Additional Dynamic Data (length = 175 bytes,
value = AA…AA), no padding (LDD = 213)
•
Case 04: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 2) + Additional Dynamic Data (length = 181 bytes,
value = AA…AA), no padding (LDD = 213)
•
Case 05: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 4) + Additional Dynamic Data (length = 4 bytes, value
= 12 34 56 78) (LDD = 38)
•
Case 06: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 4) + Additional Dynamic Data (length = 9 bytes, value
= 11 22 33 44 55 66 77 8F FF) (LDD = 43)
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 476
2CC.086.03 ICC Dynamic Data (3)
•
Case 07: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) + Additional Dynamic Data (length = 8 bytes, value
= TLV data with proprietary tag: 5F 50 81 04 AA BB CC DD)
(LDD = 46)
•
Case 08: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 4) + Additional Dynamic Data (length = 4 bytes, value
= 12 34 BB BB) (LDD = 38)
•
Case 09: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) + Additional Dynamic Data (length = 6 bytes, value
= TLV ‘Expiration Date’ data: ‘5F 24 03 40 01 01’(LDD = 44)
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The terminal must request a ARQC with CDA at first
GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication
successful) received at 2nd GENERATE AC
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message.
•
Value of Tag '9F 4C' received at 2nd GENERATE AC is the
same as the one used to compute the dynamic signature
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 477
2CC.086.04 ICC Dynamic Data (4)
Test No: 2CC.086.04 - Revision 4.2a - Number of sub cases: 9
Objective: To ensure that the terminal support ICC Dynamic Data containing the
ICC Dynamic Number with variable length (2-8 bytes) and optionally
Additional Dynamic Data with a total length LDD ≤ Nic-25, during the
Combined Data Authentication process.
Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation
EMV 4.3:
Book 2 - Section 6.6.2 - Dynamic Signature Verification
Terminal [CDA] supported AND [Online Only] supported AND [Normal Default
Configuration: Action Code processing] supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first
GenAC and TC at second GenAC
•
LT returns an ARQC to the first GEN AC.
•
Terminal is unable to go online
•
CDOL2 requests an ICC Dynamic Number (Tag '9F 4C').
•
Length NIC = 238 bytes, length NI = 247 bytes, length NCA =
248 bytes.
•
Case 01: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 2) without Additional Dynamic Data (LDD = 32)
•
Case 02: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) without Additional Dynamic Data (LDD = 38)
•
Case 03: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) + Additional Dynamic Data (length = 175 bytes,
value = AA…AA), no padding (LDD = 213)
•
Case 04: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 2) + Additional Dynamic Data (length = 181 bytes,
value = AA…AA), no padding (LDD = 213)
•
Case 05: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 4) + Additional Dynamic Data (length = 4 bytes, value
= 12 34 56 78) (LDD = 38)
•
Case 06: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 478
2CC.086.04 ICC Dynamic Data (4)
(length = 4) + Additional Dynamic Data (length = 9 bytes, value
= 11 22 33 44 55 66 77 8F FF) (LDD = 43)
•
Case 07: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) + Additional Dynamic Data (length = 8 bytes, value
= TLV data with proprietary tag: 5F 50 81 04 AA BB CC DD)
(LDD = 46)
•
Case 08: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 4) + Additional Dynamic Data (length = 4 bytes, value
= 12 34 BB BB) (LDD = 38)
•
Case 09: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) + Additional Dynamic Data (length = 6 bytes, value
= TLV ‘Expiration Date’ data: ‘5F 24 03 40 01 01’(LDD = 44)
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication
successful) contained in Financial Confirmation message or
Batch Data Capture message.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 479
2CC.086.05 ICC Dynamic Data (5)
Test No: 2CC.086.05 - Revision 43e - Number of sub cases: 9
Objective: To ensure that the terminal support ICC Dynamic Data containing the
ICC Dynamic Number with variable length (2-8 bytes) and optionally
Additional Dynamic Data with a total length LDD ≤ Nic-25, during the
Combined Data Authentication process.
Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation
EMV 4.3:
Book 2 - Section 6.6.2 - Dynamic Signature Verification
Terminal ([Offline/Online capable] supported OR [Online Only] supported) AND
Configuration: [CDA Mode4] supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
IAC’s and TAC’s are set so that ARQC is requested at first
GenAC and TC at second GenAC
•
LT returns an ARQC to the first GEN AC.
•
Length NIC = 238 bytes, length NI = 247 bytes, length NCA =
248 bytes.
•
Case 01: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 2) without Additional Dynamic Data (LDD = 32)
•
Case 02: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) without Additional Dynamic Data (LDD = 38)
•
Case 03: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) + Additional Dynamic Data (length = 175 bytes,
value = AA…AA), no padding (LDD = 213)
•
Case 04: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 2) + Additional Dynamic Data (length = 181 bytes,
value = AA…AA), no padding (LDD = 213)
•
Case 05: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 4) + Additional Dynamic Data (length = 4 bytes, value
= 12 34 56 78) (LDD = 38)
•
Case 06: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 4) + Additional Dynamic Data (length = 9 bytes, value
= 11 22 33 44 55 66 77 8F FF) (LDD = 43)
•
Case 07: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) + Additional Dynamic Data (length = 8 bytes, value
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 480
2CC.086.05 ICC Dynamic Data (5)
= TLV data with proprietary tag: 5F 50 81 04 AA BB CC DD)
(LDD = 46)
•
Case 08: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 4) + Additional Dynamic Data (length = 4 bytes, value
= 12 34 BB BB) (LDD = 38)
•
Case 09: ICC Dynamic Data used in dynamic signature
computation = table 19 of Book 2 with ICC Dynamic Number
(length = 8) + Additional Dynamic Data (length = 6 bytes, value
= TLV ‘Expiration Date’ data: ‘5F 24 03 40 01 01’(LDD = 44)
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Dynamic Data Authentication).
Pass Criteria:
•
The terminal shall request TC with CDA at second GenAC
•
The terminal shall process the transaction until completion.
•
TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication not
used) received at 1st GENERATE AC.
•
TVR byte 1, bit 3 = '0' (ie Combined Data Authentication
successful) received at 2nd GENERATE AC
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 481
2CC.091.00 Key used for PIN Encryption/Decryption
Test No: 2CC.091.00 - Revision 10g - Number of sub cases: 2
Objective: To ensure that if the terminal supports offline PIN encryption, it is able to
use a PIN encipherment public key stored in the card to encrypt the PIN
and present it to the card.
Reference Book 2 - Section 7 - Personal Identification Number Encipherment
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT supports Offline PIN encryption.
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Case 01: ICC Public Key present in LT and used for PIN
encipherment.
•
Case 02: PIN Encipherment Public Key is present in LT and
used for PIN encipherment.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Cardholder verification).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
Once deciphered with the corresponding private Key, the LT
shall recover the PIN value present within the PIN block as well
as the unpredictable Number generated by LT.
•
TSI byte 1, bit 7='1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 8='0' (ie Cardholder verification was successful)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 482
2CC.094.00 Random behaviour of PIN Encipherment padding
pattern
Test No: 2CC.094.00 - Revision 4.2a - Number of sub cases: 3
Objective: To ensure that if the terminal supports offline PIN encryption, it is able to
generate a RANDOM padding of N-17 bytes.
Reference Book 2 - Section 7.2 - PIN Encipherment and Verification
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).LT supports Offline PIN encryption.
•
PIN Encipherment Public Key and associated data is present in
LT.
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Case 01: 5 PIN entries using the SAME PIN value in a single
transaction. (LT shall return PIN Try Counter ≥ 5 if requested
and the status value returned by LT on each Verify Command is
’63 Cx’, where ‘x’ is presented from 4 to 0 in a decremental
fashion indicating the number PIN entry attempts left)
•
Case 02: 5 PIN entries using DIFFERENT PIN value each time
in a single transaction. (LT shall return PIN Try Counter ≥ 5 if
requested and the status value returned by LT on each Verify
Command is ’63 Cx’, where x is presented from 4 to 0 in a
decremental fashion indicating the number of PIN entry
attempts left)
•
Case 03: 5 consecutive transactions performed using the SAME
transaction (LT and Terminal) data with the correct PIN.
Action: NA
Procedure: Several transactions are processed with LT (in particular Cardholder
verification).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
Once deciphered with PIN encipherment private Key, the LT
shall recover the PIN value present within the PIN block as well
as the unpredictable Number generated by LT.
•
The tester shall check the "random behaviour" of the padding by
comparing the padding values. The value must appear
unrelated and must show no structure of repetition in the
padding.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 483
2CC.094.00 Random behaviour of PIN Encipherment padding
pattern
•
TSI byte 1, bit 7='1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 484
2CC.095.00 Value of ICC PIN Encryption Public Key Exponent
Test No: 2CC.095.00 - Revision 4.3d - Number of sub cases: 3
Objective: To ensure that the terminal supports value 3 and 2^16 + 1 as exponent
for ICC PIN Encipherment Public Key for PIN encryption.
Reference Book 2 - Section 7.1 - Keys and Certificates
EMV 4.3:
Book Bulletins - Section SB 147 - Bulletin n°147, Clarification on the
Format of Exponent Data Elements (September 2014)
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT supports Offline PIN encryption.
•
PIN Encipherment Public Key and associated data is present in
LT.
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Case 01: Exponent of ICC PIN Encipherment Public Key is 3,
ICC PIN Encryption Key Exponent Length is coded on 1 byte.
•
Case 02: Exponent of ICC PIN Encipherment Public Key is
2^16 + 1, ICC PIN Encryption Key Exponent Length is coded on
3 bytes.
•
Case 03: Exponent of ICC PIN Encryption Key is 3, ICC PIN
Encryption Exponent Length is coded on 3 bytes (the full 3bytes 000003 are included in the hash of the certificate).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Cardholder verification).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
Once deciphered with PIN encipherment private Key, the LT
shall recover the PIN value presented and unpredictable
Number generated by LT.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 485
2CC.095.01 Value of ICC Public Key Exponent
Test No: 2CC.095.01 - Revision 4.3d - Number of sub cases: 3
Objective: To ensure that the terminal supports value 3 and 2^16 + 1 as exponent
for ICC Public Key for PIN encryption.
Reference Book 2 - Section 6.1 - Keys and Certificates
EMV 4.3:
Book Bulletins - Section SB 147 - Bulletin n°147, Clarification on the
Format of Exponent Data Elements (September 2014)
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT supports Offline PIN encryption.
•
PIN Encipherment Public Key and associated data are not
present in LT.
•
ICC Public Key and associated data are present in LT.
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
Case 01: Exponent of ICC Public Key is 3, ICC Public Exponent
Length is coded on 1 byte.
•
Case 02: Exponent of ICC Public Key is 2^16 + 1, ICC Public
Exponent Length is coded on 3 bytes.
•
Case 03: Exponent of ICC Public Key is 3, ICC Public Exponent
Length is coded on 3 bytes (the full 3-bytes 000003 are included
in the hash of the certificate).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Cardholder verification).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
Once deciphered with ICC private Key, the LT shall recover the
PIN value presented and unpredictable Number generated by
LT.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 486
2CC.096.00 ICC PIN Encipherment Public Key recovering: ICC PIN
Encipherment Public Key
Test No: 2CC.096.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports offline PIN encryption, it is able to
retrieve the ICC PIN encipherment Public Key if data in table 20, Book 2
is present in the card.
To ensure that the terminal supports ICC PIN encipherment Public Key
Algorithm value equal to '01' for offline PIN Encryption.
To ensure that the terminal supports Issuer Public Key Algorithm value
equal to '01' for offline PIN Encryption.
To ensure that the terminal supports Hash Algorithm Indicator value
equal to '01' with Offline PIN encryption.
Reference Book 2 - Section 7.1 - Keys and Certificates
EMV 4.3:
Book 2 - Section B2.1 - RSA Algorithm
Book 2 - Section B3.1 - Secure Hash Algorithm (SHA-1)
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT supports Offline PIN encryption.
•
ICC PIN Encipherment Public Key and associated data are
present in LT.
•
ICC PIN Encipherment Public Key Certificate in LT is calculated
with ICC PIN Encipherment Public Key Algorithm value equal to
'01'.
•
Issuer Public Key Certificate in LT is calculated with Issuer
Public Key Algorithm value equal to '01'.
•
Issuer Public Key Certificate in LT is calculated with Hash
Algorithm Indicator value equal to '01'.
•
ICC PIN Encipherment Public Key Certificate in LT is calculated
with Hash Algorithm Indicator value equal to '01'.
•
Data in table 20, Book 2 - Section 7.1 is present in the LT.
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
Action: NA
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 487
2CC.096.00 ICC PIN Encipherment Public Key recovering: ICC PIN
Encipherment Public Key
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Cardholder verification).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
Once deciphered with PIN encipherment private Key, the LT
shall recover the PIN value presented and unpredictable
Number generated by LT.
•
TVR byte 3, bit 8 = '0' (ie Cardholder verification succeeded)
received at 1st GENERATE AC.
•
TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 488
2CC.097.00 ICC PIN Encipherment Public Key recovery: ICC Public
Key
Test No: 2CC.097.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports offline PIN encryption, it is able to
retrieve the ICC Public Key if data in table 20, Book 2 is not present in
the card, but all data elements in table 8, Book 2, are present in the ICC.
To ensure that the terminal supports ICC Public Key Algorithm value
equal to '01' for offline PIN Encryption.
o ensure that the terminal supports Issuer Public Key Algorithm value
equal to '01' for offline PIN Encryption.
To ensure that the terminal supports Hash Algorithm Indicator value
equal to '01' with Offline PIN Encryption.
Reference Book 2 - Section 7.1 - Keys and Certificates
EMV 4.3:
Book 2 - Section B2.1 - RSA Algorithm
Book 2 - Section B3.1 - Secure Hash Algorithm (SHA-1)
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT supports Offline PIN encryption.
•
ICC Public Key and associated data are present in LT.
•
ICC Public Key Certificate in LT is calculated with ICC Public
Key Algorithm value equal to '01'.
•
Issuer Public Key Certificate in LT is calculated with Issuer
Public Key Algorithm value equal to '01'.
•
Issuer Public Key Certificate in LT is calculated with Hash
Algorithm Indicator value equal to '01'.
•
ICC Public Key Certificate in LT is calculated with Hash
Algorithm Indicator value equal to '01'.
•
Data in table 20, Book 2 is not present in the LT, but all data
elements in table 11, Book 2 are present in the LT.
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Cardholder verification).
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 489
2CC.097.00 ICC PIN Encipherment Public Key recovery: ICC Public
Key
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
Once deciphered with ICC private Key, the LT shall recover the
PIN value presented within the PIN block and the unpredictable
Number generated by LT.
•
TSI byte 1, bit 7='1' (ie Cardholder verification was performed)
received at 1st GENERATE AC.
•
TVR byte 3, bit 8='0' (ie Cardholder verification was successful)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 490
2CC.098.00 ICC PIN Encipherment Public Key recovering failed
Test No: 2CC.098.00 - Revision 43e - Number of sub cases: 0
Objective: To ensure that if the terminal supports offline PIN encryption, and if it is
not able to retrieve the ICC PIN encipherment Public Key or ICC Public
Key, the terminal fails the PIN encryption.
Reference Book 2 - Section 7.1 - Keys and Certificates
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT supports Offline PIN encryption.
•
PIN Encipherment Public Key Certificate stored in LT is not
valid.
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Cardholder verification).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification was not
successful) received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 491
2CC.099.00 PIN Entry
Test No: 2CC.099.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports offline PIN encryption, it asks the
cardholder to enter his PIN on the PIN Pad, and encrypts it before
presentation to the card.
Reference Book 2 - Section 7.2 - PIN Encipherment and Verification
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT supports Offline PIN encryption.
•
ICC Public Key and associated data are present in LT.
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
Action: Cardholder presents a valid PIN in Clear.
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Cardholder verification).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The terminal (PIN Pad) shall request PIN entry.
•
Once deciphered with PIN encipherment private Key, the LT
shall recover the PIN Block on 8 bytes and the PIN entered in
plaintext format.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 492
2CC.100.00 Unpredictable Number
Test No: 2CC.100.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports offline PIN encryption, it issues a
GET CHALLENGE command to obtain an unpredictable Number from
the card.
Reference Book 2 - Section 7.2 - PIN Encipherment and Verification
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT supports Offline PIN encryption.
•
ICC Public Key and associated data are present in LT.
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Cardholder verification).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The LT shall receive a GET CHALLENGE command from the
terminal.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 493
2CC.100.01 Unpredictable Number (2)
Test No: 2CC.100.01 - Revision 43e - Number of sub cases: 0
Objective: To ensure that if the terminal supports offline PIN encryption, it issues a
GET CHALLENGE command. If the response is anything other than an
8-byte data block, the terminal shall consider PIN encryption as failed.
Reference Book 2 - Section 7.2 - PIN Encipherment and Verification
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
AIP of LT indicates Cardholder Verification is supported (AIP
byte 1 bit 5 = ‘1’).
•
LT supports Offline PIN encryption.
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
•
LT response to the Get Challenge command is 6 byte of data
with status value = 90 00.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Cardholder verification).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 3, bit 8 = '1' (ie Cardholder verification was not
successful) received at 1st GENERATE AC.
•
TVR byte 3, bit 4 = '0' (ie PIN entry required, PIN pad present,
but PIN was not entered is not used) received at 1st
GENERATE AC.
•
TVR byte , bit 5 = '0' (ie PIN entry required and PIN pad present
or working) received at 1st GENERATE AC.
•
TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received
at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 494
2CC.102.00 VERIFY
Test No: 2CC.102.00 - Revision 10g - Number of sub cases: 0
Objective: To ensure that if the terminal supports offline PIN encryption, it issues a
VERIFY command containing the Enciphered PIN Data.
Reference Book 2 - Section 7.2 - PIN Encipherment and Verification
EMV 4.3:
Terminal [Offline Enciphered PIN] supported
Configuration:
Conditions:
•
LT supports Offline PIN encryption.
•
ICC Public Key and associated data are present in LT.
•
CVM requires 'Enciphered PIN verification Offline' (04 00).
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Cardholder verification).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
The LT shall receive a VERIFY command from the terminal with
Enciphered PIN Data in the data field.
•
The plaintext recovered data shall comply with the format
specified in table 21 Book 2.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 495
2CC.119.00 PDOL in Enhanced Combined DDA/AC
Test No: 2CC.119.00 - Revision 13a - Number of sub cases: 3
Objective: To ensure that the terminal can use PDOL in Enhanced Combined
DDA/AC.
Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [CDA] supported AND ([Offline Only] supported OR [Offline/Online
Configuration: capable] supported)
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
TAC and IAC are set so that a TC is requested at first
GENERATE AC.
•
Case 01: PDOL is present in LT.
•
Case 02: PDOL is empty in LT.
•
Case 03: no PDOL in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC.
•
TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation
succeeded) contained in Financial Confirmation message or
Batch Data Capture message.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 496
2CC.119.01 PDOL in Enhanced Combined DDA/AC
Test No: 2CC.119.01 - Revision 43e - Number of sub cases: 3
Objective: To ensure that the terminal can use PDOL in Enhanced Combined
DDA/AC.
Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal ([Offline/Online capable] OR [Online Only]) AND ([CDA Mode1] OR
Configuration: [CDA Mode2] OR [CDA Mode4]) supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
TAC and IAC are set so that an ARQC is requested at first
GENERATE AC and TC at second GENERATE AC.
•
Case 01: PDOL is present in LT.
•
Case 02: PDOL is empty in LT.
•
Case 03: no PDOL in LT.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall process the transaction until completion, by
requesting a TC or an AAC.
•
TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation
succeeded) contained in Financial Confirmation message or
Batch Data Capture message.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 497
2CC.122.00 Response to GENERATE AC when responding AAC is
in format 1 or 2
Test No: 2CC.122.00 - Revision 13 - Number of sub cases: 2
Objective: To ensure that the terminal can use the ICC response format 1 or 2 (as
specified in book 3 part I) in Enhanced Combined DDA/AC, when LT
responds AAC to GENERATE AC command.
To ensure that the terminal sets Enhanced Combined DDA/AC failed if
LT responds AAC.
Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
TAC and IAC are set so that a TC is requested at first
GENERATE AC.
•
Case 01: LT responds with AAC to first GENERATE AC in
format 1.
•
Case 02: LT responds with AAC to first GENERATE AC in
format 2.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall process the transactions to completion.
•
The transaction shall be declined.
•
This pass criteria only applies if the terminal has the ability to
store declined transactions: TSI byte 1, bit 8 = '1' (ie Offline
Data Authentication was performed) shall be set.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 498
2CC.122.01 Response to GENERATE AC when responding AAC is
in format 1 or 2 (2)
Test No: 2CC.122.01 - Revision 13 - Number of sub cases: 2
Objective: To ensure that the terminal can use the ICC response format 1 or 2 (as
specified in book 3 part I) in Enhanced Combined DDA/AC, when LT
responds AAC to GENERATE AC command.
Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
TAC and IAC are set so that a TC is requested at first
GENERATE AC.
•
LT responds with ARQC at the first GENERATE AC
•
Case 01: LT responds with AAC at the second GENERATE AC
in format 1.
•
Case 02: LT responds with AAC at the second GENERATE AC
in format 2
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall process the transactions to completion.
•
The transaction shall be declined.
•
This pass criteria only applies if the terminal has the ability to
store declined transactions: TSI byte 1, bit 8 = '1' (ie Offline
Data Authentication was performed) shall be set.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 499
2CC.122.02 ICC responds with AAR
Test No: 2CC.122.02 - Revision 13 - Number of sub cases: 0
Objective: To ensure that the terminal treats the AAR as a logical error even in CDA
context and terminates the transaction (case where dynamic signature
is not present).
Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification
EMV 4.3:
Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005)
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
TAC and IAC are set so that a TC is requested at first
GENERATE AC.
•
LT responds AAR at the first GENERATE AC without dynamic
signature.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall terminate the transaction
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 500
2CC.122.03 ICC responds with AAR (2)
Test No: 2CC.122.03 - Revision 13 - Number of sub cases: 0
Objective: To ensure that the terminal treats an AAR as a logical error even in CDA
context and terminates the transaction (case where dynamic signature
is present).
Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification
EMV 4.3:
Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005)
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
TAC and IAC are set so that a TC is requested at first
GENERATE AC.
•
LT responds AAR at the first generate AC with dynamic
signature.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall terminate the transaction
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 501
2CC.122.04 Response to GENERATE AC when responding AAC is
in format 1 or 2 (3)
Test No: 2CC.122.04 - Revision 43e - Number of sub cases: 2
Objective: To ensure that the terminal can use the ICC response format 1 or 2 (as
specified in book 3 part I) in Enhanced Combined DDA/AC, when LT
responds AAC to GENERATE AC command.
Reference Book 2 – Section 6.6.1 - Dynamic Signature Generation
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [Online Only] AND ([CDA Mode1] OR [CDA Mode2]) supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
TAC and IAC are set so that an ARQC is requested at first
GENERATE AC.
•
Case 01: LT responds with AAC to first GENERATE AC in
format 1.
•
Case 02: LT responds with AAC to first GENERATE AC in
format 2.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall process the transactions to completion.
•
The transaction shall be declined.
•
This pass criteria only applies if the terminal has the ability to
store declined transactions: TSI byte 1, bit 8 = '1' (ie Offline
Data Authentication was performed) shall be set.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 502
2CC.122.05 Response to GENERATE AC when responding AAC is
in format 1 or 2 (4)
Test No: 2CC.122.05 - Revision 43e - Number of sub cases: 2
Objective: To ensure that the terminal can use the ICC response format 1 or 2 (as
specified in book 3 part I) in Enhanced Combined DDA/AC, when LT
responds AAC to GENERATE AC command.
Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [Online Only] AND ([CDA Mode1] OR [CDA Mode2]) supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
TAC and IAC are set so that an ARQC is requested at first
GENERATE AC.
•
LT responds with ARQC at the first GENERATE AC
•
Case 01: LT responds with AAC at the second GENERATE AC
in format 1.
•
Case 02: LT responds with AAC at the second GENERATE AC
in format 2
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall process the transactions to completion.
•
The transaction shall be declined.
•
This pass criteria only applies if the terminal has the ability to
store declined transactions: TSI byte 1, bit 8 = '1' (ie Offline
Data Authentication was performed) shall be set.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 503
2CC.122.06 ICC responds with AAR (3)
Test No: 2CC.122.06 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal treats the AAR as a logical error even in CDA
context and terminates the transaction (case where dynamic signature
is not present).
Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification
EMV 4.3:
Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005)
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [Online Only] AND ([CDA Mode1] OR [CDA Mode2]) supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
TAC and IAC are set so that an ARQC is requested at first
GENERATE AC.
•
LT responds AAR at the first GENERATE AC without dynamic
signature.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall terminate the transaction
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 504
2CC.122.07 ICC responds with AAR (4)
Test No: 2CC.122.07 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal treats an AAR as a logical error even in CDA
context and terminates the transaction (case where dynamic signature
is present).
Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification
EMV 4.3:
Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005)
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [Online Only] AND ([CDA Mode1] OR [CDA Mode2]) supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
TAC and IAC are set so that an ARQC is requested at first
GENERATE AC.
•
LT responds AAR at the first generate AC with dynamic
signature.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall terminate the transaction
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 505
2CC.122.08 Response to GENERATE AC when responding AAC is
in format 1 or 2 (5)
Test No: 2CC.122.08 - Revision 43e - Number of sub cases: 2
Objective: To ensure that the terminal can use the ICC response format 1 or 2 (as
specified in book 3 part I) in Enhanced Combined DDA/AC, when LT
responds AAC to GENERATE AC command.
Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [Online Only] AND [Normal Default Action Code Processing] AND ([CDA
Configuration: Mode3] OR [CDA Mode4]) supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
TAC and IAC are set so that an ARQC is requested at first
GENERATE AC.
•
LT responds with ARQC at the first GENERATE AC
•
Terminal is unable to go online
•
Case 01: LT responds with AAC at the second GENERATE AC
in format 1.
•
Case 02: LT responds with AAC at the second GENERATE AC
in format 2
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall process the transactions to completion.
•
The transaction shall be declined.
•
This pass criteria only applies if the terminal has the ability to
store declined transactions: TSI byte 1, bit 8 = '1' (ie Offline
Data Authentication was performed) shall be set contained in
Financial Confirmation message or Batch Data Capture
message.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 506
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 507
2CC.123.00 Signed Dynamic Application Data Length
Test No: 2CC.123.00 - Revision 15 - Number of sub cases: 2
Objective: To ensure that the terminal compares the Signed Dynamic Application
Data length with the ICC Public Key length for Combined DDA/AC Data
Authentication.
Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Length of Signed Dynamic Application Data is different from the
ICC Public Key length.
•
TAC and IAC are set so that a TC is requested at first
GENERATE AC.
•
Case 01: LT responds to the first GENERATE AC with a TC.
•
Case 02: LT responds to the first GENERATE AC with an
ARQC.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
Case 01: The terminal shall decline the transaction without
performing a second GENERATE AC
•
Case 02: The terminal shall complete the transaction
processing by performing an immediate second GENERATE
AC command requesting an AAC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message (this pass criteria apply only if the
terminal has the capability to store declined transaction).
•
TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed)
contained in Financial Confirmation message or Batch Data
Capture message (this pass criteria apply only if the terminal
has the capability to store declined transaction).
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 508
2CC.123.00 Signed Dynamic Application Data Length
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 509
2CC.123.01 Signed Dynamic Application Data Length (2)
Test No: 2CC.123.01 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal compares the Signed Dynamic Application
Data length with the ICC Public Key length for Combined DDA/AC Data
Authentication.
Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [Online Only] AND ([CDA Mode1] OR [CDA Mode2]) supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Length of Signed Dynamic Application Data is different from the
ICC Public Key length.
•
TAC and IAC are set so that an ARQC is requested at first
GENERATE AC.
•
LT responds to the first GENERATE AC with an ARQC.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall complete the transaction processing by
performing an immediate second GENERATE AC command
requesting an AAC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 2nd GENERATE AC
•
TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed)
received at 2nd GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 510
2CC.123.02 Signed Dynamic Application Data Length (3)
Test No: 2CC.123.02 - Revision 16 - Number of sub cases: 0
Objective: To ensure that the terminal compares the Signed Dynamic Application
Data length with the ICC Public Key length for Combined DDA/AC Data
Authentication.
Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [CDA] supported AND ([Online Only] supported AND [Normal Default
Configuration: Action Code processing]) supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Length of Signed Dynamic Application Data is different from the
ICC Public Key length in the second GENERATE AC.
•
TAC and IAC are set so that an ARQC is requested at first
GENERATE AC and TC at Second GENERATE AC.
•
LT responds to the first GENERATE AC with an ARQC.
•
Terminal is unable to go online
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall decline the transaction.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in the Financial Confirmation message or
Batch Data Capture message (this pass criteria applies only if
the terminal has the capability to store declined transactions).
•
TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed)
contained in the Financial Confirmation message or Batch Data
Capture message (this pass criteria applies only if the terminal
has the capability to store declined transactions).
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 511
2CC.123.03 Signed Dynamic Application Data Length (4)
Test No: 2CC.123.03 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal compares the Signed Dynamic Application
Data length with the ICC Public Key length for Combined DDA/AC Data
Authentication.
Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [Online Only] AND ([CDA Mode1] OR [CDA Mode4]) supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Length of Signed Dynamic Application Data is different from the
ICC Public Key length in the second GENERATE AC.
•
TAC and IAC are set so that an ARQC is requested at first
GENERATE AC and TC at Second GENERATE AC.
•
LT responds to the first GENERATE AC with an ARQC.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall decline the transaction.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in the Financial Confirmation message or
Batch Data Capture message (this pass criteria applies only if
the terminal has the capability to store declined transactions).
•
TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed)
contained in the Financial Confirmation message or Batch Data
Capture message (this pass criteria applies only if the terminal
has the capability to store declined transactions)..
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 512
2CC.124.00 Recovered Data Trailer not equal to BC
Test No: 2CC.124.00 - Revision 15 - Number of sub cases: 2
Objective: To ensure that the terminal checks the recovered Data Trailer for
Combined DDA/AC Data Authentication.
Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Data Trailer is different from BC.
•
TAC and IAC are set so that a TC is requested at first
GENERATE AC.
•
Case 01: LT responds to the first GENERATE AC with a TC.
•
Case 02: LT responds to the first GENERATE AC with an
ARQC.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
Case 01: The terminal shall decline the transaction without
performing a second GENERATE AC
•
Case 02: The terminal shall complete the transaction
processing by performing an immediate second GENERATE
AC command requesting an AAC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message (this pass criteria apply only if the
terminal has the capability to store declined transaction).
•
TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed)
contained in Financial Confirmation message or Batch Data
Capture message (this pass criteria apply only if the terminal
has the capability to store declined transaction).
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC.
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 513
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 514
2CC.124.01 Recovered Data Trailer not equal to BC (2)
Test No: 2CC.124.01 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal checks the recovered Data Trailer for
Combined DDA/AC Data Authentication.
Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [Online Only] AND ([CDA Mode1] OR [CDA Mode2]) supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Data Trailer is different from BC.
•
TAC and IAC are set so that an ARQC is requested at first
GENERATE AC.
•
LT responds to the first GENERATE AC with an ARQC.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
The terminal shall complete the transaction processing by
performing an immediate second GENERATE AC command
requesting an AAC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) received at 2nd GENERATE AC.
•
TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed)
received at 2nd GENERATE AC.
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 515
2CC.125.00 Recovered Data Header not equal to 6A
Test No: 2CC.125.00 - Revision 15 - Number of sub cases: 2
Objective: To ensure that the terminal checks the recovered data header for
Combined DDA/AC Data Authentication.
Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable])
Configuration: supported
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Data header is different from 6A.
•
TAC and IAC are set so that a TC is requested at first
GENERATE AC.
•
Case 01: LT responds to the first GENERATE AC with a TC.
•
Case 02: LT responds to the first GENERATE AC with an
ARQC.
Action: NA
Procedure: Application in LT is selected and transaction is processed with LT (in
particular Enhanced Combined DDA/AC).
Pass Criteria:
•
Case 01: The terminal shall decline the transaction without
performing a second GENERATE AC
•
Case 02: The terminal shall complete the transaction
processing by performing an immediate second GENERATE
AC command requesting an AAC.
•
TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was
performed) contained in Financial Confirmation message or
Batch Data Capture message (this pass criteria apply only if the
terminal has the capability to store declined transaction).
•
TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed)
contained in Financial Confirmation message or Batch Data
Capture message (this pass criteria apply only if the terminal
has the capability to store declined transaction).
•
TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)
received at 1st GENERATE AC.
•
TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not
used) received at 1st GENERATE AC
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 516
© 2017 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 Terminal Type Approval
Level 2 Test Cases v4.3f
Page 517
2CC.125.01 Recovered Data Header not equal to 6A (2)
Test No: 2CC.125.01 - Revision 43e - Number of sub cases: 0
Objective: To ensure that the terminal checks the recovered data header for
Combined DDA/AC Data Authentication.
Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification
EMV 4.3:
Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal
behaviour (Sept-2006)
Terminal [Online Only] AND ([CDA Mode1] OR [CDA Mode2]) supported
Configuration:
Conditions:
•
AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = ‘1’).
•
Data header is different from 6A.
•
TAC and IAC are set so that an ARQC is requested at first
GENERATE AC.
•
LT responds to the first GENERATE AC with an ARQC.
Action: NA
Procedure: A