L2 Test Cases v41e

EMVCo Type Approval - Terminal Level 2 - Test Cases

EMVCo Type Approval Terminal Level 2 Test Cases __________________________________________________

Version 4.1.e May 1st, 2008

Copyright © 2008 EMVCo, LLC. All Rights Reserved. Page 1


Legal Notice This document summarizes EMVCo’s present plans for type approval testing services and policies and is subject to change by EMVCo at any time without notice to any party. Neither this document nor any other document or communication creates any binding obligations upon EMVCo or any third party regarding testing services or EMVCo approval, which obligations will exist, if at all, pursuant to separate written agreements executed by EMVCo and such third parties. In the absence of a written binding agreement pursuant to which EMVCo has agreed to perform testing services for a vendor or to permit a third party to act as a test laboratory, no vendor, test laboratory nor any other third party should detrimentally rely on this document, nor shall EMVCo be liable for any such reliance.

No vendor, test laboratory nor other third party may refer to a product, service or facility as EMVCo approved, in form or in substance, nor otherwise state or imply that EMVCo (or any agent of EMVCo) has in whole or part approved a vendor, test laboratory or other third party or its products, services, or facilities, except to the extent and subject to the terms, conditions and restrictions expressly set forth in a written agreement with EMVCo, or in an approval letter issued by EMVCo. All other references to EMVCo approval are strictly and actively prohibited by EMVCo.

Under no circumstances should EMVCo type approval, when granted, be construed to imply any endorsement or warranty regarding the functionality, quality, or performance of any particular product or service, and no party shall state or imply anything to the contrary. EMVCo specifically disclaims any and all representations and warranties with respect to products that have received approval and to the type approval process generally, including, without limitation, any implied warranties of merchantability, fitness for purpose or noninfringement. All rights and remedies relating to products and services that have received EMVCo type approval are provided solely by the parties selling or otherwise providing such products or services, and not by EMVCo, and EMVCo accepts no liability whatsoever in connection with such products and services. Unless otherwise agreed in writing by EMVCo, this document and matter contained herein, including all products and services contemplated by this document are provided on an “as-is” basis, “with all faults” and with no warranties whatsoever, and EMVCo specifically disclaims any implied warranties of merchantability, fitness for purpose, or noninfringement.

Copyright ©2008 EMVCo, LLC. All rights reserved

Page 2


Version History

Version

Date

Revision Description

1.0

August 31, 2000

Initial Publication

2.0

January 31, 2002

3.5

December, 2004

4.1.a

January 4; 2006

4.1.b 4.1.c 4.1.c

September 19, 2006 April 30, 2007 August 9, 2007

4.1.d

December 1, 2007

4.1.e

May 1st, 2008

Test conformance with EMV2000 ICC Specification for Payment Systems Version 4.0 dated December, 2000. Test conformance with EMV2000 ICC Specification for Payment Systems Version 4.0 dated December, 2000, Application notes and Specifications update bulletins, Correction of previous version and latest Application notes and Specifications update bulletins incorporated TA Bulletins 42 to 46 incorporated TA Bulletins 51, 52, 53, 59, 60 and 61 incorporated TA 42 was missing from the previous edition of the test plan, and this update reintroduces TA 42. TA Bulletins 67 3rd edition, 68 1st edition, 69 2nd edition, 70 2nd edition and 71 2nd edition incorporated TA Bulletin 76, 2nd Edition TA Bulletin xx, 1st Edition

New versioning policy of the present document: Current version is 4.1.e, where 4.1 follows the current EMV ICC Specification revision number, and where .e is incremented (c, d, e,…) for each new revision of the present document issued to correct any issues, or to incorporate Type Approval Bulletins.



Table of Contents SCOPE ......................................................................................................................................................... 31 REFERENCED DOCUMENTS ................................................................................................................ 32 CHANGES WITH PREVIOUS VERSION.............................................................................................. 33 ABBREVIATIONS AND NOTATIONS................................................................................................... 34 GLOBAL GLOSSARY............................................................................................................................... 36 TEST SETTINGS ....................................................................................................................................... 46 DEFAULT VALUES SETTING ............................................................................................................................ 46 CRYPTOGRAM TYPE REQUESTED BY TERMINAL ............................................................................................. 50 RECOMMENDED TEST SCRIPT COMMANDS .................................................................................................... 50 TEST STRUCTURE................................................................................................................................... 52 TEST NUMBERING AND ASSOCIATED SUB CASES ............................................................................................. 52 TEST CATEGORY ............................................................................................................................................ 52 TEST CASES............................................................................................................................................... 55 DATA ELEMENT AND COMMAND ................................................................................................................... 56 2CA.001.01 Data elements Storage........................................................................................................ 57 2CA.001.02 Data elements Storage........................................................................................................ 58 2CA.001.03 Data elements Storage........................................................................................................ 59 2CA.001.04 Coding of Length in TLV .................................................................................................... 60 2CA.002.00 Mapping of data objects into records................................................................................. 61 2CA.004.00 Coding of a Payment System Directory: SFI Range........................................................... 62 2CA.004.01 Coding of a Payment System Directory: SFI Range (2)..................................................... 64 2CA.013.00 Processing DOLs: unknown tag ......................................................................................... 66 2CA.013.01 Processing DOLs: unknown tag (2) ................................................................................... 67 2CA.014.00 Processing DOLs: constructed tag..................................................................................... 68 2CA.014.01 Processing DOLs: constructed tag (2) ............................................................................... 69 2CA.015.00 Processing DOLs: data absent from ICC........................................................................... 70 2CA.015.01 Processing DOLs: data absent from ICC (2) ..................................................................... 71 2CA.016.00 Processing DOLs: shorter data object length, numeric format.......................................... 72 2CA.016.01 Processing DOLs: shorter data object length, numeric format (2) .................................... 73 2CA.017.00 Processing DOLs: shorter data object length, other format .............................................. 74 2CA.017.01 Processing DOLs: shorter data object length, other format (2)......................................... 75 2CA.018.00 Processing DOLs: longer data object length, numeric format........................................... 76 2CA.018.01 Processing DOLs: longer data object length, numeric format (2) ..................................... 77 2CA.019.00 Processing DOLs: longer data object length, compressed numeric format....................... 78 2CA.019.01 Processing DOLs: longer data object length, compressed numeric format (2) ................. 79 2CA.020.00 Processing DOLs: longer data object length, other format ............................................... 80 2CA.020.01 Processing DOLs: longer data object length, other format (2).......................................... 81 2CA.021.00 Processing DOLs: data not applicable............................................................................... 82 2CA.021.01 Processing DOLs: data not applicable (2)......................................................................... 83 2CA.022.00 Data Object List consistency (1)......................................................................................... 84 2CA.023.00 Data Object List consistency (2)......................................................................................... 86


Page 4

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CA.025.00 Normal Processing for EXTERNAL AUTHENTICATE - Functions specified in the AIP: Issuer Authentication ................................................................................................................................ 88 2CA.025.01 ARC checking for contrary response when declining......................................................... 90 2CA.025.02 ARC checking for contrary response when approving ....................................................... 92 2CA.025.03 ARC checking for contrary response when issuing a referral............................................ 94 2CA.026.00 Status Word Processing for EXTERNAL AUTHENTICATE .............................................. 96 2CA.027.00 Normal Processing for GENERATE AC............................................................................. 98 2CA.028.00 Normal Processing for GET CHALLENGE ....................................................................... 99 2CA.029.04 Failed Processing for GET DATA.................................................................................... 100 2CA.029.05 Failed Processing for GET DATA (1) .............................................................................. 101 2CA.029.06 Failed Processing for GET DATA (2) .............................................................................. 102 2CA.029.07 Failed Processing for GET DATA (3) .............................................................................. 103 2CA.029.08 Status Word Processing for GET DATA........................................................................... 104 2CA.029.09 Status Word Processing for GET DATA (2) ..................................................................... 106 2CA.029.10 Status Word Processing for GET DATA (3) ..................................................................... 108 2CA.029.11 Status Word Processing for GET DATA (4) ..................................................................... 110 2CA.030.00 Normal Processing for GET PROCESSING OPTIONS ................................................... 112 2CA.030.05 Failed Processing for GET PROCESSING OPTIONS..................................................... 113 2CA.030.06 Failed Processing for GET PROCESSING OPTIONS (2) ............................................... 115 2CA.031.00 Normal Processing for Internal Authenticate................................................................... 117 2CA.031.01 Status Word Processing for Internal Authenticate ........................................................... 118 2CA.032.00 Normal Processing for READ RECORD.......................................................................... 120 2CA.033.00 Normal Processing for Select ........................................................................................... 121 2CA.033.01 Failed Processing for Select ADF .................................................................................... 122 2CA.033.02 Status Word Processing for SELECT PSE ....................................................................... 123 2CA.033.04 Failed Processing for Select ADF (2)............................................................................... 125 2CA.034.02 Failed Processing for VERIFY ......................................................................................... 126 2CA.034.05 Failed Processing for VERIFY (2).................................................................................... 128 2CA.034.06 Failed Processing for VERIFY (3).................................................................................... 130 2CA.034.07 Failed Processing for VERIFY (4).................................................................................... 132 2CA.035.00 Status Word Processing for GENERATE AC ................................................................... 133 2CA.036.00 Status Word Processing for GET CHALLENGE.............................................................. 135 2CA.037.00 Status Word Processing for GET PROCESSING OPTIONS............................................ 137 2CA.039.00 Status Word Processing for READ RECORD .................................................................. 139 2CA.040.00 Status Word Processing for VERIFY................................................................................ 141 2CA.041.00 Coding of Bits and Bytes RFU.......................................................................................... 143 2CA.041.01 Coding of Bits and Bytes RFU (2) .................................................................................... 145 2CA.041.02 Coding of Bits and Bytes RFU (3) .................................................................................... 146 2CA.041.03 Coding of Bits and Bytes RFU (4) .................................................................................... 147 2CA.041.04 Coding of Bits and Bytes RFU (5) (Implied) .................................................................... 148 2CA.054.00 Syntax of GENERATE AC returned Data Field (Format 1)............................................. 149 2CA.055.00 Syntax of GENERATE AC returned Data Field (Format 2)............................................. 150 2CA.056.00 Proprietary Data Object transmitted in Response to GENERATE AC: Format 2 ........... 151 2CA.058.00 Application Transaction Counter ..................................................................................... 152 2CA.059.00 Application Cryptogram ................................................................................................... 153 2CA.060.00 Issuer Application Data.................................................................................................... 154 2CA.061.00 Cryptogram Information Data: AAC................................................................................ 155 2CA.062.00 Cryptogram Information Data: TC .................................................................................. 156 2CA.062.01 Cryptogram Information Data: TC (2)............................................................................. 157 2CA.063.00 Cryptogram Information Data: ARQC............................................................................. 158 2CA.064.00 Cryptogram Information Data: AAR ................................................................................ 159 2CA.067.00 Cryptogram Information Data: PIN try limit exceeded.................................................... 160 2CA.068.00 Advice requested in the CID and unable to go online ...................................................... 161


EMVCo Type Approval - Terminal Level 2 - Test Cases 2CA.069.00 Advice requested in the CID and advice is unsupported .................................................. 162 2CA.070.00 Syntax of GET DATA returned Data Field (ATC)............................................................ 163 2CA.071.00 Syntax of GET DATA returned Data Field (LOATC)....................................................... 165 2CA.072.00 Syntax of GET DATA returned Data Field (PIN try limit) - Terminal Behaviour When PIN Try Counter Equals 0.............................................................................................................................. 167 2CA.072.01 Syntax of GET DATA returned Data Field (PIN try limit) - Terminal Behaviour When PIN Try Counter Equals 0 (2)........................................................................................................................ 169 2CA.074.00 Syntax of GET PROCESSING OPTIONS Data Field (PDOL) ........................................ 171 2CA.075.00 Syntax of GET PROCESSING OPTIONS Data Field (no PDOL) ................................... 172 2CA.076.00 Syntax of GET PROCESSING OPTIONS Data Field: PDOL empty (implied)................ 173 2CA.077.00 Syntax of GPO returned Data Field: Format 1................................................................ 174 2CA.078.00 Syntax of GPO returned Data Field: Format 2................................................................ 175 2CA.082.00 Syntax of INTERNAL AUTHENTICATE Data Field ........................................................ 176 2CA.083.00 Syntax of INTERNAL AUTHENTICATE returned Data Field: Format 1 ........................ 177 2CA.084.00 Syntax of INTERNAL AUTHENTICATE returned Data Field: Format 2 ........................ 179 2CA.089.00 Syntax of READ RECORD returned Data Field .............................................................. 181 2CA.092.00 Syntax of SELECT Data Field .......................................................................................... 182 2CA.093.00 Syntax of SELECT PSE returned Data Field.................................................................... 183 2CA.094.00 Syntax of SELECT PSE returned Data Field: no optional data....................................... 184 2CA.095.00 Syntax of SELECT DDF returned Data Field .................................................................. 185 2CA.096.00 Syntax of SELECT DDF returned Data Field: optional data (implied)........................... 186 2CA.097.00 Syntax of SELECT ADF returned Data Field................................................................... 187 2CA.098.00 Syntax of SELECT ADF returned Data Field: optional data ........................................... 188 2CA.099.00 Response to Proprietary Data in FCI from a SELECT ADF ........................................... 189 2CA.099.01 Response to Proprietary Data in FCI from a SELECT PSE ............................................ 190 2CA.099.02 Response to Proprietary Data in FCI from a SELECT DDF ........................................... 192 2CA.100.01 Additional data object facilitating domestic processing in selection with PSE................ 193 2CA.100.02 Additional data object facilitating domestic processing in DDF selection ...................... 194 2CA.103.00 Syntax of VERIFY Data Field for option plaintext offline PIN ........................................ 195 2CA.103.01 Syntax of VERIFY Data Field for Enciphered offline PIN ............................................... 197 2CA.108.00 Syntax of GET CHALLENGE returned Data Field .......................................................... 199 APPLICATION SELECTION ............................................................................................................................. 200 2CB.002.00 Definition of PSE .............................................................................................................. 201 2CB.004.00 Definition of a Record in Payment Systems Directory ..................................................... 202 2CB.005.00 Definition of Directory Entry Format............................................................................... 203 2CB.007.00 Terminal's List of Supported Applications ....................................................................... 204 2CB.010.00 Matching AIDS: « same AID » criteria supported ........................................................... 205 2CB.010.01 Matching AIDS: « same AID » criteria supported (2)...................................................... 206 2CB.011.00 Matching AIDs: « AID beginning with Terminal AID » criteria supported..................... 207 2CB.011.01 Matching AIDs: « AID beginning with Terminal AID » criteria supported (2) ............... 208 2CB.012.00 Selection Using the Payment Systems Directory: SELECT PSE ...................................... 209 2CB.013.00 Selection Using the Payment Systems Directory: Card Blocked or Command Not Supported................................................................................................................................................ 210 2CB.016.00 Indicating end of record ................................................................................................... 211 2CB.016.01 Indicating end of record (2).............................................................................................. 212 2CB.017.00 Directory entry does not exist........................................................................................... 213 2CB.017.01 Directory entry does not exist (2) ..................................................................................... 214 2CB.017.02 Directory entry does not exist (3) ..................................................................................... 215 2CB.018.00 Directory entry processing ............................................................................................... 217 2CB.018.01 Directory entry processing (2).......................................................................................... 218 2CB.019.01 Candidate list with exact match (2) .................................................................................. 219 2CB.019.02 Candidate list with exact match (3) .................................................................................. 221 2CB.019.04 Candidate list with partial match (2)................................................................................ 222 2CB.019.05 Candidate list with partial match (3)................................................................................ 223 2CB.021.00 DDF entry......................................................................................................................... 225


Page 6

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CB.022.00 Status Word Processing for SELECT DDF ...................................................................... 226 2CB.023.00 Candidate List empty after selection with PSE................................................................. 228 2CB.023.01 Failed Processing for READ RECORD in selection by PSE............................................ 229 2CB.023.02 Failed Processing for READ RECORD in selection by PSE (2) ...................................... 231 2CB.024.00 Selection using a list of AIDs............................................................................................ 233 2CB.025.06 DF name and AID identical & SELECT command successful ......................................... 234 2CB.026.05 DF name and AID identical & application blocked ......................................................... 235 2CB.028.00 Selection using a list of AIDs............................................................................................ 236 2CB.029.00 Selection using a list of AIDs: candidate list completion ................................................. 238 2CB.031.00 Application Selection Indicator: One Occurrence Permitted........................................... 239 2CB.031.06 DF name longer than AID & multiple occurrence & application not blocked ................ 241 2CB.031.07 DF name longer than AID & multiple occurrence & application blocked ...................... 243 2CB.032.00 DFNAME is different from AID........................................................................................ 245 2CB.034.00 Multiple occurrence of application: next option supported: 90 00 .................................. 246 2CB.035.00 Multiple occurrence of application: next option failed: 62 83 ......................................... 247 2CB.036.00 Multiple occurrence of application: next option failed: other.......................................... 248 2CB.037.00 Final Selection: no mutually supported application......................................................... 250 2CB.038.00 Final Selection: one mutually supported application....................................................... 251 2CB.039.00 Final Selection: cardholder confirmation ........................................................................ 252 2CB.040.00 Final Selection: no cardholder confirmation ................................................................... 253 2CB.041.00 Final Selection: cardholder does not approve ................................................................. 254 2CB.042.00 Displaying Application to Cardholder: priority sequence ............................................... 255 2CB.042.01 Displaying Application to Cardholder when cardholder confirmation is supported ....... 256 2CB.049.00 Terminal Selection of Application without Cardholder Assistance .................................. 257 2CB.050.00 Terminal Selection of Application without Cardholder Assistance: confirmation required ................................................................................................................................................................ 258 2CB.053.00 Final Selection of Application from Candidate List: list of AID ...................................... 259 2CB.053.01 Final Selection of Application from Candidate List: list of AID (2)................................. 260 2CB.054.00 Final Selection of Application from Candidate List: PSE ................................................ 261 2CB.055.00 Final Selection of Application from Candidate List: SELECT status different from 90 00 ................................................................................................................................................................ 262 SECURITY ASPECTS ...................................................................................................................................... 264 2CC.003.00 Terminal shall be able to store 6 CA Index per RID ........................................................ 265 2CC.004.00 Algorithm For SDA .......................................................................................................... 268 2CC.006.00 Bit Length of all Moduli ................................................................................................... 270 2CC.007.00 Value of Certification Authority Public Key Exponent..................................................... 271 2CC.008.00 Value of Issuer Public Key Exponent ............................................................................... 272 2CC.009.00 Data missing: CA Public Key Index ................................................................................. 273 2CC.010.00 Data missing: Issuer PK Certificate................................................................................. 275 2CC.011.00 Data missing: Issuer PK Exponent................................................................................... 276 2CC.012.00 Data missing: Signed Static Application data.................................................................. 277 2CC.014.00 Retrieving CA Public Key used to Perform SDA: Key absent.......................................... 279 2CC.014.01 Retrieving CA Public Key used to Perform DDA: Key absent ......................................... 280 2CC.014.02 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent ................. 281 2CC.014.03 Retrieving CA Public Key used to Perform PIN Encryption: Key absent ........................ 282 2CC.014.04 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent (2)............ 283 2CC.014.05 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent (2)............ 285 2CC.014.06 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent (3)............ 287 2CC.014.07 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent (8)............ 289 2CC.015.00 Length of Issuer Public Key Certificate ........................................................................... 291 2CC.017.00 Recovered Data Trailer not equal to 'BC' ........................................................................ 292 2CC.018.00 Recovered Data Header not equal to '6A' ........................................................................ 293 2CC.019.00 Certificate Format not equal to '02' ................................................................................. 294


EMVCo Type Approval - Terminal Level 2 - Test Cases 2CC.020.00 2CC.021.00 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.043.02 2CC.043.03 2CC.043.04 2CC.043.05 2CC.044.00 2CC.044.01 2CC.044.02 2CC.044.03 2CC.044.04 2CC.044.05 2CC.045.00 2CC.045.01 2CC.045.02 2CC.045.03 2CC.045.04 2CC.045.05 2CC.046.00 2CC.046.01 2CC.046.02 2CC.046.03 2CC.046.04 2CC.046.05

Difference between calculated Hash Result and recovered Hash Result......................... 295 Issuer Identifer does not match leftmost 3-8 PAN digits .................................................. 297 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 Recover Data Trailer not equal to 'BC'............................................................................ 307 Recover 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) ........................................................................... 337 Data missing: CA Public Key Index (3) ........................................................................... 339 Data missing: CA Public Key Index (4) ........................................................................... 341 Data missing: CA Public Key Index (5) ........................................................................... 343 Data missing: CA Public Key Index (6) ........................................................................... 345 Data missing: Issuer Public Key Certificate .................................................................... 347 Data missing: Issuer Public Key Certificate (2)............................................................... 349 Data missing: Issuer Public Key Certificate (3)............................................................... 351 Data missing: Issuer Public Key Certificate (3)............................................................... 353 Data missing: Issuer Public Key Certificate (4)............................................................... 355 Data missing: Issuer Public Key Certificate (6)............................................................... 357 Data missing: Issuer PK Exponent................................................................................... 359 Data missing: Issuer PK Exponent (2)............................................................................. 361 Data missing: Issuer PK Exponent (3)............................................................................. 363 Data missing: Issuer PK Exponent (4)............................................................................. 365 Data missing: Issuer PK Exponent (5)............................................................................. 367 Data missing: Issuer PK Exponent (6)............................................................................. 369 Data missing: ICC Public Key Certificate ....................................................................... 371 Data missing: ICC Public Key Certificate (2).................................................................. 373 Data missing: ICC Public Key Certificate (3).................................................................. 375 Data missing: ICC PIN Encryption Public Key Certificate ............................................. 376 Data missing: ICC Public Key Certificate (5).................................................................. 377 Data missing: ICC Public Key Certificate (6).................................................................. 379


Page 8

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CC.046.06 2CC.046.07 2CC.047.00 2CC.047.01 2CC.047.02 2CC.047.03 2CC.047.04 2CC.047.05 2CC.047.06 2CC.047.07 2CC.050.00 2CC.050.01 2CC.050.02 2CC.050.03 2CC.050.04 2CC.050.05 2CC.050.06 2CC.052.00 2CC.052.01 2CC.052.02 2CC.052.03 2CC.052.04 2CC.052.05 2CC.052.06 2CC.053.00 2CC.053.01 2CC.053.02 2CC.053.03 2CC.053.04 2CC.053.05 2CC.053.06 2CC.054.00 2CC.054.01 2CC.054.02 2CC.054.03 2CC.054.04 2CC.054.05 2CC.054.06 2CC.055.00 2CC.055.01 2CC.055.02 2CC.055.03 2CC.055.04 2CC.055.05 2CC.055.06 2CC.056.00 2CC.056.01 2CC.056.02 2CC.056.03 2CC.056.04 2CC.056.05 2CC.056.06 2CC.057.00

Data missing: ICC Public Key Certificate (7).................................................................. 381 Data missing: ICC Public Key Certificate (8).................................................................. 383 Data missing: ICC Public Key Exponent ......................................................................... 385 Data missing: ICC Public Key Exponent (2).................................................................... 387 Data missing: ICC Public Key Exponent (3).................................................................... 389 Data missing: ICC PIN Enccryption Public Key Exponent ............................................. 390 Data missing: ICC Public Key Exponent (5).................................................................... 391 Data missing: ICC Public Key Exponent (6).................................................................... 393 Data missing: ICC Public Key Exponent (7).................................................................... 395 Data missing: ICC Public Key Exponent (8).................................................................... 397 Length of Issuer Public Key Certificate ........................................................................... 399 Length of Issuer Public Key Certificate (2)...................................................................... 400 Length of Issuer Public Key Certificate (3)...................................................................... 401 Length of Issuer Public Key Certificate (4)...................................................................... 402 Length of Issuer Public Key Certificate (5)...................................................................... 404 Length of Issuer Public Key Certificate (6)...................................................................... 406 Length of Issuer Public Key Certificate (7)...................................................................... 408 Recover Data Trailer not equal to 'BC'............................................................................ 410 Recover Data Trailer not equal to 'BC' (2) ...................................................................... 411 Recover Data Trailer not equal to 'BC' (3) ...................................................................... 412 Recover Data Trailer not equal to 'BC' (4) ...................................................................... 413 Recover Data Trailer not equal to 'BC' (5) ...................................................................... 415 Recover Data Trailer not equal to 'BC' (6) ...................................................................... 417 Recover Data Trailer not equal to 'BC' (7) ...................................................................... 419 Recover Data Header not equal to '6A'............................................................................ 421 Recover Data Header not equal to '6A' (2) ...................................................................... 422 Recover Data Header not equal to '6A' (3) ...................................................................... 423 Recover Data Header not equal to '6A' (4) ...................................................................... 424 Recover Data Header not equal to '6A' (5) ...................................................................... 426 Recover Data Header not equal to '6A' (6) ...................................................................... 427 Recover Data Header not equal to '6A' (7) ...................................................................... 429 Certificate Format not equal to '02' ................................................................................. 431 Certificate Format not equal to '02' (2)............................................................................ 432 Certificate Format not equal to '02' (3)............................................................................ 433 Certificate Format not equal to '02' (4)............................................................................ 434 Certificate Format not equal to '02' (5)............................................................................ 436 Certificate Format not equal to '02' (6)............................................................................ 437 Certificate Format not equal to '02' (7)............................................................................ 439 Difference between calculated Hash Result and recovered Hash Result......................... 441 Difference between calculated Hash Result and recovered Hash Result (2) ................... 443 Difference between calculated Hash Result and recovered Hash Result (3) ................... 445 Difference between calculated Hash Result and recovered Hash Result (4) ................... 446 Difference between calculated Hash Result and recovered Hash Result (5) ................... 448 Difference between calculated Hash Result and recovered Hash Result (6) ................... 450 Difference between calculated Hash Result and recovered Hash Result (7) ................... 452 Issuer Identifier does not match leftmost 3-8 PAN digits ................................................. 454 Issuer Identifier does not match leftmost 3-8 PAN digits (2) ........................................... 456 Issuer Identifier does not match leftmost 3-8 PAN digits (3) ........................................... 458 Issuer Identifier does not match leftmost 3-8 PAN digits (4) ........................................... 460 Issuer Identifier does not match leftmost 3-8 PAN digits (5) ........................................... 462 Issuer Identifier does not match leftmost 3-8 PAN digits (6) ........................................... 464 Issuer Identifier does not match leftmost 3-8 PAN digits (7) ........................................... 466 Certificate Expiration Date earlier than today's date ...................................................... 468


EMVCo Type Approval - Terminal Level 2 - Test Cases 2CC.057.01 Certificate Expiration Date earlier than today's date (2)................................................. 469 2CC.057.02 Certificate Expiration Date earlier than today's date (3)................................................. 470 2CC.057.03 Certificate Expiration Date earlier than today's date (4)................................................. 471 2CC.057.04 Certificate Expiration Date earlier than today's date (5)................................................. 473 2CC.057.05 Certificate Expiration Date earlier than today's date (6)................................................. 475 2CC.057.06 Certificate Expiration Date earlier than today's date (7)................................................. 477 2CC.058.00 RID, CA Public Key Index and Certificate Serial Number not valid, DDA ..................... 479 2CC.058.01 RID, CA Public Key Index and Certificate Serial Number not valid, CDA (2)................ 481 2CC.058.02 RID, CA Public Key Index and Certificate Serial Number not valid, Offline Enciphered PIN.......................................................................................................................................................... 483 2CC.058.03 RID, CA Public Key Index and Certificate Serial Number not valid (4).......................... 485 2CC.058.04 Certification Revocation List update, removal (2) ........................................................... 487 2CC.058.05 Certification Revocation List update, addition (2) ........................................................... 488 2CC.058.06 Certification Revocation List update, removal (3) ........................................................... 490 2CC.058.07 Certification Revocation List update, addition (3) ........................................................... 492 2CC.058.08 Certification Revocation List update, removal (4) ........................................................... 494 2CC.058.09 Certification Revocation List update, addition (4) ........................................................... 496 2CC.058.10 RID, CA Public Key Index and Certificate Serial Number not valid (5).......................... 498 2CC.058.11 RID, CA Public Key Index and Certificate Serial Number not valid (6).......................... 500 2CC.058.12 RID, CA Public Key Index and Certificate Serial Number not valid (7).......................... 502 2CC.059.00 Issuer Public Key Algorithm not recognized.................................................................... 504 2CC.059.01 Issuer Public Key Algorithm not recognized (2) .............................................................. 505 2CC.059.02 Issuer Public Key Algorithm not recognized (3) .............................................................. 506 2CC.059.03 Issuer Public Key Algorithm not recognized (4) .............................................................. 507 2CC.059.04 Issuer Public Key Algorithm not recognized (5) .............................................................. 509 2CC.059.05 Issuer Public Key Algorithm not recognized (6) .............................................................. 511 2CC.059.06 Issuer Public Key Algorithm not recognized (7) .............................................................. 513 2CC.060.00 Issuer Identifier wtih length between 3 to 8 digits............................................................ 515 2CC.060.01 Issuer Identifier wtih length between 3 to 8 digits (2) ...................................................... 517 2CC.060.02 Issuer Identifier wtih length between 3 to 8 digits (2) ...................................................... 519 2CC.060.03 Issuer Identifier wtih length between 3 to 8 digits (3) ...................................................... 521 2CC.060.04 Issuer Identifier wtih length between 3 to 8 digits (4) ...................................................... 523 2CC.060.05 Issuer Identifier wtih length between 3 to 8 digits (5) ...................................................... 525 2CC.061.00 Length of ICC Public Key Certificate............................................................................... 527 2CC.061.01 Length of ICC Public Key Certificate (2) ......................................................................... 528 2CC.061.02 Length of ICC Public Key Certificate (3) ......................................................................... 529 2CC.061.03 Length of ICC PIN Encipherment Public Key Certificate................................................ 530 2CC.061.04 Length of ICC Public Key Certificate (5) ......................................................................... 531 2CC.061.05 Length of ICC Public Key Certificate (6) ......................................................................... 533 2CC.061.06 Length of ICC Public Key Certificate (7) ......................................................................... 535 2CC.061.07 Length of ICC Public Key Certificate (8) ......................................................................... 537 2CC.063.00 Recover Data Trailer not equal to 'BC'............................................................................ 539 2CC.063.01 Recover Data Trailer not equal to 'BC' (2) ...................................................................... 540 2CC.063.02 Recover Data Trailer not equal to 'BC' (3) ...................................................................... 541 2CC.063.03 Recover Data Trailer not equal to 'BC' (4) ...................................................................... 542 2CC.063.04 Recover Data Trailer not equal to 'BC' (5) ...................................................................... 543 2CC.063.05 Recover Data Trailer not equal to 'BC' (6) ...................................................................... 545 2CC.063.06 Recover Data Trailer not equal to 'BC' (7) ...................................................................... 547 2CC.063.07 Recover Data Trailer not equal to 'BC' (8) ...................................................................... 549 2CC.064.00 Recover Data Header not equal to '6A'............................................................................ 551 2CC.064.01 Recover Data Header not equal to '6A' (2) ...................................................................... 552 2CC.064.02 Recover Data Header not equal to '6A' (3) ...................................................................... 553 2CC.064.03 Recover Data Header not equal to '6A' (4) ...................................................................... 554 2CC.064.04 Recover Data Header not equal to '6A' (5) ...................................................................... 555 2CC.064.05 Recover Data Header not equal to '6A' (6) ...................................................................... 557


Page 10

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CC.064.06 2CC.064.07 2CC.065.00 2CC.065.01 2CC.065.02 2CC.065.03 2CC.065.04 2CC.065.05 2CC.065.06 2CC.065.07 2CC.066.00 2CC.066.01 2CC.066.02 2CC.066.03 2CC.066.04 2CC.066.05 2CC.066.06 2CC.066.07 2CC.067.00 2CC.067.01 2CC.067.02 2CC.067.03 2CC.067.04 2CC.067.05 2CC.067.06 2CC.067.07 2CC.068.00 2CC.068.01 2CC.068.02 2CC.068.03 2CC.068.04 2CC.068.05 2CC.068.06 2CC.068.07 2CC.069.00 2CC.069.01 2CC.069.02 2CC.069.03 2CC.069.04 2CC.069.05 2CC.069.06 2CC.069.07 2CC.071.00 2CC.072.00 2CC.074.00 2CC.075.00 2CC.076.00 2CC.078.00 2CC.079.00 2CC.080.00 2CC.081.00 2CC.082.00 2CC.083.00

Recover Data Header not equal to '6A' (7) ...................................................................... 559 Recover Data Header not equal to '6A' (8) ...................................................................... 561 Certificate Format not equal to '04' ................................................................................. 563 Certificate Format not equal to '04' (2)............................................................................ 564 Certificate Format not equal to '04' (3)............................................................................ 565 Certificate Format not equal to '04' (4)............................................................................ 566 Certificate Format not equal to '04' (5)............................................................................ 567 Certificate Format not equal to '04' (6)............................................................................ 569 Certificate Format not equal to '04' (7)............................................................................ 571 Certificate Format not equal to '04' (8)............................................................................ 573 Difference between calculated Hash Result and recovered Hash Result......................... 575 Difference between calculated Hash Result and recovered Hash Result (2) ................... 576 Difference between calculated Hash Result and recovered Hash Result (3) ................... 577 Difference between calculated Hash Result and recovered Hash Result (4) ................... 578 Difference between calculated Hash Result and recovered Hash Result (5) ................... 579 Difference between calculated Hash Result and recovered Hash Result (6) ................... 581 Difference between calculated Hash Result and recovered Hash Result (7) ................... 583 Difference between calculated Hash Result and recovered Hash Result (8) ................... 585 Recovered PAN is not equal to read PAN ........................................................................ 587 Recovered PAN is not equal to read PAN (2) .................................................................. 588 Recovered PAN is not equal to read PAN (3) .................................................................. 589 Recovered PAN is not equal to read PAN (4) .................................................................. 590 Recovered PAN is not equal to read PAN (5) .................................................................. 591 Recovered PAN is not equal to read PAN (6) .................................................................. 593 Recovered PAN is not equal to read PAN (7) .................................................................. 595 Recovered PAN is not equal to read PAN (8) .................................................................. 597 Certificate Expiration Date earlier than today's date ...................................................... 599 Certificate Expiration Date earlier than today's date (2)................................................. 600 Certificate Expiration Date earlier than today's date (3)................................................. 601 Certificate Expiration Date earlier than today's date (4)................................................. 602 Certificate Expiration Date earlier than today's date (5)................................................. 603 Certificate Expiration Date earlier than today's date (6)................................................. 605 Certificate Expiration Date earlier than today's date (7)................................................. 607 Certificate Expiration Date earlier than today's date (8)................................................. 609 ICC Public Key Algorithm not recognized ....................................................................... 611 ICC Public Key Algorithm not recognized (2) ................................................................. 612 ICC Public Key Algorithm not recognized (3) ................................................................. 613 ICC Public Key Algorithm not recognized (4) ................................................................. 614 ICC Public Key Algorithm not recognized (5) ................................................................. 615 ICC Public Key Algorithm not recognized (6) ................................................................. 617 ICC Public Key Algorithm not recognized (7) ................................................................. 619 ICC Public Key Algorithm not recognized (8) ................................................................. 621 Dynamic Signature generation......................................................................................... 623 Default DDOL .................................................................................................................. 625 Source of Unpredictable Number..................................................................................... 627 DDOL does not contain unpredictable Number............................................................... 629 Default DDOL does not contain unpredictable Number.................................................. 630 Signed Dynamic Application Data Length not OK .......................................................... 631 Recovery Function............................................................................................................ 632 Recover Data Trailer not equal to 'BC'............................................................................ 633 Recover Data Header not equal to '6A'............................................................................ 634 Certificate Format not equal to '05' ................................................................................. 635 Difference between calculated Hash Result and recovered Hash Result......................... 636


EMVCo Type Approval - Terminal Level 2 - Test Cases 2CC.085.00 2CC.085.01 2CC.085.02 2CC.085.03 2CC.085.04 2CC.085.05 2CC.085.06 2CC.085.07 2CC.086.00 2CC.091.00 2CC.094.00 2CC.095.00 2CC.095.01 2CC.096.00 2CC.097.00 2CC.098.00 2CC.099.00 2CC.100.00 2CC.100.01 2CC.102.00 2CC.119.00 2CC.119.01 2CC.122.00 2CC.122.01 2CC.122.02 2CC.122.03 2CC.122.04 2CC.122.05 2CC.122.06 2CC.122.07 2CC.122.08 2CC.123.00 2CC.123.01 2CC.123.02 2CC.123.03 2CC.124.00 2CC.124.01 2CC.125.00 2CC.125.01 2CC.125.02 2CC.125.03 2CC.126.00 2CC.126.01 2CC.126.02 2CC.126.03 2CC.127.00 2CC.127.01 2CC.127.02 2CC.128.00 2CC.128.01 2CC.128.02 2CC.128.03 2CC.129.00 2CC.129.01 2CC.129.02

SDA Tag List in Dynamic Data Authentication................................................................ 638 SDA Tag List in Dynamic Data Authentication (1).......................................................... 639 SDA Tag List in Dynamic Data Authentication (3).......................................................... 641 SDA Tag List in Dynamic Data Authentication (4).......................................................... 642 SDA Tag List in Dynamic Data Authentication (5).......................................................... 643 SDA Tag List in Dynamic Data Authentication (6).......................................................... 645 SDA Tag List in Dynamic Data Authentication (7).......................................................... 647 SDA Tag List in Dynamic Data Authentication (8).......................................................... 649 ICC Dynamic Number Stored........................................................................................... 651 Key used for PIN Encryption/Decryption......................................................................... 652 Random behaviour of PIN Encipherment padding pattern .............................................. 653 Value of ICC PIN Encryption Public Key Exponent ........................................................ 654 Value of ICC Public Key Exponent .................................................................................. 655 ICC PIN Encipherment Public Key recovering: ICC PIN Encipherment Public Key ..... 656 ICC PIN Encipherment Public Key recovery: ICC Public Key........................................ 658 ICC PIN Encipherment Public Key recovering failed...................................................... 660 PIN Entry.......................................................................................................................... 661 Unpredictable Number ..................................................................................................... 662 Unpredictable Number (2) ............................................................................................... 663 VERIFY............................................................................................................................. 664 PDOL in Enhanced Combined DDA/AC.......................................................................... 665 PDOL in Enhanced Combined DDA/AC.......................................................................... 667 Response to GENERATE AC when responding AAC is in format 1or 2 .......................... 669 Response to GENERATE AC when responding AAC is in format 1or 2 (2) .................... 671 ICC responds with AAR.................................................................................................... 673 ICC responds with AAR (2) .............................................................................................. 674 Response to GENERATE AC when responding AAC is in format 1or 2 (3) .................... 675 Response to GENERATE AC when responding AAC is in format 1or 2 (4) .................... 677 ICC responds with AAR (3) .............................................................................................. 679 ICC responds with AAR (4) .............................................................................................. 680 Response to GENERATE AC when responding AAC is in format 1or 2 (5) .................... 681 Signed Dynamic Application Data Length ....................................................................... 683 Signed Dynamic Application Data Length (2) ................................................................. 685 Signed Dynamic Application Data Length (3) ................................................................. 687 Signed Dynamic Application Data Length (4) ................................................................. 689 Recovered Data trailer not equal to BC........................................................................... 691 Recovered Data trailer not equal to BC (2) ..................................................................... 693 Recovered Data header not equal to 6A........................................................................... 695 Recovered Data header not equal to 6A (2) ..................................................................... 697 Recovered Data header not equal to 6A (3) ..................................................................... 699 Recovered Data header not equal to 6A (4) ..................................................................... 701 Recovered Signed Data Format not equal to 05 .............................................................. 703 Recovered Signed Data Format not equal to 05 (2)......................................................... 705 Recovered Signed Data Format not equal to 05 (3)......................................................... 707 Recovered Signed Data Format not equal to 05 (4)......................................................... 709 Recovered CID different from CID obtained after Generate AC (1) ............................... 711 Recovered CID different from CID obtained after Generate AC (2) ............................... 713 Recovered CID different from CID obtained after Generate AC (3) ............................... 715 Compare hash result ........................................................................................................ 717 Compare hash result (2)................................................................................................... 719 Compare hash result (3)................................................................................................... 721 Compare hash result (4)................................................................................................... 723 Compare Transaction Data Hash Code ........................................................................... 725 Compare Transaction Data Hash Code (2) ..................................................................... 727 Compare Transaction Data Hash Code (3) ..................................................................... 729


Page 12

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CC.129.03 Compare Transaction Data Hash Code (4) ..................................................................... 731 2CC.130.00 Issuer Application Data in Enhanced Combined DDA/AC.............................................. 733 2CC.130.01 Issuer Application Data in Enhanced Combined DDA/AC (2) ........................................ 735 2CC.130.02 Issuer Application Data in Enhanced Combined DDA/AC (3) ........................................ 737 2CC.130.03 Issuer Application Data in Enhanced Combined DDA/AC (4) ........................................ 739 2CC.130.04 Issuer Application Data in Enhanced Combined DDA/AC (5) ........................................ 741 2CC.131.00 ICC Dynamic Number is stored ....................................................................................... 743 2CC.131.01 ICC Dynamic Number is stored (2).................................................................................. 745 2CC.133.00 Unpredictable Number generated by the terminal ........................................................... 747 2CC.133.01 Unpredictable Number not present in CDOLs ................................................................. 748 2CC.133.02 Unpredictable Number not present in CDOLs ................................................................. 749 2CC.134.00 Response to GENERATE AC when responding TC or ARQC is in format 2 ................... 751 2CC.134.01 Response to GENERATE AC when responding TC or ARQC is not in format 2 (Implied) ................................................................................................................................................................ 753 2CC.134.03 Response to GENERATE AC when responding AAC is not digitally signed (implied) .... 755 2CC.134.04 GENERATE AC Reference Control Parameter for Combined DDA/AC generation. ...... 757 2CC.134.05 Response to GENERATE AC when responding TC or ARQC is in format 2 (2).............. 758 2CC.134.06 Response to GENERATE AC when responding TC or ARQC is not in format 1 (Implied) (2)............................................................................................................................................................ 760 2CC.134.07 Response to GENERATE AC when responding AAC is not digitally signed (implied) (2) ................................................................................................................................................................ 761 2CC.134.08 GENERATE AC Reference Control Parameter for Combined DDA/AC generation (2) . 763 2CC.134.09 Response to GENERATE AC when responding TC or ARQC is in format 2 (3).............. 764 2CC.134.10 Response to GENERATE AC when responding TC or ARQC is not in format 2 (Implied) (3)............................................................................................................................................................ 766 2CC.134.11 Response to GENERATE AC when responding TC or ARQC is in format 2 (3).............. 767 2CC.134.12 Response to GENERATE AC when responding TC or ARQC is not in format 1 (Implied) (3)............................................................................................................................................................ 769 2CC.134.13 Response to GENERATE AC when responding AAC is not digitally signed (implied) (3) ................................................................................................................................................................ 770 2CC.134.14 Response to GENERATE AC when responding AAC is not digitally signed (implied) (4) ................................................................................................................................................................ 771 2CC.134.15 GENERATE AC Reference Control Parameter for Combined DDA/AC generation (3) . 773 2CC.134.16 GENERATE AC Reference Control Parameter for Combined DDA/AC generation (3) . 774 2CC.134.17 GENERATE AC Reference Control Parameter for Combined DDA/AC generation (3) . 775 2CC.135.00 Mandatory data objects are not present in response to generate AC, in Enhanced Combined DDA/AC ................................................................................................................................ 776 2CC.135.01 Mandatory data objects are not present in response to generate AC, in Enhanced Combined DDA/AC (2)........................................................................................................................... 778 2CC.135.02 Mandatory data objects are not present in response to generate AC, in Enhanced Combined DDA/AC (3)........................................................................................................................... 780 2CC.136.00 Values of CDOL2 for Transaction Data hash.................................................................. 782 2CC.136.01 Values of CDOL2 for Transaction Data hash (2) ............................................................ 784 2CC.136.02 Values of CDOL2 for Transaction Data hash (2) ............................................................ 786 2CC.137.00 Values of PDOL for Transaction Data hash .................................................................... 788 2CC.137.01 Values of PDOL for Transaction Data hash (2)............................................................... 790 2CC.137.02 Values of PDOL for Transaction Data hash (3)............................................................... 792 2CC.138.00 First Combined DDA/AC generation AAC request .......................................................... 794 2CC.138.01 First Combined DDA/AC generation AAC request .......................................................... 795 2CC.138.02 First Combined DDA/AC generation AAC request (2) .................................................... 796 2CC.139.00 Values of CDOL1 for Transaction Data hash.................................................................. 797 2CC.139.01 Values of CDOL1 for Transaction Data hash (2) ............................................................ 799 2CC.139.02 Values of CDOL1 for Transaction Data hash (3) ............................................................ 801


EMVCo Type Approval - Terminal Level 2 - Test Cases 2CC.139.03 Values of CDOL1 for Transaction Data hash (4) ............................................................ 803 2CC.139.04 Values of CDOL1 for Transaction Data hash (3) ............................................................ 805 2CC.140.00 2nd GENERATE AC for Combined DDA/AC generation not performed for ARQC ......... 807 2CC.141.00 GENERATE AC for Combined DDA/AC generation, case unable to go online, TC ....... 808 2CC.141.01 GENERATE AC for Combined DDA/AC generation, case unable to go online, AAC..... 809 2CC.141.02 GENERATE AC for Combined DDA/AC generation, case unable to go online, TC (2).. 811 2CC.141.03 GENERATE AC for Combined DDA/AC generation, case unable to go online, AAC..... 812 2CC.142.00 2nd GENERATE AC for Combined DDA/AC generation, Terminal never requesting CDA ................................................................................................................................................................ 813 2CC.143.00 Response to GENERATE AC when responding TC or ARQC can be in format 1 without CDA ........................................................................................................................................................ 814 2CC.144.00 Hash Result of SDA calculated with a long string of data ... Error! Bookmark not defined. 2CC.144.01 Hash Result of ICC Public Key calculated with a long string of data Error! Bookmark not defined. 2CC.144.02 Hash Result of ICC Public Key calculated with a long string of data (2).Error! Bookmark not defined. DATA OBJECTS ............................................................................................................................................ 821 2CE.001.00 Length field: 1 byte ........................................................................................................... 822 2CE.001.01 Length field: 2 bytes ......................................................................................................... 823 2CE.003.00 Recognition of ‘Space’ characters in AN formatted Data Objects................................... 824 2CE.003.01 Acceptance of format errors for Selection data objects - PSE ......................................... 825 2CE.003.02 Acceptance of format errors for Selection data objects - List of AIDs ............................. 826 2CE.003.03 Acceptance of format errors for Selection data objects – FINAL SELECT...................... 828 2CE.003.04 Inconsistent selection data for FCI of the PSE and FCI of ADF...................................... 829 2CE.003.05 Inconsistent selection data between list of AIDs and FINAL ADF................................... 830 2CE.003.06 Inconsistent data: only one occurrence in PSE or FINAL SELECT ................................ 832 2CE.003.07 Inconsistent data: only one occurrence in SELECT ADF or FINAL SELECT................. 833 2CE.003.08 List of AID format errors.................................................................................................. 834 APPROVED CRYPTOGRAPHY ALGORITHM .................................................................................................... 836 2CH.001.00 The Relationship Between the Lengths of the CA, Issuer, and ICC Public Keys ............. 837 2CH.001.01 The Relationship Between the Lengths of the CA, Issuer, and ICC Public Keys (2)........ 838 2CH.001.02 The Relationship Between the Lengths of the CA, Issuer, and ICC Public Keys (3)........ 839 2CH.001.03 The Relationship Between the Lengths of the CA, Issuer, and ICC PIN Encipherment Keys (4)............................................................................................................................................................ 840 2CH.001.04 The Relationship Between the Lengths of the CA, Issuer, and ICC Public Keys (5)........ 841 2CH.003.00 Upper bound for size of moduli........................................................................................ 842 2CH.003.01 Upper bound for size of moduli (2) .................................................................................. 843 2CH.003.02 Upper bound for size of moduli (3) .................................................................................. 845 2CH.003.03 Upper bound for size of moduli (4) .................................................................................. 847 2CH.003.04 Upper bound for size of moduli (5) .................................................................................. 848 FILE FOR FINANCIAL TRANSACTION INTERCHANGE ..................................................................................... 849 2CI.001.00 READ RECORD with the Short File Identifiers (SFI) ranged from 1 to 10 ...................... 850 2CI.002.00 READ RECORD in linear files .......................................................................................... 851 2CI.003.00 READ RECORD in files containing multiple records ....................................................... 852 2CI.004.00 READ RECORD with the record size in the range from 1 to 254 bytes ............................ 853 2CI.005.00 Record Data Format.......................................................................................................... 854 2CI.007.00 Free access conditions for files accessible using the READ RECORD command ............ 855 2CI.009.00 Mandatory Data Objects: Application Expiration Date.................................................... 856 2CI.010.00 Mandatory Data Objects: PAN.......................................................................................... 857 2CI.010.01 Length of Mandatory Data Objects: PAN ......................................................................... 858 2CI.011.00 Padding of Data Objects: Track 2 equivalent Data .......................................................... 860 2CI.013.00 Optional Data Objects....................................................................................................... 861 2CI.014.00 Mandatory Data Objects for Offline Static Data Authentication ...................................... 862 2CI.015.00 Mandatory Data Objects for Offline Dynamic Data Authentication................................. 864 2CI.017.00 GET DATA on PIN Try Counter........................................................................................ 866


Page 14

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CI.017.01 GET DATA on PIN Try Counter (2) .................................................................................. 867 2CI.020.00 Either the LCOL or the UCOL data objects is not present in the ICC .............................. 868 2CI.021.00 Data retrievable by GET PROCESSING OPTIONS command ......................................... 869 2CI.023.00 Functions not specified in the AIP: Offline Static Data Authentication ............................ 871 2CI.025.00 Functions not specified in the AIP: Offline Dynamic Data Authentication....................... 872 2CI.027.00 Functions not specified in the AIP: Cardholder verification............................................. 873 2CI.028.00 Functions specified in the AIP: Terminal Risk Management ............................................ 874 2CI.031.00 Functions not specified in the AIP: Issuer Authentication ................................................ 875 2CI.034.00 Functions not specified in the Application Interchange Profile: Enhanced Combined DDA / GENERATE AC ...................................................................................................................................... 876 FUNCTIONS USED IN TRANSACTION PROCESSING ......................................................................................... 878 2CJ.002.00 All bits in TSI and TVR are set to 0b................................................................................. 879 2CJ.002.01 All bits in TSI and TVR are set to 0b (2) ........................................................................... 880 2CJ.002.02 All bits in TSI and TVR are set to 0b (3) ........................................................................... 882 2CJ.002.03 All bits in TSI and TVR are set to 0b (4) ........................................................................... 883 2CJ.002.04 All bits in TSI and TVR are set to 0b (5) ........................................................................... 884 2CJ.002.05 All bits in TSI and TVR are set to 0b (6) ........................................................................... 885 2CJ.002.06 All bits in TSI and TVR are set to 0b (7) ........................................................................... 886 2CJ.002.07 All bits in TSI and TVR are set to 0b (8) ........................................................................... 887 2CJ.002.08 All bits in TSI and TVR are set to 0b (9) ........................................................................... 888 2CJ.002.09 All bits in TSI and TVR are set to 0b (10) ......................................................................... 889 2CJ.002.10 All bits in TSI and TVR are set to 0b (11) ......................................................................... 890 2CJ.002.11 All bits in TSI and TVR are set to 0b (12) ......................................................................... 891 2CJ.002.12 All bits in TSI and TVR are set to 0b (13) ......................................................................... 892 2CJ.005.00 Rules for Processing Tags listed in the PDOL (1) ............................................................ 893 2CJ.006.00 Rules for Processing Tags listed in the PDOL (2) ............................................................ 894 2CJ.007.00 Rules for Processing Tags listed in the PDOL (3) ............................................................ 895 2CJ.009.00 READ RECORD command execution ............................................................................... 896 2CJ.010.00 READ RECORD on each entry in the AFL ....................................................................... 897 2CJ.010.01 READ RECORD on each entry in the AFL (2).................................................................. 898 2CJ.011.00 Data objects processing .................................................................................................... 899 2CJ.012.00 Data objects processing (Unrecognized Data Objects) .................................................... 900 2CJ.012.01 Non recognized data object participating in offline data authentication.......................... 901 2CJ.012.02 Non recognized data objects participating in offline data authentication (2)................... 903 2CJ.012.03 Non recognized data objects participating in offline data authentication (3)................... 905 2CJ.013.00 Record Data Format: mandatory data: Application Expiration Date .............................. 907 2CJ.014.00 Record Data Format: mandatory data: PAN.................................................................... 908 2CJ.015.00 Record Data Format: mandatory data: CDOL1............................................................... 909 2CJ.016.00 Record Data Format: mandatory data: CDOL2............................................................... 910 2CJ.017.00 Record Data Format: Unique data objects....................................................................... 911 2CJ.018.00 Record Data Format: Proprietary data participating in offline data authentication ....... 912 2CJ.018.01 Record Data Format: Proprietary data participating in offline data authentication (2) . 914 2CJ.018.02 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (2).................................................................................................................................... 916 2CJ.018.03 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (3).................................................................................................................................... 918 2CJ.018.04 Record Data Format: Proprietary data participating in offline data authentication (3) . 920 2CJ.018.05 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (4).................................................................................................................................... 922 2CJ.018.06 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (5).................................................................................................................................... 924 2CJ.018.07 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (6).................................................................................................................................... 926


EMVCo Type Approval - Terminal Level 2 - Test Cases 2CJ.018.08 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (7).................................................................................................................................... 928 2CJ.019.00 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication ......................................................................................................................................... 930 2CJ.020.00 Offline Static Data Authentication is supported............................................................... 932 2CJ.021.00 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC, 1st Generate AC).......................................................................................................................................................... 933 2CJ.021.01 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC, 2nd Generate AC).......................................................................................................................................................... 935 2CJ.021.02 Both the Terminal and the Card support Enhanced Combined DDA/AC (ARQC)........... 937 2CJ.021.03 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC, 2nd Generate AC) (2) .................................................................................................................................................... 939 2CJ.021.04 Both the Terminal and the Card support Enhanced Combined DDA/AC (ARQC) (2) ..... 941 2CJ.021.05 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC, 2nd Generate AC) (2) .................................................................................................................................................... 943 2CJ.022.00 Both the Terminal and the Card support Offline SDA ...................................................... 945 2CJ.022.01 Both the Terminal and the Card support Offline SDA (2)................................................. 947 2CJ.022.02 Both the Terminal and the Card support Offline SDA (3)................................................. 949 2CJ.023.00 Both the Offline DDA and the Offline SDA are supported................................................ 951 2CJ.023.01 Both the Offline DDA and the Offline SDA are supported (2) .......................................... 953 2CJ.024.00 Neither the Offline DDA nor the Offline SDA nor the Enhanced Combined DDA/AC is performed................................................................................................................................................ 955 2CJ.024.01 Neither the Offline DDA nor the Offline SDA nor the Enhanced Combined DDA/AC is performed (2) .......................................................................................................................................... 956 2CJ.024.03 Neither the Offline DDA nor the Offline SDA nor the Enhanced Combined DDA/AC is performed (3) .......................................................................................................................................... 957 2CJ.025.00 Rules for Processing the Input Data ................................................................................. 959 2CJ.025.01 Rules for Processing the Input Data (2)............................................................................ 961 2CJ.025.02 Rules for Processing the Input Data (3)............................................................................ 963 2CJ.026.00 Rules for Processing the records identified by the AFL, when the Offline DDA is performed (1)............................................................................................................................................................ 965 2CJ.026.01 Rules for Processing the records identified by the AFL, when the Offline Combined DDA/AC is performed............................................................................................................................. 967 2CJ.027.00 Rules for Processing the records identified by the AFL, when the Offline DDA is performed (2)............................................................................................................................................................ 969 2CJ.027.01 Rules for Processing the records identified by the AFL, when the Offline Combined DDA/AC is performed (2) ....................................................................................................................... 971 2CJ.028.00 Rules for Processing the records identified by the AFL, when the Offline SDA is performed (1)............................................................................................................................................................ 973 2CJ.029.00 Rules for Processing the records identified by the AFL, when the Offline SDA is performed (2)............................................................................................................................................................ 975 2CJ.030.00 Processing AIP during Offline Static Data Authentication............................................... 977 2CJ.030.01 Processing AIP during Offline Data Authentication (2) ................................................... 979 2CJ.030.02 Processing AIP during Offline Data Authentication: Enhanced Combined DDA / GENERATE AC ...................................................................................................................................... 981 2CJ.032.00 Offline Static Data Authentication fails ............................................................................ 983 2CJ.033.00 Offline Dynamic Data Authentication fails ....................................................................... 984 2CJ.035.00 Processing Restrictions function execution....................................................................... 985 2CJ.036.00 Application Version Number assigned by the payment system ......................................... 986 2CJ.037.00 Application Version Number is not present in the ICC ..................................................... 987 2CJ.039.00 Application Version Number present in the ICC and in the terminal are the same (implied) ................................................................................................................................................................ 988 2CJ.041.00 AUC is present in the ICC and Transaction is conducted at an ATM............................... 989 2CJ.042.00 AUC is present in the ICC and Transaction is conducted at an ATM (implied) ............... 990 2CJ.043.00 AUC is present in the ICC and Transaction is not conducted at an ATM ........................ 991


Page 16

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CJ.044.00 AUC is present in the ICC and Transaction is not conducted at an ATM (implied)......... 992 2CJ.045.00 Transaction type is a Cash transaction, and Issuer Country Code = Terminal Country Code........................................................................................................................................................ 993 2CJ.046.00 Transaction type is a Cash transaction, and Issuer Country Code = Terminal Country Code (implied) ........................................................................................................................................ 994 2CJ.047.00 Transaction type is a Cash transaction, and Issuer Country Code differs from Terminal Country Code.......................................................................................................................................... 995 2CJ.048.00 Transaction type is a Cash transaction, and Issuer Country Code differs from Terminal Country Code (implied) .......................................................................................................................... 996 2CJ.049.00 Transaction type is a Purchase of goods and services, and Issuer Country Code = Terminal Country Code .......................................................................................................................... 997 2CJ.050.00 Transaction type is a Purchase of goods and Services, and Issuer Country Code = Terminal Country Code (implied)........................................................................................................... 999 2CJ.051.00 Transaction type is a Purchase of goods and Services, and Issuer Country Code differs from Terminal Country Code................................................................................................................ 1001 2CJ.052.00 Transaction type is a Purchase of goods and services, and Issuer Country Code differs from Terminal Country Code (implied) ................................................................................................ 1003 2CJ.053.00 Transaction type is a Purchase of good and services, and Issuer Country Code = Terminal Country Code........................................................................................................................................ 1005 2CJ.054.00 Transaction type is a Purchase of goods and services, and Issuer Country Code = Terminal Country Code (implied)......................................................................................................... 1007 2CJ.055.00 Transaction type is a Purchase of goods and services, and Issuer Country Code differs from Terminal Country Code................................................................................................................ 1009 2CJ.056.00 Transaction type is a Purchase of goods andservices, and Issuer Country Code differs from Terminal Country Code (implied) ................................................................................................ 1011 2CJ.057.00 Transaction has a Cashback amount, and Issuer Country Code = Terminal Country Code .............................................................................................................................................................. 1013 2CJ.058.00 Transaction has a Cashback amount, and Issuer Country Code = Terminal Country Code (implied)................................................................................................................................................ 1014 2CJ.059.00 Transaction type is a Cashback amount, and Issuer Country Code differs from Terminal Country Code........................................................................................................................................ 1015 2CJ.060.00 Transaction type is a Cashback amount, and Issuer Country Code differs from Terminal Country Code (implied) ........................................................................................................................ 1016 2CJ.061.00 Application Usage Control is not present in the ICC (implied) ...................................... 1017 2CJ.062.00 Application Usage Control is present in the ICC but not Issuer Country code (implied) .............................................................................................................................................................. 1018 2CJ.063.00 Current Date is earlier than Application Effective Date................................................. 1019 2CJ.064.00 Current Date is later than Application Effective Date (implied) .................................... 1020 2CJ.064.01 Current Date is equal to Application Effective Date (implied) ....................................... 1021 2CJ.065.00 Current Date is later than Application Expiration Date................................................. 1022 2CJ.066.00 Current Date is ealier than Application Expiration Date (implied)................................ 1023 2CJ.066.01 Current Date is equal to the Application Expiration Date (implied) .............................. 1024 2CJ.068.00 Cardholder Verification is supported in the AIP ............................................................ 1025 2CJ.069.00 Supported CVR condition: Always .................................................................................. 1027 2CJ.070.00 Supported CVR condition: If unattended cash ................................................................ 1028 2CJ.070.01 Supported CVR condition: If manual cash...................................................................... 1029 2CJ.070.02 Supported CVR condition: If purchase with cashback.................................................... 1030 2CJ.071.00 Supported CVR condition: If 'not unattended cash and not manual cash, and not purchase with cashback'....................................................................................................................................... 1031 2CJ.073.00 Supported CVR condition: If Terminal supports the CVM and CVM is offline PIN....... 1032 2CJ.073.01 Supported CVR condition: If Terminal supports the CVM and CVM is Enciphered offline PIN........................................................................................................................................................ 1033 2CJ.074.00 Supported CVR condition: If Terminal supports the CVM and CVM is online PIN ....... 1034


EMVCo Type Approval - Terminal Level 2 - Test Cases 2CJ.075.00 Supported CVR condition: If Terminal supports the CVM and CVM is signature ......... 1035 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 ................................................................................ 1036 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 .......................................................................... 1038 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 ................................................................................. 1040 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.......................................................................................... 1042 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................................................................................................ 1044 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................................................................................................. 1046 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. ............................................................................... 1048 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 .......................................................................... 1050 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. ................................................................................ 1052 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. ................................................................................... 1054 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. .......................................................................................... 1056 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.......................................................................................... 1058 2CJ.081.01 Random Transaction Selection: Transaction Amount Less than the Threshold Value for Biased Random Selection ..................................................................................................................... 1060 2CJ.081.02 Random Transaction Selection: Transaction Amount Less than the Threshold Value for Biased Random Selection ..................................................................................................................... 1061 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..................................... 1062 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..................................... 1063 2CJ.082.01 CVM List is not present in the ICC ................................................................................. 1064 2CJ.083.00 Second byte of a Cardholder Verification Rule is not satisfied....................................... 1066 2CJ.083.01 Non Supported CVR condition: If Terminal supports the CVM and CVM is offline Plaintext PIN........................................................................................................................................................ 1068 2CJ.083.02 Non Supported CVR condition: If Terminal supports the CVM and CVM is offline Enciphered PIN .................................................................................................................................... 1069 2CJ.083.03 Non Supported CVR condition: If Terminal supports the CVM and CVM is online Enciphered PIN .................................................................................................................................... 1070 2CJ.083.04 Non Supported CVR condition: If Terminal supports the CVM and CVM is Signature . 1071 2CJ.083.05 Non Supported CVR condition: If Terminal supports the CVM and CVM is offline Plaintext PIN and Signature ................................................................................................................................ 1072 2CJ.083.06 Non Supported CVR condition: If Terminal supports the CVM and CVM is offline Enciphered PIN and Signature............................................................................................................. 1073 2CJ.083.07 Non Supported CVR condition: If Terminal supports the CVM and CVM is No CVM Required................................................................................................................................................ 1074 2CJ.084.00 ICC Data required by the CVM Condition Code is missing ........................................... 1075 2CJ.084.01 ICC Data required by the CVM Condition Code is missing (Amount Authorised)......... 1077 2CJ.085.00 CVM Condition Code is outside the range of codes understood by the terminal............ 1079 2CJ.086.00 Cardholder Verification Rule for cash transactions not satisfied, transaction type ....... 1081 2CJ.086.01 Cardholder Verification Rule for cash transactions not satisfied, terminal type............ 1083 2CJ.087.00 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail CVM ..... 1085 2CJ.087.01 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail CVM ..... 1087


Page 18

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CJ.087.02 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail CVM (2)1089 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) ............................................................................................................ 1091 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)...................................................................................................... 1093 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) ...................................................................................................... 1095 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) ................................................................................................ 1097 2CJ.089.00 Second byte of CVR satisfied and CVM Code is - Enciphered PIN Online (Enciphered PIN Online supported) ................................................................................................................................. 1099 2CJ.089.01 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online (Enciphered PIN Online not supported) ........................................................................................................................... 1101 2CJ.089.02 Second byte of CVR satisfied and CVM Code is - Enciphered PIN Online (Enciphered PIN Online supported) (2) ........................................................................................................................... 1103 2CJ.089.03 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online (Enciphered PIN Online not supported) (2) ..................................................................................................................... 1105 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) ................................................... 1107 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) ............................................. 1109 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).............................................. 1111 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)........................................ 1113 2CJ.091.00 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by ICC (Enciphered PIN verified by ICC supported) ....................................................................................... 1115 2CJ.091.01 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by ICC (Enciphered PIN verified by ICC not supported) ................................................................................. 1117 2CJ.091.02 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by ICC (Enciphered PIN verified by ICC supported) (2).................................................................................. 1119 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)............................................................................ 1121 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) ................................................ 1123 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) .......................................... 1125 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)........................................... 1127 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)..................................... 1129 2CJ.093.00 Second byte of CVR satisfied and CVM Code is signature (signature supported).......... 1131 2CJ.093.01 Second byte of CVR satisfied and CVM Code is signature (signature not supported).... 1133 2CJ.093.02 Second byte of CVR satisfied and CVM Code is signature (signature supported).......... 1135 2CJ.093.03 Second byte of CVR satisfied and CVM Code is signature (signature not supported).... 1137 2CJ.094.00 Second byte of CVR satisfied and CVM Code is no CVM required (No CVM required is supported)............................................................................................................................................. 1139 2CJ.094.01 Second byte of CVR satisfied and CVM Code is No CVM required (No CVM required is not supported)....................................................................................................................................... 1141 2CJ.094.02 Second byte of CVR satisfied and CVM Code is no CVM required (No CVM required is supported)............................................................................................................................................. 1143 2CJ.094.03 Second byte of CVR satisfied and CVM Code is No CVM required (No CVM required is not supported)....................................................................................................................................... 1145


EMVCo Type Approval - Terminal Level 2 - Test Cases 2CJ.095.00 Second byte of CVR satisfied and CVM Code not understood by the terminal............... 1147 2CJ.095.01 Second byte of CVR satisfied and CVM Code not understood by the terminal............... 1149 2CJ.096.00 CVM processing succeeds ............................................................................................... 1151 2CJ.096.01 CVM processing succeeds (2) ......................................................................................... 1152 2CJ.096.02 CVM processing succeeds (3) ......................................................................................... 1153 2CJ.097.00 CVM processing fails and CVR indicates to proceed with next rule............................... 1154 2CJ.098.00 CVM processing fails and no more CVRs in the CVM List............................................. 1155 2CJ.099.00 CVM processing fails and CVR indicates to not proceed with next rule......................... 1156 2CJ.100.00 Non Supported CVR condition: If unattended Cash and transaction is not cash ........... 1158 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 .............................................................. 1160 2CJ.100.02 Non Supported CVR condition: If manual cash, and transaction is not manual cash .... 1162 2CJ.100.03 Non Supported CVR condition: If purchase with cashback, and transaction is not purchase with cashback ....................................................................................................................................... 1164 2CJ.100.04 Non Supported CVR condition: If unattended Cash and transaction is not cash ........... 1166 2CJ.100.05 Non Supported CVR condition: If manual cash, and transaction is not manual cash .... 1167 2CJ.103.00 Offline PIN is the selected CVM and Terminal does not support offline PIN................. 1168 2CJ.103.01 Offline PIN is the selected CVM and Terminal does not support offline PIN (2) ........... 1169 2CJ.103.02 Offline PIN is the selected CVM and Terminal does not support offline PIN (3) ........... 1170 2CJ.107.00 Offline PIN is the selected CVM and the number of remaining PIN trials is zero.......... 1171 2CJ.107.01 Offline PIN is the selected CVM and the number of remaining PIN trials is zero (2) .... 1172 2CJ.108.00 Offline PIN is the selected CVM and the offline PIN processing is successful ............... 1173 2CJ.108.01 Offline PIN is the selected CVM and the offline PIN processing is successful (2).......... 1175 2CJ.109.00 Online PIN is the selected CVM and Terminal does not support online PIN ................. 1177 2CJ.112.00 Online PIN is the selected CVM and the online PIN processing is successful................ 1178 2CJ.113.00 Signature (paper) is a required CVM and Terminal supports the signature process - CVM is Set to 'unknown' When Signature is Used ......................................................................................... 1180 2CJ.114.00 Combination CVM: success ............................................................................................ 1181 2CJ.114.01 Combination CVM: success (2)....................................................................................... 1182 2CJ.115.00 Combination CVM: failure.............................................................................................. 1183 2CJ.115.01 Multiple CVR entries when at least one is supported...................................................... 1184 2CJ.115.02 Combination CVM: failure (2) ........................................................................................ 1186 2CJ.116.00 Terminal Risk Management is supported in AIP............................................................. 1187 2CJ.119.00 Transaction log entry with the same PAN is available and Terminal Floor Limit is exceeded................................................................................................................................................ 1189 2CJ.120.00 Transaction log entry with the same PAN is available and Terminal Floor Limit is not exceeded (implied) ................................................................................................................................ 1191 2CJ.123.00 Transaction log is not available and Terminal Floor Limit is exceeded......................... 1193 2CJ.124.00 Transaction log is not available and Terminal Floor Limit is not exceeded (implied) ... 1195 2CJ.127.00 Transaction log entry with the same PAN is not available and Terminal Floor Limit is exceeded................................................................................................................................................ 1196 2CJ.128.00 Transaction log entry with the same PAN is not available and Terminal Floor Limit is not exceeded (implied) ................................................................................................................................ 1198 2CJ.137.00 Both the Lower and the Upper Consecutive Offline Limit are present in the ICC.......... 1199 2CJ.138.00 Lower Consecutive Offline Limit is not present in the ICC............................................. 1200 2CJ.138.01 Upper Consecutive Offline Limit is not present in the ICC............................................. 1201 2CJ.139.00 GET DATA on both the ATC and the Last Online ATC Register .................................... 1202 2CJ.140.00 The ATC Register is not present in the ICC .................................................................... 1203 2CJ.140.01 The Last Online ATC Register is not present in the ICC - LATC > 0 ............................. 1205 2CJ.140.02 The ATC Register is less than the Last online ATC......................................................... 1206 2CJ.140.03 The ATC Register is equal than to Last online ATC ....................................................... 1207 2CJ.140.04 The ATC Register is not present in the ICC – LATC = 0 ................................................ 1208 2CJ.141.00 (ATC - Last Online ATC Register) > Lower Consecutive Offline Limit.......................... 1210 2CJ.142.00 (ATC - Last Online ATC Register) = Lower Consecutive Offline Limit (implied) .......... 1211 2CJ.143.00 (ATC - Last Online ATC Register) < Lower Consecutive Offline Limit (implied) .......... 1212


Page 20

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CJ.144.00 (ATC - Last Online ATC Register) > Upper Consecutive Offline Limit.......................... 1213 2CJ.145.00 (ATC - Last Online ATC Register) = Upper Consecutive Offline Limit (implied) .......... 1214 2CJ.146.00 TC - Last Online ATC Register) < Upper Consecutive Offline Limit (implied).............. 1215 2CJ.147.00 Last Online ATC Register = 0......................................................................................... 1216 2CJ.147.01 ATC and Last Online ATC Register = 0.......................................................................... 1217 2CJ.148.00 Terminal Risk Management completion.......................................................................... 1218 2CJ.150.00 TAC Denial processing bit set to 1b................................................................................ 1220 2CJ.151.00 TAC Denial processing bit set to 0b................................................................................ 1221 2CJ.151.01 TAC Denial processing bit set to 0b (2) .......................................................................... 1222 2CJ.152.00 TAC Online Processing, bit set to 1b .............................................................................. 1223 2CJ.153.00 TAC Online Processing, bit set to 0b .............................................................................. 1224 2CJ.154.00 TAC Default processing bit set to 1b, & terminal unable to go online ........................... 1225 2CJ.155.00 TAC Default processing bit set to 0b, & terminal unable to go online ........................... 1226 2CJ.156.00 TAC Default processing bit set to 1b, & terminal has no online capability.................... 1227 2CJ.157.00 TAC Default processing bit set to 0b, & terminal has no online capability.................... 1228 2CJ.157.01 Online Only device skips TAC default............................................................................. 1229 2CJ.158.00 Terminal Action Anaysis & TVR and Issuer Action Code-Denial check requests an AAC .............................................................................................................................................................. 1230 2CJ.159.00 Terminal Action Anaysis & TVR and IAC-Denial check requests a TC (implied) .......... 1231 2CJ.159.01 Terminal Action Analysis & TVR and IAC-Denial check requests a ARQC (implied) ... 1232 2CJ.160.00 Terminal has online capability, TVR and Issuer Action Code-Online check requests an ARQC.................................................................................................................................................... 1233 2CJ.160.01 Online only terminal requests an an ARQC when not matching TAC-Online or IAC-Online .............................................................................................................................................................. 1234 2CJ.161.00 Terminal has online capability, TVR and Online Action Codes check requests a TC (implied)................................................................................................................................................ 1235 2CJ.162.00 Terminal is unable to go online, TVR and Issuer Action Code-Default check requests an AAC....................................................................................................................................................... 1236 2CJ.163.00 Terminal is unable to go online, TVR and Default Action Codes check requests a TC .. 1237 2CJ.164.00 Terminal has not online capability, TVR and Issuer Action Code-Default check requests an AAC....................................................................................................................................................... 1238 2CJ.165.00 Terminal has not online capability, TVR and Default Action Codes check requests a TC .............................................................................................................................................................. 1239 2CJ.166.00 IAC-Denial is not present in the ICC .............................................................................. 1240 2CJ.166.01 TAC-Denial is not present in the terminal ...................................................................... 1241 2CJ.167.00 IAC-Online is not present in the ICC .............................................................................. 1242 2CJ.167.01 TAC-Online is not present in the terminal ...................................................................... 1243 2CJ.168.00 IAC-Default is not present in the ICC and the Terminal is unable to go online ............. 1244 2CJ.168.01 TAC-Default is not present in the Terminal and the Terminal is unable to go online .... 1245 2CJ.169.00 IAC-Default is not present in the ICC and the Terminal is offline only .......................... 1246 2CJ.169.02 IAC-Default is not present in the ICC and the Terminal is offline only (2) .................... 1247 2CJ.170.00 Card Action Analysis function completion ...................................................................... 1248 2CJ.175.00 Generate AC Response in a Public Key Envelope .......................................................... 1249 2CJ.175.01 Generate AC Response in a Public Key Envelope .......................................................... 1251 2CJ.177.00 Advice messages during Card Action Analysis (Cryptogram Information Data: Advice required) ............................................................................................................................................... 1253 2CJ.178.00 Online Processing function execution ............................................................................. 1255 2CJ.180.00 IAD is received from the Issuer and Issuer Authentication is supported in AIP............. 1256 2CJ.181.01 Failed Processing for EXTERNAL AUTHENTICATE .................................................... 1257 2CJ.182.00 IAD is received from the Issuer and Issuer Authentication is not supported in AIP (Second Gen AC) ................................................................................................................................................ 1259 2CJ.183.00 IAD is not received from the Issuer................................................................................. 1261 2CJ.187.00 Issuer Script may contain several Issuer Script Commands ........................................... 1262


EMVCo Type Approval - Terminal Level 2 - Test Cases 2CJ.187.01 Issuer Script may contain several Issuer Script Commands (2)...................................... 1264 2CJ.187.02 Issuer Script may contain several Issuer Script Commands (3)...................................... 1266 2CJ.188.00 Issuer Script Command unknown to the terminal ........................................................... 1268 2CJ.188.01 Issuer Script Command unknown to the terminal (2)...................................................... 1270 2CJ.188.02 Issuer Script Command unknown to the terminal (3)...................................................... 1272 2CJ.189.00 Issuer Script with Tag '71' execution .............................................................................. 1274 2CJ.190.00 Issuer Script with Tag '72' execution .............................................................................. 1276 2CJ.191.00 Issuer Script Format........................................................................................................ 1278 2CJ.191.01 Issuer Script Format (2) .................................................................................................. 1280 2CJ.192.00 Script Identifier in Issuer Script ...................................................................................... 1282 2CJ.192.01 Script Identifier in Issuer Script (2)................................................................................. 1284 2CJ.193.00 Issuer Script processing .................................................................................................. 1286 2CJ.193.01 Issuer Script processing (2)............................................................................................. 1288 2CJ.193.02 Issuer Script processing (3)............................................................................................. 1290 2CJ.194.00 Issuer Script Commands not BER-TLV encoded and Issuer Script tag is '71' ................ 1292 2CJ.195.00 Issuer Script Commands not BER-TLV encoded and Issuer Script tag is '72' ................ 1294 2CJ.195.01 Issuer Script Commands not BER-TLV encoded and Issuer Script tag are '71' and '72' 1296 2CJ.195.02 Issuer Script Commands not BER-TLV encoded and Issuer Script tag are '71' and '72' (2) .............................................................................................................................................................. 1298 2CJ.195.03 Issuer Script Commands not BER-TLV encoded and Issuer Script tag are '71' and '72' (3) .............................................................................................................................................................. 1300 2CJ.197.00 SW1 in the Status Code equals '90', '62', or '63' ............................................................. 1302 2CJ.197.01 SW1 in the Status Code equals '90', '62', or '63' (2)........................................................ 1304 2CJ.197.02 SW1 in the Status Code equals '90', '62', or '63' (3)........................................................ 1306 2CJ.199.00 SWI in the Status Code is different from '90', '62', or '63' and Issuer Script tag is '71'.. 1308 2CJ.200.00 SW1 in the Status Code is different from '90', '62', or '63' and Issuer Script tag is '72' . 1310 2CJ.200.01 SW1 in the Status Code is different from '90', '62', or '63' and Issuer Script tag is '72' . 1312 2CJ.202.00 Issuer Script not processed (implied) .............................................................................. 1314 2CJ.202.01 Issuer Script not sent when no Script performed............................................................. 1315 2CJ.203.00 Enhanced Combined DDA/AC failed when ICC responded with TC (1) ........................ 1317 2CJ.203.01 Enhanced Combined DDA/AC failed when ICC responded with TC (2) ........................ 1319 2CJ.203.02 Enhanced Combined DDA/AC failed when ICC responded with TC (3) ........................ 1321 2CJ.203.03 Enhanced Combined DDA/AC failed when ICC responded with TC (4) ........................ 1323 GENERATE AC COMMAND CODING ............................................................................................................ 1325 2CK.001.00 CDOL1 for the first GENERATE AC ............................................................................. 1326 2CK.002.00 CDOL2 for the second GENERATE AC......................................................................... 1327 2CK.003.00 CDOL requests a TC Hash Value and TDOL is present in the ICC .............................. 1328 2CK.004.00 CDOL requests a TC Hash Value and TDOL is not present in the ICC ........................ 1329 2CK.005.00 CDOL requests a TC Hash Value and neither TDOL nor default TDOL is present...... 1330 2CK.005.01 CDOL requests a TC Hash Value and neither TDOL nor default TDOL is present (2) 1331 2CK.006.00 CDOL requests a TC Hash Value during the second GENERATE AC.......................... 1332 2CK.007.00 Terminal requests a TC on first GENERATE AC........................................................... 1333 2CK.008.00 Terminal requests an ARQC on first GENERATE AC ................................................... 1334 2CK.009.00 Terminal requests an AAC on first GENERATE AC ...................................................... 1335 2CK.010.00 Card responds with an ARQC on first GENERATE AC................................................. 1336 2CK.012.00 Card responds with a TC on first GENERATE AC ........................................................ 1337 2CK.013.00 Card responds with a AAC on first GENERATE AC...................................................... 1338 2CK.015.00 Terminal requests an AAC on second GENERATE AC ................................................. 1339 2CK.016.00 Terminal requests an TC on second GENERATE AC .................................................... 1341 2CK.017.00 Cryptogram at a higher level than requested (1) ........................................................... 1342 2CK.018.00 Cryptogram at a higher level than requested (2) ........................................................... 1343 2CK.018.01 Cryptogram at a higher level than requested (3) ........................................................... 1344 ERRORNEOUS OR MISSING DATA IN ICC.................................................................................................... 1345 2CL.001.00 Mandatory data objects missing: FCI (1)....................................................................... 1346 2CL.001.01 Mandatory data objects missing: Final SELECT ........................................................... 1347


Page 22

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CL.001.02 Mandatory data objects missing: FCI (2)....................................................................... 1348 2CL.002.00 Mandatory data objects missing: DF Name ................................................................... 1349 2CL.002.01 Mandatory data objects missing: DF Name (2).............................................................. 1350 2CL.003.00 Mandatory data objects missing: SFI ............................................................................. 1351 2CL.003.05 Mandatory data objects missing in directory entry: DDF Name ................................... 1352 2CL.004.00 Mandatory data objects missing in directory entry: ADF Name.................................... 1353 2CL.004.01 Mandatory data objects missing in directory entry: ADF Name (2) .............................. 1354 2CL.005.00 Mandatory data objects missing in directory entry: Application Label ......................... 1355 2CL.005.01 Mandatory data objects missing in directory entry: Application Label (2).................... 1356 2CL.006.00 Mandatory data objects missing: FCI Proprietary Template......................................... 1357 2CL.006.01 Mandatory data objects missing: FCI Proprietary Template (2) ................................... 1358 2CL.007.00 Mandatory data objects missing: AFL............................................................................ 1359 2CL.008.00 Mandatory data objects missing: AIP............................................................................. 1360 2CL.009.00 Mandatory data objects missing: CDOL1 ...................................................................... 1361 2CL.010.00 Mandatory data objects missing: CDOL2 ...................................................................... 1362 2CL.011.00 Mandatory data objects missing: PAN ........................................................................... 1363 2CL.012.00 Mandatory data objects missing: Application Expiration Date ..................................... 1364 2CL.013.00 ATC not returned by GET DATA and Both LCOL and UCOL are present.................... 1365 2CL.014.00 Last Online ATC Register not returned by GET DATA and Both LCOL and UCOL are present .................................................................................................................................................. 1366 2CL.019.00 Issuer Public Key Certificate not present and Offline SDA is supported in AIP ............ 1367 2CL.021.00 Issuer Public Key Exponent not present and Offline SDA is supported in AIP .............. 1368 2CL.023.00 Issuer Public Key Remainder not present and Offline SDA is supported in AIP............ 1369 2CL.023.01 Issuer Public Key Remainder not present and Offline SDA is supported in AIP (implied) .............................................................................................................................................................. 1371 2CL.024.00 Issuer Public Key Remainder not present and Offline DDA is supported in AIP........... 1373 2CL.024.01 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (2) ..... 1375 2CL.024.02 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (implied) .............................................................................................................................................................. 1377 2CL.024.03 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (2) (implied)................................................................................................................................................ 1378 2CL.024.04 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (5) ..... 1380 2CL.024.05 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (6) ..... 1382 2CL.024.06 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (7) ..... 1384 2CL.024.07 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (8) ..... 1386 2CL.028.00 ICC Public Key Remainder not present and Offline DDA is supported in AIP.............. 1388 2CL.028.01 ICC Public Key Remainder not present and Offline DDA is supported in AIP (2) ........ 1390 2CL.028.02 ICC Public Key Remainder not present and Offline DDA is supported in AIP (implied) .............................................................................................................................................................. 1392 2CL.028.03 ICC Public Key Remainder not present and Offline DDA is supported in AIP (2) (implied) .............................................................................................................................................................. 1394 2CL.028.04 ICC Public Key Remainder not present and Offline DDA is supported in AIP (5) ........ 1396 2CL.028.05 ICC Public Key Remainder not present and Offline DDA is supported in AIP (6) ........ 1398 2CL.028.06 ICC Public Key Remainder not present and Offline DDA is supported in AIP (6) ........ 1400 2CL.028.07 ICC PIN Encipherement Public Key Remainder not present and Offline Enciphered PIN is supported .............................................................................................................................................. 1402 2CL.028.08 ICC Public Key Remainder not present and Offline DDA is supported in AIP (9) ........ 1404 2CL.029.00 Constructed Data Objects do not parse correctly: FCI of PSE...................................... 1406 2CL.029.01 Constructed Data Objects do not parse correctly: FCI of DDF .................................... 1408 2CL.029.05 Constructed Data Objects do not parse correctly: Directory Record in Payment System Directory............................................................................................................................................... 1410 2CL.030.00 Constructed Data Objects do not parse correctly: Record Template............................. 1412 2CL.032.00 Constructed Data Objects do not parse correctly: FCI of ADF..................................... 1413


EMVCo Type Approval - Terminal Level 2 - Test Cases 2CL.033.00 Constructed Data Objects do not parse correctly: GPO response template .................. 1415 2CL.034.00 Constructed Data Objects do not parse correctly: GENERATE AC response template '77' .............................................................................................................................................................. 1416 2CL.035.00 Constructed Data Objects do not parse correctly: INTERNAL AUTHENTICATE response template ................................................................................................................................................ 1417 2CL.036.00 Dates are out of the range: effective date ....................................................................... 1419 2CL.036.01 Dates are out of the range: expiration date.................................................................... 1420 2CL.037.00 Data that must be in a specific range of values but are not: SFI ................................... 1421 2CL.037.01 Data that must be in a specific range of values but are not: SFI (2).............................. 1422 2CL.044.00 CVM List with no Cardholder Verification Rules........................................................... 1423 2CL.045.00 Errors in CVM List ......................................................................................................... 1425 2CL.047.00 AFL with an incorrect SFI .............................................................................................. 1426 2CL.048.00 AFL with an incorrect starting record number............................................................... 1427 2CL.049.00 AFL with an incorrect ending record number ................................................................ 1428 2CL.050.00 AFL with an incorrect number of records participating in Offline Data Authentication1429 2CL.054.00 ISO Padding: padding between Data object .................................................................. 1430 2CL.055.00 Format of Application Label and Application preferred Name are 'ans' ....................... 1433 2CL.056.00 Mandatory data objects missing, format 1 GERNERATE AC, TC response .................. 1434 2CL.057.00 Mandatory data objects missing, format 1 GENERATE AC, ARQC response ............... 1435 2CL.058.00 Mandatory data objects missing, format 2 GENERATE AC, TC response .................... 1436 2CL.059.00 Mandatory data objects missing, format 2 GENERATE AC, ARQC response ............... 1438 2CL.060.00 Mandatory data objects missing, format 1 INTERNAL AUTHENTICATE response ..... 1440 2CL.061.00 Mandatory data objects missing, format 2 INTERNAL AUTHENTCIATE response ..... 1441 TERMINAL GENERAL REQUIREMENTS ........................................................................................................ 1442 2CM.001.00 Merchant-controlled Terminal Provides Amount.......................................................... 1443 2CM.002.00 Merchant-controlled Terminal Obtains Amount if Not Available ................................. 1444 2CM.003.00 PDOL Requests Amount, Authorized & Amount, Other ................................................ 1445 2CM.004.00 Online Only Terminal Not Supporting Data Authentication Sets Bit ............................ 1446 2CM.006.00 Card and Terminal Application Version Numbers are different ................................... 1447 2CM.009.00 Terminal Recognition of CVM Codes ('No CVM required' supported) - CVM is Set When no CVM is Required.............................................................................................................................. 1448 2CM.009.05 Terminal Recognition of CVM Codes ('No CVM required' not supported)................... 1449 2CM.010.00 Terminal Recognition of CVM Codes ('Fail CVM processing') - CVM is Set When CVM is 'Fail CVM Processing'.......................................................................................................................... 1450 2CM.011.00 Supported CVM ............................................................................................................. 1451 2CM.013.00 PIN Try Counter Not Retrievable by ICC...................................................................... 1452 2CM.013.01 PIN Try Counter Not Retrievable by ICC (2) ................................................................ 1453 2CM.016.00 Terminal Prompt for PIN Entry (PIN Try Counter >0)................................................. 1454 2CM.016.01 Terminal Prompt for PIN Entry (PIN Try Counter >0) (2)........................................... 1455 2CM.018.00 Offline PIN Not Successful ............................................................................................ 1456 2CM.018.01 Offline PIN Not Successful (2)....................................................................................... 1457 2CM.020.00 Online PIN When PIN Try Limit is Exceeded and Terminal Supports GET DATA for PIN Try Counter........................................................................................................................................... 1458 2CM.020.01 Online PIN When PIN Try Limit is Exceeded and the Terminal does not support GET DATA for PIN Try Counter................................................................................................................... 1459 2CM.022.00 TVR is Set When PIN Entry is bypassed at Attended Terminal ..................................... 1461 2CM.023.00 CVM unsuccessful When PIN Entry is bypassed at Attended Terminal ........................ 1462 2CM.024.00 PIN Entry bypass affected all PIN methods................................................................... 1464 2CM.024.01 PIN Entry bypass does not affected all PIN methods .................................................... 1466 2CM.025.00 Terminal Prints Receipt With Line for Cardholder Signature....................................... 1468 2CM.028.00 CVM Results Set With Method Code and Condition Code of Last CVM Performed..... 1469 2CM.028.01 CVM Results Set With Method Code and Condition Code of Last CVM Performed (2)1470 2CM.028.02 CVM Results Set With Method Code and Condition Code of Last CVM Performed (3)1471 2CM.028.03 CVM Results Set With Method Code and Condition Code of Last CVM Performed (4)1472 2CM.028.04 CVM Results Set With Method Code and Condition Code of Last CVM Performed..... 1473


Page 24

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CM.030.00 CVM Result when no CVM performed........................................................................... 1474 2CM.030.01 CVM Result when no CVM performed........................................................................... 1475 2CM.030.02 CVM Result when no CVM performed........................................................................... 1476 2CM.031.00 Terminal Checks Presence of Application Selected....................................................... 1477 2CM.032.00 TVR Set if Match is Found in Exception File ................................................................ 1478 2CM.033.00 Authorization Response Code Set When Terminal Accepts Transaction Offline........... 1479 2CM.034.00 Authorization Response Code Set When Terminal Declines Transaction Offline ......... 1480 2CM.035.00 Authorization Response Code Not Set When Terminal Opts To Transmit Transaction Online ................................................................................................................................................... 1481 2CM.036.00 Terminal Completes Transaction When Card Indicated Approval ............................... 1482 2CM.036.01 Terminal Completes Transaction When Card Indicated Approval (2).......................... 1483 2CM.038.00 Terminal Transmits Auth. or Financial Transaction Request Message ........................ 1484 2CM.040.00 Advice is Requested by Card and is Supported by the Terminal and transaction is captured ................................................................................................................................................ 1485 2CM.041.00 Advice is Requested by Card and is Supported by the Terminal and transaction is not captured ................................................................................................................................................ 1486 2CM.042.00 Terminal Terminates Transaction if Card Indicates 'Service Not Allowed' (Cryptogram Information Data: Service Not allowed) .............................................................................................. 1487 2CM.042.01 Terminal Terminates Transaction if Card Indicates 'Service Not Allowed' (Cryptogram Information Data: Service Not allowed) (2)......................................................................................... 1489 2CM.042.06 Combined DDA/AC Generation failed and ICC returned an ARQC............................. 1490 2CM.042.07 Online Capable Terminal Terminates Transaction If Card Indicates ‘Service Not Alowed’ (Cryptogram Information Data: Service Not Allowed) .......................................................... 1491 2CM.042.08 Combined DDA/AC Generation failed and ICC returned an ARQC (2) ....................... 1492 2CM.043.00 Terminal Decides To Accept or Decline Transaction and Issues 2nd GENERATE AC 1493 2CM.044.00 Authorization Response Code is 'Online Approved' ...................................................... 1494 2CM.045.00 Terminal Support of Issuer Scripts in Authorization or Financial Transaction Response .............................................................................................................................................................. 1495 2CM.045.01 Terminal Support of Issuer Scripts in Authorization or Financial Transaction Response (2).......................................................................................................................................................... 1496 2CM.045.02 Terminal Support of Issuer Scripts in Authorization or Financial Transaction Response (2).......................................................................................................................................................... 1497 2CM.048.00 Terminal Reporting of Script Identifier ......................................................................... 1498 2CM.052.00 Terminal Creates an Advice When No Message is Created for Transaction ................ 1500 2CM.055.00 Terminal Supporting DDA Shall Support SDA.............................................................. 1501 2CM.055.01 Terminal Supporting CDA Shall Support SDA.............................................................. 1502 2CM.056.00 Offline Only Terminal Shall Support SDA..................................................................... 1503 2CM.057.00 Offline Terminal With Online Capability Shall Support SDA ....................................... 1504 2CM.058.00 Offline Only Terminal Shall Support Terminal Risk Management................................ 1505 2CM.059.00 Offline Terminal With Online Capability Shall Support Terminal Risk Management .. 1506 2CM.060.00 Financial Institution Terminal Supports TRM............................................................... 1507 2CM.061.00 Merchant Controlled Terminal Supports TRM.............................................................. 1509 2CM.062.00 Terminal Displays Amount of Transaction .................................................................... 1510 2CM.063.00 Cashback Amount is Transmitted in the Amount, Other Data Object ........................... 1511 2CM.064.00 Purchase and Cashback Transmitted in Amount Authorised ........................................ 1512 2CM.066.00 Authorised Amount Is Expressed With Implicit Decimal Point ..................................... 1513 2CM.067.00 Other Amount Is Expressed With Implicit Decimal Point ............................................. 1514 2CM.074.00 Terminal Displays Message To Attendant When Issuer Requests Voice Referral......... 1515 2CM.075.00 Data Displayed or Printed to Perform Referral initiated by issuer............................... 1516 2CM.076.00 Messages Displayed Requesting Attendant to Indicate Approval or Denial of a Referral initiated by issuer.................................................................................................................................. 1517 2CM.077.00 Authorization Response Code when Referral is initiated by Issuer............................... 1518 2CM.078.00 Terminal Issues Second GENERATE AC ...................................................................... 1519


EMVCo Type Approval - Terminal Level 2 - Test Cases 2CM.079.00 TVR Set When Merchant Forces Transaction Online.................................................... 1520 2CM.080.00 Attendant forces Approval of the Transaction ............................................................... 1521 2CM.081.00 Authorization Response Code when acceptance is forced............................................. 1522 2CM.082.00 Terminal Sets Indicator When Attendant forces Approval of the Transaction .............. 1523 2CM.083.00 Terminal Maintains Transaction Sequence Counter ..................................................... 1524 2CM.085.00 Generation of Unpredictable Number ........................................................................... 1525 2CM.086.00 Terminal Reading of Service Code on Magnetic Stripe................................................. 1526 2CM.087.00 Terminal Reading of Service Code on Magnetic Stripe................................................. 1527 2CM.091.00 POS Entry Mode Code Read ......................................................................................... 1528 2CM.092.00 Calculation of Dates Associated With Static Data Authentication................................ 1529 2CM.093.00 Calculation of Dates Associated With Processing Restrictions..................................... 1531 2CM.094.00 Calculation, Storage, and Display Date-Dependant Fields For Year 2000 + .............. 1533 2CM.094.01 Calculation, Storage, and Display Date-Dependant Fields For Year 2000 + .............. 1534 2CM.095.00 Processing the Year ....................................................................................................... 1535 2CM.102.00 Display For Attendant for Attended Terminal ............................................................... 1536 2CM.103.00 Display of Alphanumeric Characters ............................................................................ 1537 2CM.105.00 Protection of Captured Transactions and Advices Stored............................................. 1538 2CM.106.00 Clock With Local Date and Time................................................................................... 1539 2CM.107.00 Capability of Terminal Printer ...................................................................................... 1540 2CM.109.00 Magnetic Stripe Reader Using Full Track 1 and/or Track 2......................................... 1541 2CM.129.00 PIN Pad Shall Support Entry of 4-12 Digit PIN............................................................ 1542 2CM.129.01 PIN Pad Shall Support Entry of 4-12 Digit PIN (2) ...................................................... 1543 2CM.129.02 PIN Pad Shall Support Entry of 4-12 Digit PIN (online PIN)....................................... 1544 2CM.130.00 Display of Indication of Entry on PIN Pad - Protection of Values of Entered PIN ...... 1546 2CM.130.01 Display of Indication of Entry on PIN Pad - Protection of Values of Entered PIN (2). 1547 2CM.130.02 Display of Indication of Entry on PIN Pad - Protection of Values of Entered PIN (3). 1548 2CM.137.00 Protection of PIN During Online PIN Verification ....................................................... 1549 2CM.140.00 Amount Entry Process Separate From PIN Entry Process............................................ 1550 2CM.140.01 Amount Entry Process Separate From PIN Entry Process (2)...................................... 1551 2CM.140.02 Amount Entry Process Separate From PIN Entry Process (3)...................................... 1552 2CM.141.00 Amount Validated by Cardholder (Plaintext PIN)......................................................... 1553 2CM.141.01 Amount Validated by Cardholder (Enciphered PIN Offline)......................................... 1554 2CM.141.02 Amount Validated by Cardholder (Enciphered PIN Online)......................................... 1555 SOFTWARE ARCHITECTURE........................................................................................................................ 1556 2CN.004.00 Data Elements are Initialised in Terminal ..................................................................... 1557 2CN.012.00 Language Support by Terminal...................................................................................... 1561 2CN.016.00 Terminal Displays Error Message if Verification Process fails..................................... 1563 CARDHOLDER AND MERCHANT INTERFACE ............................................................................................... 1564 2CO.001.00 Terminal Support of Local Language ............................................................................ 1565 2CO.002.00 Terminal Display of Messages in Local Language ........................................................ 1566 2CO.003.00 Terminal Support of Relevant Character Set ................................................................. 1567 2CO.005.00 Terminal uses language With Highest Preference ......................................................... 1568 2CO.006.00 Terminal Allows Cardholder to Select Language .......................................................... 1569 2CO.008.00 Terminal Displays Message in Supported Language..................................................... 1570 2CO.011.00 Terminal Support of Explicit Selection .......................................................................... 1571 2CO.013.00 Terminal Creates a List of Applications Supported (1).................................................. 1572 2CO.014.00 Terminal Creates a List of Applications Supported (2).................................................. 1573 2CO.015.05 Terminal Presents Application List................................................................................ 1574 2CO.016.00 Terminal Selects Application With Next Highest priority .............................................. 1575 2CO.017.00 Application Used Identified on Receipt.......................................................................... 1577 2CO.018.00 Data Printed on Receipt................................................................................................. 1578 2CO.019.00 Authorization Message Used.......................................................................................... 1579 2CO.020.00 Financial Transaction Message Used............................................................................ 1580 2CO.021.00 Offline Advice message Conveyed.................................................................................. 1581 2CO.022.00 Online Advice message transmitted ............................................................................... 1582


Page 26

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CO.023.00 Reversal Used................................................................................................................. 1583 2CO.025.00 Terminal Issues a 2nd GENERATE AC Command When Unable to Go Online (1)...... 1584 2CO.026.00 Terminal Issues a 2nd GENERATE AC Command When Unable to Go Online (2)...... 1585 2CO.028.00 Terminal Continues Processing Based on Authorization Response Code ..................... 1587 2CO.028.01 Terminal Continues Processing Based on Authorization Response Code ..................... 1588 2CO.030.00 Terminal Issues a 2nd GENERATE AC Command (1) .................................................. 1589 2CO.031.00 Terminal Issues a 2nd GENERATE AC Command (2) .................................................. 1591 2CO.032.00 Terminal Sends Reversal Message................................................................................. 1593 2CO.033.00 Terminal Creates Financial Record............................................................................... 1595 2CO.034.00 Terminal Terminates Processing of Issuer Script .......................................................... 1597 2CO.034.01 Terminal Terminates Processing of Issuer Script (2)..................................................... 1599 2CO.034.02 Terminal Terminates Processing of Issuer Script exceeding device limit (1) ................ 1601 2CO.034.03 Terminal Terminates Processing of Issuer Script exceeding device limit (2) ................ 1603 2CO.035.00 Terminal Reports in Issuer Script results....................................................................... 1605 2CO.035.01 Terminal Reports in Issuer Script results (2) ................................................................. 1607 2CO.035.02 Terminal Reports in Issuer Script results (3) ................................................................. 1609 2CO.036.00 Terminal Continues Processing any Subsequent Issuer Script ...................................... 1611 2CO.036.01 Terminal Continues Processing any Subsequent Issuer Script (2) ................................ 1612 2CO.036.02 Terminal Continues Processing any Subsequent Issuer Script (2) ................................ 1613 2CO.037.00 All data in the Messages are originated from chip ........................................................ 1614 2CO.038.00 All data in the Messages are originated from chip (2)................................................... 1615 CODING OF TERMINAL DATA ELEMENT ..................................................................................................... 1616 2CP.001.00 Terminal Type................................................................................................................. 1617 2CP.002.00 Terminal Capabilities ..................................................................................................... 1618 2CP.003.00 Additional Terminal Capabilities ................................................................................... 1620 2CP.004.00 Account Type .................................................................................................................. 1622 COMMAND SYNTAX ................................................................................................................................... 1623 2CS.001.00 Mandatory Command Set................................................................................................ 1624 2CS.002.00 Select Next Command ..................................................................................................... 1627 2CS.003.00 Internal Authenticate Command ..................................................................................... 1630 2CS.004.00 Verify Command ............................................................................................................. 1633 2CS.005.00 Get Challenge command................................................................................................. 1636 2CS.006.00 Get Data command ......................................................................................................... 1640 2CS.007.00 External Authenticate command ..................................................................................... 1643 2CS.014.00 Combined functions on Transaction Flow: Offline PIN and Advice with PIN Try Limit exceeded................................................................................................................................................ 1646 2CS.014.01 Combined functions on Transaction Flow: Offline PIN and Advice with PIN Try Limit exceeded (2) .......................................................................................................................................... 1647 2CS.014.02 Combined functions on Transaction Flow: Offline PIN and Advice with PIN Try Limit exceeded (3) .......................................................................................................................................... 1648 2CS.014.03 Combined functions on Transaction Flow: Offline PIN and Advice with PIN Try Limit exceeded (4) .......................................................................................................................................... 1649 2CS.015.00 Combined functions on Transaction Flow: SDA and Record length coded on 1 or 2 bytes .............................................................................................................................................................. 1650 2CS.015.01 Combined functions on Transaction Flow: SDA and Record length of proprietary file coded on 1 or 2 bytes ............................................................................................................................ 1652 2CS.015.02 Combined functions on Transaction Flow: DDA and Record length coded on 1 or 2 bytes .............................................................................................................................................................. 1654 2CS.015.03 Combined functions on Transaction Flow: DDA and Record length of proprietary file coded on 1 or 2 bytes ............................................................................................................................ 1656 2CS.015.04 Combined functions on Transaction Flow: CDA and Record length coded on 1 or 2 bytes .............................................................................................................................................................. 1658


EMVCo Type Approval - Terminal Level 2 - Test Cases 2CS.015.05 Combined functions on Transaction Flow: CDA and Record length of proprietary file coded on 1 or 2 bytes ............................................................................................................................ 1660 2CS.016.00 Combined Test: SDA Tag List and AFL in Static Data Authentication .......................... 1662 2CS.016.03 Combined Test: SDA Tag List and AFL in Dynamic Data Authentication..................... 1664 2CS.016.05 Combined Test: SDA Tag List and AFL in Combined Data Authentication.................. 1666 COMBINED TEST ........................................................................................................................................ 1668 2CT.008.00 Combined functions on Transaction Flow: SDA and PIN Encryption ........................... 1669 2CT.009.00 Combined functions on Transaction Flow: DDA and PIN Encryption .......................... 1671 2CT.009.01 Combined functions on Transaction Flow: DDA and PIN Encryption (2)..................... 1673 2CT.010.00 Combined functions on Transaction Flow: CDA and PIN Encryption........................... 1675 2CT.010.01 Combined functions on Transaction Flow: CDA and PIN Encryption........................... 1677 2CT.011.00 Combined functions on Transaction Flow: Issuer Authentication and Script Processing .............................................................................................................................................................. 1679 2CT.011.01 Combined functions on Transaction Flow: Issuer Authentication and Script Processing (2) .............................................................................................................................................................. 1681 2CT.011.02 Combined functions on Transaction Flow: Issuer Authentication and Script Processing (3) .............................................................................................................................................................. 1683 2CT.011.03 Combined functions on Transaction Flow: Issuer Authentication and Script Processing (4) .............................................................................................................................................................. 1685 2CT.011.04 Combined functions on Transaction Flow: Issuer Authentication and Script Processing (5) .............................................................................................................................................................. 1687 2CT.012.00 Combined functions on Transaction Flow: Advice and Issuer Authentication............... 1689 2CT.012.01 Combined functions on Transaction Flow: Advice and Issuer Authentication (2) ......... 1690 2CT.013.00 Combined functions on Transaction Flow: Advice on first and second Generate AC ... 1691 2CT.013.01 Combined functions on Transaction Flow: Advice on first and second Generate AC (2) .............................................................................................................................................................. 1692 2CT.017.00 Combined Test: Get Processing and Generate AC with different response format........ 1693 2CT.017.01 Combined Test: Get Processing and Generate AC with different response format (2) .. 1694 2CT.018.00 Combined Test: Get Processing and Generate AC with different response format, CDA .............................................................................................................................................................. 1695 2CT.018.01 Combined Test: Get Processing and Generate AC with different response format, CDA (2) .............................................................................................................................................................. 1697 2CT.019.00 Combined Test: Get Processing, Internal Authenticate and Generate AC with different response format .................................................................................................................................... 1699 2CT.019.01 Combined Test: Get Processing, Internal Authenticate and Generate AC with different response format (2)............................................................................................................................... 1700 2CT.020.00 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script .................................................................................... 1701 2CT.020.01 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1................................................................................................ 1703 2CT.021.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script.......................................................................... 1704 2CT.021.01 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1 ..................................................................................... 1706 2CT.022.00 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Paper Signature, Issuer Authentication, Generate AC Format 1, Script.......................................................................... 1707 2CT.022.01 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Paper Signature, Issuer Authentication, Generate AC Format 1 ..................................................................................... 1709 2CT.023.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Paper Signature, Issuer Authentication, Generate AC Format 1, Script.......................................................................... 1710 2CT.023.01 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Paper Signature, Issuer Authentication, Generate AC Format 1, Script (2) .................................................................... 1712 2CT.024.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script .................................................................... 1713


Page 28

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CT.024.01 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script (2) .............................................................. 1715 2CT.025.00 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script.......................................................................... 1716 2CT.025.01 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script (2) .................................................................... 1718 2CT.026.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Plaintext PIN, No Issuer Authentication, Generate AC Format 2, Script.......................................................................... 1719 2CT.026.01 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Plaintext PIN, No Issuer Authentication, Generate AC Format 2, Script (2) .................................................................... 1721 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 ................................... 1722 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) ............................. 1724 2CT.028.00 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 1, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script (2)......................... 1725 2CT.028.01 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 1, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script (2)......................... 1727 2CT.029.00 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 1, TRM, SDA, DDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script .......... 1728 2CT.029.01 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 1, TRM, SDA, DDA, Paper Signature, No Issuer Authentication, Generate AC Format 1...................... 1730 2CT.030.00 Combined functions on Transaction Flow: No PSE, PDOL Empty, SDA, DDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script (2)............................................................ 1732 2CT.030.01 Combined functions on Transaction Flow: No PSE, PDOL Empty, SDA, DDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script (2)............................................................ 1734 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.................................... 1736 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) .............................. 1738 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 ....... 1740 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).. 1742 2CT.033.00 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 2, SDA, DDA,CDA, Paper Signature, No Issuer Authentication, Generate AC Format 2, Script (2)...... 1744 2CT.033.01 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 2, SDA, DDA,CDA, Paper Signature, No Issuer Authentication, Generate AC Format 2, Script (2)...... 1746 2CT.034.00 Combined functions on Transaction Flow: Proprietary Data and EMV data................ 1748 2CT.035.00 Combined functions on Transaction Flow: SDA, Keys remainder not present, Proprietary Data and EMV data .............................................................................................................................. 1749 2CT.036.00 Combined functions on Transaction Flow: DDA, Keys remainder not present, Proprietary Data and EMV data .............................................................................................................................. 1751 2CT.037.00 Combined functions on Transaction Flow: CDA, Keys remainder not present, Proprietary Data and EMV data .............................................................................................................................. 1753 2CT.038.00 Combined functions on Transaction Flow: LCOLL = 00, UCOLL= FF Proprietary Data and EMV data....................................................................................................................................... 1755 2CT.038.01 Combined functions on Transaction Flow: LCOLL = 00, UCOLL= FF Proprietary Data and EMV data....................................................................................................................................... 1757 2CT.039.00 ICC supporting DDA Only ............................................................................................. 1759 2CT.040.00 CPA compliant profile .................................................................................................... 1760 2CT.040.01 CPA compliant profile (2)............................................................................................... 1761


EMVCo Type Approval - Terminal Level 2 - Test Cases ANNEX A: TEST CASES APPLICABLE DEPENDING ON THE TERMINAL OPTIONS ........ 1763 < END OF THE DOCUMENT> ............................................................................................................. 1775


Page 30


Scope Integrated Circuit Card Specification for Payment System Version 4.0 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 Level 2 Type Approval - 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 EMV2000 Integrated Circuit Card Specification for Payment Systems Version 4.0 dated December 2000. 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 oriented toward EMV application providers.



Referenced Documents [N1]

EMV 2000 Integrated Circuit Card Specification for Version 4.0 - December Payment Systems - Book 1 - Application Independent 2000 ICC to Terminal Interface Requirements

[N2]

EMV 2000 Integrated Circuit Card Application Version 4.0 - December Specification for Payment Systems - Book 2 - 2000 Security and Key Management

[N3]

EMV 2000 Integrated Circuit Card Terminal Version 4.0 - December Specification for Payment Systems - Book 3 - 2000 Application Specification

[N4]

EMV 2000 Integrated Circuit Card Terminal Version 4.0 - December Specification for Payment Systems - Book 4 - 2000 Cardholder, Attendant, and Acquirer Interface Requirements

AN xx

All published Application Note bulletins

Bulletins 1 to 33

SU xx

All published Specification Update bulletins

Bulletins 1 to 52


Page 32


Changes with previous version This section list which test case have been modified between the previous and this version:

Test Case 2CC.144.00 2CC.144.01 2CC.144.02 2CI.027.00 2CJ.082.01 2CJ.087.00 2CJ.087.02 2CJ.088.01 2CJ.088.03 2CJ.089.01 2CJ.089.03 2CJ.090.01 2CJ.090.03 2CJ.091.01 2CJ.091.03 2CJ.092.01 2CJ.092.03 2CJ.093.01 2CJ.093.03 2CJ.094.01 2CJ.094.03 2CJ.095.00 2CJ.095.01 2CJ.103.01 2CJ.103.02 2CJ.109.00 2CJ.115.00 2CL.044.00 2CL.045.00 2CM.009.05 2CM.024.00 2CM.024.01 2CM.030.00 2CM.030.01 2CM.030.02

Modification New test New test New test Typo correction in reference Pass criteria update Pass criteria update New test Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Pass criteria update Objective, Conditions and Pass criteria update New test Pass criteria update New test New test Conditions and Pass criteria update New test New test



Abbreviations and Notations APDU

Application Protocol Data Unit

ATR

Answer to Reset

C-APDU

Command APDU

CLA

Class Byte of the Command Message

C-TPDU

Command TPDU

EMV

Europay, MasterCard, Visa

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 Copyright ©2008 EMVCo, LLC. All rights reserved

Page 34

EMVCo Type Approval - Terminal Level 2 - Test Cases NIC

Length of the ICC Public Key Modulus

P1

Parameter 1

P2

Parameter 2

P3

Parameter 3

PI

Issuer Public Key

PIC

ICC Public Key

R-APDU

Response APDU

RST

Reset

R-TPDU

Response TPDU

SCA

Certification Authority Private Key

SI

Issuer Private Key

SIC

ICC Private Key

SW1

Status Word One

SW2

Status Word Two

TPDU

Transport Protocol Data Unit



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. Copyright ©2008 EMVCo, LLC. All rights reserved

Page 36

EMVCo Type Approval - Terminal Level 2 - Test Cases 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. 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.


EMVCo Type Approval - Terminal Level 2 - Test Cases 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. 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 - Legal structure created by Europay International S.A., MasterCard International Incorporated, and Visa International Service Association for including, but not limited to, smart card interoperability specifications and associated type approval procedures. EMVCo test authority - The entity responsible for the type approval process. 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. Copyright ©2008 EMVCo, LLC. All rights reserved

Page 38

EMVCo Type Approval - Terminal Level 2 - Test Cases 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. 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.


EMVCo Type Approval - Terminal Level 2 - Test Cases 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. 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.


Page 40

EMVCo Type Approval - Terminal Level 2 - Test Cases 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 the EMVCo Test Authority that a specified product type has demonstrated sufficient conformance to the EMV specification. 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. Copyright © 2008 EMVCo, LLC. All Rights Reserved. Page 41

EMVCo Type Approval - Terminal Level 2 - Test Cases 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, Europay International S.A., MasterCard International Incorporated, Visa International Service Association or JCB Co, Ltd. 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. Copyright ©2008 EMVCo, LLC. All rights reserved

Page 42

EMVCo Type Approval - Terminal Level 2 - Test Cases 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 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.


EMVCo Type Approval - Terminal Level 2 - Test Cases 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). 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. Copyright ©2008 EMVCo, LLC. All rights reserved

Page 44

EMVCo Type Approval - Terminal Level 2 - Test Cases 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.



Test Settings Default Values setting Else 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


Batch message

Message Format - Authorization/Financial/Batch messages shall contain TSI & Service Code

AID of application Up to the Implementer 1 (default application) For the 2CT category of tests, a MasterCard AID, a VISA AID and a JCB AID shall be used once. AID of application Up to the Implementer 2 (if present) AID of application Up to the Implementer 3 (if present) AID of application Up to the Implementer 4 (if present) AID of application Up to the Implementer 5 (if present) PAN


Payment Scheme Up to the Implementer Public Key Up to the Implementer Application Primary Account Number ‘PAN)


Page 46

EMVCo Type Approval - Terminal Level 2 - Test Cases Up to the Implementer Application Primary Account Number ‘PAN) Sequence Number Issuer Public Key


ICC Public Key (if Up to the Implementer present) Application File Up to the Implementer Locator (AFL) Application currency code


Application currency exponent


Application Discretionary Data


Application Effective Date


Application Expiration Date


Application Interchange Profile


Application Prefered Name


Application Priority Indicator


Application Reference Currency


Application Reference Currency Exponent



EMVCo Type Approval - Terminal Level 2 - Test Cases Application Usage Control


Application Version Number


Cardholder Name


Cardholder Name extended


Certification Autority Public Key Index


Cardholder Verification Method (CVM) List


Directory Discretionary Template


Dedicated File (DF) Name


Directory Definition File (DDF) Name


Integrated Circuit Card (ICC) PIN Encipherment Public Key Certificat


Integrated Circuit Card (ICC) PIN Encipherment Public Key Exponent


Integrated Circuit Card (ICC) PIN Encipherment Public Key Remainder



Page 48

EMVCo Type Approval - Terminal Level 2 - Test Cases Issuer Action Code-Default


File Control Information (FCI) Template


File Control Information (FCI) Issuer Discretionary Data


Issuer Application Data


Issuer Action Code – Denial


Issuer Action Code – Online


Issuer Code Table Index


Issuer Country Code


Issuer Public Key Certificate


Issuer Public Key Exponent


Issuer Public Key Remainder


Language Preference


Last Online Application Transaction Counter (ATC) Register



EMVCo Type Approval - Terminal Level 2 - Test Cases Lower Consecutive Offline Limit


Personal Identification Number (PIN) Try Counter


Service Code


Short File Identifier (SFI)


Signed Static Application Data


Upper Consecutive Offline Limit


Static Data Authentication Tag List


Track 1 Discretionary Data


Track 2 Discretionary Data


Track 2 Equivalent Data


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. 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 Copyright ©2008 EMVCo, LLC. All rights reserved

Page 50

EMVCo Type Approval - Terminal Level 2 - Test Cases •

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


EMVCo Type Approval - Terminal Level 2 - Test Cases Test Structure 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.

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 EMV4.0 - Book 3 – 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 EMV4.0 - Book 1 – 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 EMV4.0 - Book 2 – 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 EMV4.0 - Book 3 – Annex B, Data Objects.


Page 52

EMVCo Type Approval - Terminal Level 2 - Test Cases •

2CH, Approved Cryptography Algorithm: The intent of the test cases in this category is to verify that cryptography is in accordance with EMV4.0 - Book 2 – 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 EMV4.0 - Book 3 – Sections 3, and 4.

•

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 EMV4.0 - Book 1 and Book 3 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 EMV4.0 - Book 3 – Sections 1, 3 and 5.

•

2CL, Errorneous 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 EMV4.0 - Book 1 – Sections 7 & 8, and Book 3 – Sections 4 & 7.

•

2CM, Terminal General Requirements: The intent of the test cases in this category is to verify that the terminal icomplies with EMV4.0 - Book 4 – 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 EMV4.0 - Book 4 – 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 EMV4.0 - Book 4 - 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 EMV4.0 - Book 4 - 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 EMV4.0 - Part I - Book 3 Application Specification. When the application is used to perform command syntax checking, functionality testing will not be specificallyperformed, 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 EMV4.0 – Part 2 - book 3 – 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 perfoms the EMV flow by declining or accepting the Copyright © 2008 EMVCo, LLC. All Rights Reserved. Page 53

EMVCo Type Approval - Terminal Level 2 - Test Cases transaction, depending on the predefined card profile (reflecting CCD, MasterCard, VISA and JCB card profiles).


Page 54


Test Cases



Data Element and Command


Page 56


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 1.2 - Data Objects EMV 4.0: Reference Book 3 - Section 5.2 - Data Objects EMV 4.1: 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.





•

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 offlineresponds 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


Page 58




•

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


•

The terminal shall complete and approve the transaction

•

The data in the terminal buffer when stored in the batch data capture, Online Data Capture, finanical message or any other area shall be in accordance with values sent back by the LT



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 1.2 - Data Objects EMV 4.0: Reference Book 3 - Section 5.2 - Data Objects EMV 4.1: 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.


Page 60


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 1.2 - Data Objects EMV 4.0: Reference Book 3 - Section 5.2 - Data Objects EMV 4.1: 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)



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 6.1.4 - Directory Structure EMV 4.0:

Book 1 - Section 8.2.3 - Coding of a Payment System’s Directory Reference Book 1 - Section 10.1.4 - Directory Structure EMV 4.1:

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

•


•


•


•


•


•


•


•


•


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


Page 62


2CA.004.00 Coding of a Payment System Directory: SFI Range corresponding to the Directory File



2CA.004.01 Coding of a Payment System Directory: SFI Range (2) Test No: 2CA.004.01 - Revision 10g - Number of sub cases: 10 Objective: To ensure that if the terminal supports selection with PSE and a DDF is

present, it accepts any value in the range of 1 to 10 for the SFI of the directory file of the DDF. Reference Book 1 - Section 8.2.3 - Coding of a Payment System’s Directory EMV 4.0:

Book 1 - Section 8.2.4 - Coding of Other Directories Reference Book 1 - Section 12.2.3 - Coding of a Payment System Directory EMV 4.1:

Book 1 - Section 12.2.4 - Coding of Other Directories Terminal [PSE] supported Configuration: Conditions:

•

LT contains a PSE

•

LT contains a DDF

•

Case 01: SFI value is 1 for the FCI of DDF 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 all values of SFI


Page 64


2CA.004.01 Coding of a Payment System Directory: SFI Range (2) tested



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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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).


Page 66


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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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).



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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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





Page 68


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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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





2CA.015.00 Processing DOLs: data absent from ICC Test No: 2CA.015.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 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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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’)





Page 70


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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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





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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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



the Data Object correctly truncated (portion has the same length as the Data Object in DOL).


Page 72


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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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


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).



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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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



the Data Object correctly truncated (portion has the same length as the Data Object in DOL).


Page 74


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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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


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).



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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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



the Data Object correctly padded with leading hexadecimal zeroes (portion has the same length as the Data Object in DOL)


Page 76


2CA.018.01 Processing DOLs: longer data object length, numeric format (2) Test No: 2CA.018.01 - Revision 12 - 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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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


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).



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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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



the Data Object correctly padded with trailing hexadecimal FF's (portion has the same length as the Data Object in DOL).


Page 78


2CA.019.01 Processing DOLs: longer data object length, compressed numeric format (2) Test No: 2CA.019.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 FF's if the data has a compressed numeric format. By using Dynamic Data Authentication. Reference Book 3 - Section 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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





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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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).



the Data Object correctly padded with trailing hexadecimal zeroes (portion has the same length as the Data Object in DOL).


Page 80


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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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





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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: 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





Page 82


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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0: Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•

LCOLL and UCOLL are not present in LT

•

The DDOL of LT request the LATC






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 Iniate Application

Processing, and remain consistent throughout the transaction Reference Book 2 - Section 8.1 - Application Cryptogram Generation EMV 4.0:

Book 3 - Section 1.4 - Rules for Using a Data Object List (DOL) Book 3 - Section 6.1 - Iniate Application Processing Reference Book 2 - Section 8.1 - Application Cryptogram Generation EMV 4.1:

Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) Book 3 - Section 10.1 - Iniate Application Processing Terminal NA Configuration: Conditions:

•

The PDOL of LT contains the following: -

•

Terminal Country Code Transaction Date

In addtion 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


•

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:


Page 84


2CA.022.00 Data Object List consistency (1) 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



2CA.023.00 Data Object List consistency (2) Test No: 2CA.023.00 - Revision 13 - Number of sub cases: 0 Objective: Data objects requested by PDOL are available during Initiate

Application transaction

Processing,

and

remain

consistent

throughout

the

Reference Book 2 - Section 8.1 - Application Cryptogram Generation EMV 4.0:

Book 3 - Section 1.4 - Rules for Using a Data Object List (DOL) Book 3 - Section 6.1 - Iniate Application Processing Reference Book 2 - Section 8.1 - Application Cryptogram Generation EMV 4.1:

Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) Book 3 - Section 10.1 - Iniate 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 •

In addtion 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 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


Page 86


2CA.023.00 Data Object List consistency (2) Procedure: Application in LT is selected and transaction is performed with LT. Pass Criteria:

•


•

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

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

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



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 2.3.5 - Coding of the Status Bytes EMV 4.0:

Book 3 - Section 2.5.4.4 - Data Field Returned in the Response Message Book 3 - Section 4 - Transaction Flow Book 3 - Section 6.9 - Online Processing Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1:

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


Page 88


2CA.025.00 Normal Processing for EXTERNAL AUTHENTICATE Functions specified in the AIP: Issuer Authentication 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.

•

TSI byte 1, bit 5='1' (ie Issuer authentication was performed) received at 2nd GENERATE AC.



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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: 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


•


•

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.


Page 90


2CA.025.01 ARC checking for contrary response when declining •

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



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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•

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

•


•


•




•


•


•

TSI byte 1, bit 5=’1’ (ie Issuer authentication was performed) received at 2nd GENERATE AC.


Page 92


2CA.025.02 ARC checking for contrary response when approving •

The terminal issues a second GENERATE AC requesting TC

•




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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: Terminal ([Online Only or Offline/Online capable] supported AND [Issuer Configuration: Referral] supported) Conditions:

•


•


•

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

•


•


•




•


•


•

TSI byte 1, bit 5=’1’ (ie Issuer authentication was performed)


Page 94


2CA.025.03 ARC checking for contrary response when issuing a referral received at 2nd GENERATE AC. •

The terminal shall display the “call your bank” message and perform a referral.

•




2CA.026.00 Status Word Processing for EXTERNAL AUTHENTICATE Test No: 2CA.026.00 - Revision 11 - 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 2.3.5 - Coding of the Status Bytes EMV 4.0:

Book 3 - Section 4.1 - Exception Handling Book 3 - Section 6.9 - Online Processing Book Bulletins - Section AN 17 - Bulletin n°17, Terminal Requirements regarding Status Words returned to an EXTERNAL AUTHENTICATE command (Dec-2003) Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1:

Book 3 - Section 8.1 - Exception Handling Book 3 - Section 10.9 - Online Processing Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•

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 03: LT returns status value '63 Cx' in response to EXTERNAL AUTHENTICATE

•


•

Case 05: LT returns status value '69 84' in response to


Page 96


2CA.026.00 Status Word Processing for EXTERNAL AUTHENTICATE EXTERNAL AUTHENTICATE •

Case 06: LT returns status value '6A 81' in response to EXTERNAL AUTHENTICATE

•


•


•


•


•


•


Action: NA Procedure: Application in LT is selected and transaction is started with LT. Pass Criteria:

•


•

TVR byte 5, bit 7 = '1' (ie Issuer Authentication Unsuccessful) received at 2nd GENERATE AC.

•




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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: 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.


Page 98


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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: 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:

•


•

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.



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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: 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

•


Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

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.


Page 100


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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•


•

The following status word are returned on GET DATA for LOATC

•


•



•


•

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.



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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: 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

•


•



•


•

The terminal performs PIN processing


Page 102


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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: Terminal ([Offline Enciphered PIN] supported AND [Get Data for PIN Try Configuration: Counter] supported) Conditions:

•


•

CVM List requests 'Enciphered PIN, if terminal supports' (04 03)

•


•


•



•


•

The terminal performs enciphered PIN processing



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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•


•

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 03: LT returns status '63 Cx' in response to GET DATA command

•


•


•


•

Case 07: LT returns status '6A 82' in response to GET DATA command

•


•



Page 104


2CA.029.08 Status Word Processing for GET DATA •


•


•

Case 12: LT returns status '6D 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.



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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•


•

the following status word are returned on GET DATA for LOATC

•


•


•


•


•


•


•


•


•



Page 106


2CA.029.09 Status Word Processing for GET DATA (2) •


•


•





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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: Terminal ([Get Data for PIN Try Counter] supported AND [Offline Plaintext PIN] Configuration: supported) Conditions:

•


•

CVM List requests 'Plaintext PIN, if terminal supports' (01 03)

•


•


•


•


•


•


•


•


•


•

Case 09: LT returns status '64 00' in response to GET DATA


Page 108


2CA.029.10 Status Word Processing for GET DATA (3) command •


•


•


•

Case 13: LT returns status '6E 00' in response to GET DATA command




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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: Terminal ([Get Data for PIN Try Counter] supported AND [Offline Enciphered Configuration: PIN] supported) Conditions:

•


•

CVM List requests 'Enciphered PIN, if terminal supports' (04 03)

•


•


•


•


•


•


•


•


•


•

Case 09: LT returns status '64 00' in response to GET DATA


Page 110


2CA.029.11 Status Word Processing for GET DATA (4) command •


•


•


•

Case 13: LT returns status '6E 00' in response to GET DATA command




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 2.3.5 - Coding of the Status Bytes EMV 4.0:

Book 3 - Section 6.1 - Initiate Application Processing Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1:

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:

•


•

LT shall receive a GET PROCESSING OPTIONS command following final selection process.


Page 112


2CA.030.05 Failed Processing for GET PROCESSING OPTIONS Test No: 2CA.030.05 - Revision 11 - 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 2.3.5 - Coding of the Status Bytes EMV 4.0:

Book 3 - Section 6.1 - Initiate Application Processing Book 4 - Section 2.3.1 - Initiate Application Processing Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1:

Book 3 - Section 10.1 - Initiate Application Processing Book 4 - Section 6.3.1 - Initiate Application Processing Terminal [Cardholder Confirmation] supported Configuration:

Terminal supports three AIDs (mutually supported by LT) Conditions:

•

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: NA 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 presented for cardholder confirmation.



2CA.030.05 Failed Processing for GET PROCESSING OPTIONS •

The terminal shall process the transaction with Application 2 or Application 3, until completion by requesting a TC or an AAC.


Page 114


2CA.030.06 Failed Processing for GET PROCESSING OPTIONS (2) Test No: 2CA.030.06 - Revision 11 - 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 2.3.5 - Coding of the Status Bytes EMV 4.0:

Book 3 - Section 6.1 - Initiate Application Processing Book 4 - Section 2.3.1 - Initiate Application Processing Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1:

Book 3 - Section 10.1 - Initiate Application Processing Book 4 - Section 6.3.1 - Initiate Application Processing Terminal [Cardholder Confirmation] not supported Configuration:

Terminal supports three AIDs (mutually supported by LT) Conditions:

•

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 value 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,



2CA.030.06 Failed Processing for GET PROCESSING OPTIONS (2) until completion by requesting a TC or an AAC.


Page 116


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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: 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


particular Dynamic Data Authentication). Pass Criteria:

•


•

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.



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 2.3.5 - Coding of the Status Bytes EMV 4.0:

Book 3 - Section 4.1 - Exception Handling Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1:

Book 3 - Section 8.1 - Exception Handling Terminal [DDA] supported Configuration: Conditions:

•


•

Case 01: LT returns status value '62 83' in response to INTERNAL AUTHENTICATE

•


•

Case 03: LT returns status value '63 Cx' in response to INTERNAL AUTHENTICATE

•


•


•


•

Case 07: LT returns status value '6A 81' in response to INTERNAL AUTHENTICATE

•


•


•

Case 10: LT returns status value '6A 88' in response to


Page 118


2CA.031.01 Status Word Processing for Internal Authenticate 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

•


•




•

The terminal shall terminate the transaction



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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: 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



Page 120


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 2.3.5 - Coding of the Status Bytes EMV 4.0: Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1: 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




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 8.3.3 - Using a List of AIDs EMV 4.0:

Book 3 - Section 2.3.5 - Coding of the Status Bytes Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.1:

Book 3 - Section 6.3.5 - Coding of the Status Bytes Terminal Terminal supports the LT applications Configuration: Conditions:

•

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.


Page 122


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 7.1.3 - Command-Response APDU Conventions EMV 4.0:

Book 1 - Section 8.3.2 - Using the Payment Systems Directories Book 3 - Section 2.3.5 - Coding of the Status Bytes Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: 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 06: LT returns status value '6A 83' in response to SELECT PSE

•


•


•


•

Case 10: LT returns status value '65 00' in response to SELECT



2CA.033.02 Status Word Processing for SELECT PSE PSE •


•



•

The terminal shall start the selection by PSE

•

The terminal shall switch to List of AIDs selection

•



Page 124


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 8.3.3 - Using a List of AIDs EMV 4.0:


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



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 2.3.5 - Coding of the Status Bytes EMV 4.0:

Book 3 - Section 6.5.1 - Offline PIN Processing Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1:

Book 3 - Section 10.5.1 - Offline PIN Processing Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•


•

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:

•


•

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.


Page 126


2CA.034.02 Failed Processing for VERIFY •

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.



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 2.3.5 - Coding of the Status Bytes EMV 4.0:


Book 3 - Section 10.5.1 - Offline PIN Processing Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

CVM list is 'Enciphered PIN verification performed by ICC' (04 00)

•

Case 01: LT returns status ''6983" in response to the Verify Command

•



•


•

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)


Page 128


2CA.034.05 Failed Processing for VERIFY (2) received at 1st GENERATE AC.



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.0:

Book 3 - Section 2.3.5 - Coding of the Status Bytes Book 3 - Section 6.5.1 - Offline PIN Processing Book Bulletins - Section SU 21 - Bulletin n°21, Clarification of Actions During Offline Enciphered PIN processing (Nov-2003) Reference Book 2 - Section 7.2 - PIN Encipherment and Verification EMV 4.1:

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:

•


•

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.


Page 130


2CA.034.06 Failed Processing for VERIFY (3) Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

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.

•

TVR byte 3, bit 6='1' (ie PIN Try Limited exceeded) received at 1st GENERATE AC.

•




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 2.3.5 - Coding of the Status Bytes EMV 4.0:


Book 3 - Section 10.5.1 - Offline PIN Processing Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•


•

CVM List is 'Plaintext PIN verification by ICC' (01 00)

•


•



•


•


•



Page 132


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 2.3.5 - Coding of the Status Bytes EMV 4.0:

Book 3 - Section 4.1 - Exception Handling Book Bulletins - Section SU 33 - Bulletin n°33, Clarification of Terminate in the EMV Specification (Apr-2004) Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1:

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 03: LT returns status value '63 Cx' in response to GENERATE AC

•


•


•


•

Case 07: LT returns status value '6A 81' in response to GENERATE AC

•


•




2CA.035.00 Status Word Processing for GENERATE AC •


•


•


•


•

Case 14: LT returns status value '6D 00' in response to GENERATE AC

•

Case 15: LT returns status value '6E 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.


Page 134


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 2.3.5 - Coding of the Status Bytes EMV 4.0:

Book 3 - Section 4.1 - Exception Handling Book Bulletins - Section SU 21 - Bulletin n°21, Clarification of Actions During Offline Enciphered PIN processing (Nov-2003) Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1:

Book 3 - Section 8.1 - Exception Handling Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

CVM is 'Enciphered offline PIN verification, always' (04 00)

•

Case 01: LT returns status value '62 83' in response to GET CHALLENGE

•


•

Case 03: LT returns status value '63 Cx' in response to GET CHALLENGE

•


•


•


•

Case 07: LT returns status value '6A 81' in response to GET CHALLENGE



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

•



•

The terminal shall process the transaction

•

TVR byte 3, bit 8 = '1' (ie Cardholder verification was not successful)


Page 136


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 2.3.5 - Coding of the Status Bytes EMV 4.0:



•

Case 01: LT returns status value '62 83' in response to GET PROCESSING OPTIONS

•


•

Case 03: LT returns status value '63 Cx' in response to GET PROCESSING OPTIONS

•


•


•


•

Case 07: LT returns status value '6A 81' in response to GET PROCESSING OPTIONS

•


•

Case 09: LT returns status value '6A 83' in response to GET



2CA.037.00 Status Word Processing for GET PROCESSING OPTIONS PROCESSING OPTIONS •


•


•


•

Case 13: LT returns status value '6D 00' in response to GET PROCESSING OPTIONS

•

Case 14: LT returns status value '6E 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.


Page 138


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 2.3.5 - Coding of the Status Bytes EMV 4.0:



•

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 07: LT returns status value '6A 81' in response to READ RECORD

•

Case 08: LT returns status value '6A 82' in response to READ



2CA.039.00 Status Word Processing for READ RECORD 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

•


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.


Page 140


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 2.3.5 - Coding of the Status Bytes EMV 4.0:


Book 3 - Section 8.1 - Exception Handling Terminal ([Offline Plaintext PIN] supported OR [Offline Enciphered PIN] Configuration: supported) Conditions:

•


•

LT supports Offline PIN verification.

•

Case 01: LT returns status value '62 83' in response to VERIFY

•


•


•

Case 04: LT returns status value '6A 81' in response to VERIFY

•


•


•


•


•


•




2CA.040.00 Status Word Processing for 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


particular Cardholder verification). Pass Criteria: The terminal shall terminate the transaction.


Page 142


2CA.041.00 Coding of Bits and Bytes RFU Test No: 2CA.041.00 - Revision 10e - 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 2.3.6 - Coding of RFU Data EMV 4.0:

Book 3 - Section 2.5.5.2 - Command Message Book 4 - Section A2 - Terminal Capabilities Book 4 - Section A3 - Additional Terminal Capabilities Book Bulletins - Section SU 17 - Bulletin n°17, Additional Terminal Capabilities - Cash Deposit Transaction Type (Dec-2003) Reference Book 3 - Section 6.3.6 - Coding of RFU Data EMV 4.1:

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 1, byte 5 - bits 4 to 1 are 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.



2CA.041.00 Coding of Bits and Bytes RFU •

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’


Page 144


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 2.3.6 - Coding of RFU Data EMV 4.0: Reference Book 3 - Section 6.3.6 - Coding of RFU Data EMV 4.1: Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•


•

CVM is plaintext PIN always (01 00)


particular Cardholder verification). Pass Criteria:

•

VERIFY qualifier of the Reference Data received by the LT shall have bits 4 to 1 set to ‘0’



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 2.3.6 - Coding of RFU Data EMV 4.0: Reference Book 3 - Section 6.3.6 - Coding of RFU Data EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

CVM is enciphered PIN always (04 00)



•

VERIFY qualifier of the Reference Data received by the LT shall have bits 2 to 1 set to ‘0’


Page 146


2CA.041.03 Coding of Bits and Bytes RFU (4) Test No: 2CA.041.03 - Revision 10a - 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. Reference Book 3 - Section 2.3.6 - Coding of RFU Data EMV 4.0: Reference Book 3 - Section 6.3.6 - Coding of RFU Data EMV 4.1: Terminal NA Configuration: Conditions:

•

IACs RFU bits are set to '0'


•

Terminal shall use and understand the IACs.



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 2.3.6 - Coding of RFU Data EMV 4.0: Reference Book 3 - Section 6.3.6 - Coding of RFU Data EMV 4.1: 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


Page 148


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 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message 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).


•

The terminal shall accept the card and interpret correctly the format 1 syntax.

•


•

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



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 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message 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).


•

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.


Page 150


2CA.056.00 Proprietary Data Object transmitted in Response to GENERATE AC: Format 2 Test No: 2CA.056.00 - Revision 10g - 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 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message Terminal NA Configuration: Conditions: Response to GENERATE AC includes Proprietary Data Object 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.

•




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 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message Terminal NA Configuration: Conditions:

•

CDOL2 requests Application Transaction Counter

•

LT responds with ARQC to First GENERATE AC.


•

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.


Page 152


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 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message 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.


•

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.



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 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message 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.


•

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.


Page 154


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 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message 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



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 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message Terminal [Offline Only or Offline/Online capable] supported Configuration: Conditions:

•

LT response to the first GENERATE AC:

•

Case 01: LT responses an TC without advice (40)

•

Case 02: LT responses an TC with advice and no reason (48)

•

Case 03: LT responses an TC with advice and reason is PIN Try Limit exceeded (4A)

•

Case 04: LT responses an TC with advice and reason is Issuer authentication failed (4B)


completion. Pass Criteria: The terminal shall approve the transaction offline


Page 156


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 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•

LT response to the second GENERATE AC;

•

Case 01: LT responses an TC without advice (40)

•

Case 02: LT responses an TC with advice and no reason (48)

•

Case 03: LT responses an TC with advice and reason is PIN Try Limit exceeded (4A)

•

Case 04: LT responses an TC with advice and reason is Issuer authentication failed (4B)


completion. Pass Criteria: The terminal shall approve the transaction online



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 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message 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)


completion. Pass Criteria: The terminal shall complete the transaction on line


Page 158


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 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message

Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message

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



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 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message 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.


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


Page 160


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 EMV 4.0: Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message

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



•




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 EMV 4.0: Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message

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



•

The terminal shall ignore the advice request and complete the transaction


Page 162


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 2.3.5 - Coding of the Status Bytes EMV 4.0:

Book 3 - Section 2.5.7.1 - Definition and Scope Book 3 - Section 3.2 - Data Retrievable by GET DATA Command Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1:

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)


•

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



2CA.070.00 Syntax of GET DATA returned Data Field (ATC) performed) received at 1st GENERATE AC.


Page 164


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 2.3.5 - Coding of the Status Bytes EMV 4.0:

Book 3 - Section 2.5.7.1 - Definition and Scope Book 3 - Section 3.2 - Data Retrievable by GET DATA Command Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1:

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:

•


•

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)


•

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



2CA.071.00 Syntax of GET DATA returned Data Field (LOATC) performed) received at 1st GENERATE AC.


Page 166


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 2.5.7.1 - Definition and Scope EMV 4.0:

Book 4 - Section 2.3.4.1 - Offline CVM Reference Book 3 - Section 6.5.7.1 - Definition and Scope EMV 4.1:

Book 4 - Section 6.3.4.1 - Offline CVM Terminal ([Get Data for PIN Try Counter] supported AND [Offline Plaintext PIN] Configuration: supported) Conditions:

•


•

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)


•

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.

•




2CA.072.00 Syntax of GET DATA returned Data Field (PIN try limit) Terminal Behaviour When PIN Try Counter Equals 0 •

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.


Page 168


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 2.5.7.1 - Definition and Scope EMV 4.0:

Book 4 - Section 2.3.4.1 - Offline CVM Reference Book 3 - Section 6.5.7.1 - Definition and Scope EMV 4.1:

Book 4 - Section 6.3.4.1 - Offline CVM Terminal ([Get Data for PIN Try Counter] supported AND [Offline Enciphered Configuration: PIN] supported) Conditions:

•


•

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)


•


•


•

TVR byte 3, bit 8 = ‘1’ (ie Cardholder verification was not successful)



2CA.072.01 Syntax of GET DATA returned Data Field (PIN try limit) Terminal Behaviour When PIN Try Counter Equals 0 (2) •


•

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.


Page 170


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 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0:

Book 3 - Section 2.5.8.3 - Data Field Sent in the Command Message Book 3 - Section 6.1 - Initiate Application Processing Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1:

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'



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 2.5.8.3 - Data Field Sent in the Command Message EMV 4.0:

Book 3 - Section 6.1 - Initiate Application Processing Reference Book 3 - Section 6.5.8.3 - Data Field Sent in the Command Message EMV 4.1:

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'


Page 172


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 2.5.8.3 - Data Field Sent in the Command Message EMV 4.0:

Book 3 - Section 6.1 - Initiate Application Processing Reference Book 3 - Section 6.5.8.3 - Data Field Sent in the Command Message EMV 4.1:

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'



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 2.5.8.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.8.4 - Data Field Returned in the Response EMV 4.1: Message 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.


•


•

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


Page 174


2CA.078.00 Syntax of GPO returned Data Field: Format 2 Test No: 2CA.078.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 2. Reference Book 3 - Section 2.5.8.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.8.4 - Data Field Returned in the Response EMV 4.1: Message 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.


•


•

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



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 2.5.9.3 - Data Field Sent in the Command Message EMV 4.0: Reference Book 3 - Section 6.5.9.3 - Data Field Sent in the Command Message EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

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


Page 176


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 2.5.9.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.9.4 - Data Field Returned in the Response EMV 4.1: Message Terminal [DDA] supported Configuration: Conditions:

•


•

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.


•


•

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



2CA.083.00 Syntax of INTERNAL AUTHENTICATE returned Data Field: Format 1 used) received at 1st GENERATE AC. •


•

TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) received at 1st GENERATE AC.


Page 178


2CA.084.00 Syntax of INTERNAL AUTHENTICATE returned Data Field: Format 2 Test No: 2CA.084.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 2 Reference Book 3 - Section 2.5.9.4 - Data Field Returned in the Response EMV 4.0: Message Reference Book 3 - Section 6.5.9.4 - Data Field Returned in the Response EMV 4.1: Message Terminal [DDA] supported Configuration: Conditions:

•


•

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.


•


•


•




2CA.084.00 Syntax of INTERNAL AUTHENTICATE returned Data Field: Format 2 used) received at 1st GENERATE AC. •


•



Page 180


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 7.2.4 - Data Field Returned in the Response Message EMV 4.0:

Book 3 - Section 2.5.11.4 - Data Field Returned in the Response Message Reference Book 1 - Section 11.2.4 - Data Field Returned in the Response EMV 4.1: Message

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.


•


•

Values of PAN and Application Expiration date shall be in accordance of the value returned by the LT.



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 7.3.3 - Data Field Sent in the Command Message EMV 4.0: Reference Book 1 - Section 11.3.3 - Data Field Sent in the Command Message EMV 4.1: 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


Page 182


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 7.3.4 - Data Field Returned in the Response Message EMV 4.0:

Book Bulletins - Section SU 32 - Bulletin n°32, Additional Data Elements facilitating Domestic Processing during Application Selection (Apr-2004) Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response EMV 4.1: Message 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.


•


•

LT shall receive a READ RECORD command with SFI coded according to data returned in FCI



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 7.3.4 - Data Field Returned in the Response Message EMV 4.0:


•

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’)


•


•

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


Page 184


2CA.095.00 Syntax of SELECT DDF returned Data Field Test No: 2CA.095.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 DDF command. Reference Book 1 - Section 7.3.4 - Data Field Returned in the Response Message EMV 4.0:


•

LT contains a PSE

•

LT contains a DDF

•

FCI of DDF contains all mandatory data fields: FCI Template (‘6F’), DF Name (‘84’), FCI Proprietary Template ‘A5’, SFI of the Directory File (‘88’)

•

FCI of DDF contains optional: FCI Issuer discretionary Data (tag BF0C) of DDF contains data fields: '5F54' Bank Identifier Code (BIC), '5F53' International Bank Account Number (IBAN), '5F55' Issuer Country Code (alpha 2), '5F56' Issuer Country Code (aplpha 3), and '42' Issuer Identifier Number.


•


•

LT shall received a READ RECORD command with SFI coded according to data returned in FCI of DDF selected.



2CA.096.00 Syntax of SELECT DDF returned Data Field: optional data (implied) Test No: 2CA.096.00 - Revision 11- Number of sub cases: 0 Objective: To ensure that if the terminal supports selection with PSE, it accepts

the absence of optional data objects in the data field returned by SELECT DDF command. Reference Book 1 - Section 7.3.4 - Data Field Returned in the Response Message EMV 4.0:


•

LT contains a PSE

•

LT contains a DDF

•

FCI of DDF contains all mandatory but no optional data fields: FCI Template (‘6F’), DF Name (‘84’), FCI Proprietary Template ‘A5’, SFI of the Directory File (‘88’)


•


•

LT shall received a READ RECORD command with SFI coded according to data returned in FCI of DDF selected


Page 186


2CA.097.00 Syntax of SELECT ADF returned Data Field Test No: 2CA.097.00 - Revision 11 - 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 7.3.4 - Data Field Returned in the Response Message EMV 4.0:

Book Bulletins - Section SU 4 - Bulletin n°4, Change to status of ‘Presence’ of the Application Label data element (Nov-2001) Book Bulletins - Section SU 32 - Bulletin n°32, Additional Data Elements facilitating Domestic Processing during Application Selection (Apr-2004) Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response EMV 4.1: Message 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’)

•

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’), Application Label (‘50’) 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.


•




2CA.098.00 Syntax of SELECT ADF returned Data Field: optional data Test No: 2CA.098.00 - Revision 12 - 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 7.3.4 - Data Field Returned in the Response Message EMV 4.0:

Book Bulletins - Section SU 4 - Bulletin n°4, Change to status of ‘Presence’ of the Application Label data element (Nov-2001) Book Bulletins - Section SU 32 - Bulletin n°32, Additional Data Elements facilitating Domestic Processing during Application Selection (Apr-2004) Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response EMV 4.1: Message 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 (‘A5’ with a length of ‘00’) (Application Label is an optional data)

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.


Page 188


2CA.099.00 Response to Proprietary Data in FCI from a SELECT ADF Test No: 2CA.099.00 - Revision 15 - 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 7.3.4 - Data Field Returned in the Response Message EMV 4.0:

Book Bulletins - Section AN 15 - Bulletin n°15, Additional Data Allowed in the FCI Returned in Response to a SELECT Command (Dec-2003) Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response EMV 4.1: Message 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


•

The terminal shall ignore the unrecognised or additional EMV data objects

•




2CA.099.01 Response to Proprietary Data in FCI from a SELECT PSE Test No: 2CA.099.01 - Revision 11 - 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 7.3.4 - Data Field Returned in the Response Message EMV 4.0:

Book Bulletins - Section AN 15 - Bulletin n°15, Additional Data Allowed in the FCI Returned in Response to a SELECT Command (Dec-2003) Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response EMV 4.1: Message 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.

•

Case 05: FCI Issuer discretionary Data (tag BF0C) of ADF 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.


•

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


Page 190


2CA.099.01 Response to Proprietary Data in FCI from a SELECT PSE requesting a TC or an AAC.



2CA.099.02 Response to Proprietary Data in FCI from a SELECT DDF Test No: 2CA.099.02 - Revision 11 - Number of sub cases: 4 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 DDF command. Reference Book 1 - Section 7.3.4 - Data Field Returned in the Response Message EMV 4.0:

Book Bulletins - Section AN 15 - Bulletin n°15, Additional Data Allowed in the FCI Returned in Response to a SELECT Command (Dec-2003) Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response EMV 4.1: Message Terminal [PSE] supported Configuration: Conditions:

•

LT contains a PSE.

•

LT contains a DDF.

•

Case 01: FCI (tag 6F) of DDF contains additional proprietary data fields.

•

Case 02: FCI Issuer discretionary Data (tag BF0C) of DDF contains proprietary data field: tag 5F 50 with any length and any value.

•

Case 03: FCI (tag 6F) of DDF contains Issuer Country Code data object.

•

Case 04: FCI Issuer discretionary Data (tag BF0C) of DDF contains Issuer Country Code data object.


•

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.


Page 192


2CA.100.01 Additional data object facilitating domestic processing in selection with PSE Test No: 2CA.100.01 - Revision 11 - 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 Bulletins - Section AN 20 - Bulletin n°20, Additional Data Allowed EMV 4.0: in the Directory Discretionary Template (Apr-2004)

Book Bulletins - Section SU 32 - Bulletin n°32, Additional Data Elements facilitating Domestic Processing during Application Selection (Apr-2004) Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response EMV 4.1: Message


•

LT contains a PSE.

•

Directory Discretionary template (‘73’ template) of the ADF entry contains data fields: '5F54' Bank Identifier Code (BIC), '5F53' International Bank Accounter Number (IBAN), '5F55' Issuer Country Code', '5F56' Issuer Country Code, '42' Issuer Identifier Number.


•


•

Additional data objects facilitating domestic processing are either ignored or used by the terminal.



2CA.100.02 Additional data object facilitating domestic processing in DDF selection Test No: 2CA.100.02 - Revision 11 - 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 DDF selection. Reference Book Bulletins - Section AN 20 - Bulletin n°20, Additional Data Allowed EMV 4.0: in the Directory Discretionary Template (Apr-2004)

Book Bulletins - Section SU 32 - Bulletin n°32, Additional Data Elements facilitating Domestic Processing during Application Selection (Apr-2004) Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response EMV 4.1: Message


•

LT contains a PSE.

•

LT contains a DDF.

•

Directory Discretionary template (‘73’ template) of the DDF entry 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.


•


•

Additional data objects facilitating domestic processing are either ignored or used by the terminal.


Page 194


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 2.5.12.2 - Command Message EMV 4.0:

Book 3 - Section 2.5.12.3 - Data Field Sent in the Command Message Reference Book 3 - Section 6.5.12.2 - Command Message EMV 4.1:

Book 3 - Section 6.5.12.3 - Data Field Sent in the Command Message Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•


•

LT support Offline PIN Verification.

•

CVM in LT is 'Plaintext PIN verification performed by ICC, always' (01 00).

•

Case 01: PIN length is 4.

•


•


•


•


•


•


•




2CA.103.00 Syntax of VERIFY Data Field for option plaintext offline PIN •


Action: NA Procedure: Application in LT is selected and transaction is performed with LT for all

PIN lengths tested. Pass Criteria:

•


•

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).


Page 196


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.0:

Book 3 - Section 2.5.12.2 - Command Message Book 3 - Section 2.5.12.3 - Data Field Sent in the Command Message Reference Book 2 - Section 7.2 - PIN Encipherment and Verification EMV 4.1:

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:

•


•

LT support Enciphered PIN Verification.

•

CVM is 'Offline Enciphered PIN Verification, always' (04 00).

•


•


•


•


•


•




2CA.103.01 Syntax of VERIFY Data Field for Enciphered offline PIN •


•


•


Action: NA Procedure: Application in LT is selected and transaction is performed with LT for all

PIN lengths tested. Pass Criteria:

•


•

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 and Book 2 Table 21 with the value field of tag 99 (without Tag and Length).


Page 198


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 2.5.6.4 - Data Field Returned in the Response EMV 4.0: Message

Book Bulletins - Section SU 21 - Bulletin n°21, Clarification of Actions During Offline Enciphered PIN processing (Nov-2003) Reference Book 3 - Section 6.5.6.4 - Data Field Returned in the Response EMV 4.1: Message Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

LT supports Offline enciphered PIN Verification.

•

CVM is 'Offline enciphered PIN Verification, always' (04 00).


•


•

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.



Application Selection


Page 200


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 7.3.3 - Data Field Sent in the Command Message EMV 4.0: Reference Book 1 - Section 11.3.3 - Data Field Sent in the Command Message EMV 4.1: Terminal [PSE] supported Configuration: Conditions: NA Action: NA Procedure: Application Selection with PSE process is performed. Pass Criteria:

•


•

LT shall received a READ RECORD command with SFI coded according to SFI returned in FCI.



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 8.2.3 - Coding of a Payment System’s Directory EMV 4.0: Reference Book 1 - Section 12.2.3 - Coding of a Payment System Directory EMV 4.1: 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:

•


•

LT shall receive a second READ RECORD command with SFI coded according to SFI returned in FCI of the SELECT PSE command.


Page 202


2CB.005.00 Definition of Directory Entry Format Test No: 2CB.005.00 - Revision 10g - Number of sub cases: 3 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 8.2.3 - Coding of a Payment System’s Directory EMV 4.0:

Book Bulletins - Section AN 20 - Bulletin n°20, Additional Data Allowed in the Directory Discretionary Template (Apr-2004) Reference Book 1 - Section 12.2.3 - Coding of a Payment System Directory EMV 4.1: Terminal [PSE] supported Configuration: Conditions:

•

PSE contains a directory file with entries for ADF.

•

first record of directory file contains:

•

Case 01: Template '70' contains: ‘9F12’ Application Preferred Name, Issuer Identifier Number. '42’

•

Case 02: Template '70' contains: Proprietary tag '5F 50' with max length and any value.

•

Case 03: 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:

•


•

LT shall receive a second READ RECORD command with SFI coded according to SFI returned in FCI of the SELECT PSE command.



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 8.3 - Building the Candidate List EMV 4.0: Reference Book 1 - Section 12.3 - Building the Candidate List EMV 4.1: 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 generates SELECT command for each AID stored within the terminal.


Page 204


2CB.010.00 Matching AIDS: « same AID » criteria supported Test No: 2CB.010.00 - Revision 10g - 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 8.3.1 - Matching Terminal Applications to ICC EMV 4.0: Applications Reference Book 1 - Section 12.3.1 - Matching Terminal Applications to ICC EMV 4.1: Applications 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: NA Procedure: Application Selection using list of AID is performed with LT. Pass Criteria:

•


•

Terminal shall indicate to cardholder which applications can be selected.



2CB.010.01 Matching AIDS: « same AID » criteria supported (2) Test No: 2CB.010.01 - Revision 10g - 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 8.3.1 - Matching Terminal Applications to ICC EMV 4.0: Applications Reference Book 1 - Section 12.3.1 - Matching Terminal Applications to ICC EMV 4.1: Applications 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.


•


•

Terminal shall select the application with the highest priority.


Page 206


2CB.011.00 Matching AIDs: « AID beginning with Terminal AID » criteria supported Test No: 2CB.011.00 - Revision 11 - 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 8.3.1 - Matching Terminal Applications to ICC EMV 4.0: Applications Reference Book 1 - Section 12.3.1 - Matching Terminal Applications to ICC EMV 4.1: Applications Terminal [Cardholder Confirmation] supported Configuration:

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. Conditions:

•

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.

•



•


•




2CB.011.01 Matching AIDs: « AID beginning with Terminal AID » criteria supported (2) Test No: 2CB.011.01 - Revision 11 - 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 8.3.1 - Matching Terminal Applications to ICC EMV 4.0: Applications Reference Book 1 - Section 12.3.1 - Matching Terminal Applications to ICC EMV 4.1: Applications Terminal [Cardholder Confirmation] not supported Configuration:

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. Conditions:

•

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:

•


•

Terminal shall select the application with the highest priority.


Page 208


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 8.3.2 - Using the Payment Systems Directories EMV 4.0:

Book 3 - Section 2.3.5 - Coding of the Status Bytes Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1:

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.


•


•

LT shall receive a SELECT '1PAY.SYS.DDF01' command.



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 8.3.2 - Using the Payment Systems Directories EMV 4.0:

Book 3 - Section 2.3.5 - Coding of the Status Bytes Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1:

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.


Page 210


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 8.3.2 - Using the Payment Systems Directories EMV 4.0: Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: Terminal [PSE] supported Configuration: Conditions:

•

LT contains a PSE directory file with three entries in two records.


•


•

LT shall receive a sequence of READ RECORD commands until the LT answers with '6A 83'.



2CB.016.01 Indicating end of record (2) Test No: 2CB.016.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the terminal supports selection with PSE and a DDF is

present, the terminal selects DDF and sends READ RECORD commands until card responds with '6A 83'. Reference Book 1 - Section 8.3.2 - Using the Payment Systems Directories EMV 4.0: Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: Terminal [PSE] supported Configuration: Conditions:

•

LT contains a PSE Directory file with one entry for a DDF.

•

The DDF Directory file of LT contains 3 entries in 2 records.


•


•

LT shall receive a SELECT DDF command.

•

LT shall receive a sequence of READ RECORD commands until the LT answers with '6A 83' after the DDF selection.


Page 212


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 8.3.2 - Using the Payment Systems Directories EMV 4.0: Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: Terminal [PSE] supported Configuration: Conditions:

•

LT answers '6A 83' to a READ RECORD of the PSE directory file for record number 1.


•


•

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.



2CB.017.01 Directory entry does not exist (2) Test No: 2CB.017.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the terminal supports selection with PSE, if a DDF is

present and the card answers with '6A 83' to a READ RECORD for record number 1, the terminal resumes processing for the previously interrupted directory at the point of interruption. Reference Book 1 - Section 8.3.2 - Using the Payment Systems Directories EMV 4.0: Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: Terminal [PSE] supported Configuration:

Terminal supports Application 3 only Conditions:

•

.LT contains 3 applications (ADF) and a DDF.

•

LT answers '6A 83' to a READ RECORD of the DDF directory file for record number 1.

•

LT contains a PSE Directory file containing all the directory entries (tag ’61) in a single record, with the entries in the following order: 70 || L || 61 || L || ADF1 || 61 || L || ADF2 || 61 || L || DDF1 || 61 || L || ADF3


•


•

LT shall receive several READ RECORD commands for PSE Directory File

•

LT shall receive a SELECT DDF command

•

LT shall receive READ RECORD command for DDF SFI record 1

•

LT shall receive final SELECT ADF command for Application 3.


Page 214


2CB.017.02 Directory entry does not exist (3) Test No: 2CB.017.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the terminal supports selection with PSE, if a DDF is

present and the card answers with '6A 83' to a READ RECORD for record number 1, the terminal resumes processing for the previously interrupted directory at the point of interruption. Reference Book 1 - Section 8.3.2 - Using the Payment Systems Directories EMV 4.0: Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: Terminal [PSE] supported Configuration:

Terminal supports Application 3 only Conditions:

•

.LT contains 3 applications (ADF) and a DDF.

•

LT answers '6A 83' to a READ RECORD of the DDF directory file for record number 1.

•

LT contains a PSE Directory file containing a directory entry (tag ’61) per record (4 records in total) in the following order: o

70 || L || 61 || L || ADF1

o

70 || L || 61 || L || ADF2

o

70 || L || 61 || L || DDF1

o

70 || L || 61 || L || ADF3


•


•

LT shall receive several READ RECORD commands for PSE Directory File

•

LT shall receive a SELECT DDF command

•

LT shall receive a READ RECORD command for PSE Directory



2CB.017.02 Directory entry does not exist (3) File record 4 •

LT shall receive final SELECT ADF command for Application 3.


Page 216


2CB.018.00 Directory entry processing Test No: 2CB.018.00 - Revision 10g - 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 8.3.2 - Using the Payment Systems Directories EMV 4.0: Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: Terminal (([PSE] supported AND [Cardholder Confirmation] supported) AND Configuration: [Preferred Order] not supported)

Terminal supports all ADFs listed in the directory of the LT (for selection process only). Conditions:

•

LT contains a Directory file with three entries in one record.

•

All applications in the LT have no priorities.


•


•

All mutually supported applications shall be displayed to the Cardholder.



2CB.018.01 Directory entry processing (2) Test No: 2CB.018.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the terminal supports selection with PSE and if a DDF

is present, the terminal begins with the first entry of first record of the DDF directory file and processes each entry in turn. Reference Book 1 - Section 8.3.2 - Using the Payment Systems Directories EMV 4.0: Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: Terminal (([PSE] supported AND [Cardholder Confirmation] supported) AND Configuration: [Preferred Order] not supported)

Terminal supports all ADFs listed in the directories of the LT (for selection process only). Conditions:

•

LT contains a PSE Directory file with entries for (in the following order) application 1, DDF, applications 2 and 3.

•

The of LT contains DDF Directory file with 2 entries (listing the 2 applications of the DDF).

•

LT contains 3 applications (ADF) and a DDF (all listed in the PSE Directory file).

•

DDF of LT contains 2 applications (applications 4 and 5).

•

all applications have the same priority.


•


•

All mutually supported applications shall be displayed to the Cardholder.


Page 218


2CB.019.01 Candidate list with exact match (2) Test No: 2CB.019.01 - Revision 10g - Number of sub cases: 3 Objective: To ensure that if the terminal supports selection with PSE and a DDF is

present, 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 8.3.2 - Using the Payment Systems Directories EMV 4.0:

Book Bulletins - Section AN 6 - Bulletin n°6, Clarification to Application Selection (Jun-2002) Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: Terminal ([PSE] supported AND [Cardholder Confirmation] supported) Configuration:


•

LT contains a PSE Directory file with entries for application 1, a DDF, applications 2 and 3.

•

LT contains a DDF Directory file with 2 entries (listing the 2 applications of the DDF).

•

LT contains the 3 applications (ADF) and the DDF (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: NA



2CB.019.01 Candidate list with exact match (2) Procedure: Application Selection with PSE process is performed. Pass Criteria:

•


•

all applications, including the DDF applications, are in the list presented to the cardholder.


Page 220


2CB.019.02 Candidate list with exact match (3) Test No: 2CB.019.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the terminal supports selection with PSE and a DDF is

present, 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 8.3.2 - Using the Payment Systems Directories EMV 4.0:

Book Bulletins - Section AN 6 - Bulletin n°6, Clarification to Application Selection (Jun-2002) Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: Terminal ([PSE] supported AND [Cardholder Confirmation] not supported) Configuration:

Terminal supports all ADFs listed in the directories of the LT (for the selection process). Conditions:

•


•


•


•


•

Application 5 has the highest priority.

•

All AIDs of the LT application exactly match the ones supported by the terminal.


•


•

The terminal select the application with the highest priority.



2CB.019.04 Candidate list with partial match (2) Test No: 2CB.019.04 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the terminal supports selection with PSE and a DDF is

present, 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 8.3.2 - Using the Payment Systems Directories EMV 4.0:

Book Bulletins - Section AN 6 - Bulletin n°6, Clarification to Application Selection (Jun-2002) Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: 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.

•


•


•


•


•

All AIDs of LT applications partially match the ones supported by the terminal.


•


•

all applications, including the DDF applications, are in the list presented to the cardholder.


Page 222


2CB.019.05 Candidate list with partial match (3) Test No: 2CB.019.05 - Revision 10g - 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 8.3.2 - Using the Payment Systems Directories EMV 4.0:

Book Bulletins - Section AN 6 - Bulletin n°6, Clarification to Application Selection (Jun-2002) Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: 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.

•


•


•


•


•

Application 5 has the highest priority.

•

All AIDs of the LT applications partially match the ones supported by the terminal.


•




2CB.019.05 Candidate list with partial match (3) •

The terminal selects the application with the highest priority.


Page 224


2CB.021.00 DDF entry Test No: 2CB.021.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that if the terminal supports selection with PSE, the terminal

is able to process DDF entries and select the DDF indicated. Reference Book 1 - Section 8.3.2 - Using the Payment Systems Directories EMV 4.0:

Book Bulletins - Section AN 6 - Bulletin n°6, Clarification to Application Selection (Jun-2002) Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: Terminal [PSE] supported Configuration:


•

LT contains a PSE Directory file with entries for 3 applications, and a DDF.

•

LT contains a DDF Directory file with 2 entries.

•

LT contains 3 applications (ADF) and a DDF (all listed in the PSE Directory file).

•

Case 01: in DDF Directory file all entries have priorities and the highest priority is on the first entry.

•

Case 02: in DDF Directory file all entries have priorities and the highest priority is on the second entry.


•


•

The LT shall receive a SELECT DDF command for the appropriate DDF.



2CB.022.00 Status Word Processing for SELECT DDF Test No: 2CB.022.00 - Revision 11 - Number of sub cases: 13 Objective: To ensure if a status word error occurs (ie not ’90 00’) in PSE

Application Selection, SELECT DDF, the terminal clears the candidate list and switches to List of AIDs selection. Reference Book 1 - Section 8.3.2 - Using the Payment Systems Directories EMV 4.0:

Book 3 - Section 2.3.5 - Coding of the Status Bytes Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1:

Book 3 - Section 6.3.5 - Coding of the Status Bytes Terminal [PSE] supported Configuration:

Terminal supports all ADF listed in the directories of the LT (for selection process only) Conditions:

•

LT contains PSE.

•

The LT and terminal contain 3 mutually supported applications, 1 of these stored in a subsequent DDF entry

•

Case 01: LT returns status value '63 00' in response to SELECT DDF

•

Case 02: LT returns status value '63 Cx' in response to SELECT DDF

•


•


•


•

Case 06: LT returns status value '6A 83' in response to SELECT DDF

•



Page 226


2CB.022.00 Status Word Processing for SELECT DDF •


•


•


•


•


•



•

The terminal shall clear the PSE candidate list

•

The terminal shall switch to List of AIDs selection, transmitting a SELECT command for each AID it supports.

•




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 8.3.2 - Using the Payment Systems Directories EMV 4.0: Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: 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 switch to the AID list method.


Page 228


2CB.023.01 Failed Processing for READ RECORD in selection by PSE Test No: 2CB.023.01 - Revision 11 - Number of sub cases: 12 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 8.3.2 - Using the Payment Systems Directories EMV 4.0:

Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: 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

•


•


•


•


•


•


•




2CB.023.01 Failed Processing for READ RECORD in selection by PSE •


•


•


•


Action: NA 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


Page 230


2CB.023.02 Failed Processing for READ RECORD in selection by PSE (2) Test No: 2CB.023.02 - Revision 11 - Number of sub cases: 12 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 8.3.2 - Using the Payment Systems Directories EMV 4.0:

Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 12.3.2 - Using the PSE EMV 4.1: Terminal [PSE] supported Configuration: Conditions:

•

LT contains PSE.

•

LT contains DDF.

•

LT and terminal contain 3 mutually supported applications

•

The 2nd READ RECORD command for the DDF Application Selection returns the following status value

•


•


•


•


•


•




2CB.023.02 Failed Processing for READ RECORD in selection by PSE (2) •


•


•


•


•


•


Action: NA 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:

•


•


•



Page 232


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 8.3.3 - Using a List of AIDs EMV 4.0: Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.1: Terminal Terminal supports several Applications. Configuration: Conditions: NA Action: NA Procedure: Application Selection using list of AID is performed. Pass Criteria:

•


•

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.



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 8.3.3 - Using a List of AIDs EMV 4.0: Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.1: Terminal 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 issue at least three SELECT commands including a "final" SELECT command.


Page 234


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 8.3.3 - Using a List of AIDs EMV 4.0: Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.1: Terminal Configuration:

•

Terminal supports selection by AID.

•

Terminal supports at least two applications.

Conditions: 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 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.



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 8.3.3 - Using a List of AIDs EMV 4.0:


Book 3 - Section 6.3.5 - Coding of the Status Bytes Terminal Terminal supports at least 3 AIDs mutually supported by LT. Configuration: Conditions:

•

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 06: LT returns status value of '6A 82' in response to SELECT Application.

•


•


•



Page 236


2CB.028.00 Selection using a list of AIDs •


•


Action: NA Procedure: Application Selection using list of AIDs is performed. Pass Criteria:

•


•

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.



2CB.029.00 Selection using a list of AIDs: candidate list completion Test No: 2CB.029.00 - Revision 10g - 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 8.3.3 - Using a List of AIDs EMV 4.0: Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.1: Terminal [Cardholder Confirmation] 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: NA Procedure: Application Selection using list of AID is performed. Pass Criteria:

•


•

The LT shall receive SELECT AID commands for all AIDs in the terminal list.

•



Page 238


2CB.031.00 Application Selection Indicator: One Occurrence Permitted Test No: 2CB.031.00 - Revision 12 - 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 reissues the SELECT command with P2 set to '02'. Reference Book 1 - Section 8.3.3 - Using a List of AIDs EMV 4.0: Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.1: 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.


•


•

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. Copyright © 2008 EMVCo, LLC. All Rights Reserved. Page 239


2CB.031.00 Application Selection Indicator: One Occurrence Permitted •

The terminal will not store the first AID as a selectable application.


Page 240


2CB.031.06 DF name longer than AID & multiple occurrence & application not blocked Test No: 2CB.031.06 - Revision 10g - 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 8.3.3 - Using a List of AIDs EMV 4.0: Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.1: Terminal Configuration:

Conditions:

•

Terminal supports at least one AID.

•

Terminal Application Selection Indicator allows multiple occurrences for selected AID.

•

DF Names contained in FCI returned 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.

•

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.



2CB.031.06 DF name longer than AID & multiple occurrence & application not blocked Pass Criteria:

•


•

After the first SELECT AID command, the LT shall receive several SELECT 'AIDs' with P2 option set to 'next'.

•

The terminal shall store the AID from the SELECT NEXT command responding '90 00' in the candidate list.


Page 242


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 8.3.3 - Using a List of AIDs EMV 4.0: Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.1: Terminal 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.


•


•

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.




Page 244


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 8.3.3 - Using a List of AIDs EMV 4.0: Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.1: Terminal Terminal supports at least 2 AIDs Configuration: Conditions:

•

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.


•


•

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.



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 8.3.3 - Using a List of AIDs EMV 4.0: Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.1: Terminal Configuration:

Conditions:

•

Terminal's Application Selection Indicator allows multiple occurrences for the AID.

•

Terminal supports at least 2 AIDs.

•


•

LT returns '90 00' to a SELECT command with 'next' option (3 applications with same beginning of AID in LT).


•


•

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.


Page 246


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 8.3.3 - Using a List of AIDs EMV 4.0: Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.1: Terminal Terminal supports at least 2 AIDs Configuration: Conditions:

•


•

LT returns '62 83' to first SELECT command with 'next' option.

•

LT returns '6A 82' to following SELECT command with 'next' option.


•


•

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.



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 8.3.3 - Using a List of AIDs EMV 4.0: Reference Book 1 - Section 12.3.3 - Using a List of AIDs EMV 4.1: Terminal Terminal supports at least 2 AIDs Configuration: Conditions:

•


•

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 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.

•


•



Page 248


2CB.036.00 Multiple occurrence of application: next option failed: other •


•


•



•


•

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.



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 8.3.4 - Final Selection EMV 4.0: Reference Book 1 - Section 12.4 - Final Selection EMV 4.1: 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.


Page 250


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 8.3.4 - Final Selection EMV 4.0:

Book Bulletins - Section AN 9 - Bulletin n°9, Application Priority Indicator (Mar-2003) Reference Book 1 - Section 12.4 - Final Selection EMV 4.1: Terminal NA Configuration: Conditions:

•

There is one matching AID between LT and Terminal.

•

b8 of Application Indicator returned by LT equals 0.


•


•

The terminal shall select the mutually supported AID.



2CB.039.00 Final Selection: cardholder confirmation Test No: 2CB.039.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, the terminal requests confirmation and selects the application if the cardholder approves. Reference Book 1 - Section 8.3.4 - Final Selection EMV 4.0:

Book Bulletins - Section AN 9 - Bulletin n°9, Application Priority Indicator (Mar-2003) Reference Book 1 - Section 12.4 - Final Selection EMV 4.1: Terminal [Cardholder Confirmation] supported Configuration: Conditions:

•


•


Action: Cardholder approves the selection. Procedure: Application Selection using list of AIDs is performed. Pass Criteria:

•


•

The terminal shall request confirmation from the cardholder and shall generate a SELECT AID command as response to that confirmation.


Page 252


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 8.3.4 - Final Selection EMV 4.0:

Book Bulletins - Section AN 9 - Bulletin n°9, Application Priority Indicator (Mar-2003) Reference Book 1 - Section 12.4 - Final Selection EMV 4.1: Terminal [Cardholder Confirmation] not supported Configuration: Conditions:

•


•


Action: NA Procedure: Application Selection using list of AIDs or PSE method. Pass Criteria: The terminal shall terminate the transaction.



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 8.3.4 - Final Selection EMV 4.0:

Book Bulletins - Section AN 9 - Bulletin n°9, Application Priority Indicator (Mar-2003) Reference Book 1 - Section 12.4 - Final Selection EMV 4.1: Terminal [Cardholder Confirmation] supported Configuration: Conditions:

•


•


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.


Page 254


2CB.042.00 Displaying Application to Cardholder: priority sequence Test No: 2CB.042.00 - Revision 11 - 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 8.3.4 - Final Selection EMV 4.0: Reference Book 1 - Section 12.4 - Final Selection EMV 4.1: Terminal [Cardholder Confirmation] supported Configuration: Conditions:

•

There are three matching AIDs between LT and Terminal.

•

Applications have different priorities.


•


•

The terminal shall display a list of applications ordered in priority sequence (highest priority first).



2CB.042.01 Displaying Application to Cardholder when cardholder confirmation is supported Test No: 2CB.042.01 - Revision 11 - 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 AN 9 - Bulletin n°9, Application Priority EMV 4.0: Indicator (Mar-2003) Reference EMV 4.1: Terminal [Cardholder Confirmation] supported Configuration: Conditions:

•



•


•

The terminal shall display a complete list of mutually supported applications.


Page 256


2CB.049.00 Terminal Selection of Application without Cardholder Assistance Test No: 2CB.049.00 - Revision 11 - 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 8.3.4 - Final Selection EMV 4.0:


•


•


•

No confirmation is required in Application priority indicator.

•

Terminal does not present the list to the cardholder.


•


•

The terminal shall select the application with highest priority and shall generate the SELECT AID command (with AID=application with highest priority).



2CB.050.00 Terminal Selection of Application without Cardholder Assistance: confirmation required Test No: 2CB.050.00 - Revision 11 - 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 8.3.4 - Final Selection EMV 4.0:


•


•


•

Application with highest priority requires cardholder confirmation.

•

Terminal does not present the list to the cardholder.


•


•

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).


Page 258


2CB.053.00 Final Selection of Application from Candidate List: list of AID Test No: 2CB.053.00 - Revision 11 - 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 8.3.4 - Final Selection EMV 4.0: Reference Book 1 - Section 12.4 - Final Selection EMV 4.1: Terminal [Cardholder Confirmation] not supported Configuration: Conditions:

•


•


•

Terminal uses selection using list of AIDs process.


•


•

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.



2CB.053.01 Final Selection of Application from Candidate List: list of AID (2) Test No: 2CB.053.01 - Revision 11 - 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 8.3.4 - Final Selection EMV 4.0: Reference Book 1 - Section 12.4 - Final Selection EMV 4.1: Terminal [Cardholder Configuration] supported Configuration: Conditions:

•


•


•

Terminal uses selection using list of AIDs process.

Action: Cardholder selects one application Procedure: Application Selection using list of AIDs is performed. Pass Criteria:

•


•

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.


Page 260


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 8.3.4 - Final Selection EMV 4.0: Reference Book 1 - Section 12.4 - Final Selection EMV 4.1: Terminal [PSE] supported Configuration: Conditions:

•

LT supports PSE.

•


•


•

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:

•


•

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.



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 8.3.4 - Final Selection EMV 4.0: Reference Book 1 - Section 12.4 - Final Selection EMV 4.1: Terminal NA Configuration: Conditions:

•


•


•

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 03: LT returns status value of '63 Cx' in response to SELECT on final selection.

•


•


•


•

Case 07: LT returns status value of '6A 81' in response to SELECT on final selection.

•



Page 262


2CB.055.00 Final Selection of Application from Candidate List: SELECT status different from 90 00 •


•


•


•


•


Action: NA Procedure: Application Selection using PSE or List of AIDs is performed. Pass Criteria:

•


•

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.



Security Aspects


Page 264


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 EMV 4.0: Reference Book 2 - Section 5 - Static Data Authentication (SDA) EMV 4.1: 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 06: LT contains proper static signature and associated data based on the Certification Authority Public Index 05 and



2CC.003.00 Terminal shall be able to store 6 CA Index per RID RID 1. •


•


•


•


•


•


•


•


•


•


•


•

Case 18: LT contains proper static signature and associated


Page 266


2CC.003.00 Terminal shall be able to store 6 CA Index per RID 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:

•


•

TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication succeeded) received at 1st GENERATE AC.

•


•

TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not used) received at 1st GENERATE AC.

•




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 EMV 4.0:

Book 2 - Section B2.1 - RSA Algorithm Book 2 - Section B3.1 - Secure Hash Algorithm (SHA-1) Reference Book 2 - Section 5 - Static Data Authentication (SDA) EMV 4.1:

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'.

•




•


•

TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication


Page 268


2CC.004.00 Algorithm For SDA succeeded) received at 1st GENERATE AC. •


•


•




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.0: Reference Book 2 - Section 5.1 - Keys and Certificates EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

Static signature in LT is valid.

•

length of moduli used are multiple of 8.

•


•

Case 01: Test is made for the CA key.

•

Case 02: Test is made for the Issuer key.



•


•


•


•


•



Page 270


2CC.007.00 Value of Certification Authority Public Key Exponent Test No: 2CC.007.00 - Revision 10g - 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.0: Reference Book 2 - Section 5.1 - Keys and Certificates EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•


•

Case 01: Exponent of Certification Authority Public Key is 3.

•

Case 02: Exponent of Certification Authority Public Key is 2^16 + 1.



•


•


•


•


•




2CC.008.00 Value of Issuer Public Key Exponent Test No: 2CC.008.00 - Revision 10g - Number of sub cases: 2 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.0: Reference Book 2 - Section 5.1 - Keys and Certificates EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•


•

Case 01: Exponent of Issuer Public Key is 3.

•

Case 02: Exponent of Issuer Public Key is 2^16 + 1.



•


•


•


•


•



Page 272


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 the Certification Authority Public Key EMV 4.0:

Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC Reference Book 2 - Section 5.2 - Retrieval of Certification Authority Public Key EMV 4.1:

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.

•




•


•

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.

•


•


•

TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was



2CC.009.00 Data missing: CA Public Key Index performed) received at 1st GENERATE AC.


Page 274


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.0: Reference Book 2 - Section 5.1 - Keys and Certificates EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

Issuer Public Key Certificate is missing in LT.

•




•


•


•


•


•


•




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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

Issuer Public key Exponent is missing in LT.

•




•


•


•


•


•


•



Page 276


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.0:

Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC Reference Book 2 - Section 5.1 - Keys and Certificates EMV 4.1:

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.

•




•


•


•


•


•


•




2CC.012.00 Data missing: Signed Static Application data performed) received at 1st GENERATE AC.


Page 278


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 the Certification Authority Public Key EMV 4.0: Reference Book 2 - Section 5.2 - Retrieval of Certification Authority Public Key EMV 4.1: Terminal [SDA] supported Configuration:

Terminal does not contain the Certification Authority Public Key referenced in LT. Conditions:

•




•


•


•


•


•




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 the Certification Authority Public Key EMV 4.0: Reference Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key EMV 4.1: Terminal [DDA] supported Configuration:


•



•


•

TVR byte 1, bit 4 = '1' (ie Offline Dynamic Data Authentication failed) received at 1st GENERATE AC.

•


•


•



Page 280


2CC.014.02 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent Test No: 2CC.014.02 - Revision 13 - 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 the Certification Authority Public Key EMV 4.0: Reference Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key EMV 4.1:

Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [CDA failure detected prior TAA] supported Configuration:


•

AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = 1).


•

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.

•


•


•




2CC.014.03 Retrieving CA Public Key used to Perform PIN Encryption: Key absent Test No: 2CC.014.03 - Revision 10g - 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 the Certification Authority Public Key EMV 4.0: Reference Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration:


•


•

CVM requires 'Enciphered PIN verification Offline' (04 00).


•


•


•

TSI byte 1, bit 7 = '1' (ie Cardholder verification was performed) received at 1st GENERATE AC.


Page 282


2CC.014.04 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent (2) Test No: 2CC.014.04 - Revision 13 - 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 EMV 4.0: Reference Book 2 - Section 6.2 - Retrieval of Certification Authority Public Key EMV 4.1:

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 AND [CDA failure not detected prior TAA] supported


•


•

IAC’s and TAC’s are set so that TC is requested at first Gen AC.


•

The terminal shall either terminate the transaction and not perform a second GENERATE AC or decline the transaction by performing a second GENERATE AC requesting an AAC when card responds with ARQC at first GENERATE AC.

•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data Authentication failed) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example..

•




2CC.014.04 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent (2) •


•

TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TSI value in any form such as receipt for example..


Page 284




Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA request at Configuration: GENAC1, ARQC] supported AND [CDA failure not detected prior TAA]

supported Terminal does not contain the Certification Authority Public Key referenced in LT. Conditions:

•


•

LT returns an ARQC to the first Gen AC

•

IAC’s and TAC’s are set so that an ARQC is requested at first Gen AC and a TC at second Gen AC.


•

The terminal shall decline the transaction by performing a second GENERATE AC requesting an AAC.

•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data Authentication failed) received at 2nd GENERATE AC.

•


•





TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) received at 2nd GENERATE AC.


Page 286


2CC.014.06 Retrieving CA Public Key used to Perform Combined DDA/AC: Key absent (3) Test No: 2CC.014.06 - Revision 13a - Number of sub cases: 0 Objective: To ensure that if the terminal supports Combined DDA/AC Data


Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA never at Configuration: GENAC1, ARQC] supported AND [CDA request at GENAC2, TC]

supported AND [CDA failure not detected prior TAA] supported Terminal does not contain the Certification Authority Public Key referenced in LT. Conditions:

•


•


•


•

Issuer response indicates an approval


•

The terminal shall decline the transaction

•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC 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 or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example...





•


•

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 or terminated transaction) or if the terminal has the capability to show the TSI value in any form such as receipt for example..in case of AAC and no second GENERATE AC, this pass criteria apply only if the terminal has the capability to store declined transaciton).


Page 288




Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA never at Configuration: GENAC1, ARQC] supported AND [Normal Default Action Code

processing] supported AND [CDA failure not detected prior TAA] supported Terminal does not contain the Certification Authority Public Key referenced in LT. Conditions:

•


•


•


•

Terminal is unable to go online


•

The terminal shall decline the transaction.

•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC 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 or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example...





•


•

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 or terminated transaction) or if the terminal has the capability to show the TSI value in any form such as receipt for example.


Page 290


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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

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.



•


•


•


•


•




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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

Issuer Public Key Certificate in LT is calculated with a Data Trailer different from 'BC'.

•




•


•


•


•


•



Page 292


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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

Issuer Public Key Certificate in LT is calculated with a Data Header different from '6A'.

•




•


•


•


•


•




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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

Issuer Public Key Certificate in LT is calculated with a Certificate Format different from '02'.

•




•


•


•


•


•



Page 294


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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

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.



•


•


•


•


•





Page 296


2CC.021.00 Issuer Identifer 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

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 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.



•


•


•


•

TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not



2CC.021.00 Issuer Identifer does not match leftmost 3-8 PAN digits used) received at 1st GENERATE AC. •



Page 298


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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

Issuer Public Key Certificate in LT is calculated with Certificate Expiration Date earlier than the current date.

•




•


•


•


•


•




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 revocated Certificate. Reference Book 2 - Section 5.3 - Retrieval of the Issuer Public Key EMV 4.0: Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.1:

Book Bulletins - Section SU 52 - Bulletin n°52, Certification revocation Lists (Feb-2007) Terminal ([SDA] supported AND [Key Revocation] supported) Configuration:

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) Conditions:

•

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.

•


•


Action: NA Procedure: Application in LT is selected, for each RID as specified in each case,

and transaction is processed with LT (in particular Static Data Authentication). Pass Criteria:

•

The terminal shall process the transaction until completion, by


Page 300


2CC.023.00 RID, CA Public Key Index and Certificate Serial Number not valid,SDA requesting a TC or an AAC. •


•


•


•




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 EMV 4.0: Reference Book Bulletins - Section SU 52 - Bulletin n°52, Certification revocation EMV 4.1: Lists (Feb-2007) 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 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 correcponding 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

•


•

TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication succesful) received at 1st GENERATE AC.


Page 302


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 EMV 4.0: Reference Book Bulletins - Section SU 52 - Bulletin n°52, Certification revocation EMV 4.1: Lists (Feb-2007) 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:

•


•


•


•

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 correcponding to this valid entry.


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:

•


•




2CC.023.02 Certification Revocation List update, addition failed) received at 1st GENERATE AC. •


•


•



Page 304


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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

Issuer Public Key Certificate in LT is calculated with Issuer Public Key Algorithm value different from '01'.

•




•


•


•


•


•




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 the Signed Static Application Data EMV 4.0: Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

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.



•


•


•


•


•



Page 306


2CC.028.00 Recover 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 the Signed Static Application Data EMV 4.0: Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

Signed Static Application Data in LT is calculated with a Data Trailer different from 'BC'.

•




•


•


•


•


•




2CC.029.00 Recover 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 the Signed Static Application Data EMV 4.0: Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

Signed Static Application Data in LT is calculated with a Data Header different from '6A'.

•




•


•


•


•


•



Page 308


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 the Signed Static Application Data EMV 4.0: Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

Signed Static Application Data in LT is calculated with a Certificate Format different from '03'.

•




•


•


•


•


•




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 the Signed Static Application Data EMV 4.0: Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

Signed Static Application Data in LT is calculated with a bad Hash value.

•




•


•


•


•


•



Page 310


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 the Signed Static Application Data EMV 4.0: Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

Case 01: SDA Tag List contains AFL

•

Case 02: SDA Tag List contains AFL and AIP



•


•

TVR byte 1, bit 7 = '1' (ie Offline SDA failed) received at 1st GENERATE AC.

•


•


•




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 the Signed Static Application Data EMV 4.0: Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

SDA Tag List contains tag '82' (AIP).



•


•

TVR byte 1, bit 7 = '0' (ie Offline SDA succeeded) received at 1st GENERATE AC.

•


•


•



Page 312


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 the Signed Static Application Data EMV 4.0: Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

CDOL1 requests Tag '9F 45'.

•

Data Authentication Code is 'DA C0'.



•


•


•


•


•


•

Value of Tag '9F 45' is 'DA C0' received at 1st GENERATE AC.



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 keyrelated 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 - Dynamic Data Authentication EMV 4.0: Reference Book 2 - Section 6 - Offline Dynamic Data Authentication EMV 4.1: Terminal [DDA] supported Configuration:

Conditions:

•

Terminal supports two RIDs (RIDs 1 and RIDs 2).

•


•


•

Case 01: LT generates proper good dynamic signature and associated data based on the Certification Authority Public Index 01 and RID 1.

•


•


•


•


•



Page 314


2CC.036.00 Terminal shall be able to store 6 CA Index per RID Action: NA Procedure: Application in LT is selected and transaction is processed with LT (in


•


•

TVR byte 1, bit 4= '0' (ie Offline Dynamic Data Authentication succeeded) received at 1st GENERATE AC.

•


•


•




2CC.036.01 Terminal shall be able to store 6 CA Index per RID (2) Test No: 2CC.036.01 - Revision 11 - Number of sub cases: 0 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 - Dynamic Data Authentication EMV 4.0: Reference Book 2 - Section 6 - Offline Dynamic Data Authentication EMV 4.1: Terminal [CDA] supported Configuration:

Conditions:

•


•

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.

•


•


•


•


•


•


•



Page 316


2CC.036.01 Terminal shall be able to store 6 CA Index per RID (2) Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

TVR byte 1, bit 3 = '0' (ie Offline Combined DDA/AC Data Authentication succeeded) contained in Financial Confirmation message or Batch Data Capture message.

•


•


•

TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) contained in Financial Confirmation message or Batch Data Capture message.



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: 0 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 - Dynamic Data Authentication EMV 4.0: Reference Book 2 - Section 6 - Offline Dynamic Data Authentication EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration:

Conditions:

•


•


•


•

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 07: LT contains associated data based on the Certification


Page 318


2CC.036.02 Terminal shall be able to store 6 CA Index per RID (3) Authority Public Index 00 and RID 2. •


•


•


•


•



•


•


•

TSI byte 1, bit 7 ='1' (ie Cardholder Verification was performed) received at 1st GENERATE AC.



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.0: Recovery

Book 2 - Section B2.1 - RSA Algorithm Book 2 - Section B3.1 - Secure Hash Algorithm (SHA-1) Reference Book 2 - Section A2.1 - Digital Signature Scheme Giving Message EMV 4.1: 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).

•


•

ICC Public Key Certificate in LT is calculated with ICC Public Key Algorithm 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


Page 320


2CC.037.00 Algorithm for DDA (AIP byte 1 bit 6 = 1). Action: NA Procedure: Application in LT is selected and transaction is processed with LT (in


•


•

TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication succeeded) received at 1st GENERATE AC.

•


•


•




2CC.037.01 Algorithm for DDA (2) Test No: 2CC.037.01 - Revision 11 - 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.0: Recovery

Book 2 - Section B2.1 - RSA Algorithm Book 2 - Section B3.1 - Secure Hash Algorithm (SHA-1) Reference Book 2 - Section A2.1 - Digital Signature Scheme Giving Message EMV 4.1: 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).

•


•


•


•


•



Page 322


2CC.037.01 Algorithm for DDA (2) Action: NA Procedure: Application in LT is selected and transaction is processed with LT (in


•


•

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 4 = '0' 'ie Dynamic Data Authentication not used) received at 1st GENERATE AC.

•




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.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1: 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.

•




•


•


•


•


•



Page 324


2CC.039.01 Bit Length of All Moduli (2) Test No: 2CC.039.01 - 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 Combined Dynamic Data Authentication Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•

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).


particular Combined Data Authentication). Pass Criteria:

•


•


•


•


•




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.0: Reference Book 2 - Section 7.1 - Keys and Certificates EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

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.


•


•

TVR byte 3, bit 8 = '0' (ie Cardholder verification succeeded) received at 1st GENERATE AC.

•



Page 326


2CC.040.00 Value of CA Public Key Exponent Test No: 2CC.040.00 - Revision 10g - 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 Dynamic Data Authentication. Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•


•


•




•


•


•


•


•




2CC.040.01 Value of CA Public Key Exponent (2) Test No: 2CC.040.01 - Revision 11 - 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.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•


•


•



•


•


•


•


•



Page 328


2CC.040.02 Value of CA Public Key Exponent (3) Test No: 2CC.040.02 - Revision 10g - 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.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•

LT supports Offline PIN encryption.

•


•


•


•



•


•


•




2CC.041.00 Value of Issuer Public Key Exponent Test No: 2CC.041.00 - Revision 10g - Number of sub cases: 2 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.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•


•


•

Case 02: Exponent of Issuer Public Key is 2^16 +1.



•


•


•


•


•



Page 330


2CC.041.01 Value of Issuer Public Key Exponent (2) Test No: 2CC.041.01 - Revision 11 - Number of sub cases: 2 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.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•


•


•




•


•


•


•


•




2CC.041.02 Value of Issuer Public Key Exponent (3) Test No: 2CC.041.02 - Revision 10g - Number of sub cases: 2 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.0:

Book 2 - Section 7.1 - Keys and Certificates Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1:

Book 2 - Section 7.1 - Keys and Certificates Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•


•


•



•


•


•



Page 332


2CC.042.00 Value of ICC Public Key Exponent Test No: 2CC.042.00 - Revision 10g - Number of sub cases: 2 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.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•


•

Case 01: Exponent of ICC Public Key is 3.

•

Case 02: Exponent of ICC Public Key is 2^16 + 1.



•


•


•


•


•




2CC.042.01 Value of ICC Public Key Exponent (2) Test No: 2CC.042.01 - Revision 11 - Number of sub cases: 2 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.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•

AIP of LT indicates Combined DDA/AC Data Authentication is supported (AIP byte 1 bit 1 = 1).

•


•



•


•


•


•


•



Page 334


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.0:


Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC Terminal [DDA] supported Configuration: Conditions:

•


•

Index of Certification Authority Public Key is missing in LT.



•


•


•


•


•


•




2CC.043.00 Data missing: CA Public Key Index performed) received at 1st GENERATE AC.


Page 336


2CC.043.01 Data missing: CA Public Key Index (2) Test No: 2CC.043.01 - Revision 13 - 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.0:


Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [CDA failure detected prior TAA] supported Configuration: Conditions:

•


•



•


•


•


•


•




2CC.043.01 Data missing: CA Public Key Index (2) •


•



Page 338



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 EMV 4.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1:

Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC 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 AND [CDA failure not detected prior TAA] supported Conditions:

•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data Authentication failed) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example.




TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example.

•


•


•

TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TSI value in any form such as receipt for example.


Page 340




Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA request at Configuration: GENAC1, ARQC] supported AND [CDA failure not detected prior TAA]

supported Conditions:

•


•


•


•



•


•


•

TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 2nd GENERATE AC.





•


•



Page 342


2CC.043.04 Data missing: CA Public Key Index (5) Test No: 2CC.043.04 - Revision 13a - Number of sub cases: 0 Objective: To ensure that if the Certification Authority Public Key index is missing


Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA never at Configuration: GENAC1, ARQC] supported AND [CDA request at GENAC2, TC]

supported AND [CDA failure not detected prior TAA] supported Conditions:

•


•


•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC 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 or terminated transaction) or if the terminal has the capability to



2CC.043.04 Data missing: CA Public Key Index (5) show the TVR value in any form such as receipt for example. •

TVR byte 1, bit 6 = '1' (ie ICC data missing) contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example.

•


•


•



Page 344




Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA never at Configuration: GENAC1, ARQC] supported AND [Normal Default Action Code

processing] supported AND [CDA failure not detected prior TAA] supported Conditions:

•


•


•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data Authentication failed) or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or



2CC.043.05 Data missing: CA Public Key Index (6) terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example. •


•


•


•



Page 346


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.0:



•


•




•


•


•


•


•


•




2CC.044.00 Data missing: Issuer Public Key Certificate performed) received at 1st GENERATE AC.


Page 348


2CC.044.01 Data missing: Issuer Public Key Certificate (2) Test No: 2CC.044.01 - Revision 13 - 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.0:



•


•



•


•


•


•


•


•




2CC.044.01 Data missing: Issuer Public Key Certificate (2) used) received at 1st GENERATE AC. •



Page 350



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 EMV 4.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1:


•


•


•



•


•


•

TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 2nd



2CC.044.02 Data missing: Issuer Public Key Certificate (3) GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message . •


•


•



Page 352






•


•


•


•



•


•


•


•

TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used)



2CC.044.03 Data missing: Issuer Public Key Certificate (3) received at 1st GENERATE AC. •


•



Page 354


2CC.044.04 Data missing: Issuer Public Key Certificate (4) Test No: 2CC.044.04 - Revision 13a - Number of sub cases: 0 Objective: To ensure that if the Issuer Public key Certificate is missing in ICC, the




•


•


•


•


•



•


•




2CC.044.04 Data missing: Issuer Public Key Certificate (4) show the TVR value in any form such as receipt for example. •


•


•


•



Page 356






•


•


•


•


•

Terminal is unable to go online.


•


•




2CC.044.05 Data missing: Issuer Public Key Certificate (6) show the TVR value in any form such as receipt for example. •

TVR byte 1, bit 6 = '1' (ie ICC data missing) contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TSI value in any form such as receipt for example.

•


•


•



Page 358


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.0:



•


•




•


•


•


•


•


•




2CC.045.00 Data missing: Issuer PK Exponent performed) received at 1st GENERATE AC.


Page 360


2CC.045.01 Data missing: Issuer PK Exponent (2) Test No: 2CC.045.01 - Revision 13 - 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.0:



•


•



•


•


•


•


•


•




2CC.045.01 Data missing: Issuer PK Exponent (2) used) received at 1st GENERATE AC. •



Page 362



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 EMV 4.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1:


•


•


•

IAC’s and TAC’s are set so that TC is requested at first Gen AC


•


•


•




2CC.045.02 Data missing: Issuer PK Exponent (3) GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example. •


•


•



Page 364






•


•


•


•



•


•


•


•




2CC.045.03 Data missing: Issuer PK Exponent (4) received at 1st GENERATE AC. •


•



Page 366


2CC.045.04 Data missing: Issuer PK Exponent (5) Test No: 2CC.045.04 - Revision 13a - Number of sub cases: 0 Objective: To ensure that if the Issuer Public key Exponent is missing in ICC, the




•


•


•


•


•



•


•




2CC.045.04 Data missing: Issuer PK Exponent (5) show the TVR value in any form such as receipt for example. •


•


•


•



Page 368






•


•


•


•


•



•


•




2CC.045.05 Data missing: Issuer PK Exponent (6) show the TVR value in any form such as receipt for example. •


•


•


•



Page 370


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.0:



•


•

ICC Public Key Certificate is missing in LT.



•


•


•


•


•


•




2CC.046.00 Data missing: ICC Public Key Certificate performed) received at 1st GENERATE AC.


Page 372


2CC.046.01 Data missing: ICC Public Key Certificate (2) Test No: 2CC.046.01 - Revision 13 - 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.0:



•


•



•


•


•


•


•


•




2CC.046.01 Data missing: ICC Public Key Certificate (2) used) received at 1st GENERATE AC. •



Page 374


2CC.046.02 Data missing: ICC Public Key Certificate (3) Test No: 2CC.046.02 - 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 Offline PIN Encryption process. Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.0:



•

AIP of LT indicates Cardholder veirification is supported (AIP byte 1 bit 5 = 1).

•


•



•


•

TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received at 1st GENERATE AC.

•




2CC.046.03 Data missing: ICC PIN Encryption Public Key Certificate Test No: 2CC.046.03 - Revision 10g - 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.0:



•

AIP of LT indicates Cardholder veirification is supported (AIP byte 1 bit 5 = 1).

•


•

ICC PIN Encipherment Public Key Certificate is missing in LT.


•


•


•



Page 376



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 EMV 4.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1:


•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data Authentication failed) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message

•

TVR byte 1, bit 6 = '1' (ie ICC data missing) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or



2CC.046.04 Data missing: ICC Public Key Certificate (5) terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example. •


•


•



Page 378




Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND ([CDA request at Configuration: GENAC1, ARQC] OR [Normal Default Action Code processing])


•


•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data Authentication failed) received at 2nd GENERATE AC

•


•




2CC.046.05 Data missing: ICC Public Key Certificate (6) received at 1st GENERATE AC. •


•



Page 380


2CC.046.06 Data missing: ICC Public Key Certificate (7) Test No: 2CC.046.06 - Revision 13a - Number of sub cases: 0 Objective: To ensure that if the ICC Public key Certificate is missing in ICC, the




•


•


•


•


•



•


•




2CC.046.06 Data missing: ICC Public Key Certificate (7) show the TVR value in any form such as receipt for example •


•


•


•



Page 382






•


•


•


•


•



•


•




2CC.046.07 Data missing: ICC Public Key Certificate (8) show the TVR value in any form such as receipt for example •


•


•


•



Page 384


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.0:



•


•

ICC Public key Exponent is missing in LT.



•


•


•


•


•


•




2CC.047.00 Data missing: ICC Public Key Exponent performed) received at 1st GENERATE AC.


Page 386


2CC.047.01 Data missing: ICC Public Key Exponent (2) Test No: 2CC.047.01 - Revision 13 - 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.0:



•


•



•


•


•


•


•


•




2CC.047.01 Data missing: ICC Public Key Exponent (2) used) received at 1st GENERATE AC. •



Page 388


2CC.047.02 Data missing: ICC Public Key Exponent (3) Test No: 2CC.047.02 - 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 Offline PIN Encryption process. Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.0:



•

AIP of LT indicates Cardholder verification is supported (AIP byte 1 bit 5 = 1).

•


•



•


•


•




2CC.047.03 Data missing: ICC PIN Enccryption Public Key Exponent Test No: 2CC.047.03 - Revision 10g - 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.0:



•


•


•

ICC PIN Encipherment Public Key Exponent is missing in LT.


•


•


•



Page 390



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 EMV 4.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1:


•


•


•



•


•


•




2CC.047.04 Data missing: ICC Public Key Exponent (5) GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example. •


•


•



Page 392






•


•


•


•



•


•


•


•




2CC.047.05 Data missing: ICC Public Key Exponent (6) received at 1st GENERATE AC. •


•



Page 394


2CC.047.06 Data missing: ICC Public Key Exponent (7) Test No: 2CC.047.06 - Revision 13a - Number of sub cases: 0 Objective: To ensure that if the ICC Public key Exponent is missing in ICC, the




•


•


•


•


•



•


•




2CC.047.06 Data missing: ICC Public Key Exponent (7) show the TVR value in any form such as receipt for example. •


•


•


•



Page 396






•


•


•


•


•



•


•




2CC.047.07 Data missing: ICC Public Key Exponent (8) show the TVR value in any form such as receipt for example. •


•


•


•



Page 398


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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•


•




•

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.

•




2CC.050.01 Length of Issuer Public Key Certificate (2) Test No: 2CC.050.01 - Revision 13 - 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:

Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [CDA failure detected prior TAA] supported Configuration: Conditions:

•


•


•



•


•


•


•


•


•



Page 400


2CC.050.02 Length of Issuer Public Key Certificate (3) Test No: 2CC.050.02 - Revision 11 - 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 the Issuer Public Key EMV 4.0:

Book 2 - Section 7.1 - Keys and Certificates Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•


•


•



•


•

TVR byt 3, bit 8 = '1' (ie Cardholder verification failed) received at 1st GENERATE AC.

•





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 EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:

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 AND [CDA failure not detected prior TAA] supported Conditions:

•


•


•


•



•


•


•



Page 402


2CC.050.03 Length of Issuer Public Key Certificate (4) •


•






Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND ([CDA request at Configuration: GENAC1, ARQC] OR [Normal Default Action Code processing])


•


•


•


•


•



•


•


•


•



Page 404






2CC.050.05 Length of Issuer Public Key Certificate (6) Test No: 2CC.050.05 - Revision 13a - Number of sub cases: 2 Objective: To ensure that if the terminal supports Combined DDA/AC Data




•


•


•


•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC 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 or terminated transaction).

•



Page 406


2CC.050.05 Length of Issuer Public Key Certificate (6) 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 the terminal has the capability to store declined or terminated transaction).







•


•


•


•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC 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 or terminated transaction).


Page 408




•


•

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 or terminated transaction).



2CC.052.00 Recover 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•




•


•


•


•


•



Page 410


2CC.052.01 Recover Data Trailer not equal to 'BC' (2) Test No: 2CC.052.01 - Revision 13 - 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•



•


•


•


•


•


•




2CC.052.02 Recover Data Trailer not equal to 'BC' (3) Test No: 2CC.052.02 - Revision 10g - 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 the Issuer Public Key EMV 4.0:



•


•


•



•


•


•



Page 412



Authentication process, if the Data Trailer recovered from the Issuer Public Key Certificate does not equal 'BC'. Reference EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•


•



•


•


•


•




2CC.052.03 Recover Data Trailer not equal to 'BC' (4) used) received at 1st GENERATE AC. •



Page 414






•


•


•


•



•


•


•


•


•




2CC.052.04 Recover Data Trailer not equal to 'BC' (5) performed) received at 2nd GENERATE AC.


Page 416


2CC.052.05 Recover Data Trailer not equal to 'BC' (6) Test No: 2CC.052.05 - Revision 13a - Number of sub cases: 0 Objective: To ensure that the terminal fails the Combined DDA/AC Data




•


•


•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC 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 or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example.

•




2CC.052.05 Recover Data Trailer not equal to 'BC' (6) •


•

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 or terminated transaction) or if the terminal has the capability to show the TSI value in any form such as receipt for example.


Page 418






•


•


•


•


•



•


•


•




2CC.052.06 Recover Data Trailer not equal to 'BC' (7) received at 1st GENERATE AC. •


•



Page 420


2CC.053.00 Recover 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•




•


•


•


•


•




2CC.053.01 Recover Data Header not equal to '6A' (2) Test No: 2CC.053.01 - Revision 13 - 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•



•


•


•


•


•


•



Page 422


2CC.053.02 Recover Data Header not equal to '6A' (3) Test No: 2CC.053.02 - Revision 10g - 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 the Issuer Public Key EMV 4.0:



•


•


•



•


•


•





Authentication process, if the Data Header recovered from the Issuer Public Key Certificate does not equal '6A'. Reference EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•


•



•


•


•


•



Page 424


2CC.053.03 Recover Data Header not equal to '6A' (4) •








•


•


•


•



•


•


•


•


•



Page 426


2CC.053.05 Recover Data Header not equal to '6A' (6) Test No: 2CC.053.05 - Revision 13a - Number of sub cases: 0 Objective: To ensure that the terminal fails the Combined DDA/AC Data




•


•


•


•


•



•


•


•






•



Page 428






•


•


•


•


•



•


•


•




2CC.053.06 Recover Data Header not equal to '6A' (7) received at 1st GENERATE AC. •


•



Page 430


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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•




•


•


•


•


•




2CC.054.01 Certificate Format not equal to '02' (2) Test No: 2CC.054.01 - Revision 13 - 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•



•


•


•


•


•


•



Page 432


2CC.054.02 Certificate Format not equal to '02' (3) Test No: 2CC.054.02 - Revision 10g - 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 the Issuer Public Key EMV 4.0:



•


•


•



•


•


•





Authentication process, if the Certificate Format recovered from Issuer Public Key Certificate does not equal '02'. Reference EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•


•



•


•


•


•



Page 434


2CC.054.03 Certificate Format not equal to '02' (4) •








•


•


•


•



•


•


•


•


•



Page 436


2CC.054.05 Certificate Format not equal to '02' (6) Test No: 2CC.054.05 - Revision 13a - Number of sub cases: 0 Objective: To ensure that the terminal fails the Combined DDA/AC Data




•


•


•


•


•



•


•


•






•



Page 438






•


•


•


•


•



•


•


•




2CC.054.06 Certificate Format not equal to '02' (7) received at 1st GENERATE AC. •


•



Page 440


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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•


•


•




•


•


•


•


•





Page 442


2CC.055.01 Difference between calculated Hash Result and recovered Hash Result (2) Test No: 2CC.055.01 - Revision 13 - 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•


•


•



•


•


•


•


•




2CC.055.01 Difference between calculated Hash Result and recovered Hash Result (2) •



Page 444


2CC.055.02 Difference between calculated Hash Result and recovered Hash Result (3) Test No: 2CC.055.02 - Revision 10g - 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 the Issuer Public Key EMV 4.0:



•


•


•


•


•



•


•


•





Authentication process, if the calculated Hash Result is different from the Hash Result recovered from the Issuer Public Key Certificate. Reference EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•


•


•


•



•


•


•



Page 446


2CC.055.03 Difference between calculated Hash Result and recovered Hash Result (4) received at 1st GENERATE AC. •


•








•


•


•


•


•


•



•


•


•


•



Page 448


2CC.055.04 Difference between calculated Hash Result and recovered Hash Result (5) used) received at 1st GENERATE AC. •




2CC.055.05 Difference between calculated Hash Result and recovered Hash Result (6) Test No: 2CC.055.05 - Revision 13a - Number of sub cases: 2 Objective: To ensure that the terminal fails the Combined DDA/AC Data




•


•


•


•


•


•


•



•


•



Page 450




•


•








•


•


•


•


•


•


•



•


•



Page 452


2CC.055.06 Difference between calculated Hash Result and recovered Hash Result (7) show the TVR value in any form such as receipt for example. •


•


•




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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•


•


•




•


•


•


•


•



Page 454


2CC.056.00 Issuer Identifier does not match leftmost 3-8 PAN digits performed) received at 1st GENERATE AC.



2CC.056.01 Issuer Identifier does not match leftmost 3-8 PAN digits (2) Test No: 2CC.056.01 - Revision 13 - 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•


•


•



•


•


•


•



Page 456


2CC.056.01 Issuer Identifier does not match leftmost 3-8 PAN digits (2) •


•




2CC.056.02 Issuer Identifier does not match leftmost 3-8 PAN digits (3) Test No: 2CC.056.02 - Revision 10g - 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 the Issuer Public Key EMV 4.0:



•


•


•


•


•



•


•


•



Page 458





Authentication process, if the Recovered Issuer Identifier does not match the leftmost 3-8 PAN digits. Reference EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•


•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data Authentication failed) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal


Page 460


2CC.056.03 Issuer Identifier does not match leftmost 3-8 PAN digits (4) has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example. •


•


•








•


•


•


•


•


•



•


•



Page 462




•


•




2CC.056.05 Issuer Identifier does not match leftmost 3-8 PAN digits (6) Test No: 2CC.056.05 - Revision 13a - Number of sub cases: 3 Objective: To ensure that the terminal fails the Combined DDA/AC Data




•


•


•


•


•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data


Page 464


2CC.056.05 Issuer Identifier does not match leftmost 3-8 PAN digits (6) 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 or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example. •


•


•








•


•


•


•


•


•


•



•



Page 466




•


•


•




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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•




•


•


•


•


•



Page 468


2CC.057.01 Certificate Expiration Date earlier than today's date (2) Test No: 2CC.057.01 - Revision 13 - 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•



•


•


•


•

TVR byte 1, bit 7 = '0' 'ie Static Data Authentication not used) received at 1st GENERATE AC.

•


•




2CC.057.02 Certificate Expiration Date earlier than today's date (3) Test No: 2CC.057.02 - Revision 10g - 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 the Issuer Public Key EMV 4.0:



•


•


•



•


•


•



Page 470



Authentication process, if the Certificate Expiration Date is earlier than the current date. Reference EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•


•



•


•


•


•




2CC.057.03 Certificate Expiration Date earlier than today's date (4) used) received at 1st GENERATE AC. •



Page 472






•


•


•


•



•


•


•


•


•




2CC.057.04 Certificate Expiration Date earlier than today's date (5) performed) received at 2nd GENERATE AC.


Page 474


2CC.057.05 Certificate Expiration Date earlier than today's date (6) Test No: 2CC.057.05 - Revision 13a - Number of sub cases: 0 Objective: To ensure that the terminal fails the Combined DDA/AC Data




•


•


•


•


•



•


•


•




2CC.057.05 Certificate Expiration Date earlier than today's date (6) •


•



Page 476






•


•


•


•


•



•


•


•

TVR byte 1, bit 7 = '0' 'ie Static Data Authentication not used)



2CC.057.06 Certificate Expiration Date earlier than today's date (7) received at 1st GENERATE AC. •


•



Page 478


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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:

Book Bulletins - Section SU 52 - Bulletin n°52, Certification revocation Lists (Feb-2007) Terminal ([DDA] supported AND [Key Revocation] supported) Configuration:

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) Conditions:

•


•


•


•


•



and transaction is processed with LT (in particular Dynamic Data Copyright © 2008 EMVCo, LLC. All Rights Reserved. Page 479


2CC.058.00 RID, CA Public Key Index and Certificate Serial Number not valid, DDA Authentication). Pass Criteria:

•


•


•


•


•



Page 480


2CC.058.01 RID, CA Public Key Index and Certificate Serial Number not valid, CDA (2) Test No: 2CC.058.01 - Revision 13 - Number of sub cases: 0 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:

Book Bulletins – Section SU 44 – Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Book Bulletins - Section SU 52 - Bulletin n°52, Certification revocation Lists (Feb-2007) Terminal ([CDA] supported AND [Key Revocation] supported) AND [CDA failure Configuration: detected prior TAA] supported

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) Conditions:

•


•


•


•


•




2CC.058.01 RID, CA Public Key Index and Certificate Serial Number not valid, CDA (2) 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:

•


•


•


•


•


•



Page 482


2CC.058.02 RID, CA Public Key Index and Certificate Serial Number not valid, Offline Enciphered PIN Test No: 2CC.058.02 - 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 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 the Issuer Public Key EMV 4.0:


Book 2 - Section 7.1 - Keys and Certificates Book Bulletins - Section SU 52 - Bulletin n°52, Certification revocation Lists (Feb-2007) Terminal ([Offline Enciphered PIN] supported AND [Key Revocation] supported) Configuration:

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) Conditions:

•


•


•


•


•


•

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



2CC.058.02 RID, CA Public Key Index and Certificate Serial Number not valid, Offline Enciphered PIN 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:

•


•


•



Page 484


2CC.058.03 RID, CA Public Key Index and Certificate Serial Number not valid (4) Test No: 2CC.058.03 - Revision 13 - Number of sub cases: 0 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 EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:

Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Book Bulletins – Section SU 52 – Bulletin n°52, Certification revocation Lists (Feb-2007) Terminal [CDA] supported AND [Key Revocation] supported AND [CDA failure Configuration: not detected prior TAA] supported AND ([Offline Only] OR

[Offline/Online capable]) supported 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) Conditions:

•


•


•

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 valid entry in the revocation list of the terminal.

•

Case 01 – The terminal is loaded with the 30 CRL entries, specified above, for RID 1.

•




2CC.058.03 RID, CA Public Key Index and Certificate Serial Number not valid (4) •




•


•


•


•


•



Page 486


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 EMV 4.0: Reference Book Bulletins - Section SU 52 - Bulletin n°52, Certification revocation EMV 4.1: Lists (Feb-2007) Terminal ([DDA] supported AND [Key Revocation] supported) Configuration:


•


•


•


•

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 correcpond to this valid entry.


performed to update the CRL. Application in LT is selected and transaction is processed with LT (in particular Dynamic Data Authentication). Pass Criteria:r

•


•

TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication succesful) received at 1st GENERATE AC.



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 EMV 4.0: Reference Book Bulletins - Section SU 52 - Bulletin n°52, Certification revocation EMV 4.1: Lists (Feb-2007) Terminal ([DDA] supported AND [Key Revocation] supported) Configuration:


•


•


•


•

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 correcponding to this valid entry.


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

•


•

TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication not used) received at 1st GENERATE AC.

•



Page 488


2CC.058.05 Certification Revocation List update, addition (2) used) received at 1st GENERATE AC. •

TVR byte 1, bit 4 = '1' (ie Dynamic Data Authentication failed) received at 1st GENERATE AC.

•




2CC.058.06 Certification Revocation List update, removal (3) Test No: 2CC.058.06 - Revision 16 - 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 EMV 4.0: Reference Book Bulletins - Section SU 52 - Bulletin n°52, Certification revocation EMV 4.1: Lists (Feb-2007) Terminal [CDA] supported AND [Key Revocation] supported Configuration:


•


•


•


•

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 correcpond to this valid entry.


performed to update the CRL. Application in LT is selected and transaction is processed with LT (in particular Combined Data Authentication). Pass Criteria:

•


•


•

TVR byte 1, bit 3 = '0' (ie Combined Data Authentication succesful) contained in Financial confirmation messages or Batch Data Capture message.


Page 490


2CC.058.06 Certification Revocation List update, removal (3) •

TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not used) contained in Financial confirmation messages or Batch Data Capture message.

•




2CC.058.07 Certification Revocation List update, addition (3) Test No: 2CC.058.07 - Revision 16 - 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 EMV 4.0: Reference Book Bulletins - Section SU 52 - Bulletin n°52, Certification revocation EMV 4.1: Lists (Feb-2007) Terminal [CDA] supported AND [Key Revocation] supported Configuration:


•


•


•


•

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 correcpond to this valid entry.


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 Criteriar

•


•

TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed) contained in Financial confirmation messages or Batch Data Capture message.


Page 492




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 EMV 4.0: Reference Book Bulletins - Section SU 52 - Bulletin n°52, Certification revocation EMV 4.1: Lists (Feb-2007) Terminal ([Offline Enciphered PIN ] supported AND [Key Revocation] supported) Configuration:


•


•


•


•


•

A valid CRL entry is removed from the device, where the LT . Issuer Public Key Certificate iis calculated with RID, CA Public Key Index and Certificate Serial Number correcponding 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

•


•

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)


Page 494


2CC.058.08 Certification Revocation List update, removal (4) received at 1st GENERATE AC.



2CC.058.09 Certification Revocation List update, addition (4) Test No: 2CC.058.09 - Revision 13a - Number of sub cases: 0 Objective: To ensure that the terminal is able to update the Certification

Revocation List by adding an entry. Reference EMV 4.0: Reference Book Bulletins - Section SU 52 - Bulletin n°52, Certification revocation EMV 4.1: Lists (Feb-2007) Terminal [Offline Enciphered PIN ] supported AND [Key Revocation] supported Configuration:


•


•


•


•


•

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 correcponding 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

•


•


•



Page 496






Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Book Bulletins – Section SU 52 – Bulletin n°52, Certification revocation Lists (Feb-2007) Terminal [CDA] supported AND [Key Revocation] supported AND [CDA failure Configuration: not detected prior TAA] supported AND [Online Only] supported AND

[CDA request at GENAC1, ARQC] supported 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) Conditions:

•


•


•


•


•


•



Page 498






•


•


•


•


•




2CC.058.11 RID, CA Public Key Index and Certificate Serial Number not valid (6) Test No: 2CC.058.11 - Revision 13a - Number of sub cases: 0 Objective: To ensure that when supporting Certification Revocation List (CRL),


Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Book Bulletins – Section SU 52 – Bulletin n°52, Certification revocation Lists (Feb-2007) Terminal [CDA] supported AND [Key Revocation] supported AND [Online Only] Configuration: supported AND [CDA never at GENAC1, ARQC] supported AND [CDA

request at GENAC2, TC] supported AND [CDA failure not detected prior TAA] supported 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) Conditions:

•


•


•


•


•


•



Page 500




•




•


•


•


•


•






Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Book Bulletins – Section SU 52 – Bulletin n°52, Certification revocation Lists (Feb-2007) Terminal [CDA] supported AND [Key Revocation] supported AND [CDA failure Configuration: not detected prior TAA] supported AND [Online Only] supported AND

[CDA never at GENAC1, ARQC] supported AND [Normal Default Action Code processing] supported 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) Conditions:

•


•


•


•


•


•



Page 502




•




•


•


•


•


•




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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•




•


•


•


•


•



Page 504


2CC.059.01 Issuer Public Key Algorithm not recognized (2) Test No: 2CC.059.01 - Revision 13 - 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•



•


•


•


•


•


•




2CC.059.02 Issuer Public Key Algorithm not recognized (3) Test No: 2CC.059.02 - Revision 10g - 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 the Issuer Public Key EMV 4.0:



•


•


•



•


•


•



Page 506



Authentication process, if the Issuer Public Key Algorithm is not supported (different from '01'). Reference EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:


•


•


•



•


•


•


•




2CC.059.03 Issuer Public Key Algorithm not recognized (4) used) received at 1st GENERATE AC. •



Page 508






•


•


•


•



•


•


•


•


•




2CC.059.04 Issuer Public Key Algorithm not recognized (5) performed) received at 2nd GENERATE AC.


Page 510


2CC.059.05 Issuer Public Key Algorithm not recognized (6) Test No: 2CC.059.05 - Revision 13a - Number of sub cases: 0 Objective: To ensure that the terminal fails the Combined DDA/AC Data




•


•


•


•


•



•


•


•




2CC.059.05 Issuer Public Key Algorithm not recognized (6) •


•



Page 512






•


•


•


•


•



•


•


•




2CC.059.06 Issuer Public Key Algorithm not recognized (7) received at 1st GENERATE AC. •


•



Page 514


2CC.060.00 Issuer Identifier wtih 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 5.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

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 03: Issuer Public Key Certificate in LT is calculated using Issuer Identifier with lentgh of 8 digits.


•


•

TVR byte 1, bit 4 = '0' (ie Offline Dynamic 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.

•




2CC.060.00 Issuer Identifier wtih length between 3 to 8 digits performed) received at 1st GENERATE AC.


Page 516


2CC.060.01 Issuer Identifier wtih 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•

AIP of LT indicates Dynamic Data Authentication is supported (AIP byte 1 bit 6= 1).

•


•


•

Case 03: Issuer Public Key Certificate in LT is calculated using Issuer Identifier with length of 8 digits.


•


•


•


•


•




2CC.060.01 Issuer Identifier wtih length between 3 to 8 digits (2) performed) received at 1st GENERATE AC.


Page 518


2CC.060.02 Issuer Identifier wtih length between 3 to 8 digits (2) Test No: 2CC.060.02 - Revision 16 - 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1:

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:

•


•

TAC/IAC set to request a TC in the 1st GENERATE AC, and LT responds TC

•


•


•



•

The terminal shall process the transaction until completion, by requesting a TC.

•


•

TVR byte 1, bit 3 = '0' (ie Combined Data Authentication succeeded) received at 1st GENERATE AC, at 2nd GENERATEC AC and in Financial message or Batch Data



2CC.060.02 Issuer Identifier wtih length between 3 to 8 digits (2) Capture message. •


•



Page 520


2CC.060.03 Issuer Identifier wtih 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 the Issuer Public Key EMV 4.0: Reference Book 2 - Section 6.3 - Retrieval of Issuer Public Key EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

AIP of LT indicates data authentication is not supported (AIP B1b7=0, B1b6=0, B1b1=1).

•


•


•


•

Case 03: Issuer Public Key Certificate in LT is calculated using Issuer Identifier with lentgh of 8 digits.


•


•


•




2CC.060.03 Issuer Identifier wtih length between 3 to 8 digits (3) 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.


Page 522




Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [Online Only] AND [CDA] supported AND ([CDA request at GENAC1, Configuration: ARQC] OR [CDA request at GENAC2, TC]) Conditions:

•


•

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.

•


•


•



•


•




2CC.060.04 Issuer Identifier wtih length between 3 to 8 digits (4) •

TVR byte 1, bit 3 = '0' (ie Combined Data Authentication succeeded) contained in Financial Confirmation message or Batch Data Capture message.

•


•



Page 524




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:

•


•

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.

•


•


•


•



•


•

TVR byte 1, bit 4 = '0' (ie Offline Dynamic Data Authentication



2CC.060.05 Issuer Identifier wtih length between 3 to 8 digits (5) 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.

•


•



Page 526


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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

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.



•


•


•


•


•




2CC.061.01 Length of ICC Public Key Certificate (2) Test No: 2CC.061.01 - Revision 13 - 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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•


•



•


•


•


•


•


•



Page 528


2CC.061.02 Length of ICC Public Key Certificate (3) Test No: 2CC.061.02 - Revision 11 - 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 the ICC Public Key EMV 4.0:

Book 2 - Section 7.1 - Keys and Certificates Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•

CVM List is 'Enciphered PIN, if terminal supports' (04 03)

•


•



•


•


•




2CC.061.03 Length of ICC PIN Encipherment Public Key Certificate Test No: 2CC.061.03 - Revision 11 - 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 the ICC Public Key EMV 4.0:



•


•


•

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.


•


•


•



Page 530



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 EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data Authentication failed) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message ( this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example.



2CC.061.04 Length of ICC Public Key Certificate (5) •


•


•

TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message ( this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TSI value in any form such as receipt for example.


Page 532






•


•


•


•


•



•


•


•




2CC.061.05 Length of ICC Public Key Certificate (6) •


•



Page 534


2CC.061.06 Length of ICC Public Key Certificate (7) Test No: 2CC.061.06 - Revision 13a - Number of sub cases: 2 Objective: To ensure that if the terminal supports Combined DDA/AC Data




•


•


•


•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC 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 or terminated transaction) or if the terminal has the capability to



2CC.061.06 Length of ICC Public Key Certificate (7) show the TVR value in any form such as receipt for example. •


•


•



Page 536






•


•


•


•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC 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 or



2CC.061.07 Length of ICC Public Key Certificate (8) terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example. •


•


•



Page 538



process, if the Data Trailer recovered from the ICC Public Key Certificate does not equal 'BC'. Reference Book 2 - Section 6.4 - Retrieval of the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

ICC Public Key Certificate in LT is calculated with a Data Trailer different from 'BC'.



•


•


•


•


•





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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•



•


•


•


•


•


•



Page 540


2CC.063.02 Recover Data Trailer not equal to 'BC' (3) Test No: 2CC.063.02 - Revision 11 - 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 the ICC Public Key EMV 4.0:



•


•


•



•


•


•




2CC.063.03 Recover Data Trailer not equal to 'BC' (4) Test No: 2CC.063.03 - Revision 11 - 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 the ICC Public Key EMV 4.0:



•


•


•

ICC PIN Encipherment Public Key Certificate in LT is calculated with a Data Trailer different from 'BC'.


•


•


•



Page 542



Authentication process, if the Data Trailer recovered from the ICC Public Key Certificate does not equal 'BC'. Reference EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•


•



•


•


•


•




2CC.063.04 Recover Data Trailer not equal to 'BC' (5) used) received at 1st GENERATE AC. •



Page 544






•


•


•


•



•


•


•


•


•




2CC.063.05 Recover Data Trailer not equal to 'BC' (6) performed) received at 2nd GENERATE AC.


Page 546


2CC.063.06 Recover Data Trailer not equal to 'BC' (7) Test No: 2CC.063.06 - Revision 13a - Number of sub cases: 0 Objective: To ensure that the terminal fails the Combined DDA/AC Data




•


•


•


•


•



•


•


•




2CC.063.06 Recover Data Trailer not equal to 'BC' (7) •


•



Page 548






•


•


•


•


•



•


•


•




2CC.063.07 Recover Data Trailer not equal to 'BC' (8) received at 1st GENERATE AC. •


•



Page 550



process, if the Data Header recovered from the ICC Public Key Certificate does not equal '6A'. Reference Book 2 - Section 6.4 - Retrieval of the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

ICC Public Key Certificate in LT is calculated with a Data Header different from '6A'.



•


•


•


•


•





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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•



•


•


•


•


•


•



Page 552


2CC.064.02 Recover Data Header not equal to '6A' (3) Test No: 2CC.064.02 - Revision 11 - 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 the ICC Public Key EMV 4.0:



•


•


•



•


•


•




2CC.064.03 Recover Data Header not equal to '6A' (4) Test No: 2CC.064.03 - Revision 11 - 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 the ICC Public Key EMV 4.0:



•


•


•

ICC PIN Encipherment Public Key Certificate in LT is calculated with a Data Header different from '6A'.


•


•


•



Page 554



Authentication process, if the Data Header recovered from the ICC Public Key Certificate does not equal '6A'. Reference EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•


•



•


•


•


•




2CC.064.04 Recover Data Header not equal to '6A' (5) used) received at 1st GENERATE AC. •



Page 556






•


•


•


•



•


•


•


•


•




2CC.064.05 Recover Data Header not equal to '6A' (6) performed) received at 2nd GENERATE AC.


Page 558


2CC.064.06 Recover Data Header not equal to '6A' (7) Test No: 2CC.064.06 - Revision 13a - Number of sub cases: 0 Objective: To ensure that the terminal fails the Combined DDA/AC Data




•


•


•


•


•



•


•


•






•



Page 560






•


•


•


•


•



•


•


•




2CC.064.07 Recover Data Header not equal to '6A' (8) received at 1st GENERATE AC. •


•



Page 562



process, if the Certificate Format recovered from ICC Public Key Certificate does not equal '04'. Reference Book 2 - Section 6.4 - Retrieval of the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

ICC Public Key Certificate in LT is calculated with a Certificate Format different from '04'.



•


•


•


•


•





Authentication process, if the Certificate Format recovered from ICC Public Key Certificate does not equal '04'. Reference Book 2 - Section 6.4 - Retrieval of the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•



•


•


•


•


•


•



Page 564


2CC.065.02 Certificate Format not equal to '04' (3) Test No: 2CC.065.02 - Revision 11 - 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 the ICC Public Key EMV 4.0:



•

AIP of LT indicates Card verification is supported (AIP byte 1 bit 5 = 1).

•


•



•


•


•




2CC.065.03 Certificate Format not equal to '04' (4) Test No: 2CC.065.03 - Revision 11 - 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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•

AIP of LT indicates Card verification is supported (AIP byte 1 bit 5 = 1).

•


•

ICC PIN Encipherment Public Key Certificate in LT is calculated with a Certificate Format different from '04'.


•


•


•



Page 566



Authentication process, if the Certificate Format recovered from ICC Public Key Certificate does not equal '04'. Reference EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•


•



•


•


•


•




2CC.065.04 Certificate Format not equal to '04' (5) used) received at 1st GENERATE AC. •



Page 568






•


•


•


•



•


•


•


•


•




2CC.065.05 Certificate Format not equal to '04' (6) performed) received at 2nd GENERATE AC.


Page 570


2CC.065.06 Certificate Format not equal to '04' (7) Test No: 2CC.065.06 - Revision 13a - Number of sub cases: 0 Objective: To ensure that the terminal fails the Combined DDA/AC Data




•


•


•


•


•



•


•


•






•



Page 572






•


•


•


•


•



•


•


•




2CC.065.07 Certificate Format not equal to '04' (8) received at 1st GENERATE AC. •


•



Page 574



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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

ICC Public Key Certificate in LT is calculated with a bad Hash value.



•


•


•


•


•





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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•



•


•


•


•


•


•



Page 576


2CC.066.02 Difference between calculated Hash Result and recovered Hash Result (3) Test No: 2CC.066.02 - Revision 11 - 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 the ICC Public Key EMV 4.0:



•


•


•



•


•


•




2CC.066.03 Difference between calculated Hash Result and recovered Hash Result (4) Test No: 2CC.066.03 - Revision 11 - 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 the ICC Public Key EMV 4.0:



•


•


•

ICC PIN Encipherment Public Key Certificate in LT is calculated with a bad Hash value.


•


•


•



Page 578



Authentication process, if the calculated Hash Result is different from the Hash Result recovered from the ICC Public Key Certificate. Reference EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•


•



•


•


•






•



Page 580






•


•


•


•



•


•


•


•







Page 582


2CC.066.06 Difference between calculated Hash Result and recovered Hash Result (7) Test No: 2CC.066.06 - Revision 13a - Number of sub cases: 0 Objective: To ensure that the terminal fails the Combined DDA/AC Data




•


•


•


•


•



•


•


•




2CC.066.06 Difference between calculated Hash Result and recovered Hash Result (7) received at 1st GENERATE AC. •


•



Page 584






•


•


•


•


•



•


•






•


•



Page 586


2CC.067.00 Recovered PAN is not equal to read PAN Test No: 2CC.067.00 - Revision 10g - 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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

Issuer Public Key Certificate in LT is calculated with PAN different from PAN in LT.



•


•


•


•


•




2CC.067.01 Recovered PAN is not equal to read PAN (2) Test No: 2CC.067.01 - Revision 15 - 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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•

Issuer Public Key Certificate in LT is calculated with Issuer ID different from PAN in LT.


•


•


•


•


•


•



Page 588


2CC.067.02 Recovered PAN is not equal to read PAN (3) Test No: 2CC.067.02 - Revision 16 - 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 the ICC Public Key EMV 4.0:



•


•


•



•


•


•




2CC.067.03 Recovered PAN is not equal to read PAN (4) Test No: 2CC.067.03 - Revision 16 - 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 the ICC Public Key EMV 4.0:



•


•


•

ICC PIN Encipherment Public Key Certificate in LT is calculated with application PAN different from PAN in LT.


•


•


•



Page 590



Authentication process, if the Recovered PAN does not match the PAN digits recovered from the LT. Reference EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•


•



•


•


•


•




2CC.067.04 Recovered PAN is not equal to read PAN (5) used) received at 1st GENERATE AC. •



Page 592




Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA request at Configuration: GENAC1, ARQC] AND [CDA failure not detected prior TAA] supported Conditions:

•


•


•


•

Issuer Public Key Certificate in LT is calculated with PAN different from PAN in LT.


•


•


•


•


•





Page 594






•


•


•


•


•



•


•


•




2CC.067.06 Recovered PAN is not equal to read PAN (7) •


•



Page 596






•


•


•


•


•



•


•


•




2CC.067.07 Recovered PAN is not equal to read PAN (8) received at 1st GENERATE AC. •


•

TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TSI value in any form such as receipt for example.


Page 598


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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

ICC Public Key Certificate in LT is calculated with Certificate Expiration Date earlier than the current date.



•


•


•


•


•





Authentication process, if the Certificate Expiration Date is earlier than the current date. Reference Book 2 - Section 6.4 - Retrieval of the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•



•


•


•


•


•


•



Page 600


2CC.068.02 Certificate Expiration Date earlier than today's date (3) Test No: 2CC.068.02 - Revision 11 - 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 the ICC Public Key EMV 4.0:



•


•


•



•


•


•




2CC.068.03 Certificate Expiration Date earlier than today's date (4) Test No: 2CC.068.03 - Revision 11 - 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 the ICC Public Key EMV 4.0:



•


•


•

ICC PIN Encipherment Public Key Certificate in LT is calculated with Certificate Expiration Date earlier than the current date.


•


•


•



Page 602



Authentication process, if the Certificate Expiration Date is earlier than the current date. Reference EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•


•



•


•


•


•




2CC.068.04 Certificate Expiration Date earlier than today's date (5) used) received at 1st GENERATE AC. •



Page 604






•


•


•


•



•


•


•


•


•




2CC.068.05 Certificate Expiration Date earlier than today's date (6) performed) received at 2nd GENERATE AC.


Page 606


2CC.068.06 Certificate Expiration Date earlier than today's date (7) Test No: 2CC.068.06 - Revision 13a - Number of sub cases: 0 Objective: To ensure that the terminal fails the Combined DDA/AC Data




•


•


•


•


•



•


•


•






•



Page 608






•


•


•


•


•



•


•


•


•







Page 610


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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

ICC Public Key Certificate in LT is calculated with ICC Public Key Algorithm value different from '01'.



•


•


•


•


•




2CC.069.01 ICC Public Key Algorithm not recognized (2) Test No: 2CC.069.01 - Revision 15 - 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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•



•


•


•


•


•


•



Page 612


2CC.069.02 ICC Public Key Algorithm not recognized (3) Test No: 2CC.069.02 - Revision 15 - 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 the ICC Public Key EMV 4.0:



•


•


•



•


•


•




2CC.069.03 ICC Public Key Algorithm not recognized (4) Test No: 2CC.069.03 - Revision 11 - 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 the ICC Public Key EMV 4.0:



•


•


•

ICC PIN Encipherment Public Key Certificate in LT is calculated with ICC PIN Encipherment Public Key Algorithm value different from '01'.


•


•


•



Page 614



Authentication process, if the ICC Public Key Algorithm used is not supported (different from '01'). Reference EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•


•


•

Case 01: Cleartext and recovered CID in first GENERATE AC indicates a TC

•

Case 02: Cleartext and recovered CID in first GENERATE AC indicates an ARQC


•

Case 01: The terminal shall decline the transaction by without issuning a second GENERATE AC.

•

Case 02: The terminal shall complete the transaction by performing a immediate second GENERATE AC requesting an AAC.

•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC Data Authentication failed) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal



2CC.069.04 ICC Public Key Algorithm not recognized (5) has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example. •


•


•



Page 616






•


•


•


•



•


•


•


•


•




2CC.069.05 ICC Public Key Algorithm not recognized (6) performed) received at 2nd GENERATE AC.


Page 618






•


•


•


•


•



•


•


•




2CC.069.06 ICC Public Key Algorithm not recognized (7) •


•



Page 620





Processing] supported AND [CDA failure not detected prior TAA] supported Conditions:

•


•


•


•


•



•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC 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 or terminated transaction) or if the terminal has the capability to show the TSI value in any form such as receipt for example..

•




2CC.069.07 ICC Public Key Algorithm not recognized (8) received at 1st GENERATE AC. •


•



Page 622


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.0:

Book 3 - Section 1.4 - Rules for Using a Data Object List (DOL) Reference Book 2 - Section 6.5.1 - Dynamic Signature Generation EMV 4.1:

Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) Terminal [DDA] supported Configuration: Conditions:

•


•

DDOL is present in LT.

•

Dynamic signature computed by LT is correct.



•


•


•


•


•

The LT shall receive an INTERNAL AUTHENTICATE command with concatenation of data in DDOL according to rule described



2CC.071.00 Dynamic Signature generation in Book 3 Section 1.4. •



Page 624


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.0: Reference Book 2 - Section 6.5.1 - Dynamic Signature Generation EMV 4.1: Terminal [DDA] supported Configuration:

Default DDOL is present in terminal. Conditions:

•


•

DDOL is absent in LT.

•




•


•


•


•


•

The LT shall receive an INTERNAL AUTHENTICATE command with concatenation of data in default DDOL according to rule described in Book 3 Section1.4.

•





Page 626


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.0: Reference Book 2 - Section 6.5.1 - Dynamic Signature Generation EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

DDOL requests unpredictable number (9F 37) on 4 bytes.

•




•


•


•


•


•

The LT shall receive an INTERNAL AUTHENTICATE command with unpredictable Number contained in the data field.

•





Page 628


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.0: Reference Book 2 - Section 6.5.1 - Dynamic Signature Generation EMV 4.1: Terminal [DDA] supported Configuration:

Default DDOL in terminal requests unpredictable number (9F 37). Conditions:

•


•

DDOL in LT does not request unpredictable number (9F 37).



•


•


•


•


•




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.0: Reference Book 2 - Section 6.5.1 - Dynamic Signature Generation EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

DDOL is absent in LT.

•

default DDOL in terminal does not request unpredictable number (9F 37).



•


•


•


•


•



Page 630


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.0: Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

Signed Dynamic Application Data computed by LT has a length different from that of ICC Public Key Modulus.



•


•


•


•


•




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.0: Recovery Reference Book 2 - Section A2.1 - Digital Signature Scheme Giving Message EMV 4.1: Recovery Terminal [DDA] supported Configuration: Conditions:

•


•

Signed Dynamic Application Data computed by LT is correct.

•

Issuer Public Key Certificate is valid.

•

ICC public Certificate is valid.



•


•


•


•


•



Page 632



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.0: Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

Signed Dynamic Application Data is calculated by LT with a Data Trailer different from 'BC'.


particular Dynamic Data Authentication). Pass Criteria: The terminal shall process the transaction until completion, by

requesting a TC or an AAC. •


•


•


•





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.0: Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

Signed Dynamic Application Data is calculated by LT with a Data Header different from '6A'.



•


•


•


•


•



Page 634



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.0: Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

Signed Dynamic Application Data is calculated by LT with a Certificate Format different from '05'.



•


•


•


•


•





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.0: Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

Signed Dynamic Application Data is calculated by LT with a bad Hash value.

•

Case 01: Error is on the 11th byte of the Hash.

•


•




•


•


•


•


•



Page 636




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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

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.



•


•

TVR byte 1, bit 4 = '1' (ie Offline DDA failed) received at 1st GENERATE AC.

•


•


•



Page 638


2CC.085.01 SDA Tag List in Dynamic Data Authentication (1) Test No: 2CC.085.01 - Revision 13 - 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 the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•


•




•


•


•

TVR byte 1, bit 3 = '1' (ie Offline Combined DDA/AC failed,) received at 1st GENERATE AC.

•


•


•





Page 640



while performing DDA process. Reference Book 2 - Section 6.4 - Retrieval of the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

SDA Tag List contains AIP.



•


•

TVR byte 1, bit 4 = '0' (ie Offline DDA succeeded) received at 1st GENERATE AC.

•


•


•





while performing Combined DDA/AC process. Reference Book 2 - Section 6.4 - Retrieval of the ICC Public Key EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•

SDA Tag List contains AIP.



•


•

TVR byte 1, bit 3 = '0' (ie Offline Combined DDA/AC succeeded) contained in Financial Confirmation message or Batch Data Capture message.

•


•


•



Page 642



while performing Combined DDA/AC process. Reference EMV 4.0: Reference Book 2 - Section 6.4 - Retrieval of ICC Public Key EMV 4.1:


•


•


•


•




•


•


•




2CC.085.04 SDA Tag List in Dynamic Data Authentication (5) received at 1st GENERATE AC. •


•



Page 644






•


•


•


•


•




•


•


•


•




2CC.085.05 SDA Tag List in Dynamic Data Authentication (6) used) received at 1st GENERATE AC. •



Page 646


2CC.085.06 SDA Tag List in Dynamic Data Authentication (7) Test No: 2CC.085.06 - Revision 13a - Number of sub cases: 2 Objective: To ensure that the terminal checks that SDA Tag List contains only AIP




•


•


•


•


•


•




•


•




2CC.085.06 SDA Tag List in Dynamic Data Authentication (7) •


•


•



Page 648






•


•


•


•


•


•




•


•




2CC.085.07 SDA Tag List in Dynamic Data Authentication (8) show the TVR value in any form such as receipt for example. •


•


•



Page 650


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.0: Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

CDOL1 requests an ICC Dynamic number (Tag '9F 4C').



•


•


•


•


•


•

Value of Tag '9F 4C' shall be the same as that used in DDA process (received at 1st GENERATE AC).



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.0: Reference Book 2 - Section 7 - Personal Identification Number Encipherment EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•


•

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.



•


•

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.

•


•

TVR byte 3, bit 8='0' (ie Cardholder verification was successful) received at 1st GENERATE AC.


Page 652


2CC.094.00 Random behaviour of PIN Encipherment padding pattern Test No: 2CC.094.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the terminal supports offline PIN encryption, it is able

to generate a RANDOM pattern of N-17 bytes. Reference Book 2 - Section 7.2 - PIN Encipherment and Verification EMV 4.0: Reference Book 2 - Section 7.2 - PIN Encipherment and Verification EMV 4.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.

•

PIN Encipherment Public Key and associated data is present in LT.

•


Action: NA Procedure: Several transactions are processed with LT (in particular Cardholder

verification). Pass Criteria:

•


•

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 pattern comparing values from different transactions.

•


•




2CC.095.00 Value of ICC PIN Encryption Public Key Exponent Test No: 2CC.095.00 - Revision 10g - Number of sub cases: 2 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.0: Reference Book 2 - Section 7.1 - Keys and Certificates EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•

PIN Encipherment Public Key and associated data is present in LT.

•


•

Case 01: Exponent of ICC PIN Encipherment Public Key is 3.

•

Case 02: Exponent of ICC PIN Encipherment Public Key is 2^16 + 1.



•


•

Once deciphered with PIN encipherment private Key, the LT shall recover the PIN value presented and unpredictable Number generated by LT.


Page 654


2CC.095.01 Value of ICC Public Key Exponent Test No: 2CC.095.01 - Revision 11 - Number of sub cases: 2 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.0: Reference Book 2 - Section 6.1 - Keys and Certificates EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•

PIN Encipherment Public Key and associated data are not present in LT.

•

ICC Public Key and associated data are present in LT.

•


•


•




•


•

Once deciphered with ICC private Key, the LT shall recover the PIN value presented and unpredictable Number generated by LT.



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.0:

Book 2 - Section B2.1 - RSA Algorithm Book 2 - Section B3.1 - Secure Hash Algorithm (SHA-1) Reference Book 2 - Section 7.1 - Keys and Certificates EMV 4.1:

Book 2 - Section B2.1 - RSA Algorithm Book 2 - Section B3.1 - Secure Hash Algorithm (SHA-1) Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•

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 Hash


Page 656


2CC.096.00 ICC PIN Encipherment Public Key recovering: ICC PIN Encipherment Public Key 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.

•




•


•

Once deciphered with PIN encipherment private Key, the LT shall recover the PIN value presented and unpredictable Number generated by LT.

•


•




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.0:

Book 2 - Section B2.1 - RSA Algorithm Book 2 - Section B3.1 - Secure Hash Algorithm (SHA-1) Reference Book 2 - Section 7.1 - Keys and Certificates EMV 4.1:

Book 2 - Section B2.1 - RSA Algorithm Book 2 - Section B3.1 - Secure Hash Algorithm (SHA-1) Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•


•


•


•



Page 658


2CC.097.00 ICC PIN Encipherment Public Key recovery: ICC Public Key •


•

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.

•




•


•

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.

•


•




2CC.098.00 ICC PIN Encipherment Public Key recovering failed Test No: 2CC.098.00 - Revision 10g - 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.0:

Book Bulletins - Section SU 21 - Bulletin n°21, Clarification of Actions During Offline Enciphered PIN processing (Nov-2003) Reference Book 2 - Section 7.1 - Keys and Certificates EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•

PIN Encipherment Public Key Certificate stored in LT is not valid.

•




•


•



Page 660


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.0: Reference Book 2 - Section 7.2 - PIN Encipherment and Verification EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•


•


Action: Cardholder presents a valid PIN in Clear. Procedure: Application in LT is selected and transaction is processed with LT (in


•


•

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.



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.0:

Book Bulletins - Section SU 21 - Bulletin n°21, Clarification of Actions During Offline Enciphered PIN processing (Nov-2003) Reference Book 2 - Section 7.2 - PIN Encipherment and Verification EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•


•




•


•

The LT shall receive a GET CHALLENGE command from the terminal.


Page 662


2CC.100.01 Unpredictable Number (2) Test No: 2CC.100.01 - Revision 10g - 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.0:

Book Bulletins - Section SU 21 - Bulletin n°21, Clarification of Actions During Offline Enciphered PIN processing (Nov-2003) Reference Book 2 - Section 7.2 - PIN Encipherment and Verification EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•


•

LT response to the Get Challenge command is 6 byte of data with status value = 90 00.



•


•




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.0: Reference Book 2 - Section 7.2 - PIN Encipherment and Verification EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•




•


•

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.


Page 664


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 Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation

(Dec-2001) Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:

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:

•


•

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.


particular Enhanced Combined DDA/AC). Pass Criteria:

•


•

TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation succeeded) contained in Financial Confirmation message or Batch Data Capture message.

•


•




2CC.119.00 PDOL in Enhanced Combined DDA/AC •



Page 666


2CC.119.01 PDOL in Enhanced Combined DDA/AC Test No: 2CC.119.01 - Revision 13a - Number of sub cases: 3 Objective: To ensure that the terminal can use PDOL in Enhanced Combined

DDA/AC. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation


Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA request at Configuration: GENAC1, ARQC] supported Conditions:

•


•

TAC and IAC are set so that an ARQC 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.



•


•


•


•




2CC.119.01 PDOL in Enhanced Combined DDA/AC •



Page 668


2CC.122.00 Response to GENERATE AC when responding AAC is in format 1or 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 Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation

(Dec-2001) Book Bulletins - Section SU 20 - Bulletin n°20, Combined DDA/AC Generation (Jan-2004) Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:

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:

•


•


•

Case 01: LT responds with AAC to first GENERATE AC in format 1.

•




•

The terminal shall process the transactions to completion.

•

The transaction shall be declined.



2CC.122.00 Response to GENERATE AC when responding AAC is in format 1or 2 •

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.

•


•



Page 670


2CC.122.01 Response to GENERATE AC when responding AAC is in format 1or 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 Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation

(Dec-2001) Book Bulletins - Section SU 20 - Bulletin n°20, Combined DDA/AC Generation (Jan-2004) Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:


•


•


•

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



•


•


•

This pass criteria only applies if the terminal has the ability to



2CC.122.01 Response to GENERATE AC when responding AAC is in format 1or 2 (2) store declined transactions: TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) shall be set. •


•



Page 672


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 Bulletins - Section SU 20 - Bulletin n°20, Combined DDA/AC EMV 4.0: Generation (Jan-2004)

Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:

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:

•


•


•

LT responds AAR at the first GENERATE AC without dynamic signature.



•




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 Bulletins - Section SU 20 - Bulletin n°20, Combined DDA/AC EMV 4.0: Generation (Jan-2004)

Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:

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:

•


•


•

LT responds AAR at the first generate AC with dynamic signature.



•



Page 674



specified in book 3 part I) in Enhanced Combined DDA/AC, when LT responds AAC to GENERATE AC command. Reference EMV 4.0: Reference Book 2 – Section 6.6.1 - Dynamic Signature Generation EMV 4.1:


•


•


•


•




•


•


•


•




2CC.122.04 Response to GENERATE AC when responding AAC is in format 1or 2 (3) •



Page 676



specified in book 3 part I) in Enhanced Combined DDA/AC, when LT responds AAC to GENERATE AC command. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:


•


•


•


•


•




•


•


•


•




2CC.122.05 Response to GENERATE AC when responding AAC is in format 1or 2 (4) received at 1st GENERATE AC. •



Page 678


2CC.122.06 ICC responds with AAR (3) Test No: 2CC.122.06 - 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 EMV 4.0: Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:

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 [Online Only] supported AND [CDA request at Configuration: GENAC1, ARQC] supported Conditions:

•


•


•

LT responds AAR at the first GENERATE AC without dynamic signature.



•




2CC.122.07 ICC responds with AAR (4) Test No: 2CC.122.07 - 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 EMV 4.0: Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:

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 [Online Only] supported AND [CDA request at Configuration: GENAC1, ARQC] supported Conditions:

•


•


•

LT responds AAR at the first generate AC with dynamic signature.



•



Page 680



specified in book 3 part I) in Enhanced Combined DDA/AC, when LT responds AAC to GENERATE AC command. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:

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 AND [CDA never at GENAC1,

ARQC] supported Conditions:

•


•


•


•


•


•




•


•


•

This pass criteria only applies if the terminal has the ability to store declined transactions: TSI byte 1, bit 8 = '1' (ie Offline



2CC.122.08 Response to GENERATE AC when responding AAC is in format 1or 2 (5) Data Authentication was performed) shall be set. •


•



Page 682


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 Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation

(Dec-2001) Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:


•


•

Length of Signed Dynamic Application Data is different from the ICC Public Key length.

•


•

Case 01: LT responds to the first GENERATE AC with a TC.

•

Case 02: LT responds to the first GENERATE AC with an ARQC.



•

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



2CC.123.00 Signed Dynamic Application Data Length 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 4 = '0' (ie Dynamic Data Authentication not used) received at 1st GENERATE AC


Page 684


2CC.123.01 Signed Dynamic Application Data Length (2) Test No: 2CC.123.01 - Revision 15 - 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 EMV 4.0: Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:


•


•

Length of Signed Dynamic Application Data is different from the ICC Public Key length.

•


•

LT responds to the first GENERATE AC with an ARQC.



•

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.

•




2CC.123.01 Signed Dynamic Application Data Length (2) •



Page 686




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:

•


•

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.

•


•




•


•

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 crietia applies only if the terminal has the capablity 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 crietia applies only if the terminal has the capablity to store declined transactions).



2CC.123.02 Signed Dynamic Application Data Length (3) •


•



Page 688




Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA request at Configuration: GENAC2, TC] supported Conditions:

•


•

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.

•




•


•


•

TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed) contained in the Financial Confirmation message or Batch Data Capture message (this pass crietia applies only if the terminal has the capablity to store declined transactions)..

•




2CC.123.03 Signed Dynamic Application Data Length (4) received at 1st GENERATE AC. •



Page 690


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 Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation



•


•

Data trailer is different from BC.

•


•


•




•


•


•

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).



2CC.124.00 Recovered Data trailer not equal to BC •


•


•



Page 692


2CC.124.01 Recovered Data trailer not equal to BC (2) Test No: 2CC.124.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal checks the recovered data trailer for

Combined DDA/AC Data Authentication. Reference EMV 4.0: Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:


•


•

Data trailer is different from BC.

•


•




•


•


•


•


•





Page 694


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 Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation



•


•

Data header is different from 6A.

•


•


•




•


•


•




2CC.125.00 Recovered Data header not equal to 6A •


•


•



Page 696


2CC.125.01 Recovered Data header not equal to 6A (2) Test No: 2CC.125.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal checks the recovered data header for



•


•

Data header is different from 6A.

•


•




•


•


•


•


•





Page 698





•


•

Data header is different from 6A at second GENERATE AC.

•

TAC and IAC are set so that an ARQC is requested at first GENERATE AC and a TC at second GENERATE AC.

•


•




•


•

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 crietia applies only if the terminal has the capablity to store declined transactions)..

•


•




2CC.125.02 Recovered Data header not equal to 6A (3) received at 1st GENERATE AC. •



Page 700





•


•

Data header is different from 6A at second GENERATE AC.

•


•

LT responds to the first GENERATE AC with an ARQC



•


•


•


•




2CC.125.03 Recovered Data header not equal to 6A (4) •



Page 702


2CC.126.00 Recovered Signed Data Format not equal to 05 Test No: 2CC.126.00 - Revision 15 - Number of sub cases: 2 Objective: To ensure that the terminal checks the recovered signed data format

for Combined DDA/AC Data Authentication. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation



•


•

Signed Data Format is different from 05.

•


•


•




•


•


•




2CC.126.00 Recovered Signed Data Format not equal to 05 •


•


•



Page 704


2CC.126.01 Recovered Signed Data Format not equal to 05 (2) Test No: 2CC.126.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal checks the recovered signed data format

for Combined DDA/AC Data Authentication. Reference EMV 4.0: Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:


•


•

Signed Data Format is different from 05.

•


•

LT responds to the first GENERATE AC with an ARQC..



•


•


•


•




2CC.126.01 Recovered Signed Data Format not equal to 05 (2) •



Page 706





•


•

Signed Data Format is different from 05 at second GENERATE AC.

•

TAC and IAC are set so that an ARQC is requested at first GENERATE AC and TC at second GENERATE AC.

•


•

Terminla is unable to go online



•


•


•






•



Page 708





•


•

Signed Data Format is different from 05 at second GENERATE AC.

•


•




•


•


•


•







Page 710


2CC.127.00 Recovered CID different from CID obtained after Generate AC (1) Test No: 2CC.127.00 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal checks that the CID recovered for

Combined DDA/AC Data Authentication is the same as that transmitted in the response to the GENERATE AC command. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation

(Dec-2001) Book Bulletins - Section SU 20 - Bulletin n°20, Combined DDA/AC Generation (Jan-2004) Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:


•


•


•

LT responds to the first GENERATE AC with a TC.

•

CID in signature is ARQC.



•

The terminal shall complete the transaction by performing an immediate Second Generate AC command requesting an AAC.

•


•

TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed)



2CC.127.00 Recovered CID different from CID obtained after Generate AC (1) 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). •


•



Page 712



Combined DDA/AC Data Authentication is the same as the one transmitted in the response to the GENERATE AC command. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation

(Dec-2001) Book Bulletins - Section SU 20 - Bulletin n°20, Combined DDA/AC Generation (Jan-2004) Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:


•


•


•


•

CID in signature is TC.



•

The terminal shall decline the transaction and not perform a second GENERATE AC command.

•


•

TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed)



2CC.127.01 Recovered CID different from CID obtained after Generate AC (2) contained in the Financial Confirmation message or Batch Data Capture message (this pass crietia applies only if the terminal has the capablity to store declined transactions). •


•



Page 714



Combined DDA/AC Data Authentication is the same as the one transmitted in the response to the GENERATE AC command. Reference EMV 4.0: Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:


•


•


•


•

CID in signature is TC.



•

The terminal shall decline the transaction and nort perform a second GENERATE AC command.

•


•




2CC.127.02 Recovered CID different from CID obtained after Generate AC (3) •


•



Page 716


2CC.128.00 Compare hash result Test No: 2CC.128.00 - Revision 15 - Number of sub cases: 2 Objective: To ensure that the terminal compares the hash result for Combined

DDA/AC Data Authentication. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation



•


•

Hash result is corrupted.

•


•


•

Case 02: LT responds to the first GENERATE AC with an ARQC..



•


•


•




2CC.128.00 Compare hash result •


•


•



Page 718


2CC.128.01 Compare hash result (2) Test No: 2CC.128.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal compares the hash result for Combined

DDA/AC Data Authentication. Reference EMV 4.0: Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:


•


•

Hash result is corrupted.

•


•




•


•


•


•


•





Page 720





•


•

Hash result is corrupted in second GENERATE AC response.

•


•


•




•


•

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 crietia applies only if the terminal has the capablity 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 crietia applies only if the terminal has the capablity to store declined transactions.

•




2CC.128.02 Compare hash result (3) received at 1st GENERATE AC. •



Page 722





•


•

Hash result is corrupted in second GENERATE AC response.

•


•

LT responds to the first GENERATE AC with an ARQC at first GENERATE AC.

•

Issuer response indicates approval.



•


•

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 crietia applies only if the terminal has the capablity 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 crietia applies only if the terminal has the capablity to store declined transactions.



2CC.128.03 Compare hash result (4) •


•



Page 724


2CC.129.00 Compare Transaction Data Hash Code Test No: 2CC.129.00 - Revision 15 - Number of sub cases: 2 Objective: To ensure that the terminal compares the Transaction Data Hash Code

for Combined DDA/AC Data Authentication. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation



•


•

Transaction Data Hash result is corrupted.

•


•


•




•


•


•




2CC.129.00 Compare Transaction Data Hash Code •


•


•



Page 726


2CC.129.01 Compare Transaction Data Hash Code (2) Test No: 2CC.129.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal compares the Transaction Data Hash Code



•


•

Transaction Data Hash result is corrupted.

•


•




•


•


•


•


•





Page 728





•


•

Transaction Data Hash result is corrupted in second GENERATE AC respopnse.

•


•


•




•


•


•




2CC.129.02 Compare Transaction Data Hash Code (3) •


•



Page 730





•


•

Transaction Data Hash result is corrupted in second GENERATE AC respopnse.

•


•




•


•


•

TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failedd) contained in the Financial Confirmation message or Batch Data Capture message (this pass crietia applies only if the terminal has the capablity to store declined transactions).

•




2CC.129.03 Compare Transaction Data Hash Code (4) •



Page 732


2CC.130.00 Issuer Application Data in Enhanced Combined DDA/AC Test No: 2CC.130.00 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal can use Issuer Application Data in

Enhanced Combined DDA/AC. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation



•


•


•

LT responds with ARQC to first GENERATE AC and TC to second.

•

Issuer Application Data is present in response to first GENERATE AC command.



•


•

TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation succeeded) received at 2nd GENERATE AC.

•


•


•




2CC.130.00 Issuer Application Data in Enhanced Combined DDA/AC performed) contained in Financial Confirmation message or Batch Data Capture message.


Page 734


2CC.130.01 Issuer Application Data in Enhanced Combined DDA/AC (2) Test No: 2CC.130.01 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal can use Issuer Application Data in

Enhanced Combined DDA/AC. Reference Book Bulletins - Section AN 6 - Bulletin n°6, Clarification to Application EMV 4.0: Selection (Jun-2002) Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:


•


•

TAC and IAC are set so that a TC is requested at first GENERATE AC and TC at second GENERATE AC..

•


•

Issuer Application Data is present in response to second GENERATE AC.

•




•


•

TVR, TSI (contained in Financial Confirmation message or Batch Data Capture message or other) shall have: -

TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation succeeded) set.

-

TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) set.



2CC.130.01 Issuer Application Data in Enhanced Combined DDA/AC (2) •


•



Page 736



Enhanced Combined DDA/AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:


•


•


•


•

Issuer Application Data is present in response to first GENERATE AC command.



•


•


•


•


•




2CC.130.02 Issuer Application Data in Enhanced Combined DDA/AC (3) performed) contained in Financial Confirmation message or Batch Data Capture message.


Page 738





•


•


•


•




•


•

TVR, TSI (contained in Financial Confirmation message or Batch Data Capture message or other) shall have:

•

-


-





2CC.130.03 Issuer Application Data in Enhanced Combined DDA/AC (4) received at 1st GENERATE AC. •



Page 740




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:

•


•


•


•


•




•


•

TVR, TSI (contained in Financial Confirmation message or Batch Data Capture message or other) shall have: -


-




2CC.130.04 Issuer Application Data in Enhanced Combined DDA/AC (5) •


•



Page 742


2CC.131.00 ICC Dynamic Number is stored Test No: 2CC.131.00 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal stores the ICC Dynamic Number in Tag 9F

4C for Combined DDA/AC Data Authentication. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation



•

CDOL2 requests ICC Dynamic number (tag 9F 4C).

•


•


•


•




•


•


•


•




2CC.131.00 ICC Dynamic Number is stored •

ICC Dynamic Number stored in Tag 9F 4C is the same as that used in Enhanced Combined DDA/AC, received at 2nd GENERATE AC.

•

TVR, TSI and ICC Dynamic Number (contained in Financial Confirmation message or Batch Data Capture message or other) shall have:

- TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation succeeded) set. - TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) set. - ICC Dynamic Number stored in Tag 9F 4C is the same as that used in Enhanced Combined DDA/AC.


Page 744


2CC.131.01 ICC Dynamic Number is stored (2) Test No: 2CC.131.01 - Revision 16 - Number of sub cases: 0 Objective: To ensure that the terminal stores the ICC Dynamic Number in Tag 9F

4C for Combined DDA/AC Data Authentication. Reference EMV 4.0: Reference Book 2 - Section 6.6.2 - Dynamic Signature Verification EMV 4.1:

Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND ([CDA request at Configuration: GENAC1, ARQC] supported OR [CDA request at GENAC2, TC]

supported) Conditions:

•

CDOL2 requests ICC Dynamic number (tag 9F 4C).

•


•

TAC and IAC are set so that an ARQC is requested at first GENERATE AC

•




•


•


•


•


•

TVR, TSI and ICC Dynamic Number (contained in Financial Confirmation message or Batch Data Capture message or



2CC.131.01 ICC Dynamic Number is stored (2) other) shall have: - TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation succeeded) set. - TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) set. - ICC Dynamic Number stored in Tag 9F 4C is the same as that used in Enhanced Combined DDA/AC.


Page 746


2CC.133.00 Unpredictable Number generated by the terminal Test No: 2CC.133.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal generates a different random number from

one transaction to another, for Combined DDA/AC Data Authentication. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation

(Dec-2001) Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•

CDOL1 and CDOL2 in LT include Unpredictable Number generated by the terminal (tag 9F 37).

•


Action: NA Procedure: At least three transactions are processed. The unpredictable number

values generated by the terminal will be compared. Pass Criteria:

•


•


•


•


•


•

Tag 9F37 is checked and compared with the one from the previous transaction. They shall be different.



2CC.133.01 Unpredictable Number not present in CDOLs Test No: 2CC.133.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal does not verify the presence of the

Unpredictable Number (9F37) in the CDOL1 and CDOL2, for Combined DDA/AC Data Authentication. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:

Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported Configuration: Conditions:

•

CDOL1 and CDOL2 in LT does not include Unpredictable Number generated by the terminal (tag 9F 37).

•




•


•

TVR byte 1, bit 3 = '1' (ie Combined DDA/AC Generation failed) contained in Financial Confirmation message or Batch Data Capture message.

•


•


•



Page 748


2CC.133.02 Unpredictable Number not present in CDOLs Test No: 2CC.133.02 - Revision 15 - Number of sub cases: 0 Objective: To ensure when the CDOL1 and/or CDOL2 does not contain the

Unpredictable Number (9F37), and if CDA is not performed, the terminal disregard the absence of Unpredictable number and continues transaction without failing CDA during online transaction. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:

Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND ([Online Only] OR [Online/Offline Capable]) AND Configuration: [CDA never at GENAC1, ARQC] supported AND [CDA never at

GENAC 2, TC] supported Conditions:

•

CDOL1 and CDOL2 in LT does not include Unpredictable Number generated by the terminal (tag 9F 37).

•


•


•

LT answers with an ARQC at first GENERATE AC.

•

Issuer response indicates APPROVAL



•


•

TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation not used) received at 1st and 2nd GENERATE AC

•

TVR byte 1, bit 7 = '0' (ie Static Data Authentication not used) received at 1st and 2nd GENERATE AC.



2CC.133.02 Unpredictable Number not present in CDOLs •

TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not used) received at 1st and 2nd GENERATE AC


Page 750


2CC.134.00 Response to GENERATE AC when responding TC or ARQC is in format 2 Test No: 2CC.134.00 - Revision 15 - Number of sub cases: 2 Objective: To ensure that the terminal can use the ICC response format 2 as

specified in book 3, part I, in Enhanced Combined DDA/AC To ensure that the terminal stores the Application Cryptogram in Tag 9F 26 for Combined DDA/AC Data Authentication. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation


Book 2 - Section 6.6.2 - Dynamic Signature Verification 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:

•


•

LT response to GENERATE AC is in format 2.

•

TAC and IAC are set so that a TC is requested at first GENERATE AC and TC at second GENERATE AC.

•


•

Case 01: LT answers to the first GENERATE AC with an TC.

•

Case 03: LT answers to the first GENERATE AC with an ARQC and to the second GENERATE AC with a TC.



•

The terminal shall process the transaction until completion by requesting a TC.



2CC.134.00 Response to GENERATE AC when responding TC or ARQC is in format 2 •

TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation succeeded) contained in Financial Confirmation message or Batch Data Capture message)

•


•

Application Cryptogram, contained in Financial Confirmation message or Batch Data Capture message, is the same as that used in Enhanced Combined DDA/AC.

•


•



Page 752


2CC.134.01 Response to GENERATE AC when responding TC or ARQC is not in format 2 (Implied) Test No: 2CC.134.01 - Revision 15 - Number of sub cases: 3 Objective: To ensure that the terminal does not use the ICC response format 1 in

Enhanced Combined DDA/AC (as specified in book 3 part I) when responding TC or ARQC. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation

(Dec-2001) Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1: Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable]) Configuration: supported Conditions:

•


•

Case 01: TAC and IAC are set so that a TC is requested at first GENERATE AC. LT answers with TC to first GENERATE AC in format 1.

•

Case 02: TAC and IAC are set so that a TC is requested at first GENERATE AC. LT answers to the first GENERATE AC with an ARQC in format 1.

•

Case 03: TAC and IAC are set so that a TC is requested at first GENERATE AC, and to request TC in the second GENERATE AC. LT answers with ARQC to first GENERATE AC in format 2 and TC to second GENERATE AC in format 1. Terminal is unable to go online.



•

The terminal shall decline or terminate the transaction .

•

Case 03: The terminal shall decline the transaction or terminated according to the implementation

•




2CC.134.01 Response to GENERATE AC when responding TC or ARQC is not in format 2 (Implied) Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined transaction).


Page 754


2CC.134.03 Response to GENERATE AC when responding AAC is not digitally signed (implied) Test No: 2CC.134.03 - Revision 16 - Number of sub cases: 2 Objective: To ensure that the terminal does not support an AAC response to

GENERATE AC, if the response is formatted as a TC (AAC digitally signed), in Enhanced Combined DDA/AC. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation



•


•


•

Case 01: LT responds with AAC to first GENERATE AC digitally signed (same process as a TC) in format 2.

•

Case 02: LT responds with ARQC to first GENERATE AC and with AAC to second GENERATE AC digitally signed (same process as a TC) in format 2.



•

The terminal shall decline the transactions.

•

This pass criteria only applies if the terminal has the ability to store declined transactions: TVR byte 1, bit 3 = ‘0’ (ie Combined DDA/AC Generation not failed) shall be set.

•




2CC.134.03 Response to GENERATE AC when responding AAC is not digitally signed (implied) •



Page 756


2CC.134.04 GENERATE AC Reference Control Parameter for Combined DDA/AC generation. Test No: 2CC.134.04 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal sets the GENERATE AC Reference Control

Parameter flag for Enhanced Combined DDA/AC request. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation

(Dec-2001) Book Bulletins - Section SU 9 - Bulletin n°9, Modification to Combined Dynamic Data Authentication (Mar-2002) Book Bulletins - Section SU 20 - Bulletin n°20, Combined DDA/AC Generation (Jan-2004) Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:


•


•

IAC and TAC set so that the Terminal requests TC at first GENERATE AC.



•


•

P1 = Reference Control Parameter (50 - TC).



2CC.134.05 Response to GENERATE AC when responding TC or ARQC is in format 2 (2) Test No: 2CC.134.05 - Revision 15 - Number of sub cases: 2 Objective: To ensure that the terminal can use the ICC response format 2 as



Book 2 - Section 6.6.2 - Dynamic Signature Verification Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA request at Configuration: GENAC1, ARQC] supported AND [CDA request at GENAC2, TC]


•


•


•


•

Case 01: LT answers with an ARQC.

•

Case 02: LT answers with an ARQC to first GENERATE AC and with a TC to the second GENERATE AC.



•


•



Page 758


2CC.134.05 Response to GENERATE AC when responding TC or ARQC is in format 2 (2) •


•


•


•




2CC.134.06 Response to GENERATE AC when responding TC or ARQC is not in format 1 (Implied) (2) Test No: 2CC.134.06 - Revision 15 - Number of sub cases: 2 Objective: To ensure that the terminal does not use the ICC response format 1 in



Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA request at Configuration: GENAC1, ARQC] supported AND [CDA request at GENAC2, TC]


•


•

Case 01: TAC and IAC are set so that an ARQC is requested at first GENERATE AC. LT answers with ARQC in format 1.

•

Case 02: TAC and IAC are set so that an ARQC is requested at first GENERATE AC,and to request TC in the second GENERATE AC. LT answers with ARQC to first GENERATE AC in format 2 and TC to second GENERATE AC in format 1.



•

The terminal shall decline or terminate the transaction.

•



Page 760


2CC.134.07 Response to GENERATE AC when responding AAC is not digitally signed (implied) (2) Test No: 2CC.134.07 - Revision 16 - Number of sub cases: 2 Objective: To ensure that the terminal does not support an AAC response to

GENERATE AC, if the response is formatted as a TC (AAC digitally signed), in Enhanced Combined DDA/AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:


•


•


•

Case 01: LT responds with AAC to first GENERATE AC digitally signed (same process as a TC) in format 2.

•

Case 02: LT responds with AAC to second GENERATE AC digitally signed (same process as a TC) in format 2.



•


•

This pass criteria only applies if the terminal has the ability to store declined transactions: TVR byte 1, bit 3 (ie Combined DDA/AC Generation not failed) shall be set.

•


•





Page 762


2CC.134.08 GENERATE AC Reference Control Parameter for Combined DDA/AC generation (2) Test No: 2CC.134.08 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal sets the GENERATE AC Reference Control

Parameter flag for Enhanced Combined DDA/AC request. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:


•


•

IAC and TAC set so that the Terminal requests an ARQC at first GENERATE AC and a TC at second GENERATE AC.

•

Issuer response indicates approval



•


•

First GENERATE AC, P1 '90' - ARQC.

•

Second GENERATE AC, P1 = '50' - TC (when not supporting CDA at GenAC2, TC the P1 shall be '40')




specified in book 3, part I, in Enhanced Combined DDA/AC To ensure that the terminal stores the Application Cryptogram in Tag 9F 26 for Combined DDA/AC Data Authentication. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:

Book 2 - Section 6.6.2 - Dynamic Signature Verification Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND ([Online Only] AND [Normal Default Action Code Configuration: processing]) supported AND [CDA request at GENAC1, ARQC]


•


•


•


•

Case 01: LT answers to the first GENERATE AC with an ARQC.

•

Case 02: LT answers with an TC at second GENERATE AC, transaction is unable to go online.



•


•



Page 764




•


•


•





Enhanced Combined DDA/AC (as specified in book 3 part I) when responding TC or ARQC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:

Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND ([Online Only] AND [Normal Default Action Code Configuration: processing]) supported AND [CDA request at GENAC1, ARQC]


•


•

Case 01: TAC and IAC are set so that an ARQC is requested at first GENERATE AC. LT answers with ARQC in format 1.

•

Case 02: TAC and IAC are set so that an ARQC is requested at first GENERATE AC, and to request TC in the second GENERATE AC. LT answers with ARQC to first GENERATE AC in format 2 and TC to second GENERATE AC in format 1 and transaction is unable to go online.



•

The terminal shall decline or terminate the transaction

•



Page 766





Book 2 - Section 6.6.2 - Dynamic Signature Verification Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA request at Configuration: GENAC2, TC] supported Conditions:

•


•


•


•


•

LT answers to the second GENERATE AC with a TC.



•


•






•


•


•



Page 768






•


•

TAC and IAC are set so that an ARQC is requested at first GENERATE AC, and to request TC in the second GENERATE AC. LT answers with ARQC to first GENERATE AC in format 2 and TC to second GENERATE AC in format 1.



•

The terminal shall decline or terminate the transaction

•







•


•


•


•

LT responds with AAC to second GENERATE AC digitally signed (same process as a TC) in format 2.



•


•

This pass criteria only applies if the terminal has the ability to store declined transactions: TVR byte 1, bit 3 (ie Combined DDA/AC Generation failed) shall be set.

•


•



Page 770




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:

•


•

TAC and IAC are set so that an ARQC is requested at first GENERATE AC and a TC is requested at second GENERATE AC.

•


•

LT responds with AAC to second GENERATE AC digitally signed (same process as a TC) in format 2.



•


•

This pass criteria only applies if the terminal has the ability to store declined transactions: TVR byte 1, bit 3 (ie Combined DDA/AC Generation failed) shall be set.

•


•





Page 772




Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA request at Configuration: GENAC1, ARQC] supported and [CDA request at GENAC2, TC]


•


•




•


•

P1 = Reference Control Parameter (50 - TC, 90 - ARQC).






•


•


•

Issuer response indicates approval.



•


•

Second GENERATE AC P1 ‘50‘- TC.


Page 774




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:

•


•


•

Terminal unable to go online



•


•

P1 = Reference Control Parameter (50 - TC).



2CC.135.00 Mandatory data objects are not present in response to generate AC, in Enhanced Combined DDA/AC Test No: 2CC.135.00 - Revision 16 - Number of sub cases: 6 Objective: To ensure that the terminal checks that the data in table 16, Book 2,

section 6.6.1 is present. By using Combined DDA/AC Data Authentication. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation


Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Book Bulletins - Section SU 54 - Bulletin No.54, Missing Mandatory Command Response Data (Nov 2006) Terminal [CDA] supported AND ([Offline Only] OR [Offline/Online capable]) Configuration: supported Conditions:

•


•


•

LT responds to GENERATE AC command in format 2

•

Case 01: Signed Dynamic Application Data (Tag 9F4B) is not present in TC response to the first GENERATE AC.

•

Case 02: Cryptogram Information Data (Tag 9F27) is not present in TC response to the first GENERATE AC.

•

Case 03: Application Transaction Counter (Tag 9F36) is not present in TC response to the first GENERATE AC.

•

Case 04: LT responds with ARQC to first GENERATE AC and TC to second GENERATE AC, Signed Dynamic Application Data (Tag 9F4B) is not present in TC response to the second GENERATE AC and Terminal is unable to go online.

•

Case 05: LT responds with ARQC to first GENERATE AC and TC to second GENERATE AC, Cryptogram Information Data (Tag 9F27) is not present in TC response to the second


Page 776


2CC.135.00 Mandatory data objects are not present in response to generate AC, in Enhanced Combined DDA/AC GENERATE AC and Terminal is unable to go online. •

Case 06: LT responds with ARQC to first GENERATE AC and TC to second GENERATE AC, Application Transaction Counter (Tag 9F36) is not present in TC response to the second GENERATE AC an terminal is unable to go online.


particular Enhanced Combined DDA/AC). Pass Criteria: The terminal shall terminate the transaction.



2CC.135.01 Mandatory data objects are not present in response to generate AC, in Enhanced Combined DDA/AC (2) Test No: 2CC.135.01 - Revision 15 - Number of sub cases: 3 Objective: To ensure that the terminal checks that the data in table 16, Book 2,

section 6.6.1 is present. By using Combined DDA/AC Data Authentication. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:

Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Book Bulletins - Section SU 54 - Bulletin No.54, Missing Mandatory Command Response Data (Nov 2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA request at Configuration: GENAC2, TC] supported Conditions:

•


•


•


•

Case 01: LT responds with ARQC to first GENERATE AC and TC to second GENERATE AC, Signed Dynamic Application Data (Tag 9F4B) is not present in TC response to the second GENERATE AC.

•

Case 02: LT responds with ARQC to first GENERATE AC and TC to second GENERATE AC, Cryptogram Information Data (Tag 9F27) is not present in TC response to the second GENERATE AC.

•

Case 03: LT responds with ARQC to first GENERATE AC and TC to second GENERATE AC, Application Transaction Counter (Tag 9F36) is not present in TC response to the second GENERATE AC.



Page 778


2CC.135.01 Mandatory data objects are not present in response to generate AC, in Enhanced Combined DDA/AC (2) particular Enhanced Combined DDA/AC). Pass Criteria:

•

The terminal shall terminate the transaction.



2CC.135.02 Mandatory data objects are not present in response to generate AC, in Enhanced Combined DDA/AC (3) Test No: 2CC.135.02 - Revision 15 - Number of sub cases: 3 Objective: To ensure that the terminal checks that the data in table 16, Book 2,

section 6.6.1 is present. By using Combined DDA/AC Data Authentication. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:

Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Book Bulletins - Section SU 54 - Bulletin No.54, Missing Mandatory Command Response Data (Nov 2006) Terminal [CDA] supported AND ([Online Only] AND [Normal Default Action Code Configuration: processing]) supported Conditions:

•


•

TAC and IAC are set so that an ARQC is requested at first GENERATE AC and TC to second GENERATE AC.

•


•

Transaction is unable to go online

•

Case 01: LT responds with ARQC to first GENERATE AC and TC to second GENERATE AC, Signed Dynamic Application Data (Tag 9F4B) is not present in TC response to the second GENERATE AC.

•

Case 02: LT responds with ARQC to first GENERATE AC and TC to second GENERATE AC, Cryptogram Information Data (Tag 9F27) is not present in TC response to the second GENERATE AC.

•

Case 03: LT responds with ARQC to first GENERATE AC and TC to second GENERATE AC, Application Transaction Counter (Tag 9F36) is not present in TC response to the second GENERATE AC.

Action: NA


Page 780


2CC.135.02 Mandatory data objects are not present in response to generate AC, in Enhanced Combined DDA/AC (3) Procedure: Application in LT is selected and transaction is processed with LT (in


•

The terminal shall terminate the transaction.



2CC.136.00 Values of CDOL2 for Transaction Data hash Test No: 2CC.136.00 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal stores the values of the data elements

specified by CDOL2 for Enhanced Combined DDA/AC during 2nd GENERATE AC. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation



•


•

TAC and IAC are set so that a TC is requested at first GENERATE AC and a TC at second GENERATE AC.

•


•

LT sends an ARQC at 1st GENERATE AC, Enhanced Combined DDA/AC is correct at the 1st GENERATE AC.

•

LT sends a TC at 2nd GENERATE AC, Enhanced Combined DDA/AC is correct at the 2nd GENERATE AC.



•


•

TVR and TSI (contained in Financial Confirmation message or Batch Data Capture message or other) shall have: -

TVR byte 1, bit 3 = '0' (ie. Combined DDA/AC Generation succeeded) set.

-


-

TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication


Page 782


2CC.136.00 Values of CDOL2 for Transaction Data hash not failed) set •


•




2CC.136.01 Values of CDOL2 for Transaction Data hash (2) Test No: 2CC.136.01 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal stores the values of the data elements

specified by CDOL2 for Enhanced Combined DDA/AC during 2nd GENERATE AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:



•


•


•


•




•


•



-


-

TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not failed) set


Page 784


2CC.136.01 Values of CDOL2 for Transaction Data hash (2) •


•





specified by CDOL2 for Enhanced Combined DDA/AC during 2nd GENERATE AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:



•


•


•

Transaction is unable to go online.

•


•




•


•



-


-

TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication


Page 786


2CC.136.02 Values of CDOL2 for Transaction Data hash (2) not failed) set •


•




2CC.137.00 Values of PDOL for Transaction Data hash Test No: 2CC.137.00 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal stores the values of the data elements

specified by PDOL for Enhanced Combined DDA/AC at the 2nd GENERATE AC. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation



•


•

TAC and IAC are set so that a TC is requested at first GENERATE AC and a TC at Second GENERATE AC.

•


•


•


•

PDOL is present in LT (Value indicated by PDOL will change between the 1st and the 2nd GENERATE AC).



•


•

TVR and TSI (contained in Financial Confirmation message or Batch Data Capture message or other) shall have:

- TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation succeeded) set. - TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) Copyright ©2008 EMVCo, LLC. All rights reserved

Page 788


2CC.137.00 Values of PDOL for Transaction Data hash set. •


•




2CC.137.01 Values of PDOL for Transaction Data hash (2) Test No: 2CC.137.01 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal stores the values of the data elements

specified by PDOL for Enhanced Combined DDA/AC at the 2nd GENERATE AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:



•


•


•


•


•




•


•


- TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation succeeded) set. - TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) set. Copyright ©2008 EMVCo, LLC. All rights reserved

Page 790


2CC.137.01 Values of PDOL for Transaction Data hash (2) •


•




2CC.137.02 Values of PDOL for Transaction Data hash (3) Test No: 2CC.137.02 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal stores the values of the data elements

specified by PDOL for Enhanced Combined DDA/AC at the 2nd GENERATE AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:



•


•


•


•


•


•




•


•


- TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation succeeded) set. - TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) Copyright ©2008 EMVCo, LLC. All rights reserved

Page 792


2CC.137.02 Values of PDOL for Transaction Data hash (3) set. •


•




2CC.138.00 First Combined DDA/AC generation AAC request Test No: 2CC.138.00 - Revision 13 - Number of sub cases: 0 Objective: To ensure that Enhanced Combined DDA/AC generation is not

requested when the device generates an AAC in the 1st GENERATE AC. Reference Book Bulletins - Section SU 20 - Bulletin n°20, Combined DDA/AC EMV 4.0: Generation (Jan-2004) Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:


•


•

TAC and IAC are such that the terminal requests AAC at first GENERATE AC.



•

The terminal shall process the transaction until completion, as a decline.

•

P1 = '00' at first GENERATE AC


Page 794


2CC.138.01 First Combined DDA/AC generation AAC request Test No: 2CC.138.01 - Revision 13 - Number of sub cases: 0 Objective: To ensure that Enhanced Combined DDA/AC generation is not

requested when the device generates an AAC in the 2nd GENERATE AC. Reference Book Bulletins - Section SU 20 - Bulletin n°20, Combined DDA/AC EMV 4.0: Generation (Jan-2004) Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:


•


•

LT responds with an ARQC in the 1st GENERATE AC

•

TAC and IAC are such that the terminal requests AAC in the second GENERATE AC or Issuer host declines the transaction.



•


•

P1 = '00' at second GENERATE AC



2CC.138.02 First Combined DDA/AC generation AAC request (2) Test No: 2CC.138.02 - Revision 13 - Number of sub cases: 0 Objective: To ensure that Enhanced Combined DDA/AC generation is not

requested when the device generates an AAC in the 2nd GENERATE AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:

Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported [ AND [Online Only] supported Configuration: Conditions:

•


•


•

LT responds with an ARQC in the 1st GENERATE AC

•

TAC and IAC are such that the terminal requests AAC in the second GENERATE AC or Issuer host declines the transaction.



•


•

P1 = '00' at second GENERATE AC


Page 796


2CC.139.00 Values of CDOL1 for Transaction Data hash Test No: 2CC.139.00 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal stores the values of the data elements

specified by CDOL1 for Enhanced Combined DDA/AC at the first GENERATE AC. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation



•


•


•


•

LT sends a TC at 2nd GENERATE AC.



•


•


•


•


•




2CC.139.00 Values of CDOL1 for Transaction Data hash performed) contained in Financial Confirmation message or Batch Data Capture message.


Page 798



specified by CDOL1 for Enhanced Combined DDA/AC at the 2nd GENERATE AC. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation



•


•


•


•


•




•


•


- TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation succeeded) set. - TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) Copyright © 2008 EMVCo, LLC. All Rights Reserved. Page 799


2CC.139.01 Values of CDOL1 for Transaction Data hash (2) set. •


•



Page 800



specified by CDOL1 for Enhanced Combined DDA/AC at the first GENERATE AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:


•


•


•


•

LT sends a TC at 2nd GENERATE AC



•


•


•


•


•




2CC.139.02 Values of CDOL1 for Transaction Data hash (3) Batch Data Capture message.


Page 802



specified by CDOL1 for Enhanced Combined DDA/AC at the 2nd GENERATE AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:



•


•


•


•


•




•


•






•



Page 804



specified by CDOL1 for Enhanced Combined DDA/AC at the 2nd GENERATE AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:



•


•


•


•


•




•


•






•



Page 806


2CC.140.00 2nd GENERATE AC for Combined DDA/AC generation not performed for ARQC Test No: 2CC.140.00 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal does not perform GENERATE AC with

Enhanced Combined DDA/AC request when the terminal option never request an ARQC with Enhanced Combined DDA/AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:

Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable]) Configuration: supported AND [CDA never at GENAC1, ARQC] supported Conditions:

•


•

TAC and IAC set so that the Terminal requests ARQC at first GENERATE AC.



•

The terminal shall process the transaction until completion without CDA at first GENERATE AC.

•

P1 = Reference Control Parameter of first GENERATE AC (80 ARQC).

•

TVR byte 1, bit 8 = '1' (Offline Data Authentication was not performed) received at 1st GENERATE AC.



2CC.141.00 GENERATE AC for Combined DDA/AC generation, case unable to go online, TC Test No: 2CC.141.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that, when unable to go online and a TC is requested, the

terminal perform the 2nd GENERATE AC with Enhanced Combined DDA/AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:

Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND ([Offline/Online capable] supported OR ([Online Configuration: Only] AND [Normal Default Action Code processing])) supported AND

[CDA never at GENAC1, ARQC] supported Conditions:

•


•

TAC and IAC set so that the Terminal requests ARQC at first GENERATE AC and requests a TC at Second GENERATE AC.

•




•


•

The 2nd GENERATE AC is requested as a TC with CDA

•

TVR byte 1, bit 8 = '1' (Offline Data Authentication was not performed) received in 1st GENERATE AC.

•

TVR byte 1, bit 8 = '0' (Offline Data Authentication was performed) received in 2nd GENERATE AC and contained in Financial Confirmation message or Batch Data Capture message.


Page 808


2CC.141.01 GENERATE AC for Combined DDA/AC generation, case unable to go online, AAC Test No: 2CC.141.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that, when unable to go online and an AAC is requested, the

terminal perform the 2nd GENERATE AC without Enhanced Combined DDA/AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:


[CDA never at GENAC1, ARQC] supported Conditions:

•


•

TAC and IAC set so that the Terminal requests ARQC at first GENERATE AC and requests an AAC at Second GENERATE AC.

•




•


•

The 2nd GENERATE AC is requested by the terminal without CDA

•

TVR byte 1, bit 8 = '1' (Offline Data Authentication was not performed) received in 1st GENERATE AC.

•

TVR byte 1, bit 8 = '1' (Offline Data Authentication was not performed) received in 2nd GENERATE AC and contained in Financial Confirmation message or Batch Data Capture message.




Page 810


2CC.141.02 GENERATE AC for Combined DDA/AC generation, case unable to go online, TC (2) Test No: 2CC.141.02 - Revision 13a - Number of sub cases: 0 Objective: To ensure that, when unable to go online and a TC is requested, the

terminal perform the 2nd GENERATE AC with Enhanced Combined DDA/AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:


[CDA request at GENAC1, ARQC] supported Conditions:

•


•


•


•

TAC/IAC-Default B1b8=1 all other are zero filled



•


•

The 2nd GENERATE AC is requested as a TC with CDA

•




2CC.141.03 GENERATE AC for Combined DDA/AC generation, case unable to go online, AAC Test No: 2CC.141.03 - Revision 13a - Number of sub cases: 0 Objective: To ensure that, when unable to go online and an AAC is requested, the

terminal perform the 2nd GENERATE AC without Enhanced Combined DDA/AC. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:


[CDA request at GENAC1, ARQC] supported Conditions:

•


•

TAC and IAC set so that the Terminal requests ARQC at first GENERATE AC and requests an AAC at Second GENERATE AC.

•




•


•


•



Page 812


2CC.142.00 2nd GENERATE AC for Combined DDA/AC generation, Terminal never requesting CDA Test No: 2CC.142.00 - Revision 15 - Number of sub cases: 0 Objective: When supporting options not to request CDA for online requests and

successful online approvals CDA is not requested. Reference EMV 4.0: Reference Book 2 - Section 6.6.1 - Dynamic Signature Generation EMV 4.1:

Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND ([Offline/Online capable] supported OR [Online Configuration: Only] supported) AND [CDA never at GENAC1, ARQC] supported AND

[CDA never at GENAC2, TC] supported Conditions:

•


•




•


•


•

TVR byte 1, bit 8 = '1' (Offline Data Authentication was not performed) contained in Financial Confirmation message or Batch Data Capture message.



2CC.143.00 Response to GENERATE AC when responding TC or ARQC can be in format 1 without CDA Test No: 2CC.143.00 - Revision 15 - Number of sub cases: 3 Objective: To ensure that the terminal can use the ICC response format 1 as

specified in book 3, part I, without Enhanced Combined DDA/AC even when CDA is supported in AIP Reference EMV 4.0: Reference Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal EMV 4.1: behaviour (Sept-2006) Terminal [CDA] supported AND ([Online Only] OR [Offline/Online capable]) Configuration: supported AND [CDA never at GENAC1, ARQC] supported Conditions:

•


•

LT response to GENERATE AC is in format 1 without CDA.

•


•

LT answers with an ARQC to first GENERATE AC.



•

The terminal shall process the transaction until completion by requesting a TC or an AAC.

•

The Terminal shall accept the response in format 1


Page 814


2CC.144.00 Hash Result of SDA calculated with a long string of data Test No: 2CC.144.00 - Revision 17 - Number of sub cases: 0 Objective: To ensure that the terminal performs correctly the Static Data

Authentication process if the Hash Result of the Signed Static Application Data is calculated with a long string of data Reference EMV 4.0: Reference Book 2 - Section 5.4 - Verification of Signed Static Application Data EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

Length length NI = 247 bytes, length NCA = 248 bytes.

•

Exponent of Issuer Public Key is 3.

•

Signed Static Application Data in LT is calculated with the following:

•

o

An EMV file containing all the usual EMV signed data and containing in separate record where the signed data is one proprietary tag filled with 00s followed by 00 padding upto the maximum record size (252 bytes in template ‘70’).

o

Another EMV file (in the SFI range 1 to 10) with 3 signed records, one of 127 bytes in length (with a proprietary tag and with the length coded in a single byte length), one with 127 bytes (with a proprietary tag and with the length coded in two bytes length) and one with the maximum record size length (252 bytes in template ‘70’).

o

Sign all allowable EMV records of all EMV files of the LT (some data such as AFL, Issuer Certificate and SSAD cannot be included)

AFL are built correctly including the reference of the data authentication of the above records.

Action: NA



2CC.144.00 Hash Result of SDA calculated with a long string of data Procedure: Application in LT is selected and transaction is processed with LT (in


•


•

TVR byte 1, bit 7 = '0' (ie Offline Static Data Authentication successful) received at 1st GENERATE AC.

•


•


•



Page 816


2CC.144.01 Hash Result of ICC Public Key calculated with a long string of data Test No: 2CC.144.01 - Revision 17 - Number of sub cases: 0 Objective: To ensure that the terminal performs correctly the Dynamic Data

Authentication process if the Hash Result of the ICC Public Key Certificate is calculated with a long string of data Reference EMV 4.0: Reference Book 2 - Section 6.3 – Retrieval of ICC Public Key EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

Length NIC = 247 bytes, length NI = 247 bytes, length NCA = 248 bytes.

•

Exponent of Issuer Public Key is 3.

•

Static Application Data to be authenticated in LT is calculated with the following:

•

o


o


o





2CC.144.01 Hash Result of ICC Public Key calculated with a long string of data Action: NA Procedure: Application in LT is selected and transaction is processed with LT (in


•


•


•


•

TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication successful) received at 1st GENERATE AC.

•



Page 818


2CC.144.02 Hash Result of ICC Public Key calculated with a long string of data (2) Test No: 2CC.144.02 - Revision 17 - Number of sub cases: 0 Objective: To ensure that the terminal performs correctly the Combined Data

Authentication process if the Hash Result of the ICC Public Key Certificate is calculated with a long string of data Reference EMV 4.0: Reference Book 2 - Section 6.3 – Retrieval of ICC Public Key EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•


•

Exponent of ICC Public Key is 3.

•

Static Application Data to be authenticated in LT is calculated with the following:

•

o


o


o



Action: NA



2CC.144.02 Hash Result of ICC Public Key calculated with a long string of data (2) Procedure: Application in LT is selected and transaction is processed with LT (in


•


•


•

TVR byte 1, bit 3 = '0' (ie Combined Data Authentication successful) received at 1st GENERATE AC or not used.

•



Page 820


Data Objects



2CE.001.00 Length field: 1 byte Test No: 2CE.001.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal is able to support Data Object with Length on 1

byte (b8 = 0). Reference Book 3 - Section Annex B - Rules for BER-TLV Data Objects EMV 4.0: Reference Book 3 - Section Annex B - Rules for BER-TLV Data Objects EMV 4.1: Terminal NA Configuration: Conditions: LT contains Data Objects to be read with length on one byte (PAN for

instance). Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall process the transaction until completion and shall

correctly manage the Data Object received with length coded on 1 byte.


Page 822


2CE.001.01 Length field: 2 bytes Test No: 2CE.001.01 - Revision 10g - Number of sub cases: 2 Objective: To ensure that terminal is able to support Data Object with Length on 2

bytes (81 xx). Reference Book 3 - Section Annex B - Rules for BER-TLV Data Objects EMV 4.0: Reference Book 3 - Section Annex B - Rules for BER-TLV Data Objects EMV 4.1: Terminal NA Configuration: Conditions: LT contains Data Object with length coded on 2 bytes:

•

Case 01: LT contains PAN

•

Case 02: LT contains Issuer Public Key with length >127 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 and shall

correctly manage the Data Object received with length coded on 2 bytes.



2CE.003.00 Recognition of ‘Space’ characters in AN formatted Data Objects Test No: 2CE.003.00 - Revision 13 - Number of sub cases: 0 Objective: To ensure that terminal accepts data objects from the ICC with ‘space’

characters included in AN defined fields. Reference Book Bulletins - Section SU 14 - Bulletin n°14, Change to format EMV 4.0: specification for the Application Label and Application Preferred Name

(Oct-2002) Reference EMV 4.1: Terminal NA Configuration: Conditions:

•

LT shall contain the following data objects with at least one ‘space’ character in each data object:

- Application Preferred Name. - Application Label. •

LT shall contain the Issuer Code Table Index.


•


•

If the terminal has a display and supports Cardholder Confirmation, the Application Preferred Name shall be displayed with the ‘space’ if the terminal supports the Issuer Code Table Index within the LT.

•

If the terminal has a display and supports Cardholder Confirmation, but is unable to support the Application Preferred Name, the terminal shall display Application Label with the ‘space’ using the Common Character Set.


Page 824


2CE.003.01 Acceptance of format errors for Selection data objects PSE Test No: 2CE.003.01 - Revision 10g - Number of sub cases: 00 Objective: The terminal accepts application selection data objects from the ICC

with format errors, when processing PSE. Reference Book Bulletins - Section AN 7-02 - Bulletin n°7, Data Element Format EMV 4.0: Convention Definition (Jun-2004)

Book Bulletins - Section SU 14 - Bulletin n°14, Change to format specification for the Application Label and Application Preferred Name (Oct-2002) Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 12.2.5 - Error Handling for FCI Response Data EMV 4.1: Terminal [PSE] supported Configuration: Conditions:

•

LT contains PSE.

•

LT shall contain the following data objects with the specified value, resulting in a format error:

•

FCI of the PSE contains Language Preference = '23 33'.

•

FCI of the PSE contains Issuer Code Table Index = ‘F1’.

•

ADF Entry contains Application Label = ’00 00 00 41 50 50 20 7F 7F 7F’.

•

ADF Entry contains Application Preferred Name = ’01 02 03 41 42 43 44 7F 7F 7F’.

Action: NA Procedure: Application in LT is selected with PSE and transaction is processed

with LT. Pass Criteria: The terminal shall process the transaction until completion, by




2CE.003.02 Acceptance of format errors for Selection data objects List of AIDs Test No: 2CE.003.02 - Revision 15 - Number of sub cases: 04 Objective: The terminal accepts application selection data objects from the ICC

with format errors, when processing List of AIDs. Reference Book Bulletins - Section AN 7-02 - Bulletin n°7, Data Element Format EMV 4.0: Convention Definition (Jun-2004)

Book Bulletins - Section SU 14 - Bulletin n°14, Change to format specification for the Application Label and Application Preferred Name (Oct-2002) Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 12.2.5 - Error Handling for FCI Response Data EMV 4.1:

Book 3 - Section 7.5 – Erroneous or Missing Data in the ICC Book Bulletins - Section SU 49 - Bulletin n°49, Data Errors During List of AID Selection (July-2006) Terminal NA Configuration: Conditions:

•

LT does not contain PSE.

•

The terminal contains exactly one AID which exactly matches one DF Name of the LT

•


•

Case 01: LT shall contain the following data objects with the specified value, resulting in a format error:

•

-

FCI of an ADF contains Application Label = ’00 00 00 41 50 50 20 7F 7F 7F’.

-

FCI of an ADF contains Language Preference = ’23 33’

-

FCI of an ADF contains Issuer Code Index = ‘F1’

-

FCI of an ADF contains Application Preferred Name = ’01 02 03 41 42 43 44 7F 7F 7F’.

Case 02: The SELECT response contains a format error on the


Page 826


2CE.003.02 Acceptance of format errors for Selection data objects List of AIDs Application Label, unrelated to length. •

Case 03: The SELECT response contains a Language Preference coded as: '5F 2D 05 xx xx xx xx yy' where x are some values consistent with ISO 639 and 'yy' is any value other than '00' or 'FF'.

•

Case 04: The SELECT response duplicates the Issuer Code Index table.

Action: NA Procedure: Application in LT is selected with List of AIDs and transaction is

correctly processed with LT. Pass Criteria: The terminal shall process the transaction until completion, by




2CE.003.03 Acceptance of format errors for Selection data objects – FINAL SELECT Test No: 2CE.003.03 - Revision 10g - Number of sub cases: 00 Objective: The terminal accepts application selection data objects from the ICC

with format errors, when processing FINAL SELECT. Reference Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during EMV 4.0: Application Selection (Jun-2004) Reference Book 1 - Section 12.4 - Final Selection EMV 4.1: Terminal NA Configuration: Conditions:

•


•

FCI of an ADF of FINAL SELECT contains Application Label = ’00 00 00 41 50 50 20 7F 7F 7F’.

•

FCI of an ADF of FINAL SELECT contains Language Preference = '23 33'.

•

FCI of an ADF of FINAL SELECT contains Issuer Code Table Index = ‘F1’.

•

FCI of an ADF of FINAL SELECT contains Application Preferred Name = ’01 02 03 41 42 43 44 7F 7F 7F’.

Action: NA Procedure: Application in LT is selected with List of AIDs and transaction is

correctly processed with LT. Pass Criteria: The terminal shall process the transaction until completion, by



Page 828


2CE.003.04 Inconsistent selection data for FCI of the PSE and FCI of ADF Test No: 2CE.003.04 - Revision 10g - Number of sub cases: 00 Objective: To ensure that the terminal does not terminate the transaction if data is

located in several places with different values during Application Selection. Reference Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during EMV 4.0: Application Selection (Jun-2004) Reference Book 1 - Section 12.2.5 - Error Handling for FCI Response Data EMV 4.1: Terminal [PSE] supported Configuration: Conditions:

•

LT contains PSE.

•

LT shall contain the following data objects in the given location:

•

FCI of the PSE contains Language Preference = ’65 6E’.

•

FCI of the PSE contains Issuer Code Table Index = ’01’.

•

FCI of ADF returned to Final SELECT contains Language Preference = ’66 72’.

•

FCI of ADF returned to Final SELECT contains Issuer Code Table Index = ’02’.

Action: NA Procedure: Application Selection with PSE method is performed. Pass Criteria:

•


•

The terminal may use the varying data from either location.



2CE.003.05 Inconsistent selection data between list of AIDs and FINAL ADF Test No: 2CE.003.05 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal does not terminate the transaction if data is

located in several places with different values during Application Selection. Reference Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during EMV 4.0: Application Selection (Jun-2004) Reference Book 1 - Section 12.2.5 - Error Handling for FCI Response Data EMV 4.1: Terminal NA Configuration: Conditions:

•

LT does not contain PSE.

•

The LT shall contain two ADFs both of which are supported by the terminal

•

LT shall contain the following data objects in the specified location:

•

ADF1 - FCI of the ADF contains Application Label = ’45 4D 56 43 4F 30 30 31’. - FCI of the ADF contains Application Preferred Name = ’45 4D 56 43 4F 30 30 31 54 45 53 54’. - FCI of the ADF contains Language Preference = ’65 6E’. - FCI of the ADF contains Issuer Code Table Index = ’01’.

•

ADF2 -

•

FCI of the ADF contains Application Label = ’45 4D 56 43 4F 30 30 31’. FCI of the ADF contains Application Preferred Name = ’45 4D 56 43 4F 30 30 31 54 45 53 54’. FCI of the ADF contains Language Preference = ’65 6E’.

Either ADF is returned is choosen for the Final SELECT process and the selected application shall return:

o

-

Language Prefernce: '66 72'

-

Issuer Code Table Index: '02'

Action: NA


Page 830


2CE.003.05 Inconsistent selection data between list of AIDs and FINAL ADF Procedure: Application Selection using list of AIDs method is performed. Pass Criteria:

•


•

The terminal may use the varying data from either location.



2CE.003.06 Inconsistent data: only one occurrence in PSE or FINAL SELECT Test No: 2CE.003.06 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal does not terminate the transaction if the

card contains only one occurrence (in PSE or FINAL SELECT) of a data object that should exist in both places. Reference Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during EMV 4.0: Application Selection (Jun-2004) Reference Book 1 - Section 12.2.5 - Error Handling for FCI Response Data EMV 4.1: Terminal [PSE] supported Configuration: Conditions:

•

LT contains PSE.

•

Case 01: FCI of the PSE: Language preference - not present and Issuer Code Table Index - not present. FCI of ADF returned to Final SELECT contains: Language Preference = ’65 6E’ and Issuer Code Table Index = ’01’.

•

Case 02: FCI of the PSE contains: Language preference = ’65 6E’ and Issuer Code Table Index = ’01’. FCI of ADF returned to Final SELECT: Language Preference - not present and Issuer Code Table Index - not present.

Action: NA Procedure: Application Selection with PSE method is performed. Pass Criteria: The terminal shall process the transaction until completion, by



Page 832


2CE.003.07 Inconsistent data: only one occurrence in SELECT ADF or FINAL SELECT Test No: 2CE.003.07 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal does not terminate the transaction if the

card contains only one occurrence (in SELECT ADF or FINAL SELECT) of a data object that should exist in both places. Reference Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during EMV 4.0: Application Selection (Jun-2004) Reference Book 1 - Section 12.2.5 - Error Handling for FCI Response Data EMV 4.1: Terminal NA Configuration: Conditions:

•

LT does not contains PSE.

•

Case 01: FCI of the ADF does not contain: Application Label, Application Preferred Name, Language preference or Issuer Code Table Index. FCI of the ADF returned to Final SELECT contains Application label = ’45 4D 56 43 4F 30 30 31’, Application Preferred Name = ’45 4D 56 43 4F 30 30 31 54 45 53 54’, Language Preference = ’65 6E’, Issuer Code Table Index = ’01’.

•

Case 02: FCI of the ADF contains Application label = ’45 4D 56 43 4F 30 30 31, Application Preferred Name = ’45 4D 56 43 4F 30 30 31 54 45 53 54’, Language preference = ’65 6E’, Issuer Code Table Index = ’01’. FCI of ADF returned to Final SELECT does not contain:, Application Label, Application Preferred Name, Language Preference, Issuer Code Table Index.

Action: NA Procedure: Application Selection using list of AIDs method is performed. Pass Criteria: The terminal shall process the transaction until completion, by




2CE.003.08 List of AID format errors Test No: 2CE.003.08 - Revision 12 - Number of sub cases: 07 Objective: The terminal continues the processing the transaction as expected

when encountering format errors, on significant data objects, while processing list of AID. Reference EMV 4.0: Reference Book 1 - Section 12.2.5 - Error handling for FCI Response Data EMV 4.1:

Book Bulletins - Section SU49 – Bulletin n°49, Data Errors During List of AID Selection (July-2006) Terminal NA Configuration: Conditions:

•

LT does not support PSE

•

The terminal contains at least two AIDs which exactly match two DF names of the LT

•

Case 01: The SELECT Response to one terminal AID contains a format error on the FCI template, which does not parse correctly

•

Case 02: The SELECT Response to one terminal AID contains a DF Name longer than 16 bytes

•

Case 03: The SELECT Response to one terminal AID contains a format error on the FCI proprietary template, which does not parse correctly

•

Case 04: The SELECT Response to one terminal contains a Application Priority Indicator longer than 1 byte

•

Case 05: The SELECT Response to one terminal AID duplicates the PDOL

•

Case 06: The SELECT Response to one terminal AID contains a format error on the FCI Issuer Discretionary Data, which does not parse correctly

•

Case 07: The SELECT Response to one terminal AID duplicates the Log Entry.

Action: NA


Page 834


2CE.003.08 List of AID format errors Procedure: Application in LT is selected with List of AIDs and transaction is

correctly processed with LT. Pass Criteria: •

•

The AID / DF Name with the format error is not added to the candidate list. The terminal shall process the transaction until completion, by requesting a TC or an AAC.



Approved Cryptography Algorithm


Page 836


2CH.001.00 The Relationship Between the Lengths of the CA, Issuer, and ICC Public Keys Test No: 2CH.001.00 - Revision 10g - Number of sub cases: 2 Objective: To ensure that if terminal supports the Static Data Authentication, it

supports Public key Moduli with length verifying NI <= NCA. Reference Book Bulletins - Section AN 5 - Bulletin n°5, Key Length Terminal EMV 4.0: Checking Requirements Clarification (Jun-2002) Reference EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

Case 01: NI
•

Case 02: NI=NCA , Static signature in LT is valid.



•


•

TVR byte 1, bit 7 ='0' (ie Offline Static Data Authentication succeeded) received at 1st GENERATE AC.

•


•


•




2CH.001.01 The Relationship Between the Lengths of the CA, Issuer, and ICC Public Keys (2) Test No: 2CH.001.01 - Revision 10g - Number of sub cases: 2 Objective: To ensure that if terminal supports Dynamic Data Authentication, it

supports Public key Moduli with length verifying NIC <= NI <= NCA. Reference Book Bulletins - Section AN 5 - Bulletin n°5, Key Length Terminal EMV 4.0: Checking Requirements Clarification (Jun-2002) Reference EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

Case 01: NIC
•

Case 02: NIC = NI = NCA , Dynamic signature computed by LT is valid.



•


•


•


•


•



Page 838


2CH.001.02 The Relationship Between the Lengths of the CA, Issuer, and ICC Public Keys (3) Test No: 2CH.001.02 - Revision 11 - Number of sub cases: 2 Objective: To ensure that if terminal supports the Combined DDA/AC Data

Authentication, it supports Public key Moduli with length verifying NIC <= NI <= NCA. Reference Book Bulletins - Section AN 5 - Bulletin n°5, Key Length Terminal EMV 4.0: Checking Requirements Clarification (Jun-2002) Reference EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•

Case 01: NIC
•

Case 02: NIC = NI = NCA , Dynamic signature computed by LT is valid.


•


•


•


•


•




2CH.001.03 The Relationship Between the Lengths of the CA, Issuer, and ICC PIN Encipherment Keys (4) Test No: 2CH.001.03 - Revision 13 - Number of sub cases: 2 Objective: To ensure that if terminal supports PIN Encipherment, it supports

Public key Moduli with length verifying NPE <= NI <= NCA. Reference Book Bulletins - Section AN 5 - Bulletin n°5, Key Length Terminal EMV 4.0: Checking Requirements Clarification (Jun-2002) Reference EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•

Case 01: NPE
•

Case 02: NPE = NI = NCA , PIN encipherment block computed by LT is valid.


•


•


•



Page 840


2CH.001.04 The Relationship Between the Lengths of the CA, Issuer, and ICC Public Keys (5) Test No: 2CH.001.04 - Revision 10g - Number of sub cases: 2 Objective: To ensure that if terminal supports PIN Encipherment, it supports

Public key Moduli with length verifying NIC <= NI <= NCA. Reference Book Bulletins - Section AN 5 - Bulletin n°5, Key Length Terminal EMV 4.0: Checking Requirements Clarification (Jun-2002) Reference EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•

Case 01: NIC
•

Case 02: NIC = NI = NCA , PIN encipherment block computed by LT is valid.


•


•


•




2CH.003.00 Upper bound for size of moduli Test No: 2CH.003.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if terminal supports Static Data Authentication, it

supports Public key Moduli with maximum length as defined below: max NI length is 248 bytes. max NCA length is 248 bytes. Reference Book 2 - Section B2.1 - RSA Algorithm EMV 4.0: Reference Book 2 - Section B2.1 - RSA Algorithm EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

Length NI = 248 bytes, length NCA = 248 bytes.

•




•


•

TVR byte 1, bit 7 ='0' (ie Offline Static Data Authentication succeeded) received at 1st GENERATE AC.

•


•

TVR byte 1, bit 4 = '0' (ie Dynamic Data Authentication not used) received at 1st GENERATE A.

•



Page 842


2CH.003.01 Upper bound for size of moduli (2) Test No: 2CH.003.01 - Revision 14 - Number of sub cases: 2 Objective: To ensure that if terminal supports Dynamic Data Authentication, it

supports Public key Moduli with maximum length as defined below: max NIC length is 247 bytes. max NI length is 247 bytes. max NCA length is 248 bytes. Reference Book 2 - Section B2.1 - RSA Algorithm EMV 4.0:

Book Bulletins - Section AN 8 - Bulletin n°8, Issuer and ICC Public Key Length Restrictions (Feb-2003) Reference Book 2 - Section B2.1 - RSA Algorithm EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•


•


•

Case 01: INTERNAL AUTHENTICATE response field is in format 1.

•

Case 02: INTERNAL AUTHENTICATE response field is in format 2.



•


•




2CH.003.01 Upper bound for size of moduli (2) succeeded) received at 1st GENERATE AC. •


•


•



Page 844


2CH.003.02 Upper bound for size of moduli (3) Test No: 2CH.003.02 - Revision 12 - Number of sub cases: 0 Objective: To

ensure that if terminal supports Combined DDA/AC Data Authentication, it supports Public key Moduli with maximum length as defined below: max NIC length is 238 bytes. max NI length is 247 bytes. max NCA length is 248 bytes.

Reference Book 2 - Section B2.1 - RSA Algorithm EMV 4.0:

Book Bulletins - Section AN 8 - Bulletin n°8, Issuer and ICC Public Key Length Restrictions (Feb-2003) Reference Book 2 - Section B2.1 - RSA Algorithm EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•


•

Dynamic signature computed by LT is valid, and:

•

LT response of GENERATE AC is in format 2 and IAD is not present.

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. •


•




2CH.003.02 Upper bound for size of moduli (3) received at 1st GENERATE AC. •


•



Page 846


2CH.003.03 Upper bound for size of moduli (4) Test No: 2CH.003.03 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if terminal supports PIN Encipherment, it supports

Public key Moduli with maximum length as defined below: max NPE length is 247 bytes. max NI length is 247 bytes. max NCA length is 248 bytes. Reference Book 2 - Section B2.1 - RSA Algorithm EMV 4.0:

Book Bulletins - Section AN 8 - Bulletin n°8, Issuer and ICC Public Key Length Restrictions (Feb-2003) Reference Book 2 - Section B2.1 - RSA Algorithm EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•

Length NPE = 247 bytes, length NI = 247 bytes, length NCA = 248 bytes.


•


•


•




2CH.003.04 Upper bound for size of moduli (5) Test No: 2CH.003.04 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if terminal supports PIN Encipherment, it supports

Public key Moduli with maximum length as defined below: max NIC length is 247 bytes. max NI length is 247 bytes. max NCA length is 248 bytes. Reference Book 2 - Section B2.1 - RSA Algorithm EMV 4.0:

Book Bulletins - Section AN 8 - Bulletin n°8, Issuer and ICC Public Key Length Restrictions (Feb-2003) Reference Book 2 - Section B2.1 - RSA Algorithm EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•



•


•


•



Page 848


File for Financial Transaction Interchange



2CI.001.00 READ RECORD with the Short File Identifiers (SFI) ranged from 1 to 10 Test No: 2CI.001.00 - Revision 10g - Number of sub cases: 10 Objective: To ensure that the terminal is able to read data in file with SFI in range

1 to 10 (0x01 to 0x0A) using READ RECORD command. Reference Book 3 - Section 3 - Files for Financial Transaction Interchange EMV 4.0: Reference Book 3 - Section 7 - Files for Financial Transaction Interchange EMV 4.1: Terminal NA Configuration: Conditions:

•

Case 01: PAN is located in file with SFI 01.

•


•


•


•


•


•


•


•


•





Page 850


2CI.002.00 READ RECORD in linear files Test No: 2CI.002.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal is able to read data in file with linear

structure and records with fixed size or variable size using READ RECORD commands. Reference Book 3 - Section 3 - Files for Financial Transaction Interchange EMV 4.0: Reference Book 3 - Section 7 - Files for Financial Transaction Interchange EMV 4.1: Terminal NA Configuration: Conditions:

•

One Mandatory Data Element (PAN for instance) is located in file with linear structure and records with fixed size.

•

Another Mandatory Data Element (Expiration Date for Instance) is located in file with linear structure and records with variable size.





2CI.003.00 READ RECORD in files containing multiple records Test No: 2CI.003.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal is able to read data in file with several

records using READ RECORD commands. Reference Book 3 - Section 3 - Files for Financial Transaction Interchange EMV 4.0: Reference Book 3 - Section 7 - Files for Financial Transaction Interchange EMV 4.1: Terminal NA Configuration: Conditions:

•

One Mandatory Data Element (PAN for instance) is located in first record of a file.

•

Another Mandatory Data Element (Expiration Date for Instance) is located in second record of same file.

•

Another Mandatory Data Element (CDOL1 and CDOL2 for Instance) is located in third record of same file.




Page 852


2CI.004.00 READ RECORD with the record size in the range from 1 to 254 bytes Test No: 2CI.004.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal is able to read data in file with record size in

range from 1 to 254 bytes using READ RECORD commands. Reference Book 3 - Section 3 - Files for Financial Transaction Interchange EMV 4.0: Reference Book 3 - Section 7 - Files for Financial Transaction Interchange EMV 4.1: Terminal NA Configuration: Conditions:

•

A record containing only the template and length equals 00 (70 00) is located in a single record.

•

A Data Element with 'average length' is located in a single record (for instance Signed Static Application Data or CDOL1).

•

A Data Element with maximum length (Total length including Tag and Length and Template is 254) is located in a single record (for instance CDOL1)





2CI.005.00 Record Data Format Test No: 2CI.005.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal is able to extract data read in record from

template ‘70’. Reference Book 3 - Section 3 - Files for Financial Transaction Interchange EMV 4.0: Reference Book 3 - Section 7 - Files for Financial Transaction Interchange EMV 4.1: Terminal NA Configuration: Conditions: Mandatory Data Elements (PAN, Expiration Date, CDOL1 and CDOL2)

are located in a record within template 0x70. 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



Page 854


2CI.007.00 Free access conditions for files accessible using the READ RECORD command Test No: 2CI.007.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal is able to access file with READ RECORD

command. Reference Book 3 - Section 3 - Files for Financial Transaction Interchange EMV 4.0: Reference Book 3 - Section 7 - Files for Financial Transaction Interchange EMV 4.1: Terminal NA Configuration: Conditions: Mandatory Data Elements are located in a file accessible with READ

RECORD 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




2CI.009.00 Mandatory Data Objects: Application Expiration Date Test No: 2CI.009.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal checks that mandatory Data Object

Application Expiration Date is present in the card and is able to use it. Reference Book 3 - Section 3.1 - Mandatory Data Objects EMV 4.0: Reference Book 3 - Section 7.2 - Mandatory Data Objects EMV 4.1: Terminal NA Configuration: Conditions: Application Expiration Date is present 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



Page 856


2CI.010.00 Mandatory Data Objects: PAN Test No: 2CI.010.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal checks that mandatory Data Object PAN is

present in the card and use it. Reference Book 3 - Section 3.1 - Mandatory Data Objects EMV 4.0: Reference Book 3 - Section 7.2 - Mandatory Data Objects EMV 4.1: Terminal NA Configuration: Conditions: PAN is present 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




2CI.010.01 Length of Mandatory Data Objects: PAN Test No: 2CI.010.01 - Revision 10g - Number of sub cases: 10 Objective: To ensure that terminal accepts the Application PAN with a variety of

lengths up to 19 digits. Reference Book 3 - Section 3.1 - Mandatory Data Objects EMV 4.0: Reference Book 3 - Section 7.2 - Mandatory Data Objects EMV 4.1: Terminal NA Configuration: Conditions:

•

CDOL1 requests Application PAN.

•

10 tests are performed with varying lengths of the Application PAN:

•

Case 01: LT contains PAN with length ‘5 bytes’ (CN 10).

•


•


•


•


•


•


•


•


•

Case 10: LT contains PAN with length ’10 bytes’ (CN 19).


•


•

First GENERATE AC will contain the PAN as read from the LT.


Page 858




2CI.011.00 Padding of Data Objects: Track 2 equivalent Data Test No: 2CI.011.00 - Revision 12 - Number of sub cases: 3 Objective: To ensure that terminal accepts the Track 2 equivalent Data with a

variety of lengths up to 19 bytes padded with 'F' when needed. Reference Book 3 - Section Table A1 - Data Elements Dictionary EMV 4.0:

Book Bulletins - Section AN 18 - Bulletin n°18, Track 2 Equivalent Data Padding (Dec-2003) Reference Book 3 - Section Table 33 - Data Elements Dictionary EMV 4.1: Terminal NA Configuration: Conditions:

•

CDOL1 requests Track 2 Equivalent Data.

•

3 tests are performed with varying lengths of the Track 2 equivalent Data:

•

Case 01: LT contains Track 2 equivalent Data with 15 bytes length, 14.5 bytes used, with an 'F' padding at the end.

•

Case 02: LT contains Track 2 equivalent Data with 16 bytes length, all bytes used, thus no padding.

•

Case 03: LT contains Track 2 equivalent Data with 19 bytes length, 18.5 bytes used, with an 'F' padding at the end.


particular Read Application Data with padding). Pass Criteria:

•


•

First GENERATE AC will contain the Track 2 Equivalent Data as read from the LT.


Page 860


2CI.013.00 Optional Data Objects Test No: 2CI.013.00 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal accepts presence or absence of optional

Data Objects. Reference Book 3 - Section 3.1 - Mandatory Data Objects EMV 4.0: Reference Book 3 - Section 7.2 - Mandatory Data Objects EMV 4.1: Terminal NA Configuration: Conditions:

•

Test is made for the presence and the absence of all Optional Data Objects coming from card (source = ICC in Table A-1 Data Elements Dictionary) and read with READ RECORD.

•

Presence of Mandatory data Object listed in Book 3 table II-2, table II-3, table II-4 is not tested.

•

Proprieraty Templates (e.g. FCI Proprietary Template) are tested with the presence of proprietary data objects inside.

•

Case 01: no optional data objects are present.

•

Case 02: all optional data objects are present.





2CI.014.00 Mandatory Data Objects for Offline Static Data Authentication Test No: 2CI.014.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal verifies presence in the card of mandatory

Data Objects used for Offline Static Data Authentication (if supported), and that it uses these objects. Reference Book 3 - Section 3.1 - Mandatory Data Objects EMV 4.0: Reference Book 3 - Section 7.2 - Mandatory Data Objects EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

Certification Authority Public Key Index is present in LT.

•

Issuer Public Key Certificate is present in LT.

•

Signed Static Application Data is present in LT.

•

Issuer Public Key Remainder is present in LT (The Issuer Public Key used in this test case allows the issuer public Key remainder to be present).

•

Issuer Public Key Exponent is present in LT



•


•


•

TVR byte 1, bit 6 = '0' (ie No ICC Data missing) received at 1st GENERATE AC.

•



Page 862


2CI.014.00 Mandatory Data Objects for Offline Static Data Authentication •


•

TSI byte 1 bit 8 = '1' (ie Offline Data authentication was performed) received at 1st GENERATE AC.



2CI.015.00 Mandatory Data Objects for Offline Dynamic Data Authentication Test No: 2CI.015.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal verifies the presence in the card of

mandatory Data Objects used for Offline Dynamic Data Authentication (if supported), and that it uses these objects. Reference Book 3 - Section 3.1 - Mandatory Data Objects EMV 4.0: Reference Book 3 - Section 7.2 - Mandatory Data Objects EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

Certification Authority Public Key Index is present in LT.

•

Issuer Public Key Certificate is present in LT.

•

Issuer Public Key Remainder is present in LT (The Issuer Public Key used in this test case allows the issuer public Key remainder to be present).

•

Issuer Public Key Exponent is present in LT.

•

ICC Public Key Certificate is present in LT.

•

ICC Public Key Remainder is present in LT (The ICC Public Key is used in this test case allows the ICC Public Key remainder to be present).

•

ICC Public Key Exponent is present in LT.

•

DDOL present in the LT.



•


•



Page 864


2CI.015.00 Mandatory Data Objects for Offline Dynamic Data Authentication succeeded) received at 1st GENERATE AC. •

TVR byte 1, bit 6 = '0' (ie No ICC Data missing) received at 1st GENERATE AC.

•


•


•

TSI byte 1 bit 8= '1' (ie Offline Data authentication was performed) received at 1st GENERATE AC.



2CI.017.00 GET DATA on PIN Try Counter Test No: 2CI.017.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal is able to retrieve the PTC using the GET

DATA command. Reference Book 3 - Section 3.2 - Data Retrievable by GET DATA Command EMV 4.0:

Book 4 - Section 2.3.4.1 - Offline CVM Reference Book 3 - Section 7.3 - Data Retrievable by GET DATA Command EMV 4.1:

Book 4 - Section 6.3.4.1 - Offline CVM Terminal ([Get Data for PIN Try Counter] supported AND [Offline Plaintext PIN] Configuration: supported) Conditions:

•


•

CVM in LT is 'Plaintext PIN verification performed by ICC, Always' (01 00).


•


•

LT shall receive a GET DATA command (80 CA 9F 17 00) before receiving the VERIFY command.


Page 866


2CI.017.01 GET DATA on PIN Try Counter (2) Test No: 2CI.017.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal is able to retrieve the PTC using the GET

DATA command. Reference Book 3 - Section 3.2 - Data Retrievable by GET DATA Command EMV 4.0:

Book 4 - Section 2.3.4.1 - Offline CVM Reference Book 3 - Section 7.3 - Data Retrievable by GET DATA Command EMV 4.1:

Book 4 - Section 6.3.4.1 - Offline CVM Terminal ([Get Data for PIN Try Counter] supported AND [Offline Enciphered Configuration: PIN] supported) Conditions:

•


•

CVM in LT is 'Enciphered PIN verification performed by ICC, Always' (04 00).


•


•

LT shall receive a GET DATA command (80 CA 9F 17 00) before receving a GET CHALLENGE command.



2CI.020.00 Either the LCOL or the UCOL data objects is not present in the ICC Test No: 2CI.020.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal aborts velocity checking when either Lower

or Upper consecutive Offline limits are not present in the card. Reference Book 3 - Section 3.2 - Data Retrievable by GET DATA Command EMV 4.0: Reference Book 3 - Section 7.3 - Data Retrievable by GET DATA Command EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•

Case 01: Lower Consecutive Offline limit is not present in LT.

•

Case 02: Upper Consecutive Offline limit is not present in LT.


•

Terminal will terminate Velocity checking, The terminal shall process the transaction until completion, by requesting a TC or an AAC.

•

LT shall not receive a GET DATA command for the ATC ( 80 CA 9F 36 00).

•

LT shall not receive a GET DATA command for the LOATC (80 CA 9F 13 00).


Page 868


2CI.021.00 Data retrievable by GET PROCESSING OPTIONS command Test No: 2CI.021.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the terminal is able to retrieve and understand both AFL

and AIP, using the GET PROCESSING OPTIONS command. Reference Book 3 - Section 3.3 - Data Retrievable by GET PROCESSING EMV 4.0: OPTIONS Reference Book 3 - Section 7.4 - Data Retrievable by GET PROCESSING EMV 4.1: OPTIONS Terminal NA Configuration: Conditions:

•

AFL and AIP are present in the LT.

•


•


•


•


•

AIP of LT indicates Combined Authentication is supported (AIP byte 1 bit 1 = 1).

•

Issuer Authentication Data is sent back to the terminal in emulated response from the issuer.

•

LT shall returns status ’90 00’ in response to EXTERNAL AUTHENTICATE command without returned data field.

•

Issuer authentication shall be verified by CDOL2 if terminal has online capability.

Action: NA Procedure: Application in LT is selected and transaction is processed with LT.



2CI.021.00 Data retrievable by GET PROCESSING OPTIONS command Pass Criteria:

•


•

LT shall receive a GET PROCESSING OPTIONS command.

•

LT shall receive a sequence of READ RECORD according to AFL.

•

TVR, TSI and command received by the LT shall reflect options supported in AIP (Offline Authentication, Cardholder Verification, Terminal Risk Management and Issuer Authentication) and terminal configurations, received at 1st GENERATE AC and received at 2nd GENERATE AC.


Page 870


2CI.023.00 Functions not specified in the AIP: Offline Static Data Authentication Test No: 2CI.023.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal does not perform Offline Static Data

Authentication if not supported in AIP. Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

AIP of LT indicates Static Data Authentication is not supported (AIP byte 1 bit 7 = 0).

•

AIP of LT indicates Dynamic Data Authentication is not supported (AIP byte 1 bit 6 = 0).

•

AIP of LT indicates CDA is not supported (AIP byte 1 bit 1 = 0).


•


•

TVR byte 1, bit 8 = '1' (ie Offline Data Authentication was not performed) received at 1st GENERATE AC.

•


•


•

TSI byte 1, bit 8 = '0' (ie Offline Data Authentication was not performed) received at 1st GENERATE AC.



2CI.025.00 Functions not specified in the AIP: Offline Dynamic Data Authentication Test No: 2CI.025.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal does not perform Offline Dynamic Data

Authentication if not supported in AIP. Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•


•



•


•


•


•


•



Page 872


2CI.027.00 Functions not specified in the AIP: Cardholder verification Test No: 2CI.027.00 - Revision 17 - Number of sub cases: 0 Objective: To ensure that the terminal does not perform Cardholder Verification if

not supported in AIP. Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1:

Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal NA Configuration: Conditions:

•

AIP of LT indicates Cardholder Verification is not supported (AIP byte 1 bit 5 = 0).

•

CVM is present in LT and indicates 'Fail CVM, always' (00 00).


•


•

TVR byte 3, bit 8 = '0' (ie Cardholder Verification is successful) received at 1st GENERATE AC.

•

TSI byte 1, bit 7 = '0' (ie Cardholder Verification was not performed) received at 1st GENERATE AC.

•

CVM result = (3F 00 00), meaning no CVM performed.



2CI.028.00 Functions specified in the AIP: Terminal Risk Management Test No: 2CI.028.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the terminal performs Terminal Risk Management if

supported in AIP. Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal (([Velocity Checking] supported OR [Floor Limit Checking] supported) Configuration: OR [Random Transaction Selection] supported) Conditions:

•



•


•

TSI byte 1, bit 4 = '1' (ie Terminal Risk Management was performed) received at 1st GENERATE AC.


Page 874


2CI.031.00 Functions not specified in the AIP: Issuer Authentication Test No: 2CI.031.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal does not perform Issuer Authentication if

not supported in AIP. Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•

AIP of LT returned by LT specifies that Issuer Authentication is not supported (AIP Byte 1 bit 3 = 0).

•


•

Issuer Authentication Data received in the authorization response message.


•


•

The LT shall not receive an EXTERNAL AUTHENTICATE command following the First GENERATE AC.

•

TSI byte 1, bit 5 = '0' (ie Issuer Authentication was not performed) received at 2nd GENERATE AC.



2CI.034.00 Functions not specified in the Application Interchange Profile: Enhanced Combined DDA / GENERATE AC Test No: 2CI.034.00 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal does not perform Enhanced Combined

DDA / GENERATE AC if not supported by the ICC, as specified in the Application Interchange Profile. Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1:


•


•


•


•

LT responds with a TC.


•

The terminal shall not ask the ICC to process a combined DDA in 1st GENERATE AC.

•


•


•


•



Page 876


2CI.034.00 Functions not specified in the Application Interchange Profile: Enhanced Combined DDA / GENERATE AC •




Functions used in Transaction Processing


Page 878


2CJ.002.00 All bits in TSI and TVR are set to 0b Test No: 2CJ.002.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that all TVR and TSI bits are set to 0b when the terminal

starts the transaction. Reference Book 3 - Section 6.1 - Initiate Application Processing EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal NA Configuration: Conditions:

•

A first transaction is performed raising the TVR bits: Byte 2 bit 8 to bit-4 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8 to -7 (Cardholder verification not successful, Unrecognised CVM) and raising the TSI bits: Byte 1 bit 7 to -6 (Cardholder verification was performed, Card risk management was performed.

•

A second transaction is performed where the PDOL requests TSI and TVR.


•

TSI returned by terminal with GET PROCESSING OPTIONS shall be set to 0b in the second transaction.

•

TVR returned by terminal with GET PROCESSING OPTIONS shall be set to 0b in the second transaction.



2CJ.002.01 All bits in TSI and TVR are set to 0b (2) Test No: 2CJ.002.01 - Revision 16 - Number of sub cases: 2 Objective: To ensure that all TVR and TSI bits are set to 0b when the terminal

starts the transaction. Reference EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

•

Case 01: o

A first transaction is performed raising the TVR bits: Byte 1 bit 8-7 (Offline data authentication was not successful, SDA failed), Byte 2 bit 8 to -4 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8- to 7 (Cardholder verification not successful, Unrecognised CVM) and raising the TSI bits: Byte 1 bit 8 to 6 (Offline data authentication was performed, Cardholder verification was performed, Card risk management was performed).

o


Case 02: o

A first transaction is performed raising the TVR bits: Byte 1 bit 8 (Offline Data Authentication not performed)

o



•


•



Page 880





starts the transaction. Reference EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal [Exception List] supported Configuration: Conditions:

•

A first transaction is performed raising the TVR bits: Byte 1 bit 5 (Card appears in exception file), Byte 2 bit 8 to -4 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8 to -7 (Cardholder verification not successful, Unrecognised CVM) and raising the TSI bits: Byte 1 bit 7 to -6 (Cardholder verification was performed, Card risk management was performed).

•



•


•



Page 882



starts the transaction. Reference EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•

A first transaction is performed raising the TVR bits: Byte 1 bit 8,4 (Offline data authentication was not successful, DDA failed), Byte 2 bit 8 to -4 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8 to-7 (Cardholder verification not successful, Unrecognised CVM) and Byte 5 bit 8 (Default TDOL used) and raising the TSI bits: Byte 1bit 8 to -6 (Offline data authentication was performed, Cardholder verification was performed, Card risk management was performed).

•



•


•





starts the transaction. Reference EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•

A first transaction is performed raising the TVR bits: Byte 1 bit 3 (CDA failed), Byte 2 bit 8 to -4 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8 -to 7 (Cardholder verification not successful, Unrecognised CVM) and raising the TSI bits: Byte 1 bit 8- to 6 (Offline data authentication was performed, Cardholder verification was performed, Card risk management was performed).

•



•


•



Page 884



starts the transaction. Reference EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal [Offline Plaintext Configuration: supported Conditions:

PIN] supported OR [Offline Enciphered PIN]

•

A first transaction is performed raising the TVR bits: Byte 2 bit 8- to 4 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8,6,4 (Cardholder verification not successful, PIN Try Limit exceeded, PIN entry required, PIN pad present but PIN was not entered) and raising the TSI bits: Byte 1 bit 7 to -6 (Cardholder verification was performed, Card risk management was performed).

•



•


•





starts the transaction. Reference EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal [Offline Plaintext PIN] not supported OR [Offline Enciphered PIN] not Configuration: supported Conditions:

•

A first transaction is performed raising the TVR bits: Byte 2 bit 8 to-4 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8,5 (Cardholder verification not successful, PIN entry required, PIN pad not present or not working) and raising the TSI bits: Byte 1 bit 7- to 6 (Cardholder verification was performed, Card risk management was performed).

•



•


•



Page 886



starts the transaction. Reference EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal [Online Enciphered PIN] supported Configuration: Conditions:

•

A first transaction is performed raising the TVR bits: Byte 2 bit 8 to- 4 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8,3 (Cardholder verification not successful, Online PIN entered) and Byte 5 bit 6 to-5 (Script processing failed before final GENERATE AC, Script processing failed after final GENERATE AC) and raising the TSI bits: Byte 1 bit 7 to-6,3 (Cardholder verification was performed, Card risk management was performed, script processing was performed.

•



•


•





starts the transaction. Reference EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal [Online Only] OR [Offline/Online capable] supported Configuration: Conditions:

•

A first transaction is performed raising the TVR bits: Byte 2 bit 8 to-4 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8 to-7 (Cardholder verification not successful, Unrecognised CVM) and Byte 5 bit 7- to 5 (Issuer Authentication failed, Script processing failed before final GENERATE AC, Script processing failed after final GENERATE AC) and raising the TSI bits: Byte 1 bit 7 to -5,3 (Cardholder verification was performed, Card risk management was performed, Issuer Authentication was performed, script processing was performed.

•



•


•



Page 888



starts the transaction. Reference EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal [Floor Limit Checking] supported Configuration: Conditions:

•

A first transaction is performed raising the TVR bits: Byte 2 bit 8 to -4 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8 to -7 (Cardholder verification not successful, Unrecognised CVM) Byte 4 bit 8 (transaciton exceeds floor limit) and raising the TSI bits: Byte 1 bit 7 to -6, 4 (Cardholder verification was performed, Card risk management was performed, Terminal risk management was performed).

•



•


•





starts the transaction. Reference EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•

A first transaction is performed raising the TVR bits: Byte 2 bit 8 to-4 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8 to- 7 (Cardholder verification not successful, Unrecognised CVM) Byte 4 bit 7 to- 6 (Upper consecutive offline limit exceeded, Lower consecutive offline limit exceeded) and raising the TSI bits: Byte 1 bit 7 to- 6, 4 (Cardholder verification was performed, Card risk management was performed, Terminal risk management was performed).

•



•


•



Page 890



starts the transaction. Reference EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal [Random Transaction Selection] supported Configuration: Conditions:

•

A first transaction is performed raising the TVR bits: Byte 2 bit 8 to-4 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8 to-7 (Cardholder verification not successful, Unrecognised CVM) Byte 4 bit 5 (transaction selected randomly for online processing) and raising the TSI bits: Byte 1 bit 7 to- 6, 4 (Cardholder verification was performed, Card risk management was performed, Terminal risk management was performed).

•



•


•





starts the transaction. Reference EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal [Attended] supported AND [Forced Online] supported Configuration: Conditions:

•

A first transaction is performed raising the TVR bits: Byte 2 bit 8 to- 4 (ICC have different application version, Expired Application, Application not yet effective, Requested service not allowed for card product), Byte 3 bit 8 to- 7 (Cardholder verification not successful, Unrecognised CVM) Byte 4 bit 4 (Merchant forced transaction online) and raising the TSI bits: Byte 1 bit 7 to -6, 4 (Cardholder verification was performed, Card risk management was performed, Terminal risk management was performed).

•



•


•



Page 892


2CJ.005.00 Rules for Processing Tags listed in the PDOL (1) Test No: 2CJ.005.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that if PDOL is present in the FCI of selected ADF and if it

contains a Data Element which is not defined in Book 1 Annex B and Book 3 Annex A Data Elements or does not have the terminal as source, the terminal sends a GET PROCESSING OPTIONS command with a PDOL containing a Data Element with tag and the length specified and a value of all hexadecimal zeroes. Reference Book 3 - Section 6.1 - Initiate Application Processing EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal NA Configuration: Conditions:

•

PDOL is sent back by the LT in FCI of selected ADF.

•

Case 01: PDOL requests a Data Element which is not defined in either Book 1 Annex B or Book 3 Annex A

•

Case 02: PDOL requests a Data Element which has the ICC as source


•

LT shall receive a GET PROCESSING OPTIONS command with a data field containing a data object with Tag '83'.

•

The Data Element in PDOL related to sub case conditions shall be replaced in template '83' with a Data Element of same length and a value of hexadecimal zeroes.



2CJ.006.00 Rules for Processing Tags listed in the PDOL (2) Test No: 2CJ.006.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if PDOL is present in the FCI of selected ADF and if it

contains a Data Element which is a constructed Data Object, the terminal sends a GET PROCESSING OPTIONS command with a PDOL containing a Data Element with the tag and length specified and a value of all hexadecimal zeroes. Reference Book 3 - Section 6.1 - Initiate Application Processing EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal NA Configuration: Conditions: PDOL is sent back by the LT in FCI of selected ADF and it contains a

Data Element which is a constructed Data Object. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

Constructed Data Object in PDOL shall be replaced in template '83' with a Data Element of same length and a value of hexadecimal zeroes.


Page 894


2CJ.007.00 Rules for Processing Tags listed in the PDOL (3) Test No: 2CJ.007.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that if PDOL is present in the FCI of selected ADF and if it

contains a Data Element which is not present in the terminal, the terminal sends a GET PROCESSING OPTIONS command with a PDOL containing a Data Element with the tag and length specified and a value of all hexadecimal zeroes. Reference Book 3 - Section 6.1 - Initiate Application Processing EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1: Terminal NA Configuration: Conditions: PDOL is sent back by the LT in FCI of selected ADF and it contains a

Data Element which cannot be provided by the terminal at the moment the ARC (tag '8A'). Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

Data Object in PDOL which cannot be provided at the moment shall be replaced in template '83' with a Data Element of same length and a value of hexadecimal zeroes.



2CJ.009.00 READ RECORD command execution Test No: 2CJ.009.00 - Revision 10d - Number of sub cases: 0 Objective: To ensure that the terminal always sends the READ RECORDS

commands immediately after the GET PROCESSING OPTIONS command. Reference Book 3 - Section 6.2 - Read Application Data EMV 4.0: Reference Book 3 - Section 10.2 - Read Application Data EMV 4.1: Terminal NA Configuration: Conditions: NA Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: LT

shall receive a sequence of READ RECORD commands immediately after the GET PROCESSING OPTIONS command.


Page 896


2CJ.010.00 READ RECORD on each entry in the AFL Test No: 2CJ.010.00 - Revision 10g - Number of sub cases: 6 Objective: To ensure that the terminal is able to interpret the AFL and send READ

RECORD commands for each record between the starting record Number and the ending record number, inclusively. Reference Book 3 - Section 3 - Files for Financial Transaction Interchange EMV 4.0:

Book 3 - Section 6.2 - Read Application Data Reference Book 3 - Section 7.1 - Mapping Data Objects EMV 4.1:

Book 3 - Section 10.2 - Read Application Data Terminal NA Configuration: Conditions:

•

Case 01: The AFL of the LT refers to file 1 - records 1 to 5.

•

Case 02: The AFL of the LT refers to file 1 - records 1 to 5, file 2 - records 2 to 3, and file 3 - records 3 to 3.

•


•


•


•


Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The LT shall receive a sequence of READ RECORD commands

according to the AFL.



2CJ.010.01 READ RECORD on each entry in the AFL (2) Test No: 2CJ.010.01 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal is able to interpret the AFL and send READ

RECORD commands for each record between the starting record number and the ending record number, inclusively. Reference Book 3 - Section Annex A - Data Elements Table EMV 4.0: Reference Book 3 - Section A1 - Data Elements by Name EMV 4.1: Terminal NA Configuration: Conditions:

•

Case 01: AFL with a length of 128 bytes.

•

Case 02: GET PROCESSING OPTIONS responses from LT is in format 1 and contains an AFL with 62 entries (length of 248 bytes).

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The LT shall receive a sequence of READ RECORD commands

according to the AFL.


Page 898


2CJ.011.00 Data objects processing Test No: 2CJ.011.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the terminal stores all data elements read during the

Read Application Data phase. Reference Book 3 - Section 6.2 - Read Application Data EMV 4.0: Reference Book 3 - Section 10.2 - Read Application Data EMV 4.1: Terminal NA Configuration: Conditions:

•

CDOL1 requests all data elements read in file referenced in AFL, Except CDOL1 and CDOL2.

•

The following AFL combinations are tested:

•


•


•


Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The LT shall receive in the GENERATE AC data field, correct values

for data elements stored during the Read Application Data phase.



2CJ.012.00 Data objects processing (Unrecognized Data Objects) Test No: 2CJ.012.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal ignores unrecognized Data Objects read

during the Read Application Data phase. Reference Book 3 - Section 6.2 - Read Application Data EMV 4.0: Reference Book 3 - Section 10.2 - Read Application Data EMV 4.1: Terminal NA Configuration: Conditions: Records to be read contain non-EMV Data Objects. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall accept the card and process the transaction until



Page 900


2CJ.012.01 Non recognized data object participating in offline data authentication Test No: 2CJ.012.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal is able to include non recognized data

objects used in offline Static Data Authentication, provided that they are read with the READ RECORD command and are located in records participating in offline Static Data Authentication, according to AFL. Reference Book 3 - Section 6.2 - Read Application Data EMV 4.0: Reference Book 3 - Section 10.2 - Read Application Data EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

A non-EMV Data Object is included in a record listed in the AFL as participating in data authentication.

•


•

Issuer Public Key Certificate and Signed Static Application Data are valid.



•


•


•


•


•





Page 902


2CJ.012.02 Non recognized data objects participating in offline data authentication (2) Test No: 2CJ.012.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal is able to include non recognized data

objects in offline Dynamic Data Authentication, provided that they are read with the READ RECORD command and are located in records participating in offline Dynamic Data Authentication, according to AFL. Reference Book 3 - Section 6.2 - Read Application Data EMV 4.0: Reference Book 3 - Section 10.2 - Read Application Data EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•


•

Issuer Public Key Certificate, ICC Public Key Certificate and Dynamic signature are valid.



•


•


•


•


•





Page 904


2CJ.012.03 Non recognized data objects participating in offline data authentication (3) Test No: 2CJ.012.03 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal is able to include non recognized data

objects in offline Dynamic Data Authentication, provided that they are read with the READ RECORD command and are located in records participating in offline Dynamic Data Authentication, according to AFL. By using Combined DDA/AC Data Authentication. Reference Book 3 - Section 6.2 - Read Application Data EMV 4.0: Reference Book 3 - Section 10.2 - Read Application Data EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•


•




•


•


•


•


•




2CJ.012.03 Non recognized data objects participating in offline data authentication (3) performed) contained in Financial Confirmation message or Batch Data Capture message.


Page 906


2CJ.013.00 Record Data Format: mandatory data: Application Expiration Date Test No: 2CJ.013.00 - Revision 10d - Number of sub cases: 0 Objective: To ensure that the terminal terminates the transaction if the Application

Expiration Date is missing. Reference Book 3 - Section 3.1 - Mandatory Data Objects EMV 4.0:

Book 3 - Section 6.2 - Read Application Data Reference Book 3 - Section 7.2 - Mandatory Data Objects EMV 4.1:

Book 3 - Section 10.2 - Read Application Data Terminal NA Configuration: Conditions: Application Expiration Date is missing in LT. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall terminate the transaction.



2CJ.014.00 Record Data Format: mandatory data: PAN Test No: 2CJ.014.00 - Revision 10d - Number of sub cases: 0 Objective: To ensure that the terminal terminates the transaction if the PAN is

missing. Reference Book 3 - Section 3.1 - Mandatory Data Objects EMV 4.0:


Book 3 - Section 10.2 - Read Application Data Terminal NA Configuration: Conditions: PAN is missing in LT. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall terminate the transaction.


Page 908


2CJ.015.00 Record Data Format: mandatory data: CDOL1 Test No: 2CJ.015.00 - Revision 10d - Number of sub cases: 0 Objective: To ensure that the terminal terminates the transaction if the CDOL1 is



Book 3 - Section 10.2 - Read Application Data Terminal NA Configuration: Conditions: CDOL1 is missing in LT. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall terminate the transaction.



2CJ.016.00 Record Data Format: mandatory data: CDOL2 Test No: 2CJ.016.00 - Revision 10d - Number of sub cases: 0 Objective: To ensure that the terminal terminates the transaction if the CDOL2 is



Book 3 - Section 10.2 - Read Application Data Terminal NA Configuration: Conditions: CDOL2 is missing in LT. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall terminate the transaction.


Page 910


2CJ.017.00 Record Data Format: Unique data objects Test No: 2CJ.017.00 - Revision 10 - Number of sub cases: 5 Objective: To ensure that the terminal terminates the transaction if a Data Object

is duplicated. Reference Book 3 - Section 6.2 - Read Application Data EMV 4.0: Reference Book 3 - Section 10.2 - Read Application Data EMV 4.1: Terminal NA Configuration: Conditions:

•

Case 01: PAN is duplicated in LT

•

Case 02: Expiration Date is duplicated in LT

•

Case 03: AUC is duplicated in LT

•

Case 04: Issuer Public Key Exponent is duplicated in LT

•

Case 05: CDOL1 is duplicated in LT

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall terminate the transaction.



2CJ.018.00 Record Data Format: Proprietary data participating in offline data authentication Test No: 2CJ.018.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal is able to read and include in Offline Static

Data authentication, data objects located in proprietary files, provided that proprietary files are TLV-coded. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:

Book Bulletins - Section SU 12-01 - Bulletin n°12, Offline Data Authentication Processing (Oct-2002) Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

An EMV Data Object is included in a record, located in a proprietary file, listed in AFL, and included in the data to be signed.

•


•

EMV Data Object located in proprietary files will be TLV coded with record tag ‘70’.

•

Signed Static Application Data is valid, including in the computation the tag '70' and associated length of the record contained in the proprietary files.



•


•


•


•



Page 912


2CJ.018.00 Record Data Format: Proprietary data participating in offline data authentication used) received at 1st GENERATE AC. •




2CJ.018.01 Record Data Format: Proprietary data participating in offline data authentication (2) Test No: 2CJ.018.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal is able to read and include in Offline

Dynamic Data Authentication, data objects located in proprietary files, provided that proprietary files are TLV-coded. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:

Book Bulletins - Section SU 12-01 - Bulletin n°12, Offline Data Authentication Processing (Oct-2002) Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•


•


•

ICC Public Key Certificate is valid including in the computation the tag '70' and associated length of the record contained in the proprietary files.



•


•


•


•



Page 914


2CJ.018.01 Record Data Format: Proprietary data participating in offline data authentication (2) received at 1st GENERATE AC. •




2CJ.018.02 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (2) Test No: 2CJ.018.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal fails Dynamic Data Authentication when

data objects located in proprietary files are not TLV coded with record tag ‘70’. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:


•

An EMV Data Object is included in a record, located in a proprietary (SFI 11 to 30) file, listed in AFL, and included in the data to be signed.

•

EMV Data Object located in proprietary files is not TLV coded with record tag ‘70’.

•


•

ICC Public Key Certificate is valid.

•

Signed Static Application Data is good.


•


•

TVR byte 1, bit 4 = ‘1’ (ie Offline Dynamic Data Authentication failed) received at 1st GENERATE AC.

•


•



Page 916


2CJ.018.02 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (2) •

TSI byte 1, bit 8 = ‘1’ (ie Offline Data Authentication was performed) received at 1st GENERATE AC.



2CJ.018.03 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (3) Test No: 2CJ.018.03 - Revision 13 - Number of sub cases: 0 Objective: To

ensure that the terminal fails Combined DDA/AC Data Authentication when data objects located in proprietary files are not TLV coded with record tag ‘70’.

Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:

Book Bulletins - Section SU 12-01 - Bulletin n°12, Offline Data Authentication Processing (Oct-2002) Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1:


•

An EMV Data Object is included in a record, located in a proprietary file (SFI 11 to 30), listed in AFL, and included in the data to be signed.

•


•


•


•

Signed Static Application Data is good


•


•


•

TVR byte 1, bit 3 = ‘1’ (e Offline Combined DDA/AC Data Authentication failed) received at 1st GENERATE AC.

•



Page 918




•




2CJ.018.04 Record Data Format: Proprietary data participating in offline data authentication (3) Test No: 2CJ.018.04 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal is able to read and include in Offline

combined DDA/AC data authentication, data objects located in proprietary files, provided that proprietary files are TLV-coded. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:

Book Bulletins - Section SU 12-01 - Bulletin n°12, Offline Data Authentication Processing (Oct-2002) Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•


•


•

ICC Public Key Certificate is valid including in the computation the tag '70' and associated length of the record contained in the proprietary files.


•


•


•


•



Page 920


2CJ.018.04 Record Data Format: Proprietary data participating in offline data authentication (3) •






Reference EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1:


•


•


•


•


•


•



•


•

TVR byte 1, bit 3 = ‘1’ (e Offline Combined DDA/AC Data Authentication failed) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or


Page 922


2CJ.018.05 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (4) if the terminal has the capability to show the TVR value in any form such as receipt for example. •


•


•




2CJ.018.06 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (5) Test No: 2CJ.018.06 - Revision 13a - Number of sub cases: 0 Objective: To





•


•


•


•


•


•


•



•


•

TVR byte 1, bit 3 = ‘1’ (e Offline Combined DDA/AC Data Authentication failed) received at 2nd.


Page 924




•


•




2CJ.018.07 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (6) Test No: 2CJ.018.07 - Revision 13a - Number of sub cases: 0 Objective: To





•


•


•


•


•


•


•


•



•


•

TVR byte 1, bit 3 = ‘1’ (e Offline Combined DDA/AC Data Authentication failed) contained in Financial Confirmation


Page 926


2CJ.018.07 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (6) message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example. •


•


•









•


•


•


•


•


•


•


•



•


•

TVR byte 1, bit 3 = ‘1’ (e Offline Combined DDA/AC Data


Page 928


2CJ.018.08 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication (7) 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 or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example. •


•


•




2CJ.019.00 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication Test No: 2CJ.019.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal fails Static Data Authentication when data

objects located in proprietary files are not TLV coded with record tag ‘70’. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:


•


•


•


•

Signed Static Application Data is valid.



•


•

TVR byte 1, bit 7 = ‘1’ (ie Offline Static Data Authentication failed) received at 1st GENERATE AC.

•


•



Page 930


2CJ.019.00 Record Data Format: Non-TLV coded proprietary data participating in offline data authentication •




2CJ.020.00 Offline Static Data Authentication is supported Test No: 2CJ.020.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if both the card and the terminal support Offline Static

Data Authentication, the terminal performs Offline Static Data Authentication at any time after the Read Application Data phase but before completion of the terminal analysis. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

Signed Static Application Data is not valid.

•

IAC denial byte 1 bit 7 = '1', Offline Static Data Authentication failed.


•

The terminal issues a first GENERATE AC requesting AAC.

•


•


•



Page 932


2CJ.021.00 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC, 1st Generate AC) Test No: 2CJ.021.00 - Revision 13 - Number of sub cases: 0 Objective: To ensure that if both the card and the terminal support Enhanced

Combined DDA/AC, the terminal performs Enhanced Combined DDA/AC. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation

(Dec-2001) Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1:


•


•

TAC and IAC are set so that a TC is requested at first GENERATE AC

•

LT answers TC at 1st GENERATE AC.

•

Enhanced Combined DDA/AC Generation signature generated by LT is valid.



•


•


•


•




2CJ.021.00 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC, 1st Generate AC) •


•



Page 934


2CJ.021.01 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC, 2nd Generate AC) Test No: 2CJ.021.01 - Revision 13 - Number of sub cases: 0 Objective: To ensure that if both the card and the terminal support Enhanced




•


•


•

LT answers ARQC at 1st GENERATE AC and TC at 2nd GENERATE AC.

•


•




•


•


•




2CJ.021.01 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC, 2nd Generate AC) •


•


•



Page 936


2CJ.021.02 Both the Terminal and the Card support Enhanced Combined DDA/AC (ARQC) Test No: 2CJ.021.02 - Revision 13 - Number of sub cases: 0 Objective: To ensure that if both the card and the terminal support Enhanced




•


•


•

LT answers ARQC at 1st GENERATE AC.

•




•


•


•


•




2CJ.021.02 Both the Terminal and the Card support Enhanced Combined DDA/AC (ARQC) •


•



Page 938


2CJ.021.03 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC, 2nd Generate AC) (2) Test No: 2CJ.021.03 - Revision 13 - Number of sub cases: 0 Objective: To ensure that if both the card and the terminal support Enhanced

Combined DDA/AC, the terminal performs Enhanced Combined DDA/AC. Reference EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1:



•


•


•


•




•


•


•


•




2CJ.021.03 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC, 2nd Generate AC) (2) •


•



Page 940


2CJ.021.04 Both the Terminal and the Card support Enhanced Combined DDA/AC (ARQC) (2) Test No: 2CJ.021.04 - Revision 13 - Number of sub cases: 0 Objective: To ensure that if both the card and the terminal support Enhanced



•


•


•

LT answers ARQC at 1st GENERATE AC.

•




•


•


•


•




2CJ.021.04 Both the Terminal and the Card support Enhanced Combined DDA/AC (ARQC) (2) •


•



Page 942


2CJ.021.05 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC, 2nd Generate AC) (2) Test No: 2CJ.021.05 - Revision 13 - Number of sub cases: 0 Objective: To ensure that if both the card and the terminal support Enhanced


Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND ([Online Only] AND [Normal Default Action Code Configuration: processing]) supported Conditions:

•


•


•


•


•




•


•


•


•




2CJ.021.05 Both the Terminal and the Card support Enhanced Combined DDA/AC (TC, 2nd Generate AC) (2) received at 1st GENERATE AC. •


•



Page 944


2CJ.022.00 Both the Terminal and the Card support Offline SDA Test No: 2CJ.022.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if both the card and the terminal support Offline Static

Data Authentication, and either terminal or card does not support Offline Dynamic Data Authentication, or either the card or terminal (or both) does not support Enhanced Combined DDA/AC Generation, the terminal performs Offline Static Data Authentication. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal (([SDA] supported AND [DDA] not supported) AND [CDA] not Configuration: supported) Conditions:

•


•


•


•

Static signature in LT is not valid.



•


•


•


•


•




2CJ.022.00 Both the Terminal and the Card support Offline SDA performed) received at 1st GENERATE AC.


Page 946


2CJ.022.01 Both the Terminal and the Card support Offline SDA (2) Test No: 2CJ.022.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if both the card and the terminal support Offline Static

Data Authentication, and either terminal or card does not support Offline Dynamic Data Authentication, or either the card or terminal (or both) does not support Enhanced Combined DDA/AC Generation, the terminal performs Offline Static Data Authentication. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal (([SDA] supported AND [DDA] supported) AND [CDA] not supported) Configuration: Conditions:

•


•


•


•




•


•


•


•


•




2CJ.022.01 Both the Terminal and the Card support Offline SDA (2) performed) received at 1st GENERATE AC.


Page 948


2CJ.022.02 Both the Terminal and the Card support Offline SDA (3) Test No: 2CJ.022.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if both the card and the terminal support Offline Static

Data Authentication, and either terminal or card does not support Offline Dynamic Data Authentication, or either the card or terminal (or both) does not support Enhanced Combined DDA/AC Generation, the terminal performs Offline Static Data Authentication. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal (([SDA] supported AND [DDA] supported) AND [CDA] supported) Configuration: Conditions:

•


•


•


•




•


•


•


•


•




2CJ.022.02 Both the Terminal and the Card support Offline SDA (3) performed) received at 1st GENERATE AC.


Page 950


2CJ.023.00 Both the Offline DDA and the Offline SDA are supported Test No: 2CJ.023.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if both the card and the terminal support Offline Static

Data Authentication and Offline Dynamic Data Authentication, and either the card or terminal (or both) does not support Enhanced Combined DDA/AC Generation, the terminal performs only Offline Dynamic Data Authentication. Reference NA EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal (([SDA] supported AND [DDA] supported) AND [CDA] not supported) Configuration: Conditions:

•


•


•


•

Dynamic signature generated by LT is not valid.



•


•


•


•


•




2CJ.023.00 Both the Offline DDA and the Offline SDA are supported performed) received at 1st GENERATE AC.


Page 952


2CJ.023.01 Both the Offline DDA and the Offline SDA are supported (2) Test No: 2CJ.023.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if both the card and the terminal support Offline Static

Data Authentication and Offline Dynamic Data Authentication, and either the card or terminal (or both) does not support Enhanced Combined DDA/AC Generation, the terminal performs only Offline Dynamic Data Authentication. Reference NA EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal (([SDA] supported AND [DDA] supported) AND [CDA] supported) Configuration: Conditions:

•


•


•


•

Dynamic signature generated by LT is not valid.



•


•


•


•


•




2CJ.023.01 Both the Offline DDA and the Offline SDA are supported (2) performed) received at 1st GENERATE AC.


Page 954


2CJ.024.00 Neither the Offline DDA nor the Offline SDA nor the Enhanced Combined DDA/AC is performed Test No: 2CJ.024.00 - Revision 10g - Number of sub cases: 2 Objective: To ensure that if neither Offline Static Data Authentication, nor Offline

Dynamic Data Authentication nor the Enhanced Combined DDA/AC Generation is performed, the terminal sets the 'Offline data authentication was not performed' bit in the TVR to 1b. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:

Book Bulletins - Section SU 12-01 - Bulletin n°12, Offline Data Authentication Processing (Oct-2002) Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal (([SDA] not supported AND [DDA] not supported) AND [CDA] not Configuration: supported) Conditions:

•

Case 01: LT does not support SDA, DDA or Combined DDA/AC.

•

Case 02: LT supports (SDA, DDA and Combined DDA/AC).


•


•

TVR byte 1, bit 8 = '1' (ie Offline Data Authentication not performed) TVR is received at 1st GENERATE AC.

•


•


•


•

TSI byte 1, bit 8='0' (ie Offline data authentication was not performed) received at 1st GENERATE AC.



2CJ.024.01 Neither the Offline DDA nor the Offline SDA nor the Enhanced Combined DDA/AC is performed (2) Test No: 2CJ.024.01 - Revision 10g - Number of sub cases: 2 Objective: To ensure that if neither Offline Static Data Authentication, nor Offline


Book Bulletins - Section SU 12-01 - Bulletin n°12, Offline Data Authentication Processing (Oct-2002) Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal (([SDA] supported AND [DDA] not supported) AND [CDA] not Configuration: supported) Conditions:

•

Case 01: LT does not support SDA, DDA or Combined DDA/AC

•

Case 02: LT does not support SDA supports DDA and Combined DDA/AC.


•


•

TVR byte 1, bit 8 = '1' (ie Offline Data Authentication not performed) received at 1st GENERATE AC.

•


•


•


•

TSI byte 1, bit 8='0' (ie Offline data authentication was not performed) received at 1st GENERATE AC.


Page 956


2CJ.024.03 Neither the Offline DDA nor the Offline SDA nor the Enhanced Combined DDA/AC is performed (3) Test No: 2CJ.024.03 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if neither Offline Static Data Authentication, nor Offline


Book Bulletins - Section SU 12-01 - Bulletin n°12, Offline Data Authentication Processing (Oct-2002) Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal (([SDA] supported AND [DDA] supported) AND [CDA] supported) Configuration: Conditions:

•

LT does not support Static Data Authentication.

•

LT does not support Dynamic Data Authentication.

•

LT does not support Enhanced Combined DDA/AC.


•


•

TVR byte 1, bit 8 = '1' (ie Offline Data Authentication not performed) TVR is received at 1st GENERATE AC.

•


•


•


•

TSI byte 1, bit 8='0' (ie Offline data authentication was not



2CJ.024.03 Neither the Offline DDA nor the Offline SDA nor the Enhanced Combined DDA/AC is performed (3) performed) received at 1st GENERATE AC.


Page 958


2CJ.025.00 Rules for Processing the Input Data Test No: 2CJ.025.00 - Revision 11 - Number of sub cases: 6 Objective: To ensure that if Offline Static Data Authentication is performed, the

terminal concatenates the data retrieved from the records identified by the AFL with the data from the Static Data Authentication Tag List, and uses the concatenation as input to the string to be signed. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:


•


•

AFL indicates data to be included in Static Signature.

•

LT contains a Static Data Authentication Tag List.

•

Case 01: One record of LT indicated in AFL for Static Signature is right padded with '00' (after the last data object but in the record template).

•

Case 02: One record of LT indicated in AFL for Static Signature is left padded with 'FF' (before the first data object but in the record template).

•

Case 03: One record of LT indicated in AFL for Static Signature is not padded.

•

Case 04: One record of LT indicated in AFL for Static Signature is right padded with 50 bytes of value '00' (after the last data object but in the record template).

•

Case 05: One record of LT indicated in AFL for Static Signature is left padded with 50 bytes of value 'FF' (before the first data object but in the record template).

•

Case 06: 25 records of LT indicated in AFL are used as input



2CJ.025.00 Rules for Processing the Input Data for Static Signature Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•


•


•



Page 960


2CJ.025.01 Rules for Processing the Input Data (2) Test No: 2CJ.025.01 - Revision 11 - Number of sub cases: 6 Objective: To ensure that if Offline Dynamic Data Authentication is performed, the

terminal concatenates the data retrieved from the records identified by the AFL with the data from the Static Data Authentication Tag List, and uses the concatenation as input to the string to be signed. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:


•


•


•


•


•


•


•


•

Case 06: 25 records of LT indicated in AFL are used as input for Static Signature



2CJ.025.01 Rules for Processing the Input Data (2) Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•


•


•



Page 962


2CJ.025.02 Rules for Processing the Input Data (3) Test No: 2CJ.025.02 - Revision 11 - Number of sub cases: 6 Objective: To ensure that if Offline Enhanced DDA/AC Data Authentication is

performed, the terminal concatenates the data retrieved from the records identified by the AFL with the data from the Static Data Authentication Tag List, and uses the concatenation as input to the string to be signed. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:


•


•


•


•


•


•


•


•

Case 06: 25 records of LT indicated in AFL are used as input for Static Signature



2CJ.025.02 Rules for Processing the Input Data (3) Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•

TVR byte 1, bit 3 = '0' (ie Combined Data Authentication succeeded) received at 1st GENERATE AC.

•


•

TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) - TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) set.


Page 964


2CJ.026.00 Rules for Processing the records identified by the AFL, when the Offline DDA is performed (1) Test No: 2CJ.026.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that when terminal performs Dynamic Data Authentication

and builds the string to be signed, the terminal does not include tag 70 and length for records referenced in AFL as participating in Dynamic Data Authentication but located in files with SFI in range 1 to 10. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:


•


•

Records participating in Dynamic Data Authentication are located in:

- File with SFI 1, record 1. - File with SFI 3, records 2 and 3. - File with SFI 10, record 5. •

Dynamic signature generated by the LT is valid.



•


•


•




2CJ.026.00 Rules for Processing the records identified by the AFL, when the Offline DDA is performed (1) used) received at 1st GENERATE AC. •


•



Page 966


2CJ.026.01 Rules for Processing the records identified by the AFL, when the Offline Combined DDA/AC is performed Test No: 2CJ.026.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that when terminal performs Combined DDA/AC Data

Authentication and builds the string to be signed, the terminal does not include tag 70 and length for records referenced in AFL as participating in Combined DDA/AC Data Authentication but located in files with SFI in range 1 to 10. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:


•


•





•


•


•




2CJ.026.01 Rules for Processing the records identified by the AFL, when the Offline Combined DDA/AC is performed received at 1st GENERATE AC. •


•



Page 968


2CJ.027.00 Rules for Processing the records identified by the AFL, when the Offline DDA is performed (2) Test No: 2CJ.027.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that when terminal performs Dynamic Data Authentication

and builds the string to be signed, the terminal includes all data of records referenced in AFL as participating in Dynamic Data Authentication and located in files with SFI in range 11 to 30. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:


•


•



Records from SFI 11-30 are BER-TLV encoded.

•




•


•




2CJ.027.00 Rules for Processing the records identified by the AFL, when the Offline DDA is performed (2) •


•


•



Page 970


2CJ.027.01 Rules for Processing the records identified by the AFL, when the Offline Combined DDA/AC is performed (2) Test No: 2CJ.027.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that when terminal performs Combined DDA/AC Data

Authentication and builds the string to be signed, the terminal includes all data of records referenced in AFL as participating in Combined DDA/AC Data Authentication and located in files with SFI in range 11 to 30. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:


•


•




•



•


•




2CJ.027.01 Rules for Processing the records identified by the AFL, when the Offline Combined DDA/AC is performed (2) •


•


•



Page 972


2CJ.028.00 Rules for Processing the records identified by the AFL, when the Offline SDA is performed (1) Test No: 2CJ.028.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that when terminal performs Static Data Authentication and

builds the string to be signed, the terminal does not include tag 70 and length for records referenced in AFL as participating in Static Data Authentication but located in files with SFI in range 1 to 10. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

Records participating in Static Data Authentication are located in:

- File with SFI 1, record 1 - File with SFI 3, records 2 and 3. - File with SFI 10, record 5. •

Static signature in the LT is valid.



•


•


•


•




2CJ.028.00 Rules for Processing the records identified by the AFL, when the Offline SDA is performed (1) used) received at 1st GENERATE AC. •



Page 974


2CJ.029.00 Rules for Processing the records identified by the AFL, when the Offline SDA is performed (2) Test No: 2CJ.029.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that when terminal performs Static Data Authentication and

builds the string to be signed, the terminal includes all data of records referenced in AFL as participating in Static Data Authentication and located in files with SFI in range 11 to 30. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

Records participating in Static Data Authentication are located in:



•

Static signature in the LT is valid.



•


•


•




2CJ.029.00 Rules for Processing the records identified by the AFL, when the Offline SDA is performed (2) used) received at 1st GENERATE AC. •


•



Page 976


2CJ.030.00 Processing AIP during Offline Static Data Authentication Test No: 2CJ.030.00 - Revision 10g - Number of sub cases: 0 Objective: To

ensure that when terminal performs Offline Static Data Authentication the terminal checks the AIP and processes the Data Authentication accordingly. To ensure that the terminal verifies signature as described in Book 2 Annex A 2.1 when Static Data Authentication is performed. To ensure that the terminal sets the 'Offline data authentication was performed' bit in the TSI to 1b upon completion of the Offline Data Authentication process.

Reference Book 2 - Section A2.1 - Digital Signature Scheme Giving Message EMV 4.0: Recovery

Book 3 - Section 4 - Transaction Flow Book 3 - Section 6.3 - Offline Data Authentication Reference Book 2 - Section A2.1 - Digital Signature Scheme Giving Message EMV 4.1: Recovery

Book 3 - Section 8 - Transaction Flow Book 3 - Section 10.3 - Offline Data Authentication Terminal [SDA] supported Configuration: Conditions:

•


•

Issuer Public Key Certificate and Static signature in LT are valid.



•


•




2CJ.030.00 Processing AIP during Offline Static Data Authentication succeeded) received at 1st GENERATE AC. •


•


•



Page 978


2CJ.030.01 Processing AIP during Offline Data Authentication (2) Test No: 2CJ.030.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that when terminal performs Offline Dynamic Data

Authentication the terminal checks the AIP and processes the Data Authentication accordingly. To ensure that the terminal verifies signature as described in Book 2 Annex A 2.1 during Dynamic Data Authentication process. To ensure that if all the steps described in Book 2 - Section 6.5 are OK, the terminal succeeds the Dynamic Data Authentication process. To ensure that the terminal sets the 'Offline data authentication was performed' bit in the TSI to 1b upon completion of the Offline Dynamic Data Authentication process. Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification EMV 4.0:

Book 2 - Section A2.1 - Digital Signature Scheme Giving Message Recovery Book 3 - Section 4 - Transaction Flow Book 3 - Section 6.3 - Offline Data Authentication Reference Book 2 - Section 6.5.2 - Dynamic Signature Verification EMV 4.1:

Book 2 - Section A2.1 - Digital Signature Scheme Giving Message Recovery Book 3 - Section 8 - Transaction Flow Book 3 - Section 10.3 - Offline Data Authentication Terminal [DDA] supported Configuration: Conditions:

•


•

Issuer Public Key Certificate and ICC Public Key Certificate are valid.

•




2CJ.030.01 Processing AIP during Offline Data Authentication (2) Action: NA Procedure: Application in LT is selected and transaction is processed with LT (in


•


•


•


•


•



Page 980


2CJ.030.02 Processing AIP during Offline Data Authentication: Enhanced Combined DDA / GENERATE AC Test No: 2CJ.030.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that when terminal performs Offline Combined DDA/AC Data

Authentication the terminal checks the AIP and processes the Data Authentication accordingly. To ensure that the terminal verifies signature as described in Book 2 Annex A 2.1 when performing Combined DDA/AC Data Authentication. To ensure that the terminal sets the 'Offline data authentication was performed' bit in the TSI to 1b upon completion of the Offline Data Authentication process. Reference Book 2 - Section A2.1 - Digital Signature Scheme Giving Message EMV 4.0: Recovery

Book 3 - Section 4 - Transaction Flow Book 3 - Section 6.3 - Offline Data Authentication Reference Book 2 - Section A2.1 - Digital Signature Scheme Giving Message EMV 4.1: Recovery

Book 3 - Section 8 - Transaction Flow Book 3 - Section 10.3 - Offline Data Authentication Terminal [CDA] supported Configuration: Conditions:

•


•

Issuer Public Key Certificate and ICC Public Key Certificate are valid.

•

Dynamic signature generated by LT is valid.


particular Combined DDA/AC Data Authentication). Pass Criteria:

•




2CJ.030.02 Processing AIP during Offline Data Authentication: Enhanced Combined DDA / GENERATE AC •

TVR byte 1, bit 3 = '0' (ie Combined DDA/AC generation succeeded) contained in Financial Confirmation message or Batch Data Capture message.

•


•


•



Page 982


2CJ.032.00 Offline Static Data Authentication fails Test No: 2CJ.032.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal set the 'Offline Static Data Authentication

failed' bit in the TVR to 1b, if Static Data Authentication is performed but is unsuccessful. To ensure that the terminal sets the 'Offline data authentication was performed' bit in the TSI to 1b upon completion of the Offline Static Data Authentication process. Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

Signed Static Application Data in LT is not valid.

•




•


•


•


•


•




2CJ.033.00 Offline Dynamic Data Authentication fails Test No: 2CJ.033.00 - Revision 10g - Number of sub cases: 0 Objective: To

ensure that the terminal set the 'Offline Dynamic Data Authentication failed' bit in the TVR to 1b if Dynamic Data Authentication is performed but is unsuccessful. To ensure that the terminal sets the 'Offline data authentication was performed' bit in the TSI to 1b upon completion of the Offline Dynamic Data Authentication process.

Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•

Data signature returned by the LT is not valid.

•




•


•


•


•


•



Page 984


2CJ.035.00 Processing Restrictions function execution Test No: 2CJ.035.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal performs processing restrictions functions

at some time after Read Application Data and before completion of the terminal action analysis process. Reference Book 3 - Section 6.4 - Processing Restrictions EMV 4.0: Reference Book 3 - Section 10.4 - Processing Restrictions EMV 4.1: Terminal NA Configuration: Conditions:

•

Application Version Number is different in LT and Terminal.

•

Issuer Country Code matches Terminal Country Code.

•

Transaction is not valid for domestic in AUC.

•

Application Expiration Date in the LT has passed.


•


•

TVR byte 2, bit 8 = '1' (ie ICC and Terminal have different application versions) received at 1st GENERATE AC.

•

TVR byte 2, bit 5 = '1' (ie Requested service not allowed for card product) received at 1st GENERATE AC.

•

TVR byte 2, bit 7 = '1' (ie Expired application) received at 1st GENERATE AC.



2CJ.036.00 Application Version Number assigned by the payment system Test No: 2CJ.036.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that the terminal maintains an Application Version Number

assigned by the payment system. Reference Book 3 - Section 6.4.1 - Application Version Number EMV 4.0: Reference Book 3 - Section 10.4.1 - Application Version Number EMV 4.1: Terminal NA Configuration: Conditions:

•

CDOL1 requests Application Version Number (9F 09).

•

Test is made for all applications supported by the terminal.


•


•

LT shall received the value of application version number for the selected application.


Page 986


2CJ.037.00 Application Version Number is not present in the ICC Test No: 2CJ.037.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal continues processing the transaction until

the end if Application Version Number is not present in the ICC. Reference Book 3 - Section 6.4.1 - Application Version Number EMV 4.0: Reference Book 3 - Section 10.4.1 - Application Version Number EMV 4.1: Terminal NA Configuration: Conditions:

•

Application Version Number is not present in the LT.


•


•

The terminal shall presume applications are compatible between ICC and terminal.

•

TVR byte 2, bit 8 = '0' (ie ICC and terminal does not have different application versions) received at 1st GENERATE AC.



2CJ.039.00 Application Version Number present in the ICC and in the terminal are the same (implied) Test No: 2CJ.039.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal does not set the ' ICC and terminal have

different application versions' bit in the TVR to 1b if the Application Version Number present in the ICC and in the terminal are the same. Reference Book 3 - Section 6.4.1 - Application Version Number EMV 4.0: Reference Book 3 - Section 10.4.1 - Application Version Number EMV 4.1: Terminal NA Configuration: Conditions:

•

LT and terminal have the same Application Version Number.


•


•

TVR byte 2, bit 8 = '0' (ie ICC and terminal have the same application versions) received at 1st GENERATE AC.


Page 988


2CJ.041.00 AUC is present in the ICC and Transaction is conducted at an ATM Test No: 2CJ.041.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the terminal is an ATM the AUC is present in the card,

and the 'Valid at ATMs' bit is not set to 1b in the AUC, the terminal sets the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal [ATM] supported Configuration: Conditions:

•

AUC is present in LT.

•

'Valid at ATMs' bit is not set to 1b in the AUC.


•


•




2CJ.042.00 AUC is present in the ICC and Transaction is conducted at an ATM (implied) Test No: 2CJ.042.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the terminal is an ATM the AUC is present in the card,

and the 'Valid at ATMs' bit is set to 1b in the AUC, the terminal does not set the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal [ATM] supported Configuration: Conditions:

•


•

'Valid at ATMs' bit in the AUC is set to 1b.


•


•

TVR byte 2, bit 5 = '0' (ie Requested service allowed for card product) received at 1st GENERATE AC.


Page 990


2CJ.043.00 AUC is present in the ICC and Transaction is not conducted at an ATM Test No: 2CJ.043.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the terminal is not an ATM the AUC is present in the

card, and the 'Valid at terminals other than ATMs ' bit is not set to 1b in the AUC, the terminal sets the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal [ATM] not supported Configuration: Conditions:

•


•

'Valid at terminals other than ATMs' bit is not set to 1b in the AUC.


•


•




2CJ.044.00 AUC is present in the ICC and Transaction is not conducted at an ATM (implied) Test No: 2CJ.044.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the terminal is other than ATM the AUC is present in

the card, and the 'Valid at terminals other than ATMs ' bit is set to 1b in the AUC, the terminal does not set the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal [ATM] not supported Configuration: Conditions:

•


•

'Valid at terminals other than ATMs' bit is set to 1b in the AUC.


•


•



Page 992


2CJ.045.00 Transaction type is a Cash transaction, and Issuer Country Code = Terminal Country Code Test No: 2CJ.045.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code matches Issuer Country

Code, Transaction Type indicates a cash transaction, the AUC is present in the card, and the 'Valid for domestic cash transactions' bit is not set to 1b in the AUC, the terminal sets the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal [Cash] supported Configuration: Conditions:

•

Transaction is a cash transaction.

•


•


'Valid for domestic cash transactions' bit is not set to 1b in the AUC. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•

Transaction Type shall indicate a cash transaction.



2CJ.046.00 Transaction type is a Cash transaction, and Issuer Country Code = Terminal Country Code (implied) Test No: 2CJ.046.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code matches Issuer Country

Code, Transaction Type indicates a cash transaction, the AUC is present in the card, and the 'Valid for domestic cash transactions' bit is set to 1b in the AUC, the terminal does not set the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal [Cash] supported Configuration: Conditions:

•


•


•


•

'Valid for domestic cash transactions' bit is set to 1b in the AUC.


•


•


•



Page 994


2CJ.047.00 Transaction type is a Cash transaction, and Issuer Country Code differs from Terminal Country Code Test No: 2CJ.047.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code does not match Issuer

Country Code, Transaction Type indicates a cash transaction, the AUC is present in the card, and the 'Valid for international cash transactions' bit is not set to 1b in the AUC, the terminal sets the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal [Cash] supported Configuration: Conditions:

•


•


•

Issuer Country Code does not match Terminal Country Code.

•

'Valid for international cash transactions' bit is not set to 1b in the AUC.


•


•


•




2CJ.048.00 Transaction type is a Cash transaction, and Issuer Country Code differs from Terminal Country Code (implied) Test No: 2CJ.048.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code does not match Issuer

Country Code, Transaction Type indicates a cash transaction, the AUC is present in the card, and the 'Valid for international cash transactions' bit is set to 1b in the AUC, the terminal does not set the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal [Cash] supported Configuration: Conditions:

•


•


•


•

'Valid for international cash transactions' bit is set to 1b in the AUC.


•


•


•



Page 996


2CJ.049.00 Transaction type is a Purchase of goods and services, and Issuer Country Code = Terminal Country Code Test No: 2CJ.049.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code matches Issuer Country

Code, Transaction Type indicates a purchase of goods and services, the AUC is present in the card, and the 'Valid for domestic goods' bit is not set to 1b in the AUC, the terminal sets the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0:

Book Bulletins - Section AN 27 - Bulletin n°27, Terminal Behaviour for Goods & Services Checks during the Processing Restriction Function (July 2005) Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1:

Book Bulletins - Section AN 27 - Bulletin n°27, Terminal Behaviour for Goods & Services Checks during the Processing Restriction Function (July 2005) Terminal [Goods] supported OR [Services] supported Configuration: Conditions:

•

Transaction is a purchase of goods and services.

•


•


•

'Valid for domestic goods' bit is not set to 1b in the AUC.

•

‘Valid for domestic services’ bit is not set to 1b in the AUC


•


•


•

Transaction Type shall indicate a purchase of goods and



2CJ.049.00 Transaction type is a Purchase of goods and services, and Issuer Country Code = Terminal Country Code services.


Page 998


2CJ.050.00 Transaction type is a Purchase of goods and Services, and Issuer Country Code = Terminal Country Code (implied) Test No: 2CJ.050.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code matches Issuer Country

Code, Transaction Type indicates a purchase of goods and services, the AUC is present in the card, and the 'Valid for domestic goods' bit is set to 1b in the AUC, the terminal does not set the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0:



•

Transaction is a purchase of goods or services (Transaction type is ‘00’).

•


•


•

'Valid for domestic goods' bit is set to 1b in the AUC.

•

‘Valid for domestic services’ bit is not set to 1b in the AUC.


•


•




2CJ.050.00 Transaction type is a Purchase of goods and Services, and Issuer Country Code = Terminal Country Code (implied) •

Transaction Type shall indicate a purchase of goods and services.


Page 1000


2CJ.051.00 Transaction type is a Purchase of goods and Services, and Issuer Country Code differs from Terminal Country Code Test No: 2CJ.051.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code does not match Issuer

Country Code, Transaction Type indicates a purchase of goods and services, the AUC is present in the card, and the 'Valid for international goods' bit is not set to 1b in the AUC, the terminal sets the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0:



•


•


•


•

'Valid for international goods' bit is not set to 1b in the AUC.

•

‘Valid for international services’ bit is not set to 1b in the AUC


•


•




2CJ.051.00 Transaction type is a Purchase of goods and Services, and Issuer Country Code differs from Terminal Country Code •



Page 1002


2CJ.052.00 Transaction type is a Purchase of goods and services, and Issuer Country Code differs from Terminal Country Code (implied) Test No: 2CJ.052.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code does not match Issuer

Country Code, Transaction Type indicates a purchase of goods and services, the AUC is present in the card, and the 'Valid for international goods' bit is set to 1b in the AUC, the terminal does not set the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0:



•


•


•


•

'Valid for international goods' bit is set to 1b in the AUC.

•

‘Valid for international services’ bit is not set to 1b in the AUC


•


•




2CJ.052.00 Transaction type is a Purchase of goods and services, and Issuer Country Code differs from Terminal Country Code (implied) •



Page 1004


2CJ.053.00 Transaction type is a Purchase of good and services, and Issuer Country Code = Terminal Country Code Test No: 2CJ.053.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code matches Issuer Country

Code, Transaction Type indicates a purchase of goods and services, the AUC is present in the card, and the 'Valid for domestic services' bit is not set to 1b in the AUC, the terminal sets the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0:



•


•


•


•

'Valid for domestic services' bit is not set to 1b in the AUC.

•

‘Valid for domestic goods’ bit is not set to 1b in the AUC.


•


•




2CJ.053.00 Transaction type is a Purchase of good and services, and Issuer Country Code = Terminal Country Code •



Page 1006


2CJ.054.00 Transaction type is a Purchase of goods and services, and Issuer Country Code = Terminal Country Code (implied) Test No: 2CJ.054.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code matches Issuer Country

Code, Transaction Type indicates a purchase of goods and services, the AUC is present in the card, and the 'Valid for domestic services' bit is set to 1b in the AUC, the terminal does not set the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0:



•


•


•


•

'Valid for domestic services' bit is set to 1b in the AUC.

•

‘Valid for domestic goods’ bit is not set to 1b in the AUC


•


•




2CJ.054.00 Transaction type is a Purchase of goods and services, and Issuer Country Code = Terminal Country Code (implied) •



Page 1008


2CJ.055.00 Transaction type is a Purchase of goods and services, and Issuer Country Code differs from Terminal Country Code Test No: 2CJ.055.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code does not match Issuer

Country Code, Transaction Type indicates a purchase of goods and services, the AUC is present in the card, and the 'Valid for international services' bit is not set to 1b in the AUC, the terminal sets the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0:



•

Transaction is a purchase of goods or services(Transaction type is ‘00’).

•


•


•

'Valid for international services' bit is not set to 1b in the AUC.

•

Valid for international goods’ bit is not set to 1b in the AUC


•


•




2CJ.055.00 Transaction type is a Purchase of goods and services, and Issuer Country Code differs from Terminal Country Code •



Page 1010


2CJ.056.00 Transaction type is a Purchase of goods andservices, and Issuer Country Code differs from Terminal Country Code (implied) Test No: 2CJ.056.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code does not match Issuer

Country Code, Transaction Type indicates a purchase of goods and services, the AUC is present in the card, and the 'Valid for international services' bit is set to 1b in the AUC, the terminal does not set the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0:



•


•


•


•

'Valid for international services' bit is set to 1b in the AUC.

•

‘Valid for international goods’ bit is not set to 1b in the AUC


•


•




2CJ.056.00 Transaction type is a Purchase of goods andservices, and Issuer Country Code differs from Terminal Country Code (implied) •



Page 1012


2CJ.057.00 Transaction has a Cashback amount, and Issuer Country Code = Terminal Country Code Test No: 2CJ.057.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code matches Issuer Country

Code,Transaction has a Cashback amount, the AUC is present in the card, and the 'Domestic Cashback allowed' bit is not set to 1b in the AUC, the terminal sets the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal [CashBack] supported Configuration: Conditions:

•

Transaction has a cashback amount.

•


•


•

'Domestic cashback allowed' bit is not set to 1b in the AUC.


•


•




2CJ.058.00 Transaction has a Cashback amount, and Issuer Country Code = Terminal Country Code (implied) Test No: 2CJ.058.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code matches Issuer Country

Code, Transaction has a Cashback amount, the AUC is present in the card, and the 'Domestic cashback allowed' bit is set to 1b in the AUC, the terminal does not set the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal [CashBack] supported Configuration: Conditions:

•


•


•


•

'Domestic cashback allowed' bit is set to 1b in the AUC.


•


•



Page 1014


2CJ.059.00 Transaction type is a Cashback amount, and Issuer Country Code differs from Terminal Country Code Test No: 2CJ.059.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code does not match Issuer

Country Code, Transaction has a Cashback amount, the AUC is present in the card, and the 'International cashback allowed' bit is not set to 1b in the AUC, the terminal sets the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal [CashBack] supported Configuration: Conditions:

•


•


•


•

'International cashback allowed' bit is not set to 1b in the AUC.


•


•




2CJ.060.00 Transaction type is a Cashback amount, and Issuer Country Code differs from Terminal Country Code (implied) Test No: 2CJ.060.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Terminal Country Code does not match Issuer

Country Code, Transaction has a Cashback amount, the AUC is present in the card, and the 'International cashback allowed' bit is set to 1b in the AUC, the terminal does not set the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal [CashBack] supported Configuration: Conditions:

•


•


•


•

'International cashback allowed' bit is set to 1b in the AUC.


•


•



Page 1016


2CJ.061.00 Application Usage Control is not present in the ICC (implied) Test No: 2CJ.061.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Application Usage control is not present in the

ICC, the Terminal does not set the 'Requested service not allowed for card product' bit in the TVR to 1b. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal NA Configuration: Conditions:

•

AUC is not present in LT.


•


•




2CJ.062.00 Application Usage Control is present in the ICC but not Issuer Country code (implied) Test No: 2CJ.062.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Application Usage control is present in the ICC but

not Issuer Country Code, the Terminal skips the second set of tests described in Book 3 Section 6.4.3. Reference Book 3 - Section 6.4.2 - Application Usage Control EMV 4.0: Reference Book 3 - Section 10.4.2 - Application Usage Control EMV 4.1: Terminal NA Configuration: Conditions:

•


•

'valid at ATMs' and 'valid at terminals other than ATMs' are set in AUC.

•

Issuer Country Code is not present in the LT.


•

The terminal shall process the transaction until completion,by requesting a TC or an AAC.

•



Page 1018


2CJ.063.00 Current Date is earlier than Application Effective Date Test No: 2CJ.063.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal sets to 1b the 'Application not yet effective'

bit in TVR if the current date is earlier than the Application Effective Date. Reference Book 3 - Section 6.4.3 - Application Effective/Expiration Dates EMV 4.0: Checking Reference Book 3 - Section 10.4.3 - Application Effective/Expiration Dates EMV 4.1: Checking Terminal NA Configuration: Conditions:

•

Application Effective Date is present in the LT.

•

Current date is earlier than the Application Effective Date.


•

The terminal shall process the transaction until completion by requesting a TC or an AAC..

•

TVR byte 2, bit 6 = '1' (ie Application not yet effective) received at 1st GENERATE AC.



2CJ.064.00 Current Date is later than Application Effective Date (implied) Test No: 2CJ.064.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal does not set to 1b the 'Application not yet

effective' bit if the current date is later or equal to the Application Effective Date. Reference Book 3 - Section 6.4.3 - Application Effective/Expiration Dates EMV 4.0: Checking Reference Book 3 - Section 10.4.3 - Application Effective/Expiration Dates EMV 4.1: Checking Terminal NA Configuration: Conditions:

•


•

Current date is later than the Application Effective Date.


•


•

TVR byte 2, bit 6 = '0' (ie Application effective) received at 1st GENERATE AC.


Page 1020


2CJ.064.01 Current Date is equal to Application Effective Date (implied) Test No: 2CJ.064.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal does not set to 1b the 'Application not yet

effective' bit if the current date is later or equal to the Application Effective Date. Reference Book 3 - Section 6.4.3 - Application Effective/Expiration Dates EMV 4.0: Checking Reference Book 3 - Section 10.4.3 - Application Effective/Expiration Dates EMV 4.1: Checking Terminal NA Configuration: Conditions:

•


•

Current data is equal to the Application Effective Date.


•


•

TVR byte 2, bit 6 = '0' (ie Application effective) received at 1st GENERATE AC.



2CJ.065.00 Current Date is later than Application Expiration Date Test No: 2CJ.065.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal sets to 1b the 'expired Application' bit if the

current date is later than the Application Expiration Date. Reference Book 3 - Section 6.4.3 - Application Effective/Expiration Dates EMV 4.0: Checking Reference Book 3 - Section 10.4.3 - Application Effective/Expiration Dates EMV 4.1: Checking Terminal NA Configuration: Conditions:

•

Current date is later than the Application Expiration Date.


•


•

TVR byte 2, bit 7 = '1' (ie expired Application) received at 1st GENERATE AC.


Page 1022


2CJ.066.00 Current Date is ealier than Application Expiration Date (implied) Test No: 2CJ.066.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal does not set to 1b the 'expired Application'

bit if the current date is earlier or equal to the Application Expiration Date. Reference Book 3 - Section 6.4.3 - Application Effective/Expiration Dates EMV 4.0: Checking Reference Book 3 - Section 10.4.3 - Application Effective/Expiration Dates EMV 4.1: Checking Terminal NA Configuration: Conditions:

•

Current date is earlier than the Application Expiration Date.


•


•

TVR byte 2, bit 7 = '0' (ie non expired Application) received at 1st GENERATE AC.



2CJ.066.01 Current Date is equal to the Application Expiration Date (implied) Test No: 2CJ.066.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal does not set to 1b the 'expired Application'

bit if the current date is earlier or equal to the Application Expiration Date. Reference Book 3 - Section 6.4.3 - Application Effective/Expiration Dates EMV 4.0: Checking Reference Book 3 - Section 10.4.3 - Application Effective/Expiration Dates EMV 4.1: Checking Terminal NA Configuration: Conditions:

•

Current date is equal to the Application Expiration Date.


•


•

TVR byte 2, bit 7 = '0' (ie non expired Application) received at 1st GENERATE AC.


Page 1024


2CJ.068.00 Cardholder Verification is supported in the AIP Test No: 2CJ.068.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the card supports Cardholder verification (AIP

indicates Cardholder Verification supported), the terminal performs Cardholder verification after the Read Application Data and before completion of the terminal analysis process. To ensure that the terminal sets the 'Cardholder verification was performed' bit in the TSI to 1b, if the Cardholder verification process is performed (successful or not). To ensure that the terminal sets to 1b the 'Cardholder verification was not successful' bit if the list of CVMs is exhausted and Cardholder Verification has not been successful. Reference Book 3 - Section 4 - Transaction Flow EMV 4.0:

Book 3 - Section 6.5 - Cardholder Verification Book Bulletins - Section SU 8-02 - Bulletin n°8, Editorial Changes for EMV 2000 Version 1.0 (Dec-2002) Book Bulletins - Section SU 22 - Bulletin n°22, Terminal behaviour when data for CVM condition is not known (Apr-2004) Reference Book 3 - Section 8 - Transaction Flow EMV 4.1:

Book 3 - Section 10.5 - Cardholder Verification Terminal NA Configuration: Conditions:

•


•

CVM in LT is 'Fail CVM, always' (00 00).


•

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



2CJ.068.00 Cardholder Verification is supported in the AIP at 1st GENERATE AC. •

CVM Results shall be set to "00 00 01''.

•

TSI byte 1, bit 7 = '1' (ie Cardholder verification performed) received at 1st GENERATE AC.


Page 1026


2CJ.069.00 Supported CVR condition: Always Test No: 2CJ.069.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition 'Always' Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal NA Configuration: Conditions:

•

AIP of LT indicates Cardholder Verification is supported (AIP byte 1 bit 5 = 1)

•

CVM in LT is 'Fail CVM, always' (00 00).


•


•


•

CVM Results shall be set to "00 00 01''

•




2CJ.070.00 Supported CVR condition: If unattended cash Test No: 2CJ.070.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If unattended cash'. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal ([Cash] supported AND [Unattended] supported) Configuration: Conditions:

•


•

Transaction Type is cash.

•

CVM in LT is 'Fail CVM, if unattended cash' (00 01) followed by 'Fail CVM, always' (00 00).


•


•


•

CVM result = 00 01 01 (fail CVM if unattended cash, failed).

•



Page 1028


2CJ.070.01 Supported CVR condition: If manual cash Test No: 2CJ.070.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If manual cash'. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal ([Attended] supported AND [Cash] supported) Configuration: Conditions:

•


•


•

CVM in LT is 'Fail CVM, if manual cash' (00 04) followed by 'Fail CVM, always' (00 00).


•


•


•

CVM result = 00 04 01 (fail CVM if manual cash, failed).

•




2CJ.070.02 Supported CVR condition: If purchase with cashback Test No: 2CJ.070.02 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If purchase with

cashback'. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [CashBack] supported Configuration: Conditions:

•


•

Transaction Type is purchase with cashback.

•

CVM in LT is 'Fail CVM, if purchase with cashback' (00 05) followed by 'Fail CVM, always' (00 00).


•


•


•

CVM result = 00 05 01 (fail CVM if purchase with cashback, failed).

•



Page 1030


2CJ.071.00 Supported CVR condition: If 'not unattended cash and not manual cash, and not purchase with cashback' Test No: 2CJ.071.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If 'not unattended

cash and not manual cash, and not purchase with cashback'. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Goods] supported OR [Services] supported Configuration: Conditions:

•


•

CVM in LT is 'Fail CVM, if 'not unattended cash and not manual cash, and not purchase with cashback' (00 02) followed by 'Fail CVM, always' (00 00).

•

CDOL1 requests Amount Authorised and Amount Other.

•

Transaction Type is goods.and services.


•


•


•

CVM result = 00 02 01 (fail CVM if 'not unattended cash and not manual cash and not purchase with cashback, failed).

•




2CJ.073.00 Supported CVR condition: If Terminal supports the CVM and CVM is offline PIN Test No: 2CJ.073.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If Terminal supports

the CVM', when CVM is offline PIN. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•


•

CVM in LT is 'Plaintext PIN verification performed by ICC, if Terminal supports the CVM' (01 03).

Action: Cardholder presents a wrong PIN. Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•


•



Page 1032


2CJ.073.01 Supported CVR condition: If Terminal supports the CVM and CVM is Enciphered offline PIN Test No: 2CJ.073.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If Terminal supports

the CVM', when CVM is Enciphered offline PIN. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

CVM in LT is 'Enciphered PIN verified by ICC', if Terminal supports the CVM' (04 03).

Action: Cardholder presents a valid PIN. Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•


•




2CJ.074.00 Supported CVR condition: If Terminal supports the CVM and CVM is online PIN Test No: 2CJ.074.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If Terminal supports

the CVM', when CVM is online PIN. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Online Enciphered PIN] supported Configuration: Conditions:

•

Application in LT is selected and transaction is processed with LT.

•


•

CVM in LT is 'Enciphered Online PIN verification, if Terminal supports the CVM' (02 03).

Action: Cardholder enters a valid PIN. Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

TVR byte 3, bit 8 = '0' (ie Cardholder verification successful) received at 1st GENERATE AC.

•

TVR byte 3, bit 3 = '1' (ie online PIN entered) received at 1st GENERATE AC.

•

Encrypted PIN Data is sent in the Authorization Request.

•


•



Page 1034


2CJ.075.00 Supported CVR condition: If Terminal supports the CVM and CVM is signature Test No: 2CJ.075.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If Terminal supports

the CVM', when CVM is signature. Reference Book 3 - Section 5.3 - Command Use EMV 4.0: Reference Book 3 - Section 9.3 - Command Use EMV 4.1: Terminal [Signature] supported Configuration: Conditions:

•


•

CVM in LT is 'signature, if Terminal supports the CVM' (1E 03).


•


•


•

CVM Results shall be set to "1E 03 00''.

•




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 Test No: 2CJ.077.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition "If Transaction is in the

application currency and is under X value" when the transaction amount is less than X. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 22 - Bulletin n°22, Terminal behaviour when data for CVM condition is not known (Apr-2004) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Amount known before CVM Processing] supported Configuration: Conditions:

•


•

CVM in LT is 'Fail CVM, if Transaction is in the application currency and is under X' value (00 06) followed by 'Fail CVM, always' (00 00).

•

Transaction Amount is known before CVM Processing.

•

Transaction amount is less than X value.

•

Transaction Currency Code equals Application Currency Code.


•


•


•

CVM result = 00 06 01 (fail CVM if Transaction is in the application currency and is under X, failed).

•



Page 1036




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 Test No: 2CJ.077.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition "If Transaction is in the

application currency and is under X value" when the transaction amount is Greater than X. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

CVM in LT is 'Fail CVM, if Transaction is in the application currency under X' value (00 06) followed by Fail CVM, always' (00 00).

•


•

Transaction amount is greater than X value.

•



•


•


•

CVM Results show 'Fail CVM, always, process is failed' as the last CVM processed ('00 00 01').

•



Page 1038




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 Test No: 2CJ.077.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition "If Transaction is in the

application currency and is under X value" when the transaction amount is Equal to X. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

CVM in LT is 'Fail CVM, if Transaction is in the application currency under X' value (00 06) followed by 'Fail CVM, always' (00 00).

•


•

Transaction amount is equal to X value.

•



•


•


•


•



Page 1040




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. Test No: 2CJ.078.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition "If Transaction is in the

application currency and is over X value" when transaction amount is greater than X. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

CVM in LT is 'Fail CVM, if Transaction is in the application currency and is over X value' (00 07) followed by 'Fail CVM, always' (00 00).

•


•

Transaction amount is greater than X value.

•



•


•


•

CVM result = 00 07 01 (fail CVM if Transaction is in the application currency and is over X, failed).

•



Page 1042




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. Test No: 2CJ.078.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition "If Transaction is in the

application currency and is over X value" when transaction amount is less than X. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

CVM in LT is 'Fail CVM, if Transaction is in the application currency and is over X' value (00 07) followed by 'Fail CVM, always ' (00 00).

•


•

Transaction amount is less than X value.

•



•


•


•


•



Page 1044




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. Test No: 2CJ.078.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition "If Transaction is in the

application currency and is over X value" when transaction amount is Equal to X. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

CVM in LT is 'Fail CVM, if Transaction is in the application currency and is over X' value (00 07) followed by 'Fail CVM, always' (00 00).

•


•

Transaction amount is equal to X value.

•



•


•


•


•



Page 1046




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. Test No: 2CJ.079.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If Transaction is in

the application currency and is under Y value' when the transaction amount is less than Y. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

CVM in LT is 'Fail CVM, if Transaction is in the application currency and is under Y value' (00 08) followed by 'Fail CVM, always' (00 00).

•


•

Transaction amount is less than Y value.

•



•


•


•

CVM result = 00 08 01 (fail CVM if Transaction is in the application currency and is under Y, failed).

•



Page 1048




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 Test No: 2CJ.079.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If Transaction is in

the application currency and is under Y value' when the transaction amount is greater than Y. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

CVM in LT is 'Fail CVM if Transaction is in the application currency and is under Y' value (00 08) followed by 'Fail CVM, always' (00 00).

•


•

Transaction amount is greater than Y value.

•



•


•


•


•



Page 1050




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. Test No: 2CJ.079.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If Transaction is in

the application currency and is under Y value' when the transaction amount is equal to Y. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

CVM in LT is 'Fail CVM, if Transaction is in the application currency and is under Y' value (00 08) followed by 'Fail CVM, always' (00 00).

•


•

Transaction amount is equal to Y value.

•



•


•


•


•



Page 1052




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. Test No: 2CJ.080.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If Transaction is in

the application currency and is over Y value' when the transaction amount is greater than Y. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

CVM in LT is 'Fail CVM, if Transaction in the application currency and is over Y' value (00 09) followed by 'Fail CVM, always' (00 00).

•


•

Transaction amount is greater than Y value.

•



•


•


•

CVM result = 00 09 01 (fail CVM if Transaction is in the application currency and is over Y, failed).

•



Page 1054




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. Test No: 2CJ.080.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If Transaction is in

the application currency and is over Y value' when the transaction amount is equal to Y. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

CVM in LT is 'Fail CVM, if Transaction is in the application currency and is over Y' value (00 09) followed by 'Fail CVM always' (00 00).

•


•

Transaction amount is equal to Y value.

•



•


•


•


•



Page 1056




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. Test No: 2CJ.080.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal supports CVM condition is 'If Transaction is in

the application currency and is over Y value' when the transaction amount is less than Y. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

CVM in LT is 'Fail CVM, if Transaction is in the application currency and is over Y' value (00 09) followed by 'Fail CVM always' (00 00).

•


•

Transaction amount is less than Y value.

•



•


•


•


•



Page 1058




2CJ.081.01 Random Transaction Selection: Transaction Amount Less than the Threshold Value for Biased Random Selection Test No: 2CJ.081.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal performs Random Transaction Selection

checking, when the transaction amount is less than the Threshold Value for Biased Random Selection Reference Book 3 - Section 6.6.2 - Random Transaction Selection EMV 4.0: Reference Book 3 - Section 10.6.2 - Random Transaction Selection EMV 4.1: Terminal [Random Transaction Selection] supported Configuration: Conditions:

•


•

Transaction Amount is less than the Threshold Value for Biased Random Selection.

•

Random Number is less than or equal to Target Percentage to be Used for Random Selection (Test must be repeated until this condition is met).


•


•

TVR byte 4, bit 5 = '1' (ie Transaction selected randomly for online processing) received at 1st GENERATE AC.


Page 1060


2CJ.081.02 Random Transaction Selection: Transaction Amount Less than the Threshold Value for Biased Random Selection Test No: 2CJ.081.02 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal performs Random Transaction Selection

checking, when the transaction amount is less than the Threshold Value for Biased Random Selection Reference Book 3 - Section 6.6.2 - Random Transaction Selection EMV 4.0: Reference Book 3 - Section 10.6.2 - Random Transaction Selection EMV 4.1: Terminal [Random Transaction Selection] supported Configuration: Conditions:

•


•

Transaction Amount is less than the Threshold Value for Biased Random Selection.

•

Random Number is greater than the Target Percentage to be Used for Random Selection (Test must be repeated until this condition is met).


•


•

TVR byte 4, bit 5 = '0' (ie Transaction has not been selected randomly for online processing) received at 1st GENERATE AC.



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 Test No: 2CJ.081.03 - Revision 10g - Number of sub cases: 2 Objective: To ensure that terminal performs Random Transaction Selection

checking, when the transaction amount is equal to or greater than the Threshold Value for Biased Random Selection, but less than the Floor Limit Reference Book 3 - Section 6.6.2 - Random Transaction Selection EMV 4.0: Reference Book 3 - Section 10.6.2 - Random Transaction Selection EMV 4.1: Terminal [Random Transaction Selection] supported Configuration: Conditions:

•


•

Random Number is less than or equal to Transaction Target Percentage (Test must be repeated until this condition is met).

•

Case 01: Transaction Amount is equal to the Threshold Value for Biased Random Selection but less than the Floor Limit.

•

Case 02: Transaction Amount is greater than the Threshold Value for Biased Random Selection but less than the Floor Limit.


•


•

TVR byte 4, bit 5 = '1' (ie Transaction selected randomly for online processing) received at 1st GENERATE AC.


Page 1062


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 Test No: 2CJ.081.04 - Revision 10g - Number of sub cases: 2 Objective: To ensure that terminal performs Random Transaction Selection

checking, when the transaction amount is equal to or greater than the Threshold Value for Biased Random Selection, but less than the Floor Limit. Reference Book 3 - Section 6.6.2 - Random Transaction Selection EMV 4.0: Reference Book 3 - Section 10.6.2 - Random Transaction Selection EMV 4.1: Terminal [Random Transaction Selection] supported Configuration: Conditions:

•


•

Random Number is greater than the Transaction Target Percentage (Test must be repeated until this condition is met).

•

Case 01: Transaction Amount is equal to the Threshold Value for Biased Random Selection but less than the Floor Limit.

•

Case 02: Transaction Amount is greater than the Threshold Value for Biased Random Selection but less than the Floor Limit.


•


•

TVR byte 4, bit 5 = '0' (ie Transaction has not been selected randomly for online processing) received at 1st GENERATE AC.



2CJ.082.01 CVM List is not present in the ICC Test No: 2CJ.082.01 - Revision 17 - Number of sub cases: 0 Objective: To ensure that terminal does not set the 'Cardholder verification was

performed' bit in the TSI to 1b, if CVM List is not present in the ICC. To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b if Cardholder verification is supported in AIP and CVM List is missing in the card. To ensure that the terminal sets the CVM Results byte 1 to 'No CVM performed' if no CVM is present or there is no CVM conditions satisfied Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0:

Book 3 - Section 6.5 - Cardholder Verification Book 4 - Section 2.3.4.5 - CVM Results Book Bulletins - Section SU 8-02 - Bulletin n°8, Editorial Changes for EMV 2000 Version 1.0 (Dec-2002) Book Bulletins - Section SU 22 - Bulletin n°22, Terminal behaviour when data for CVM condition is not known (Apr-2004) Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1:

Book 3 - Section 10.5 - Cardholder Verification Book 4 - Section 6.3.4.5 - CVM Results Terminal NA Configuration: Conditions:

•


•

CVM is not present in the LT.


•


•

TSI byte 1, bit 7 = '0' (ie Cardholder verification was not


Page 1064


2CJ.082.01 CVM List is not present in the ICC performed) received at 1st GENERATE AC. •

TVR byte 3, bit 8 = '0' (ie Cardholder verification not failed) received at 1st GENERATE AC.

•

TVR byte 1, bit 6 = '1' (ie ICC Data missing) received at 1st GENERATE AC.

•

CVM Results ('3F 00 00)



2CJ.083.00 Second byte of a Cardholder Verification Rule is not satisfied Test No: 2CJ.083.00 - Revision 11 - Number of sub cases: 9 Objective: To ensure that if the conditions expressed in the second byte of a

Cardholder Verification Rule are not satisfied, the terminal bypasses the rules and proceeded to the next rule. To ensure that the terminal sets the CVM Results byte 3 to 'failed' when the last CVM performed was not considered as successful. To ensure that if the CVM List is present in the ICC, the terminal processes each rule in the order in which it appears in the CVM List, until the cardholder verification process is completed. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book 4 - Section 2.3.4.5 - CVM Results Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1:

Book 4 - Section 6.3.4.5 - CVM Results Terminal NA Configuration: Conditions:

•


•

CVM List is 'Fail CVM, (associated condition described in below sub-cases) followed by 'Fail CVM, always' (00 00).

•

Case 01: condition is ‘if unattended cash’ (00 01) and transaction is not cash.

•

Case 02: [Attended] supported - condition is ‘if unattended cash’ (00 01).

•

Case 03: condition is ‘manual cash’ (00 04) and transaction is not cash.

•

Case 04: [Unattended] supported - condition is ‘manual cash’ (00 04).

•

Case 05: condition is ‘purchase with cashback’ (00 05) and


Page 1066


2CJ.083.00 Second byte of a Cardholder Verification Rule is not satisfied transaction is not cashback. •

Case 06: condition is ‘if transaction is under X' (00 06) and amount is over X.

•

Case 07: condition is ‘if transaction is over X' (00 07) and amount is under X.

•

Case 08: condition is ‘if transaction is under Y' (00 08) and amount is over Y.

•

Case 09: condition is ‘if transaction is over Y' (00 09) and amount is under Y.


•


•


•

CVM result ='00 00 01'.

•




2CJ.083.01 Non Supported CVR condition: If Terminal supports the CVM and CVM is offline Plaintext PIN Test No: 2CJ.083.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal processes the next CVM in the list when the

CVM condition is 'If Terminal supports the CVM', when CVM is offline PIN and the terminal does not support offline Plaintext PIN. To ensure that if the CVM List is present in the ICC, the terminal processes each rule in the order in which it appears in the CVM List, until the cardholder verification process is completed. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Offline Plaintext PIN] not supported Configuration: Conditions:

•


•

CVM in LT is 'Plaintext PIN verification performed by ICC if Terminal supports the CVM' (01 03) followed by 'Fail CVM, always' (00 00).

•

CDOL1 requests CVM Results.


•


•


•

CVM Results show 'Fail CVM, always, process is failed' as the last CVM processed (00 00 01').

•



Page 1068


2CJ.083.02 Non Supported CVR condition: If Terminal supports the CVM and CVM is offline Enciphered PIN Test No: 2CJ.083.02 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal processes the next CVM in the list when the

CVM condition is 'If Terminal supports the CVM', when CVM is offline PIN and the terminal does not support offline Enciphered PIN. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Offline Enciphered PIN] not supported Configuration: Conditions:

•


•

CVM in LT is 'Offline Enciphered PIN verification performed by ICC if Terminal supports the CVM' (04 03) followed by 'Fail CVM, always' (00 00).

•



•


•


•


•




2CJ.083.03 Non Supported CVR condition: If Terminal supports the CVM and CVM is online Enciphered PIN Test No: 2CJ.083.03 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal processes the next CVM in the list when the

CVM condition is 'If Terminal supports the CVM', when CVM is online PIN and the terminal does not support online Enciphered PIN. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Online Enciphered PIN] not supported Configuration: Conditions:

•


•

CVM in LT is 'Online Enciphered PIN verification performed by ICC if Terminal supports the CVM' (02 03) followed by 'Fail CVM, always' (00 00).

•



•


•


•

TVR byte 3, bit 3 = '0' (ie online PIN not entered) received at 1st GENERATE AC.

•


•



Page 1070


2CJ.083.04 Non Supported CVR condition: If Terminal supports the CVM and CVM is Signature Test No: 2CJ.083.04 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal processes the next CVM in the list when the

CVM condition is 'If Terminal supports the CVM', when CVM is Signature and the terminal does not support Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Signature] not supported Configuration: Conditions:

•


•

CVM in LT is 'Signature if Terminal supports the CVM' (1E 03) followed by 'Fail CVM, always' (00 00).

•



•


•


•


•




2CJ.083.05 Non Supported CVR condition: If Terminal supports the CVM and CVM is offline Plaintext PIN and Signature Test No: 2CJ.083.05 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal processes the next CVM in the list when the

CVM condition is 'If Terminal supports the CVM', when CVM is offline Plaintext PIN and Signature and the terminal does not support offline Plaintext PIN or Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal ([Offline Plaintext PIN] not supported OR [Signature] not supported) Configuration: Conditions:

•


•

CVM in LT is 'Offline Plaintext PIN verification performed by ICC and Signature if Terminal supports the CVM' (03 03) followed by 'Fail CVM, always' (00 00).

•



•


•


•


•



Page 1072


2CJ.083.06 Non Supported CVR condition: If Terminal supports the CVM and CVM is offline Enciphered PIN and Signature Test No: 2CJ.083.06 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal processes the next CVM in the list when the

CVM condition is 'If Terminal supports the CVM', when CVM is offline Enciphered PIN and Signature and the terminal does not support offline Enciphered PIN or Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal ([Offline Enciphered PIN] not supported OR [Signature] not supported) Configuration: Conditions:

•


•

CVM in LT is 'Offline Enciphered PIN verification performed by ICC and Signature if Terminal supports the CVM' (05 03) followed by 'Fail CVM, always' (00 00).

•



•


•


•


•




2CJ.083.07 Non Supported CVR condition: If Terminal supports the CVM and CVM is No CVM Required Test No: 2CJ.083.07 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal processes the next CVM in the list when the

CVM condition is 'If Terminal supports the CVM', when CVM is 'No CVM Required' and the terminal does not support 'No CVM Required'. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [No CVM] not supported Configuration: Conditions:

•


•

CVM in LT is 'No CVM Required if Terminal supports the CVM' (1F 03) followed by 'Fail CVM, always' (00 00).

•



•


•


•


•



Page 1074


2CJ.084.00 ICC Data required by the CVM Condition Code is missing Test No: 2CJ.084.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the ICC data required by the condition expressed in

the second byte of a Cardholder Verification Rule is not present, the terminal bypasses the rules and proceeded to the next rule. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

CVM List is Fail CVM if transaction is in the application currency and is under X' value (00 06) followed by 'Fail CVM, always' (00 00).

•

Application Currency Code is not present in the LT.

•


•

X is such as Transaction amount is under X.

•



•


•


•


•

TSI byte 1, bit 7 = '1' (ie Cardholder verification performed)



2CJ.084.00 ICC Data required by the CVM Condition Code is missing received at 1st GENERATE AC.


Page 1076


2CJ.084.01 ICC Data required by the CVM Condition Code is missing (Amount Authorised) Test No: 2CJ.084.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the ICC data required by the condition expressed in

the second byte of a Cardholder Verification Rule is not present, the terminal bypasses the rules and proceeded to the next rule. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 22 - Bulletin n°22, Terminal behaviour when data for CVM condition is not known (Apr-2004) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Amount known before CVM Processing] not supported Configuration: Conditions:

•


•

CVM List is Fail CVM if transaction is in the application currency and is under X' value (00 06) followed by 'Fail CVM, always' (00 00).

•

Application Currency Code is present in the LT.

•

Transaction Currency Code is equal to Application Currency Code.

•

Transaction Amount is unknown before CVM Processing.

•

X is such as Transaction amount is under X.


•


•


•

CVM Results show 'Fail CVM, always, process is failed' as the



2CJ.084.01 ICC Data required by the CVM Condition Code is missing (Amount Authorised) last CVM processed ('00 00 01'). •



Page 1078


2CJ.085.00 CVM Condition Code is outside the range of codes understood by the terminal Test No: 2CJ.085.00 - Revision 11 - Number of sub cases: 7 Objective: To ensure that if the condition code expressed in the second byte of a

Cardholder Verification Rule is outside the range of codes understood by the terminal, the terminal bypasses the rules and proceeded to the next rule. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal NA Configuration: Conditions:

•


•

Case 01: CVM List is 'Fail CVM, if RFU (00 0A) following by 'Fail CVM, always' (00 00).

•

Case 02: CVM List is 'Online Enciphered PIN, if RFU' (02 0A) following by 'Fail CVM, always' (00 00).

•

Case 03: CVM List is 'Offline Plaintext PIN and signature, if RFU' (03 0A) following by 'Fail CVM, always' (00 00).

•

Case 04: CVM List is 'offline enciphered PIN, if RFU' (04 0A) following by 'Fail CVM, always' (00 00).

•

Case 05: CVM List is 'Offline enciphered PIN and signature, if RFU' (05 0A) following by 'Fail CVM, always' (00 00).

•

Case 06: CVM List is 'RFU, if RFU' (3F 0A) following by 'Fail CVM, always' (00 00).

•

Case 07: CVM List is 'RFU, if RFU' (07 0A) following by 'Fail CVM, always' (00 00).




2CJ.085.00 CVM Condition Code is outside the range of codes understood by the terminal Pass Criteria:

•


•


•


•



Page 1080


2CJ.086.00 Cardholder Verification Rule for cash transactions not satisfied, transaction type Test No: 2CJ.086.00 - Revision 11 - Number of sub cases: 2 Objective: When a cash cardholder verification rule is not satisfied based on

transaction type, the terminal bypasses the rule and proceeded to the next rule. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal NA Configuration: Conditions:

•


•

LT supports Cardholder verification.

•

Transaction Type is not cash.

•

CVM List is 'Fail CVM, with the following conditions satisfied, followed by Fail CVM, always'.

•

Case 01: [Unattended] supported - condition is ‘if unattended cash’ (00 01).

•

Case 02: [Attended] supported - condition is ‘manual cash’ (00 04).


•


•

TVR byte 3, bit 8 = ‘1’ (ie Cardholder verification failed) received at 1st GENERATE AC.

•




2CJ.086.00 Cardholder Verification Rule for cash transactions not satisfied, transaction type received at 1st GENERATE AC. •

CVM Results = '00 00 01' (Fail CVM, always, failed) received at 1st GENERATE AC.


Page 1082


2CJ.086.01 Cardholder Verification Rule for cash transactions not satisfied, terminal type Test No: 2CJ.086.01 - Revision 11 - Number of sub cases: 2 Objective: When a cash cardholder verification rule is not satisfied, based on

terminal type, the terminal bypasses the rule and proceeded to the next rule. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

LT supports Cardholder verification.

•


•

CVM List is 'Fail CVM, with the following conditions satisfied, followed by Fail CVM, always'.

•

Case 01: [Attended] supported - condition is ‘if unattended cash’ (00 01).

•

Case 02: [Unattended] supported - condition is ‘manual cash’ (00 04).


•


•

TVR byte 3, bit 8 = ‘1’ (ie Cardholder verification failed) received at 1st GENERATE AC.

•




2CJ.086.01 Cardholder Verification Rule for cash transactions not satisfied, terminal type received at 1st GENERATE AC. •

CVM Results = '00 00 01' (Fail CVM, always, failed)


Page 1084


2CJ.087.00 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail CVM Test No: 2CJ.087.00 - Revision 17 - Number of sub cases: 5 Objective: To ensure that the terminal performs the CVM if the condition code is

satisfied and CVM code is fail CVM Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1:


•


•

CVM List is 'Fail CVM' with the following conditions satisfied:

•

Case 01: condition is 'always' (00 00).

•

Case 02: ([Unattended] supported AND [Cash] supported) condition is 'If unattended cash (Transaction is cash)' (00 01).

•

Case 03: condition is 'not unattended cash and not manual cash, and not purchase with cashback (Transaction is not cash and not purchase with cashback)' (00 02).

•

Case 04: ([Attended] supported AND [Cash] supported) condition is 'If manual cash (Transaction is cash)' (00 04).

•

Case 05: condition is 'If purchase with cashback (Transaction is purchase with cashback)' (00 05).


•




2CJ.087.00 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail CVM •


•

TVR byte 3, bit 7 = '0' (ie Recognised CVM) received at 1st GENERATE AC.

•


•

CVM Result = (00 xx 01) where xx = number of the CVM condition of the sub case in question.


Page 1086


2CJ.087.01 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail CVM Test No: 2CJ.087.01 - Revision 11 - Number of sub cases: 4 Objective: To ensure that the terminal performs the CVM if the condition code is

satisfied and CVM code is fail CVM Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•


•

Transaction Amount is in the Application Currency

•

CVM List is 'Fail CVM' with the following conditions satisfied:

•

Case 01: condition is ' transaction is under X (and Amount is under X)' (00 06).

•

Case 02: condition is ' transaction is over Y (and Amount is over Y)' (00 09).

•

Case 03: condition is ' transaction is over X (and Amount is over X)' (00 07).

•

Case 04: condition is ' transaction is under Y (and Amount is under Y)' (00 08).


•




2CJ.087.01 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail CVM •


•


•



Page 1088


2CJ.087.02 Second byte of Cardholder Verification Rule satisfied and CVM Code is Fail CVM (2) Test No: 2CJ.087.02 - Revision 17 - Number of sub cases: 0 Objective: To ensure that the terminal stops the CVM processing when the CVM

code is fail CVM, when the setting of the byte 1 bit 7 of this entry is ‘1’ Reference NA EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1:


•


•

CVM List is 'Fail CVM, always (40 00), followed by Plaintext PIN verification performed by ICC, always (01 00), followed by Enciphered PIN verified online, always (02 00), followed by Plaintext PIN verification performed by ICC and signature, always (03 00), followed by Enciphered PIN verification performed by ICC, always (04 00), followed by Enciphered PIN verification performed by ICC and signature, always (05 00), followed by Signature, always (1E 00), followed by No CVM, always (1F 00)


•


•


•


•

CVM Result = 40 00 01




Page 1090


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) Test No: 2CJ.088.00 - Revision 10g - Number of sub cases: 5 Objective: To ensure that if terminal supports Plaintext PIN verified by ICC, the

terminal performs the CVM if the condition code is satisfied and CVM code is Plaintext PIN verified by ICC. To ensure that the terminal sets the CVM Results byte 3 to 'failed' when the last CVM performed was not considered as successful. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book 4 - Section 6.3.4.5 - CVM Results Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•


•

CVM List is 'Plaintext PIN verified by ICC' with the following conditions satisfied:

•


•

Case 02: ([Unattended] supported AND [Cash] supported) condition is 'unattended cash (Transaction is cash)' (01 01).

•

Case 03: ([Attended] supported AND [Cash] supported) condition is 'If manual cash' (Transaction is cash) (01 04).

•


•

Case 05: condition is 'not unattended cash and not manual cash, and not purchase with cashback (Transaction is not cash and not purchase with cashback) (01 02).



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) Action: Cardholder enters wrong PIN. Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•

Terminal shall ask the cardholder to present his PIN.

•


•



Page 1092


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) Test No: 2CJ.088.01 - Revision 17 - Number of sub cases: 5 Objective: To ensure that if the terminal does not support Plaintext PIN verified by

ICC, the terminal performs the CVM if the condition code is satisfied and CVM code is Plaintext PIN verified by ICC. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal [Offline Plaintext PIN] not supported Configuration: Conditions:

•


•


•


•

Case 02: ([Unattended] supported AND [Cash] supported) condition is 'unattended cash' (Transaction is cash)' (01 01).

•

Case 03: condition is 'not unattended cash and not manual cash, and not purchase with cashback' (Transaction is not cash and not purchase with cashback) (01 02).

•

Case 04: ([Attended] supported AND [Cash] supported) condition is 'If manual cash' (Transaction is cash)' (01 04).

•





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) Pass Criteria:

•


•


•

TVR byte 3, bit 5 = '1' (ie PIN entry required and PIN pad not present or not working) received at 1st GENERATE AC (this TVR is only applicable when terminal does not support Offline Enciphered PIN)

•


•


•

CVM Result = 3F 00 01


Page 1094


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) Test No: 2CJ.088.02 - Revision 11 - Number of sub cases: 4 Objective: To ensure that if terminal supports Plaintext PIN verified by ICC, the

terminal performs the CVM if the condition code is satisfied and CVM code is Plaintext PIN verified by ICC. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 22 - Bulletin n°22, Terminal behaviour when data for CVM condition is not known (Apr-2004) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal ([Offline Plaintext PIN] supported AND [Amount known before CVM Configuration: Processing] supported) Conditions:

•


•


•


•


•

Case 01: condition is 'transaction is under X (and Amount is under X)' (01 06).

•

Case 02: condition is 'transaction is over Y (and Amount is over Y)' (01 09).

•

Case 03: condition is 'transaction is over X (and Amount is over X)' (01 07).

•

Case 04: condition is 'transaction is under Y (and Amount is under Y)' (01 08).

Action: Cardholder enters wrong PIN. Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•




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) requesting a TC or an AAC. •


•


•


•



Page 1096


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) Test No: 2CJ.088.03 - Revision 17 - Number of sub cases: 4 Objective: To ensure that if the terminal does not support Plaintext PIN verified by

ICC, the terminal performs the CVM if the condition code is satisfied and CVM code is Plaintext PIN verified by ICC. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 22 - Bulletin n°22, Terminal behaviour when data for CVM condition is not known (Apr-2004) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1:

Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal ([Offline Plaintext PIN] not supported AND [Amount known before CVM Configuration: Processing] supported ) Conditions:

•


•


•


•


•


•


•


•





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) Pass Criteria:

•


•


•

TVR byte 3, bit 5 = '1' (ie PIN entry required and PIN pad not present or not working) received at 1st GENERATE AC (only if terminal does not support both Enciphered and plaintext PIN)

•


•

CVM Result = 3F 00 01.


Page 1098


2CJ.089.00 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online (Enciphered PIN Online supported) Test No: 2CJ.089.00 - Revision 11 - Number of sub cases: 5 Objective: To ensure that if terminal supports Enciphered PIN Online, the terminal

performs the CVM if the condition code is satisfied and CVM code is Enciphered PIN Online. To ensure that the terminal sets the CVM Results byte 3 to 'failed' when the last CVM performed was not considered as successful. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book 4 - Section 6.3.4.5 - CVM Results Terminal [Online Enciphered PIN] supported Configuration: Conditions:

•


•

CVM List is 'Enciphered PIN online' with the following conditions satisfied:

•


•

Case 02: ([Unattended] supported AND [Cash] supported) condition is 'unattended cash' (Transaction is cash) (02 01).

•

Case 03: ([Attended] supported AND [Cash] supported) condition is 'If manual cash' (Transaction is cash) (02 04).

•

Case 04: condition is 'If purchase with cashback' (Transaction is purchase with cashback) (02 05).

•

Case 05: condition is 'not unattended cash and not manual cash, and not purchase with cashback (Transaction is not cash and not purchase with cashback )' (02 02).



2CJ.089.00 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online (Enciphered PIN Online supported) Action: Cardholder enters a valid PIN. Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•


•


•


•


•



Page 1100


2CJ.089.01 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online (Enciphered PIN Online not supported) Test No: 2CJ.089.01 - Revision 17 - Number of sub cases: 5 Objective: To ensure that if the terminal does not support Enciphered PIN Online,

the terminal performs the CVM if the condition code is satisfied and CVM code is Enciphered PIN Online Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Online Enciphered PIN] not supported Configuration:

Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Conditions:

•


•


•


•


•


•

Case 04: condition is 'If purchase with cashback' (Transaction is purchase with cashback)' (02 05).

•





2CJ.089.01 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online (Enciphered PIN Online not supported) Pass Criteria:

•


•


•

TVR byte 3, bit 5 = '1' (ie PIN entry required and PIN pad not present) received at 1st GENERATE AC.

•


•


•


•



Page 1102


2CJ.089.02 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online (Enciphered PIN Online supported) (2) Test No: 2CJ.089.02 - Revision 11 - Number of sub cases: 4 Objective: To ensure that if terminal supports Enciphered PIN Online, the terminal

performs the CVM if the condition code is satisfied and CVM code is Enciphered PIN Online Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 22 - Bulletin n°22, Terminal behaviour when data for CVM condition is not known (Apr-2004) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal ([Online Enciphered PIN] supported AND [Amount known before CVM Configuration: Processing] supported) Conditions:

•


•


•


•


•


•


•


•



•




2CJ.089.02 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online (Enciphered PIN Online supported) (2) requesting a TC or an AAC. •


•


•


•


•


•



Page 1104


2CJ.089.03 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online (Enciphered PIN Online not supported) (2) Test No: 2CJ.089.03 - Revision 17 - Number of sub cases: 4 Objective: To ensure that if the terminal does not support Enciphered PIN Online,

the terminal performs the CVM if the condition code is satisfied and CVM code is Enciphered PIN Online Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal ([Online Enciphered PIN] not supported AND [Amount known before Configuration: CVM Processing] supported) Conditions:

•


•


•


•


•


•


•


•





2CJ.089.03 Second byte of CVR satisfied and CVM Code is Enciphered PIN Online (Enciphered PIN Online not supported) (2) Pass Criteria:

•


•


•


•


•


•



Page 1106


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) Test No: 2CJ.090.00 - Revision 10g - Number of sub cases: 5 Objective: To ensure that if terminal supports Plaintext PIN verified by ICC and

signature, the terminal performs the CVM if the condition code is satisfied and CVM code is Plaintext PIN verified by ICC and Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal ([Offline Plaintext PIN] supported AND [Signature] supported) Configuration: Conditions:

•


•

CVM List is 'Plaintext PIN verified by ICC and signature' with the following conditions satisfied:

•


•

Case 02: ([Unattended] supported AND [Cash] supported) condition is 'unattended cash (Transaction is cash)' (03 01).

•


•


•



•




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) requesting a TC or an AAC. •


•


•


•



Page 1108


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) Test No: 2CJ.090.01 - Revision 17 - Number of sub cases: 5 Objective: To ensure that if the terminal does not support Plaintext PIN verified by

ICC or signature, the terminal performs the CVM if the condition code is satisfied and CVM code is Plaintext PIN verified by ICC and Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal ([Offline Plaintext PIN] not supported OR [Signature] not supported) Configuration: Conditions:

•


•


•


•


•


•


•





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) Pass Criteria:

•


•


•

TVR byte 3, bit 5 = ‘1’ (ie PIN entry required and PIN pad not present or not working) received at 1st GENERATE AC (only if terminal does not support both enciphered and plaintext PIN)

•


•


•



Page 1110


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) Test No: 2CJ.090.02 - Revision 11 - Number of sub cases: 4 Objective: To ensure that if terminal supports Plaintext PIN verified by ICC and

signature, the terminal performs the CVM if the condition code is satisfied and CVM code is Plaintext PIN verified by ICC and Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 22 - Bulletin n°22, Terminal behaviour when data for CVM condition is not known (Apr-2004) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal (([Offline Plaintext PIN] supported AND [Amount known before CVM Configuration: Processing] supported) AND [Signature] supported) Conditions:

•


•


•


•


•


•


•


•


Action: Cardholder enters wrong PIN. Procedure: Application in LT is selected and transaction is processed with LT.



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) Pass Criteria:

•


•


•


•


•



Page 1112


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) Test No: 2CJ.090.03 - Revision 17 - Number of sub cases: 4 Objective: To ensure that if the terminal does not support Plaintext PIN verified by

ICC or signature, the terminal performs the CVM if the condition code is satisfied and CVM code is Plaintext PIN verified by ICC and Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal ([Amount known before CVM Processing] supported AND ([Signature] Configuration: not supported OR [Offline Plaintext PIN] not supported)) Conditions:

•


•


•


•


•


•


•


•


Action: NA



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) Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•


•


•



Page 1114


2CJ.091.00 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by ICC (Enciphered PIN verified by ICC supported) Test No: 2CJ.091.00 - Revision 10g - Number of sub cases: 5 Objective: To ensure that if terminal supports Enciphered PIN verified by ICC, the

terminal performs the CVM if the condition code is satisfied and CVM code is Enciphered PIN verified by ICC. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

CVM List is 'Enciphered PIN verified by ICC' with the following conditions satisfied:

•

Case 01: condition is 'always' (04 00)

•

Case 02: ([Unattended] supported AND [Cash] supported) condition is 'unattended cash' (Transaction is cash)' (04 01)

•

Case 03: ([Attended] supported AND [Cash] supported) condition is 'If manual cash' (Transaction is cash)' (04 04)

•

Case 04: condition is 'If purchase with cashback' (Transaction is purchase with cashback)' (04 05)

•

Case 05: condition is 'not unattended cash and not manual cash, and not purchase with cashback (Transaction is not cash and not purchase with cashback )' (04 02)


•




2CJ.091.00 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by ICC (Enciphered PIN verified by ICC supported) requesting a TC or an AAC. •


•


•


•



Page 1116


2CJ.091.01 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by ICC (Enciphered PIN verified by ICC not supported) Test No: 2CJ.091.01 - Revision 17 - Number of sub cases: 5 Objective: To ensure that if the terminal does not support Enciphered PIN verified

by ICC, the terminal performs the CVM if the condition code is satisfied and CVM code is Enciphered PIN verified by ICC. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal [Offline Enciphered PIN] not supported Configuration: Conditions:

•


•


•


•

Case 02: ([Unattended] supported AND [Cash] supported) condition is 'unattended cash' (Transaction is cash)' (04 01)

•


•


•

Case 05: condition is 'not unattended cash and not manual cash, and not purchase with cashback (Transaction is not cash and not purchase with cashback )' (04 02)




2CJ.091.01 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by ICC (Enciphered PIN verified by ICC not supported) Pass Criteria:

•


•


•


•


•


•



Page 1118


2CJ.091.02 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by ICC (Enciphered PIN verified by ICC supported) (2) Test No: 2CJ.091.02 - Revision 11 - Number of sub cases: 4 Objective: To ensure that if terminal supports Enciphered PIN verified by ICC, the

terminal performs the CVM if the condition code is satisfied and CVM code is Enciphered PIN verified by ICC. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 22 - Bulletin n°22, Terminal behaviour when data for CVM condition is not known (Apr-2004) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal ([Offline Enciphered PIN] supported AND [Amount known before CVM Configuration: Processing] supported) Conditions:

•


•


•


•


•

Case 01: condition is 'transaction is under X (and Amount is under X)' (04 06)

•

Case 02: condition is 'transaction is over Y (and Amount is over Y)' (04 09)

•

Case 03: condition is 'transaction is over X (and Amount is over X)' (04 07)

•

Case 04: condition is 'transaction is under Y (and Amount is under Y)' (04 08)




2CJ.091.02 Second byte of CVR satisfied and CVM Code is Enciphered PIN verified by ICC (Enciphered PIN verified by ICC supported) (2) Pass Criteria:

•


•


•


•


•



Page 1120


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) Test No: 2CJ.091.03 - Revision 17 - Number of sub cases: 4 Objective: To ensure that if the terminal does not support Enciphered PIN verified

by ICC, the terminal performs the CVM if the condition code is satisfied and CVM code is Enciphered PIN verified by ICC. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal ([Offline Enciphered PIN] not supported AND [Amount known before Configuration: CVM Processing] supported) Conditions:

•


•


•


•


•


•


•


•


Action: NA



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) Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•


•


•



Page 1122


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) Test No: 2CJ.092.00 - Revision 10g - Number of sub cases: 5 Objective: To ensure that if terminal supports Enciphered PIN verified by ICC and

signature, the terminal performs the CVM if the condition code is satisfied and CVM code is Enciphered PIN verified by ICC and Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal ([Offline Enciphered PIN] supported AND [Signature] supported) Configuration: Conditions:

•


•

CVM List is 'Enciphered PIN verified by ICC and signature' with the following conditions satisfied:

•


•

Case 02: ([Unattended] supported AND [Cash] supported) condition is 'unattended cash (Transaction is cash)' (05 01)

•

Case 03: condition is 'not unattended cash and not manual cash, and not purchase with cashback (Transaction is not cash and not purchase with cashback)' (05 02)

•


•





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) Pass Criteria:

•


•


•


•


•



Page 1124


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) Test No: 2CJ.092.01 - Revision 17 - Number of sub cases: 5 Objective: To ensure that if the terminal does not support Enciphered PIN verified

by ICC or signature, the terminal performs the CVM if the condition code is satisfied and CVM code is Enciphered PIN verified by ICC and Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal ([Offline Enciphered PIN] not supported OR [Signature] not supported) Configuration: Conditions:

•


•


•


•


•


•


•

Case 05: condition is ''not unattended cash and not manual cash, and not purchase with cashback' (Transaction is not cash and not purchase with cashback ) (05 02)

Action: NA



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) Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•

TVR byte 3, bit 5 = '1' (ie PIN entry required and PIN pad not present or not working) received at 1st GENERATE AC (only if terminal does not support plaintext PIN and does not support enciphered PIN)

•


•


•



Page 1126


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) Test No: 2CJ.092.02 - Revision 11 - Number of sub cases: 4 Objective: To ensure that if terminal supports Enciphered PIN verified by ICC and

signature, the terminal performs the CVM if the condition code is satisfied and CVM code is Enciphered PIN verified by ICC and Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 22 - Bulletin n°22, Terminal behaviour when data for CVM condition is not known (Apr-2004) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal ([Offline Enciphered PIN] supported AND [Signature] supported AND Configuration: [Amount known before CVM Processing] supported) Conditions:

•


•


•


•


•


•


•


•





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) Pass Criteria:

•


•


•


•


•



Page 1128


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) Test No: 2CJ.092.03 - Revision 17 - Number of sub cases: 4 Objective: To ensure that if the terminal does not support Enciphered PIN verified

by ICC or signature, the terminal performs the CVM if the condition code is satisfied and CVM code is Enciphered PIN verified by ICC and Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal ([Amount known before CVM Processing] supported AND ([Signature] Configuration: not supported OR [Offline Enciphered PIN] not supported)) Conditions:

•


•


•


•


•


•


•


•


Action: NA



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) Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•

TVR byte 3, bit 5 = '1' (ie PIN entry required and PIN pad not present or not working) received at 1st GENERATE AC (only if terminal does not support both plaintext and enciphered PIN)

•


•



Page 1130


2CJ.093.00 Second byte of CVR satisfied and CVM Code is signature (signature supported) Test No: 2CJ.093.00 - Revision 11 - Number of sub cases: 5 Objective: To ensure that if terminal supports signature, the terminal performs the

CVM if the condition code is satisfied and CVM code is Signature. To ensure that the terminal sets the CVM Results byte 3 to 'failed' when the last CVM performed was not considered as successful. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book 4 - Section 6.3.4.5 - CVM Results Terminal [Signature] supported Configuration: Conditions:

•


•

Transaction is processed so the outcome is an Approval

•

CVM List is 'signature' with the following conditions satisfied:

•

Case 01: condition is 'always' (1E 00)

•

Case 02: ([Unattended] supported AND [Cash] supported) condition is 'unattended cash' (Transaction is cash) (1E 01)

•

Case 03: ([Attended] supported AND [Cash] supported) condition is 'If manual cash' (Transaction is cash) (1E 04)

•

Case 04: condition is 'If purchase with cashback' (Transaction is purchase with cashback)' (1E 05)

•

Case 05: condition is 'not unattended cash and not manual cash, and not purchase with cashback' (Transaction is not cash and not purchase with cashback) (1E 02)



2CJ.093.00 Second byte of CVR satisfied and CVM Code is signature (signature supported) Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•

The terminal shall print a ticket with signature line

•


•

CVM Result = (1E xx 00) where xx = number of the CVM condition of the sub case in question.


Page 1132


2CJ.093.01 Second byte of CVR satisfied and CVM Code is signature (signature not supported) Test No: 2CJ.093.01 - Revision 17 - Number of sub cases: 5 Objective: To ensure that if the terminal does not support signature, the terminal

performs the CVM if the condition code is satisfied and CVM code is Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal [Signature] not supported Configuration: Conditions:

•


•


•

Case 01: condition is 'always' (1E 00)

•

Case 02: ([Unattended] supported AND [Cash] supported) condition is 'unattended cash' (Transaction is cash) (1E 01)

•

Case 03: ([Attended] supported AND [Cash] supported) condition is 'If manual cash' (Transaction is cash) (1E 04)

•

Case 04: condition is 'If purchase with cashback' (Transaction is purchase with cashback)' (1E 05)

•

Case 05: condition is 'not unattended cash and not manual cash, and not purchase with cashback' (Transaction is not cash and not purchase with cashback) (1E 02)


•




2CJ.093.01 Second byte of CVR satisfied and CVM Code is signature (signature not supported) requesting a TC or an AAC. •


•


•


•



Page 1134


2CJ.093.02 Second byte of CVR satisfied and CVM Code is signature (signature supported) Test No: 2CJ.093.02 - Revision 11 - Number of sub cases: 4 Objective: To ensure that if terminal supports signature, the terminal performs the

CVM if the condition code is satisfied and CVM code is Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 22 - Bulletin n°22, Terminal behaviour when data for CVM condition is not known (Apr-2004) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal ([Signature] supported AND [Amount known before CVM Processing] Configuration: supported) Conditions:

•


•


•


•

Transaction is processed so the outcome is an Approval

•


•

Case 01: condition is 'transaction is under X (and Amount is under X)' (1E 06)

•

Case 02: condition is 'transaction is over Y (and Amount is over Y)' (1E 09)

•

Case 03: condition is 'transaction is over X (and Amount is over X)' (1E 07)

•

Case 04: condition is 'transaction is under Y (and Amount is under Y)' (1E 08)


•




2CJ.093.02 Second byte of CVR satisfied and CVM Code is signature (signature supported) requesting a TC or an AAC. •

The terminal shall print a ticket with signature line

•


•

CVM Result = (1E xx 00) where xx = number of the CVM condition of the sub case in question.


Page 1136


2CJ.093.03 Second byte of CVR satisfied and CVM Code is signature (signature not supported) Test No: 2CJ.093.03 - Revision 17 - Number of sub cases: 4 Objective: To ensure that if the terminal does not support signature, the terminal

performs the CVM if the condition code is satisfied and CVM code is Signature. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal ([Signature] not supported Configuration: Processing] supported) Conditions:

AND [Amount known before CVM

•


•


•


•


•

Case 01: condition is 'transaction is under X (and Amount is under X)' (1E 06)

•

Case 02: condition is 'transaction is over Y (and Amount is over Y)' (1E 09)

•

Case 03: condition is 'transaction is over X (and Amount is over X)' (1E 07)

•

Case 04: condition is 'transaction is under Y (and Amount is under Y)' (1E 08)




2CJ.093.03 Second byte of CVR satisfied and CVM Code is signature (signature not supported) Pass Criteria:

•


•


•


•



Page 1138


2CJ.094.00 Second byte of CVR satisfied and CVM Code is no CVM required (No CVM required is supported) Test No: 2CJ.094.00 - Revision 10g - Number of sub cases: 5 Objective: To ensure that the CVM is successful when the CVM code is 'No CVM

required' and CVM condition is satisfied Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [NO CVM] supported Configuration: Conditions:

•


•

CVM List is 'No CVM required' with the following conditions satisfied:

•

Case 01: condition is 'always' (1F 00)

•

Case 02: ([Unattended] supported AND [Cash] supported) condition is 'unattended cash' (Transaction is cash) (1F 01)

•

Case 03: ([Attended] supported AND [Cash] supported) condition is 'If manual cash' (Transaction is cash) (1F 04)

•

Case 04: condition is 'If purchase with cashback' (Transaction is purchase with cashback)' (1F 05)

•

Case 05: condition is 'not unattended cash and not manual cash, and not purchase with cashback' (Transaction is not cash and not purchase with cashback) (1F 02)


•




2CJ.094.00 Second byte of CVR satisfied and CVM Code is no CVM required (No CVM required is supported) •


•


•

CVM Result = (1F xx 02) where xx = number of the CVM condition of the sub case in question.


Page 1140


2CJ.094.01 Second byte of CVR satisfied and CVM Code is No CVM required (No CVM required is not supported) Test No: 2CJ.094.01 - Revision 17 - Number of sub cases: 5 Objective: To ensure that if the terminal does not support 'No CVM required', the

terminal considers that the CVM is unsuccessful if the condition code is satisfied and CVM code is 'No CVM Required'. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal [No CVM] not supported Configuration: Conditions:

•


•


•


•

Case 02: ([Unattended] supported AND [Cash] supported) condition is 'unattended cash (Transaction is cash) (1F 01)

•


•


•





2CJ.094.01 Second byte of CVR satisfied and CVM Code is No CVM required (No CVM required is not supported) Pass Criteria:

•


•


•


•


•



Page 1142


2CJ.094.02 Second byte of CVR satisfied and CVM Code is no CVM required (No CVM required is supported) Test No: 2CJ.094.02 - Revision 11 - Number of sub cases: 4 Objective: To ensure that if terminal supports No CVM required, the terminal

considers that the CVM is not successful if the condition code is satisfied and CVM code is 'No CVM Required'. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 22 - Bulletin n°22, Terminal behaviour when data for CVM condition is not known (Apr-2004) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal ([NO CVM] supported AND [Amount known before CVM Processing] Configuration: supported) Conditions:

•


•


•


•


•

Case 01: condition is 'transaction is under X (and Amount is under X)' (1F 06)

•

Case 02: condition is 'transaction is over Y (and Amount is over Y)' (1F 09)

•

Case 03: condition is 'transaction is over X (and Amount is over X)' (1F 07)

•

Case 04: condition is 'transaction is under Y (and Amount is under Y)' (1F 08)


•




2CJ.094.02 Second byte of CVR satisfied and CVM Code is no CVM required (No CVM required is supported) requesting a TC or an AAC. •


•


•

CVM Result = (1F xx 02) where xx = number of the CVM condition of the sub case in question.


Page 1144


2CJ.094.03 Second byte of CVR satisfied and CVM Code is No CVM required (No CVM required is not supported) Test No: 2CJ.094.03 - Revision 17 - Number of sub cases: 4 Objective: To ensure that if the terminal does not support 'No CVM required', the

terminal considers that the CVM is successful if the condition code is satisfied and CVM code is 'No CVM Required'. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal ([No CVM] not supported Configuration: Processing] supported) Conditions:

AND [Amount known before CVM

•


•


•


•


•

Case 01: condition is 'transaction is under X (and Amount is under X)' (1F 06)

•

Case 02: condition is 'transaction is over Y (and Amount is over Y)' (1F 09)

•


•





2CJ.094.03 Second byte of CVR satisfied and CVM Code is No CVM required (No CVM required is not supported) Pass Criteria:

•


•


•


•



Page 1146


2CJ.095.00 Second byte of CVR satisfied and CVM Code not understood by the terminal Test No: 2CJ.095.00 - Revision 17 - Number of sub cases: 10 Objective: To ensure that the terminal sets the 'Unrecognized CVM ' bit in the TVR

to 1b, if the condition code is satisfied and CVM code is not understood by the terminal (RFU) Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:



•


•

CVM List is 'RFU' with the following conditions satisfied:

•


•

Case 02: ([Unattended] supported AND [Cash] supported) condition is 'unattended cash (Transaction is cash)' (3F 01)

•

Case 03: CVM List is 'RFU, always' (07 00)

•


•

Case 05: condition is 'not unattended cash and not manual cash, and not purchase with cashback (Transaction is not cash and not purchase with cashback')' (07 02)

•

Case 06: ([Attended] supported AND [Cash] supported) condition is 'If manual cash (Transaction is cash)' (07 04)

•




2CJ.095.00 Second byte of CVR satisfied and CVM Code not understood by the terminal •

Case 08: condition is 'If purchase with cashback' (and Transaction is purchase with cashback)' (07 05)

•


•



•


•

TVR byte 3, bit 8 = '1' (ie Cardholder verification was not successful

•

TVR byte 3, bit 7 = '1' (ie Unrecognized CVM) received at 1st GENERATE AC.

•


•



Page 1148


2CJ.095.01 Second byte of CVR satisfied and CVM Code not understood by the terminal Test No: 2CJ.095.01 - Revision 17 - Number of sub cases: 4 Objective: To ensure that the terminal sets the 'Unrecognized CVM ' bit in the TVR

to 1b, if the condition code is satisfied and CVM code is not understood by the terminal (RFU) Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal [Amount known before CVM Processing] supported Configuration: Conditions:

•


•


•


•

CVM List is 'RFU' with the following conditions satisfied:

•


•


•


•





2CJ.095.01 Second byte of CVR satisfied and CVM Code not understood by the terminal Pass Criteria:

•


•

TVR byte 3, bit 7 = '1' (ie Unrecognized CVM) received at 1st GENERATE AC.

•


•


•



Page 1150


2CJ.096.00 CVM processing succeeds Test No: 2CJ.096.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal does not set the 'Cardholder verification

was not successful' bit in the TVR to 1b, if the CVM processing succeeds. To ensure that the terminal sets the 'Cardholder verification was performed' bit in the TSI to 1b, if the Cardholder verification process is performed (successful or not) Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Offline Plaintext Configuration: supported Conditions:

PIN] supported OR [Offline Enciphered PIN]

•


•

CVM List is 'Plaintext PIN verification performed by ICC if Terminal supports the CVM' (01 03) followed by ‘Enciphered Offline PIN verification performed by ICC if Terminal supports the CVM’ (04 03)

Action: Correct PIN Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•


•

CVM Result = (xx 03 02) where xx correspond to the CVM performed



2CJ.096.01 CVM processing succeeds (2) Test No: 2CJ.096.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal does not set the 'Cardholder verification

was not successful' bit in the TVR to 1b, if the CVM processing succeeds. To ensure that the terminal sets the 'Cardholder verification was performed' bit in the TSI to 1b, if the Cardholder verification process is performed (successful or not) Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Online Enciphered PIN] supported OR [Signature] supported Configuration: Conditions:

•


•

CVM List is 'Enciphered Online PIN if Terminal supports the CVM' (02 03) followed by 'Signature, always' (1E 00)


•


•


•


•

When processing Online Enciphered PIN, CVM Result = 02 03 00

•

When processing Signature, CVM Result = 1E 00 00.


Page 1152


2CJ.096.02 CVM processing succeeds (3) Test No: 2CJ.096.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal does not set the 'Cardholder verification

was not successful' bit in the TVR to 1b, if the CVM processing succeeds. To ensure that the terminal sets the 'Cardholder verification was performed' bit in the TSI to 1b, if the Cardholder verification process is performed (successful or not) Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [No CVM] Configuration: Conditions:

•


•

CVM List is 'No CVM, always' (1F 00)


•


•


•


•

CVM Result = (1F 00 02)



2CJ.097.00 CVM processing fails and CVR indicates to proceed with next rule Test No: 2CJ.097.00 - Revision 11 - Number of sub cases: 3 Objective: To ensure that the terminal processes next CVR in the CVM List, if the

current one is not successful and the 'Apply succeeding Cardholder Verification Rule if this CVM is unsuccessful' bit is set to 1b Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal NA Configuration: Conditions:

•


•

Case 01: CVM in LT is 'Plaintext PIN verification performed by ICC, Always' (41 00) followed by 'Fail CVM, always' (00 00). When terminal support Offline PIN, PIN is wrongly presented.

•

Case 02: [Signature] not supported - CVM in LT is 'Signature, Always' (5E 00) followed by 'Fail CVM, always' (00 00).

•

Case 03: [Onfline Enciphered PIN] not supported - CVM in LT is 'Online PIN, Always' (42 00) followed by 'Fail CVM, always' (00 00)


•


•

TVR byte 3, bit 8 = '1' (ie Cardholder verification unsuccessful) received at 1st GENERATE AC.

•


•

CVM Result = (00 00 01)


Page 1154


2CJ.098.00 CVM processing fails and no more CVRs in the CVM List Test No: 2CJ.098.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal fails the Cardholder verification and sets

the 'Cardholder verification was not successful' bit in the TVR to 1b, if a CVM processing fails, the 'Apply succeeding Cardholder Verification Rule if this CVM is unsuccessful' bit is set to 1b, and there are no more Cardholder Verification Rules in the CVM List. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal NA Configuration: Conditions:

•


•

Case 01: CVM in LT is 'Plaintext PIN verification performed by ICC, always' (41 00). If terminal support offline PIN, when PIN is wrongly entered

•

Case 02: CVM in LT is 'Fail CVM, always' (40 00)


•


•


•


•

CVM Result = (xx 00 01) where xx is 41 for subcase 01 and 40 for subcase 02



2CJ.099.00 CVM processing fails and CVR indicates to not proceed with next rule Test No: 2CJ.099.00 - Revision 13 - Number of sub cases: 3 Objective: To ensure that the terminal fails the Cardholder verification and sets

the 'Cardholder verification was not successful' bit in the TVR to 1b, if a CVM processing fails, and the 'Apply succeeding Cardholder Verification Rule if this CVM is unsuccessful' bit is not set to 1b. To ensure that if the CVM List is present in the ICC, the terminal processes each rule in the order in which it appears in the CVM List, until the cardholder verification process is completed. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal NA Configuration: Conditions:

•


•

Case 01: [Offline Plaintext PIN] supported - CVM in LT is 'Plaintext PIN verification performed by ICC if Terminal supports the CVM' ('Apply succeeding Cardholder Verification Rule if this CVM is unsuccessful' bit is not set to 1b) (01 03) followed by 'No CVM, always' (1F 00), Wrong PIN presented

•

Case 02: [Signature] not supported AND [Amount known before CVM processing] supported - CVM in LT is 'Signature, Always’ (‘Apply succeding Cardholder Verification Rule if this CVM is unsuccessful’ bit is not set to 1b) (1E 00) followed by 'No CVM required, if transaction is under X' (1F 06)

•

Case 03: CVM in LT is 'Fail CVM, Always' (00 00) followed by 'Signature, always' (1E 00)


•


•

TVR byte 3, bit 8 = '1' (ie Cardholder verification was not


Page 1156


2CJ.099.00 CVM processing fails and CVR indicates to not proceed with next rule successful) received at 1st GENERATE AC. •


•

CVM Result = (xx xx 01) where xx = number of the CVM condition of the sub case in question.



2CJ.100.00 Non Supported CVR condition: If unattended Cash and transaction is not cash Test No: 2CJ.100.00 - Revision 10g - Number of sub cases: 8 Objective: To ensure that terminal processes the next CVM in the list when the

CVM condition is 'If unattended cash' when transaction is not cash. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal NA Configuration: Conditions:

•


•

CVM in LT is 'Fail CVM If unattended cash' (00 01) followed by 'Fail CVM, always' (00 00).

•

Case 01: [Goods] supported - Transaction is goods

•

Case 02: [Services] supported - Transaction is services

•

Case 03: [CashBack] supported - Transaction is cashback

•

Case 04: Transaction is Inquiry and terminal supports Inquiry transaction

•

Case 05: Transaction is transfer and terminal supports transfer transaction

•

Case 06: Transaction is payment and terminal supports payment transaction

•

Case 07: Transaction is administrative and terminal supports administrative transaction

•

Case 08: Transaction is cash deposit and terminal supports cash deposit transaction


•



Page 1158


2CJ.100.00 Non Supported CVR condition: If unattended Cash and transaction is not cash requesting a TC or an AAC. •


•

CVM Results show 'Fail CVM, always, process is failed' as the last CVM processed (00 00 01)

•




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 Test No: 2CJ.100.01 - Revision 10g - Number of sub cases: 3 Objective: To ensure that terminal processes the next CVM in the list when the

CVM condition is 'If not unattended Cash and not manual cash and not purchase with cashback', when transaction is unattended cash. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Cash] supported OR [Cashback] supported Configuration: Conditions:

•


•

CVM in LT is 'Fail CVM If not unattended Cash and not manual cash and not purchase with cashback' (00 02) followed by 'Fail CVM, always' (00 00).

•

Case 01: ([Unattended] supported AND [Cash] supported) Transaction is cash

•

Case 02: ([Attended] supported AND [Cash] supported) Transaction is cash

•



•


•


•



Page 1160


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 •




2CJ.100.02 Non Supported CVR condition: If manual cash, and transaction is not manual cash Test No: 2CJ.100.02 - Revision 10g - Number of sub cases: 8 Objective: To ensure that terminal processes the next CVM in the list when the

CVM condition is 'If manual cash' when transaction is not manual cash. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Attended] supported Configuration: Conditions:

•


•

CVM in LT is 'Fail CVM If manual cash' (00 04) followed by 'Fail CVM, always' (00 00).

•


•


•


•

Case 04: Transaction is Inquiry and terminal supports Inquiry transaction

•

Case 05: Transaction is Transfer and terminal supports transfer transaction

•


•


•




Page 1162


2CJ.100.02 Non Supported CVR condition: If manual cash, and transaction is not manual cash Pass Criteria:

•


•


•


•




2CJ.100.03 Non Supported CVR condition: If purchase with cashback, and transaction is not purchase with cashback Test No: 2CJ.100.03 - Revision 10g - Number of sub cases: 8 Objective: To ensure that terminal processes the next CVM in the list when the

CVM condition is 'If purchase with cashback' when transaction is not purchase with cashback Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:


•


•

CVM in LT is 'Fail CVM If purchase with cashback' (00 05) followed by 'Fail CVM, always' (00 00).

•

Case 01: [Cash] supported - Transaction is cash

•


•


•

Case 04: Transaction is inquiry and terminal supports inquiry transaction

•

Case 05: Transaction is transfer and terminal supports transfer transaction

•


•


•


Action: NA


Page 1164


2CJ.100.03 Non Supported CVR condition: If purchase with cashback, and transaction is not purchase with cashback Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•


•




2CJ.100.04 Non Supported CVR condition: If unattended Cash and transaction is not cash Test No: 2CJ.100.04 - Revision 13 - Number of sub cases: 2 Objective: To ensure that terminal processes the next CVM in the list when the

CVM condition is 'If unattended cash' when transaction type is not cash. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Attended] supported Configuration: Conditions:

•


•

CVM in LT is 'Fail CVM If unattended cash' (00 01) followed by 'Fail CVM, always' (00 00).

•

Case 01: Transaction type is not cash.

•

Case 02: [Cash] supported and Transaction type is cash.


•


•


•


•



Page 1166


2CJ.100.05 Non Supported CVR condition: If manual cash, and transaction is not manual cash Test No: 2CJ.100.05 - Revision 13 - Number of sub cases: 0 Objective: To ensure that terminal processes the next CVM in the list when the

CVM condition is 'If manual cash' when transaction type is not manual cash. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0:

Book Bulletins - Section SU 16 - Bulletin n°16, Enhancement to If Cash or Cashback CVM Condition Code (Dec-2003) Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal [Unattended] supported Configuration: Conditions:

•


•

CVM in LT is 'Fail CVM If manual cash' (00 04) followed by 'Fail CVM, always' (00 00).

•

Case 01: Transaction type is not cash.

•

Case 02: [Cash] supported and Transaction type is cash.


•


•


•


•




2CJ.103.00 Offline PIN is the selected CVM and Terminal does not support offline PIN Test No: 2CJ.103.00 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal sets the 'PIN entry required and PIN pad

not present or not working' bit in the TVR to 1b, if an offline PIN is the selected CVM and the terminal does not support offline plaintext PIN verification and offline Enciphered PIN. Reference Book 3 - Section 6.5.1 - Offline PIN Processing EMV 4.0: Reference Book 3 - Section 10.5.1 - Offline PIN Processing EMV 4.1: Terminal ([Offline Plaintext PIN] not supported AND [Offline Enciphered PIN] not Configuration: supported) Conditions:

•


•

Case 01: CVM List is 'Plaintext PIN verified by ICC, always' (01 00)

•

Case 02: CVM List is 'Enciphered Offline PIN verified by ICC, always' (04 00)


•


•


•


•



Page 1168


2CJ.103.01 Offline PIN is the selected CVM and Terminal does not support offline PIN (2) Test No: 2CJ.103.01 - Revision 17 - Number of sub cases: 0 Objective: To ensure that the terminal does not set the 'PIN entry required and

PIN pad not present or not working' bit in the TVR to 1b, if offline plaintext PIN is the selected CVM and the terminal does not support offline plaintext PIN verification but supports offline enciphered PIN Reference Book 3 - Section 6.5.1 - Offline PIN Processing EMV 4.0: Reference Book 3 - Section 10.5.1 - Offline PIN Processing EMV 4.1:

Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal ([Offline Plaintext PIN] not supported AND [Offline Enciphered PIN] Configuration: supported) Conditions:

•


•

CVM List is 'plaintext Offline PIN verified by ICC, always' (01 00)


•


•


•

TVR byte 3, bit 5 = '0' (ie PIN entry required and PIN pad not present is not set) received at 1st GENERATE AC.

•


•




2CJ.103.02 Offline PIN is the selected CVM and Terminal does not support offline PIN (3) Test No: 2CJ.103.02 - Revision 17 - Number of sub cases: 0 Objective: To ensure that the terminal does not set the 'PIN entry required and

PIN pad not present or not working' bit in the TVR to 1b, if offline enciphered PIN is the selected CVM and the terminal does not support offline enciphered PIN verification but supports offline plaintext PIN Reference Book 3 - Section 6.5.1 - Offline PIN Processing EMV 4.0: Reference Book 3 - Section 10.5.1 - Offline PIN Processing EMV 4.1:

Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal ([Offline Plaintext PIN] supported AND [Offline Enciphered PIN] not Configuration: supported) Conditions:

•


•

CVM List is 'enciphered Offline PIN verified by ICC, always' (04 00)


•


•


•

TVR byte 3, bit 5 = '0' (ie PIN entry required and PIN pad not present is not set) received at 1st GENERATE AC.

•


•



Page 1170


2CJ.107.00 Offline PIN is the selected CVM and the number of remaining PIN trials is zero Test No: 2CJ.107.00 - Revision 10g - Number of sub cases: 0 Objective: 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 number of remaining PIN trials is reduced to zero upon initial use of the VERIFY command (ie the status code is '63C0') Reference Book 3 - Section 6.5.1 - Offline PIN Processing EMV 4.0: Reference Book 3 - Section 10.5.1 - Offline PIN Processing EMV 4.1: Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•


•

CVM List is 'Plaintext PIN verified by ICC, always' (01 00)

•

LT returns '63C0' to VERIFY command.


•


•


•

TVR byte 3, bit 6 = '1' (ie PIN Try Limit exceeded) received at 1st GENERATE AC.

•


•




2CJ.107.01 Offline PIN is the selected CVM and the number of remaining PIN trials is zero (2) Test No: 2CJ.107.01 - Revision 10g - Number of sub cases: 0 Objective: 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 number of remaining PIN trials is reduced to zero upon initial use of the VERIFY command (ie the status code is '63C0') Reference Book 3 - Section 6.5.1 - Offline PIN Processing EMV 4.0: Reference Book 3 - Section 10.5.1 - Offline PIN Processing EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

CVM List is 'Enciphered PIN verified by ICC, always' (04 00)

•

LT returns '63C0' to VERIFY command.


•


•


•


•


•



Page 1172


2CJ.108.00 Offline PIN is the selected CVM and the offline PIN processing is successful Test No: 2CJ.108.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal considers the CVM as successful, if an

offline PIN is the selected CVM and VERIFY command returns 90 00. To ensure that the terminal sets byte 3 of the CVM Result to successful, if offline PIN verification by the ICC is successful. To ensure that the terminal is able to recognize the absence of returned Data field in the VERIFY command. Reference Book 3 - Section 2.3.5 - Coding of the Status Bytes EMV 4.0:

Book 3 - Section 2.5.12.4 - Data Field Returned in the Response Message Book 3 - Section 6.5.1 - Offline PIN Processing Book 4 - Section 2.3.4.1 - Offline CVM Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1:

Book 3 - Section 6.5.12.4 - Data Field Returned in the Response Message Book 3 - Section 10.5.1 - Offline PIN Processing Book 4 - Section 6.3.4.1 - Offline CVM Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•


•

CVM List is 'Plaintext PIN verified by ICC, always' (01 00)

•

LT returns '90 00' to VERIFY command.


•




2CJ.108.00 Offline PIN is the selected CVM and the offline PIN processing is successful requesting a TC or an AAC. •

The terminal shall accept the VERIFY response message with the non presence of the returned data field.

•


•

TVR byte 3, bit 6 = '0' (ie PIN Try limit not exceeded) received at 1st GENERATE AC.

•

TVR byte 3, bit 5 = '0' (ie PIN Entry required and PIN pad present) received at 1st GENERATE AC.

•

TVR byte 3, bit 4 = '0' (ie PIN entered) received at 1st GENERATE AC.

•


•



Page 1174


2CJ.108.01 Offline PIN is the selected CVM and the offline PIN processing is successful (2) Test No: 2CJ.108.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal considers the CVM as successful, if an

offline PIN is the selected CVM and VERIFY command returns 90 00 To ensure that the terminal sets byte 3 of the CVM Result to successful, if offline PIN verification by the ICC is successful. To ensure that the terminal is able to recognize the absence of returned Data field in the VERIFY command. Reference Book 3 - Section 2.3.5 - Coding of the Status Bytes EMV 4.0:

Book 3 - Section 2.5.12.4 - Data Field Returned in the Response Message Book 3 - Section 6.5.1 - Offline PIN Processing Reference Book 3 - Section 6.3.5 - Coding of the Status Bytes EMV 4.1:

Book 3 - Section 6.5.12.4 - Data Field Returned in the Response Message Book 3 - Section 10.5.1 - Offline PIN Processing Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

CVM List is 'Enciphered PIN verified by ICC, always' (04 00)

•

LT returns '90 00' to VERIFY command.


•


•

The terminal shall accept the VERIFY response message with the non presence of the returned data field.



2CJ.108.01 Offline PIN is the selected CVM and the offline PIN processing is successful (2) •


•

TVR byte 3, bit 6 = '0' (ie PIN Try limit not exceeded) received at 1st GENERATE AC.

•

TVR byte 3, bit 5 = '0' (ie PIN Entry required and PIN pad present) received at 1st GENERATE AC.

•

TVR byte 3, bit 4 = '0' (ie PIN entered) received at 1st GENERATE AC.

•


•



Page 1176


2CJ.109.00 Online PIN is the selected CVM and Terminal does not support online PIN Test No: 2CJ.109.00 - Revision 17 - Number of sub cases: 0 Objective: To ensure that the terminal sets the 'PIN entry required and PIN pad

not present or not working' bit in the TVR to 1b, if enciphered PIN verified online is the selected CVM and the terminal does not support enciphered PIN verified online. Reference Book 3 - Section 6.5.2 - Online PIN Processing EMV 4.0: Reference Book 3 - Section 10.5.2 - Online PIN Processing EMV 4.1:

Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal [Online Enciphered PIN] not supported Configuration: Conditions:

•


•

CVM List is 'Enciphered PIN verified online, always' (02 00)


•


•


•


•


•


•




2CJ.112.00 Online PIN is the selected CVM and the online PIN processing is successful Test No: 2CJ.112.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal considers the CVM as successful, if

enciphered PIN verified online is the selected CVM and Issuer answered that PIN presented is good. To ensure that the PIN Pad enciphers the PIN upon entry for transmission in the authorization or financial transaction, if CVM is online PIN verification. To ensure that the terminal sets the CVM Results byte 3 to 'unknown' when PIN is entered for online verification. Reference Book 3 - Section 6.5.2 - Online PIN Processing EMV 4.0:

Book 4 - Section 2.3.4.2 - Online CVM Reference Book 3 - Section 10.5.2 - Online PIN Processing EMV 4.1:

Book 4 - Section 6.3.4.2 - Online CVM Terminal [Online Enciphered PIN] supported Configuration: Conditions:

•


•

CVM List is 'Enciphered PIN verified online, always' (02 00)

•

Issuer returns an acceptance


•


•


•


•



Page 1178


2CJ.112.00 Online PIN is the selected CVM and the online PIN processing is successful •


•

Authorization or financial request message shall contain encrypted PIN



2CJ.113.00 Signature (paper) is a required CVM and Terminal supports the signature process - CVM is Set to 'unknown' When Signature is Used Test No: 2CJ.113.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal considers the CVM as successful, if

signature is the selected CVM and terminal supports the signature process. To ensure that the terminal sets the CVM Results byte 3 to 'unknown' when signature is the applicable CVM. Reference Book 3 - Section 6.5.3 - Signature Processing EMV 4.0:

Book 4 - Section 2.3.4.4 - Signature (Paper) Reference Book 3 - Section 10.5.3 - Signature Processing EMV 4.1:

Book 4 - Section 6.3.4.4 - Signature (Paper) Terminal [Signature] supported Configuration: Conditions:

•


•

CVM List is 'signature, always' (1E 00)


•


•


•


•

CVM Result = 1E 00 00


Page 1180


2CJ.114.00 Combination CVM: success Test No: 2CJ.114.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if a CVM requires multiple verification methods (for

example, offline PIN plus signature), the terminal considers the CVM as successful, if all methods in the CVM are successful. Reference Book 3 - Section 6.5.4 - Combination CVMs EMV 4.0: Reference Book 3 - Section 10.5.4 - Combination CVMs EMV 4.1: Terminal ([Offline Plaintext PIN] supported AND [Signature] supported) Configuration: Conditions:

•


•

CVM List is 'Plaintext PIN verified by ICC plus signature, always' (03 00)


•


•


•


•




2CJ.114.01 Combination CVM: success (2) Test No: 2CJ.114.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if a CVM requires multiple verification methods (for

example, offline PIN plus signature), the terminal considers the CVM as successful, if all methods in the CVM are successful. Reference Book 3 - Section 6.5.4 - Combination CVMs EMV 4.0: Reference Book 3 - Section 10.5.4 - Combination CVMs EMV 4.1: Terminal ([Offline Enciphered PIN] supported AND [Signature] supported) Configuration: Conditions:

•


•

CVM List is 'Enciphered PIN verified by ICC plus signature, always' (05 00)


•


•


•


•



Page 1182


2CJ.115.00 Combination CVM: failure Test No: 2CJ.115.00 - Revision 17 - Number of sub cases: 2 Objective: To ensure that if a CVM requires multiple verification methods (for

example, offline PIN plus signature), the terminal considers the CVM as failed, if one of the methods in the CVM fails. Reference Book 3 - Section 6.5.4 - Combination CVMs EMV 4.0: Reference Book 3 - Section 10.5.4 - Combination CVMs EMV 4.1:

Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•


•

CVM List is 'Plaintext PIN verified by ICC plus signature, always' (03 00)

•

Case 01: [Signature] supported - PIN entered is not good

•

Case 02: [Signature] not supported - PIN entered is good


•


•


•


•

Case 01: CVM Result = 03 00 01

•

Case 02: CVM Result = 3F 00 01



2CJ.115.01 Multiple CVR entries when at least one is supported Test No: 2CJ.115.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal processes the first CVM code supported in

the list when the CVM list contains several entries in which at least one is supported. Reference Book 3 - Section 6.5 - Cardholder Verification EMV 4.0: Reference Book 3 - Section 10.5 - Cardholder Verification EMV 4.1: Terminal NA Configuration: Conditions:

•


•

CVM list contains at least 10 entries including the following:

- Enciphered PIN verified online if terminal supports the CVM (02 03) - Enciphered PIN verified by ICC if terminal supports the CVM (04 03) - Plaintext PIN verification performed by ICC if terminal supports the CVM (01 03) - Signature if terminal supports the CVM (1E 03) - NO CVM if terminal supports the CVM (1F 03) •


•

CVM selected is performed successfully


•


•

TVR byte 3, bit 8 = ‘0’ (ie Cardholder verification successful) received at 1st GENERATE AC.

•

CVM Results reflect the first supported CVM for the first two bytes and for the last byte: if signature or online PIN = “00”,


Page 1184


2CJ.115.01 Multiple CVR entries when at least one is supported anything else = “02” •




2CJ.115.02 Combination CVM: failure (2) Test No: 2CJ.115.02 - Revision 11 - Number of sub cases: 2 Objective: To ensure that if a CVM requires multiple verification methods (for

example, offline PIN plus signature), the terminal considers the CVM as failed, if one of the methods in the CVM fails. Reference Book 3 - Section 6.5.4 - Combination CVMs EMV 4.0: Reference Book 3 - Section 10.5.4 - Combination CVMs EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

CVM List is 'Enciphered PIN verified by ICC plus signature, always' (05 00)

•

Case 01: [Signature] supported - PIN entered is not good

•

Case 02: [Signature] not supported - PIN entered is good


•


•


•


•



Page 1186


2CJ.116.00 Terminal Risk Management is supported in AIP Test No: 2CJ.116.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that if the card supports Terminal Risk Management, the

terminal performs Risk Management at sometime after Read Application Data and prior to the issuing of the first GENERATE AC command. Reference Book 3 - Section 6.6 - Terminal Risk Management EMV 4.0: Reference Book 3 - Section 10.6 - Terminal Risk Management EMV 4.1: Terminal ([Velocity Checking] supported AND [Floor Limit Checking] supported) Configuration: Conditions:

•


•

Transaction Amount is above Terminal floor Limit

•

Lower and Upper Consecutive Offline Limits are present in the LT.

•

ATC is not returned by GET DATA

•

CDOL1 requests Terminal Floor Limit and Amount Authorized Numeric


•


•

TVR byte 4, bit 8 = '1' (ie Transaction exceeds floor limit) 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.

•

TSI byte 1, bit 4 = '1' (ie Terminal Risk Management was



2CJ.116.00 Terminal Risk Management is supported in AIP performed) received at 1st GENERATE AC. •

TVR byte 2, bit 4 = '0' (ie not a New Card) received at 1st GENERATE AC.

•



Page 1188


2CJ.119.00 Transaction log entry with the same PAN is available and Terminal Floor Limit is exceeded Test No: 2CJ.119.00 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal sets the 'Transaction exceeds floor limit' bit

in the TVR to 1b, if a transaction log entry with the same Application PAN is availables and if the sum of the Amount, Authorized and the Amount stored in the most recent log entry for that PAN is greater than or equal to the Terminal Floor Limit. Reference Book 3 - Section 6.6.1 - Floor Limits EMV 4.0: Reference Book 3 - Section 10.6.1 - Floor Limits EMV 4.1: Terminal ([Floor Limit Checking] supported AND [Transaction Log] supported) Configuration: Conditions:

•


•

Transaction log is available if supported by the terminal with the same PAN as the LT PAN (another transaction has been made with same PAN before with Amount less than Terminal floor Limit)

•

CDOL1 requests Terminal Floor Limit and Amount Authorized

•

Case 01: Sum of Transaction Amount, Authorized and Amount stored in the log is equal to Terminal floor Limit (Amount Authorized can include a cash back amount)

•

Case 02: Sum of Transaction Amount, Authorized and Amount stored in the log is greater than Terminal floor Limit (Amount Authorized can include a cash back amount)


•


•


•

Amount Authorized returned in First GENERATE AC is the



2CJ.119.00 Transaction log entry with the same PAN is available and Terminal Floor Limit is exceeded same as the amount entered and sum of Transaction Amount, Authorized and Amount of previous transaction with same PAN is equal (sub case 01) to or greater than (sub case 02) Terminal floor Limit •



Page 1190


2CJ.120.00 Transaction log entry with the same PAN is available and Terminal Floor Limit is not exceeded (implied) Test No: 2CJ.120.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal does not set the 'Transaction exceeds floor

limit' bit in the TVR to 1b, if a transaction log entry with the same Application PAN is available, and if the sum of the Amount Authorized and the Amount stored in the most recent log entry for that PAN is less than the Terminal Floor Limit. Reference Book 3 - Section 6.6.1 - Floor Limits EMV 4.0: Reference Book 3 - Section 10.6.1 - Floor Limits EMV 4.1: Terminal ([Floor Limit Checking] supported AND [Transaction Log] supported) Configuration: Conditions:

•


•

Transaction log is available if supported by the terminal with the same PAN as the LT PAN (another transaction has been made with same PAN before with Amount less than Terminal floor Limit)

•

Sum of Transaction Amount, Authorized and Amount stored in the log is less than Terminal floor Limit (Amount Authorized can include a cash back amount)

•



•


•

TVR byte 4, bit 8 = '0' (ie Transaction does not exceed floor limit) received at 1st GENERATE AC.

•

Amount Authorized returned in First GENERATE AC is the same as the amount entered and sum of Transaction Amount, Authorized and Amount of previous transaction with same PAN is less than Terminal floor Limit



2CJ.120.00 Transaction log entry with the same PAN is available and Terminal Floor Limit is not exceeded (implied) •



Page 1192


2CJ.123.00 Transaction log is not available and Terminal Floor Limit is exceeded Test No: 2CJ.123.00 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal sets the 'Transaction exceeds floor limit' bit

in the TVR to 1b, if no transaction log is available and if the Amount, Authorized is greater than or equal to the Terminal Floor Limit. Reference Book 3 - Section 6.6.1 - Floor Limits EMV 4.0: Reference Book 3 - Section 10.6.1 - Floor Limits EMV 4.1: Terminal [Floor Limit Checking] supported Configuration: Conditions:

•


•

Transaction log is not available

•


•

Case 01: Transaction Amount, Authorized is equal to Terminal floor Limit (Amount Authorized can include a cash back amount)

•

Case 02: Transaction Amount, Authorized is greater than Terminal floor Limit (Amount Authorized can include a cash back amount)


•


•


•

Amount Authorized returned in First GENERATE AC is the same as the amount entered and Transaction Amount, Authorized is equal to (sub case 01) or greater than (sub case 02) Terminal floor Limit

•




2CJ.123.00 Transaction log is not available and Terminal Floor Limit is exceeded performed) received at 1st GENERATE AC.


Page 1194


2CJ.124.00 Transaction log is not available and Terminal Floor Limit is not exceeded (implied) Test No: 2CJ.124.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal does not set the 'Transaction exceeds floor

limit' bit in the TVR to 1b, if no transaction log is available and if the Amount, Authorized is less than the Terminal Floor Limit. Reference Book 3 - Section 6.6.1 - Floor Limits EMV 4.0: Reference Book 3 - Section 10.6.1 - Floor Limits EMV 4.1: Terminal [Floor Limit Checking] supported Configuration: Conditions:

•


•

Transaction log is not available

•

Transaction Amount, Authorized is less than Terminal floor Limit (Amount Authorized can include a cash back amount)

•



•


•


•

Amount Authorized returned in First GENERATE AC is the same as the amount entered and Transaction Amount, Authorized is less than Terminal floor Limit

•




2CJ.127.00 Transaction log entry with the same PAN is not available and Terminal Floor Limit is exceeded Test No: 2CJ.127.00 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal sets the 'Transaction exceeds floor limit' bit

in the TVR to 1b, if no transaction log with the same PAN is available and if the Amount, Authorized is greater than or equal to the Terminal Floor Limit. Reference Book 3 - Section 6.6.1 - Floor Limits EMV 4.0: Reference Book 3 - Section 10.6.1 - Floor Limits EMV 4.1: Terminal [Floor Limit Checking] supported Configuration: Conditions:

•


•

Transaction log is not available for same PAN (another transaction as been made with another PAN before with Amount less than Terminal floor Limit)

•


•

Case 01: Transaction Amount, Authorized is equal to Terminal floor Limit (Amount Authorized can include a cash back amount)

•

Case 02: Transaction Amount, Authorized is greater than Terminal floor Limit (Amount Authorized can include a cash back amount)


•


•


•

Amount Authorized returned in First GENERATE AC is the same as the amount entered and Transaction Amount, Authorized is equal to (sub case 01) or greater than (sub case 02) Terminal floor Limit

•



Page 1196


2CJ.127.00 Transaction log entry with the same PAN is not available and Terminal Floor Limit is exceeded performed) received at 1st GENERATE AC.



2CJ.128.00 Transaction log entry with the same PAN is not available and Terminal Floor Limit is not exceeded (implied) Test No: 2CJ.128.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal does not set the 'Transaction exceeds floor

limit' bit in the TVR to 1b, if no transaction log with the same PAN is available and if the Amount, Authorized is less than the Terminal Floor Limit. Reference Book 3 - Section 6.6.1 - Floor Limits EMV 4.0: Reference Book 3 - Section 10.6.1 - Floor Limits EMV 4.1: Terminal [Floor Limit Checking] supported Configuration: Conditions:

•


•

Transaction log is not available for same PAN (another transaction has been made with another PAN before with Amount less than Terminal floor Limit)

•

Transaction Amount, Authorized is less than Terminal floor Limit (Amount Authorized can include a cash back amount)

•



•


•


•

Amount Authorized returned in First GENERATE AC is the same as the amount entered and Transaction Amount, Authorized is less than Terminal floor Limit

•



Page 1198


2CJ.137.00 Both the Lower and the Upper Consecutive Offline Limit are present in the ICC Test No: 2CJ.137.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if Lower and Upper Consecutive Offline Limits are

present in the card, the terminal performs velocity checking. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0: Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•


•

GET DATA returns status word ‘6A 88’, data not present for the ATC


•


•


•


•

TVR byte 2, bit 4 = '0' (ie not a New Card) received at 1st GENERATE AC.

•




2CJ.138.00 Lower Consecutive Offline Limit is not present in the ICC Test No: 2CJ.138.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if either Lower or Upper Consecutive Offline Limits is

absent in the card, the terminal does not perform velocity checking. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0: Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•

Lower Consecutive Offline Limit is absent in the LT.


•


•

TVR byte 4, bit 7 = '0' (ie Lower Consecutive Offline Limit not exceeded) received at 1st GENERATE AC.

•

TVR byte 4, bit 6 = '0' (ie Upper Consecutive Offline Limit not exceeded) received at 1st GENERATE AC.

•

The terminal shall not issue the GET DATA command for the ATC or the LOATC


Page 1200


2CJ.138.01 Upper Consecutive Offline Limit is not present in the ICC Test No: 2CJ.138.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if either Lower or Upper Consecutive Offline Limits is

absent in the card, the terminal does not perform velocity checking. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0: Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•

Upper Consecutive Offline Limit is absent in the LT.


•


•


•


•

The terminal shall not issue the GET DATA command for the ATC or the LOATC



2CJ.139.00 GET DATA on both the ATC and the Last Online ATC Register Test No: 2CJ.139.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if terminal performs velocity checking, it reads the ATC

and Last online ATC using GET DATA command. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0: Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•



•


•

LT shall receive 2 GET DATAs command for ATC and Last Online ATC


Page 1202


2CJ.140.00 The ATC Register is not present in the ICC Test No: 2CJ.140.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure when the ATC is not returned by the card in response to the

GET DATA command, the terminal sets both the 'Lower consecutive offline limit exceeded' and the 'Upper consecutive offline limit exceeded' bits in the TVR to 1b and does not set the 'New Card' bit in the TVR to 1b. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0:

Book Bulletins - Section SU 18 - Bulletin n°18, Velocity Checking Modification (Apr-2004) Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•


•


•

If returned, Last Online ATC is greater than 0


•


•


•


•

TVR byte 2, bit 4 = '0' (ie not a new card) received at 1st GENERATE AC.

•

TVR byte 1, bit 6 = '1' (ie ICC Data missing) received at 1st



2CJ.140.00 The ATC Register is not present in the ICC GENERATE AC.


Page 1204


2CJ.140.01 The Last Online ATC Register is not present in the ICC LATC > 0 Test No: 2CJ.140.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Last Online ATC is not returned by the card in

response to the GET DATA command, the terminal sets both the 'Lower consecutive offline limit exceeded' and the 'Upper consecutive offline limit exceeded' bits in the TVR to 1b and does not set the 'New Card' bit in the TVR to 1b. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0: Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•


•

GET DATA returns status word ‘6A 88’, data not present for the Last Online ATC


•


•


•


•


•




2CJ.140.02 The ATC Register is less than the Last online ATC Test No: 2CJ.140.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the ATC is less than to Last Online ATC, the terminal

sets both the ‘Lower consecutive offline limit exceeded’ and the ‘Upper consecutiveoffline limit exceeded’ bits in the TVR to 1b and does not set the ‘New Card’ bit in the TVR to 1b. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0:


•


•


•

Last Online ATC found in the LT is 'FF FF'

•

ATC found in LT is '00 00'


•


•


•


•



Page 1206


2CJ.140.03 The ATC Register is equal than to Last online ATC Test No: 2CJ.140.03 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the ATC is equal to to Last Online ATC, the terminal

sets both the ‘Lower consecutive offline limit exceeded’ and the ‘Upper consecutiveoffline limit exceeded’ bits in the TVR to 1b and does not set the ‘New Card’ bit in the TVR to 1b. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0:


•


•


•

Last Online ATC found in the LT is 'FF FF'

•

ATC found in LT is 'FF FF''


•


•


•


•




2CJ.140.04 The ATC Register is not present in the ICC – LATC = 0 Test No: 2CJ.140.04 - Revision 12 - Number of sub cases: 0 Objective: To ensure that if the ATC is not returned by the card in response to the

GET DATA command, the terminal sets both the ’Lower consecutive offline limit exceeded’ and the ‘Upper consecutive offline limit exceeded’ bits in the TVR to 1b and sets the ‘New Card’ bit in the TVR to 1b (LATC = 0). Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0:


•


•


•

Last Online ATC found in the LT is '00 00'

•



•


•


•


•

If Last Online ATC is recovered via GET DATA, TVR byte 2, bit 4 = '1' (ie new card) received at 1st GENERATE AC.

•



Page 1208




2CJ.141.00 (ATC - Last Online ATC Register) > Lower Consecutive Offline Limit Test No: 2CJ.141.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the difference between the ATC and the Last Online

ATC Register is greater than the Lower Consecutive Offline Limit, the terminal sets the 'Lower consecutive offline limit exceeded' bit in the TVR to 1b. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0: Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•


•

ATC and Last Online ATC are returned by GET DATA

•

ATC - Last Online ATC > Lower Consecutive Offline Limit


•


•



Page 1210


2CJ.142.00 (ATC - Last Online ATC Register) = Lower Consecutive Offline Limit (implied) Test No: 2CJ.142.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the difference between the ATC and the Last Online

ATC Register is equal to the Lower Consecutive Offline Limit, the terminal does not set the 'Lower consecutive offline limit exceeded' bit in the TVR to 1b. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0: Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•


•


•

ATC - Last Online ATC = Lower Consecutive Offline Limit


•


•




2CJ.143.00 (ATC - Last Online ATC Register) < Lower Consecutive Offline Limit (implied) Test No: 2CJ.143.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the difference between the ATC and the Last Online

ATC Register is less than the Lower Consecutive Offline Limit, the terminal does not set the 'Lower consecutive offline limit exceeded' bit in the TVR to 1b. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0: Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•


•


•

ATC - Last Online ATC < Lower Consecutive Offline Limit


•


•



Page 1212


2CJ.144.00 (ATC - Last Online ATC Register) > Upper Consecutive Offline Limit Test No: 2CJ.144.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the difference between the ATC and the Last Online

ATC Register is greater than the Upper Consecutive Offline Limit, the terminal sets the 'Upper consecutive offline limit exceeded' bit in the TVR to 1b. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0: Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•


•


•

ATC - Last Online ATC > Upper Consecutive Offline Limit


•


•




2CJ.145.00 (ATC - Last Online ATC Register) = Upper Consecutive Offline Limit (implied) Test No: 2CJ.145.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the difference between the ATC and the Last Online

ATC Register is equal to the Upper Consecutive Offline Limit, the terminal does not set the 'Upper consecutive offline limit exceeded' bit in the TVR to 1b. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0: Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•


•


•

ATC - Last Online ATC = Upper Consecutive Offline Limit


•


•



Page 1214


2CJ.146.00 TC - Last Online ATC Register) < Upper Consecutive Offline Limit (implied) Test No: 2CJ.146.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the difference between the ATC and the Last Online

ATC Register is less than the Upper Consecutive Offline Limit, the terminal does not set the 'Upper consecutive offline limit exceeded' bit in the TVR to 1b. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0: Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•


•


•

ATC - Last Online ATC < Upper Consecutive Offline Limit


•


•




2CJ.147.00 Last Online ATC Register = 0 Test No: 2CJ.147.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the Last Online ATC is equal to 0, the terminal sets

the 'New card' bit in the TVR to 1b. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0: Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•


•


•


•

Last Online ATC when returned by GET DATA have the value = 0


•


•

TVR byte 2, bit 4 = '1' (ie New Card) received at 1st GENERATE AC.


Page 1216


2CJ.147.01 ATC and Last Online ATC Register = 0 Test No: 2CJ.147.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the ATC and Last Online ATC are equal to 0, the

terminal sets the 'New card' bit in the TVR to 1b. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0:


•


•


•


•

ATC and Last Online ATC = 0


•


•

TVR byte 2, bit 4 = '1' (ie New Card) received at 1st GENERATE AC.

•


•




2CJ.148.00 Terminal Risk Management completion Test No: 2CJ.148.00 – Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal sets the 'Terminal Risk Management was

performed' bit in the TSI to 1b, when the Terminal Risk management is completed. Reference Book 3 - Section 6.6.3 - Velocity Checking EMV 4.0: Reference Book 3 - Section 10.6.3 - Velocity Checking EMV 4.1: Terminal (([Velocity Checking] supported OR [Floor Limit Checking] supported) Configuration: OR [Random Transaction Selection] supported) Conditions:

•


•

Terminal Supports minimum of one form of Terminal Risk Management:

- Floor Limit Checking - Random Transaction Selection - Velocity Checking •


•


•

Lower and Upper Consecutive Offline Limits are greater than ATC - Last Online ATC


•


•

TSI byte 1, bit 4 = '1' (ie Terminal Risk Management was performed,received at 1st GENERATE AC.

•


•

TVR byte 4, bit 7 = '0' (ie Lower Consecutive Offline Limit not


Page 1218


2CJ.148.00 Terminal Risk Management completion exceeded) received at 1st GENERATE AC.



2CJ.150.00 TAC Denial processing bit set to 1b Test No: 2CJ.150.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal issues a GENERATE AC requesting an

AAC, if for a bit set to 1b in the TVR, the corresponding bit in the TAC Denial is set to 1b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal Configuration:

Conditions:

•

Terminal Action Code Denial has one bit set to 1b and the corresponding TVR bit is set to 1b.

•

Terminal Action Code Default has all bits set to 0b.

•

Issuer Action Codes have all bits set to 0b.

•

AIP of LT must be set to execute the function associated with the TAC bit selected by tester and the LT will be set so the executed function will fail


•


•

The LT shall receive a first GENERATE AC command requesting an AAC in all cases


Page 1220


2CJ.151.00 TAC Denial processing bit set to 0b Test No: 2CJ.151.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal issues a GENERATE AC requesting a TC,

if for a bit set to 1b in the TVR, the corresponding bit in the TAC Denial is set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline Only or Offline/Online capable] supported Configuration:

Conditions:

•


•

Terminal Action Codes Online & Default have all bits set to 0b.

•


•

AIP of LT must be set to execute the function associated with the TAC bit selected by the tester, and the LT will be set so the executed function will fail


•


•

The LT shall receive a first GENERATE AC command requesting an TC in all cases.



2CJ.151.01 TAC Denial processing bit set to 0b (2) Test No: 2CJ.151.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal issues a GENERATE AC requesting a

ARQC, if for a bit set to 1b in the TVR, the corresponding bit in the TAC Denial is set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration:

Conditions:

•


•

Terminal Action Codes Online & Default have all bits set to 0b.

•

Issuer Action Codes Default and Denial have all bits set to 0b.

•

Issuer Action Code Online has one bits set to 1b in order that the Terminal shoud request an ARQC

•



•


•

The LT shall receive a first GENERATE AC command requesting an ARQC in all cases


Page 1222


2CJ.152.00 TAC Online Processing, bit set to 1b Test No: 2CJ.152.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the terminal issues a GENERATE AC requesting an

ARQC, if the terminal has online capabilities and if for a bit set to 1b in the TVR, the corresponding bit in the TAC Online is set to 1b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline/Online capable] supported Configuration:

Conditions:

•

Terminal Action Code Online has one bit set to 1b and the corresponding TVR bit is set to 1b.

•

Terminal Action Code Denial has all bits set to 0b.

•


•



•


•




2CJ.153.00 TAC Online Processing, bit set to 0b Test No: 2CJ.153.00 - Revision 12 – Number of sub cases: 0 Objective: To ensure that the terminal issues a GENERATE AC requesting a TC,

if the terminal has online capabilities and if for a bit set to 1b in the TVR, the corresponding bit in the TAC Online is set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline/Online capable] supported Configuration:

Conditions:

•

Terminal Action Code Online has one bit set to 0b and the corresponding TVR bit is set to 1b.

•


•


•



•


•

The LT shall receive a first GENERATE AC command requesting a TC in all cases


Page 1224


2CJ.154.00 TAC Default processing bit set to 1b, & terminal unable to go online Test No: 2CJ.154.00 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal issues a second GENERATE AC

requesting an AAC and online connection was requested after first GENERATE AC and terminal is unable to go online, and for a bit set to 1b in the TVR, the corresponding bit in the TAC Default is set to 1b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline/Online capable] supported OR ([Online Only] supported AND Configuration: [Normal Default Action Code processing] supported)) OR ([Offline Only]

supported AND [Terminal checks the AC default after 1st GENAC] supported)

Conditions:

•


•


•

Terminal Action Code Default has one bit set to 1b and the corresponding TVR bit is set to 1b.

•

LT returns ARQC to first GENERATE AC command.

•


•



•


•

The LT shall receive a second GENERATE AC command requesting an AAC in all cases



2CJ.155.00 TAC Default processing bit set to 0b, & terminal unable to go online Test No: 2CJ.155.00 - Revision 12- Number of sub cases: 0 Objective: To ensure that the terminal issues a second GENERATE AC

requesting a TC, if online connection was requested after first GENERATE AC, terminal is unable to go online, and for each bit set to 1b in the TVR, the corresponding bit in both the IAC Default and TACDefault is set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal Configuration:

Conditions:

•

[Offline/Online capable] supported OR ([Online Only AND Normal Default Action processing]) supported

•

Terminal Action Code Denial has all bit set to 0b.

•

Terminal has online capabilities and unable to go online

•


•


•


•



•


•

The LT shall receive a second GENERATE AC command requesting a TC in all cases


Page 1226


2CJ.156.00 TAC Default processing bit set to 1b, & terminal has no online capability Test No: 2CJ.156.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal skips the check of Online Action Codes and

issues a first GENERATE AC requesting an AAC, if terminal has no online capabilities, and for a bit set to 1b in the TVR, the corresponding bit in the TAC Default is set to 1b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline Only] supported AND [Terminal checks the AC default prior 1st Configuration: GENAC] supported

Conditions:

•


•

Terminal Action Code Online has all bit set to 1b.

•


•


•



•

The terminal shall process the transaction until completion, by requesting an AAC.

•




2CJ.157.00 TAC Default processing bit set to 0b, & terminal has no online capability Test No: 2CJ.157.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal skips the check of Online Action Codes and

issues a first GENERATE AC requesting a TC, if terminal has no online capability, and for each bit set to 1b in the TVR, the corresponding bit in both the IAC Default and TAC-Default is set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline Only] supported AND [Terminal checks the AC default prior 1st Configuration: GENAC]

Conditions:

•


•

Terminal Action Code Online has all bit set to 1b.

•


•

Issuer Action Code Denial has all bit set to 0b.

•

Issuer Action Code Default has all bits set to 0b.

•


Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The LT shall receive a first GENERATE AC command requesting a TC

in all cases


Page 1228


2CJ.157.01 Online Only device skips TAC default Test No: 2CJ.157.01 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the terminal skips the check of Default Action Codes

when unable to go online and finding no matching bits in the TACDefault or IAC-Default. Reference EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1:

SU 51 – Bulletin n° 51, Online-only terminals (July 2006) Terminal [Online Only] supported AND [Skip Default Action Code processing] Configuration: supported

Conditions:

•


•

Terminal Action Code Default has one bit set to 0b.

•

Issuer Action Code Denial has all bit set to 0b.

•

Issuer Action Code Online has all bits set to 0b.

•


•

LT responds ARQC to the first Generate AC.

•


Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The LT shall receive a second GENERATE AC command requesting a

AAC.



2CJ.158.00 Terminal Action Anaysis & TVR and Issuer Action CodeDenial check requests an AAC Test No: 2CJ.158.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal performs Action Analysis prior to the

issuing of the first GENERATE AC command. To ensure that the terminal issues a GENERATE AC requesting an AAC if for a bit that is set to 1b in the TVR, the corresponding bit in the IAC Denial is set to 1b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal Terminal Action Codes have all bits set to 0b. Configuration: Conditions:

•

Issuer Action Code Denial has one bit set to 1b and the corresponding TVR bit is set to 1b.

•


•

AIP of LT must be set to execute the function associated with the IAC bit selected by tester and the LT will be set so the executed function will fail


•


•



Page 1230


2CJ.159.00 Terminal Action Anaysis & TVR and IAC-Denial check requests a TC (implied) Test No: 2CJ.159.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal performs Action Analysis prior to the

issuing of the first GENERATE AC command. To ensure that the terminal issues a GENERATE AC requesting a TC if for a bit that is set to 1b in the TVR, the corresponding bit in the IAC Denial is set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline Only or Offline/Online capable] supported Configuration:

Terminal Action Codes have all bits set to 0b. Conditions:

•


•

Issuer Action Codes Online & Default have all bits set to 0b.

•

AIP of LT must be set to execute the function associated with the IAC bit selected by the tester, and the LT will be set so the executed function will fail


•


•

The LT shall receive a first GENERATE AC command requesting an TC in all cases



2CJ.159.01 Terminal Action Analysis & TVR and IAC-Denial check requests a ARQC (implied) Test No: 2CJ.159.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal performs Action Analysis prior to the

issuing of the first GENERATE AC command. To ensure that the terminal issues a GENERATE AC requesting a ARQC if for a bit that is set to 1b in the TVR, the corresponding bit in the IAC Denial is set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration:

Conditions:

•

Terminal Action Codes Denial & Default have all bits set to 0b.

•

Terminal Action Code Online has a bit set to 1b, in order that the Terminal request an ARQC

•


•

Issuer Action Codes Online & Default have all bits set to 0b.

•



•


•

The LT shall receive a first GENERATE AC command requesting an ARQC


Page 1232


2CJ.160.00 Terminal has online capability, TVR and Issuer Action Code-Online check requests an ARQC Test No: 2CJ.160.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal issues a GENERATE AC requesting an

ARQC, if the terminal has online capabilities and if for a bit set to 1b in the TVR, the corresponding bit in the IAC Online is set to 1b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration:


•

Issuer Action Codes Denial & Default have all bits set to 0b.

•

Issuer Action Code Online has one bit set to 1b and the corresponding TVR bit is set to 1b.

•



•


•




2CJ.160.01 Online only terminal requests an an ARQC when not matching TAC-Online or IAC-Online Test No: 2CJ.160.01 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the terminal issues a GENERATE AC requesting an

ARQC, if the terminal has online capabilities and if for a bit set to 1b in the TVR, the corresponding bit in the IAC Online is set to 0b. Reference EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1:

SU 51 – Bulletin n° 51, Online-only terminals (July 2006) Terminal [Online Only] supported Configuration:

•

Terminal Action Codes have all bits set to 0b.

Conditions: Issuer Action Codes have all bits set to 0b. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

The LT shall receive a first GENERATE AC command requesting an ARQC.


Page 1234


2CJ.161.00 Terminal has online capability, TVR and Online Action Codes check requests a TC (implied) Test No: 2CJ.161.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal Issues a GENERATE AC requesting a TC,

if terminal has online capabilities, and if for a bit set to 1b in the TVR, the corresponding bit in the IAC Online is set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline/Online capable] supported Configuration:


•

Issuer Action Codes Denial & Default have all bits set to 0b.

•

Issuer Action Code Online has one bit set to 0b and the corresponding TVR bit is set to 1b.

•



•


•

The LT shall receive a first GENERATE AC command requesting a TC in all cases



2CJ.162.00 Terminal is unable to go online, TVR and Issuer Action Code-Default check requests an AAC Test No: 2CJ.162.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the terminal issues a second GENERATE AC

requesting an AAC, if online connection was requested after first GENERATE AC, terminal is unable to go online, and for a bit set to 1b in the TVR, the corresponding bit in the IAC-Default is set to 1b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline/Online capable] supported OR ([Online Only AND Normal Configuration: Default Action Code processing]) supported

Conditions:

•


•


•

Issuer Action Code Denial has all bits set to 0b.

•


•

Issuer Action Code Default has one bit set to 1b and the corresponding TVR bit is set to 1b.

•



•


•

In all cases, the LT shall receive a second GENERATE AC command requesting an AAC


Page 1236


2CJ.163.00 Terminal is unable to go online, TVR and Default Action Codes check requests a TC Test No: 2CJ.163.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the terminal issues a second GENERATE AC

requesting an TC, if online connection was requested after first GENERATE AC, terminal is unable to go online, and for a bit set to 1b in the TVR, the corresponding bit in the IAC-Default is set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline/Online capable] supported OR ([Online Only AND Normal Configuration: Default Action Code processing]) supported

Conditions:

•


•


•


•


•


•



•


•

The LT shall receive a second GENERATE AC command requesting a TC in all cases



2CJ.164.00 Terminal has not online capability, TVR and Issuer Action Code-Default check requests an AAC Test No: 2CJ.164.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal skips the check of Online Action Codes and

issues a first GENERATE AC requesting an AAC, if terminal has not rejected the transaction, terminal has no online capabilities, and for a bit set to 1b in the TVR, the corresponding bit in the IAC-Default is set to 1b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline Only] supported AND [Terminal checks the AC default prior 1st Configuration: GENAC]


•


•


•



•


•



Page 1238


2CJ.165.00 Terminal has not online capability, TVR and Default Action Codes check requests a TC Test No: 2CJ.165.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal skips the check of Online Action Codes and

issues a first or second GENERATE AC requesting a TC, if terminal has not rejected the transaction, terminal has no online capabilities, and for a bit set to 1b in the TVR, the corresponding bit in the IACDefault is set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline Only] supported AND [Terminal checks the AC default prior 1st Configuration: GENAC]


•


•


•



•


•

The LT shall receive a first GENERATE AC command requesting an TC in all cases



2CJ.166.00 IAC-Denial is not present in the ICC Test No: 2CJ.166.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that if the Issuer Action Code Denial does not exist in the

card, the terminal uses a default value with all bits set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline/Online capable] supported Configuration:

Conditions:

•


•

Terminal Action Code Online has all bits set to 0b.

•


•

Issuer Action Code Denial does not exist in the card

•


•


•

AIP of LT must be set to execute the function associated with the IAC bit selected by the tester and the LT will be set so the executed function will fail


•


•

The LT shall receive a first GENERATE AC command requesting a TC.


Page 1240


2CJ.166.01 TAC-Denial is not present in the terminal Test No: 2CJ.166.01 - Revision 12 - Number of sub cases: 0 Objective: To ensure that if the Terminal Action Code Denial does not exist in the

terminal, the terminal uses a default value with all bits set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline/Online capable] supported Configuration:

Conditions:

•

Terminal Action Code Denial is not present

•


•


•


•


•


•

AIP of LT must be set to execute the function associated with the TAC bit selected by the tester and the LT will be set so the executed function will be fail

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The LT shall receive a first GENERATE AC command requesting a TC



2CJ.167.00 IAC-Online is not present in the ICC Test No: 2CJ.167.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that If the Issuer Action Code Online does not exist in the

card, the terminal uses a default value with all bits set to 1b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline/Online capable] supported Configuration:

Conditions:

•


•


•


•

Issuer Action Code Online does not exist in the card

•


•


•

AIP of LT must be set to execute the function associated with the IAC bit selected by the tester and the LT will be set so the executed function will fail


•


•

The LT shall receive a first GENERATE AC command requesting an ARQC


Page 1242


2CJ.167.01 TAC-Online is not present in the terminal Test No: 2CJ.167.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the Terminal Action Code Online does not exist in the

terminal, the terminal uses a default value with all bits set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline Only or Offline/Online capable] supported Configuration:

Conditions:

•

Terminal Action Code Online is not present

•


•


•


•


•


•

AIP of LT must be set to execute the function associated with the TAC bit selected by the tester and the LT will be set so the executed function will be fail


•


•

The LT shall receive a first GENERATE AC command requesting a cryptogram TC for all tests



2CJ.168.00 IAC-Default is not present in the ICC and the Terminal is unable to go online Test No: 2CJ.168.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that if the Issuer Action Code Default does not exist in the

card, the terminal uses a default value with all bits set to 1b when the terminal is unable to go online. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline/Online capable] supported OR ([Online Only AND Normal Configuration: Default Action processing]) supported

Conditions:

•


•


•

Terminal is unable to go online (no response received from issuer for instance)

•

Issuer Action Code Default does not exist in the card

•


•

LT requests ARQC to first GENERATE AC command.

•

AIP of LT must be set to execute the function associated with the IAC bit selected by the tester and the LT will be set so the executed function will fail for the second risk management

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The LT shall receive a second GENERATE AC command requesting

an AAC in all cases


Page 1244


2CJ.168.01 TAC-Default is not present in the Terminal and the Terminal is unable to go online Test No: 2CJ.168.01 - Revision 12 - Number of sub cases: 0 Objective: To ensure that if the Terminal Action Code Default does not exist in the

terminal, the terminal uses a default value with all bits set to 0b. Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal [Offline/Online capable] supported OR ([Online Only AND Normal Configuration: Default Action Code processing]) supported

Conditions:

•

Terminal Action Code Default is not present

•


•


•


•


•


•


•

LT requests ARQC to first GENERATE AC command.

•

AIP of LT must be set to execute a function which will fail for the second risk management (e.g. floor limit exceded)


•


•

The LT shall receive a second GENERATE AC command requesting an TC in all cases



2CJ.169.00 IAC-Default is not present in the ICC and the Terminal is offline only Test No: 2CJ.169.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the Issuer Action Code Default does not exist in the

card, the terminal uses a default value with all bits set to 1b when the terminal is offline only. Reference Book 3 - Section 5.3 - Command Use EMV 4.0:

Book 3 - Section 6.7 - Terminal Action Analysis Reference Book 3 - Section 9.3 - Command Use EMV 4.1:

Book 3 - Section 10.7 - Terminal Action Analysis Terminal ([Offline Only] supported AND [Terminal checks the AC default prior 1st Configuration: GENAC] supported)

Conditions:

•


•


•


•


•


•


•

AIP must be set to execute a function associated with the IAC and this function will be failed by the LT (e.g. SDA is failed then the TVR byte 1 bit 7 is set to 1b)

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The LT shall receive a first GENERATE AC command requesting an

AAC in all cases


Page 1246


2CJ.169.02 IAC-Default is not present in the ICC and the Terminal is offline only (2) Test No: 2CJ.169.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the Issuer Action Code Default does not exist in the

card, the terminal uses a default value with all bits set to 1b when the terminal is offline only Reference Book 3 - Section 6.7 - Terminal Action Analysis EMV 4.0: Reference Book 3 - Section 10.7 - Terminal Action Analysis EMV 4.1: Terminal ([Offline Only] supported AND [Terminal checks the AC default prior 1st Configuration: GENAC] not supported)

Conditions:

•


•


•


•


•


•

AIP must be set to execute a function associated with the IAC and this function will be failed by the LT (e.g. SDA is failed then the TVR byte 1 bit 7 is set to 1).

•

LT requests ARQC in First GENERATE AC

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The LT shall receive a second GENERATE AC command requesting

an AAC in all cases



2CJ.170.00 Card Action Analysis function completion Test No: 2CJ.170.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal sets the 'Card Risk Management was

performed' bit in the TSI to 1b after an ARQC is returned by the card. Reference Book 3 - Section 6.8 - Card Action Analysis EMV 4.0: Reference Book 3 - Section 10.8 - Card Action Analysis EMV 4.1: Terminal NA Configuration: Conditions: LT returns ARQC to first GENERATE AC. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

TSI byte 1, bit 6 = '1' (ie the Card Risk Management was performed) received at 2nd GENERATE AC.


Page 1248


2CJ.175.00 Generate AC Response in a Public Key Envelope Test No: 2CJ.175.00 - Revision 15 - Number of sub cases: 2 Objective: To ensure that if the transaction is eligible for Enhanced Combined

DDA/AC, the ICC response is an offline approval (TC) or an online request (ARQC), and if the ICC returns the GENERATE AC response in a public key envelope as specified in Book 2 Section 6.6, the terminal is able to interpret correctly this response. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation

(Dec-2001) Reference Book 2 - Section 6.6 - Combined DDA/Application Cryptogram EMV 4.1: Generation (CDA)


•


•


•

LT returns its GENERATE AC response in a public key envelope

•

Case 01: LT answers with an ARQC to the first Generate AC

•

Case 02: LT answers with a TC to the first Generate AC


•


•

The terminal shall correctly interpret the LT response.

•




2CJ.175.00 Generate AC Response in a Public Key Envelope •


•

TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation not yet performed) received at 1st GENERATE AC.

•

TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation succeeded) contained in Financial Confirmation message or Batch Data Capture message


Page 1250


2CJ.175.01 Generate AC Response in a Public Key Envelope Test No: 2CJ.175.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that if the transaction is eligible for Enhanced Combined

DDA/AC, the ICC response is an online request (ARQC), and if the ICC returns the GENERATE AC response in a public key envelope as specified in Book 2 Section 6.6, the terminal is able to interpret correctly this response. Reference EMV 4.0: Reference Book 2 - Section 6.6 - Combined DDA/Application Cryptogram EMV 4.1: Generation (CDA)


•


•


•

LT returns its GENERATE AC response in a public key envelope

•

LT answers with an ARQC to the first Generate AC


•


•

The terminal shall correctly interpret the LT response.

•


•




2CJ.175.01 Generate AC Response in a Public Key Envelope •

TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation not yet performed) received at 1st GENERATE AC.

•

TVR byte 1, bit 3 = '0' (ie Combined DDA/AC Generation succeeded) contained in Financial Confirmation message or Batch Data Capture message


Page 1252


2CJ.177.00 Advice messages during Card Action Analysis (Cryptogram Information Data: Advice required) Test No: 2CJ.177.00 - Revision 12 - Number of sub cases: 0 Objective: To verify that the terminal correctly interprets answer to a GENERATE

AC command requiring an Advice (Cryptogram Information Data: Advice required). To ensure that the terminal formats and sends an advice message to the issuer, if the 'Advice Required'. bit is set to 1b in the Cryptogram Information Data and transaction is not captured. To ensure that the terminal transmits in real-time online advices similary to an autorisation message or financial transaction. Reference Book 3 - Section 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message

Book 3 - Section 6.8.3 - Advice Messages Book 4 - Section 2.3.7 - Card Action Analysis Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message

Book 3 - Section 10.8.2 - Advice Messages Book 4 - Section 6.3.7 - Card Action Analysis Terminal [Advice] supported Configuration: Conditions:

•

LT answers to the GENERATE AC with the bit 4 of its Cryptogram Information Data (CID) sets to '1'.

•

Transaction is not captured


•

The terminal shall process the transaction until completion by an AAC.

•

The terminal shall either prepare an offline advice message or transmit an online advice message




Page 1254


2CJ.178.00 Online Processing function execution Test No: 2CJ.178.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal performs the Online Processing function if

the card returns an ARQC in the first GENERATE AC. Reference Book 3 - Section 6.9 - Online Processing EMV 4.0: Reference Book 3 - Section 10.9 - Online Processing EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•

LT returns an ARQC in response to first GENERATE AC.

•

LT must be set so that the terminal will not request an AAC on the first GENERATE AC command.


•


•

The Terminal shall prepare and send Authorization or Financial request message for the issuer



2CJ.180.00 IAD is received from the Issuer and Issuer Authentication is supported in AIP Test No: 2CJ.180.00 - Revision 12 - Number of sub cases: 3 Objective: To ensure that the terminal issues an EXTERNAL AUTHENTICATE

command with IAD received, if the card supports Issuer Authentication in AIP and if IAD is present in authorization response message. Reference Book 3 - Section 6.9 - Online Processing EMV 4.0: Reference Book 3 - Section 10.9 - Online Processing EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•

AIP of LT indicates Issuer Authentication is supported (AIP byte 1 bit 3 = '1')

•

Authorization response message contains IAD

•

Case 01: The host sends Issuer Authentication Data with length equal to 10 bytes, valid cryptogram & 2 bytes proprietary data

•

Case 02: The host sends Issuer Authentication Data with length equal to 8 bytes, valid cryptogram only

•



•

The temrinal shall process the transaction until completion by requesting a TC or an AAC.

•

The LT shall receive an EXTERNAL AUTHENTICATE command after the first GENERATE AC.

•

Data field of EXTERNAL AUTHENTICATE received by LT shall contain IAD as received from Issuer


Page 1256


2CJ.181.01 Failed Processing for EXTERNAL AUTHENTICATE Test No: 2CJ.181.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal accepts a failed status '69 85' in response

to EXTERNAL AUTHENTICATE command and either understands it as failed processing (and sets the 'Issuer authentication was unsuccessful' bit' in the TVR to 1b), or terminate the transaction Reference Book 3 - Section 6.9 - Online Processing EMV 4.0:

Book Bulletins - Section AN 17 - Bulletin n°17, Terminal Requirements regarding Status Words returned to an EXTERNAL AUTHENTICATE command (Dec-2003) Reference Book 3 - Section 10.9 - Online Processing EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•

Issuer Authentication Data is sent back to the terminal in the emulated response from Issuer

•

LT returns status '69 85' in response to EXTERNAL AUTHENTICATE command.


particular on-line processing and Issuer Authentication processing). Pass Criteria: The terminal shall:

•

either process the transaction until completion and sets the TVR byte 5, bit 7 = '1' (ie Issuer Authentication was unsuccessful), received at 2nd GENERATE AC.

•


or terminate the transaction. Copyright © 2008 EMVCo, LLC. All Rights Reserved. Page 1257



Page 1258


2CJ.182.00 IAD is received from the Issuer and Issuer Authentication is not supported in AIP (Second Gen AC) Test No: 2CJ.182.00 - Revision 12 - Number of sub cases: 3 Objective: To

ensure that the terminal does not send EXTERNAL AUTHENTICATE command if the card does not support Issuer Authentication in AIP and if IAD is present in authorization response message, but sends the IAD in the CDOL2 if requested by the card.

Reference Book 3 - Section 6.9 - Online Processing EMV 4.0: Reference Book 3 - Section 10.9 - Online Processing EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•

AIP of LT indicates Issuer Authentication shall not be performed (AIP byte 1 bit 3 = '0')

•

Authorization response message contains IAD

•

CDOL2 contains the IAD

•


•

Case 02: The host sends Issuer Authentication Data with length equal to 8 bytes, valid cryptogram

•



•


•

LT shall not receive EXTERNAL AUTHENTICATE command after first GENERATE AC.

•

LT shall receive GENAC2 command with a CDOL2 containing



2CJ.182.00 IAD is received from the Issuer and Issuer Authentication is not supported in AIP (Second Gen AC) the IAD as sent in the Authorization response message


Page 1260


2CJ.183.00 IAD is not received from the Issuer Test No: 2CJ.183.00 - Revision 10g - Number of sub cases: 0 Objective: To

ensure that the terminal does not send EXTERNAL AUTHENTICATE command and sets the 'Issuer authentication was performed' bit in the Transaction Status Information to '0', if the card supports Issuer Authentication in AIP and if IAD is not present in authorization response message.

Reference Book 3 - Section 6.9 - Online Processing EMV 4.0:

Book 4 - Section 8.2.2 - Downgraded Authorisation Reference Book 3 - Section 10.9 - Online Processing EMV 4.1:

Book 4 - Section 12.2.2 - Downgraded Authorisation Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•

AIP of LT indicates Issuer Authentication is supported (AIP byte 1 bit 3 = '1')

•

Authorization response message does not contain IAD


•


•

LT shall not receive EXTERNAL AUTHENTICATE command after first GENERATE AC.

•

TSI byte 1, bit 5 = '0' (ie the Issuer Authentication was not performed) received at 2nd GENERATE AC.



2CJ.187.00 Issuer Script may contain several Issuer Script Commands Test No: 2CJ.187.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal is able to receive and manage Issuer

scripts containing several commands. To ensure that the terminal processes commands in the same sequence they appear in the script. Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:

Book Bulletins - Section AN 13 - Bulletin n°13, TVR and TSI Bit Settings Following Script Processing (Dec-2003) Reference Book 3 - Section 10.10 - Issuer-to-Card Script Processing EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•

Authorization response message contains one Issuer script with tag ’71’ containing three commands.

•

LT returns '90 00' to each command of the script


•


•

The LT shall receive a sequence of commands 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.


Page 1262


2CJ.187.00 Issuer Script may contain several Issuer Script Commands •

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



2CJ.187.01 Issuer Script may contain several Issuer Script Commands (2) Test No: 2CJ.187.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal is able to receive and manage Issuer



•


•

Authorization response message contains one Issuer script with tag ’72’ containing three commands.

•



•


•

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


Page 1264


2CJ.187.01 Issuer Script may contain several Issuer Script Commands (2) Capture message •




2CJ.187.02 Issuer Script may contain several Issuer Script Commands (3) Test No: 2CJ.187.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal is able to receive and manage Issuer



•


•

Authorization response message contains one Issuer script with tag ’71’ containing three commands and one Issuer script with tag ’72’ containing three commands.

•



•


•

The LT shall receive a sequence of commands according to the scripts contained in the authorization response before and after the second GENERATE AC.

•


•


•

TSI byte 1, bit 3 = '1' (ie Script processing was performed)


Page 1266


2CJ.187.02 Issuer Script may contain several Issuer Script Commands (3) received at 2nd GENERATE AC. •

Issuer Script Results for the script with Tag 71, Byte 1 shall be set to '20', script processing successful, contained in Financial Confirmation message or Batch Data Capture message

•




2CJ.188.00 Issuer Script Command unknown to the terminal Test No: 2CJ.188.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal is able to deliver to the card a non EMV

command contained in a script. Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message contains one Issuer script with tag ’71’ containing three non EMV commands.

•



•


•

The LT shall receive a sequence of non EMV commands according to the script contained in the authorization response before the second GENERATE AC.

•


•


•


•



Page 1268




2CJ.188.01 Issuer Script Command unknown to the terminal (2) Test No: 2CJ.188.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal is able to deliver to the card non described

commands contained in a script. Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message contains one Issuer script with tag ’72' containing three non EMV commands.

•



•


•

The LT shall receive a sequence of non EMV commands according to the script contained in the authorization response after the second 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


Page 1270


2CJ.188.01 Issuer Script Command unknown to the terminal (2) Confirmation message or Batch Data Capture message



2CJ.188.02 Issuer Script Command unknown to the terminal (3) Test No: 2CJ.188.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal is able to deliver to the card non described

commands contained in a script. Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message contains one Issuer script with tag ’71’ containing three non EMV commands and one Issuer script with tag ’72’ containing three non EMV commands.

•



•


•

The LT shall receive a sequence of non EMV commands according to the scripts contained in the authorization response before and after the second GENERATE AC.

•


•


•


•

Issuer Script Results for the script with Tag 71, Byte 1 shall be set to '20', script processing successful, contained in Financial


Page 1272


2CJ.188.02 Issuer Script Command unknown to the terminal (3) Confirmation message or Batch Data Capture message •




2CJ.189.00 Issuer Script with Tag '71' execution Test No: 2CJ.189.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal processes a script with Tag = 71 before the

second GENERATE AC. To ensure that the terminal sets the 'Script processing was performed' bit in the TSI to 1b, if one script was received in the authorization response and was processed by the terminal. Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message contains one Issuer script with Tag '71'

•



•


•

The LT shall receive a sequence of commands according to the script contained in the authorization response before the final GENERATE AC.

•


•


•



Page 1274


2CJ.189.00 Issuer Script with Tag '71' execution •




2CJ.190.00 Issuer Script with Tag '72' execution Test No: 2CJ.190.00 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal processes a script with Tag = 72 after the

second GENERATE AC. To ensure that the terminal sets the 'Script processing was performed' bit in the TSI to 1b, if one script was received in the authorization response and was processed by the terminal. Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message contains one Issuer script with Tag '72'

•



•


•

The LT shall receive a sequence of commands according to the script contained in the authorization response after the final GENERATE AC.

•


•


•

TSI byte 1, bit 3 = '1' (ie Script processing was performed) contained in Financial Confirmation message or Batch Data


Page 1276


2CJ.190.00 Issuer Script with Tag '72' execution Capture message •




2CJ.191.00 Issuer Script Format Test No: 2CJ.191.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal is able to recognize script format (ie a

constructed data object containing a Script Identifier and a sequence of Issuer Script Command APDUs). Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Case 01: Authorization response message contains one '71' Issuer script containing a script Identifier, LT returns '90 00' to each command of the script

•

Case 02: Authorization response message contains one '71' Issuer script containing a script Identifier with length equal to zero, LT returns '90 00' to each command of the script


•


•

The LT shall receive a sequence of commands APDUs according to the script contained in the authorization response before the final GENERATE AC.

•


•


•



Page 1278


2CJ.191.00 Issuer Script Format •




2CJ.191.01 Issuer Script Format (2) Test No: 2CJ.191.01 - Revision 15 - Number of sub cases: 2 Objective: To ensure that the terminal is able to recognize script format (ie a

constructed data object containing a Script Identifier and a sequence of Issuer Script Command APDUs). Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Case 01: Authorization response message contains one '72' Issuer script containing a script Identifier, LT returns '90 00' to each command of the script

•

Case 02: Authorization response message contains one '72' Issuer script containing a script Identifier with length equal to zero, LT returns '90 00' to each command of the script


•


•

The LT shall receive a sequence of commands APDUs according to the script contained in the authorization response after second GENERATE AC.

•


•


•



Page 1280


2CJ.191.01 Issuer Script Format (2) Capture message •




2CJ.192.00 Script Identifier in Issuer Script Test No: 2CJ.192.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that the terminal is able to receive and manage a script

without optional Script Identifier. Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message contains one '71' Issuer script without script Identifier

•



•


•

The LT shall receive a sequence of commands APDUs according to the script contained in the authorization response before second GENERATE AC.

•


•


•


•



Page 1282




2CJ.192.01 Script Identifier in Issuer Script (2) Test No: 2CJ.192.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal is able to receive and manage a script

without optional Script Identifier. Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message contains one '72' Issuer script without script Identifier

•



•


•

The LT shall receive a sequence of commands APDUs according to the script contained in the authorization response after second GENERATE AC.

•


•


•


•

Issuer Script Results for the script with Tag 72, Byte 1 shall be set to '20', script processing successful, contained in Financial


Page 1284


2CJ.192.01 Script Identifier in Issuer Script (2) Confirmation message or Batch Data Capture message



2CJ.193.00 Issuer Script processing Test No: 2CJ.193.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal processes scripts in the same sequence

they appear in authorization response. To ensure that the terminal is able to receive and manage multiple Issuer scripts in a single authorization message. To ensure that the terminal reports a script execution success in the Issuer Script Results. Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:

Book 4 - Section 2.3.9 - Issuer-to-Card Script Processing Book Bulletins - Section AN 13 - Bulletin n°13, TVR and TSI Bit Settings Following Script Processing (Dec-2003) Reference Book 3 - Section 10.10 - Issuer-to-Card Script Processing EMV 4.1:

Book 4 - Section 6.3.9 - Issuer-to-Card Script Processing Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•

Authorization response message contains three Issuer script with tag '71'

•

LT returns '90 00' to each command of a script


•


•

The LT shall receive a sequence of commands APDUs in the order in which scripts were in the authorization response before second GENERATE AC.

•


•

TVR byte 5, bit 5 = '0' (ie Script processing after final GENERATE AC not used) contained in Financial Confirmation


Page 1286


2CJ.193.00 Issuer Script processing message or Batch Data Capture message •


•


•

Issuer Script Results for 2nd script with Tag 71, Byte 1 shall be set to '20', script processing successful) contained in Financial Confirmation message or Batch Data Capture message

•

Issuer Script Results for the 3rd script with Tag 71, Byte 1 shall be set to '20', script processing successful, contained in Financial Confirmation message or Batch Data Capture message



2CJ.193.01 Issuer Script processing (2) Test No: 2CJ.193.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal processes scripts in the same sequence




•


•

Authorization response message contains three Issuer script with tag '72'

•



•


•

The LT shall receive a sequence of commands APDUs in the order in which scripts were in the authorization response after second GENERATE AC.

•


•

TVR byte 5, bit 6 = '0' (ie Script processing after final


Page 1288


2CJ.193.01 Issuer Script processing (2) GENERATE AC not used) received at 2nd GENERATE AC. •


•


•

Issuer Script Results for 2nd script with Tag 72, Byte 1 shall be set to '20', script processing successful, contained in Financial Confirmation message or Batch Data Capture message

•




2CJ.193.02 Issuer Script processing (3) Test No: 2CJ.193.02 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal processes scripts in the same sequence




•


•

Authorization response message contains four Issuer script with tag '71' and four Issuer script with tag '72'

•



•


•

The LT shall receive a sequence of commands APDUs in the order in which scripts were in the authorization response before and after second GENERATE AC.

•


•

TVR byte 5, bit 6 = '0' (ie Script processing succeeded before


Page 1290


2CJ.193.02 Issuer Script processing (3) final GENERATE AC) received at 2nd GENERATE AC. •


•


•

Issuer Script Results for 2nd script with Tag 71, Byte 1 shall be set to '20', script processing successful, contained in Financial Confirmation message or Batch Data Capture message

•

Issuer Script Results for 3rd script with Tag 71, Byte 1 shall be set to '20', script processing successful, contained in Financial Confirmation message or Batch Data Capture message

•

Issuer Script Results for 4th script with Tag 71, Byte 1 shall be set to '20', script processing successful, contained in Financial Confirmation message or Batch Data Capture message

•

Issuer Script Results for the 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

•

Issuer Script Results for the 2nd script with Tag 72, Byte 1 shall be set to '20', script processing successful, contained in Financial Confirmation message or Batch Data Capture message

•


•

Issuer Script Results for the 4th script with Tag 72, Byte 1 shall be set to '20', script processing successful, contained in Financial Confirmation message or Batch Data Capture message



2CJ.194.00 Issuer Script Commands not BER-TLV encoded and Issuer Script tag is '71' Test No: 2CJ.194.00 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal sets the 'Script processing failed before

final GENERATE AC' bit in the TVR to 1b, if the command contained in the script with Tag 71 received is not BER-TLV encoded with Tag '86' Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message contains an Issuer script with Tag '71'

•

Case 01: Commands in Issuer Script are not BER-TLV encoded in tag '86'

•

Case 02: Commands in Issuer Script are encoded in tag '86' but Length value of tag '86' is not correct


•


•

TVR byte 5, bit 6 = '1' (ie Script processing failed before final GENERATE AC) received at 2nd GENERATE AC.

•


•


•

Issuer Script Results Byte 1 shall be set to '00', script not


Page 1292


2CJ.194.00 Issuer Script Commands not BER-TLV encoded and Issuer Script tag is '71' performed contained in Financial Confirmation message or Batch Data Capture message



2CJ.195.00 Issuer Script Commands not BER-TLV encoded and Issuer Script tag is '72' Test No: 2CJ.195.00 - Revision 15 - Number of sub cases: 2 Objective: To ensure that the terminal sets the 'Script processing failed after final

GENERATE AC' bit in the TVR to 1b, if the command contained in the script with Tag 72 received is not BER-TLV encoded with Tag '86' Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message contains an Issuer script with Tag '72'

•


•



•


•

TVR byte 5, bit 5 = '1' (ie Script processing failed after final GENERATE AC) contained in Financial Confirmation message or Batch Data Capture message

•


•



Page 1294


2CJ.195.00 Issuer Script Commands not BER-TLV encoded and Issuer Script tag is '72' •

Issuer Script Results Byte 1 shall be set to '00', script not performed contained in Financial Confirmation message or Batch Data Capture message



2CJ.195.01 Issuer Script Commands not BER-TLV encoded and Issuer Script tag are '71' and '72' Test No: 2CJ.195.01 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal sets the 'Script processing failed after final

GENERATE AC' bit and 'Script processing failed before final GENERATE AC' bit in the TVR to 1b, if the commands contained in the script with Tag 71 and 72 received are not BER-TLV encoded with Tag '86' Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message contains an Issuer script with Tag '71' and an Issuer script with Tag '72' both contains the following commands:

•


•



•


•


•


•



Page 1296


2CJ.195.01 Issuer Script Commands not BER-TLV encoded and Issuer Script tag are '71' and '72' received at 2nd GENERATE AC. •

Issuer Script Results Byte 1 shall be set to '00', script not performed for script with tag 71, contained in Financial Confirmation message or Batch Data Capture message

•

Issuer Script Results Byte 1 shall be set to '00', script not performed for script with tag 72, contained in Financial Confirmation message or Batch Data Capture message



2CJ.195.02 Issuer Script Commands not BER-TLV encoded and Issuer Script tag are '71' and '72' (2) Test No: 2CJ.195.02 - Revision 15 - Number of sub cases: 2 Objective: To ensure that the terminal sets the 'Script processing failed after final

GENERATE AC' bit in the TVR to 1b, if the command contained in the script with Tag 72 received is not BER-TLV encoded with Tag '86', when tag 71 and 72 scripts are received Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message contains an Issuer script with Tag '71' commands.

•

Authorization response message contains also an Issuer script with Tag '72':

•

Case 01: Commands in Tag ‘72’ Issuer Script are not BER-TLV encoded in tag '86'

•

Case 02: Commands in Tag ‘72’ Issuer Script are encoded in tag '86' but Length value of tag '86' is not correct


•


•


•

TVR byte 5, bit 6 = '0' (ie Script processing succeded before final GENERATE AC) received at 2nd GENERATE AC.


Page 1298


2CJ.195.02 Issuer Script Commands not BER-TLV encoded and Issuer Script tag are '71' and '72' (2) •


•

Issuer Script Results for the script with Tag 71, Byte 1 shall be set to '2x', script processing successful, contained in Financial Confirmation message or Batch Data Capture message

•

Issuer Script Results for the script with Tag 72, Byte 1 shall be set to '00', script processing not performed, contained in Financial Confirmation message or Batch Data Capture message



2CJ.195.03 Issuer Script Commands not BER-TLV encoded and Issuer Script tag are '71' and '72' (3) Test No: 2CJ.195.03 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal sets the 'Script processing failed before

final GENERATE AC' bit in the TVR to 1b, if the command contained in the script with Tag 71 received is not BER-TLV encoded with Tag '86', when tag 71 and 72 scripts are received Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message contains an Issuer script with Tag '72' command.

•

Authorization response message contains also an Issuer script with Tag '71':

•


•



•


•

TVR byte 5, bit 5 = '0' (ie Script processing succeded after final GENERATE AC) contained in Financial Confirmation message or Batch Data Capture message

•



Page 1300


2CJ.195.03 Issuer Script Commands not BER-TLV encoded and Issuer Script tag are '71' and '72' (3) •


•


•

Issuer Script Results for the script with Tag 72, Byte 1 shall be set to '2x', script processing successful, contained in Financial Confirmation message or Batch Data Capture message



2CJ.197.00 SW1 in the Status Code equals '90', '62', or '63' Test No: 2CJ.197.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal proceeds with the next command in the

script if the card returns status code with SW1 equal to '90', '62', or '63' Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message contains one Issuer script with tag '71' containing the following commands.

•

LT returns 90 00 to script command 1.

•

LT returns 62 xx to script command 2.

•


•

LT returns 90 00 to 2 other script commands.


•


•

The LT shall receive all the commands contained in the script before second GENERATE AC.

•


•


•



Page 1302


2CJ.197.00 SW1 in the Status Code equals '90', '62', or '63' received at 2nd GENERATE AC. •

Issuer Script Results Byte 1 shall be set to '20', script processing successful, contained in Financial Confirmation message or Batch Data Capture message



2CJ.197.01 SW1 in the Status Code equals '90', '62', or '63' (2) Test No: 2CJ.197.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal proceeds with the next command in the

script if the card returns status code with SW1 equal to '90', '62', or '63' Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•


•


•


•


•



•


•

The LT shall receive all the commands contained in the script after second GENERATE AC.

•


•


•



Page 1304


2CJ.197.01 SW1 in the Status Code equals '90', '62', or '63' (2) Capture message •

Issuer Script Results Byte 1 shall be set to '20', script processing successful, contained in Financial Confirmation message or Batch Data Capture message



2CJ.197.02 SW1 in the Status Code equals '90', '62', or '63' (3) Test No: 2CJ.197.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal proceeds with the next command in the

script if the card returns status code with SW1 equal to '90', '62', or '63'. Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•


•


•


•


•


•

Authorization response message contains also one Issuer script with tag '72' containing the following commands.

•


•


•


•



•



Page 1306


2CJ.197.02 SW1 in the Status Code equals '90', '62', or '63' (3) •

The LT shall receive all the commands contained in the script before and after second GENERATE AC.

•


•


•


•


•




2CJ.199.00 SWI in the Status Code is different from '90', '62', or '63' and Issuer Script tag is '71' Test No: 2CJ.199.00 - Revision 15 - Number of sub cases: 6 Objective: To ensure that the terminal sets the 'Script processing failed before

final GENERATE AC' bit in the TVR to 1b, if Script Tag is 71 and SW1 in the status code returned by the card to a script command is different from '90', '62', or '63'. To ensure that the terminal reports a script error in the Issuer Script Results. Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:



•


•

Authorization response message contains one Issuer script with Tag '71' containing three command.

•

LT returns 90 00 to script command 1 and to command 3 (if terminal sends it)

•

LT returns the following status to script command 2:

•

Case 01: SW1 SW2 is 69 xx

•

Case 02: SW1 SW2 is 6A xx

•


•

Case 04: SW1 SW2 is 65 00

•

Case 05: SW1 SW2 is 6D 00

•

Case 06: SW1 SW2 is 6E 00


Page 1308


2CJ.199.00 SWI in the Status Code is different from '90', '62', or '63' and Issuer Script tag is '71' Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

TVR byte 5 bit 6 = '1' (ie Script processing failed before final GENERATE AC) received at 2nd GENERATE AC.

•

TVR byte 5, bit 5 = '0' (ie Script processing after final GENERATE AC not used) received at 2nd GENERATE AC.

•


•

Issuer Script Results Byte 1 shall be set to '1x', script processing failed, x is equal to 2 as it is the second command failed, contained in Financial Confirmation message or Batch Data Capture message

•

LT shall not receive command 3



2CJ.200.00 SW1 in the Status Code is different from '90', '62', or '63' and Issuer Script tag is '72' Test No: 2CJ.200.00 - Revision 15 - Number of sub cases: 6 Objective: To ensure that the terminal sets the 'Script processing failed after final

GENERATE AC' bit in the TVR to 1b, if Script Tag is 72 and SW1 in the status code returned by the card to a script command is different from '90', '62', or '63'. To ensure that the terminal reports a script error in the Issuer Script Results. Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:



•


•

Authorization response message contains one Issuer script with Tag '72' containing three commands.

•

LT returns 90 00 to script command 1 and to command 3 (if terminal sends it)

•

LT returns the following status to script command 2:

•

Case 01: SW1 SW2 is 69 83

•

Case 02: SW1 SW2 is 6A xx

•


•


•

Case 05: SW1 SW2 is 6D 00

•

Case 06: SW1 SW2 is 6E 00


Page 1310


2CJ.200.00 SW1 in the Status Code is different from '90', '62', or '63' and Issuer Script tag is '72' Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•


•

TSI byte 1, bit 3 = '1' (ie Script processing was performed, if present in Financial Confirmation message or Batch Data Capture message

•

Issuer Script Results Byte 1 shall be set to '1x', script processing failed, x is equal to 2 as it is the second command failed, contained in Financial Confirmation message or Batch Data Capture message

•

LT shall not receive command 3



2CJ.200.01 SW1 in the Status Code is different from '90', '62', or '63' and Issuer Script tag is '72' Test No: 2CJ.200.01 - Revision 11 - Number of sub cases: 4 Objective: To ensure that the terminal sets the 'Script processing failed before

final GENERATE AC' bit in the TVR to 1b, if Script Tag is 71 and SW1 in the status code returned by the card to a script command is different from '90', '62', or '63', and that it sets 'Script processing failed after final GENERATE AC' bit in the TVR to 1b, if Script Tag is 72 and SW1 in the status code returned by the card. to a script command is different from '90', '62', or '63'. Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:



•

Authorisation system sends the following scripts:

•

Case 01: Script '71' contains three commands: LT returns '69xx' on command 2, Script '72' contains two commands, LT returns '9000' on each.

•

Case 02: Script '71' contains two commands: LT returns '9000' on each, Script '72' contains two commands: LT returns '69xx' on command 1.

•

Case 03: Script '71' contains two commands: LT returns '6Axx' on command 1, Script '72' contains two commands: LT returns '6900' on command 1.

•

Case 04: Script '71' contains two commands: LT returns '6Axx' on command 1, Script '72' contains three commands: LT returns '6Axx' on command 2



Page 1312


2CJ.200.01 SW1 in the Status Code is different from '90', '62', or '63' and Issuer Script tag is '72' Pass Criteria:

•


•

TVR byte 5, bit 5 = '1' (ie Script processing failed after final GENERATE AC, in batch data capture, for the subcases 2,3 and 4

•

TVR byte 5, bit 5 = '0' (ie Script processing succeded after final GENERATE AC, in batch data capture, for the subcases 1

•

TVR byte 5, bit 6 = '1' (ie Script processing failed before final GENERATE AC, in batch data capture, for the subcases 1,3,4

•

TVR byte 5, bit 6 = '0' (ie Script processing succeded before final GENERATE AC, in batch data capture, for the subcases 2

•

TSI byte 1, bit 3 = '1' (ie Script processing was performed) received at second GENERATE AC.

•

Issuer Script Results Byte 1 shall be set to '1x', script processing failed, in the script containing errors. X is the sequence number of the command which failed, contained in Financial Confirmation message or Batch Data Capture message

•

Issuer Script Results Byte 1 shall be set to '20', script processing succeded for the correct script, contained in Financial Confirmation message or Batch Data Capture message

•

LT shall not received any command after a failed command in a script. Following script shall be performed



2CJ.202.00 Issuer Script not processed (implied) Test No: 2CJ.202.00 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal does not set the 'Script processing was

performed' bit in the TSI to 1b, if no script was received in the authorization response Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:


•


•

Authorization response message does not contains any Issuer script


•


•

TSI byte 1 bit 3 = '0' (ie Script processing was not performed) received at 2nd GENERATE AC.

•

TSI byte 1 bit 3 = '0' (ie Script processing was not performed) contained in Financial Confirmation message or Batch Data Capture message

•

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

•


•

No Issuer Script Results contained in Financial Confirmation message or Batch Data Capture message


Page 1314


2CJ.202.01 Issuer Script not sent when no Script performed Test No: 2CJ.202.01 - Revision 12 - Number of sub cases: 3 Objective: To ensure that the terminal does not set the 'Script processing was

performed' bit in the TSI to 1b, if no script was received in the authorization response Reference Book 3 - Section 6.10 - Issuer-to-Card Script Processing EMV 4.0:

Book Bulletins - Section AN 13 - Bulletin n°13, TVR and TSI Bit Settings Following Script Processing (Dec-2003) Reference Book 3 - Section 10.10 - Issuer-to-Card Script Processing EMV 4.1: Terminal [Online Only or Offline/online capable] supported Configuration: Conditions:

•


•

Two transactions are made in each subcase.

•

Subcase 01: Authorization response message contains “71” scripts in the first transaction. Authorization response message contains no script in the second transaction

•

Subcase 02: Authorization response message contains “72” scripts. Authorization response message contains no script in the second transaction

•

Subcase 03: Authorization response message contains “71” and “72” scripts. Authorization response message contains no script in the second transaction


•

The terminal shall process the transaction until completion, by requesting a TC or an AAC in first and second transaction.

•

TSI byte 1 bit 3 = '0' (ie Script processing was not performed) received at 2nd GENERATE AC in the second transaction.

•

TSI byte 1 bit 3 = '0' (ie Script processing was not performed, if present in Financial Confirmation message or Batch Data



2CJ.202.01 Issuer Script not sent when no Script performed Capture message in the second transaction •

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 in the second transaction

•

TVR byte 5, bit 6 = '0' (ie Script processing before final GENERATE AC not used) received at 2nd GENERATE AC in the second transaction.

•

No Issuer Script Results contained in Financial Confirmation message or Batch Data Capture message in the second transaction


Page 1316


2CJ.203.00 Enhanced Combined DDA/AC failed when ICC responded with TC (1) Test No: 2CJ.203.00 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal declines the transaction if ICC has

responded with TC and Enhanced Combined DDA/AC failed (1st GENERATE AC). To ensure that the terminal sets the 'Combined DDA/AC Generation failed' bit in the TVR to 1b if the Enhanced Combined DDA/AC Generation is performed but unsuccessful. To ensure that the terminal sets the 'Offline data authentication was performed' bit in the TSI to 1b upon completion of the Offline Data Authentication Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0:

Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined Dynamic Data Authentication and Application Cryptogram Generation (Dec-2001) Book Bulletins - Section SU 20 - Bulletin n°20, Combined DDA/AC Generation (Jan-2004) Reference Book2 - Section 6.6.2 – Dynamic Signature Verification EMV 4.1:

Book3 - Section 10.3 - Offline Data Authentication 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:

•


•


•

LT responds TC to the 1st GENERATE AC.

•

Digital signature is not valid.

Action: NA



2CJ.203.00 Enhanced Combined DDA/AC failed when ICC responded with TC (1) Procedure: Application in LT is selected and transaction is processed with LT (in


•

The terminal shall decline the transaction without performing a second GENERATE AC

•



Page 1318



responded with TC and Enhanced Combined DDA/AC failed (2nd GENERATE AC) Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation

(Dec-2001) Book Bulletins - Section SU 20 - Bulletin n°20, Combined DDA/AC Generation (Jan-2004) Reference Book2 - Section 6.6.2 – Dynamic Signature Verification EMV 4.1:


•


•


•


•

LT responds TC to the 2nd GENERATE AC and Digital signature is not valid.

•

LT responds ARQC to the 1st GENERATE AC and Digital signature is valid.



•

The terminal shall decline the transaction after the 2nd GENERATE AC.



2CJ.203.01 Enhanced Combined DDA/AC failed when ICC responded with TC (2) •

The following 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

•


•



Page 1320



responded with TC and Enhanced Combined DDA/AC failed (2nd GENERATE AC) Reference EMV 4.0: Reference Book2 - Section 6.6.2 – Dynamic Signature Verification EMV 4.1:

Book3 - Section 10.3 - Offline Data Authentication Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA request at Configuration: GENAC2, TC] supported Conditions:

•


•


•


•


•

LT responds ARQC to the 1st GENERATE AC and Digital signature is valid (when CDA requested).



•


•






•



Page 1322



responded with TC and Enhanced Combined DDA/AC failed (2nd GENERATE AC) Reference EMV 4.0: Reference Book2 - Section 6.6.2 – Dynamic Signature Verification EMV 4.1:

Book3 - Section 10.3 - Offline Data Authentication Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND ([Online Only] AND [Normal Default Action Code Configuration: processing]) supported Conditions:

•


•

TAC and IAC are set so that an ARQC is requested at first GENERATE AC and a TC at second GENERATE AC

•


•


•

LT responds ARQC to the 1st GENERATE AC and Digital signature is valid (when CDA requested).



•


•






•



Page 1324


Generate AC Command coding



2CK.001.00 CDOL1 for the first GENERATE AC Test No: 2CK.001.00 - Revision 10c - Number of sub cases: 3 Objective: To ensure that the terminal supports valid CDOL1.

To ensure that the terminal checks that mandatory Data Object CDOL1 is present in the card and use it. To ensure that the terminal is able to build GENERATE AC Data field according to CDOL1 rules. Reference Book 3 - Section 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0:

Book 3 - Section 3.1 - Mandatory Data Objects Book 3 - Section 5.2.1 - Card Risk Management Data Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1:

Book 3 - Section 7.2 - Mandatory Data Objects Book 3 - Section 9.2.1 - Card Risk Management Data Terminal NA Configuration: Conditions:

•

Case 01: CDOL1 contains date of the day, terminal type, PAN

•

Case 02: CDOL1 contains transaction amount, terminal type, transaction amount

•

Case 03: CDOL1 contains Issuer Authentication Data, Transaction Amount

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall return a GENERATE AC command to the LT with

Data field correctly filled according to CDOL1


Page 1326


2CK.002.00 CDOL2 for the second GENERATE AC Test No: 2CK.002.00 - Revision 10c - Number of sub cases: 3 Objective: To ensure that the terminal supports a valid CDOL2.

To ensure that the terminal checks that mandatory Data Object CDOL2 is present in the card and uses it. To ensure that the terminal is able to build GENERATE AC Data field according to CDOL2 rules. Reference Book 3 - Section 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0:

Book 3 - Section 3.1 - Mandatory Data Objects Book 3 - Section 5.2.1 - Card Risk Management Data Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1:

Book 3 - Section 7.2 - Mandatory Data Objects Book 3 - Section 9.2.1 - Card Risk Management Data Terminal NA Configuration: Conditions:

•

First GENERATE AC returns ARQC.

•

Case 01: CDOL2 contains date of the day, terminal type, PAN

•

Case 02: CDOL2 contains transaction amount, terminal type, transaction amount

•

Case 03: CDOL2 contains Issuer Authentication Data, Transaction Amount

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall return a second GENERATE AC command to the LT

with Data field correctly filled according to CDOL2



2CK.003.00 CDOL requests a TC Hash Value and TDOL is present in the ICC Test No: 2CK.003.00 - Revision 10c - Number of sub cases: 0 Objective: To ensure that the terminal supports a valid TDOL.

To ensure that if TC Hash Value is requested in CDOL, the terminal is able to calculate TC Hash value according to the TDOL provided by the card. Reference Book 3 - Section 1.4 - Rules for Using a Data Object List (DOL) EMV 4.0:

Book 3 - Section 5.2.2 - Transaction Certificate Data Reference Book 3 - Section 5.4 - Rules for Using a Data Object List (DOL) EMV 4.1:

Book 3 - Section 9.2.2 - Transaction Certificate Data Terminal NA Configuration: Conditions:

•

LT contains TDOL

•

CDOL1 requests TC Hash value


Data field containing a TC Hash value correctly calculated


Page 1328


2CK.004.00 CDOL requests a TC Hash Value and TDOL is not present in the ICC Test No: 2CK.004.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that if TC Hash Value is requested in CDOL, and TDOL is

not provided by the card, the terminal is able to calculate TC Hash value according to the default TDOL contained in the terminal, and that it sets the 'Default TDOL used' bit in the TVR to 1b. Reference Book 3 - Section 5.2.2 - Transaction Certificate Data EMV 4.0: Reference Book 3 - Section 9.2.2 - Transaction Certificate Data EMV 4.1: Terminal [Default TDOL] supported Configuration:

The default TDOL value is known Conditions:

•

LT does not contains TDOL

•



Data field containing a TC Hash value correctly calculated with default TDOL as input TVR byte 5, bit 8 = '1' (ie Default TDOL used) received at 1st GENERATE AC.



2CK.005.00 CDOL requests a TC Hash Value and neither TDOL nor default TDOL is present Test No: 2CK.005.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if TC Hash Value is requested in CDOL, TDOL is not

provided by the card and there is no default TDOL in terminal, the terminal is able to calculate TC Hash value using a TDOL with no data object. Reference Book 3 - Section 5.2.2 - Transaction Certificate Data EMV 4.0:

Book Bulletins - Section AN 11 - Bulletin n°11, Setting of Default TDOL Used Bit in TVR (Jun-2003) Reference Book 3 - Section 9.2.2 - Transaction Certificate Data EMV 4.1: Terminal [Default TDOL] not supported Configuration: Conditions:

•

LT does not contain TDOL

•



•

The terminal shall return a GENERATE AC command to the LT with Data field containing a TC Hash value correctly calculated with a TDOL with no entry

•

TVR byte 5, bit 8 = '0' (ie Default TDOL not used) received at 1st GENERATE AC.


Page 1330


2CK.005.01 CDOL requests a TC Hash Value and neither TDOL nor default TDOL is present (2) Test No: 2CK.005.01 - Revision 12 - Number of sub cases: 0 Objective: To ensure that if TC Hash Value is requested in CDOL, TDOL is not

provided by the card and there is no default TDOL in terminal, the terminal is able to calculate TC Hash value using a TDOL with no data object. Reference Book 3 - Section 5.2.2 - Transaction Certificate Data EMV 4.0:

Book Bulletins - Section AN 11 - Bulletin n°11, Setting of Default TDOL Used Bit in TVR (Jun-2003) Reference Book 3 - Section 9.2.2 - Transaction Certificate Data EMV 4.1: Terminal [Default TDOL] supported Configuration:

Default TDOL not present Conditions:

•

LT does not contain TDOL

•



data field containing a calculated TC Hash value with no input data •

TVR byte 5, bit 8 = '0' (ie Default TDOL not used) received at 1st GENERATE AC.



2CK.006.00 CDOL requests a TC Hash Value during the second GENERATE AC Test No: 2CK.006.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that if TC Hash Value is requested in CDOL2, the terminal

ensures that the data provided in the TC Hash value is current at the time the command is issued. Reference Book 3 - Section 5.2.2 - Transaction Certificate Data EMV 4.0: Reference Book 3 - Section 9.2.2 - Transaction Certificate Data EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•

LT contains TDOL

•

TDOL requests TSI

•


•

LT returns ARQC to first GENERATE AC.

•

Issuer Authentication is supported and performed


•

The terminal shall return a second GENERATE AC command to the LT with Data field containing a TC Hash value correctly calculated (in particular with TSI with 'Issuer Authentication was performed ' bit set)

•

TSI received at 1st GENERATE AC byte 1, bit 5 = '0' (ie Issuer Authentication was not performed

•

TSI received at 2nd GENERATE AC byte 1, bit 5 = '1' (ie Issuer Authentication was performed


Page 1332


2CK.007.00 Terminal requests a TC on first GENERATE AC Test No: 2CK.007.00 - Revision 11 - Number of sub cases: 3 Objective: To ensure that if the terminal requests a TC in first GENERATE AC, it

supports AAC, or ARQC or TC in the response from the card. Reference Book 3 - Section 5.3.1 - GENERATE AC (First Issuance) EMV 4.0:

Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Reference Book 3 - Section 9.3.1 - GENERATE AC (First Issuance) EMV 4.1:

Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Terminal [Offline Only or Offline/Online capable] supported Configuration: Conditions:

•

IAC and TAC set so that Terminal requests TC on first GENERATE AC.

•

Case 01: LT returns AAC in the response to first GENERATE AC

•

Case 02: LT returns ARQC in the response to first GENERATE AC

•

Case 03: LT returns TC in the response to first GENERATE AC

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall process the transaction until completion according to

the type of cryptogram received



2CK.008.00 Terminal requests an ARQC on first GENERATE AC Test No: 2CK.008.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that if the terminal requests an ARQC in first GENERATE

AC, it supports AAC, or ARQC in the response from the card. Reference Book 3 - Section 5.3.1 - GENERATE AC (First Issuance) EMV 4.0:

Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Reference Book 3 - Section 9.3.1 - GENERATE AC (First Issuance) EMV 4.1:

Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•

IAC and TAC set so that Terminal requests ARQC on first GENERATE AC.

•

Case 01: LT returns AAC in the response to first GENERATE AC

•

Case 02: LT returns ARQC in the response to first GENERATE AC


the type of cryptogram received.


Page 1334


2CK.009.00 Terminal requests an AAC on first GENERATE AC Test No: 2CK.009.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that if the terminal requests an AAC in first GENERATE AC,

it supports only AAC in the response from the card. Reference Book 3 - Section 5.3.1 - GENERATE AC (First Issuance) EMV 4.0: Reference Book 3 - Section 9.3.1 - GENERATE AC (First Issuance) EMV 4.1: Terminal NA Configuration: Conditions:

•

IAC and TAC set so that Terminal requests AAC on first GENERATE AC.

•

LT returns AAC in the response to first GENERATE AC.


the type of cryptogram received.



2CK.010.00 Card responds with an ARQC on first GENERATE AC Test No: 2CK.010.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that if the card responds with an ARQC to first GENERATE

AC and is permitted to do so and if terminal has online capability, the terminal prepares and sends an authorization or financial request message Reference Book 3 - Section 5.3.1 - GENERATE AC (First Issuance) EMV 4.0: Reference Book 3 - Section 9.3.1 - GENERATE AC (First Issuance) EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration:

Terminal Action Code Denial has all bits set to 0b. Conditions:

•

Issuer Action Code Denial has all bits set to 0b to prevent the terminal from requesting an AAC on the first GENERATE AC.

•

LT returns ARQC in the response to first GENERATE AC.

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall prepare and send an authorization or financial

request message.


Page 1336


2CK.012.00 Card responds with a TC on first GENERATE AC Test No: 2CK.012.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the card responds with a TC to first GENERATE AC

and is permitted to do so, the terminal completes the transaction offline (accepted). Reference Book 3 - Section 5.3.1 - GENERATE AC (First Issuance) EMV 4.0: Reference Book 3 - Section 9.3.1 - GENERATE AC (First Issuance) EMV 4.1: Terminal [Offline Only or Offline/Online capable] supported Configuration:

All Terminal Action Codes have all bits set to 0b. Conditions:

•

All Issuer Action Codes have all bits set to 0b.

•

LT returns TC in the response to first GENERATE AC.

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall complete the transaction offline (accepted).



2CK.013.00 Card responds with a AAC on first GENERATE AC Test No: 2CK.013.00 - Revision 11 - Number of sub cases: 3 Objective: To ensure that if the card responds with an AAC to first GENERATE

AC, the terminal completes the transaction offline (declined). To ensure that the terminal declines the transaction if the card returned a Decline to GENERATE AC. Reference Book 3 - Section 5.3.1 - GENERATE AC (First Issuance) EMV 4.0:

Book 4 - Section 2.3.7 - Card Action Analysis Reference Book 3 - Section 9.3.1 - GENERATE AC (First Issuance) EMV 4.1:

Book 4 - Section 6.3.7 - Card Action Analysis Terminal NA Configuration: Conditions:

•

Case 01: IAC and TAC set so that the Terminal requests an AAC in first GENERATE AC, ICC responds with AAC.

•

Case 02: IAC and TAC set so that the Terminal requests an ARQC in first GENERATE AC, ICC responds with AAC and Terminal is [Online Only or Offline/Online capable].

•

Case 03: IAC and TAC set so that the Terminal requests a TC in first GENERATE AC, ICC responds with AAC and Terminal is [Offline Only or Offline/Online capable].

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall complete the transaction offline (declined).


Page 1338


2CK.015.00 Terminal requests an AAC on second GENERATE AC Test No: 2CK.015.00 - Revision 11 - Number of sub cases: 3 Objective: To ensure that if the terminal requests an AAC in second GENERATE

AC, it supports an AAC in the response from the card. To ensure that the terminal declines the transaction if the card returned a Decline to GENERATE AC. Reference Book 3 - Section 5.3.2 - GENERATE AC (Second Issuance) EMV 4.0:

Book 4 - Section 2.3.7 - Card Action Analysis Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Reference Book 3 - Section 9.3.2 - GENERATE AC (Second Issuance) EMV 4.1:

Book 4 - Section 6.3.7 - Card Action Analysis Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•

IAC set so that Terminal requests ARQC on first GENERATE AC.

•

Host Source shall return denial response in the authorization response

•

Case 01: LT returns AAC in the response to second GENERATE AC

•

Case 02: LT returns ARQC in the response to second GENERATE AC

•

Case 03: LT returns TC in the response to second GENERATE AC

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall decline the transaction.




Page 1340


2CK.016.00 Terminal requests an TC on second GENERATE AC Test No: 2CK.016.00 - Revision 10a - Number of sub cases: 2 Objective: To ensure that if the terminal requests an TC in second GENERATE

AC, it supports AAC or TC in the response from the card. Reference Book 3 - Section 5.3.2 - GENERATE AC (Second Issuance) EMV 4.0: Reference Book 3 - Section 9.3.2 - GENERATE AC (Second Issuance) EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration:

TAC are set so that the terminal request a TC on second GENERATE AC Conditions:

•

IAC set so that Terminal requests ARQC on first GENERATE AC. and TC on second GENERATE AC.

•

Case 01: LT returns TC in the response to second GENERATE AC

•

Case 02: LT returns AAC in the response to second GENERATE AC

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall either decline or accept the transaction depending

on the LT response



2CK.017.00 Cryptogram at a higher level than requested (1) Test No: 2CK.017.00 - Revision 11 - Number of sub cases: 3 Objective: To ensure that the terminal terminates the transaction if the card

responds with a cryptogram with higher level than the one requested in first GENERATE AC. Reference Book 3 - Section 5.3 - Command Use EMV 4.0:

Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Reference Book 3 - Section 9.3 - Command Use EMV 4.1:

Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Terminal NA Configuration: Conditions:

•

Case 01: IAC and TAC set so that the Terminal requests an AAC in first GENERATE AC, ICC responds with TC

•

Case 02: IAC and TAC set so that the Terminal requests an AAC in first GENERATE AC, ICC responds with ARQC.

•

Case 03: IAC and TAC set so that the Terminal requests an ARQC in first GENERATE AC, ICC responds with TC and Terminal is [Online Only or Offline/Online capable]



Page 1342


2CK.018.00 Cryptogram at a higher level than requested (2) Test No: 2CK.018.00 - Revision 12 - Number of sub cases: 3 Objective: To ensure that the terminal completes the transaction and considers

the cryptogram as an AAC if the card responds with a cryptogram of higher level than the one requested in second GENERATE AC. Reference Book 3 - Section 5.3 - Command Use EMV 4.0: Reference Book 3 - Section 9.3 - Command Use EMV 4.1: Terminal [Online Only OR Offline/Online capable] supported Configuration: Conditions: TAC/IAC-Decline & TAC/IAC-Online do not match any TVR bits prior to

the 1st GENERATE AC , resulting in a ARQC request. The LT responds with an ARQC. •

Case 01: Issuer host declines, resulting in a decline. The LT responds with a TC

•

Case 02: Issuer host declines, resulting in an ACC. TAC/IACDefault match at least 1 TVR bit prior to the 2nd GENERATE AC, resulting in an AAC request. The LT responds with ARQC

•

Case 03: Issuer hot approval, resulting in a TC. The LT responds with ARQC.

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: In all cases, the terminal shall complete the transaction and consider

the cryptogram as an AAC (declined)



2CK.018.01 Cryptogram at a higher level than requested (3) Test No: 2CK.018.01 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the terminal completes the transaction and considers

the cryptogram as an AAC if the card responds with a cryptogram of higher level than the one requested in second GENERATE AC. Reference Book 3 - Section 5.3 - Command Use EMV 4.0: Reference Book 3 - Section 9.3 - Command Use EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•

TAC/IAC-Decline, TAC/IAC-Online & TAC/IAC-Default do not match any TVR bits prior to the 1st GENERATE AC, result in a TC request. The LT responds with an ARQC.

•

TAC/IAC-Default match no bits in the TVR prior to the 2nd GENERATE AC, resulting in a TC request. The LT responds with an ARQC.

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: In all cases, the terminal shall complete the transaction and consider

the cryptogram as an AAC (declined)


Page 1344


Errorneous or Missing Data in ICC



2CL.001.00 Mandatory data objects missing: FCI (1) Test No: 2CL.001.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal switches to 'list of AIDs' method if

mandatory FCI is missing in a response to SELECT command during the 'select by PSE' process. Reference Book 1 - Section 7.3.4 - Data Field Returned in the Response Message EMV 4.0:

Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response EMV 4.1: Message

Book 1 - Section 12.3.2 - Using the PSE Terminal [PSE] supported Configuration: Conditions:

•

LT contains PSE.

•

LT contains DDF.

•

Case 01: LT response to SELECT PSE does not contain the FCI Data object (entire data missing: TLV)

•

Case 02: LT response to SELECT DDF does not contain the FCI Data object (entire data missing: TLV)


•

The terminal shall switch to List of AIDs selection, transmitting a SELECT command for each AID it supports

•



Page 1346


2CL.001.01 Mandatory data objects missing: Final SELECT Test No: 2CL.001.01 - Revision 11 - Number of sub cases: 3 Objective: To ensure that the terminal continues with final selection when

mandatory data is missing in a response to the final SELECT command Reference Book 1 - Section 7.3.4 - Data Field Returned in the Response Message EMV 4.0:

Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 11.3.4 - Data Field Returned in the Response EMV 4.1: Message Terminal NA Configuration: Conditions:

•

Case 01: LT response to final SELECT does not contain the FCI Data object (entire data missing: TLV)

•

Case 02: LT response to final SELECT does not contain the DF Name Data object (entire data missing: TLV)

•

Case 03: LT response to final SELECT does not contain FCI Proprietary Template Data object (entire data missing: TLV)


•

The terminal shall remove the selected application from candidate list

•

The terminal shall resume the final selection process

•




2CL.001.02 Mandatory data objects missing: FCI (2) Test No: 2CL.001.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal removes application from candidate list if

mandatory FCI is missing in a response to SELECT ADF Reference Book 1 - Section 7.3.4 - Data Field Returned in the Response Message EMV 4.0:


Book 1 - Section 12.4 - Final Selection Terminal NA Configuration: Conditions:

•

LT does not contains PSE.

•

LT and terminal support mutually two ADF with same priority

•

LT response to SELECT ADF 1 does not contains the FCI Data object (entire data missing: TLV) when building the candidate list


•

The terminal shall process the transaction until completion with ADF 2, by requesting a TC or an AAC.


Page 1348


2CL.002.00 Mandatory data objects missing: DF Name Test No: 2CL.002.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that if the terminal supports PSE selection and mandatory

DF Name is missing in a response to SELECT PSE or DDF or ADF command, it switches to List of AID method Reference Book 1 - Section 7.3.4 - Data Field Returned in the Response Message EMV 4.0:



•

LT contains PSE.

•

LT contains DDF.

•

Case 01: LT response to SELECT PSE does not contain the DF Name Data object (entire data missing: TLV)

•

Case 02: LT response to SELECT DDF does not contain the DF Name Data object (entire data missing: TLV)

Action: NA Procedure: Application selection with PSE process is performed by the LT Pass Criteria:

•


•


•




2CL.002.01 Mandatory data objects missing: DF Name (2) Test No: 2CL.002.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal removes application from candidate list if

mandatory DF name is missing in a response to SELECT ADF Reference Book 1 - Section 7.3.4 - Data Field Returned in the Response Message EMV 4.0:



•

LT does not contain PSE

•


•

LT response to SELECT ADF 1 does not contains the DF Name Data object (entire data missing: TLV) when building the candidate list

Action: NA Procedure: Application selection is performed by the LT Pass Criteria:

•



Page 1350


2CL.003.00 Mandatory data objects missing: SFI Test No: 2CL.003.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that if the terminal supports selection with PSE and

mandatory SFI is missing in a response to SELECT PSE or DDF command, it switches to List of AID method Reference Book 1 - Section 7.3.4 - Data Field Returned in the Response Message EMV 4.0:



•

LT contains PSE.

•

LT contains DDF.

•

Case 01: LT response to SELECT PSE does not contain the SFI Data object (entire data missing: TLV)

•

Case 02: LT response to SELECT DDF does not contain the SFI Data object (entire data missing: TLV)

Action: NA Procedure: Application selection process with PSE is performed by the LT Pass Criteria:

•


•


•




2CL.003.05 Mandatory data objects missing in directory entry: DDF Name Test No: 2CL.003.05 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the terminal supports selection with PSE and

mandatory DDF Name is missing in a DDF Directory entry of the Payment System Directory, it switches to List of AIDs method. Reference Book 1 - Section 8.2.3 - Coding of a Payment System’s Directory EMV 4.0:

Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 12.2.3 - Coding of a Payment System Directory EMV 4.1:


•

LT contains PSE

•

LT contains a DDF1 under the PSE

•

LT contains a DDF2 under the DDF1

•

Case 01: DDF1 Name data object (entire data missing: TLV) is not present in entry when processing PSE Directory file

•

Case 02: DDF2 Name data object (entire data missing: TLV) is not in entry present when processing DDF1 Directory file


•


•


•



Page 1352


2CL.004.00 Mandatory data objects missing in directory entry: ADF Name Test No: 2CL.004.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the terminal supports selection with PSE and

mandatory ADF Name is missing in a ADF Directory entry of the Payment System Directory, it switches to List of AIDs method. Reference Book 1 - Section 8.2.3 - Coding of a Payment System’s Directory EMV 4.0:



•

Payment System Directory of LT contains an ADF Directory entry

•

ADF Name data object (entire data missing: TLV) is not present in this entry

Action: NA Procedure: Application selection process is performed by the LT Pass Criteria:

•


•


•




2CL.004.01 Mandatory data objects missing in directory entry: ADF Name (2) Test No: 2CL.004.01 - Revision 11 - Number of sub cases: 00 Objective: To ensure that if the terminal supports selection with PSE and DDF is

present and mandatory ADF Name is missing in a ADF Directory entry of the DDF, it switches to List of AIDs method. Reference Book 1 - Section 8.2.3 - Coding of a Payment System’s Directory EMV 4.0:



•

LT contains PSE.

•

LT contains DDF.

•

DDF Directory of LT contains an ADF Directory entry

•

ADF name data object (entire data missing: TLV) is not present in this entry


•


•


•



Page 1354


2CL.005.00 Mandatory data objects missing in directory entry: Application Label Test No: 2CL.005.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal switches to List of AIDs method if

mandatory Application Label is missing from an ADF while the terminal is reading the PSE. Reference Book 1 - Section 8.2.3 - Coding of a Payment System’s Directory EMV 4.0:



•

PSE Directory of LT contains an ADF Directory entry

•

Application Label data object (entire data missing: TLV) is not present in this entry


•


•


•




2CL.005.01 Mandatory data objects missing in directory entry: Application Label (2) Test No: 2CL.005.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the terminal supports selection with PSE and DDF is

present and mandatory application Label is missing in a ADF Directory entry of the DDF, it switches to List of AIDs method. Reference Book 1 - Section 8.2.3 - Coding of a Payment System’s Directory EMV 4.0:



•

LT contains PSE.

•

LT contains DDF.

•

DDF Directory of LT contains an ADF Directory entry

•

Application Label data object (entire data missing: TLV) is not present in this entry


•


•


•



Page 1356


2CL.006.00 Mandatory data objects missing: FCI Proprietary Template Test No: 2CL.006.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal switch to list of AIDs method if mandatory

FCI Proprietary Template (tag A5) is missing in a response to SELECT ADF, PSE or DDF command Reference Book 1 - Section 7.3.4 – Data Field Returned in the Response EMV 4.0: Message



•

LT contains PSE.

•

LT contains DDF.

•

Case 01: LT response to SELECT PSE does not contain FCI Proprietary Template data object (entire data missing: TLV)

•

Case 02: LT response to SELECT DDF does not contain FCI Proprietary Template data object (entire data missing: TLV)


•


•


•




2CL.006.01 Mandatory data objects missing: FCI Proprietary Template (2) Test No: 2CL.006.01 - Revision 11 - Number of sub cases: 1 Objective: To ensure that the terminal removes from the candidate list the

application if mandatory FCI Proprietary Template is missing in a response to SELECT ADF command Reference Book 1 - Section 7.3.4 - Data Field Returned in the Response Message EMV 4.0:



•


•


•

LT response to SELECT ADF 1 does not contains FCI Proprietary Template data object (entire data missing: TLV) when building the candidate list


•



Page 1358


2CL.007.00 Mandatory data objects missing: AFL Test No: 2CL.007.00 - Revision 15 - Number of sub cases: 3 Objective: To ensure that the terminal terminates the transaction if mandatory AFL

is missing in a response to GET PROCESSING OPTIONS command Reference Book 3 - Section 3.3 - Data Retrievable by GET PROCESSING EMV 4.0: OPTIONS

Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC Reference Book 3 - Section 7.4 - Data Retrievable by GET PROCESSING EMV 4.1: OPTIONS

Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC Book Bulletins - Section SU 54 - Bulletin No.54, Missing Mandatory Command Response Data (Nov 2006) Terminal NA Configuration: Conditions:

•

Case 01: LT response to GET PROCESSING OPTIONS in format 1, and the AFL value is missing.

•

Case 02: LT response to GET PROCESSING OPTIONS in format 2, and the AFL value is missing from the TLV data object (94 00).

•

Case 03: LT response to GET PROCESSING OPTIONS in format 2, the AFL TLV data object is missing in its entierity.




2CL.008.00 Mandatory data objects missing: AIP Test No: 2CL.008.00 - Revision 1( - Number of sub cases: 3 Objective: To ensure that the terminal terminates the transaction if mandatory AIP

is missing in a response to GET PROCESSING OPTIONS command Reference Book 3 - Section 3.3 - Data Retrievable by GET PROCESSING EMV 4.0: OPTIONS

Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC Reference Book 3 - Section 7.4 - Data Retrievable by GET PROCESSING EMV 4.1: OPTIONS

Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC Book Bulletins - Section SU 54 - Bulletin No.54, Missing Mandatory Command Response Data (Nov 2006) Terminal NA Configuration: Conditions:

•

Case 01: LT response to GET PROCESSING OPTIONS in format 1, and the AIP value is missing.

•

Case 02: LT response to GET PROCESSING OPTIONS in format 2, and the AIP value is missing from the TLV data object. (82 00)

•

Case 03: LT response to GET PROCESSING OPTIONS in format 2, the AIP TLV data object is missing in its entierity.



Page 1360


2CL.009.00 Mandatory data objects missing: CDOL1 Test No: 2CL.009.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal terminates the transaction if mandatory

CDOL1 is missing in the card Reference Book 3 - Section 3.1 - Mandatory Data Objects EMV 4.0:

Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC Reference Book 3 - Section 7.2 - Mandatory Data Objects EMV 4.1:

Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC Terminal NA Configuration: Conditions:

•

Case 01: LT does not contain CDOL1 data object (entire data missing: TLV)

•

Case 02: LT contains CDOL1 with a length equal to zero




2CL.010.00 Mandatory data objects missing: CDOL2 Test No: 2CL.010.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal terminates the transaction if mandatory

CDOL2 is missing in the card Reference Book 3 - Section 3.1 - Mandatory Data Objects EMV 4.0:



•

Case 01: LT does not contain CDOL2 data object (entire data missing: TLV)

•

Case 02: LT contains CDOL2 with a length equal to zero



Page 1362


2CL.011.00 Mandatory data objects missing: PAN Test No: 2CL.011.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal terminates the transaction if mandatory

PAN is missing in the card Reference Book 3 - Section 3.1 - Mandatory Data Objects EMV 4.0:



•

Case 01: LT does not contain PAN data object (entire data missing: TLV)

•

Case 02: LT contains PAN with a length equal to zero




2CL.012.00 Mandatory data objects missing: Application Expiration Date Test No: 2CL.012.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal terminates the transaction if mandatory

Application Expiration Date is missing in the card Reference Book 3 - Section 3.1 - Mandatory Data Objects EMV 4.0:



•

Case 01: LT does not contain Application Expiration Date data object (entire data missing: TLV)

•

Case 02: LT contains Application Expiration Date with a length equal to zero



Page 1364


2CL.013.00 ATC not returned by GET DATA and Both LCOL and UCOL are present Test No: 2CL.013.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b

if both Lower and Upper Consecutive Offline Limit data objects are present in the ICC and if the ATC is not returned by the GET DATA. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•

AIP of LT indicates TRM to be performed (AIP Byte 1 bit 4 = '1')

•

Lower and Upper Consecutive Offline Limit are present in LT

•



•


•


•


•


•




2CL.014.00 Last Online ATC Register not returned by GET DATA and Both LCOL and UCOL are present Test No: 2CL.014.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that terminal sets the 'ICC data missing' bit in the TVR to 1b

if both Lower and Upper Consecutive Offline Limit data objects are present in the ICC and if the Last Online ATC is not returned by the GET DATA. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal [Velocity Checking] supported Configuration: Conditions:

•

AIP of LT indicates TRM to be performed (AIP byte 1 bit 4= '1')

•

Lower and Upper Consecutive Offline Limit are present in LT

•

Last Online ATC is not returned by GET DATA


•


•


•


•


•



Page 1366


2CL.019.00 Issuer Public Key Certificate not present and Offline SDA is supported in AIP Test No: 2CL.019.00 - Revision 11 - Number of sub cases: 0 Objective: 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 Issuer Public Key Certificate is missing in the card. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•

AIP of LT indicates Offline Static Data Authentication is supported (AIP byte 1 bit 7 = '1')

•

Issuer Public Key Certificate data object (entire data missing: TLV) is not present in LT


•


•


•

TVR byte 1, bit 8 = '0' (ie Offline data authentication was performed) received at 1st GENERATE AC.

•

TVR byte 1, bit 7 = '1' (ie Static Data Authentication failed) received at 1st GENERATE AC.

•


•




2CL.021.00 Issuer Public Key Exponent not present and Offline SDA is supported in AIP Test No: 2CL.021.00 - Revision 11 - Number of sub cases: 0 Objective: 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 Issuer Public Key Exponent is missing in the card. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

Issuer Public Key Exponent data object (entire data missing: TLV) is not present in LT


•


•


•


•


•


•



Page 1368


2CL.023.00 Issuer Public Key Remainder not present and Offline SDA is supported in AIP Test No: 2CL.023.00 - Revision 11 - Number of sub cases: 0 Objective: 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 Issuer Public Key Remainder is missing in the card and the length of the recovered Issuer Public Key indicates that Issuer Public Key Remainder should be present. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

Issuer Public Key Remainder data object (entire data missing: TLV) is not present in LT

•

Size of Issuer Public Key and CA Public Key is such as NI > NCA - 36


•


•


•


•


•




2CL.023.00 Issuer Public Key Remainder not present and Offline SDA is supported in AIP •



Page 1370


2CL.023.01 Issuer Public Key Remainder not present and Offline SDA is supported in AIP (implied) Test No: 2CL.023.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal performs the SDA, if Offline Static Data

Authentication is supported in AIP and Issuer Public Key Remainder is missing in the card and the length of the recovered Issuer Public Key indicates that Issuer Public Key Remainder should not be present. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•


•

Size of Issuer Public Key and CA Public Key is such as NI < NCA - 36


•


•


•


•

TVR byte 1, bit 6 = '0' (ie ICC Data not missing) received at 1st GENERATE AC.

•


•




2CL.023.01 Issuer Public Key Remainder not present and Offline SDA is supported in AIP (implied) used) received at 1st GENERATE AC.


Page 1372


2CL.024.00 Issuer Public Key Remainder not present and Offline DDA is supported in AIP Test No: 2CL.024.00 - Revision 11 - Number of sub cases: 0 Objective: 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 Remainder is missing in the card and the length of the recovered Issuer Public Key indicates that Issuer Public Key Remainder should be present. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•

AIP of LT indicates Offline Dynamic Data Authentication is supported (AIP byte 1 bit 6 = '1')

•


•



•


•


•


•


•




2CL.024.00 Issuer Public Key Remainder not present and Offline DDA is supported in AIP •



Page 1374


2CL.024.01 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (2) Test No: 2CL.024.01 - Revision 13 - Number of sub cases: 0 Objective: 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 Remainder is missing in the card and the length of the recovered Issuer Public Key indicates that Issuer Public Key Remainder should be present. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1:


•

AIP of LT indicates CDA is supported (AIP byte 1 bit 1 = '1')

•


•



•


•


•


•


•

TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed) received at 1st GENERATE AC.



2CL.024.01 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (2) •


•



Page 1376


2CL.024.02 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (implied) Test No: 2CL.024.02 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal performs the Dynamic Data Authentication, if

Offline Dynamic Data Authentication is supported in AIP and Issuer Public Key Remainder is missing in the card and the length of the recovered Issuer Public Key indicates that Issuer Public Key Remainder should not be present. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•


•



•


•


•


•




2CL.024.03 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (2) (implied) Test No: 2CL.024.03 - Revision 11 - Number of sub cases: 0 Objective: To ensure that terminal peforms the Combined DDA/AC Data

Authentication, if Offline Combined DDA/AC Data Authentication is supported in AIP and Issuer Public Key Remainder is missing in the card and the length of the recovered Issuer Public Key indicates that Issuer Public Key Remainder should not be present. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•


•



•


•

TVR byte 1, bit 3 = '0' (ie Offline Combined DDA/AC Data Authentication succeeded) contained in Financial Confirmation message or Batch Data Capture message

•


•


•

TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) contained in Financial Confirmation message or Batch Data Capture message

•

TVR byte 1, bit 6 = '0' (ie ICC Data not missing) received at 1st


Page 1378


2CL.024.03 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (2) (implied) GENERATE AC.






•


•


•


•



•


•

TVR byte 1, bit 6 = '1' (ie ICC Data missing) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example.

•

TVR byte 1, bit 8 = '0' (ie Offline data authentication was


Page 1380


2CL.024.04 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (5) performed) received at 1st GENERATE AC. •

TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example.

•


•






Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND ([Online Only] supported AND [CDA request at Configuration: GENAC1, ARQC]supported AND [CDA failure not detected prior TAA]


•


•


•


•


•



•


•

TVR byte 1, bit 6 = '1' (ie ICC Data missing) received at 2nd GENERATE AC.

•



Page 1382


2CL.024.05 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (6) •


•


•








•


•


•

IAC’s and TAC’s are set so that an ARQC is requested at first Gen AC.

•


•


•



•


•

TVR byte 1, bit 6 = '1' (ie ICC Data missing) contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form


Page 1384


2CL.024.06 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (7) such as receipt for example. •

TVR byte 1, bit 8 = '1' (ie Offline data authentication was not performed) received at 1st GENERATE AC.

•

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 or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example.

•


•






Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND ([Online Only] supported AND [CDA never at Configuration: GENAC1, ARQC] supported AND [Normal Default Action Code


•


•


•


•


•


•



•


•

TVR byte 1, bit 6 = '1' (ie ICC Data missing) contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the


Page 1386


2CL.024.07 Issuer Public Key Remainder not present and Offline DDA is supported in AIP (8) terminal has the capability to show the TVR value in any form such as receipt for example. •


•


•


•




2CL.028.00 ICC Public Key Remainder not present and Offline DDA is supported in AIP Test No: 2CL.028.00 - Revision 11 - Number of sub cases: 0 Objective: 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 Remainder is missing in the card and the length of the recovered ICC Public Key indicates that ICC Public Key Remainder should be present. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

ICC Public Key Remainder data object (entire data missing: TLV) is not present in LT

•

Size of ICC Public Key and Issuer Public Key is such as NICC > NI - 42


•


•


•


•


•


•



Page 1388


2CL.028.00 ICC Public Key Remainder not present and Offline DDA is supported in AIP received at 1st GENERATE AC.



2CL.028.01 ICC Public Key Remainder not present and Offline DDA is supported in AIP (2) Test No: 2CL.028.01 - Revision 13 - Number of sub cases: 0 Objective: 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 Remainder is missing in the card and the length of the recovered ICC Public Key indicates that ICC Public Key Remainder should be present. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1:


•


•


•



•


•


•


•


•

TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed) received at 1st GENERATE AC.

•



Page 1390


2CL.028.01 ICC Public Key Remainder not present and Offline DDA is supported in AIP (2) received at 1st GENERATE AC. •




2CL.028.02 ICC Public Key Remainder not present and Offline DDA is supported in AIP (implied) Test No: 2CL.028.02 - Revision 16 - Number of sub cases: 2 Objective: To ensure that terminal performs the Dynamic Data Authentication, if

Offline Dynamic Data Authentication is supported in AIP and ICC Public Key Remainder is missing in the card and the length of the recovered ICC Public Key indicates that ICC Public Key Remainder should not be present. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

Size of ICC Public Key and Issuer Public Key is such as NICC < NI – 42

•

Case 01 - ICC Public Key Remainder data object is not present in LT (entire data object missing: TLV)

•

Case 02 - ICC Public Key Remainder data object is coded with a length of '00' in LT


•


•


•


•


•



Page 1392


2CL.028.02 ICC Public Key Remainder not present and Offline DDA is supported in AIP (implied) used) received at 1st GENERATE AC. •




2CL.028.03 ICC Public Key Remainder not present and Offline DDA is supported in AIP (2) (implied) Test No: 2CL.028.03 - Revision 16 - Number of sub cases: 2 Objective: To ensure that terminal peforms the Combined DDA/AC Data

Authentication, if Offline Combined DDA/AC Data Authentication is supported in AIP and ICC Public Key Remainder is missing in the card and the length of the recovered ICC Public Key indicates that ICC Public Key Remainder should not be present. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•

Size of ICC Public Key and Issuer Public Key is such as NICC < NI – 42

•

Case 01 - ICC Public Key Remainder data object is not present in LT (entire data object missing: TLV)

•

Case 02 - ICC Public Key Remainder data object is coded with a length of '00' in LT


•


•

TVR byte 1, bit 3 = '0' (ie Offline Combined DDA/AC Data Authentication succeeded) contained in Financial Confirmation message or Batch Data Capture message

•


•


•



Page 1394


2CL.028.03 ICC Public Key Remainder not present and Offline DDA is supported in AIP (2) (implied) Batch Data Capture message •

TVR byte 1, bit 6 = '0' (ie ICC Data not missing) contained in Financial Confirmation message or Batch Data Capture message.




if Offline Combined DDA/AC Data Authentication is supported in AIP and ICC Public Key Remainder is missing in the card and the length of the recovered ICC Public Key indicates that ICC Public Key Remainder should be present. Reference EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1:


•


•


•


•



•


•

TVR byte 1, bit 6 = '1' (ie ICC Data missing) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example.

•

TVR byte 1, bit 8 = '0' (ie Offline data authentication was


Page 1396


2CL.028.04 ICC Public Key Remainder not present and Offline DDA is supported in AIP (5) performed) received at 1st GENERATE AC. •

TVR byte 1, bit 3 = '1' (ie Combined Data Authentication failed) received at 2nd GENERATE AC or contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form such as receipt for example.

•


•








•


•


•


•


•

Size of ICC Public Key and Issuer Public Key is such as NICC > NI – 42


•


•

TVR byte 1, bit 6 = '1' (ie ICC Data missing) received at 2nd GENERATE AC.

•



Page 1398


2CL.028.05 ICC Public Key Remainder not present and Offline DDA is supported in AIP (6) •


•


•








•


•


•


•


•


•



•


•

TVR byte 1, bit 6 = '1' (ie ICC Data missing) contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the terminal has the capability to show the TVR value in any form


Page 1400


2CL.028.06 ICC Public Key Remainder not present and Offline DDA is supported in AIP (6) such as receipt for example. •

TVR byte 1, bit 8 = '1' (ie Offline data authentication was not performed) received at 1st GENERATE AC.

•


•


•




2CL.028.07 ICC PIN Encipherement Public Key Remainder not present and Offline Enciphered PIN is supported Test No: 2CL.028.07 - Revision 16 - Number of sub cases: 2 Objective: To ensure that terminal performs the Offline PIN Encipherment, if ICC

PIN Encipherment Public Key Remainder is missing in the card and the length of the recovered ICC PIN Enchiperment Public Key indicates that ICC PIN Encipherment Public Key Remainder should not be present. Reference EMV 4.0: Reference Book 2 – Section 7.1 Keys and certificates EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•


•

Size of ICC PIN Encipherment Public Key and Issuer Public Key is such as NPE < NI – 42 in order to have several padding bytes ‘BB’

•

Case 01 - ICC PIN Encipherement Public Key Remainder data object is not present in LT (entire data object missing: TLV)

•

Case 02 - ICC Public Key Encipherment Remainder data object is coded with a length of '00' in LT


•


•


•


•

TVR byte 1, bit 6 = '0' (ie ICC Data not missing) received at 1st


Page 1402


2CL.028.07 ICC PIN Encipherement Public Key Remainder not present and Offline Enciphered PIN is supported GENERATE AC.







•


•


•


•


•


•



•


•

TVR byte 1, bit 6 = '1' (ie ICC Data missing) contained in Financial Confirmation message or Batch Data Capture message (this pass criteria apply only if the terminal has the capability to store declined or terminated transaction) or if the


Page 1404


2CL.028.08 ICC Public Key Remainder not present and Offline DDA is supported in AIP (9) terminal has the capability to show the TVR value in any form such as receipt for example. •


•


•


•




2CL.029.00 Constructed Data Objects do not parse correctly: FCI of PSE Test No: 2CL.029.00 - Revision 11 - Number of sub cases: 5 Objective: To ensure that if the terminal supports selection with PSE and FCI of

PSE template does not parse correctly, it switches to List of AIDs method Reference Book 1 - Section 6 - Files EMV 4.0:

Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 10 - Files EMV 4.1: Terminal [PSE] supported Configuration: Conditions:

•

LT contains PSE.

•

Case 01: FCI template '6F' of LT returned in response to SELECT PSE has a bad tag '6A'

•

Case 02: FCI template '6F' of LT returned in response to SELECT PSE has a bad length and value field has the correct length

•

Case 03: FCI of LT returned in response to SELECT PSE contains DF Name with bad tag '85'

•

Case 04: FCI of LT returned in response to SELECT PSE contains DF Name with bad length and value field has the correct length

•

Case 05: FCI of LT returned in response to SELECT PSE contains SFI Dir File Data Object with value field longer (+1) than specified in the length field


•


•



Page 1406


2CL.029.00 Constructed Data Objects do not parse correctly: FCI of PSE •




2CL.029.01 Constructed Data Objects do not parse correctly: FCI of DDF Test No: 2CL.029.01 - Revision 11 - Number of sub cases: 5 Objective: To ensure that if the terminal supports selection with PSE and FCI of

DDF template does not parse correctly, it switches to List of AIDs method Reference Book 1 - Section 6 - Files EMV 4.0:

Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 10 - Files EMV 4.1:


•

LT contains PSE.

•

LT contains DDF.

•

Case 01: FCI template '6F' of LT returned in response to SELECT DDF has a bad tag '6A'

•

Case 02: FCI template '6F' of LT returned in response to SELECT DDF has a bad length and value field has the correct length

•

Case 03: FCI of LT returned in response to SELECT DDF contains DF Name with bad tag '85'

•

Case 04: FCI of LT returned in response to SELECT DDF contains DF Name with bad length and value field has the correct length

•

Case 05: FCI of LT returned in response to SELECT contains SFI Dir File Data Object with value field longer (+1) than specified in the length field


•


The terminal shall switch to List of AIDs selection, transmitting a Copyright ©2008 EMVCo, LLC. All rights reserved

Page 1408


2CL.029.01 Constructed Data Objects do not parse correctly: FCI of DDF SELECT command for each AID it supports. •




2CL.029.05 Constructed Data Objects do not parse correctly: Directory Record in Payment System Directory Test No: 2CL.029.05 - Revision 15 - Number of sub cases: 4 Objective: To ensure that if Directory Record in Payment System Directory does

not parse correctly, it switches to List of AIDs method Reference Book 1 - Section 6 - Files EMV 4.0:

Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 10 - Files EMV 4.1: Terminal [PSE] supported Configuration: Conditions:

•

The Record returned in response to Read Directory command does not parse correctly:

•

Case 01: Record of LT returned in response to READ RECORD of Directory file has a bad length and value field has the correct length

•

Case 02: Record of LT returned in response to READ RECORD of Directory file has a bad tag '74'

•

Case 03: Record of LT returned in response to READ RECORD of Directory file contains a data object '4F' ADF Name located within the Application Template ‘70’ but before the application template '61'

•

Case 04: Record of LT returned in response to READ RECORD of Directory file contains a data object '4F' ADF Name located within the Application Template ‘70’ but after the application template '61'

Action: NA Procedure: Application selection process with PSE is performed by the LT. Pass Criteria:

•


•


•



Page 1410


2CL.029.05 Constructed Data Objects do not parse correctly: Directory Record in Payment System Directory requesting a TC or an AAC.



2CL.030.00 Constructed Data Objects do not parse correctly: Record Template Test No: 2CL.030.00 - Revision 10f - Number of sub cases: 4 Objective: To ensure that the terminal terminates the processing if record

template does not parse correctly Reference Book 1 - Section 6 – Files EMV 4.0:

Book Bulletins - Section SU 33 - Bulletin n°33, Clarification of Terminate in the EMV Specification (Apr-2004) Reference Book 1 - Section 10 - Files EMV 4.1: Terminal NA Configuration: Conditions:

•

Record template returned in response to READ RECORD during read application data does not parse correctly:

•

Case 01: Record of LT returned in response to READ RECORD of an AEF file has a bad length and value field has the correct length

•

Case 02: Record of LT returned in response to READ RECORD of an AEF has a bad tag '74'

•

Case 03: Record of LT returned in response to READ RECORD of an AEF has no template, but directly a primitive data object CDOL1

•

Case 04: Record of LT returned in response to READ RECORD of an AEF file has a good length and value field has this length+1



Page 1412


2CL.032.00 Constructed Data Objects do not parse correctly: FCI of ADF Test No: 2CL.032.00 - Revision 15 - Number of sub cases: 6 Objective: To ensure that the terminal remove the application from the candidate

list if FCI of ADF template does not parse correctly during final selection Reference Book 1 - Section 6 - Files EMV 4.0:

Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 10 - Files EMV 4.1: Terminal NA Configuration: Conditions:

•


•


•

following FCI template are returned during the final selection:

•

Case 01: FCI template '6F' of LT returned in response to SELECT ADF 1 has a bad tag '6A' instead of ‘6F’

•

Case 02: FCI template '6F' of LT returned in response to SELECT ADF 1 has a bad length and value field has the correct length

•

Case 03: FCI of LT returned in response to SELECT ADF 1 contains DF Name with bad tag '85' instead of ‘84’

•

Case 04: FCI of LT returned in response to SELECT ADF 1 contains DF Name with bad length and value field has the correct length

•

Case 05: FCI of LT returned in response to SELECT ADF 1 contains PDOL Data Object with value field longer (+1) than specified in the length field

•

Case 06: FCI of LT returned in response to SELECT ADF contains PDOL Data Object but located in the wrong position: under the '6F' FCI template and before the 'A5' FCI proprietary



2CL.032.00 Constructed Data Objects do not parse correctly: FCI of ADF template •

Case 07: FCI of LT returned in response to SELECT ADF contains PDOL Data Object but located in the wrong position: under the '6F' FCI template and after the 'A5' FCI proprietary template


•



Page 1414


2CL.033.00 Constructed Data Objects do not parse correctly: GPO response template Test No: 2CL.033.00 - Revision 10e - Number of sub cases: 7 Objective: To ensure that the terminal terminates the transaction if GET

PROCESSING OPTIONS response template does not parse correctly Reference Book 1 - Section 6 - Files EMV 4.0:

Book Bulletins - Section SU 33 - Bulletin n°33, Clarification of Terminate in the EMV Specification (Apr-2004) Reference Book 1 - Section 10 - Files EMV 4.1: Terminal NA Configuration: Conditions:

•

Case 01: GET POCESSING OPTIONS response template '77' of LT has a bad tag '70'

•

Case 02: GET POCESSING OPTIONS response template '77' of LT has a bad length and value field has the correct length

•

Case 03: GET POCESSING OPTIONS response template '80' of LT has a bad tag '70'

•

Case 04: GET POCESSING OPTIONS response template '80' of LT has a bad length and value field has the correct length

•

Case 05: GET POCESSING OPTIONS response template '77' of LT contains AFL with bad Tag '74'

•

Case 06: GET POCESSING OPTIONS response template '77' of LT contains AIP with bad length field '03' and correct length in the value field

•

Case 07: GET POCESSING OPTIONS response template '77' of LT do not contains AIP




2CL.034.00 Constructed Data Objects do not parse correctly: GENERATE AC response template '77' Test No: 2CL.034.00 - Revision 13a - Number of sub cases: 6 Objective: To ensure that the terminal terminates the transaction if GENERATE

AC response template does not parse correctly Reference Book 3 - Section 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message

Book Bulletins - Section SU 33 - Bulletin n°33, Clarification of Terminate in the EMV Specification (Apr-2004) Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message Terminal NA Configuration: Conditions:

•

Case 01: GENERATE AC response template '77' of LT contains CID with bad Tag '9D 27'

•

Case 02: GENERATE AC response template '77' of LT contains ATC with bad length '03' and value field has the correct length

•

Case 03: GENERATE AC response template '77' of LT contains Application Cryptogram with bad length of the value field: Tag '9F 26', Length field '08', value on 9 bytes.

•

Case 04: GENERATE AC response template '77' of LT has the length field incorrect: total length +1

•

Case 05: GENERATE AC response template of LT has a bad tag '70'

•

Case 06: GENERATE AC response template '80' of LT has the length field incorrect: total length +1



Page 1416


2CL.035.00 Constructed Data Objects do not parse correctly: INTERNAL AUTHENTICATE response template Test No: 2CL.035.00 - Revision 10e - Number of sub cases: 6 Objective: To ensure that the terminal terminates the transaction if INTERNAL

AUTHENTICATE response template does not parse correctly for Dynamic Data Authentication Reference Book 3 - Section 2.5.9.4 - Data Field Returned in the Response EMV 4.0: Message

Book Bulletins - Section SU 33 - Bulletin n°33, Clarification of Terminate in the EMV Specification (Apr-2004) Reference Book 3 - Section 6.5.9.4 - Data Field Returned in the Response EMV 4.1: Message Terminal [DDA] supported Configuration: Conditions:

•


•

Case 01: INTERNAL AUTHENTICATE response template '77' of LT has the length field incorrect: total length +1

•

Case 02: INTERNAL AUTHENTICATE response template '77' of LT contains the Signed Dynamic Application Data with bad tag '8F 4B'

•

Case 03: INTERNAL AUTHENTICATE response template '77' of LT contains the Signed Dynamic Application Data with bad length (value field +1) and value has the correct length

•

Case 04: INTERNAL AUTHENTICATE response template '77' of LT has an unexpected tag '70'

•

Case 05: INTERNAL AUTHENTICATE response template '80' of LT has the length field incorrect: total length +1

•

Case 06: INTERNAL AUTHENTICATE response template '80' of LT has a bad tag '79'




2CL.035.00 Constructed Data Objects do not parse correctly: INTERNAL AUTHENTICATE response template particular Dynamic Data Authentication). Pass Criteria: The terminal shall terminate the transaction


Page 1418


2CL.036.00 Dates are out of the range: effective date Test No: 2CL.036.00 - Revision 11 - Number of sub cases: 7 Objective: To ensure that the terminal terminates the transaction if dates provided

by the card are out of range Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0:

Book Bulletins - Section SU 33 - Bulletin n°33, Clarification of Terminate in the EMV Specification (Apr-2004) Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal NA Configuration: Conditions:

•

Case 01: Month of the date is 13

•


•


•

Case 04: Day of the date is 00

•


•


•

Case 07: Date is 310212 (31 Febuary 2012)




2CL.036.01 Dates are out of the range: expiration date Test No: 2CL.036.01 - Revision 10e - Number of sub cases: 7 Objective: To ensure that the terminal terminates the transaction if dates provided

by the card are out of range Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0:


•


•


•


•


•


•


•

Case 07: Date is 310206 (31 Febuary 2006)



Page 1420


2CL.037.00 Data that must be in a specific range of values but are not: SFI Test No: 2CL.037.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that if the terminal supports selection with PSE and SFI

value returned by the card in FCI is not in the range of supported values, it switches to List of AIDs method. Reference Book 1 - Section 8.2.3 - Coding of a Payment System’s Directory EMV 4.0:

Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 12.2.3 - Coding of a Payment System Directory EMV 4.1: Terminal [PSE] supported Configuration: Conditions:

•

LT response to SELECT PSE, SW1 SW2 = ’90 00’

•

Case 01: SFI of Directory File returned by the LT is 00

•


•



•


•


•




2CL.037.01 Data that must be in a specific range of values but are not: SFI (2) Test No: 2CL.037.01 - Revision 10g - Number of sub cases: 3 Objective: To ensure that if the terminal supports selection with PSE and contains

a DDF, the SFI value returned by the card in FCI of the DDF is not in the range of supported values, it terminates the processing. Reference Book 1 - Section 8.2.3 - Coding of a Payment System’s Directory EMV 4.0:

Book Bulletins - Section SU 29-02 - Bulletin n°29, Error Handling during Application Selection (Jun-2004) Reference Book 1 - Section 12.2.3 - Coding of a Payment System Directory EMV 4.1: Terminal [PSE] supported Configuration: Conditions:

•

LT contains a DDF

•

Case 01: SFI of DDF Directory File returned by the LT is 00

•


•



•


•


•



Page 1422


2CL.044.00 CVM List with no Cardholder Verification Rules Test No: 2CL.044.00 - Revision 17 - Number of sub cases: 2 Objective: To ensure that the terminal processes the transaction to completion if

the CVM List does not contain any Cardholder Verification Rule To ensure that the terminal considers that a CVM List with no Cardholder Verification Rules is the same as a CVM List not being present. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0:

Book 4 - Section 2.3.4.5 - CVM Results Book Bulletins - Section SU 33 - Bulletin n°33, Clarification of Terminate in the EMV Specification (Apr-2004) Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1:

Book 4 - Section 6.3.4.5 - CVM Results Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal NA Configuration: Conditions:

•


•

Subcase 01: CVM List in LT does not contain any Cardholder Verification Rule (Length = 0)

•

Subcase 02: CVM List in LT does not contain any Cardholder Verification Rule, but contain 8 bytes as value X and Y (Length = 08, Value = 00 00 00 00 00 00 00 00)


•

The terminal shall process the transaction to completion

•

TVR byte 1, bit 6 = '1' (ie ICC data missing)

•

TVR byte 3, bit 8 = '0' (ie Cardholder verification not failed)



2CL.044.00 CVM List with no Cardholder Verification Rules received at 1st GENERATE AC. •

TSI byte 1, bit 7 = '0' (ie Cardholder verification was not performed)

•

CVM Results ('3F 00 00')


Page 1424


2CL.045.00 Errors in CVM List Test No: 2CL.045.00 - Revision 18 - Number of sub cases: 2 Objective: To ensure that the terminal terminates the transaction if the CVM List

has format errors. Reference NA EMV 4.0: Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1:


•


•

Case 01: CVM List is Fail CVM, always, but the Y value is coded on 3 bytes only: ‘8E 09 00 00 01 00 00 00 02 00 00’

•

Case 02: CVM List is Fail CVM, always, but the length byte value is incorrect: ‘8E 0E 00 00 00 01 00 00 00 02 00 00’




2CL.047.00 AFL with an incorrect SFI Test No: 2CL.047.00 - Revision 10e - Number of sub cases: 2 Objective: To ensure that the terminal terminates the transaction if an SFI in the

AFL has a value of 0 or 31 Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0:


•

Case 01: SFI in AFL is 0

•

Case 02: SFI in AFL is 31



Page 1426


2CL.048.00 AFL with an incorrect starting record number Test No: 2CL.048.00 - Revision 10e - Number of sub cases: 0 Objective: To ensure that the terminal terminates the transaction if a start record

number in AFL has a value of 0 Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0:

Book Bulletins - Section SU 33 - Bulletin n°33, Clarification of Terminate in the EMV Specification (Apr-2004) Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal NA Configuration: Conditions: Start record number in AFL has a value of 0 Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall terminate the transaction



2CL.049.00 AFL with an incorrect ending record number Test No: 2CL.049.00 - Revision 10e - Number of sub cases: 0 Objective: To ensure that the terminal terminates the transaction if a start record

number in AFL has a value greater than the ending record Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0:

Book Bulletins - Section SU 33 - Bulletin n°33, Clarification of Terminate in the EMV Specification (Apr-2004) Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal NA Configuration: Conditions: Start record number in AFL has a value greater than ending record Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall terminate the transaction


Page 1428


2CL.050.00 AFL with an incorrect number of records participating in Offline Data Authentication Test No: 2CL.050.00 - Revision 10e - Number of sub cases: 0 Objective: To ensure that the terminal terminates the transaction if an entry in AFL

has an incorrect number of records participating in Offline Data Authentication. Reference Book 3 - Section 3.4 - Erroneous or Missing Data in the ICC EMV 4.0:

Book Bulletins - Section SU 33 - Bulletin n°33, Clarification of Terminate in the EMV Specification (Apr-2004) Reference Book 3 - Section 7.5 - Erroneous or Missing Data in the ICC EMV 4.1: Terminal NA Configuration: Conditions: Ending record number - start record number + 1
participating in Offline Data Authentication Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall terminate the transaction



2CL.054.00 ISO Padding: padding between Data object Test No: 2CL.054.00 - Revision 11 - Number of sub cases: 19 Objective: To ensure that a terminal ignores the padding, if there are padding with

bytes 0x00 or 0xFF between 2 Data Elements in a Template Reference Book 3 - Section 1.2 - Data Objects EMV 4.0: Reference Book 3 - Section 5.2 - Data Objects EMV 4.1: Terminal NA Configuration: Conditions:

•

Length of padding bytes is included in the template length

•

Case 01: A record template '70' of LT contains two data objects with a padding of 50 bytes with a value of '00' in between

•

Case 02: A record template '70' of LT contains two data objects with a padding 0000 before the first data object

•

Case 03: A record template '70' of LT contains two data objects with a padding of 200 bytes with a value of '00' after the second data object

•

Case 04: A record template '70' of LT contains two data objects with a padding FFFF in between

•

Case 05: A record template '70' of LT contains two data objects with a padding of 50 bytes with a value of 'FF' before the first data object

•

Case 06: A record template '70' of LT contains two data objects with a padding FFFF after the second data object

•

Case 07: A FCI template '6F' of the SELECT ADF response of LT contains DF Name and FCI proprietary template with a padding 0000 in between

•

Case 08: A FCI template '6F' of the SELECT ADF response of LT contains DF Name and FCI proprietary template with a padding of 200 bytes with a value of '00' before DF Name

•

Case 09: A FCI template '6F' of the SELECT ADF response of LT contains DF Name and FCI proprietary template with a padding 0000 after FCI proprietary template


Page 1430


2CL.054.00 ISO Padding: padding between Data object •

Case 10: A FCI template '6F' of the SELECT ADF response of LT contains DF Name and FCI proprietary template with a padding of 50 bytes with a value of 'FF' in between

•

Case 11: A FCI template '6F' of the SELECT ADF response of LT contains DF Name and FCI proprietary template with a padding FFFF before DF Name

•

Case 12: A FCI template '6F' of the SELECT ADF response of LT contains DF Name and FCI proprietary template with a padding 0000 after FCI proprietary template

•

Case 13: A GET PROCESSING OPTION response template '77' of LT contains AFL and AIP with a padding 0000 in between

•

Case 14: A GET PROCESSING OPTION response template '77' of LT contains AFL and AIP with a padding of 50 bytes with a value of '00' after the two objects

•

Case 15: A GET PROCESSING OPTION response template '77' of LT contains AFL and AIP with a padding 0000 before the two objects

•

Case 16: A GET PROCESSING OPTION response template '77' of LT contains AFL and AIP with a padding of 200 bytes with a value of 'FF' in between

•

Case 17: A GET PROCESSING OPTION response template '77' of LT contains AFL and AIP with a padding FFFF after the two objects

•

Case 18: A GET PROCESSING OPTION response template '77' of LT contains AFL and AIP with a padding FFFF before the two objects

•

Case 19: A record template '70' of LT contains a padding of 251 bytes with a value of '00'


requesting a TC or an AAC. Copyright © 2008 EMVCo, LLC. All Rights Reserved. Page 1431



Page 1432


2CL.055.00 Format of Application Label and Application preferred Name are 'ans' Test No: 2CL.055.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal supports the new 'ans' format of the

Application Label and Application preferred Name Reference Book Bulletins - Section SU 14 - Bulletin n°14, Change to format EMV 4.0: specification for the Application Label and Application Preferred Name

(Oct-2002) Reference Book1 – Annex B – Data Elements Table EMV 4.1: Terminal NA Configuration: Conditions:

•

LT contains an ADF

•

Case 01: FCI of ADF contains Application Label and Application preferred Name with ans format and a 'space' character

•

Case 02: FCI of ADF contains Application Label and Application preferred Name with ans format and a '&' character

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




2CL.056.00 Mandatory data objects missing, format 1 GERNERATE AC, TC response Test No: 2CL.056.00 - Revision 15 - Number of sub cases: 3 Objective: To ensure that the terminal checks that the data in table 13, Book 3,

section 6.5.5.3 is present when performing GENERATE AC without CDA. Reference EMV 4.0: Reference Book 3 – Section 6.5.5.3 – Data Field Returned in the Response EMV 4.1: Message

Book Bulletins - Section SU 54 - Bulletin No.54, Missing Mandatory Command Response Data (Nov 2006) Terminal (Offline Only OR Offline/Online Capable) supported AND [CDA] not Configuration: supported Conditions:

•

TAC/IAC set to request a TC in first GENERATE AC

•

LT responds to GENERATE AC command with a TC in format 1

•

Case 01: Application Cryptogram value is not present in first GENERATE AC response

•

Case 02: Cryptogram Information Data value is not present in first GENERATE AC response

•

Case 03: Application Transaction Counter value is not present in first GENERATE AC response

Action: NA Procedure: Application in LT is selected and transaction is processed with LT Pass Criteria:

•



Page 1434


2CL.057.00 Mandatory data objects missing, format 1 GENERATE AC, ARQC response Test No: 2CL.057.00 - Revision 15 - Number of sub cases: 3 Objective: To ensure that the terminal checks that the data in table 13, Book 3,

section 6.5.5.3 is present when performing GENERATE AC without CDA. Reference EMV 4.0: Reference Book 3 – Section 6.5.5.3 – Data Field Returned in the Response EMV 4.1: Message

Book Bulletins - Section SU 54 - Bulletin No.54, Missing Mandatory Command Response Data (Nov 2006) Terminal ([Online Only] OR [Online/Offline Capable]) AND [CDA] not supported Configuration: Conditions:

•

TAC/IAC set to request an ARQC in the first GENERATE AC, and TC in second GENERATE AC

•


•

LT responds with ARQC to first GENERATE AC and TC to second GENERATE AC

•

Case 01: Application Cryptogram value is not present in second GENERATE AC response

•

Case 02: Cryptogram Information Data value is not present in second GENERATE AC response

•

Case 03: Application Transaction Counter value is not present in second GENERATE AC response


•




2CL.058.00 Mandatory data objects missing, format 2 GENERATE AC, TC response Test No: 2CL.058.00 - Revision 15 - Number of sub cases: 6 Objective: To ensure that the terminal checks that the data in table 13, Book 3,

section 6.5.5.3 is present when performing GENERATE AC Reference EMV 4.0: Reference Book 3 - Section 6.5.5.3 – Data Field Returned in the Response EMV 4.1: Message

Book Bulletins - Section SU 54 - Bulletin No.54, Missing Mandatory Command Response Data (Nov 2006) Terminal [Offline Only] supported OR [Offline/Online] supported Configuration: Conditions:

•

TAC/IAC set to request TC in first GENERATE AC

•

LT responds to GENERATE AC command with a TC in format 2

•

Case 01: Application Cryptogram value is missing from the TLV data object in the GENERATE AC response (9F 26 00)

•

Case 02: Application Crytogram data object is missing in its entierity in the GENERATE AC response

•

Case 03: Cryptogram Information Data value is missing from the TLV data object in the GENERATE AC response. (9F 27 00)

•

Case 04: Cryptogram Information Data TLV data object is missing in its entierity in the GENERATE AC response.

•

Case 05: Application Transaction Counter value is missing from the TLV data object in the GENERATE AC response (9F 36 00)

•

Case 06: Application Transaction Counter TLV data object is missing in its entierity in the GENERATE AC response,

Action: NA Procedure: Application in LT is selected and transaction is processed with LT


Page 1436


2CL.058.00 Mandatory data objects missing, format 2 GENERATE AC, TC response Pass Criteria:

•




2CL.059.00 Mandatory data objects missing, format 2 GENERATE AC, ARQC response Test No: 2CL.059.00 - Revision 16 - Number of sub cases: 6 Objective: To ensure that the terminal checks that the data in table 13, Book 3,

section 6.5.5.3 is present when performing GENERATE AC Reference EMV 4.0: Reference Book 3 - Section 6.5.5.3 – Data Field Returned in the Response EMV 4.1: Message

Book Bulletins - Section SU 54 - Bulletin No.54, Missing Mandatory Command Response Data (Nov 2006) Terminal ([Online Only] supported OR [Online/Offline Capable]) supported Configuration: Conditions:

•

TAC/IAC set to request ARQC in first GENERATE AC and TC in second GENERATE AC

•

LT responds to GENERATE AC is in format 2

•

Case 01: Application Cryptogram value is missing from the TLV data object in the second GENERATE AC response (9F 26 00)

•

Case 02: Application Crytogram data object is missing in its entierity in the second GENERATE AC response

•

Case 03: Cryptogram Information Data value is missing from the TLV data object in the second GENERATE AC response. (9F 27 00)

•

Case 04: Cryptogram Information Data TLV data object is missing in its entierity in the second GENERATE AC response.

•

Case 05: Application Transaction Counter value is missing from the TLV data object in the GENERATE AC response (9F 36 00)

•

Case 06: Application Transaction Counter TLV data object is missing in its entierity in the second GENERATE AC response,

Action: NA


Page 1438


2CL.059.00 Mandatory data objects missing, format 2 GENERATE AC, ARQC response Procedure: Application in LT is selected and transaction is processed with LT Pass Criteria:

•




2CL.060.00 Mandatory data objects missing, format 1 INTERNAL AUTHENTICATE response Test No: 2CL.060.00 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal checks that the data specified in Book 3,

section 6.5.9.4 is present. Reference EMV 4.0: Reference Book 3 - Section 6.5.9.4 – Data Field Returned in the Response EMV 4.1: Message

Book Bulletins - Section SU 54 - Bulletin No.54, Missing Mandatory Command Response Data (Nov 2006) Terminal [DDA] Supported Configuration: Conditions:

•

AIP of LT indicates DDA is supported (AIP byte 1 bit 6 = 1).

•

LT responds to INTERNAL AUTHENTICATE command in format 1

•

Signed Dynamic Application Data value is missing


•



Page 1440


2CL.061.00 Mandatory data objects missing, format 2 INTERNAL AUTHENTCIATE response Test No: 2CL.061.00 - Revision 15 - Number of sub cases: 2 Objective: To ensure that the terminal checks that the data specified in Book 3,

section 6.5.9.4 is present. Reference EMV 4.0: Reference Book 3 - Section 6.5.9.4 – Data Field Returned in the Response EMV 4.1: Message

Book Bulletins - Section SU 54 - Bulletin No.54, Missing Mandatory Command Response Data (Nov 2006) Terminal [DDA] Supported Configuration: Conditions:

•

AIP of LT indicates DDA is supported (AIP byte 1 bit 6 = 1).

•

LT responds to INTERNAL AUTHENTICATE command in format 2

•

Case 01: Signed Dynamic Application Data value is missing from the TLV data object (9F 4B 00)

•

Case 02: Signed Dynamic Application Data TLV data object is missing in its entirety


•




Terminal General Requirements


Page 1442


2CM.001.00 Merchant-controlled Terminal Provides Amount Test No: 2CM.001.00 - Revision 10 - Number of sub cases: 2 Objective: To ensure that the terminal provides the amount of the transaction

during Initiate Application Processing if PDOL includes amount field Reference Book 4 - Section 2.3.1 - Initiate Application Processing EMV 4.0: Reference Book 4 - Section 6.3.1 - Initiate Application Processing EMV 4.1: Terminal [Terminal Type 2x] supported Configuration: Conditions: PDOL requests Amount, Authorized

•

Case 01: PDOL requests amount in numeric format

•

Case 02: PDOL requests amount in binary format

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The LT shall receive a GET PROCESSING OPTIONS with data field

containing the amount of the transaction



2CM.002.00 Merchant-controlled Terminal Obtains Amount if Not Available Test No: 2CM.002.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal displays the 'Enter Amount' message and

obtains the amount of the transaction, during Initiate Application Processing if PDOL includes amount field and it is not yet available Reference Book 4 - Section 2.3.1 - Initiate Application Processing EMV 4.0: Reference Book 4 - Section 6.3.1 - Initiate Application Processing EMV 4.1: Terminal [Terminal Type 2x] supported Configuration: Conditions: PDOL requests Amount, Authorized

•

Case 01: PDOL requests amount in numeric format

•

Case 02: PDOL requests amount in binary format


•

The Terminal shall obtain the amount before issuing the GET PROCESSING OPTIONS command

•

The Terminal should display the 'Enter Amount' message

•

The LT shall receive a GET PROCESSING OPTIONS command where data field contains the amount of the transaction


Page 1444


2CM.003.00 PDOL Requests Amount, Authorized & Amount, Other Test No: 2CM.003.00 - Revision 15 - Number of sub cases: 4 Objective: To ensure that the terminal correctly processes a PDOL request for

Amount, Authorized & Amount, Other. Reference Book 4 - Section 2.3.1 - Initiate Application Processing EMV 4.0: Reference Book 3 - Section 10.1 - Initiate Application Processing EMV 4.1:

Book 4 - Section 6.3.1 - Initiate Application Processing

Terminal N/A Configuration: Conditions:

•

Transaction amount is greater than zero.

•

Case 01: PDOL requests Amount, Authorized in numeric format (tag '9F 02')

•

Case 02: PDOL requests Amount, Authorized in binary format (tag '81)

•

Case 03: PDOL requests Amount, Other in numeric format (tag '9F 03')

•

Case 04: PDOL requests Amount, Other in binary format (tag '9F 04')


•

GET PROCESSING OPTIONS command contains the transaction amount consistent with the PDOL. If the terminal is unable to obtain the amount at this point the amount field shall be filled with hexadecimal zeroes.

•

The terminal shall process the transaction until completion



2CM.004.00 Online Only Terminal Not Supporting Data Authentication Sets Bit Test No: 2CM.004.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that an online only terminal sets the 'Offline Static Data

Authentication was not performed' bit in the TVR to 1b, if it does not support any form of data authentication according to the Terminal capabilities Reference Book 4 - Section 2.3.2 - Data Authentication EMV 4.0: Reference Book 4 - Section 6.3.2 - Offline Data Authentication EMV 4.1: Terminal ([Online Only] supported AND [SDA] not supported) Configuration: Conditions: NA Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•

TVR byte 1, bit 8 = '1' (ie Data Authentication was not performed) received at 1st GENERATE AC.

•


•


•



Page 1446


2CM.006.00 Card and Terminal Application Version Numbers are different Test No: 2CM.006.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the card and terminal Application Version Numbers

are different, the terminal attempts to continue processing the transaction. If it is unable to continue, the terminal aborts the transaction. Reference Book 4 - Section 2.3.3 - Processing Restrictions EMV 4.0: Reference Book 4 - Section 6.3.3 - Processing Restrictions EMV 4.1: Terminal NA Configuration: Conditions:

•

LT and terminal have different Application Version Number


•

The terminal shall attempt to process the transaction until completion, by requesting a TC or an AAC, if unable the terminal shall abort the transaction.

•

TVR byte 2, bit 8 = '1' (ie ICC and terminal have different application versions) received at 1st GENERATE AC.



2CM.009.00 Terminal Recognition of CVM Codes ('No CVM required' supported) - CVM is Set When no CVM is Required Test No: 2CM.009.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal recognizes CVM code 'No CVM Required' if

the terminal supports this CVM. To ensure that the terminal sets the CVM Results byte 3 to 'successful' when applicable CVM is 'No CVM Required'. Reference Book 4 - Section 2.3.4 - Cardholder Verification Processing EMV 4.0:

Book 4 - Section 2.3.4.5 - CVM Results Reference Book 4 - Section 6.3.4 - Cardholder Verification Processing EMV 4.1:

Book 4 - Section 6.3.4.5 - CVM Results Terminal [NO CVM] supported Configuration: Conditions:

•


•

CVM List is 'No CVM required, always' (1F 00)


•


•

TVR byte 3, bit 8 = '0' (ie cardholder verification succeeded) received at 1st GENERATE AC.

•

The terminal shall set byte 3 of the CVM Results to 'successful'

•


•



Page 1448


2CM.009.05 Terminal Recognition of CVM Codes ('No CVM required' not supported) Test No: 2CM.009.05 - Revision 18 - Number of sub cases: 0 Objective: To ensure that the terminal recognizes CVM code 'No CVM required' if

the terminal does not support this CVM. Reference Book 4 - Section 2.3.4 - Cardholder Verification Processing EMV 4.0: Reference Book 4 - Section 6.3.4 - Cardholder Verification Processing EMV 4.1: Terminal [No CVM] not supported Configuration: Conditions:

•


•


•

CVM List is 'No CVM required, always' (1F 00)


•


•

TVR byte 3, bit 8 = '1' (ie cardholder verification was not successful) received at 1st GENERATE AC.

•

The terminal shall set byte 3 of the CVM Results to 'not successful'

•


•




2CM.010.00 Terminal Recognition of CVM Codes ('Fail CVM processing') - CVM is Set When CVM is 'Fail CVM Processing' Test No: 2CM.010.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal recognizes CVM code 'Fail CVM'.

To ensure that the terminal sets the CVM Results byte 3 to 'Failed' when applicable CVM is Fail CVM Reference Book 4 - Section 2.3.4 - Cardholder Verification Processing EMV 4.0:

Book 4 - Section 2.3.4.5 - CVM Results Reference Book 4 - Section 6.3.4 - Cardholder Verification Processing EMV 4.1:

Book 4 - Section 6.3.4.5 - CVM Results Terminal NA Configuration: Conditions:

•


•

CVM List is 'Fail CVM, always' (00 00).


•


•

TVR byte 3, bit 8 = '1' (ie cardholder verification was not successful) received at 1st GENERATE AC.

•


•

CVM Result = 00 00 01) received at 1st GENERATE AC.


Page 1450


2CM.011.00 Supported CVM Test No: 2CM.011.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that CVM supported by the terminal are indicated in terminal

capabilities Reference Book 4 - Section 2.3.4 - Cardholder Verification Processing EMV 4.0: Reference Book 4 - Section 6.3.4 - Cardholder Verification Processing EMV 4.1: Terminal NA Configuration: Conditions: PDOL requests Terminal capabilities Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

Terminal capabilities returned by terminal shall reflect the CVM supported by the terminal



2CM.013.00 PIN Try Counter Not Retrievable by ICC Test No: 2CM.013.00 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal prompts for PIN entry if PIN Try Counter is

not retrievable or GET DATA is not supported by LT Reference Book 4 - Section 2.3.4.1 - Offline CVM EMV 4.0: Reference Book 4 - Section 6.3.4.1 - Offline CVM EMV 4.1: Terminal ([Offline Plaintext PIN] supported AND [Get Data for PIN Try Counter] Configuration: supported) Conditions:

•


•

LT does not return PIN Try Counter in response to GET DATA (PIN Try Counter)

•

CVM List is 'Plaintext PIN, always' (01 00)

•

Case 01: Get Data for PTC returns PTC with zero length

•

Case 02: LT returns status different from 90 00 to GET DATA (PIN Try Counter)


•


•

Terminal shall display the 'Enter PIN' message after having received the response to GET DATA command.


Page 1452


2CM.013.01 PIN Try Counter Not Retrievable by ICC (2) Test No: 2CM.013.01 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal prompts for PIN entry if PIN Try Counter is

not retrievable or GET DATA is not supported by LT Reference Book 4 - Section 2.3.4.1 - Offline CVM EMV 4.0: Reference Book 4 - Section 6.3.4.1 - Offline CVM EMV 4.1: Terminal ([Get Data for PIN Try Counter] supported AND [Offline Enciphered Configuration: PIN] supported) Conditions:

•


•

LT does not return PIN Try Counter in response to GET DATA (PIN Try Counter)

•

CVM List is 'Enciphered PIN verification performed by ICC, always' (04 00)

•

Case 01: Get Data for PTC returns PTC with zero length

•

Case 02: LT returns status different from 90 00 to GET DATA (PIN Try Counter)


•


•

Terminal shall display the 'Enter PIN' message after having received the response to GET DATA command.



2CM.016.00 Terminal Prompt for PIN Entry (PIN Try Counter >0) Test No: 2CM.016.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal prompts for PIN entry and displays a

message such as 'Enter PIN', if PIN Try counter returned by GET DATA is not 0 Reference Book 4 - Section 2.3.4.1 - Offline CVM EMV 4.0: Reference Book 4 - Section 6.3.4.1 - Offline CVM EMV 4.1: Terminal ([Offline Plaintext PIN] supported AND [Get Data for PIN Try Counter] Configuration: supported) Conditions:

•


•

LT returns PIN Try Counter > 0 to GET DATA

•

CVM List is Plaintext PIN always (01 00)


•


•

Terminal shall display the 'Enter PIN' message after having received the GET DATA command


Page 1454


2CM.016.01 Terminal Prompt for PIN Entry (PIN Try Counter >0) (2) Test No: 2CM.016.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal prompts for PIN entry and displays a

message such as 'Enter PIN', if PIN Try counter returned by GET DATA is not 0 Reference Book 4 - Section 2.3.4.1 - Offline CVM EMV 4.0: Reference Book 4 - Section 6.3.4.1 - Offline CVM EMV 4.1: Terminal ([Get Data for PIN Try Counter] supported AND [Offline Enciphered Configuration: PIN] supported) Conditions:

•


•

LT returns PIN Try Counter > 0 to GET DATA

•

CVM List is Enciphered PIN verification performed by ICC, always (04 00)


•


•

Terminal shall display the 'Enter PIN' message after receiving the GET DATA command



2CM.018.00 Offline PIN Not Successful Test No: 2CM.018.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal does not set CVM Result and continue the

processing of CVM List, if offline PIN verification by the ICC is not successful Reference Book 4 - Section 2.3.4.1 – Offline CVM EMV 4.0: Reference Book 4 - Section 6.3.4.1 – Offline CVM EMV 4.1: Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•


•

LT returns PIN Try Counter > 0 to GET DATA if Terminal supports GET DATA for PTC

•

CVM List is 'Plaintext PIN, always' (41 00) followed by 'Fail CVM, always' (00 00).

•

Status value returned by the LT on the VERIFY Command is '63 C0'


•


•

TVR byte 3, bit 8 = '1' (ie Cardholder verification was failed,received at 1st GENERATE AC.

•


•



Page 1456


2CM.018.01 Offline PIN Not Successful (2) Test No: 2CM.018.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal does not set CVM Result and continue the

processing of CVM List, if offline PIN verification by the ICC is not successful Reference Book 4 - Section 2.3.4.1 - Offline CVM EMV 4.0: Reference Book 4 - Section 6.3.4.1 - Offline CVM EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

LT returns PIN Try Counter > 0 to GET DATA if Terminal supports GET DATA for PTC

•

CVM List is 'Enciphered PIN verification performed by ICC, always' (44 00) followed by 'Fail CVM, always' (00 00).

•

Status value returned by the LT on the VERIFY Command is '63 C0'


•


•

TVR byte 3, bit 8 = '1' (ie Cardholder verification was failed),received at 1st GENERATE AC.

•


•




2CM.020.00 Online PIN When PIN Try Limit is Exceeded and Terminal Supports GET DATA for PIN Try Counter Test No: 2CM.020.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal allows a PIN to be entered for online

verification even if the card's PIN Try Limit is exceeded Reference Book 4 - Section 2.3.4.2 - Online CVM EMV 4.0: Reference Book 4 - Section 6.3.4.2 - Online CVM EMV 4.1: Terminal (([Get Data for PIN Try Counter] supported AND [Online Enciphered Configuration: PIN] supported) AND ([Offline Plaintext PIN] supported OR [Offline

Enciphered PIN] supported)) Conditions:

•


•

CVM List requests 'Plaintext PIN if terminal supports' (41 03) followed by 'Enciphered Offline PIN if terminal supports' (44 03) followed by 'Online Enciphered PIN always (02 00).

•

LT returns PIN Try Counter = 0 to GET DATA


•


•


•


•

TVR byte 3, bit 3 = '1' (ie Online PIN entered) received at 1st GENERATE AC.

•

Terminal shall display an 'Enter PIN' Message

•



Page 1458


2CM.020.01 Online PIN When PIN Try Limit is Exceeded and the Terminal does not support GET DATA for PIN Try Counter Test No: 2CM.020.01 - Revision 11 - Number of sub cases: 3 Objective: To ensure that the terminal allows a PIN to be entered for online

verification even if the card's PIN Try Limit is exceeded Reference Book 4 - Section 2.3.4.2 - Online CVM EMV 4.0: Reference Book 4 - Section 6.3.4.1 - Online CVM EMV 4.1: Terminal (([Get Data for PIN Try Counter] not supported AND [Online Configuration: Enciphered PIN] supported) AND ([Offline Plaintext PIN] supported OR

[Offline Enciphered PIN] supported)) Conditions:

•


•

LT returns 63C0 to VERIFY command.

•

Case 01: CVM List requests 'Plaintext PIN if terminal supports' (41 03), followed by 'Online Enciphered PIN always' (02 00)

•

Case 02: CVM List requests 'Enciphered Offline PIN if terminal supports' (44 03), followed by 'Online Enciphered PIN always' (02 00)

•

Case 03: CVM List requests 'Plaintext PIN if terminal supports' (41 03) followed by 'Enciphered Offline PIN if terminal supports' (44 03) followed by 'Online Enciphered PIN always (02 00)


•


•


•




2CM.020.01 Online PIN When PIN Try Limit is Exceeded and the Terminal does not support GET DATA for PIN Try Counter •

TVR byte 3, bit 3 = '1' (ie Online PIN entered) received at 1st GENERATE AC.

•

Terminal shall display an 'Enter PIN' Message

•



Page 1460


2CM.022.00 TVR is Set When PIN Entry is bypassed at Attended Terminal Test No: 2CM.022.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the terminal sets the 'PIN entry required, PIN pad

present, but PIN was not entered' bit in the TVR to 1b and the 'PIN Try Limit exceeded" bit in the TVR is not set to 1b, if an attended terminal bypasses PIN entry Reference Book 4 - Section 2.3.4.3 - PIN Entry Bypass EMV 4.0: Reference Book 4 - Section 6.3.4.3 - PIN Entry Bypass EMV 4.1: Terminal (([PIN Bypass] supported AND [Attended] supported) AND (([Offline Configuration: Plaintext PIN] supported OR [Offline Enciphered PIN] supported) OR

[Online Enciphered PIN] supported)) Conditions:

•


•

The following sub cases shall be performed, depending on the terminal options

•

Case 01: CVM List is 'Plaintext PIN verification by ICC always'

•

Case 02: CVM List is 'Enciphered PIN verification performed by ICC always'

•

Case 03: CVM List is 'Enciphered PIN online always'

Action: the Merchant forces the bypass of the PIN Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

TVR byte 3, bit 4 = '1' (ie PIN entry required, PIN pad present, but PIN was not entered) received at 1st GENERATE AC.

•

TVR byte 3, bit 6 = '0' (ie PIN Try Limit not exceeded) received at 1st GENERATE AC.



2CM.023.00 CVM unsuccessful When PIN Entry is bypassed at Attended Terminal Test No: 2CM.023.00 - Revision 11 - Number of sub cases: 3 Objective: To ensure that the terminal considers the CVM as unsuccessful and

continue the processing of CVM, if PIN entry is bypassed Reference Book 4 - Section 2.3.4.3 - PIN Entry Bypass EMV 4.0: Reference Book 4 - Section 6.3.4.3 - PIN Entry Bypass EMV 4.1: Terminal (([PIN Bypass] supported AND [Attended] supported) AND (([Offline Configuration: Plaintext PIN] supported OR [Offline Enciphered PIN] supported) OR

[Onfline Enciphered PIN] supported)) Conditions:

•


•

The following sub cases shall be performed, depending on the terminal options

•

Case 01: CVM List is 'Plaintext PIN verification by ICC always (41 00), followed by Fail CVM always (00 00)’

•

Case 02: CVM List is 'Enciphered PIN verification performed by ICC always (44 00), followed by Fail CVM always (00 00)’

•

Case 03: CVM List is 'Enciphered PIN online always (42 00), followed by Fail CVM always (00 00)’


•


•


•


•



Page 1462


2CM.023.00 CVM unsuccessful When PIN Entry is bypassed at Attended Terminal •

TVR byte 3, bit 4 ='1' (ie PIN Entry required and PIN Pad present, but PIN was not entered. received at 1st GENERATE AC.

•

CVM Results ('00 00 01')



2CM.024.00 PIN Entry bypass affected all PIN methods Test No: 2CM.024.00 - Revision 18 - Number of sub cases: 0 Objective: To ensure that when PIN entry has been bypassed for one PIN-related

CVM, the terminal may be considered bypassed for any subsequent PIN-related CVM Reference Book 4 - Section 2.3.4.3 - PIN Entry Bypass EMV 4.0: Reference Book 4 - Section 6.3.4.3 - PIN Entry Bypass EMV 4.1:

Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal ([Subsequent PIN Bypass] supported AND [PIN Bypass] supported Configuration: AND [Attended Terminal] supported) AND (([Offline Plaintext PIN]

supported AND [Offline Enciphered PIN] supported) OR (Offline Plaintext PIN] supported AND [Online Enciphered PIN] supported) OR ([Offline Enciphered PIN] supported AND [Online Enciphered PIN] supported)) Conditions:

•


•

CVM List is 'Plaintext PIN verification by ICC if supported’ (41 03) followed by is 'Enciphered PIN verification performed by ICC of supported’ (44 03) followed by 'Enciphered PIN online if supported’ (42 03) followed by ‘Fails CVM always (00 00).


•


•


•


•


•

CVM Results ('00 00 01')


Page 1464


2CM.024.00 PIN Entry bypass affected all PIN methods •

Terminal does not prompt for 2nd PIN method



2CM.024.01 PIN Entry bypass does not affected all PIN methods Test No: 2CM.024.01 - Revision 18 - Number of sub cases: 0 Objective: To ensure that when PIN entry has been bypassed for one PIN-related

CVM, the terminal may be not considered bypassed for any subsequent PIN-related CVM Reference Book 4 - Section 2.3.4.3 - PIN Entry Bypass EMV 4.0: Reference Book 4 - Section 6.3.4.3 - PIN Entry Bypass EMV 4.1:

Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal ([PIN Bypass] supported AND [Attended Terminal] supported) AND Configuration: ((Offline Plaintext PIn] supported AND [Offline Enciphered PIN]

supported) OR (Offline Plaintext PIN] supported AND [Online Enciphered PIN] supported) OR ([Offline Enciphered PIN] supported AND [Online Enciphered PIN] supported)) AND [Subsequent PIN Bypass] not supported Conditions:

•


•

CVM List is 'Plaintext PIN verification by ICC if supported’ (41 03) followed by is 'Enciphered PIN verification performed by ICC of supported’ (44 03) followed by 'Enciphered PIN online if supported’ (42 03) followed by ‘Fails CVM always (00 00).

Action: the Merchant forces the bypass of the PIN and enter correct PIN for 2nd

Method Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•


•


•

CVM Results is the set to the second CVM supported by the


Page 1466


2CM.024.01 PIN Entry bypass does not affected all PIN methods Terminal (but is a PIN CVM) •

Terminal prompt for 2nd PIN method



2CM.025.00 Terminal Prints Receipt With Line for Cardholder Signature Test No: 2CM.025.00 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal prints a receipt with line for Cardholder

signature when signature is the applicable CVM Reference Book 4 - Section 2.3.4.4 - Signature (Paper) EMV 4.0: Reference Book 4 - Section 6.3.4.4 - Signature (Paper) EMV 4.1: Terminal [Signature] supported Configuration: Conditions:

•


•

CVM is Signature, always (1E 00)

•

Case 01: Offline transaction

•

Case 02: Online transaction


•


•

Terminal shall print a receipt with a line for Cardholder signature


Page 1468


2CM.028.00 CVM Results Set With Method Code and Condition Code of Last CVM Performed Test No: 2CM.028.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal sets the CVM Results bytes 1 and 2

according to the last CVM performed Reference Book 4 - Section 2.3.4.5 - CVM Results EMV 4.0: Reference Book 4 - Section 6.3.4.5 - CVM Results EMV 4.1: Terminal NA Configuration: Conditions:

•


•

CVM list in LT is 'Fail CVM, always' (00 00) followed by 'NO CVM always' (1F 00)


•


•

CVM Result shall be set to ‘00 00 01'

•




2CM.028.01 CVM Results Set With Method Code and Condition Code of Last CVM Performed (2) Test No: 2CM.028.01 - Revision 11 - Number of sub cases: 4 Objective: To ensure that the terminal sets the CVM Results bytes 1 and 2

according to the last CVM performed Reference Book 4 - Section 2.3.4.5 - CVM Results EMV 4.0: Reference Book 4 - Section 6.3.4.5 - CVM Results EMV 4.1: Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•


•

Case 01: CVM list in LT is 'Offline Plaintext PIN always (41 00) followed by Signature always' (1E 00) and correct PIN is entered

•

Case 02: CVM list in LT is 'Offline Plaintext PIN always (41 00) followed by Signature always' (1E 00) and a wrong PIN is entered

•

Case 03: CVM list in LT is 'Fail CVM, always' (00 00) followed by 'NO CVM always' (1F 00)


•


•


•

Case 01: CVM Result shall be set to ‘41 00 02'

•

Case 02: CVM Results '1E 00 00' if terminal supports signature or '1E 00 01' when signature is not supported

•



Page 1470



according to the last CVM performed Reference Book 4 - Section 2.3.4.5 - CVM Results EMV 4.0: Reference Book 4 - Section 6.3.4.5 - CVM Results EMV 4.1: Terminal [Online Enciphered PIN] supported Configuration: Conditions:

•


•

Case 01: CVM list in LT is 'Online Enciphered PIN always' (42 00) followed by 'Fail CVM always' (00 00) and wrong PIN is entered

•

Case 02: CVM list in LT is 'Online Enciphered PIN always' (42 00) followed by 'Fail CVM always' (00 00) and a good PIN is entered

•



•


•


•


•


•





according to the last CVM performed Reference Book 4 - Section 2.3.4.5 - CVM Results EMV 4.0: Reference Book 4 - Section 6.3.4.5 - CVM Results EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

Case 01: CVM list in LT is 'Offline Enciphered PIN always' (44 00) and a good PIN is entered

•

Case 02: CVM list in LT is 'NO CVM, if terminal supports (1F 03), followed by Offline Enciphered PIN, always' (44 00) (if PIN is entered it is a good PIN)

•



•


•

CVM Results byte 1 and 2 shall always be set in accordance with last CVM performed in the list.

•


•


•

Case 02: CVM Result shall be set to ‘1F 03 02' or ’44 00 02’

•



Page 1472


2CM.028.04 CVM Results Set With Method Code and Condition Code of Last CVM Performed Test No: 2CM.028.04 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal sets the CVM Results bytes 1 and 2

according to the last CVM performed Reference Book 4 - Section 2.3.4.5 - CVM Results EMV 4.0: Reference Book 4 - Section 6.3.4.5 - CVM Results EMV 4.1: Terminal [NO CVM] supported Configuration: Conditions:

•


•

CVM list in LT is 'NO CVM always' (1F 00) followed by 'Fail CVM, always' (00 00).


•


•

CVM Result shall be set to ‘1F 00 02'

•




2CM.030.00 CVM Result when no CVM performed Test No: 2CM.030.00 - Revision 17 - Number of sub cases: 0 Objective: To ensure that the terminal sets the CVM Results byte 1 to 'No CVM

performed' if no CVM is present or there is no CVM conditions satisfied Reference Book 4 - Section 2.3.4.5 - CVM Results EMV 4.0: Reference Book 4 - Section 6.3.4.5 - CVM Results EMV 4.1:

Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal [NO CVM] not supported Configuration: Conditions:

•


•

CVM list in LT is NO CVM, if terminal supports the CVM (1F 03)


•


•

TVR byte 3, bit 8 = '1' (ie Cardholder verification failed) received at 1st GENERATE AC. TVR byte 3, bit 7 = '0' (ie Recognized CVM) received at 1st GENERATE AC.

•


•



Page 1474




Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal [Amount known before CVM processing] supported Configuration: Conditions:

•


•

CVM list in LT is Fails CVM if Amount under X (00 06) and Amount is over X, but conditions are not satisfied


•


•


•


•






Book Bulletins - Section SU 48 - Bulletin n°48, CVM List Processing (Oct-2007) Terminal [Signature] not supported Configuration: Conditions:

•


•

CVM list in LT is: Signature, if terminal supports the CVM (1E 03)


•


•


•

TVR byte 3, bit 7 = '0' (ie Recognized CVM) received at 1st GENERATE AC.

•


•



Page 1476


2CM.031.00 Terminal Checks Presence of Application Selected Test No: 2CM.031.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that if the terminal has an exception file, the terminal checks

the presence of the application selected in the exception file and does not set the 'Card appears in Exception file' bit in the TVR to 1b, if no match is found with the current PAN Reference Book 4 - Section 2.3.5 - Terminal Risk Management EMV 4.0: Reference Book 4 - Section 6.3.5 - Terminal Risk Management EMV 4.1: Terminal [Exception List] supported Configuration: Conditions:

•

Case 01: Exception File does not contain the PAN of LT

•

Case 02: Exception File does not contain the PAN sequence number of LT


•


•

TVR byte 1, bit 5 = '0' (ie Card does not appear in Exception file,received at 1st GENERATE AC.



2CM.032.00 TVR Set if Match is Found in Exception File Test No: 2CM.032.00 - Revision 15 - Number of sub cases: 2 Objective: To ensure that if the terminal has an exception file, the terminal sets

the 'Card appears in Exception file' bit in the TVR to 1b, if a match is found with the current PAN Reference Book 4 - Section 2.3.5 - Terminal Risk Management EMV 4.0: Reference Book 4 - Section 6.3.5 - Terminal Risk Management EMV 4.1: Terminal [Exception List] supported Configuration: Conditions:

•

The terminal exception file contains data also represented in the LT (I.e. PAN and PAN Sequence Number)1


•


•

TVR byte 1, bit 5 = '1' (ie Card appears in Exception file) received at 1st GENERATE AC.

1

The related test tool script will likely require modification based on the device vendor's implementation of the terminal exception file. Additional subcases may become necessary if the terminal exception list may be configured with variouis independent data objects (i.e. Cardholder Name & Application Label, & PAN OR Cardholder Name & PAN, etc.). In such a situation the laboratory must fully describe the nature of the additional subcases in their test report. Copyright ©2008 EMVCo, LLC. All rights reserved

Page 1478


2CM.033.00 Authorization Response Code Set When Terminal Accepts Transaction Offline Test No: 2CM.033.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal sets Authorization Response Code to

'Offline approved' if result of Terminal Action Analysis is Offline Reference Book 4 - Section 2.3.6 - Terminal Action Analysis EMV 4.0: Reference Book 4 - Section 6.3.6 - Terminal Action Analysis EMV 4.1: Terminal [Offline Only or Offline/Online capable] supported Configuration: Conditions:

•

LT parameters are set so that transaction is approved Offline

•

CDOL1 requests Authorization Response Code.


•


•

Authorization Response Code shall be 'Offline Approved' whatever response of ICC



2CM.034.00 Authorization Response Code Set When Terminal Declines Transaction Offline Test No: 2CM.034.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal sets Authorization Response Code to

'Declined Offline' if result of Terminal Action Analysis is to decline offline Reference Book 4 - Section 2.3.6 - Terminal Action Analysis EMV 4.0: Reference Book 4 - Section 6.3.6 - Terminal Action Analysis EMV 4.1: Terminal NA Configuration: Conditions:

•

LT parameters are set so that transaction is declined off-line

•



•

The terminal shall process the transaction until completion, by requesting an AAC.

•

Authorization Response Code shall be 'Declined Offline'


Page 1480


2CM.035.00 Authorization Response Code Not Set When Terminal Opts To Transmit Transaction Online Test No: 2CM.035.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal does not set Authorization Response Code

to any value if result of Terminal Action Analysis is to transmit online Reference Book 4 - Section 2.3.6 - Terminal Action Analysis EMV 4.0: Reference Book 4 - Section 6.3.6 - Terminal Action Analysis EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•



•


•

Authorization Response Code shall not be filled



2CM.036.00 Terminal Completes Transaction When Card Indicated Approval Test No: 2CM.036.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal completes the transaction if the card

returned an Approval to GENERATE AC. Reference Book 4 - Section 2.3.7 - Card Action Analysis EMV 4.0: Reference Book 4 - Section 6.3.7 - Card Action Analysis EMV 4.1: Terminal [Offline only or Offline/Online capable] supported Configuration:

TAC-Online, TAC-Default & TAC-Denial are zero filled Conditions:

•

IAC-Online, IAC-Default & IAC-Denial are zero filled

•

LT returns TC to first GENERATE AC

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall process the transaction until completion.


Page 1482


2CM.036.01 Terminal Completes Transaction When Card Indicated Approval (2) Test No: 2CM.036.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal completes the transaction if the card

returned an Approval to GENERATE AC. Reference Book 4 - Section 2.3.7 - Card Action Analysis EMV 4.0: Reference Book 4 - Section 6.3.7 - Card Action Analysis EMV 4.1: Terminal Configuration:

TAC-Online, TAC-Default & TAC-Denial are zero filled Conditions:

•

IAC-Online, IAC-Default & IAC-Denial are zero filled

•

LT responds ARQC to 1st GENERATE AC

•

LT returns TC to Second GENERATE AC




2CM.038.00 Terminal Transmits Auth. or Financial Transaction Request Message Test No: 2CM.038.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal transmits a financial or authorization

Request message if the card indicates to process Online in response to first GENERATE AC. Reference Book 4 - Section 2.3.7 - Card Action Analysis EMV 4.0: Reference Book 4 - Section 6.3.7 - Card Action Analysis EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions: LT returns ARQC to GENERATE AC. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

The terminal shall format and transmit a financial or authorization message


Page 1484


2CM.040.00 Advice is Requested by Card and is Supported by the Terminal and transaction is captured Test No: 2CM.040.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal does not create an advice if the card

requests it but the transaction is captured Reference Book 4 - Section 2.3.7 - Card Action Analysis EMV 4.0: Reference Book 4 - Section 6.3.7 - Card Action Analysis EMV 4.1: Terminal ([Advice] supported AND ([Online Data Capture] supported OR [Batch Configuration: Data Capture] supported)) Conditions:

•

LT returns Advice required in first GENERATE AC.

•

Transaction is captured (batch or online data capture)


•


•

The Terminal shall not transmit an advice message



2CM.041.00 Advice is Requested by Card and is Supported by the Terminal and transaction is not captured Test No: 2CM.041.00 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal creates an advice if the card requests it and

the transaction is not captured Reference Book 4 - Section 2.3.7 - Card Action Analysis EMV 4.0: Reference Book 4 - Section 6.3.7 - Card Action Analysis EMV 4.1: Terminal [Advice] supported Configuration: Conditions:

•

LT returns Advice required in first GENERATE AC.

•

Transaction is not captured (such a decline).


•

The terminal shall process the transaction until completion, by requesting an AAC in the 2nd GENERATE AC.

•

The Terminal shall either prepare an offline advice message or transmit an online advice message


Page 1486


2CM.042.00 Terminal Terminates Transaction if Card Indicates 'Service Not Allowed' (Cryptogram Information Data: Service Not allowed) Test No: 2CM.042.00 - Revision 12 - Number of sub cases: 4 Objective: To verify that the terminal interprets correctly answer to a GENERATE

AC command requiring an Advice and indicating a Service not allowed. To ensure that the terminal displays a 'Not accepted' message and terminates the transaction if the card indicates a 'Service not allowed' in response to GENERATE AC. Reference Book 3 - Section 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message

Book 4 - Section 2.3.7 - Card Action Analysis Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message

Book 4 - Section 6.3.7 - Card Action Analysis Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Terminal NA Configuration: Conditions:

•

Conditions are set such as the transaction requests a TC or ARQC in the 1st GENERATE AC (i.e. no TVR match for TAC/IAC-Denial)

•

Case 01: LT returns 'Service not allowed' in first GENERATE AC with AAC (CID = 01)

•

Case 02: LT returns 'Service not allowed' in first GENERATE AC with ARQC (CID = 81)

•

Case 03: LT returns 'Service not allowed' in first GENERATE AC with AAC and advice (CID = 09)

•

Case 04: LT returns 'Service not allowed' in first GENERATE AC with ARQC and advice (CID = 89)



2CM.042.00 Terminal Terminates Transaction if Card Indicates 'Service Not Allowed' (Cryptogram Information Data: Service Not allowed) Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•

The terminal shall terminate the transaction and should display ‘NOT ACCEPTED’


Page 1488


2CM.042.01 Terminal Terminates Transaction if Card Indicates 'Service Not Allowed' (Cryptogram Information Data: Service Not allowed) (2) Test No: 2CM.042.01 - Revision 15 - Number of sub cases: 4 Objective: To verify that the terminal interprets correctly answer to a GENERATE

AC command requiring an Advice and indicating a Service not allowed. Reference Book 3 - Section 2.5.5.4 - Data Field Returned in the Response EMV 4.0: Message

Book 4 - Section 2.3.7 – Card Action Analysis Reference Book 3 - Section 6.5.5.4 - Data Field Returned in the Response EMV 4.1: Message

Book 4 - Section 6.3.7 – Card Action Analysis Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•

Conditions are set such as the transaction is requested online by the Terminal

•

Case 01: LT returns 'Service not allowed' in second GENERATE AC with AAC (CID = 01)

•

Case 02: LT returns 'Service not allowed' in second GENERATE AC with TC (CID = 41)

•

Case 03: LT returns 'Service not allowed' in second GENERATE AC with AAC and advice (CID = 09)

•

Case 04: LT returns 'Service not allowed' in second GENERATE AC with TC and advice (CID = 49)


•

The terminal shall terminate the transaction and should display ‘NOT ACCEPTED’



2CM.042.06 Combined DDA/AC Generation failed and ICC returned an ARQC Test No: 2CM.042.06 - Revision 13 - Number of sub cases: 0 Objective: To ensure that if Combined DDA/AC Generation failed and if the card

returns an ARQC, the terminal sets the 'Combined DDA/AC Generation failed' bit in the TVR to 1b and completes the transaction by performing immediately a second GENERATE AC requesting for an AAC. Reference Book Bulletins - Section SU 6 - Bulletin n°6, Modification to Combined EMV 4.0: Dynamic Data Authentication and Application Cryptogram Generation

(Dec-2001) Reference Book2 - Section 6.6.2 – Dynamic Signature Verification EMV 4.1:


•


•


•

Enhanced Combined DDA/AC signature generated in LT is failed

•

LT returns an ARQC in first GENERATE AC.


particular Enhanced Combined DDA/AC Authentication). Pass Criteria:

•


•



Page 1490


2CM.042.07 Online Capable Terminal Terminates Transaction If Card Indicates ‘Service Not Alowed’ (Cryptogram Information Data: Service Not Allowed) Test No: 2CM.042.07 - Revision 12 - Number of sub cases: 2 Objective: To verify that the terminal interprets correctly answer to a GENERATE

AC command requiring an Advice and indicating a Service not allowed. To ensure that the terminal displays a ‘Not Accepted’ message and terminates the transaction if the card indicates a ‘Service Not Alowed’ in response to GENERATE AC. Reference Book 3 - Section 6.5.5.4 – Data Field Returned in EMV 4.0: Message

the Response

Book 4 - Section 6.3.7 – Card Action Analysis Reference Book 3 - Section 2.5.5.4 – Data Field Returned in EMV 4.1: Message

the Response

Book 4 - Section 2.3.7 – Card Action Analysis Book Bulletins - Section SU 42 - Bulletin n°42, Voice Referrals (Oct2005) Terminal [Offline Only OR Offline/Online capable] supported Configuration: Conditions: Conditions are set such as the terminal request a TC in the 1st

GENERATE AC (ie no TVR match for TAC/IAC-Denial, TAC/IACOnline, or TAC/IAC-Default) •

Case 1: LT returns ‘Service Not Allowed’ in first GENERATE AC with TC (CID = 41)

•

Case 2: LT returns ‘Service Not Allowed’ in first GENERATE AC with TC (CID = 49).

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall terminate the transaction and should display ‘NOT

ALLOWED’.



2CM.042.08 Combined DDA/AC Generation failed and ICC returned an ARQC (2) Test No: 2CM.042.08 - Revision 13 - Number of sub cases: 0 Objective: To ensure that if Combined DDA/AC Generation failed and if the card

returns an ARQC, the terminal sets the 'Combined DDA/AC Generation failed' bit in the TVR to 1b and completes the transaction by performing immediately a second GENERATE AC requesting for an AAC. Reference EMV 4.0: Reference Book2 - Section 6.6.2 – Dynamic Signature Verification EMV 4.1:

Book3 - Section 10.3 - Offline Data Authentication Book Bulletins - Section SU 44 - Bulletin n°44, CDA modified terminal behaviour (Sept-2006) Terminal [CDA] supported AND [Online Only] supported AND [CDA request at Configuration: GENAC1, ARQC] supported Conditions:

•


•


•

Enhanced Combined DDA/AC signature generated in LT is failed

•

LT returns an ARQC in first GENERATE AC.


particular Enhanced Combined DDA/AC Authentication). Pass Criteria:

•


•



Page 1492


2CM.043.00 Terminal Decides To Accept or Decline Transaction and Issues 2nd GENERATE AC Test No: 2CM.043.00 - Revision 10 - Number of sub cases: 2 Objective: To ensure that the terminal issue a second GENERATE AC indicating

the content of the Authorization Response Code, if transaction is processed online Reference Book 4 - Section 2.3.8 - Online Processing EMV 4.0: Reference Book 4 - Section 6.3.8 - Online Processing EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•

Case 01: Issuer returns an Authorization Response Code indicating acceptance

•

Case 02: Issuer returns an Authorization Response Code indicating decline


•


•

The LT shall receive a second GENERATE AC indicating TC for test 1 and AAC for test 2



2CM.044.00 Authorization Response Code is 'Online Approved' Test No: 2CM.044.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the terminal transmit a reversal message, if transaction

is processed online and transaction is captured online and Authorization Response Code is 'online approved' and card returns AAC to second GENERATE AC. Reference Book 4 - Section 2.3.8 - Online Processing EMV 4.0: Reference Book 4 - Section 6.3.8 - Online Processing EMV 4.1: Terminal ([Online Data Capture] supported AND [Online Only or Offline/Online Configuration: capable] supported) Conditions:

•


•

Transactions are captured online (financial message)

•

Authorization Response Code returned is 'online approved'

•

LT returns AAC to second GENERATE AC.


•


•

The Terminal shall format and transmit a Reversal Message in real time.


Page 1494


2CM.045.00 Terminal Support of Issuer Scripts in Authorization or Financial Transaction Response Test No: 2CM.045.00 - Revision 11 - Number of sub cases: 2 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 in authorization or financial response Reference Book 4 - Section 2.3.9 - Issuer-to-Card Script Processing EMV 4.0: Reference Book 4 - Section 6.3.9 - Issuer-to-Card Script Processing EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•

Case 01: Issuer Response contains three '71' scripts where the total length of these constructed data objects is 128 bytes. For example: '71 28 9F 18 04 00 00 00 01 86 1F {'1F' command bytes}' + '71 29 9F 18 04 00 00 00 02 86 20 {'20' command bytes}'+ '71 29 9F 18 04 00 00 00 03 86 20 {'20' command bytes}'

•

Case 02: Issuer Response contains one '71' script where the total length of these constructed data objects is 128 bytes. For example: '71 7E 9F 18 04 00 00 00 01 86 75 {'75' command bytes}'


•


•

The LT shall receive APDU commands according to the scripts sent in the response



2CM.045.01 Terminal Support of Issuer Scripts in Authorization or Financial Transaction Response (2) Test No: 2CM.045.01 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal is able to manage and perform scripts if it


•


•

Case 01: Issuer Response contains three '72' scripts where the total length of these constructed data objects is 128 bytes. For example: '72 28 9F 18 04 00 00 00 01 86 1F {'1F' command bytes}' + '72 29 9F 18 04 00 00 00 02 86 20 {'20' command bytes}'+ '72 29 9F 18 04 00 00 00 03 86 20 {'20' command bytes}'

•

Case 02: Issuer Response contains one '72' script where the total length of these constructed data objects is 128 bytes. For example: '72 7E 9F 18 04 00 00 00 01 86 75 {'75' command bytes}'


•


•



Page 1496


2CM.045.02 Terminal Support of Issuer Scripts in Authorization or Financial Transaction Response (2) Test No: 2CM.045.02 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal is able to manage and perform scripts if it


•


•

Case 01: Issuer Response contains one '71' scrips and one '72' script where the total length of these constructed data objects is 128 bytes. For example: '71 3E 9F 18 04 00 00 00 01 86 35 {'35' command bytes}' + '72 3E 9F 18 04 00 00 00 02 86 35 {'35' command bytes}'

•

Case 02: Issuer Response contains one '71' scrips and two '72' script where the total length of these constructed data objects is 128 bytes. For example: '71 28 9F 18 04 00 00 00 01 86 1F {'1F' command bytes}'+ '72 29 9F 18 04 00 00 00 02 86 20 {'20' command bytes}' + '72 29 9F 18 04 00 00 00 03 86 20 {'20' command bytes}'


•


•




2CM.048.00 Terminal Reporting of Script Identifier Test No: 2CM.048.00 - Revision 11 - Number of sub cases: 8 Objective: To ensure that the terminal reports in the Issuer Script Results the

results of scripts processed Reference Book 4 - Section 2.3.9 - Issuer-to-Card Script Processing EMV 4.0:

Book Bulletins - Section AN 13 - Bulletin n°13, TVR and TSI Bit Settings Following Script Processing (Dec-2003) Reference Book 4 - Section 6.3.9 - Issuer-to-Card Script Processing EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•

All Scripts have an unique Script Identifer

•

Case 01: Issuer script response contains 3 '71' scripts: the two first are ok the last fail

•

Case 02: Issuer script response contains 3 '71' scripts: all are ok

•

Case 03: Issuer script response contains 3 '72' scripts: the two first are ok the last fail

•

Case 04: Issuer script response contains 3 '72' scripts: all are ok

•

Case 05: Issuer script response contains two Tag 71 scripts and one Tag 72 script, the two first Tag 71 script are ok and the Tag 72 script is failed

•

Case 06: Issuer script response contains one Tag 71 script, one Tag 72 script, the two scripts are ok

•

Case 07: Issuer script response contains two Tag 71 scripts and one Tag 72 script , the first Tag 71 scripts failed and the two next scripts are ok

•

Case 08: Issuer script response contains one Tag 71 script and two Tag 72 scripts, the first Tag 71 script is ok, the first tag 72 script failed and the last Tag 72 scripts is ok


Page 1498


2CM.048.00 Terminal Reporting of Script Identifier Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

TVR byte 5 bit 6 = ‘0’ i.e. Script processing before final GENERATE AC not used or successful: cases 02, 03, 04, 05, 06 and 08 received at 2nd GENERATE AC

•

TVR byte 5 bit 6 = ‘1’ i.e. Script processing failed before final GENERATE AC: cases 01 and 07 received at 2nd GENERATE AC

•

TVR byte 5, bit 5 = ‘0’ i.e. Script processing after final GENERATE AC not used or successful: cases 01, 02, 04, 06 and 07 contained in Financial Confirmation message or Batch Data Capture message

•

TVR byte 5, bit 5 = ‘1’ i.e. Script processing failed after final GENERATE AC: cases 03, 05 and 08contained in Financial Confirmation message or Batch Data Capture message

•

Issuer Script Results (contained in Financial Confirmation message or Batch Data Capture message):

•

Case 01 ISR: 20 xx xx xx xx 20 yy yy yy yy 1x zz zz zz zz

•

Case 02 ISR: 20 xx xx xx xx 20 yy yy yy yy 20 zz zz zz zz

•


•

Case 04 ISR: 20 xx xx xx xx 20 yy yy yy yy 20 zz zz zz zz

•


•

Case 06 ISR: 20 xx xx xx xx 20 yy yy yy yy

•

Case 07 ISR: 1x xx xx xx xx 20 yy yy yy yy 20 zz zz zz zz

•

Case 08 ISR: 20 xx xx xx xx 1x yy yy yy yy 20 zz zz zz zz



2CM.052.00 Terminal Creates an Advice When No Message is Created for Transaction Test No: 2CM.052.00 - Revision 15 - Number of sub cases: 6 Objective: To ensure that the terminal creates an Advice message containing the

Issuer Script Results if no message is created for the transaction (declined transaction) Reference Book 4 - Section 2.3.9 - Issuer-to-Card Script Processing EMV 4.0: Reference Book 4 - Section 6.3.9 - Issuer-to-Card Script Processing EMV 4.1: Terminal ([Online Only or Offline/Online capable] supported AND [Advice] Configuration: supported) Conditions:

•


•

Final GENERATE AC returns AAC

•

Case 01: Issuer script response contains 1 Tag 71 script

•

Case 02: Issuer script response contains 3 Tag 71 scripts

•

Case 03: Issuer script response contains 1 Tag 72 script

•

Case 04: Issuer script response contains 3 Tag 72 scripts

•

Case 05: Issuer script response contains 2 Tag 71 scripts and one Tag 72 script

•

Case 06: Issuer script response contains 2 Tag 72 scripts and one Tag 71 script


•


•

The terminal shall create an Advice Message including Issuer Script Results.


Page 1500


2CM.055.00 Terminal Supporting DDA Shall Support SDA Test No: 2CM.055.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal supports Static Data Authentication if it

supports Dynamic Data Authentication Reference Book 4 - Section 2.4 - Conditions for Support of Functions EMV 4.0: Reference Book 4 - Section 6.4 - Conditions for Support of Functions EMV 4.1: Terminal [DDA] supported Configuration:

Conditions:

•

Terminal contains the CA Public Key referenced in LT

•


•

signed Static Data is good in LT

•

CDOL1 requests Terminal Capabilities


•


•

Terminal Capabilities shall indicate Static Data Authentication support

•


•


•


•




2CM.055.01 Terminal Supporting CDA Shall Support SDA Test No: 2CM.055.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal supports Static Data Authentication if it

supports Combined DDA/AC Data Authentication Reference Book 4 - Section 2.4 - Conditions for Support of Functions EMV 4.0: Reference Book 4 - Section 6.4 - Conditions for Support of Functions EMV 4.1: Terminal [CDA] supported Configuration:

Conditions:

•


•

AIP of LT indicates Static Data Authentication is supported (AIP byte 1 bit 7 = 1)

•

Signed Static Data is good in LT

•



•


•


•

TVR byte 1, bit 7 = '0' (ie Static Data Authentication succeeded) contained in Financial Confirmation message or Batch Data Capture message

•


•


•



Page 1502


2CM.056.00 Offline Only Terminal Shall Support SDA Test No: 2CM.056.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal supports Static Data Authentication if it is

offline only Reference Book 4 - Section 2.4 - Conditions for Support of Functions EMV 4.0: Reference Book 4 - Section 6.4 - Conditions for Support of Functions EMV 4.1: Terminal [Offline Only] supported Configuration:

Terminal contains the CA Public Key referenced in LT Conditions:

•


•


•



•


•


•


•




2CM.057.00 Offline Terminal With Online Capability Shall Support SDA Test No: 2CM.057.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal supports Static Data Authentication if it is

offline with online capabilities Reference Book 4 - Section 2.4 - Conditions for Support of Functions EMV 4.0: Reference Book 4 - Section 6.4 - Conditions for Support of Functions EMV 4.1: Terminal [Offline/Online capable] supported Configuration:

Conditions:

•


•


•


•



•


•


•

TVR byte 1, bit 7 = '0' (ie Static Data Authentication succeeded, eceived at 1st GENERATE AC.

•



Page 1504


2CM.058.00 Offline Only Terminal Shall Support Terminal Risk Management Test No: 2CM.058.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal supports Terminal Risk Management if it is

offline only Reference Book 4 - Section 2.4 - Conditions for Support of Functions EMV 4.0: Reference Book 4 - Section 6.4 - Conditions for Support of Functions EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•


•



•


•


•


•


•




2CM.059.00 Offline Terminal With Online Capability Shall Support Terminal Risk Management Test No: 2CM.059.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal supports Terminal Risk Management if it is

offline with online capabilities Reference Book 4 - Section 2.4 - Conditions for Support of Functions EMV 4.0: Reference Book 4 - Section 6.4 - Conditions for Support of Functions EMV 4.1: Terminal [Offline/Online capable] supported Configuration: Conditions:

•


•


•


•



•


•


•


•


•



Page 1506


2CM.060.00 Financial Institution Terminal Supports TRM Test No: 2CM.060.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that the terminal supports Terminal Risk Management if it is

a Financial institution Terminal Reference Book 4 - Section 2.4 - Conditions for Support of Functions EMV 4.0: Reference Book 4 - Section 6.4 - Conditions for Support of Functions EMV 4.1: Terminal [Terminal Type 1x] supported AND ([Velocity Checking] supported OR Configuration: [Floor Limit Checking] supported OR [Random Transaction Selection]

supported OR [Exception File] supported OR [Transaction Log] supported) Conditions:

•


•


•


•


•

CDOL1 requests Terminal Type


•


•


•


•


•





Page 1508


2CM.061.00 Merchant Controlled Terminal Supports TRM Test No: 2CM.061.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal supports Terminal Risk Management if it is

a Merchant Controlled Terminal Reference Book 4 - Section 2.4 - Conditions for Support of Functions EMV 4.0: Reference Book 4 - Section 6.4 - Conditions for Support of Functions EMV 4.1: Terminal [Terminal Type 2x] supported Configuration: Conditions:

•


•


•


•


•

CDOL1 requests Terminal Type


•


•


•


•


•




2CM.062.00 Terminal Displays Amount of Transaction Test No: 2CM.062.00 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal indicates the amount of the transaction to

the cardholder Reference Book 4 - Section 2.5.1 - Amount Entry and Management EMV 4.0: Reference Book 4 - Section 6.5.1 - Amount Entry and Management EMV 4.1: Terminal NA Configuration: Conditions: NA Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

The transaction amount shall be indicated to the cardholder preferably by means of the terminal display, alternatively by printing on the receipt.


Page 1510


2CM.063.00 Cashback Amount is Transmitted in the Amount, Other Data Object Test No: 2CM.063.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal uses Amount Other field for Cash Back

Amount, if cash back is supported Reference Book 4 - Section 2.5.1 - Amount Entry and Management EMV 4.0: Reference Book 4 - Section 6.5.1 - Amount Entry and Management EMV 4.1: Terminal [CashBack] supported Configuration: Conditions:

•

AUC in LT indicate cashback supported

•

CDOL1 requests Amount Other (in Numeric or Binary format)

Action: Cardholder asks for Cash back Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

Amount Other shall contain value entered for Cashback



2CM.064.00 Purchase and Cashback Transmitted in Amount Authorised Test No: 2CM.064.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal include Purchase Amount and Cashback

Amount in Amount Authorized Reference Book 4 - Section 2.5.1 - Amount Entry and Management EMV 4.0: Reference Book 4 - Section 6.5.1 - Amount Entry and Management EMV 4.1: Terminal [CashBack] supported Configuration: Conditions:

•


•

CDOL1 requests Amount Authorized (in Numeric or Binary format), and Amount Other (in Numeric or Binary format)


•


•

Amount Authorized shall be the sum of Cashback Amount and Purchase Amount


Page 1512


2CM.066.00 Authorised Amount Is Expressed With Implicit Decimal Point Test No: 2CM.066.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal stores Amount Authorized with Implicit

Decimal Point Reference Book 4 - Section 2.5.1 - Amount Entry and Management EMV 4.0: Reference Book 4 - Section 6.5.1 - Amount Entry and Management EMV 4.1: Terminal NA Configuration: Conditions:

•

Purchase Amount has decimal values

•

CDOL1 requests Amount Authorized


•


•

Amount Authorized shall be expressed with implicit decimal point for the currency used



2CM.067.00 Other Amount Is Expressed With Implicit Decimal Point Test No: 2CM.067.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal stores Amount Other with Implicit Decimal

Point Reference Book 4 - Section 2.5.1 - Amount Entry and Management EMV 4.0: Reference Book 4 - Section 6.5.1 - Amount Entry and Management EMV 4.1: Terminal [CashBack] supported Configuration: Conditions:

•

Purchase Amount has decimal values

•


•

CDOL1 requests Amount Other


•


•

Amount Other shall be expressed with implicit decimal point for the currency used


Page 1514


2CM.074.00 Terminal Displays Message To Attendant When Issuer Requests Voice Referral Test No: 2CM.074.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Authorization Response Code returned by the

issuer, indicates a voice referral, an attended terminal displays the 'Call Your Bank' message Reference Book 4 - Section 2.5.2 - Voice Referrals EMV 4.0: Reference Book 4 - Section 6.5.2 - Voice Referrals EMV 4.1: Terminal ([Online Only or Offline/Online capable] supported AND [Issuer Configuration: Referral] supported) Conditions:

•


•

Authorization Response Code returned in the response indicates a voice Referral


•


•

Terminal shall display the 'Call your Bank' message



2CM.075.00 Data Displayed or Printed to Perform Referral initiated by issuer Test No: 2CM.075.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Authorization Response Code returned by the

issuer, indicates a voice referral, an attended terminal displays or prints appropriate application data like the PAN Reference Book 4 - Section 2.5.2 - Voice Referrals EMV 4.0: Reference Book 4 - Section 6.5.2 - Voice Referrals EMV 4.1: Terminal ([Online Only or Offline/Online capable] supported AND [Issuer Configuration: Referral] supported) Conditions:

•


•



•


•

Terminal shall display or print PAN and other appropriate data


Page 1516


2CM.076.00 Messages Displayed Requesting Attendant to Indicate Approval or Denial of a Referral initiated by issuer Test No: 2CM.076.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Authorization Response Code returned by the

issuer, indicates a voice referral, an attended terminal displays a message requesting the attendant to enter the response from the Bank Reference Book 4 - Section 2.5.2 - Voice Referrals EMV 4.0: Reference Book 4 - Section 6.5.2 - Voice Referrals EMV 4.1: Terminal ([Online Only or Offline/Online capable] supported AND [Issuer Configuration: Referral] supported) Conditions:

•


•



•


•

Terminal shall display a message requesting the attendant to enter the response from the Bank (after 'Call your Bank' and 'data' messages)



2CM.077.00 Authorization Response Code when Referral is initiated by Issuer Test No: 2CM.077.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Authorization Response Code returned by the

issuer, indicates a voice referral, an attended terminal does not modify the Authorization Response Code received Reference Book 4 - Section 2.5.2 - Voice Referrals EMV 4.0: Reference Book 4 - Section 6.5.2 - Voice Referrals EMV 4.1: Terminal ([Online Only or Offline/Online capable] supported AND [Issuer Configuration: Referral] supported) Conditions:

•


•


•



•


•

Authorization Response Code shall be the same as the one received from issuer.


Page 1518


2CM.078.00 Terminal Issues Second GENERATE AC Test No: 2CM.078.00 - Revision 10 - Number of sub cases: 2 Objective: To ensure that if the Authorization Response Code returned by the

issuer, indicates a voice referral, an attended Terminal sends a second GENERATE AC command in accordance with response from the Bank entered manually Reference Book 4 - Section 2.5.2 - Voice Referrals EMV 4.0: Reference Book 4 - Section 6.5.2 - Voice Referrals EMV 4.1: Terminal ([Online Only or Offline/Online capable] supported AND [Issuer Configuration: Referral] supported) Conditions:

•


•


•

Case 01: transaction approved by the Bank

•

Case 02: transaction declined by the Bank


•


•

LT may receive an EXTERNAL AUTHENTICATE command

•

xy = 01: LT shall receive a second GENERATE AC command requesting a TC

•

xy = 02: LT shall receive a second GENERATE AC command requesting a AAC



2CM.079.00 TVR Set When Merchant Forces Transaction Online Test No: 2CM.079.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if a transaction is forced online, an attended Terminal

sets the 'Merchant forced transaction online' bit in the TVR to 1b. Reference Book 4 - Section 2.5.3 - Transaction Forced Online EMV 4.0: Reference Book 4 - Section 6.5.3 - Transaction Forced Online EMV 4.1: Terminal ([Attended] supported AND [Forced Online] supported) Configuration: Conditions: NA Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

TVR byte 4, bit 4 = '1' (ie Merchant forced transaction) received at 2nd GENERATE AC.


Page 1520


2CM.080.00 Attendant forces Approval of the Transaction Test No: 2CM.080.00 - Revision 10f - Number of sub cases: 2 Objective: To ensure that if attendant forces the approval of a transaction, the

terminal either sends online financial advice or creates a batch data capture entry Reference Book 4 - Section 2.5.4 - Transaction Forced Acceptance EMV 4.0: Reference Book 4 - Section 6.5.4 - Transaction Forced Acceptance EMV 4.1: Terminal ([Attended] supported AND [Forced Approval] supported) Configuration: Conditions:

•

Case 01: LT response is an AAC to the first Generate AC

•

Case 02: LT response is an ARQC to the first Generate AC and AAC to the second

Action: Attendant forces acceptance of the transaction Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

The Terminal shall either send online financial advice or create a batch data capture entry



2CM.081.00 Authorization Response Code when acceptance is forced Test No: 2CM.081.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if attendant forces the approval of a transaction, the

terminal does not modify the Authorization Response Code Reference Book 4 - Section 2.5.4 - Transaction Forced Acceptance EMV 4.0: Reference Book 4 - Section 6.5.4 - Transaction Forced Acceptance EMV 4.1: Terminal (([Attended] supported AND [Forced Approval] supported) AND [Online Configuration: Only or Offline/Online capable] supported) Conditions:

•


•

Case 01: Host declines (Authorisation Response Code indicates a decline)

•

Case 02: Host approves (Authorisation Response Code indicates an Approval) and LT declines at 2nd GENERATE AC with an AAC


•


•

Authorization Response Code in online financial advice or in batch data capture entry shall be the same as the one received from Issuer


Page 1522


2CM.082.00 Terminal Sets Indicator When Attendant forces Approval of the Transaction Test No: 2CM.082.00 - Revision 12 - Number of sub cases: 4 Objective: To ensure that the terminal sets an indicator in the online advice or

batch data capture if the attendant forced acceptance of the transaction. Reference Book 4 - Section 2.5.4 - Transaction Forced Acceptance EMV 4.0: Reference Book 4 - Section 6.5.4 - Transaction Forced Acceptance EMV 4.1: Terminal (([Attended] supported AND [Forced Approval] supported) AND [Online Configuration: Only or Offline/Online capable] supported) Conditions:

•


•

Case 01 - Attendant forces acceptance of card generated offline decline (i.e. 1st GENERATE AC request = ARQC, response = AAC)

•

Case 02: Attendant forces acceptance of device generated offline decline (i.e. 1st GENERATE AC request = AAC)

•

Case 03: Attendant forces acceptance of device generated online decline (i.e. 2nd GENERATE AC request = TC, response = AAC)

•

Case 04: Attendant forces acceptance of device generated online decline (i.e. 2nd GENERATE AC request = AAC)


•


•

The terminal shall set an indicator in the online advice or batch data capture that the attendant forced acceptance of the transaction



2CM.083.00 Terminal Maintains Transaction Sequence Counter Test No: 2CM.083.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal maintains a Transaction Sequence Counter Reference Book 4 - Section 2.5.5 - Transaction Sequence Counter EMV 4.0: Reference Book 4 - Section 6.5.5 - Transaction Sequence Counter EMV 4.1: Terminal NA Configuration: Conditions:

•

A minimun of 4 Transaction are performed

•

If terminal is online capable: 2 transactions are performed online and 2 transactions are performed offline in the same test

•

CDOL1 requests Transaction Sequence Counter


•

The terminal shall process the transaction until completion, by requesting a TC or an AAC for each transaction

•

Transaction Sequence Counter shall be incremented by one at each transaction


Page 1524


2CM.085.00 Generation of Unpredictable Number Test No: 2CM.085.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal is able to generate an unpredictable

number Reference Book 4 - Section 2.5.6 - Unpredictable Number EMV 4.0: Reference Book 4 - Section 6.5.6 - Unpredictable Number EMV 4.1: Terminal NA Configuration: Conditions:

•

A minimun of 4 Transaction are performed

•

CDOL1 requests Unpredictable Number


•

The terminal shall process the transaction until completion, by requesting a TC or an AAC for each transaction

•

Unpredictable Number shall be different at each transaction



2CM.086.00 Terminal Reading of Service Code on Magnetic Stripe Test No: 2CM.086.00 - Revision 12 - Number of sub cases: 2 Objective: To ensure that the terminal displays a message 'Use Chip Reader' if

the magstripe is read and the Service Code begins with '2' or '6', and if the terminal does not have a combined IC and magnetic stripe reader. Reference Book 4 - Section 2.6 - Card Reading EMV 4.0:

Bulletins - Section AN 28 - Bulletin n°28, Data source for ChipOriginated Messages (July-2005) Reference Book 4 - Section 6.6 - Card Reading EMV 4.1: Terminal [Combined IC and Magnetic stripe reader] not supported Configuration: Conditions:

•

A data is present in magnetic and not in ICC : Service Code ‘5F 30’

•

Case 01: Magstripe LT is read with Service Code beginning with '2'

•



Magstripe shall be swiped first, and the ICC inserted following prompt. Pass Criteria:

•

The terminal shall prompt the user to insert the ICC

•

The authorization message, financial transaction message, or batch file shall not contain the magnetic stripe data (Service Code’5F 30’)

•



Page 1526


2CM.087.00 Terminal Reading of Service Code on Magnetic Stripe Test No: 2CM.087.00 - Revision 10 - Number of sub cases: 2 Objective: To ensure that the terminal switch to IC process if the magstripe is read

and the Service Code begins with '2' or '6' Reference Book 4 - Section 2.6 - Card Reading EMV 4.0: Reference Book 4 - Section 6.6 - Card Reading EMV 4.1: Terminal ([Combined IC and Magnetic stripe reader] supported AND [Magnetic Configuration: stripe first] supported) Conditions:

•

LT is a combined magstripe and Chip ICC

•


•


Action: NA Procedure: Application in LT is selected and transaction is processed with LT

(Magstripe shall be used) Pass Criteria: The terminal shall switch to IC process and shall send EMV command

to LT



2CM.091.00 POS Entry Mode Code Read Test No: 2CM.091.00 - Revision 12 - Number of sub cases: 2 Objective: To ensure that if the terminal fails to read the ICC but can read

magstripe and Service code begins with '2' or '6', the terminal set POS entry mode code to 'Magnetic Stripe read, last transaction was an unsuccessful IC read' in the transaction message Reference Book 4 - Section 2.6.2 - Exception Handling EMV 4.0: Reference Book 4 - Section 6.6.2 - Exception Handling EMV 4.1: Terminal [Magstripe Reader] supported AND [Attended] supported Configuration: Conditions:

•

LT has non functional ICC

•


•


Action: NA Procedure: Transaction is started with LT ICC Pass Criteria:

•

The terminal shall switch to magstripe processing

•

The transaction message (financial or batch data capture) shall have the POS entry mode code set to 'Magnetic Stripe read, last transaction was an unsuccessful IC read'


Page 1528


2CM.092.00 Calculation of Dates Associated With Static Data Authentication Test No: 2CM.092.00 - Revision 12 - Number of sub cases: 5 Objective: To ensure that the terminal is capable of properly calculating date

associated with Static data authentication for dates before, including, and after the year 2000 Reference Book 4 - Section 2.7.1 - Data Authentication EMV 4.0: Reference Book 4 - Section 6.7.1 - Data Authentication EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

Issuer Public Key Certificate in LT is calculated with different Certificate Expiration Dates:

•

Case 01: Certificate Expiration Date is 101010

•


•


•


•




•


•


•

TVR byte 1, bit 7 shall be set according to the Certificate Expiration Date ('1' if before the current date, '0' if in or after the



2CM.092.00 Calculation of Dates Associated With Static Data Authentication current date), received at 1st GENERATE AC. •


•



Page 1530


2CM.093.00 Calculation of Dates Associated With Processing Restrictions Test No: 2CM.093.00 - Revision 12 - Number of sub cases: 12 Objective: To ensure that the terminal is capable of properly calculating date

associated with processing restrictions for dates before, including, and after the year 2000 Reference Book 4 - Section 2.7.2 - Processing Restrictions EMV 4.0: Reference Book 4 - Section 6.7.2 - Processing Restrictions EMV 4.1: Terminal NA Configuration: Conditions:

•

Case 01: Application Expiration Date is 900101

•


•


•

Case 04: Application Effective Date is 000112

•


•


•


•


•


•


•


•



•




2CM.093.00 Calculation of Dates Associated With Processing Restrictions requesting a TC or an AAC. •

TVR byte 2, bit 7 shall be set according to the Application Expiration Dates ('1' if the current date is after the expiration date,, '0' if the current date is before the expiration date), received at 1st GENERATE AC.

•

TVR byte 2, bit 6 shall be set according to the Application Effective Dates ('0' if the current date is after the effective date, '1' if the current date is before the effective date), received at 1st GENERATE AC.


Page 1532


2CM.094.00 Calculation, Storage, and Display Date-Dependant Fields For Year 2000 + Test No: 2CM.094.00 - Revision 16 - Number of sub cases: 3 Objective: To ensure that the terminal is able to accurately calculate and store

date dependent fields representing the year 2000 Reference Book 4 - Section 2.7.3 - Data Management EMV 4.0: Reference Book 4 - Section 6.7.3 - Date Management EMV 4.1: Terminal [Internal Date Management] supported Configuration: Conditions:

•

CDOL1 requests Transaction Date and Transaction Time

•

Case 01: Terminal Date is set to 31/12/2020 23h 59min

•


•



requesting a TC or an AAC. Transaction Date shall have been updated to correct value: * 01/01/2021 * 01/03/2013 * 29/02/2012



2CM.094.01 Calculation, Storage, and Display Date-Dependant Fields For Year 2000 + Test No: 2CM.094.01 - Revision 15 - Number of sub cases: 3 Objective: To ensure that the terminal is able to accurately calculate and store

date dependent fields representing the year 2000 Reference Book 4 - Section 2.7.3 - Data Management EMV 4.0: Reference Book 4 - Section 6.7.3 - Date Management EMV 4.1: Terminal [Online Only] Configuration: supported Conditions:

supported AND [Internal Date Management] not

•

CDOL1 requests Transaction Date and Transaction Time

•

Case 01: Terminal Date either in terminal host and in internal clock (if supported) is set to 31/12/2020 23h 59min

•


•



requesting a TC or an AAC. Transaction Date shall have been updated to correct value: * 01/01/2021 * 01/03/2013 * 29/02/2012


Page 1534


2CM.095.00 Processing the Year Test No: 2CM.095.00 - Revision 10g - Number of sub cases: 6 Objective: To ensure that the terminal is able process 2 digits year correctly Reference Book 4 - Section 2.7.3 - Data Management EMV 4.0: Reference Book 4 - Section 6.7.3 - Date Management EMV 4.1: Terminal NA Configuration: Conditions:

•

Case 01: Application Expiration Date with year 00

•


•


•


•


•



•


•

TVR byte 2, bit 7 shall be set according to the Application Expiration Dates ('1' if before the current date, '0' if after the current date), received at 1st GENERATE AC.



2CM.102.00 Display For Attendant for Attended Terminal Test No: 2CM.102.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that if the terminal is attended, it has a display for the

attendant Reference Book 4 - Section 3.2 - Display EMV 4.0: Reference Book 4 - Section 7.2 - Display EMV 4.1: Terminal [Attended] supported Configuration: Conditions: NA Action: NA Procedure: Visual inspection by the tester is required Pass Criteria: Terminal shall have a display for the attendant


Page 1536


2CM.103.00 Display of Alphanumeric Characters Test No: 2CM.103.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that if the terminal has a display, it is capable of displaying at

least 32 alphanumeric characters (two lines of 16 positions each). Reference Book 4 - Section 3.2 - Display EMV 4.0: Reference Book 4 - Section 7.2 - Display EMV 4.1: Terminal [Display] supported Configuration: Conditions: NA Action: NA Procedure: Visual inspection by the tester is required Pass Criteria: Display shall be capable of displaying at least 32 alphanumeric

characters (two lines of 16 positions each).



2CM.105.00 Protection of Captured Transactions and Advices Stored Test No: 2CM.105.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that when the terminal supports batch data capture, the

captured transactions and advices stored in the terminal are not erased or altered until the next reconciliation with the acquiring system. Reference Book 4 - Section 3.3 - Memory Protection EMV 4.0: Reference Book 4 - Section 7.3 - Memory Protection EMV 4.1: Terminal [Batch Data Capture] supported Configuration: Conditions: NA Action: NA Procedure:

•

Several Transactions are performed with the terminal.

•

Transaction stored are read before reconciliation with the acquiring system

Pass Criteria: The Capture transactions and advices stored in the terminal shall not

be erased or altered.


Page 1538


2CM.106.00 Clock With Local Date and Time Test No: 2CM.106.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that Offline-only terminals and offline terminals with online

capability have a clock with the local date and time Reference Book 4 - Section 3.4 - Clock EMV 4.0: Reference Book 4 - Section 7.4 - Clock EMV 4.1: Terminal [Offline Only or Offline/Online capable] supported Configuration: Conditions: CDOL1 requests Transaction Date and Transaction Time Action: NA Procedure: Several Transactions are performed with the terminal. Pass Criteria: Transaction Date and Time shall be coherent.



2CM.107.00 Capability of Terminal Printer Test No: 2CM.107.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if present, the printer shall be able to print 20 characters

per line Reference Book 4 - Section 3.5 - Printer EMV 4.0: Reference Book 4 - Section 7.5 - Printer EMV 4.1: Terminal [Printer] supported Configuration: Conditions: 10 bytes (20 characters) AID in LT. For example, 'A0 00 00 00 09 08 07

06 05 04' Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: AID shall be printed correctly on the receipt


Page 1540


2CM.109.00 Magnetic Stripe Reader Using Full Track 1 and/or Track 2 Test No: 2CM.109.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that if present, terminal Magstripe Reader is able to read full

track 1 and /or track 2 Reference Book 4 - Section 3.6 - Magnetic Stripe Reader EMV 4.0: Reference Book 4 - Section 7.6 - Magnetic Stripe Reader EMV 4.1: Terminal [Magstripe Reader] supported Configuration: Conditions: NA Action: NA Procedure: Transaction is performed with magstripe LT Pass Criteria: Terminal shall be able to read either Track 1 or Track 2 or both



2CM.129.00 PIN Pad Shall Support Entry of 4-12 Digit PIN Test No: 2CM.129.00 - Revision 10g - Number of sub cases: 5 Objective: To ensure that PIN Pad terminal supports 4 to 12 digits PIN. Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.0: Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.1: Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•


•

CVM in LT is Plaintext PIN verification performed by ICC always (01 00)

•

Case 01: PIN in LT has a length of 4 digits

•


•


•


•


Action: PIN is presented correctly Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•


•

PIN received by LT shall be OK


Page 1542


2CM.129.01 PIN Pad Shall Support Entry of 4-12 Digit PIN (2) Test No: 2CM.129.01 - Revision 10g - Number of sub cases: 5 Objective: To ensure that PIN Pad terminal supports 4 to 12 digits PIN. Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.0: Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

CVM in LT is Enciphered PIN verification performed by ICC, always (04 00)

•


•


•


•


•



•


•


•

TSI byte 1, bit 7 = '1' (ie Cardholder verification was performe) received at 1st GENERATE AC.

•

PIN received by LT shall be OK



2CM.129.02 PIN Pad Shall Support Entry of 4-12 Digit PIN (online PIN) Test No: 2CM.129.02 - Revision 10g - Number of sub cases: 5 Objective: To ensure that PIN Pad terminal supports 4 to 12 digits PIN when CVM

to be performed is online PIN. Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.0: Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.1: Terminal [Online Enciphered PIN] supported Configuration: Conditions:

•


•

CVM in LT is enciphered PIN verified online, always (02 00)

•


•


•


•


•



•


•

TVR byte 3, bit 8 = ‘0’ (ie Cardholder verification successful) received at 1st GENERATE AC.

•


•

TSI byte 1, bit 7 = ‘1’ (ie Cardholder verification was performed) received at 1st GENERATE AC.

•

PIN transmitted in the online message shall match the value entered at the PIN pad.


Page 1544




2CM.130.00 Display of Indication of Entry on PIN Pad - Protection of Values of Entered PIN Test No: 2CM.130.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that when a display is present on a PIN Pad, an indication of

the entry of each digit shall be displayed To ensure that when a display is present on a PIN Pad, the values of the entered PIN are not displayed or disclosed by visible or audible feedback means, in accordance with ISO 9564-1 Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.0: Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.1: Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•


•

CVM in LT is Plaintext PIN verification performed by ICC, always (01 00)


•


•

An indication of the entry of each digit shall be displayed

•

The value of the entered PIN shall not be displayed

•

The value of the entered PIN shall not be disclosed by audible feedback means


Page 1546


2CM.130.01 Display of Indication of Entry on PIN Pad - Protection of Values of Entered PIN (2) Test No: 2CM.130.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that when a display is present on a PIN Pad, an indication of

the entry of each digit shall be displayed To ensure that when a display is present on a PIN Pad, the values of the entered PIN are not displayed or disclosed by visible or audible feedback means, in accordance with ISO 9564-1 Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.0: Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.1: Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•


•

CVM in LT is Enciphered offline PIN verification performed by ICC, always (04 00)


•


•


•


•




2CM.130.02 Display of Indication of Entry on PIN Pad - Protection of Values of Entered PIN (3) Test No: 2CM.130.02 - Revision 10g - Number of sub cases: 00 Objective: To ensure that when a display is present on a PIN Pad, an indication of

the entry of each digit shall be displayed To ensure that when a display is present on a PIN Pad, the values of the entered PIN are not displayed or disclosed by visible or audible feedback means, in accordance with ISO 9564-1 Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.0: Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.1: Terminal [Online Enciphered PIN] supported Configuration: Conditions:

•


•

CVM in LT is Enciphered online PIN verification performed by ICC, always (02 00)


•


•


•


•



Page 1548


2CM.137.00 Protection of PIN During Online PIN Verification Test No: 2CM.137.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal enciphers the online PIN according to ISO

9564-1 and transmits it according to the payment system's rules, if the terminal supports online PIN verification Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.0: Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.1: Terminal [Online Enciphered PIN] supported Configuration: Conditions:

•


•

CVM in LT is enciphered PIN verified online, always (02 00)


•


•

The enciphered PIN Data in financial or authorization request message shall contain the PIN entered enciphered according to ISO 9564-1



2CM.140.00 Amount Entry Process Separate From PIN Entry Process Test No: 2CM.140.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Terminal is attended and supports PIN entry, the

amount entry process is separate from the PIN entry process Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.0: Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.1: Terminal ([Attended] supported AND [Offline Plaintext PIN] supported) Configuration: Conditions:

•


•

CVM in LT is Plaintext PIN verification performed by ICC, always (01 00)


•


•

The amount entry process shall be separated from the PIN entry process to avoid any accidental display of a PIN on the terminal display


Page 1550


2CM.140.01 Amount Entry Process Separate From PIN Entry Process (2) Test No: 2CM.140.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that if the Terminal is attended and supports PIN entry, the

amount entry process is separate from the PIN entry process Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.0: Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.1: Terminal ([Attended] supported AND [Offline Enciphered PIN] supported) Configuration: Conditions:

•


•

CVM in LT is Enciphered PIN verification performed by ICC, always (04 00)


•


•




2CM.140.02 Amount Entry Process Separate From PIN Entry Process (3) Test No: 2CM.140.02 - Revision 10g - Number of sub cases: 00 Objective: To ensure that if the Terminal is attended and supports PIN entry, the

amount entry process is separate from the PIN entry process Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.0: Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.1: Terminal ([Attended] supported AND [Online Enciphered PIN] supported) Configuration: Conditions:

•


•

CVM in LT is Enciphered Online PIN verification performed, always (02 00)


•


•



Page 1552


2CM.141.00 Amount Validated by Cardholder (Plaintext PIN) Test No: 2CM.141.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the Amount entry is validated by the cardholder before

entry of the PIN if the Terminal is attended and supports PIN entry and Amount and PIN are entered on the same key pad Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.0: Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.1: Terminal (([Attended] supported AND [Amount and PIN are entered on same Configuration: keypad]) AND [Offline Plaintext PIN] supported) Conditions:

•


•

CVM in LT is Plaintext PIN verification performed by ICC, if terminal supports (01 03)


•


•

Amount entry and PIN entry are clearly separate operations.



2CM.141.01 Amount Validated by Cardholder (Enciphered PIN Offline) Test No: 2CM.141.01 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the Amount entry is validated by the cardholder before

entry of the PIN if the Terminal is attended and supports PIN entry and Amount and PIN are entered on the same key pad Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.0: Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.1: Terminal (([Attended] supported AND [Amount and PIN are entered on same Configuration: keypad]) AND [Offline Enciphered PIN] supported) Conditions:

•


•

CVM in LT is Enciphered PIN verification performed by ICC, if terminal supports (04 03)


•


Amount entry and PIN entry are clearly separate operations.


Page 1554


2CM.141.02 Amount Validated by Cardholder (Enciphered PIN Online) Test No: 2CM.141.02 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the Amount entry is validated by the cardholder before

entry of the PIN if the Terminal is attended and supports PIN entry and Amount and PIN are entered on the same key pad Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.0: Reference Book 2 - Section 11.1.2 - PIN Pads EMV 4.1: Terminal (([Attended] supported AND [Amount and PIN are entered on same Configuration: keypad]) AND [Online Enciphered PIN] supported) Conditions:

•


•

CVM in LT is enciphered PIN verification online, if terminal supports (02 03)


•


•

Amount entry and PIN entry are clearly separate operations



Software Architecture


Page 1556


2CN.004.00 Data Elements are Initialised in Terminal Test No: 2CN.004.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the data elements listed in "Data Elements Table" Book

3 Annex A are initialized in the terminal or obtainable at the time of a transaction Reference Book 4 - Section 6 - Data Management EMV 4.0: Reference Book 4 - Section 10 - Data Management EMV 4.1: Terminal NA Configuration: Conditions:

•

CDOL1 requests (several tests can be made since length is too long to return all data):

- Account Type - Acquirer Identifier. - Additional Terminal Capabilities. - Amount, Authorized (Binary) - Amount, Authorized (Numeric) - Amount, Other (Binary) - Amount, Other (Numeric) - Amount Reference Currency. - Application Identifier. - Application Version Number. - CVM Results. - Certification Authority Public Key Index. - Interface Device Serial Number. - Merchant Category Code.



2CN.004.00 Data Elements are Initialised in Terminal - Merchant Identifier. - Merchant Name and Location - POS Entry Mode. - Terminal Capabilities. - Terminal Country Code. - Terminal Floor Limit. - Terminal identification. - Terminal Risk Management Data. - Terminal Type. - Terminal Verification Results. - Transaction Currency Code. - Transaction Currency Exponent. - Transaction Date. - Transaction Reference Currency Code. - Transaction Reference Currency Exponent. - Transaction Sequence Counter. - Transaction Status Information. - Transaction Time. - Transaction Type. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

Data Element returned by the terminal shall have correct format and coherent value:


Page 1558


2CN.004.00 Data Elements are Initialised in Terminal - Account Type - b - Acquirer Identifier - n 6-11 - Additional Terminal Capabilities - b - Amount Authorized - b - Amount Authorized - n 12 - Amount Other - b - Amount Other - n 12 - Amount Reference Currency - b - Application Identifier - b - Application Version Number - b -CVM Results - b - Certification Authority Public Key Index - b - Interface Device Serial Number - an 8 -Merchant Category Code - n 4 - Merchant Identifier - ans 15 - Merchant Name and Location – ans -POS Entry Mode - n 2 - Terminal Capabilities - b - Terminal Country Code - n 3 - Terminal Floor Limit - b - Terminal identification - an 8 -Terminal Risk Management Data - b - Terminal Type - n 2



2CN.004.00 Data Elements are Initialised in Terminal - Terminal Verification Results - b -Transaction Currency Code - n 3 - Transaction Currency Exponent - n 1 - Transaction Date - n 6 (YYMMDD) - Transaction Reference Currency Code - n 3 - Transaction Reference Currency Exponent - n 1 - Transaction Sequence Counter - n 4-8 - Transaction Status Information - b - Transaction Time - n 6 (HHMMSS) - Transaction Type - n 2


Page 1560


2CN.012.00 Language Support by Terminal Test No: 2CN.012.00 - Revision 11 - Number of sub cases: 6 Objective: To ensure that the terminal has parameters initialized so that it can

identify what language(s) are supported to process the card's Language Preference Reference Book 4 - Section 6.1 - Application Independent Data EMV 4.0:

Book Bulletins - Section AN 12 - Bulletin n°12, Language Preference Coding (Jul-2003) Reference Book 4 - Section 10.1 - Application Independent Data EMV 4.1: Terminal NA Configuration: Conditions:

•

Case 01: LT language preference (coded in lower case) matches one language supported by the terminal

•

Case 02: LT language preference (coded in lower case) matches all languages supported by the terminal (if supporting multiple languages)

•

Case 03: LT language preference (coded in lower case) matches one language supported by the terminal, additionaly the LT contains another language preference (coded in lower case) not supported by the terminal

•

Case 04: LT language preference (coded in upper case) matches one language supported by the terminal

•

Case 05: LT language preference (coded in upper case) matches all languages supported by the terminal (if supporting multiple languages)

•

Case 06: LT language preference (coded in upper case) matches one language supported by the terminal, additionaly the LT contains another language preference (coded in upper case) not supported by the terminal




2CN.012.00 Language Support by Terminal Pass Criteria:

•


•

The languages supported by the terminal shall be used if matched by LT in Language Preference


Page 1562


2CN.016.00 Terminal Displays Error Message if Verification Process fails Test No: 2CN.016.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the Checksum verification process fails during the

loading of the Certification Authority Public Key, the terminal shall not accept the Certification Authority Public Key. To ensure that if operator action is needed during the loading of the Certification Authority Public Key, the terminal displays an error message if the process fail. Reference Book 4 - Section 6.2 - Application Dependent Data EMV 4.0:

Book Bulletins - Section SU 38 - Bulletin n°38, Terminal Key Management Reference Book 4 - Section 10.2 - Application Dependent Data EMV 4.1:

Book Bulletins - Section SU 38 - Bulletin n°38, Terminal Key Management Terminal (((([SDA] supported OR [DDA] supported) OR [CDA] supported) OR Configuration: [Offline Enciphered PIN] supported) and [CAPK verification] supported) Conditions:

•

Certification Authority Public Key is verified with Certification Authority Public Key checksum

•

The Certification Authority Public Key checksum is not good

Action: NA Procedure: Certification Authority Public Key loading is processed Pass Criteria:

•

The Certification Authority Public Key attempting to be loaded is rejected

•

The terminal shall display an error message If an operator action is needed



Cardholder and Merchant Interface


Page 1564


2CO.001.00 Terminal Support of Local Language Test No: 2CO.001.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal supports the local language which is the

language of common usage in the terminal's locality or region Reference Book 4 - Section 7.1 - Language Selection EMV 4.0:

Book Bulletins - Section AN 12 - Bulletin n°12, Language Preference Coding (Jul-2003) Reference Book 4 - Section 11.1 - Language Selection EMV 4.1: Terminal [Display] supported Configuration: Conditions: LT has Language Preference set according to the terminal's locality or

region •

Case 01: LT language Preference is coded with lower case characters

•

Case 02: LT language Preference is coded with upper case characters


•


•

The message displayed shall be in the language of common usage in the terminal's locality or region



2CO.002.00 Terminal Display of Messages in Local Language Test No: 2CO.002.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal displays the messages to the attendant in

the language of common usage in the terminal's locality or region Reference Book 4 - Section 7.1 - Language Selection EMV 4.0: Reference Book 4 - Section 11.1 - Language Selection EMV 4.1: Terminal ([Attended] supported AND [Display] supported) Configuration: Conditions: NA Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

The message displayed for the attendant shall be in the language of common usage in the terminal's locality or region


Page 1566


2CO.003.00 Terminal Support of Relevant Character Set Test No: 2CO.003.00 - Revision 12 - Number of sub cases: 5 Objective: To ensure that the terminal displays the messages using the relevant

character set defined in the corresponding part of ISO 8859 Reference Book 4 - Section 7.1 - Language Selection EMV 4.0: Reference Book 4 - Section 11.1 - Language Selection EMV 4.1: Terminal [Display] supported AND [Issuer Code Table Index] supported Configuration:

The terminal supports at least one Issuer Code Table Index Conditions:

•

Case 01: LT has as language preference one of the language preference supported by the terminal

•

Case 02: LT has as languages preference all of the languages preference supported by the terminal (if multiple)

•

Case 03: LT has as language preference one of the language preference supported by the terminal plus a second language preference not supported by the terminal

•

Case 04: LT has Spanish as language preference

•

Case 05: LT has Chinese (Mandarin) as language preference


•


•

The languages supported by the terminal (and the LT) shall be used with relevant character set



2CO.005.00 Terminal uses language With Highest Preference Test No: 2CO.005.00 - Revision 10g - Number of sub cases: 4 Objective: To ensure that the terminal compare the card's Language Preference

with the languages supported in the terminal at the beginning of the transaction and uses the language with the highest preference in the messages displayed to the cardholder if a match is found. Reference Book 4 - Section 7.1 - Language Selection EMV 4.0: Reference Book 4 - Section 11.1 - Language Selection EMV 4.1: Terminal ([Display] supported AND [Multiple Languages] supported) Configuration: Conditions:

•

Case 01: LT has language 1 and language 2 (in order of priority) as languages preference, both supported by the terminal

•

Case 02: LT has language 1 and language 2 (in order of priority) as languages preference, only one supported by the terminal

•

Case 03: LT has language 1, language 2 and language 3 (in order of priority) as languages preference, all supported by the terminal

•

Case 04: LT has language 1, language 2 and language 3 (in order of priority) as languages preference, two are supported by the terminal


•


•

The messages for the cardholder shall be displayed in the Language with highest priority supported by both LT and Terminal


Page 1568


2CO.006.00 Terminal Allows Cardholder to Select Language Test No: 2CO.006.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that the terminal compare the card's Language Preference

with the languages supported in the terminal at the beginning of the transaction and allows the cardholder to choose if no match is found and Terminal supports several Languages Reference Book 4 - Section 7.1 - Language Selection EMV 4.0: Reference Book 4 - Section 11.1 - Language Selection EMV 4.1: Terminal ([Display] supported AND [Multiple Languages] supported) Configuration: Conditions: LT have Language Preference value with no matching language with

Terminal Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

The terminal shall allow the cardholder to choose from amongst the terminal supported languges.

•

All messages displayed to the cardholder shall be in the cardholder selected language.



2CO.008.00 Terminal Displays Message in Supported Language Test No: 2CO.008.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal uses the language it supports if no match is

found with card supported Languages and Terminal supports only one Language (Language of common usage in the region) Reference Book 4 - Section 7.1 - Language Selection EMV 4.0: Reference Book 4 - Section 11.1 - Language Selection EMV 4.1: Terminal ([Display] supported AND [Multiple Languages] not supported) Configuration: Conditions: LT have Language Preference value with no matching language with

Terminal Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

The messages for the Cardholder shall be displayed in the Terminal supported Language (Language of common usage in the region)


Page 1570


2CO.011.00 Terminal Support of Explicit Selection Test No: 2CO.011.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal supports explicit selection of application Reference Book 4 - Section 7.3 - Application Selection EMV 4.0: Reference Book 4 - Section 11.3 - Application Selection EMV 4.1: Terminal NA Configuration: Conditions:

•

LT does not have a PSE

•

Terminal and LT have at least one matching application


•


•

The LT shall receive a SELECT command for each of the terminal supported application



2CO.013.00 Terminal Creates a List of Applications Supported (1) Test No: 2CO.013.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that applications mutually supported by card and terminal

are displayed using the Application Preferred Name if the terminal supports cardholder application selection and if Application Preferred Name is present as well as the Issuer Code Table Index to be used Reference Book 4 - Section 7.3 - Application Selection EMV 4.0: Reference Book 4 - Section 11.3 - Application Selection EMV 4.1: Terminal ([Cardholder Confirmation] supported AND [Issuer Code Table Index] Configuration: supported) Conditions:

•

LT and Terminal have three mutually supported applications

•

LT applications have a priority order specified in Application Priority Indicator

•

LT applications have Application Preferred Name and Issuer Code Table Index


•


•

The terminal shall display the list of applications mutually supported using the Application preferred Name and corresponding Issuer Code Table for each Application


Page 1572


2CO.014.00 Terminal Creates a List of Applications Supported (2) Test No: 2CO.014.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that applications mutually supported by card and terminal

are displayed using the Application Label if the terminal supports cardholder application selection and if Application Preferred Name is absent Reference Book 4 - Section 7.3 - Application Selection EMV 4.0: Reference Book 4 - Section 11.3 - Application Selection EMV 4.1: Terminal [Cardholder Confirmation] supported Configuration: Conditions:

•


•


•

LT applications have not Application Preferred Name


•


•

The terminal shall display the list of applications mutually supported using the Application Label and common Issuer Table Index



2CO.015.05 Terminal Presents Application List Test No: 2CO.015.05 - Revision 10 - Number of sub cases: 0 Objective: To ensure that if the card returns SW1 SW2 other than '9000' in

response to the SELECT command, a terminal allowing cardholder selection or confirmation should display the 'Try again' message and presents to the cardholder the list of applications supported by both the ICC and the terminal without this application. Reference Book 4 - Section 7.3 - Application Selection EMV 4.0: Reference Book 4 - Section 11.3 - Application Selection EMV 4.1: Terminal [Cardholder Confirmation] supported Configuration: Conditions:

•

Terminal and LT have three mutually supported applications

•

LT returns SW1SW2 different from '90 00' in response to the Final SELECT command.


•

The terminal shall present to the cardholder the list of all applications supported by both the ICC and the terminal without this application.

•

The terminal should display the 'Try again' message.


Page 1574


2CO.016.00 Terminal Selects Application With Next Highest priority Test No: 2CO.016.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that if the terminal does not support cardholder application

selection, and if selected application returned status different from 90 00, it selects the application with second priority from the list of application mutually supported by card and terminal and not requiring cardholder confirmation Reference Book 4 - Section 7.3 - Application Selection EMV 4.0: Reference Book 4 - Section 11.3 - Application Selection EMV 4.1: Terminal [Cardholder Confirmation] not supported Configuration: Conditions:

•


•


•

Application with highest priority in the list of mutually supported applications requires Cardholder confirmation

•

LT returns status different from 9000 to the SELECT command sent to select Application with second highest priority in the list of mutually supported applications (the SELECT command sent for this application during the phase where terminal looks for mutually supported application works correctly)


•


•

After the phase where terminal looks for the applications present in the card, the LT shall receive a SELECT command for the application with second highest priority in the list of mutually supported application and LT shall return status different from 90 00

•

The LT shall receive another SELECT command for the application with third highest priority in the list of mutually



2CO.016.00 Terminal Selects Application With Next Highest priority supported application


Page 1576


2CO.017.00 Application Used Identified on Receipt Test No: 2CO.017.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal prints partial Application PAN (or the full

PAN, if allowed by payment system rules) and the AID on the receipt Reference Book 4 - Section 7.3 - Application Selection EMV 4.0: Reference Book 4 - Section 11.3 - Application Selection EMV 4.1: Terminal [Printer] supported Configuration: Conditions: NA Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

The terminal shall print a receipt with partial Application PAN (or the full PAN, if allowed by payment system rules) and the AID



2CO.018.00 Data Printed on Receipt Test No: 2CO.018.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal prints the AID in hexadecimal characters on

the receipt Reference Book 4 - Section 7.4 - Receipt EMV 4.0: Reference Book 4 - Section 11.4 - Receipt EMV 4.1: Terminal [Printer] supported Configuration: Conditions: NA Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

The terminal shall print a receipt with the AID in hexadecimal characters


Page 1578


2CO.019.00 Authorization Message Used Test No: 2CO.019.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal uses an authorization message when

transactions are batch data captured Reference Book 4 - Section 8.1 - Message Content EMV 4.0: Reference Book 4 - Section 12.1 - Message Content EMV 4.1: Terminal ([Batch Data Capture] supported AND [Online Only or Offline/Online Configuration: capable] supported) Conditions: LT parameters are set so that transaction is performed on-line Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

The terminal shall prepare and transmit an authorization request message



2CO.020.00 Financial Transaction Message Used Test No: 2CO.020.00 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the terminal uses a Financial Transaction message

when online data capture is performed by the acquirer Reference Book 4 - Section 8.1 - Message Content EMV 4.0: Reference Book 4 - Section 12.1 - Message Content EMV 4.1: Terminal ([Online Data Capture] supported AND [Online Only or Offline/Online Configuration: capable] supported) Conditions: LT parameters are set so that transaction is performed on-line Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

The terminal shall prepare and transmit a financial transaction message


Page 1580


2CO.021.00 Offline Advice message Conveyed Test No: 2CO.021.00 - Revision 13 - Number of sub cases: 0 Objective: To ensure that the terminal conveys offline advices within batch data

capture when supported. Reference Book 4 - Section 8.1 - Message Content EMV 4.0: Reference Book 4 - Section 12.1 - Message Content EMV 4.1: Terminal [Batch Data Capture] supported AND [Advice] supported Configuration: Conditions:

•

LT requests an Advice in response to First GENERATE AC with an AAC.

•

Transaction is not captured

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: Terminal shall convey offline advices.



2CO.022.00 Online Advice message transmitted Test No: 2CO.022.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the terminal transmits in real-time online advices

similary to an autorisation message or financial transaction. Reference Book 4 - Section 8.1 - Message Content EMV 4.0: Reference Book 4 - Section 12.1 - Message Content EMV 4.1: Terminal (([Online Data Capture] supported AND [Online Only or Offline/Online Configuration: capable] supported) AND [Advice] supported) Conditions:

•

LT requests an Advice in response to First GENERATE AC.

•

LT response with an AAC


•


•

The terminal shall prepare and transmit an advice in real time.


Page 1582


2CO.023.00 Reversal Used Test No: 2CO.023.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the terminal transmits reversal messages realtime Reference Book 4 - Section 8.1 - Message Content EMV 4.0: Reference Book 4 - Section 12.1 - Message Content EMV 4.1: Terminal ([Online Data Capture] supported AND [Online Only or Offline/Online Configuration: capable] supported) Conditions:

•

First GENERATE AC response from LT is ARQC

•

Issuer returns incorrect authorization responses

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall prepare and transmit a Reversal in real time.



2CO.025.00 Terminal Issues a 2nd GENERATE AC Command When Unable to Go Online (1) Test No: 2CO.025.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the terminal set Authorization Response Code to

'Unable to go online, offline accepted' and issues a second GENERATE AC indicating TC if the terminal accepts the transaction after not having been able to go online Reference Book 4 - Section 8.2.1 - Unable to Go Online EMV 4.0: Reference Book 4 - Section 12.2.1 - Unable to Go Online EMV 4.1: Terminal [Offline Only or Offline/Online capable] supported OR [Online Only Configuration: AND Normal Default Action Code processing] supported

Terminal Action Codes Default, Denial and Online have all bits set to 0b. Conditions:

•

Issuer Action Codes Denial and Online have all bits set to 0b.

•

Issuer Action Codes Default have all bits set to 0b.

•


•


•

CDOL2 requests Authorization response Code.


•


•

The LT shall receive a second GENERATE AC command requesting a TC

•

Authorization response Code shall contain to 'Unable to go online, offline accepted'


Page 1584


2CO.026.00 Terminal Issues a 2nd GENERATE AC Command When Unable to Go Online (2) Test No: 2CO.026.00 - Revision 12 - Number of sub cases: 4 Objective: To ensure that the terminal set Authorization Response Code to

'Unable to go online, offline declined and issues a second GENERATE AC indicating AAC if the terminal declines the transaction after not having been able to go online Reference Book 4 - Section 8.2.1 - Unable to Go Online EMV 4.0: Reference Book 4 - Section 12.2.1 - Unable to Go Online EMV 4.1: Terminal Configuration:

Conditions:

•

[Terminal checks the AC default prior 1st GENAC] not supported

•

Terminal Action Codes Denial and Online have all bits set to 0b.

•


•


•


•


•

Case 01: SDA in LT is wrong, Issuer Action Code Default is set to 40 00 00 00 00 [SDA supported]

•

Case 02: Transaction Amount exceed floor limit, Issuer Action Code Default is set to 00 00 00 80 00 [Terminal Risk Management, Floor Limit supported]

•

Case 03: LT application expired, Issuer Action Code Default is set to 00 40 00 00 00

•

Case 04: LOATC = 0, Issuer Action Code Default is set to 00 08 00 00 00 [Terminal Risk Management, Velocity Checking supported] LOATC = 0, Issuer Action Code Default is set to 00 08 00 00 00 [Terminal Risk Management, Velocity Checking supported]

Action: NA



2CO.026.00 Terminal Issues a 2nd GENERATE AC Command When Unable to Go Online (2) Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

The LT shall receive a second GENERATE AC command requesting an AAC

•

Authorization response Code shall contain to 'Unable to go online, offline declined'


Page 1586


2CO.028.00 Terminal Continues Processing Based on Authorization Response Code Test No: 2CO.028.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal continue the processing of the transaction

according to the Authorization Response Code if transaction is performed online. Reference Book 4 - Section 8.2.2 - Downgraded Authorisation EMV 4.0: Reference Book 4 - Section 12.2.2 - Downgraded Authorisation EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•

Case 01: Authorization Response Code is Online approved

•

Case 02: Authorization Response Code is Online declined


Authorization Response Code shall be the same as the one received from issuer Depending on Authorization Response Code received the terminal shall •

Case 01: send a second GENERATE AC requesting TC

•

Case 02: send a second GENERATE AC requesting AAC



2CO.028.01 Terminal Continues Processing Based on Authorization Response Code Test No: 2CO.028.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal continue the processing of the transaction

according to the Authorization Response Code if transaction is performed online. Reference Book 4 - Section 8.2.2 - Downgraded Authorisation EMV 4.0: Reference Book 4 - Section 12.2.2 - Downgraded Authorisation EMV 4.1: Terminal [Online Only or Offline/Online capable] supported AND [Issuer referral] Configuration: supported Conditions:

•


•


•

Authorization Response Code is Referral


Authorization Response Code shall be the same as the one received from issuer Depending on Authorization Response Code received the terminal shall display 'Call Your Bank' message.


Page 1588


2CO.030.00 Terminal Issues a 2nd GENERATE AC Command (1) Test No: 2CO.030.00 - Revision 12 - Number of sub cases: 2 Objective: To ensure that the terminal set Authorization Response Code to

'Unable to go online, offline accepted' and issues a second GENERATE AC indicating TC if the authorization response received is incorrect and if the terminal accepts the transaction. Reference Book 4 - Section 8.2.3 - Authorisation Response Incidents EMV 4.0:

Book Bulletins - Section AN 16 - Bulletin n°16, Authorisation Request Repeats (Dec-2003) Reference Book 4 - Section 12.2.3 - Authorisation Response Incidents EMV 4.1: Terminal [Offline/Online capable] supported OR [Online Only AND Normal Configuration: Default Action processing] supported

Terminal Action Codes Denial and Online have all bits set to 0b. Conditions:

•


•

Issuer Action Codes Default have all bits set to 0

•


•

CDOL2 requests Authorization response Code.

•

Case 01: No autorisation Response from the Issuer

•

Case 02: Issuer returns invalid format authorization response


•


•

Terminal may repeat the authorization request after incorrect or absent response

•


•

Authorization Response Code shall contain to 'Unable to go



2CO.030.00 Terminal Issues a 2nd GENERATE AC Command (1) online, offline accepted'


Page 1590


2CO.031.00 Terminal Issues a 2nd GENERATE AC Command (2) Test No: 2CO.031.00 - Revision 12 - Number of sub cases: 2 Objective: To ensure that the terminal set Authorization Response Code to

'Unable to go online, offline declined' and issues a second GENERATE AC indicating AAC if the authorization response received is incorrect if the terminal declines the transaction. Reference Book 4 - Section 8.2.3 - Authorisation Response Incidents EMV 4.0:

Book Bulletins - Section AN 16 - Bulletin n°16, Authorisation Request Repeats (Dec-2003) Reference Book 4 - Section 12.2.3 - Authorisation Response Incidents EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration:

Terminal Action Codes Denial and Online have all bits set to 0b. Conditions:

•


•

Issuer Action Codes Default is set to 00 40 00 00 00

•

LT application expired

•


•


•


•



•


•


•

The LT shall receive a second GENERATE AC command requesting an AAC



2CO.031.00 Terminal Issues a 2nd GENERATE AC Command (2) •

Authorization response Code shall contain to 'Unable to go online, offline declined'


Page 1592


2CO.032.00 Terminal Sends Reversal Message Test No: 2CO.032.00 - Revision 12 - Number of sub cases: 2 Objective: To ensure that the terminal sends a reversal message to the issuer if

online data capture is performed and the authorization response received is incorrect. Reference Book 4 - Section 8.2.3 - Authorisation Response Incidents EMV 4.0:

Book Bulletins - Section AN 16 - Bulletin n°16, Authorisation Request Repeats (Dec-2003) Reference Book 4 - Section 12.2.3 - Authorisation Response Incidents EMV 4.1: Terminal ([Online Data Capture] supported AND [Online Only or Offline/Online Configuration: capable] supported)

Terminal Action Codes Denial and Online have all bits set to 0b. Terminal Action Codes Default have all bits set to 1b. Conditions:

•


•


•


•

AIP of LT must be set to execute the function associated with the TAC default bit selected by the tester, and the LT will be set so the executed function will fail.

•


•



•

The terminal shall process the transaction until completion,

•

Terminal shall request an AAC at second GENERATE AC.

•




2CO.032.00 Terminal Sends Reversal Message •

The terminal shall prepare and transmit a Reversal message based on the recommended format described in Book 4 Tables 21 and 22.


Page 1594


2CO.033.00 Terminal Creates Financial Record Test No: 2CO.033.00 - Revision 16 - Number of sub cases: 2 Objective: To ensure that the terminal creates a financial record if a reversal has

been sent and transaction is finally approved. Reference Book 4 - Section 8.2.3 - Authorisation Response Incidents EMV 4.0:

Book Bulletins - Section AN 16 - Bulletin n°16, Authorisation Request Repeats (Dec-2003) Reference Book 4 - Section 12.2.3 - Authorisation Response Incidents EMV 4.1: Terminal [Online Data Capture] AND ([Offline/Online Capable] OR ([Online Only] Configuration: AND [Normal Default Action Code Processing]))

Terminal Action Codes Default, Denial and Online have all bits set to 0b. Conditions:

•

Online Data capture is performed

•


•


•


•

Case 01: No financial transaction response from the Issuer

•

Case 02: Issuer returns invalid format financial transaction response


•


•

Following the response of the first GENERATE AC, the terminal shall prepare a financial transaction request on the format described in Book 4 - Tables 10

•




2CO.033.00 Terminal Creates Financial Record •


•

Following the response of the second GENERATE AC, the terminal shall prepare a reversal message in real time based on the format described in Book 4 - Tables 21

•

Following the response of the second GENERATE AC, the terminal shall prepare a financial record to be forwarded to the acquirer.


Page 1596


2CO.034.00 Terminal Terminates Processing of Issuer Script Test No: 2CO.034.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal terminates the processing of a script if there

is a script length error or syntax error. Reference Book 4 - Section 8.2.4 - Script Incidents EMV 4.0:

Book Bulletins - Section AN 13 - Bulletin n°13, TVR and TSI Bit Settings Following Script Processing (Dec-2003) Reference Book 4 - Section 12.2.4 - Script Incidents EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•

All Scripts received have a unique Script Identifier

•

Case 01: Issuer script response contains 2 '71' scripts: a '71' script with a syntax error: 3 commands are in the script and the length of the first '86' tag is larger than the command, followed by a correct '71' script

•

Case 02: Issuer script response contains 2 '71' scripts: a '71' script with a syntax error: tag of Script id is incorrect, followed by a correct '71' script


•


•

The LT shall not receive any command of the first script

•


•

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.

•




2CO.034.00 Terminal Terminates Processing of Issuer Script received at 2nd GENERATE AC. •

Issuer Script Results shall be set to: '00 xx xx xx xx 20 yy yy yy yy', contained in Financial Confirmation message or Batch Data Capture message


Page 1598


2CO.034.01 Terminal Terminates Processing of Issuer Script (2) Test No: 2CO.034.01 - Revision 15 - Number of sub cases: 2 Objective: To ensure that the terminal terminates the processing of a script if there

is a script length error or syntax error. Reference Book 4 - Section 8.2.4 - Script Incidents EMV 4.0:

Book Bulletins - Section AN 13 - Bulletin n°13, TVR and TSI Bit Settings Following Script Processing (Dec-2003) Reference Book 4 - Section 12.2.4 - Script Incidents EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•

Case 01: Issuer script response contains 2 '72' scripts: a '72' script with a syntax error: 3 commands are in the script and the length of the first '86' tag is larger than the command, followed by a correct '72' script

•

Case 02: Issuer script response contains 2 '72' scripts: a '72' script with a syntax error: tag of Script id is incorrect, followed by a correct '72' script


•


•

The LT shall not receive any command of the first script

•

TVR byte 5 bit 6 = '0' (ie Script processing before final GENERATE AC,not used received at 2nd GENERATE AC.

•

TVR byte 5, bit 5 = '1' (ie Script processing failed after final GENERATE AC) contained in Financial Confirmation message or Batch Data Capture message.

•




2CO.034.01 Terminal Terminates Processing of Issuer Script (2) Capture message •

Issuer Script Results shall be set to: '00 xx xx xx xx 20 yy yy yy yy', contained in Financial Confirmation message or Batch Data Capture message


Page 1600


2CO.034.02 Terminal Terminates Processing of Issuer Script exceeding device limit (1) Test No: 2CO.034.02 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal terminates the processing of an issuer

script when exceeding the device limit. Reference Book 4 - Section 8.2.4 - Script Incidents EMV 4.0:

Book Bulletins - Section AN 13 - Bulletin n°13, TVR and TSI Bit Settings Following Script Processing (Dec-2003) Reference Book 4, Section 6.3.9 - Issuer-to-Card Script Processing EMV 4.1:

Book 4, Section 12.2.4 - Script Incidents Terminal [Online Only or Offline/Online capable] supported AND [Issuer Script Configuration: device limit => 128 bytes] supported Conditions:

•


•

All Scripts received have a unique Script Identifier

•

Issuer sends two type '71' issuer scripts where the sum length exceeds the device limit (typically 128 bytes). The first issuer script is one hundred bytes in length, the second is at least twenty-nine bytes in length or large enough to exceed the device limit.

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: • The terminal shall process the transaction until completion

• The terminal shall process the first issuer script and terminate the second •

TVR byte 5, bit 6 = '1' (i.e. Script processing failed before final GENERATE AC), received at 2nd GENERATE AC

•

TVR byte 5, bit 5 = '0' (i.e. No script processing after final GENERATE AC), contained in Financial Confirmation message or Batch Data Capture message

•

TSI byte 1, bit 3 = '1' (i.e. Script processing was performed),



2CO.034.02 Terminal Terminates Processing of Issuer Script exceeding device limit (1) received at 2nd GENERATE AC •

Issuer Script Results = 20 yy yy yy yy 00 xx xx xx xx (in financial transaction confirmation or batch data capture)


Page 1602


2CO.034.03 Terminal Terminates Processing of Issuer Script exceeding device limit (2) Test No: 2CO.034.03 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the terminal terminates the processing of an issuer

script when exceeding the device limit. Reference Book 4 - Section 8.2.4 - Script Incidents EMV 4.0:

Book Bulletins - Section AN 13 - Bulletin n°13, TVR and TSI Bit Settings Following Script Processing (Dec-2003) Reference Book 4, Section 6.3.9 - Issuer-to-Card Script Processing EMV 4.1:

Book 4, Section 12.2.4 - Script Incidents Terminal [Online Only or Offline/Online capable] supported AND [Issuer Script Configuration: device limit => 128 bytes] supported Conditions: • LT parameters are set so that transaction is performed on-line

• All Scripts received have a unique Script Identifier •

Issuer sends two type '72' issuer scripts where the sum length exceeds the device limit (typically 128 bytes). The first issuer script is one hundred bytes in length, the second is at least twenty-nine bytes in length or large enough to exceed the device limit.

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: • The terminal shall process the transaction until completion

• The terminal shall process the first issuer script and terminate the second •

TVR byte 5, bit 6 = '0' (i.e. No script processing before final GENERATE AC), contained in Financial Confirmation message or Batch Data Capture message

•

TVR byte 5, bit 5 = '1' (i.e. Script processing failed after final GENERATE AC ), contained in Financial Confirmation message or Batch Data Capture message



2CO.034.03 Terminal Terminates Processing of Issuer Script exceeding device limit (2) •

TSI byte 1, bit 3 = '1' (i.e. Script processing was performed), contained in Financial Confirmation message or Batch Data Capture message

•

Issuer Script Results = 20 yy yy yy yy 00 xx xx xx xx (in financial transaction confirmation or batch data capture)


Page 1604


2CO.035.00 Terminal Reports in Issuer Script results Test No: 2CO.035.00 - Revision 16 - Number of sub cases: 2 Objective: To ensure that the terminal terminates the processing if Issuer Script

does not parse correctly and reports scripts error in Issuer Script Results Reference Book 1 - Section 6 - Files EMV 4.0:

Book 4 - Section 8.2.4 - Script Incidents Book Bulletins - Section AN 13 - Bulletin n°13, TVR and TSI Bit Settings Following Script Processing (Dec-2003) Reference Book 1 - Section 10 - Files EMV 4.1:

Book 4 - Section 12.2.4 - Script Incidents Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•

Case 01: Issuer sends '71' script with a readable Script Identifier (’44 33 22 11’) and with a syntax error: 3 commands are in the script and the length of the first '86' tag is larger than the command

•

Case 02: Issuer sends '71' script with a readable Script Identifier (’44 33 22 11’) and with a syntax error: tag of Script id is incorrect


•


•

The terminal shall terminate the bad parsed Issuer script processing and continue subsequent Scripts if readable

•

Case 01: Issuer Script Result (contained in Financial Confirmation message or Batch Data Capture message) set to '00 44 33 22 11', script not performed for the failed script.

•

Case 02: Issuer Script Result (contained in Financial



2CO.035.00 Terminal Reports in Issuer Script results Confirmation message or Batch Data Capture message) set to '00 00 00 00 00’. •

TVR byte 5 bit 6 = '1' (ie Script processing failed before final GENERATE AC, not used) 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) contained in Financial Confirmation message or Batch Data Capture message.


Page 1606


2CO.035.01 Terminal Reports in Issuer Script results (2) Test No: 2CO.035.01 - Revision 16 - Number of sub cases: 2 Objective: To ensure that the terminal terminates the processing if Issuer Script




•


•

Case 01: Issuer sends '72' script with a readable Script Identifier (’44 33 22 11’) and with a syntax error: 3 commands are in the script and the length of the first '86' tag is larger than the command

•

Case 02: Issuer sends '72' script with a readable Script Identifier (’44 33 22 11’) and with a syntax error: tag of Script id is incorrect


•


•

The terminal shall terminate the bad parsed Issuer script processing and continue subsequent Scripts if readable

•

Case 01: Issuer Script Result (contained in Financial Confirmation message or Batch Data Capture message) set to '00 44 33 22 11', script not performed for the failed script.

•

Case 02: Issuer Script Result (contained in Financial



2CO.035.01 Terminal Reports in Issuer Script results (2) Confirmation message or Batch Data Capture message) set to '00 00 00 00 00', script not performed for the failed script. •

TVR byte 5 bit 6 = '0' (ie Script processing failed before final GENERATE AC), not used received at 2nd GENERATE AC.

•

TVR byte 5, bit 5 = '1' (ie Script processing failed after final GENERATE AC) contained in Financial Confirmation message or Batch Data Capture message.

•

TSI byte 1, bit 3 = '1' (ie Script processing was performed), if present in Financial Confirmation message or Batch Data Capture message


Page 1608


2CO.035.02 Terminal Reports in Issuer Script results (3) Test No: 2CO.035.02 - Revision 15 - Number of sub cases: 4 Objective: To ensure that the terminal terminates the processing if Issuer Script




•


•

Case 01: Issuer sends back a '71' script and a '72' scripts, all with readable Script Identifier: script '71' has a syntax error and script '72' is good

•

Case 02: Issuer sends back a '71' script and a '72' scripts all with readable Script Identifier: script '71' is good and script '72' has a syntax error

•

Case 03: Issuer sends back two '71' scripts and a '72' scripts all with readable Script Identifier: first script '71' is good, second script '71' has a syntax error and script '72' is good

•

Case 04: Issuer sends back two '71' scripts and two '72' scripts all with readable Script Identifier: first script '71' is good, second script '71' has a syntax error, first script '72' is good and second script '72' has a syntax error


•




2CO.035.02 Terminal Reports in Issuer Script results (3) •

The terminal shall terminate the bad parsed Issuer scripts processing and continue subsequent Scripts if readable

•

Issuer Script Results of each bad scripts (contained in Financial Confirmation message or Batch Data Capture message) set to '00', script not performed for the failed scripts.

•

TVR byte 5, bit 5 and bit 6 set to the correct value according to each subcases

•



Page 1610


2CO.036.00 Terminal Continues Processing any Subsequent Issuer Script Test No: 2CO.036.00 - Revision 11 - Number of sub cases: 3 Objective: To ensure that the terminal continues processing of any subsequent

script if the script currently processed has a syntax error. Reference Book 4 - Section 8.2.4 - Script Incidents EMV 4.0: Reference Book 4 - Section 12.2.4 - Script Incidents EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•

Case 01: Issuer sends back 2 '71' scripts: script 1 has a syntax error and script 2 is good

•

Case 02: Issuer sends back 3 '71' scripts: script 3 has a syntax error and script 1 and 2 are good

•

Case 03: Issuer sends back 2 '71' scripts: script 1 is good and script 2 has a syntax error


•


•

The LT shall receive command from the correct scripts only



2CO.036.01 Terminal Continues Processing any Subsequent Issuer Script (2) Test No: 2CO.036.01 - Revision 11 - Number of sub cases: 3 Objective: To ensure that the terminal continues processing of any subsequent


•


•

Case 01: Issuer sends back 2 '72' scripts: script 1 has a syntax error and script 2 is good

•

Case 02: Issuer sends back 3 '72' scripts: script 3 has a syntax error and script 1 and 2 are good

•

Case 03: Issuer sends back 2 '72' scripts: script 1 is good and script 2 has a syntax error


•


•



Page 1612


2CO.036.02 Terminal Continues Processing any Subsequent Issuer Script (2) Test No: 2CO.036.02 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the terminal continues processing of any subsequent


•


•

Case 01: Issuer sends back a '71' script and a '72' scripts: script '71' has a syntax error and script '72' is good

•

Case 02: Issuer sends back a '71' script and a '72' scripts: script '71' is good and script '72' has a syntax error

•

Case 03: Issuer sends back two '71' scripts and a '72' scripts: first script '71' is good, second script '71' has a syntax error and script '72' is good


•


•




2CO.037.00 All data in the Messages are originated from chip Test No: 2CO.037.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that terminal does not use magstripe data to populate an

authorisation message or financial transaction message when a data is present in magstripe and not in ICC. Reference Book 4 - Section 8.1 – Message Content EMV 4.0:

Bulletins - Section AN 28 - Bulletin n°28, Data Source for ChipOriginated Messages (July-2005) Reference Book 4 - Section 12.1 – Message Content EMV 4.1:

Bulletins - Section AN 28 - Bulletin n°28, Data Source for ChipOriginated Messages (July-2005) Terminal ([Combined IC and Magnetic stripe reader] supported AND [Magnetic Configuration: stripe first] supported) Conditions: A data is present in magstripe and not in ICC: LT does not contain

Track 2 Equivalent Data tag '57' and does not contain Service Code tag '5F 30'. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The authorization message, financial transaction message, or batch file

shall not contain the magnetic stripe data (Service Code ' 5F 30')


Page 1614


2CO.038.00 All data in the Messages are originated from chip (2) Test No: 2CO.038.00 - Revision 15 - Number of sub cases: 0 Objective: To ensure that terminal does not use magstripe data to populate an

authorisation message or financial transaction message when a data is present in magstripe and not in ICC. Reference Book 4 - Section 8.1 – Message Content EMV 4.0:

Bulletins - Section AN 28 - Bulletin n°28, Data Source for ChipOriginated Messages (July-2005) Reference Book 4 - Section 12.1 – Message Content EMV 4.1:

Bulletins - Section AN 28 - Bulletin n°28, Data Source for ChipOriginated Messages (July-2005) Terminal ([Combined IC and Magnetic stripe reader] supported AND [Magnetic Configuration: stripe first] supported) Conditions: A data has a different value in magstripe and in ICC: Track 2

Equivalent Data – ‘57’ Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The authorisation message or financial transaction message shall

contain the LT (ICC) data. For offline only terminals, the value will be checked in batch file.



Coding of Terminal Data Element


Page 1616


2CP.001.00 Terminal Type Test No: 2CP.001.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that the terminal has Terminal Type coded according to its

effective type. Reference Book 4 - Section Annex A - Coding of Terminal Data Elements EMV 4.0: Reference Book 4 - Section Annex A - Coding of Terminal Data Elements EMV 4.1: Terminal NA Configuration: Conditions: CDOL1 requests Terminal Type and Terminal Capabilities Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: Terminal capabilities shall be coded according to the terminal

supported features indicated below: * Attended Terminal - x1 or x2 or x3 * Unattended Terminal - x4 or x5 or x6 * Terminal operated by Financial Institutions - 1x * Terminal operated by Merchant - 2x * Terminal operated by Cardholder - 3x * Online only - x1 or x4 * Offline with online capabilities - x2 or x5 * Offline only - x3 or x6



2CP.002.00 Terminal Capabilities Test No: 2CP.002.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that the terminal has Terminal capabilities coded according

to its effective Capabilities Reference Book 4 - Section Annex A - Coding of Terminal Data Elements EMV 4.0:

Book Bulletins - Section SU 9 - Bulletin n°9, Modification to Combined Dynamic Data Authentication (Mar-2002) Book Bulletins - Section SU 10 - Bulletin n°10, Addition of flag to indicate support of No CVM Required cardholder verification method (Mar-2002) Reference Book 4 - Section Annex A - Coding of Terminal Data Elements EMV 4.1: Terminal NA Configuration: Conditions: CDOL1 requests Terminal Capabilities Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: Terminal capabilities shall be coded according to the terminal

supported features indicated below: * Manual Key entry - byte 1, b8 = 1 * Magnetic stripe - byte 1, b7 = 1 * IC with contacts - byte 1, b6 = 1 * Plaintext PIN verified by ICC - byte 2, b8 = 1 * Enciphered PIN online - byte 2, b7 = 1 * Signature - byte 2, b6 = 1 * Offline Enciphered PIN verified by ICC - byte 2, b5 = 1 * No CVM required - byte 2, b4 = 1 * Static Data Authentication - byte 3, b8 = 1 * Dynamic Data Authentication - byte 3, b7 = 1 Copyright ©2008 EMVCo, LLC. All rights reserved

Page 1618


2CP.002.00 Terminal Capabilities * Card capture - byte 3, b6 = 1 * Combined DDA/AC Data Authentication - Byte 3, b4 = 1



2CP.003.00 Additional Terminal Capabilities Test No: 2CP.003.00 - Revision 10 - Number of sub cases: 0 Objective: To ensure that the terminal has Additional Terminal capabilities coded

according to its effective Capabilities Reference Book 4 - Section Annex A - Coding of Terminal Data Elements EMV 4.0:

Book Bulletins - Section SU 17 - Bulletin n°17, Additional Terminal Capabilities - Cash Deposit Transaction Type (Dec-2003) Reference Book 4 - Section Annex A - Coding of Terminal Data Elements EMV 4.1: Terminal NA Configuration: Conditions: CDOL1 requests Additional Terminal Capabilities Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: Transaction Type Capabilities shall be coded according to the terminal

supported features indicated below: * Cash deposit - byte 2, b8 = 1 * Cash - byte 1, b8 = 1 * Goods - byte 1, b7 = 1 * Services - byte 1, b6 = 1 * Cashback - byte 1, b5 = 1 * Inquiry - byte 1, b4 = 1 * Transfer - byte 1, b3 = 1 * Payment - byte 1, b2 = 1 * Administrative - byte 1, b1 = 1 * Numeric Keys - byte 3, b8 = 1 * Alphabetical and special characters keys - byte 3, b7 = 1 * Command Keys - byte 3, b6 = 1 Copyright ©2008 EMVCo, LLC. All rights reserved

Page 1620


2CP.003.00 Additional Terminal Capabilities * Function Keys - byte 3, b5 = 1 * Print, attendant - byte 4, b8 = 1 * Print, cardholder - byte 4, b7 = 1 * Display, attendant - byte 4, b6 = 1 * Display, cardholder - byte 4, b5 = 1 * Code table 10 - byte 4, b2 = 1 * Code table 9: - byte 4, b1 = 1 * Code table 8: - byte 5, b8 = 1 * Code table 7: - byte 5, b7 = 1 * Code table 6 - byte 5, b6 = 1 * Code table 5: - byte 5, b5 = 1 * Code table 4: - byte 5, b4 = 1 * Code table 3: - byte 5, b3 = 1 * Code table 2: - byte 5, b2 = 1 * Code table 1: - byte 5, b1 = 1



2CP.004.00 Account Type Test No: 2CP.004.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the terminal stores the account type value in dedicated

tag when a specific account type I selected Reference Book Bulletins - Section SU 39 - Bulletin n°39, Definition of the new EMV 4.0: data element ‘Account Type’ Reference Book Bulletins - Section SU 39 - Bulletin n°39, Definition of the new EMV 4.1: data element ‘Account Type’ Terminal [Account Type] supported Configuration: Conditions: PDOL requests Accoutn Type (tag ‘5F 57’) Action: A specific account is selected Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall send in the PDOL the value of the account type

according to one selected


Page 1622


Command Syntax



2CS.001.00 Mandatory Command Set Test No: 2CS.001.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that all terminals issue the basic mandatory commands in

the correct format and issues them at the expected times during the transaction flow. Reference Book 1 - Section 7.2.2 - Command Message EMV 4.0:

Book 1 - Section 7.2.3 - Data Field Sent in the Command Message Book 1 - Section 7.3.2 - Command Message Book 3 - Section 2.5.5.2 - Command Message Book 3 - Section 2.5.5.3 - Data Field Sent in the Command Message Book 3 - Section 2.5.8.2 - Command Message Book 3 - Section 2.5.11.2 - Command Message Book 3 - Section 2.5.11.3 - Data Field Sent in the Command Message Reference Book 1 - Section 11.2.2 - Command Message EMV 4.1:

Book 1 - Section 11.2.3 - Data Field Sent in the Command Message Book 1 - Section 11.3.2 - Command Message Book 3 - Section 6.5.5.2 - Command Message Book 3 - Section 6.5.5.3 - Data Field Sent in the Command Message Book 3 - Section 6.5.8.2 - Command Message Book 3 - Section 6.5.11.2 - Command Message Book 3 - Section 6.5.11.3 - Data Field Sent in the Command Message Terminal NA Configuration: Conditions:

•

LT contains AIP value '00 00' - Card does not support additional functionality

•

LT contains the following mandatory Data Objects (Application Expiration Date, Application PAN, CDOL1, and CDOL2)

•

Case 01: LT requests a transaction using t=0 protocol


Page 1624


2CS.001.00 Mandatory Command Set •


Action: NA Procedure: The terminal will perform the following functions as a part of the basic

EMV transaction: - Application Selection. - Initiate Application Processing. - Read Application Data. - Terminal Action Analysis. - Completion. Pass Criteria:

•

Terminal shall process the card to transaction completion for both protocols.

•

Terminal shall be consistent with the command formats.

•

Terminal shall issue all mandatory commands as specified below.

•

Each command shall contain the correct syntax and be issued at the appropriate time. (Follow command flow and syntax below)

- Select: Mandatory Command 00 A4 04 00 Lc Command Data Le Lc = 05 - 10 (Length of Command Data) Command Data = File Name Le = (Not Present T=0) - Get Processing Options: Mandatory Command 80 A8 00 00 Lc Command Data Le Lc = variable (Length of Command Data)



2CS.001.00 Mandatory Command Set Command Data = (Processing Options Data Object List - PDOL) Le = (Not Present T=0) - Read Record: Mandatory Command 00 B2 P1 P2 00 P1 = Record Number P2= Reference control parameter - Short File Indicator (SFI) Multiple Read Record commands will be issued dependent on AFL - GENERATE AC.: Mandatory Command 80 AE P1 00 Lc Command Data Le P1 = Reference Control Parameter (00 - AAC, 40 - TC, 80 - ARQC) Le = 00 (Not Present T=0)


Page 1626


2CS.002.00 Select Next Command Test No: 2CS.002.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure the terminal issues the Select Next command in the correct

format and issued at the expected times during the transaction flow. Reference Book 1 - Section 7.3.2 - Command Message EMV 4.0: Reference Book 1 - Section 11.3.2 - Command Message EMV 4.1: Terminal NA Configuration: Conditions:

•

LT contains DF name longer than the terminal stored AID

•

LT contains AIP value '00 00' - Card does not support additional functionality

•


•


•



EMV transaction: - Application Selection. - Initiate Application Processing. - Read Application Data. - Terminal Action Analysis. - Completion. Pass Criteria:

•


•




2CS.002.00 Select Next Command •


•

Terminal shall issue Select next command in response to receiving a Df name longer than the AID stored in the terminal.

Each command shall contain the correct syntax and be issued at the appropriate time. (Follow command flow and syntax below) - Select: Mandatory Command 00 A4 04 00 Lc Command Data Le Lc = 05 - 10 (Length of Command Data) Command Data = File Name Le = (Not Present T=0) - Select Next: Mandatory Command 00 A4 04 02 Lc Command Data Le Lc = 05 - 10 (Length of Command Data) Command Data = File Name Le = (Not Present T=0) - Get Processing Options: Mandatory Command 80 A8 00 00 Lc Command Data Le Lc = variable (Length of Command Data) Command Data = (Processing Options Data Object List - PDOL) Le = (Not Present T=0) - Read Record: Mandatory Command 00 B2 P1 P2 00 P1 = Record Number P2= Reference control parameter - Short File Indicator (SFI) Multiple Read Record commands will be issued dependent on Copyright ©2008 EMVCo, LLC. All rights reserved

Page 1628


2CS.002.00 Select Next Command Application File Locators. - GENERATE AC.: Mandatory Command 80 AE P1 00 Lc Command Data Le P1 = Reference Control Parameter (00 - AAC, 40 - TC, 80 - ARQC) Le = 00 (Not Present T=0)



2CS.003.00 Internal Authenticate Command Test No: 2CS.003.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that if the terminal supports Dynamic Data Authentication,

the internal authenticate command is properly issued. Reference Book 3 - Section 2.5.9.2 - Command Message EMV 4.0:


Book 3 - Section 6.5.9.3 - Data Field Sent in the Command Message Terminal [DDA] supported Configuration: Conditions:

•

LT contains AIP value '20 00' - Offline DDA is supported

•


•

LT contains required Data Objects to support DDA

•


•



EMV transaction: - Application Selection. - Initiate Application Processing. - Read Application Data. - Data Authentication. - Terminal Action Analysis. - Completion. Pass Criteria:

•



Page 1630


2CS.003.00 Internal Authenticate Command •


•


•

Terminal shall issue Internal Authenticate command after Read Application Data but prior to 1st Gen AC command

•


- Select: Mandatory Command 00 A4 04 00 Lc Command Data Le Lc = 05 - 10 (Length of Command Data) Command Data = File Name Le = (Not Present T=0) - Get Processing Options: Mandatory Command 80 A8 00 00 Lc Command Data Le Lc = variable (Length of Command Data) Command Data = (Processing Options Data Object List - PDOL) Le = (Not Present T=0) - Read Record: Mandatory Command 00 B2 P1 P2 00 P1 = Record Number P2= Reference control parameter - Short File Indicator (SFI) Multiple Read Record commands will be issued dependent on Application File Locators. - Internal Authenticate: Mandatory if terminal supports Dynamic Data Authentication Copyright © 2008 EMVCo, LLC. All Rights Reserved. Page 1631


2CS.003.00 Internal Authenticate Command 00 88 00 00 Lc Command Data Le Lc = (Length of Command Data) Command Data = Length of authentication-related data Le = 00 (Not Present for T=0) - GENERATE AC.: Mandatory Command 80 AE P1 00 Lc Command Data Le P1 = Reference Control Parameter (00 - AAC, 40 - TC, 80 - ARQC) Le = 00 (Not Present T=0)


Page 1632


2CS.004.00 Verify Command Test No: 2CS.004.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that terminal supporting Cardholder verification form,

Plaintext PIN verified by ICC, issues the Verify Command in the correct format and is issued at the expected time during the transaction flow. If the terminal supports Get Data for PIN try counter, the Get Data command will be issued prior to the Verify command. Reference Book 3 - Section 2.5.12.2 - Command Message EMV 4.0: Reference Book 3 - Section 6.5.12.2 - Command Message EMV 4.1: Terminal [Offline Plaintext PIN] supported Configuration: Conditions:

•

LT contains AIP value '10 00' - Cardholder verification is supported

•


•

LT contains CVM list, tag '8E' contains CVR plain text PIN verified by ICC, always (01 00)

•


•



EMV transaction: - Application Selection. - Initiate Application Processing. - Read Application Data. - Cardholder Verification. - Terminal Action Analysis. - Completion. Copyright © 2008 EMVCo, LLC. All Rights Reserved. Page 1633


2CS.004.00 Verify Command Pass Criteria:

•


•


•


•

If terminal supports Get Data for PIN try counter, it shall be issued prior to the Verify Command.

•

Terminal shall issue Verify Command after Read Application Data but prior to 1st GEN AC.

•


- Select: Mandatory Command 00 A4 04 00 Lc Command Data Le Lc = 05 - 10 (Length of Command Data) Command Data = File Name Le = (Not Present T=0) - Get Processing Options: Mandatory Command 80 A8 00 00 Lc Command Data Le Lc = variable (Length of Command Data) Command Data = (Processing Options Data Object List - PDOL) Le = (Not Present T=0) - Read Record: Mandatory Command 00 B2 P1 P2 00 P1 = Record Number P2= Reference control parameter - Short File Indicator (SFI) Multiple Read Record commands will be issued dependent on Copyright ©2008 EMVCo, LLC. All rights reserved

Page 1634


2CS.004.00 Verify Command Application File Locators. - Get Data For PIN Try Counter: If Terminal Supports 80 CA 9F 17 00 Lc = Not Present Command Data = Not Present - Verify Command 00 20 00 P2 Lc Command Data Le P2 = Qualifier (80 - plaintext) Command Data (Transaction PIN Data) Le = (Not Present) - GENERATE AC.: Mandatory Command 80 AE P1 00 Lc Command Data Le P1 = Reference Control Parameter (00 - AAC, 40 - TC, 80 - ARQC) Le = 00 (Not Present T=0)



2CS.005.00 Get Challenge command Test No: 2CS.005.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure to the terminal issues the Get Challenge and Verify

command in the correct format and issues them at the expected times during the transaction flow if the terminal supports Cardholder verification form, Enciphered PIN verified by ICC. If the terminal supports Get Data command for PIN Try counter, it shall be issued prior to the Verify command. Reference Book 3 - Section 2.5.6.2 - Command Message EMV 4.0:

Book 3 - Section 2.5.6.3 - Data Field Sent in the Command Message Book 3 - Section 2.5.12.2 - Command Message Reference Book 3 - Section 6.5.6.2 - Command Message EMV 4.1:

Book 3 - Section 6.5.6.3 - Data Field Sent in the Command Message Book 3 - Section 6.5.12.2 - Command Message Terminal [Offline Enciphered PIN] supported Configuration: Conditions:

•

LT contains AIP value '10 00' - Cardholder verification is supported

•


CVM list tag '8E' contains CVR Enciphered PIN verified by ICC always (04 00) •

LT contains all mandatory data objects to support Enciphered PIN

•


•



EMV transaction: - Application Selection.


Page 1636


2CS.005.00 Get Challenge command - Initiate Application Processing. - Read Application Data. - Cardholder Verification. - Terminal Action Analysis. - Completion. Pass Criteria:

•


•


•


•

If the Terminal supports Get Data for PIN Try Counter, it will be issued prior to the Verify command.

•

Terminal shall issue Get Challenge command after Read Application Data but prior to Verify command

•


- Select: Mandatory Command 00 A4 04 00 Lc Command Data Le Lc = 05 - 10 (Length of Command Data) Command Data = File Name Le = (Not Present T=0) - Get Processing Options: Mandatory Command 80 A8 00 00 Lc Command Data Le Lc = variable (Length of Command Data) Command Data = (Processing Options Data Object List - PDOL) Copyright © 2008 EMVCo, LLC. All Rights Reserved. Page 1637


2CS.005.00 Get Challenge command Le = (Not Present T=0) - Read Record: Mandatory Command 00 B2 P1 P2 00 P1 = Record Number P2= Reference control parameter - Short File Indicator (SFI) Multiple Read Record commands will be issued dependent on Application File Locators. - Get Data For PIN Try Counter: If Terminal Supports 80 CA 9F 17 00 Lc = Not Present Command Data = Not Present - Get Challenge: Mandatory Command if terminal supports Enciphered PIN 00 84 00 00 Lc Command Data Le Lc = Not Present Command Data = Not Present Le = 00 - Verify: Mandatory Command if terminal supports Enciphered PIN 00 20 00 P2 Lc Command Data Le P2 = Qualifier (88 - enciphered) Command Data (Transaction PIN Data) Le = (Not Present) - GENERATE AC.: Mandatory Command 80 AE P1 00 Lc Command Data Le P1 = Reference Control Parameter (00 - AAC, 40 - TC, 80 - ARQC)


Page 1638


2CS.005.00 Get Challenge command Le = 00 (Not Present T=0)



2CS.006.00 Get Data command Test No: 2CS.006.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that if the terminal supports Velocity Checking as a part of

Terminal Risk Management, the terminal shall issue the Get Data command in the correct format and is issued at the expected times during the transaction flow. Reference Book 3 - Section 2.5.7.2 - Command Message EMV 4.0:


Book 3 - Section 6.5.7.3 - Data Field Sent in the Command Message Terminal [Velocity Checking] supported Configuration: Conditions:

•

AIP of LT indicates TRM to be performed

•


•

LT contains Upper and Lower Consecutive Off-line Limits

•


•



EMV transaction: - Application Selection. - Initiate Application Processing. - Read Application Data. - Terminal Risk Management. - Terminal Action Analysis. - completion. Pass Criteria:

•

Terminal shall process the card to transaction completion for


Page 1640


2CS.006.00 Get Data command both protocols. •


•


•

Terminal shall issue Get Data Commands for Application Transaction Counter and Last On-line Application Transaction Counter after Read Application Data but prior to 1st GEN AC.

•


- Select: Mandatory Command 00 A4 04 00 Lc Command Data Le Lc = 05 - 10 (Length of Command Data) Command Data = File Name Le = (Not Present T=0) - Get Processing Options: Mandatory Command 80 A8 00 00 Lc Command Data Le Lc = variable (Length of Command Data) Command Data = (Processing Options Data Object List - PDOL) Le = (Not Present T=0) - Read Record: Mandatory Command 00 B2 P1 P2 00 P1 = Record Number P2= Reference control parameter - Short File Indicator (SFI) Multiple Read Record commands will be issued dependent on Application File Locators.



2CS.006.00 Get Data command - Get Data For ATC: Mandatory Command 80 CA 9F 36 00 Lc = Not Present Command Data = Not Present - Get Data For Last Online ATC: Mandatory Command 80 CA 9F 13 00 Lc = Not Present Command Data = Not Present - GENERATE AC.: Mandatory Command 80 AE P1 00 Lc Command Data Le P1 = Reference Control Parameter (00 - AAC, 40 - TC, 80 - ARQC) Le = 00 (Not Present T=0)


Page 1642


2CS.007.00 External Authenticate command Test No: 2CS.007.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that a terminal with online capability can issue the External

Authenticate command after the first GENERATE AC but prior to second GENERATE AC. The command is in the correct format and issued at the expected times during the transaction flow. Reference Book 3 - Section 2.5.4.2 - Command Message EMV 4.0:


Book 3 - Section 6.5.4.3 - Data Field Sent in the Command Message Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•

LT contains AIP value '04 00' - Issuer authentication is supported

•


•

1st GEN AC - ARQC

•

Issuer authentication data- returned in response to host

•


•



EMV transaction: - Application Selection. - Initiate Application Processing. - Read Application Data. - Terminal Action Analysis.



2CS.007.00 External Authenticate command - Online Processing. - Issuer Authentication. - completion. Pass Criteria:

•


•


•


•

Terminal shall issue External Authenticate command after the First GENERATE AC command, but prior to the Second GENERATE AC command.

•


- Select: Mandatory Command 00 A4 04 00 Lc Command Data Le Lc = 05 - 10 (Length of Command Data) Command Data = File Name Le = (Not Present T=0) - Get Processing Options: Mandatory Command 80 A8 00 00 Lc Command Data Le Lc = variable (Length of Command Data) Command Data = (Processing Options Data Object List - PDOL) Le = (Not Present T=0) - Read Record: Mandatory Command 00 B2 P1 P2 00 P1 = Record Number Copyright ©2008 EMVCo, LLC. All rights reserved

Page 1644


2CS.007.00 External Authenticate command P2= Reference control parameter - Short File Indicator (SFI) Multiple Read Record commands will be issued dependent on Application File Locators. - First GENERATE AC.: Mandatory Command 80 AE P1 00 Lc Command Data Le P1 = Reference Control Parameter (00 - AAC, 40 - TC, 80 - ARQC) Note: For this test P1 = 80. Le = 00 (Not Present T=0) - External Authenticate: Mandatory Command 00 82 00 00 Lc Command Data Le Lc = 8 - 16 (Length of Command Data) Command Data = Issuer Authentication Data Le = Not Present - Second GENERATE AC.: Mandatory Command 80 AE P1 00 Lc Command Data Le P1 = Reference Control Parameter (00 - AAC, 40 - TC, 80 - ARQC) Le = 00 (Not Present T=0)



2CS.014.00 Combined functions on Transaction Flow: Offline PIN and Advice with PIN Try Limit exceeded Test No: 2CS.014.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the Terminal is able to perform the transaction when

advice 'PIN Try Limit exceeded' to the issuer is requested and PIN offline verification failed Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal ([Advice] supported AND [Offline Plaintext PIN] supported) Configuration: Conditions:

•


•

CVM requires 'Plaintext PIN verification Offline' (01 00)

•

LT answers to the GENERATE AC with the bit 2 and 4 of its Cryptogram Information Data (CID) sets to '1'

•

LT answers on GENERATE AC is AAC


•

The terminal shall process the transaction until completion and is declined.

•

The terminal shall send an advice message only if it does not store in batch file declined transactions.

•

TVR byte 3, bit 8 = '1'(ie Cardholder verification failed) received at 1st GENERATE AC.

•



Page 1646


2CS.014.01 Combined functions on Transaction Flow: Offline PIN and Advice with PIN Try Limit exceeded (2) Test No: 2CS.014.01 - Revision 10 - Number of sub cases: 0 Objective: To ensure that the Terminal is able to perform the transaction when

advice 'PIN Try Limit exceeded' to the issuer is requested and PIN offline verification was correct Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal ([Advice] supported AND [Offline Plaintext PIN] supported) Configuration: Conditions:

•


•

CVM requires 'Plaintext PIN verification Offline' (01 00)

•

PIN verification occurs correctly in LT

•


•

LT answers on GENERATE AC is TC


•

The terminal shall process the transaction until completion and is approved.

•


•





advice 'PIN Try Limit exceeded' to the issuer is requested and PIN offline verification failed Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal ([Advice] supported AND [Offline Enciphered PIN] supported) Configuration: Conditions:

•


•

CVM requires Enciphered PIN verification Offline, always' (04 00)

•


•

LT answers on GENERATE AC is AAC


•


•

The terminal shall send an advice message only if it does not store in batch file declined transactions.

•

TVR byte 3, bit 8 = '1'(ie Cardholder verification failed) received at 1st GENERATE AC.

•



Page 1648



advice 'PIN Try Limit exceeded' to the issuer is requested and PIN offline verification was correct Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal ([Advice] supported AND [Offline Enciphered PIN] supported) Configuration: Conditions:

•


•

CVM requires Enciphered PIN verification Offline, always' (04 00)

•

PIN verification occurs correctly in LT

•


•

LT answers on GENERATE AC is TC


•

The terminal shall process the transaction until completion and is approved.

•


•




2CS.015.00 Combined functions on Transaction Flow: SDA and Record length coded on 1 or 2 bytes Test No: 2CS.015.00 - Revision 10g - Number of sub cases: 4 Objective: To ensure that the terminal supports Static Data Authentication and the

records involved in the SDA calculation are coded on 1 or 2 bytes Reference Book 3 - Section 4 - Transaction Flow EMV 4.0:

Book Bulletins - Section SU 8-02 - Bulletin n°8, Editorial Changes for EMV 2000 Version 1.0 (Dec-2002) Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [SDA] supported Configuration:


•


•

Signed Static Application Data is good in LT

•

Case 01: Record length listed in the AFL as participating in data authentication is coded on 1 byte (b8 = 0)

•

Case 02: Record length listed in the AFL as participating in data authentication is coded on 2 bytes (81 xx)

•

Case 03: The length of a Data Object participating in data authentication is coded on 1 byte (b8 = 0)

•

Case 04: The length of a Data Object participating in data authentication is coded on 2 bytes (81 xx)


•


•


•



Page 1650


2CS.015.00 Combined functions on Transaction Flow: SDA and Record length coded on 1 or 2 bytes •


•


•




2CS.015.01 Combined functions on Transaction Flow: SDA and Record length of proprietary file coded on 1 or 2 bytes Test No: 2CS.015.01 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal supports Static Data Authentication and the

records of proprietary file involved in the SDA calculation are coded on 1 or 2 bytes. Reference Book Bulletins - Section SU 8-02 - Bulletin n°8, Editorial Changes for EMV 4.0: EMV 2000 Version 1.0 (Dec-2002)

Book Bulletins - Section SU 12-01 - Bulletin n°12, Offline Data Authentication Processing (Oct-2002) Reference Book3 - Section 10.3 - Offline Data Authentication EMV 4.1:

Book3 – Annex B2 – Coding of the Length Terminal [SDA] supported Configuration: Conditions:

•

An EMV Data Object is included in a record, located in a proprietary file, and listed in AFL and included in the data to be signed

•


•

EMV Data Object located in proprietary files will be TLV coded with record tag ‘70’

•

Signed Static Application Data is good including in the computation the tag 70 and associated length of the record contained in the proprietary files

•

Case 01: Record length of the proprietary file participating in data authentication is coded on 1 byte (b8 = 0)

•

Case 02: Record length of the proprietary file participating in data authentication is coded on 2 bytes (81 xx)



•



Page 1652


2CS.015.01 Combined functions on Transaction Flow: SDA and Record length of proprietary file coded on 1 or 2 bytes •


•


•


•




2CS.015.02 Combined functions on Transaction Flow: DDA and Record length coded on 1 or 2 bytes Test No: 2CS.015.02 - Revision 10g - Number of sub cases: 4 Objective: To ensure that the terminal supports Dynamic Data Authentication and

the records involved in the DDA calculation are coded on 1 or 2 bytes Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [DDA] supported Configuration:


•


•

Signed Dynamic Application Data is good in LT

•


•


•


•



•


•

Terminal Capabilities shall indicate Dynamic Data Authentication supported

•


•



Page 1654


2CS.015.02 Combined functions on Transaction Flow: DDA and Record length coded on 1 or 2 bytes used) received at 1st GENERATE AC. •


•




2CS.015.03 Combined functions on Transaction Flow: DDA and Record length of proprietary file coded on 1 or 2 bytes Test No: 2CS.015.03 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal supports Dynamic Data Authentication and

the records of proprietary file involved in the DDA calculation are coded on 1 or 2 bytes. Reference Book Bulletins - Section SU 12-01 - Bulletin n°12, Offline Data EMV 4.0: Authentication Processing (Oct-2002) Reference Book3 - Section 10.3 - Offline Data Authentication EMV 4.1:

Book3 – Annex B2 – Coding of the Length Terminal [DDA] supported Configuration: Conditions:

•


•


•


•

Signed Dynamic Application Data is good including in the computation the tag 70 and associated length of the record contained in the proprietary files

•


•



•


•



Page 1656


2CS.015.03 Combined functions on Transaction Flow: DDA and Record length of proprietary file coded on 1 or 2 bytes •


•


•




2CS.015.04 Combined functions on Transaction Flow: CDA and Record length coded on 1 or 2 bytes Test No: 2CS.015.04 - Revision 11 - Number of sub cases: 4 Objective: To ensure that the terminal supports Combined DDA/AC Data

Authentication and the records involved in the CDA calculation are coded on 1 or 2 bytes Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [CDA] supported Configuration:


•

AIP of LT indicates Combined Data Authentication is supported (AIP byte 1 bit 1 = 1).

•


•


•


•



•

The terminal shall process the transaction until completion, by requesting a TC

•

Terminal Capabilities shall indicate Combined Data Authentication support

•


•



Page 1658


2CS.015.04 Combined functions on Transaction Flow: CDA and Record length coded on 1 or 2 bytes •

TVR byte 1, bit 3 = '0' (ie Combined Data Authentication succeeded) received at 1st GENERATE AC.

•

TSI byte 1, bit 8 = '1' (ie Offline Data Authentication was performed) contained in financial message or Batch Data Capture



2CS.015.05 Combined functions on Transaction Flow: CDA and Record length of proprietary file coded on 1 or 2 bytes Test No: 2CS.015.05 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the terminal supports Combined DDA/AC Data

Authentication and the records of proprietary file involved in the CDA calculation are coded on 1 or 2 bytes. Reference Book Bulletins - Section SU 12-01 - Bulletin n°12, Offline Data EMV 4.0: Authentication Processing (Oct-2002) Reference Book3 - Section 10.3 - Offline Data Authentication EMV 4.1:

Book3 – Annex B2 – Coding of the Length Terminal [CDA] supported Configuration: Conditions:

•


•

AIP of LT indicatesCombined Data Authentication is supported (AIP byte 1 bit 1 = 1).

•


•

Signed Dynamic Application Data is good including in the computation the tag 70 and associated length of the record contained in the proprietary files

•


•



•


•



Page 1660


2CS.015.05 Combined functions on Transaction Flow: CDA and Record length of proprietary file coded on 1 or 2 bytes •


•

TVR byte 1, bit 3 = '0' (ie Offline Combined Data Authentication succeeded) received at 1st GENERATE AC.

•




2CS.016.00 Combined Test: SDA Tag List and AFL in Static Data Authentication Test No: 2CS.016.00 - Revision 11 - Number of sub cases: 8 Objective: To ensure that the terminal supports that SDA Tag List and record

listed in AFL participate in the SDA Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal [SDA] supported Configuration: Conditions:

•


•

SDA signature is good for each sub case

•

Case 01: SDA Tag List contains tag '82' (AIP) and a record from an EMV file is listed in the AFL and participate in Static Data Authentication

•

Case 02: SDA Tag List contains tag '82' (AIP) and a record from a proprietary file is listed in the AFL and participate in Static Data Authentication

•

Case 03: SDA Tag List contains tag '82' (AIP) and a record from an EMV file and a record from a proprietary file is listed in the AFL and participate in Static Data Authentication

•

Case 04: SDA Tag List contains tag '82' (AIP) and no records are listed as participating in Static Data Authentication

•

Case 05: SDA Tag List is not present, and a record from an EMV file is listed in the AFL and participate in Static Data Authentication

•

Case 06: SDA Tag List is not present and a record from a proprietary file is listed in the AFL and participate in Static Data Authentication

•

Case 07: SDA Tag List is not present and a record from an EMV file and a record from a proprietary file is listed in the AFL and participate in Static Data Authentication


Page 1662


2CS.016.00 Combined Test: SDA Tag List and AFL in Static Data Authentication Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•


•


•




2CS.016.03 Combined Test: SDA Tag List and AFL in Dynamic Data Authentication Test No: 2CS.016.03 - Revision 11 - Number of sub cases: 8 Objective: To ensure that the terminal supports that SDA Tag List and record

listed in AFL participate in the DDA Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•

SDA signature is good for each sub case

•

Case 01: SDA Tag List contains AIP, and a record from an EMV file is listed in the AFL and participate in Dynamic Data Authentication

•

Case 02: SDA Tag List contains AIP and a record from a proprietary file is listed in the AFL and participate in Dynamic Data Authentication

•

Case 03: SDA Tag List contains AIP and a record from an EMV file and a record from a proprietary file is listed in the AFL and participate in Dynamic Data Authentication

•

Case 04: SDA Tag List contains AIP and no records are listed as participating in Dynamic Data Authentication

•

Case 05: SDA Tag List is not present, and a record from an EMV file is listed in the AFL and participate in Dynamic Data Authentication

•

Case 06: SDA Tag List is not present and a record from a proprietary file is listed in the AFL and participate in Dynamic Data Authentication

•

Case 07: SDA Tag List is not present and a record from an EMV file and a record from a proprietary file is listed in the AFL and participate in Dynamic Data Authentication


Page 1664


2CS.016.03 Combined Test: SDA Tag List and AFL in Dynamic Data Authentication Action: NA Procedure: Application in LT is selected and transaction is processed with LT (In


•


•


•


•


•




2CS.016.05 Combined Test: SDA Tag List and AFL in Combined Data Authentication Test No: 2CS.016.05 - Revision 11 - Number of sub cases: 8 Objective: To ensure that the terminal supports that SDA Tag List and record

listed in AFL participate in the CDA Reference Book 3 - Section 6.3 - Offline Data Authentication EMV 4.0: Reference Book 3 - Section 10.3 - Offline Data Authentication EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•

Case 01: SDA Tag List contains AIP, and a record from an EMV file is listed in the AFL and participate in Combined Data Authentication

•

Case 02: SDA Tag List contains AIP and a record from a proprietary file is listed in the AFL and participate in Combined Data Authentication

•

Case 03: SDA Tag List contains AIP and a record from an EMV file and a record from a proprietary file is listed in the AFL and participate in Combined Data Authentication

•

Case 04: SDA Tag List contains AIP and no records are listed as participating in Combined Data Authentication

•

Case 05: SDA Tag List is not present, and a record from an EMV file is listed in the AFL and participate in Combined Data Authentication

•

Case 06: SDA Tag List is not present and a record from a proprietary file is listed in the AFL and participate in Combined Data Authentication

•

Case 07: SDA Tag List is not present and a record from an EMV file and a record from a proprietary file is listed in the AFL and participate in Combined Data Authentication

Action: NA


Page 1666


2CS.016.05 Combined Test: SDA Tag List and AFL in Combined Data Authentication Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

TVR byte 1, bit 3 = '0' (ie Offline CDA succeeded) received at 1st GENERATE AC.

•


•


•




Combined Test

Introduction Note of the 2CT serie: The tests of the 2CT serie shall be performed once for each payment scheme profile.


Page 1668


2CT.008.00 Combined functions on Transaction Flow: SDA and PIN Encryption Test No: 2CT.008.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the Terminal is able to perform both Static Data

Authentication and PIN Encryption during the same transaction Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal ([SDA] supported AND [Offline Enciphered PIN] supported) Configuration: Conditions:

•


•


•

CVM requires 'Enciphered PIN verification Offline' (04 00)


•


•


•


•


•


•


•




2CT.008.00 Combined functions on Transaction Flow: SDA and PIN Encryption performed) received at 1st GENERATE AC.


Page 1670


2CT.009.00 Combined functions on Transaction Flow: DDA and PIN Encryption Test No: 2CT.009.00 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the Terminal is able to perform both Dynamic Data

Authentication and PIN Encryption using ICC Public Key during the same transaction Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal ([DDA] supported AND [Offline Enciphered PIN] supported) Configuration: Conditions:

•


•


•


•

All certificates and related calculations for PIN Encipherment are made from the ICC Public Key.


•


•


•


•


•




2CT.009.00 Combined functions on Transaction Flow: DDA and PIN Encryption •


•



Page 1672


2CT.009.01 Combined functions on Transaction Flow: DDA and PIN Encryption (2) Test No: 2CT.009.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the Terminal is able to perform both Dynamic Data

Authentication and PIN Encryption using ICC PIN Encipherment Public Key during the same transaction Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal ([DDA] supported AND [Offline Enciphered PIN] supported) Configuration: Conditions:

•


•


•


•

All certificates and related calculations for PIN Encipherment are made from the ICC PIN Encipherment Public Key.


•


•


•


•


•




2CT.009.01 Combined functions on Transaction Flow: DDA and PIN Encryption (2) •


•



Page 1674


2CT.010.00 Combined functions on Transaction Flow: CDA and PIN Encryption Test No: 2CT.010.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that the Terminal is able to perform both Combined DDA/AC

Data Authentication and PIN Encryption using ICC Public Key during the same transaction Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal ([CDA] supported AND [Offline Enciphered PIN] supported) Configuration: Conditions:

•


•


•


•

All certificates and related calculations for PIN Encipherment are made from the ICC Public Key.

•

IAC’s and TAC’s are set so that TC is requested at first and second Gen AC.

•

If transaction is processed online, terminal is unable to go online.


•


•


•




2CT.010.00 Combined functions on Transaction Flow: CDA and PIN Encryption •

TVR byte 1, bit 3 = '0' (ie Offline Combined Data Authentication succeeded) contained in Financial Confirmation message or Batch Data Capture message

•



Page 1676


2CT.010.01 Combined functions on Transaction Flow: CDA and PIN Encryption Test No: 2CT.010.01 - Revision 16 - Number of sub cases: 0 Objective: To ensure that the Terminal is able to perform both Combined DDA/AC

Data Authentication and PIN Encryption using ICC PIN Encipherment Public Key during the same transaction Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal ([CDA] supported AND [Offline Enciphered PIN] supported) Configuration: Conditions:

•


•


•


•

All certificates and related calculations for PIN Encipherment are made from the ICC PIN Encipherment Public Key.

•


•



•


•


•




2CT.010.01 Combined functions on Transaction Flow: CDA and PIN Encryption •

TVR byte 1, bit 3 = '0' (ie Offline Combined Data Authentication succeeded) contained in Financial Confirmation message or Batch Data Capture message

•


•


•



Page 1678


2CT.011.00 Combined functions on Transaction Flow: Issuer Authentication and Script Processing Test No: 2CT.011.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal is able to perform both Issuer

Authentication and Issuer Script Processing during the same transaction Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•

Response message from the Issuer contains the following scripts:

•

Case 01: one '71' script

•

Case 02: one '72' script

•

Case 03: one '71' script and one '72' script


•


•

TVR byte 5 bit 6 = '0' (ie Script processing did not fail before final GENERATE AC (subcase 01 and 03)) received at 2nd GENERATE AC.

•

TVR byte 5 bit 5 = '0' (ie Script processing did not fail after final GENERATE AC (subcase 02 and 03)) contained in Financial Confirmation message or Batch Data Capture message

•




2CT.011.00 Combined functions on Transaction Flow: Issuer Authentication and Script Processing contained in Financial Confirmation message or Batch Data Capture message •

TVR byte 5 bit 7 = '0' (ie Issuer Authentication was successful) received at 2nd GENERATE AC.

•

TSI byte 1, bit 5 = '1' (ie Issuer Authentication was performed) received at 2nd GENERATE AC.


Page 1680


2CT.011.01 Combined functions on Transaction Flow: Issuer Authentication and Script Processing (2) Test No: 2CT.011.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the Terminal is able to perform both Issuer

Authentication and Issuer Script Processing with error during the same transaction Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•

Authorization response message contains one '71' Issuer script with the following commands.

•


•



•


•


•


•


•

TSI byte 1, bit 5 = '1' (ie Issuer Authentication was performed)



2CT.011.01 Combined functions on Transaction Flow: Issuer Authentication and Script Processing (2) received at 2nd GENERATE AC.


Page 1682


2CT.011.02 Combined functions on Transaction Flow: Issuer Authentication and Script Processing (3) Test No: 2CT.011.02 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal is able to perform both Issuer


•


•


•


•


•



•


•


•

TVR byte 5 bit 5 = '1' (ie Script processing failed after final GENERATE AC) contained in Financial Confirmation message or Batch Data Capture message

•




2CT.011.02 Combined functions on Transaction Flow: Issuer Authentication and Script Processing (3) •



Page 1684




•


•


•


•


•


•


•


•



•


•






•

TVR byte 5 bit 5 = '1' (ie Script processing failed after final GENERATE AC) contained in Financial Confirmation message or Batch Data Capture message

•


•



Page 1686




•


•


•


•


•


•


•


•



•


•






•

TVR byte 5 bit 5 = '0' (ie Script processing succeeded after final GENERATE AC) contained in Financial Confirmation message or Batch Data Capture message

•


•



Page 1688


2CT.012.00 Combined functions on Transaction Flow: Advice and Issuer Authentication Test No: 2CT.012.00 - Revision 12 - Number of sub cases: 0 Objective: To ensure that the Terminal is able to perform Issuer Authentication

and to support advice message to the issuer, if the 'Advice required' bit is set to 1b in the Cryptogram Information Data. Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•

LT answers to the First GENERATE AC with the bit 4 of its Cryptogram Information Data (CID) sets to '1'

•

LT answers on second GENERATE AC is AAC

•

Transaction shall not be captured

Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria: The terminal shall process the transaction until completion and is

declined. Terminal shall transmit an advice if Advice is supported and data capture is not supported.



2CT.012.01 Combined functions on Transaction Flow: Advice and Issuer Authentication (2) Test No: 2CT.012.01 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the Terminal is able to perform Issuer Authentication

and to support advice message to the issuer, if the 'Advice required' bit and the 'Issuer Authentication Failed' bits are set to 1b in the Cryptogram Information Data. Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•

LT answers to the first GENERATE AC with the bits 1, 2 and 4 of its Cryptogram Information Data (CID) are set to '1'.

•


•

Transaction shall not be captured


•


•

Terminal shall transmit an advice if Advice is supported nad data capture is not supported.


Page 1690


2CT.013.00 Combined functions on Transaction Flow: Advice on first and second Generate AC Test No: 2CT.013.00 - Revision 15 - Number of sub cases: 0 Objective: To ensure that the Terminal is able to support advice messages to the

issuer, during first and second GENERATE AC. To ensure that if the terminal does not support advices that it ignores the advice request and completes the transaction. Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•

LT answers to the first GENERATE AC with the bit 4 of its Cryptogram Information Data (CID) sets to '1'

•

LT answers on second GENERATE AC is TC

•

LT answers to the second GENERATE AC with the bit 4 of its Cryptogram Information Data (CID) sets to '1'


•


•

The terminal shall transmit an advice, if Advice is supported and data capture is not supported



2CT.013.01 Combined functions on Transaction Flow: Advice on first and second Generate AC (2) Test No: 2CT.013.01 - Revision 11 - Number of sub cases: 0 Objective: To ensure that the Terminal is able to support advice messages to the

issuer, during first and second GENERATE AC. Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal ([Advice] supported AND [Online Only or Offline/Online capable] Configuration: supported) Conditions:

•


•

LT answers to the first GENERATE AC with the bit 4 of its Cryptogram Information Data (CID) sets to '1'

•


•

LT answers to the second GENERATE AC with the bit 4 of its Cryptogram Information Data (CID) sets to '1'


•


•

The terminal shall send an advice message.


Page 1692


2CT.017.00 Combined Test: Get Processing and Generate AC with different response format Test No: 2CT.017.00 - Revision 10g - Number of sub cases: 2 Objective: To ensure that the terminal supports in the same transaction the

response format 1 and 2 for Get Processing and GENERATE AC. Reference Book 3 - Section 2.5 - Commands EMV 4.0: Reference Book 3 - Section 6.5 - Commands EMV 4.1: Terminal NA Configuration: Conditions:

•

Case 01: Response to GET PROCESSING OPTIONS is in format 1 and Response to GENERATE AC is in format 2

•



•




2CT.017.01 Combined Test: Get Processing and Generate AC with different response format (2) Test No: 2CT.017.01 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the terminal supports in the same transaction the

response format 1 and 2 for Get Processing and GENERATE AC. Reference Book 3 - Section 2.5 - Commands EMV 4.0: Reference Book 3 - Section 6.5 - Commands EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•

Case 01: Response to GET PROCESSING OPTIONS is in format 1, Response to first GENERATE AC is in format 2 and Response to second GENERATE AC is in format 1

•


•



•



Page 1694


2CT.018.00 Combined Test: Get Processing and Generate AC with different response format, CDA Test No: 2CT.018.00 - Revision 16 - Number of sub cases: 2 Objective: To ensure that the terminal supports in the same transaction the

response format 1 and 2 for Get Processing and GENERATE AC when performing Combined Data Authentication Reference Book 3 - Section 2.5 - Commands EMV 4.0: Reference Book 3 - Section 6.5 - Commands EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•


•


•


•



•


•

TVR byte 1, bit 3 = '0' (ie Offline Combined Data Authentication succeeded or not used) contained in Financial Confirmation message or Batch Data Capture message.

•


•




2CT.018.00 Combined Test: Get Processing and Generate AC with different response format, CDA used) received at 1st GENERATE AC.


Page 1696


2CT.018.01 Combined Test: Get Processing and Generate AC with different response format, CDA (2) Test No: 2CT.018.01 - Revision 16 - Number of sub cases: 2 Objective: To ensure that the terminal supports in the same transaction the

response format 1 and 2 for Get Processing and GENERATE AC when performing Combined Data Authentication Reference Book 3 - Section 2.5 – Commands EMV 4.0: Reference Book 3 - Section 6.5 – Commands EMV 4.1: Terminal [CDA] supported Configuration: Conditions:

•


•


•

IAC’s and TAC’s are set so that ARQC is requested at first Gen AC and TC at second Gen AC.

•


•


•



•


•

TVR byte 1, bit 3 = '0' (ie Offline Combined Data Authentication succeeded or not used) contained in Financial Confirmation message or Batch Data Capture message.



2CT.018.01 Combined Test: Get Processing and Generate AC with different response format, CDA (2) •


•



Page 1698


2CT.019.00 Combined Test: Get Processing, Internal Authenticate and Generate AC with different response format Test No: 2CT.019.00 - Revision 11 - Number of sub cases: 3 Objective: To ensure that the terminal supports in the same transaction the

response format 1 and 2 for Get Processing, Internal Authenticate and GENERATE AC. Reference Book 3 - Section 2.5 - Commands EMV 4.0: Reference Book 3 - Section 6.5 - Commands EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•


•


•

Case 01: Response to GET PROCESSING OPTIONS is in format 1 and Response to INTERNAL AUTHENTICATE is in format 2 and Response to GENERATE AC is in format 1

•


•



•




2CT.019.01 Combined Test: Get Processing, Internal Authenticate and Generate AC with different response format (2) Test No: 2CT.019.01 - Revision 11 - Number of sub cases: 3 Objective: To ensure that the terminal supports in the same transaction the

response format 1 and 2 for Get Processing, Internal Authenticate and GENERATE AC. Reference Book 3 - Section 2.5 - Commands EMV 4.0: Reference Book 3 - Section 6.5 - Commands EMV 4.1: Terminal ([DDA] supported AND [Online Only or Offline/Online capable] Configuration: supported) Conditions:

•


•


•


•

Case 01: Response to GET PROCESSING OPTIONS is in format 1 and Response to INTERNAL AUTHENTICATE is in format 2, Response to first GENERATE AC is in format 1 and Response to second GENERATE AC is in format 2

•


•



•



Page 1700


2CT.020.00 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script Test No: 2CT.020.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: PSE, Get Processing with an empty PDOL, SDA, Plaintext PIN, Issuer Authentication, GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•


•

LT contains a PSE

•

Select ADF response of LT contains an empty PDOL

•

CVM requires 'Plaintext PIN verification Offline, if terminal supports CVM (01 03), followed by 'Paper Signature, if terminal supports CVM (1E 03), followed by 'Online PIN, if terminal supports CVM (02 03), followed by 'No CVM, always' (1F 00)

•

GENERATE AC LT response is in format 1

•

Case 01: LT parameters are set so that transaction is performed on-line, LT answers with an 72 script.

•

Case 02: LT parameters are set so that transaction is performed off-line.

•

Case 03: LT parameters are set so that transaction is performed



2CT.020.00 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script on-line, LT answers with an 71 script Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•



Page 1702


2CT.020.01 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1 Test No: 2CT.020.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: PSE, Get Processing with an empty PDOL, SDA, Plaintext PIN, Issuer Authentication, GENERATE AC Format 1 Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•

AIP of LT indicates Issuer Authentication is supported (AIP byte 1 bit 3 = 1

•

LT contains a PSE

•


•

CVM requires 'Plaintext PIN verification Offline, if terminal supports CVM (01 03), followed by 'Paper Signature, if terminal supports CVM (1E 03), followed by 'No CVM, always' (1F 00)

•


•

LT parameters are set so that transaction is performed off-line.


•




2CT.021.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script Test No: 2CT.021.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing with an empty PDOL, SDA, Plaintext PIN, Issuer Authentication, GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•


•

LT does not contain a PSE

•


•

CVM requires 'Plaintext PIN verification Offline, if terminal supports CVM (01 03), followed by 'Paper Signature, if terminal supports CVM (1E 03), followed by 'Online PIN, if terminal supports CVM (02 03), followed by 'No CVM, always' (1F 00)

•


•


•


•

Case 03: LT parameters are set so that transaction is performed on-line, LT answers with an 71 script


Page 1704


2CT.021.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•




2CT.021.01 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1 Test No: 2CT.021.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing with an empty PDOL, SDA, Plaintext PIN, Issuer Authentication, GENERATE AC Format 1 Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•


•


•


•


•


•



•



Page 1706


2CT.022.00 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Paper Signature, Issuer Authentication, Generate AC Format 1, Script Test No: 2CT.022.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: PSE, Get Processing with an empty PDOL, SDA, Paper Signature, Issuer Authentication, GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•


•

LT contains a PSE

•


•

CVM requires 'Paper Signature, if terminal supports CVM (1E 03), followed by 'No CVM, always' (1F 00)

•


•


•


•




2CT.022.00 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Paper Signature, Issuer Authentication, Generate AC Format 1, Script Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•



Page 1708


2CT.022.01 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Paper Signature, Issuer Authentication, Generate AC Format 1 Test No: 2CT.022.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: PSE, Get Processing with an empty PDOL, SDA, Paper Signature, Issuer Authentication, GENERATE AC Format 1 Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•


•

LT contains a PSE

•


•


•


•



•




2CT.023.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Paper Signature, Issuer Authentication, Generate AC Format 1, Script Test No: 2CT.023.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing with an empty PDOL, SDA, Paper Signature, Issuer Authentication, GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•


•


•


•


•


•


•


•


Action: NA


Page 1710


2CT.023.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Paper Signature, Issuer Authentication, Generate AC Format 1, Script Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•




2CT.023.01 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Paper Signature, Issuer Authentication, Generate AC Format 1, Script (2) Test No: 2CT.023.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following functions: No PSE, Get Processing with an empty PDOL, SDA, Paper Signature, Issuer Authentication, GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•


•


•


•


•


•



•



Page 1712


2CT.024.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script Test No: 2CT.024.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing with an empty PDOL, SDA, Paper Signature, No Issuer Authentication, GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•


•


•


•

GENERATE AC LT response is in format 1, IAD is not present

•


•


•





2CT.024.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script Pass Criteria:

•



Page 1714


2CT.024.01 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script (2) Test No: 2CT.024.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing with an empty PDOL, SDA, Paper Signature, No Issuer Authentication, GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•


•


•


•


•



•




2CT.025.00 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script Test No: 2CT.025.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: PSE, Get Processing with an empty PDOL, SDA, Paper Signature, No Issuer Authentication, GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•

LT contains PSE.

•


•


•


•


•


•



•



Page 1716


2CT.025.00 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script requesting a TC or an AAC.



2CT.025.01 Combined functions on Transaction Flow: PSE, PDOL empty, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script (2) Test No: 2CT.025.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: PSE, Get Processing with an empty PDOL, SDA, Paper Signature, No Issuer Authentication, GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•

LT contains PSE.

•


•


•


•



•



Page 1718


2CT.026.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Plaintext PIN, No Issuer Authentication, Generate AC Format 2, Script Test No: 2CT.026.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing with an empty PDOL, SDA, Plaintext PIN, No Issuer Authentication (IAD present), GENERATE AC Format 2, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•


•


•


•

GENERATE AC LT response is in format 2, IAD present

•


•


•


Action: NA



2CT.026.00 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Plaintext PIN, No Issuer Authentication, Generate AC Format 2, Script Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•



Page 1720


2CT.026.01 Combined functions on Transaction Flow: No PSE, PDOL empty, SDA, Plaintext PIN, No Issuer Authentication, Generate AC Format 2, Script (2) Test No: 2CT.026.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing with an empty PDOL, SDA, Plaintext PIN, No Issuer Authentication (IAD present), GENERATE AC Format 2, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•


•


•


•


•



•




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 Test No: 2CT.027.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing Option Format 2, SDA, Plaintext PIN, No Issuer Authentication (IAD present), GENERATE AC Format 2, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•


•

Select ADF response of LT contains a valid PDOL

•

Get Processing Options response of LT is in format 2

•


•


•


•


•


Action: NA


Page 1722


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 Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•




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) Test No: 2CT.027.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing Option Format 2, SDA, Plaintext PIN, No Issuer Authentication (IAD present), GENERATE AC Format 2, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•


•


•


•


•


•



•



Page 1724


2CT.028.00 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 1, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script (2) Test No: 2CT.028.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing Option Format 1, SDA, Paper Signature, No Issuer Authentication (IAD present), GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•


•


•


•


•


•


•


•


Action: NA



2CT.028.00 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 1, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script (2) Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•



Page 1726


2CT.028.01 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 1, SDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script (2) Test No: 2CT.028.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing Option Format 1, SDA, Paper Signature, No Issuer Authentication (IAD present), GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•


•


•


•


•


•



•




2CT.029.00 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 1, TRM, SDA, DDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script Test No: 2CT.029.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing Option Format 1, TRM, SDA, DDA, Paper Signature, No Issuer Authentication (IAD present), GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•


•

AIP of LT indicates Terminal Risk Management is to be perfomed (AIP byte 1 bit 4 = 1).

•


•


•


•


•


•


•



Page 1728


2CT.029.00 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 1, TRM, SDA, DDA, Paper Signature, No Issuer Authentication, Generate AC Format 1, Script •



•




2CT.029.01 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 1, TRM, SDA, DDA, Paper Signature, No Issuer Authentication, Generate AC Format 1 Test No: 2CT.029.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing Option Format 1, TRM, SDA, DDA, Paper Signature, No Issuer Authentication (IAD present), GENERATE AC Format 1 Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•


•

AIP of LT indicates Terminal Risk Management is to be perfomed (AIP byte 1 bit 4 = 1).

•


•


•


•


•


•




Page 1730


2CT.029.01 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 1, TRM, SDA, DDA, Paper Signature, No Issuer Authentication, Generate AC Format 1 Pass Criteria:

•




2CT.030.00 Combined functions on Transaction Flow: No PSE, PDOL Empty, SDA, DDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script (2) Test No: 2CT.030.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing Option with an empty PDOL, SDA, DDA, Plaintext PIN, Issuer Authentication, GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•


•


•


•


•


•


•


•


•



Page 1732


2CT.030.00 Combined functions on Transaction Flow: No PSE, PDOL Empty, SDA, DDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script (2) on-line, LT answers with an 71 script Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•




2CT.030.01 Combined functions on Transaction Flow: No PSE, PDOL Empty, SDA, DDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script (2) Test No: 2CT.030.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing Option with an empty PDOL, SDA, DDA, Plaintext PIN, Issuer Authentication, GENERATE AC Format 1, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•


•


•


•


•


•


•



•



Page 1734


2CT.030.01 Combined functions on Transaction Flow: No PSE, PDOL Empty, SDA, DDA, Plaintext PIN, Issuer Authentication, Generate AC Format 1, Script (2) requesting a TC or an AAC.



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 Test No: 2CT.031.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: PSE, Get Processing Option is in format 2, SDA, DDA, Enciphered PIN, Issuer Authentication, GENERATE AC Format 2, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•


•


•

A PSE is present in LT

•

Get Processing Options response of LT is in Format 2

•

CVM requires 'Enciphered PIN verification Offline, if terminal supports CVM (04 03), followed by 'Paper Signature, if terminal supports CVM (1E 03), followed by 'No CVM, always' (1F 00)

•


•


•


•



Page 1736


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 on-line, LT answers with an 71 script. Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•




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) Test No: 2CT.031.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: PSE, Get Processing Option is in format 2, SDA, DDA, Enciphered PIN, Issuer Authentication, GENERATE AC Format 2, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•


•


•

A PSE is present in LT

•


•


•


•



•



Page 1738


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) requesting a TC or an AAC.



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 Test No: 2CT.032.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing Option is in format 2, TRM, SDA, DDA, CDA, Enciphered PIN, Issuer Authentication, GENERATE AC Format 2, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•

AIP of LT indicates Combined DDA/AC Authentication is supported (AIP byte 1 bit 1 = 1).

•


•


•

AIP of LT indicates Terminal Risk Management is to be performed (AIP byte 1 bit 4 = 1).

•


•


•


•


•



Page 1740


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 on-line, LT answers with an 72 script. •


•



•




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) Test No: 2CT.032.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing Option is in format 2, TRM, SDA, DDA, CDA, Enciphered PIN, Issuer Authentication, GENERATE AC Format 2, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•


•


•


•


•

AIP of LT indicates Terminal Risk Management is to be performed (AIP byte 1 bit 4 = 1).

•


•


•


•



Page 1742


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) Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•




2CT.033.00 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 2, SDA, DDA,CDA, Paper Signature, No Issuer Authentication, Generate AC Format 2, Script (2) Test No: 2CT.033.00 - Revision 10g - Number of sub cases: 3 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing Option is in format 2, SDA, DDA, CDA, Paper Signature, No Issuer Authentication, GENERATE AC Format 2, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Online Only or Offline/Online capable] supported Configuration: Conditions:

•


•


•


•


•


•


•


•


•


•


•



Page 1744


2CT.033.00 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 2, SDA, DDA,CDA, Paper Signature, No Issuer Authentication, Generate AC Format 2, Script (2) Action: NA Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•




2CT.033.01 Combined functions on Transaction Flow: No PSE, Get Processing Option Format 2, SDA, DDA,CDA, Paper Signature, No Issuer Authentication, Generate AC Format 2, Script (2) Test No: 2CT.033.01 - Revision 10g - Number of sub cases: 0 Objective: To ensure that the Terminal supports in the same transaction the

following LT functions: No PSE, Get Processing Option is in format 2, SDA, DDA, CDA, Paper Signature, No Issuer Authentication, GENERATE AC Format 2, Script Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Offline Only] supported Configuration: Conditions:

•


•


•


•


•


•


•


•


•



•



Page 1746




2CT.034.00 Combined functions on Transaction Flow: Proprietary Data and EMV data Test No: 2CT.034.00 - Revision 11 - Number of sub cases: 00 Objective: To ensure that the Terminal is able to perform correctly the transaction

on the following LT profile Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal NA Configuration: Conditions:

•

AIP of LT = '7D 00'

•

Language Preference of LT = ' 6A 61 65 6E'

•

Application Version Number of LT = '02 00'

•

AFL of LT has a length of 20 bytes

•

CDOL1 and CDOL2 of LT have a length of 128 bytes

•

CVM List of LT = '00 00 00 00 00 00 00 00 41 03 1E 03 02 03 1F 03'

•

A record of LT contain the proprietary tag '9F 54'

•

A record of LT contain the proprietary tag 'DF 4F'

•

A record of LT contain the proprietary tag '9F 55''


•



Page 1748


2CT.035.00 Combined functions on Transaction Flow: SDA, Keys remainder not present, Proprietary Data and EMV data Test No: 2CT.035.00 - Revision 11 - Number of sub cases: 00 Objective: To ensure that the Terminal is able to perform correctly the transaction

on the following LT profile: SDA, Keys remainder not present, Proprietary Data and EMV data Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [SDA] supported Configuration:

Conditions:

•

CA Public Key has a length of 1984 bits

•

AIP of LT = '5C 00'

•


•


•


•


•

CVM List of LT = '00 00 00 00 00 00 00 00 41 03 1E 03 02 03 1F 03'

•


•


•


•

Issuer Public Key has a length of 1744 bits

•

Issuer Public Key Remainder is not present in LT


•




2CT.035.00 Combined functions on Transaction Flow: SDA, Keys remainder not present, Proprietary Data and EMV data requesting a TC or an AAC. •



Page 1750


2CT.036.00 Combined functions on Transaction Flow: DDA, Keys remainder not present, Proprietary Data and EMV data Test No: 2CT.036.00 - Revision 11 - Number of sub cases: 2 Objective: To ensure that the Terminal is able to perform correctly the transaction

on the following LT profile: DDA, Keys remainder not present, Proprietary Data and EMV data Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [DDA] supported Configuration:

Conditions:

•


•

AIP of LT = '7C 00'

•


•


•


•


•

CVM List of LT = '00 00 00 00 00 00 00 00 41 03 1E 03 02 03 1F 03'

•


•


•


•


•

ICC Public Key has a lentgh of 1504 bits

•

Case 01: Issuer Public Key Remainder is not present in LT

•

Case 02: ICC Public Key Remainder is not present in LT

Action: NA



2CT.036.00 Combined functions on Transaction Flow: DDA, Keys remainder not present, Proprietary Data and EMV data Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•



Page 1752


2CT.037.00 Combined functions on Transaction Flow: CDA, Keys remainder not present, Proprietary Data and EMV data Test No: 2CT.037.00 - Revision 15 - Number of sub cases: 00 Objective: To ensure that the Terminal is able to perform correctly the transaction

on the following LT profile: CDA, Keys remainder not present, Proprietary Data and EMV data Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [CDA] supported Configuration:

Conditions:

•


•

AIP of LT = '7D 00'

•


•


•


•


•

CVM List of LT = '00 00 00 00 00 00 00 00 41 03 1E 03 02 03 1F 03'

•


•


•


•


•

ICC Public Key has a lentgh of 1504 bits

•


•




2CT.037.00 Combined functions on Transaction Flow: CDA, Keys remainder not present, Proprietary Data and EMV data •

Case 01: Issuer Public Key Remainder is missing

•

Case 02: ICC Public Key Remainder is missing


•


•



Page 1754


2CT.038.00 Combined functions on Transaction Flow: LCOLL = 00, UCOLL= FF Proprietary Data and EMV data Test No: 2CT.038.00 - Revision 11 - Number of sub cases: 00 Objective: To ensure that the Terminal is able to perform correctly the transaction

on the following LT profile Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Velocity checking] supported Configuration: Conditions:

•

AIP of LT = '7D 00'

•


•


•


•

CDOL1 and CDOL2 of LT have a length of 131 bytes (1 bytes Tag, 2 bytes Length, 128 bytes Value)

•

CVM List of LT = '00 00 00 00 00 00 00 00 41 03 1E 03 02 03 1F 03'

•


•


•


•

Lower Consecutive Offline Limit = 00

•

Upper Consecutive Offline Limit = FF

•


•

ATC - Last Online ATC = Upper Consecutive Offline Limit

Action: NA



2CT.038.00 Combined functions on Transaction Flow: LCOLL = 00, UCOLL= FF Proprietary Data and EMV data Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•

TVR byte 4, bit 6 = '0' (ie Upper Consecutive Offline Limit is not exceeded) received at 1st GENERATE AC.

•



Page 1756


2CT.038.01 Combined functions on Transaction Flow: LCOLL = 00, UCOLL= FF Proprietary Data and EMV data Test No: 2CT.038.01 - Revision 11 - Number of sub cases: 00 Objective: To ensure that the Terminal is able to perform correctly the transaction

on the following LT profile Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [Velocity checking] supported Configuration: Conditions:

•

AIP of LT = '7D 00'

•


•


•

Issuer Identifier of LT = '354FFFFF'

•


•

CDOL1 and CDOL2 of LT have a length of 131 bytes (1 bytes Tag, 2 bytes Length, 128 bytes Value)

•

CVM List of LT = '00 00 00 00 00 00 00 00 41 03 1E 03 02 03 1F 03'

•


•


•


•

Lower Consecutive Offline Limit = 00

•

Upper Consecutive Offline Limit = FF

•


Action: NA



2CT.038.01 Combined functions on Transaction Flow: LCOLL = 00, UCOLL= FF Proprietary Data and EMV data Procedure: Application in LT is selected and transaction is processed with LT. Pass Criteria:

•


•


•



Page 1758


2CT.039.00 ICC supporting DDA Only Test No: 2CT.039.00 - Revision 12 - Number of sub cases: 00 Objective: To ensure that the Terminal is able to perform correctly the transaction

on the following LT profile Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal [DDA] supported Configuration: Conditions:

•

AIP of LT = '3C 00'

•

AFL of LT indicates no records are signed (i.e. fourth byte of each entry = ‘00’)

•

Signed Static Application Data (tag’93’) is not present in any record.


•


•

TVR byte 1, bit 8 = '0' (i.e. Offline data authentication performed) received at 1st GENERATE AC.

•

TVR byte 1, bit 6 = '0' (i.e. no ICC data missing) received at 1st GENERATE AC.

•

TVR byte 1, bit 4 = '0' (i.e. DDA passed) received at 1st GENERATE AC.

•

TSI byte 1, bit 8 = '1 (i.e. Offline data authentication was performed) received at 1st GENERATE AC.



2CT.040.00 CPA compliant profile Test No: 2CT.040.00 - Revision 16 - Number of sub cases: 0 Objective: To ensure that the Terminal supports CPA compliant profile card

application Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal NA Configuration: Conditions:

•

Select ADF response of LT contains a valid PDOL requesting related data of 128 bytes.

•

CDOL1 contains all data listed in CPA specifications (version 1.0 december 2005) Table 15-5 and filled with other data in order to have a CDOL1 related data length of 65 bytes

•

CDOL2 contains all data listed in CPA specifications (version 1.0 december 2005) Table 17-6 and filled with other data in order to have CDOL2 related data length of 63 bytes

•

1st GENERATE AC and 2nd GENERATE AC responses are in format 2, IAD is present with a length of 32 bytes.

•



•


•

The terminal shall return a GET PROCESSING OPTIONS command to the LT with data field correctly filled according to PDOL, where the length byte for tag '83' is coded on two bytes

•

The terminal shall return GENERATE AC commands to the LT with Data field correctly filled according to CDOL1 and 2


Page 1760


2CT.040.01 CPA compliant profile (2) Test No: 2CT.040.01 - Revision 16 - Number of sub cases: 0 Objective: To ensure that the Terminal supports CPA compliant profile card

application Reference Book 3 - Section 4 - Transaction Flow EMV 4.0: Reference Book 3 - Section 8 - Transaction Flow EMV 4.1: Terminal NA Configuration: Conditions:

•


•


•

Select ADF response of LT contains: 6F 81 F0 (FCI Template containing 240 bytes, 2 byte length) 84 10 <16 bytes of DF Name> A5 81 DB (FCI Proprietary template, 2 bytes length) 9F 38 81 D7 <215 bytes of valid PDOL>

•

CDOL1 contains all data listed in CPA specifications (version 1.0 december 2005) Table 15-5 without any additional data

•

CDOL2 contains all data listed in CPA specifications (version 1.0 december 2005) Table 17-6 without any additional data

•

1st GENERATE AC and 2nd GENERATE AC responses are in format 2, IAD is present with a length of 32 bytes.

•



•


•

The terminal shall return a GET PROCESSING OPTIONS command to the LT with data field correctly filled according to



2CT.040.01 CPA compliant profile (2) PDOL •

The terminal shall return GENERATE AC commands to the LT with Data field correctly filled according to CDOL1 and 2


Page 1762


Annex A: Test cases applicable depending on the terminal options This section list the test cases applicable to perform the Terminal Type Approval Level 2, in accordance with the Implementation Conformance Statement – Version 3.0, Level 2 – EMV Application Kernel. The test are sorted by configurable options according to the ICS template. All Terminals

2CA.001.02

2CA.097.00

2CI.021.00

2CA.001.04

2CA.098.00

2CI.027.00

2CJ.097.00

2CL.049.00

2CA.002.00

2CA.099.00

2CJ.002.00

2CJ.098.00

2CL.050.00

2CJ.005.00

2CJ.099.00

2CL.054.00

2CA.013.00

2CL.048.00

2CA.014.00

2CB.007.00

2CJ.006.00

2CJ.100.00

2CL.055.00

2CA.015.00

2CB.024.00

2CJ.007.00

2CJ.100.01

2CM.006.00

2CJ.009.00

2CJ.100.03

2CM.010.00

2CA.017.00

2CB.025.06

2CJ.010.00

2CJ.115.01

2CM.011.00

2CA.018.00

2CB.026.05

2CJ.010.01

2CJ.150.00

2CM.028.00

2CA.019.00

2CB.028.00

2CJ.011.00

2CJ.158.00

2CA.020.00

2CB.031.00

2CJ.012.00

2CM.034.00

2CA.021.00

2CB.031.06

2CJ.013.00

2CM.036.01

2CA.016.00

2CA.022.00

2CB.031.07

2CJ.014.00

2CA.023.00

2CB.032.00

2CJ.015.00

2CJ.170.00

2CM.042.00

2CA.027.00

2CB.034.00

2CJ.016.00

2CK.001.00

2CM.003.00

2CA.030.00

2CB.035.00

2CJ.017.00

2CK.002.00

2CM.066.00

2CA.064.00

2CB.036.00

2CJ.035.00

2CK.003.00

2CM.083.00

2CA.032.00

2CB.037.00

2CJ.036.00

2CK.009.00

2CM.085.00

2CA.033.00

2CB.038.00

2CJ.037.00

2CK.013.00

2CM.093.00

2CJ.039.00

2CK.017.00

2CA.033.01

2CM.040.00

2CA.033.04

2CB.053.00

2CJ.061.00

2CM.095.00

2CA.035.00

2CB.055.00

2CJ.062.00

2CN.004.00

2CA.037.00

2CE.001.00

2CJ.063.00

2CL.001.02

2CN.012.00

2CA.039.00

2CE.001.01

2CJ.064.00

2CL.002.01

2CO.011.00

2CA.041.00

2CE.003.00

2CJ.064.01

2CL.006.01

2CA.041.03

2CE.003.02

2CJ.065.00

2CL.007.00

2CP.001.00

2CA.041.04

2CE.003.03

2CJ.066.00

2CL.008.00

2CP.002.00

2CA.054.00

2CE.003.05

2CJ.066.01

2CL.009.00

2CP.003.00

2CA.055.00

2CE.003.07

2CE.003.08

2CL.010.00

2CS.001.00

2CA.056.00

2CI.001.00

2CJ.068.00

2CL.011.00

2CS.002.00

2CJ.069.00

2CL.012.00

2CJ.082.01

2CL.030.00

2CA.058.00 2CA.059.00

2CI.002.00

2CA.060.00

2CI.003.00

2CA.061.00

2CI.004.00

2CJ.083.00

2CL.033.00

2CA.074.00

2CI.005.00

2CJ.084.01

2CL.034.00

2CA.075.00

2CI.007.00

2CJ.085.00

2CL.036.00

2CL.032.00


2CT.017.00

2CT.034.00


ACCOUNT TYPE

2CA.076.00

2CI.009.00

2CJ.086.00

2CL.036.01

2CT.040.00

2CA.077.00

2CI.010.00

2CJ.086.01

2CL.001.01

2CT.040.01

2CA.078.00

2CI.010.01

2CJ.087.00

2CL.044.00

2CA.089.00

2CI.011.00

2CJ.095.00

2CL.045.00

2CA.092.00

2CI.013.00

2CJ.087.02

2CL.047.00

2CJ.177.00

2CM.041.00

2CP.004.00 st

Checks the ACs prior 1 GENAC & OFFLINE ONLY

2CJ.169.00

ADVICE

2CA.067.00

ADVICE & (BDC or ODC)

2CM.040.00

ADVICE & NO BDC & NO ODC

2CA.068.00

ADVICE & BDC

2CO.021.00

ADVICE & ODC & ONLINE CAPABLE

2CO.022.00

ADVICE & ONLINE CAPABLE

2CM.052.00

2CT.013.01

ADVICE & PIN

2CS.014.00

2CS.014.01

ADVICE & ENC PIN

2CS.014.02

2CS.014.03

Amount and PIN are entered on same keypad & Attended & PIN

2CM.141.00

Amount and PIN are entered on same keypad & Attended & ENC PIN

2CM.141.01

Amount and PIN are entered on same keypad & Attended & ENC PIN ONLINE

2CM.141.02

APPROVAL F & Attended

2CM.080.00

APPROVAL F & Attended & ONLINE CAPABLE

2CM.081.00

2CM.082.00

ATM

2CJ.041.00

2CJ.042.00

Attend

2CJ.100.02

2CM.102.00 2CO.002.00

BDC

2CM.105.00

BDC & OFFLINE CAPABLE

2CA.001.03


Page 1764

EMVCo Type Approval - Terminal Level 2 - Test Cases BDC & ONLINE CAPABLE

2CO.019.00

BYPASS & Attended & (PIN or ENC PIN or ENC PIN ONLINE)

2CM.022.00

CARD CONF

2CM.023.00

2CB.010.00

2CB.011.00

2CB.029.00

2CB.039.00

2CB.041.00

2CO.014.00

2CO.015.05

2CB.042.00

2CB.042.01

2CA.030.05

2CJ.047.00

2CJ.048.00

2CJ.100.05

2CM.064.00

CARD CONF & ICTIx

2CO.013.00

CARD CONF & PSE

2CB.019.01

2CB.019.04

CARD CONF & PSE & NO PREF ORDER

2CB.018.00

2CB.018.01

CASH

2CJ.045.00

2CJ.046.00

CASH & Attended

2CJ.070.01

2CJ.100.04

CASH & Unattended

2CJ.070.00

CASHBACK

2CJ.057.00

2CJ.059.00

2CJ.070.02

2CJ.058.00

2CJ.060.00

2CM.063.00 2CM.067.00

2CC.036.01

2CC.037.01

2CC.039.01

2CC.040.01

2CJ.027.01

2CC.041.01

2CC.042.01

2CC.144.02

2CC.133.01

2CJ.030.02

2CC.133.00

2CC.085.03

2CC.138.00

2CH.001.02

2CH.003.02

2CI.034.00

2CJ.012.03

2CJ.018.04

2CJ.025.02

2CJ.026.01

CDA

CDA & CDA Failure detected prior TAA

CDA & (Offline Only OR Offline/Online capable) & CDA failure not detected prior TAA

2CL.024.03

2CL.028.03

2CM.055.01 2CT.037.00

2CS.015.04

2CS.015.05

2CS.016.05

2CT.018.00

2CJ.002.04

2CT.018.01

2CC.014.02

2CC.043.01

2CC.044.01

2CC.045.01

2CC.046.01

2CC.047.01

2CC.050.01

2CC.052.01

2CC.053.01

2CC.054.01

2CC.055.01

2CC.056.01

2CC.057.01

2CC.061.01

2CC.063.01

2CC.064.01

2CC.065.01

2CC.066.01

2CC.067.01

2CC.068.01

2CC.069.01

2CC.085.01

2CJ.018.03

2CL.024.01

2CL.028.01

2CC.014.04

2CC.043.02

2CC.044.02

2CC.045.02

2CC.046.04

2CC.047.04

2CC.050.03

2CC.052.03

2CC.053.03

2CC.054.03

2CC.055.03

2CC.056.03

2CC.057.03

2CC.061.04

2CC.063.04

2CC.064.04

2CC.065.04

2CC.066.04

2CC.067.04

2CC.068.04

2CC.069.04

2CC.085.04

2CJ.018.05

2CL.024.04

2CL.028.04

2CC.059.01

2CC.059.03


EMVCo Type Approval - Terminal Level 2 - Test Cases CDA & Online Only & CDA request at GENAC1, ARQC & CDA failure not detected prior TAA

CDA & Online Only & CDA never at GENAC1, ARQC & Normal Default Action Code processing & CDA failure not detected prior TAA

CDA & Online Only & CDA request at GENAC1, ARQC & Normal Default Action Code processing & CDA failure not detected prior TAA

2CC..014.05 2CC.043.03

2CC.044.03

2CC.045.03

2CC.046.05

2CC.047.05

2CC.050.04

2CC.052.04

2CC.053.04

2CC.054.04

2CC.055.04

2CC.056.04

2CC.057.04

2CC.061.05

2CC.063.05

2CC.064.05

2CC.065.05

2CC.066.05

2CC.067.05

2CC.068.05

2CC.069.05

2CC.085.05

2CJ.018.06

2CL.024.05

2CL.028.05

2CC..014.07 2CC.043.05

2CC.044.05

2CC.045.05

2CC.046.07

2CC.047.07

2CC.050.06

2CC.052.06

2CC.053.06

2CC.054.06

2CC.055.06

2CC.056.06

2CC.057.06

2CC.061.06

2CC.063.07

2CC.064.07

2CC.065.07

2CC.066.07

2CC.067.07

2CC.068.07

2CC.069.07

2CC.085.07

2CJ.018.08

2CL.024.07

2CL.028.07

2CC..014.08 2CC.043.06

2CC.044.06

2CC.045.06

2CC.046.08

2CC.047.08

2CC.050.07

2CC.052.07

2CC.053.07

2CC.054.07

2CC.055.07

2CC.056.07

2CC.057.07

2CC.061.07

2CC.063.08

2CC.064.08

2CC.065.08

2CC.066.08

2CC.069.08

2CC.085.08

2CJ.018.09

2CC.059.04

2CC.059.06

2CC.059.07

2CC.067.08

2CC.068.08

2CL.024.08

2CL.028.08

2CC.014.06

2CC.043.04

2CC.044.04

2CC.045.04

2CC.046.06

2CC.047.06

2CC.050.05

2CC.052.05

2CC.053.05

2CC.054.05

2CC.055.05

2CC.056.05

2CC.057.05

2CC.061.06

2CC.063.06

2CC.064.06

2CC.065.06

2CC.066.06

2CC.067.06

2CC.068.06

2CC.069.06

2CC.085.06

2CJ.018.07

2CL.024.06

2CL.028.06

CDA & ENC PIN

2CT.010.00

2CT.010.01

CDA & (OFFLINE ONLY OR OFFLINE/ONLINE CAPABLE)

2CC.119.00

2CC.122.00

2CC.122.01

2CC.122.02

2CC.122.03

2CC.123.00

2CC.124.00

2CC.125.00

2CC.126.00

2CC.127.00

2CC.127.01

2CC.128.00

2CC.129.00

2CC.130.00

2CC.130.01

2CC.131.00

2CC.134.00

2CC.134.01

2CC.134.03

2CC.134.04

2CC.135.00

2CC.136.00

2CC.137.00

2CC.138.01

2CC.139.00

2CC.139.01

2CJ.021.00

2CJ.021.01

2CJ.021.02

2CJ.175.00

2CJ.203.00

2CJ.203.01

2CM.042.06 2CC.060.02

2CC.119.01

2CC.122.04

2CC.122.05

CDA & Online Only & CDA never at GENAC1, ARQC & CDA request at GENAC2, TC & CDA failure not detected prior TAA

CDA & Online Only & CDA request at GENAC1, ARQC

2CC.059.05

2CC.122.06


2CC.122.07

Page 1766

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CC.123.01

2CC.124.01

2CC.125.01

2CC.128.01

2CC.129.01

2CC.130.02

2CC.126.01

2CC.127.02

CDA & Online Only & CDA never at GENAC1, ARQC

2CC.122.08

CDA & (Online Only OR Offline/Online capable) & CDA never at GENAC1, ARQC

2CC.140.00

2CC.143.00

CDA & (Online Only OR Offline/Online capable) & CDA never at GENAC2, TC & CDA never at GENAC1, ARQC

2CC.142.00

2CC.133.02

CDA & Online Only & Normal Default Action Code processing

2CC.123.02

2CC.125.02

2CC.126.02

2CC.128.02

2CC.129.02

2CC.134.17

2CC.135.02

2CJ.021.05

2CJ.203.03

2CC.130.04

2CC.060.05 CDA & Online Only & CDA request at GENAC2, TC

2CC.123.03

2CC.125.03

2CC.126.03

2CC.128.03

2CC.129.03

2CC.130.03

2CC.134.11

2CC.134.12

2CC.134.13

2CC.134.16

2CC.135.01

2CJ.203.02

2CC.134.10

2CC.136.02

2CC.137.02

2CC.134.15

2CC.136.01

2CJ.021.04

2CJ.175.01

CDA & Online Only & CDA request GENAC1, ARQC & Normal Default Action Code processing

2CC.134.09 2CC.139.04

CDA & (Online Only OR Offline/Online capable) & CDA never GENAC1, ARQC & Normal Default Action Code processing

2CC.141.00

2CC.141.01

CDA & (Online Only OR Offline/Online capable) & CDA request GENAC1, ARQC & Normal Default Action Code processing 2CC.141.02

2CC.141.03

CDA & Online Only & CDA request at GENAC1, ARQC & CDA request at GENAC2, TC

2CC.134.05

2CC.134.05

2CC.137.01

2CC.139.03

2CJ.021.03

CDA & Online Only & (CDA request at GENAC1, ARQC OR CDA request at GENAC2, TC )

2CC.131.01

2CC.060.04

CDA & Online Only & CDA request at GENAC1, ARQC

2CC.134.07

2CC.134.08

2CC.139.02

2CM.042.08

CDA & Online Only

CVM_AMOUNT

2CC.134.14

2CC.138.02

2CJ.077.00

2CJ.078.00

2CJ.079.00

2CJ.080.00

2CJ.084.00

2CJ.077.01

2CJ.078.01

2CJ.079.01

2CJ.080.01

2CJ.087.01


EMVCo Type Approval - Terminal Level 2 - Test Cases 2CJ.077.02

2CJ.078.02

2CJ.079.02

2CJ.080.02

2CJ.095.01

2CC.060.01

2CC.080.00

2CJ.030.01

2CM.030.01 CVM_AMOUNT & (NO ENC PIN or NO SGN)

2CJ.092.03

CVM_AMOUNT & (NO PIN or NO SGN)

2CJ.090.03

CVM_AMOUNT & ENC PIN

2CJ.091.02

CVM_AMOUNT & ENC PIN ONLINE

2CJ.089.02

CVM_AMOUNT & NO CVM

2CJ.094.02

CVM_AMOUNT & NO ENC PIN

2CJ.091.03

CVM_AMOUNT & NO ENC PIN ONLINE

2CJ.089.03

CVM_AMOUNT & NO NO CVM

2CJ.094.03

CVM_AMOUNT & NO PIN

2CJ.088.03

CVM_AMOUNT & NO SGN

2CJ.093.03

CVM_AMOUNT & PIN

2CJ.088.02

CVM_AMOUNT & PIN & SGN

2CJ.090.02

CVM_AMOUNT & SGN

2CJ.093.02

D_TDOL

2CK.004.00

2CK.005.01

DDA

2CA.013.01

2CC.039.00

2CA.014.01

2CC.040.00

2CC.061.00

2CC.081.00

2CJ.033.00

2CA.015.01

2CC.041.00

2CC.063.00

2CC.082.00

2CL.024.00

2CA.016.01

2CC.042.00

2CC.064.00

2CC.083.00

2CL.024.02

2CA.017.01

2CC.043.00

2CC.065.00

2CC.085.00

2CL.028.00

2CA.018.01

2CC.044.00

2CC.066.00

2CC.085.02

2CL.028.02

2CA.019.01

2CC.045.00

2CC.067.00

2CC.086.00

2CL.035.00

2CA.020.01

2CC.046.00

2CC.068.00

2CH.001.01

2CM.055.00

2CA.021.01

2CC.047.00

2CC.069.00

2CH.003.01

2CL.060.00

2CA.031.00

2CC.050.00

2CC.071.00

2CI.015.00

2CS.003.00

2CA.031.01

2CC.052.00

2CC.072.00

2CI.025.00

2CS.015.02

2CA.082.00

2CC.053.00

2CC.074.00

2CJ.012.02

2CS.015.03

2CA.083.00

2CC.054.00

2CC.075.00

2CJ.018.01

2CS.016.03

2CA.084.00

2CC.055.00

2CC.076.00

2CJ.018.02

2CT.036.00

2CC.014.01

2CC.056.00

2CL.061.00

2CJ.025.01

2CT.019.00


Page 1768

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CC.036.00

2CC.057.00

2CC.078.00

2CJ.026.00

2CT.039.00

2CC.037.00

2CC.059.00

2CC.079.00

2CJ.027.00

2CJ.002.03

2CC.144.01

DDA & ONLINE CAPABLE

2CT.019.01

DDA & ENC PIN

2CT.009.00

2CT.009.01

DISPLAY

2CM.062.00

2CM.103.00 2CO.001.00

2CO.002.00

DISPLAY AND Code Table

2CO.003.00

ENC PIN

2CA.028.00

2CC.060.03

2CC.068.03

2CH.001.03

2CA.034.06

2CC.061.02

2CC.069.02

2CH.001.04

2CA.034.05

2CC.046.02

2CC.061.03

2CC.069.03

2CH.003.03

2CA.036.00

2CC.046.03

2CC.063.02

2CC.091.00

2CH.003.04

2CA.040.00

2CC.047.02

2CC.063.03

2CC.094.00

2CJ.073.01

2CA.041.02

2CC.047.03

2CC.064.02

2CC.095.00

2CJ.091.00

2CA.103.01

2CC.050.02

2CC.064.03

2CC.095.01

2CJ.107.01

2CA.108.00

2CC.052.02

2CC.065.02

2CC.096.00

2CJ.108.01

2CC.014.03

2CC.053.02

2CC.065.03

2CC.097.00

2CJ.115.02

2CC.036.02

2CC.054.02

2CC.066.02

2CC.098.00

2CM.018.01

2CC.039.02

2CC.055.02

2CC.066.03

2CC.099.00

2CM.129.01

2CC.040.02

2CC.056.02

2CC.067.02

2CC.100.00

2CM.130.01

2CC.041.02

2CC.057.02

2CC.067.03

2CC.100.01

2CC.059.02

2CC.068.02

2CC.102.00

2CJ.096.00

2CM.028.03 2CL.028.07

ENC PIN & Attended

2CM.140.01

ENC PIN & SGN

2CJ.092.00

2CJ.092.02

2CJ.114.01

2CJ.074.00

2CJ.089.00

2CJ.112.00

2CM.137.00

2CJ.096.01

2CM.028.02 2CJ.002.07

ENC PIN ONLINE

ENC PIN ONLINE & Attended

2CM.140.02

EXCEPT

2CM.031.00

2CM.032.00 2CJ.002.02

GDPTC & ENC PIN

2CA.029.07

2CA.072.01

2CI.017.01

2CM.129.02 2CM.130.02

2CM.013.01 2CM.016.01

2CA.029.11 GDPTC & ENC PIN ONLINE & (PIN or ENC PIN)

2CS.005.00

2CM.020.00


EMVCo Type Approval - Terminal Level 2 - Test Cases GDPTC & PIN

2CA.029.06

2CA.072.00

2CI.017.00

2CM.013.00 2CM.016.00

2CJ.049.00

2CJ.050.00

2CJ.051.00

2CJ.052.00

2CJ.053.00

2CJ.054.00

2CJ.055.00

2CJ.056.00

2CA.025.03

2CM.074.00 2CM.075.00 2CM.076.00 2CM.077.00

2CA.029.10

GOODS or SERVICES

IREFER & ONLINE CAPABLE

2CJ.071.00

2CM.078.00

IREFER & ONLINE CAPABLE

2CO.028.01

LOG & TRM (FL)

2CJ.119.00

2CJ.120.00

MagStripe

2CM.091.00

2CM.109.00

MSC & MS FIRST

2CM.087.00

2CO.037.00

MSS

2CM.086.00

MULT_LANG & DISPLAY

2CO.005.00

NO ADVICE

2CA.069.00

NO CARD CONF

2CB.010.01

2CB.040.00

2CB.011.01

2CA.030.06

NO CARD CONF & PSE

2CB.019.02

2CB.019.05

NO CVM

2CJ.094.00

2CM.009.00 2CJ.096.02

NO D_TDOL

2CK.005.00

NO ENC PIN

2CJ.083.02

2CJ.083.06

2CJ.091.01

NO ENC PIN ONLINE

2CJ.083.03

2CJ.089.01

2CJ.109.00

no NO CVM

2CJ.083.07

2CJ.094.01

2CM.009.05 2CM.030.00

NO PIN

2CJ.083.01

2CJ.083.05

2CJ.088.01

NO PIN & ENC PIN

2CJ.103.01

NO PIN & NO ENC PIN

2CJ.103.00

NO PIN OR NO ENC PIN

2CJ.002.06

2CO.038.00

2CO.006.00

2CB.049.00

2CB.050.00

2CO.016.00

2CJ.092.01

2CJ.090.01


Page 1770

EMVCo Type Approval - Terminal Level 2 - Test Cases NO SDA & NO DDA & NO CDA

2CJ.024.00

NO SDA & ONLINE ONLY

2CM.004.00

NO SGN

2CJ.083.04

2CJ.083.05

2CJ.093.01

2CM.030.02

2CJ.083.06

2CJ.090.01

2CO.032.00

2CJ.092.01

st

Checks the ACs prior 1 GENAC not supported & OFFLINE ONLY

2CJ.169.02

st

[Default Action Codes prior to the 1 GENERATE AC processing] NOT supported

2CO.026.00

NO_GDPTC & ENC PIN ONLINE & (PIN or ENC PIN)

2CM.020.01

not ATM

2CJ.043.00

2CJ.044.00

ODC & ONLINE CAPABLE

2CM.044.00

2CO.020.00

2CO.023.00

ODC & (Offline/Online capable OR (Online Only & Normal Default Action Code processing))

2CO.033.00

OFFLINE ONLY or OFFLINE/ONLINE CAPABLE

2CA.062.00

2CJ.159.00

2CM.033.00 2CL.058.00

2CK.007.00

2CJ.151.00

2CK.012.00

2CM.106.00

2CM.042.07

2CK.013.00

OFFLINE ONLY

2CK.018.01

2CM.056.00 2CT.023.01

2CT.028.01

2CJ.167.01

2CM.058.00 2CT.024.01

2CT.029.01

2CM.036.00

2CT.020.01

2CT.025.01

2CT.030.01

2CT.021.01

2CT.026.01

2CT.031.01

2CT.022.01

2CT.027.01

2CT.032.01

2CT.033.01

st

OFFLINE ONLY & Checks the ACs prior 1 GENAC

2CJ.156.00

2CJ.157.00

2CJ.164.00

2CJ.165.00

[Offline/Online capable] OR [Online Only AND Normal Default Action processing]

2CJ.155.00

2CJ.168.00

2CJ.168.01

2CJ.162.00

2CO.030.00

2CJ.163.00 [Offline Only or Offline/Online capable] OR [Online Only AND Normal Default Action processing]

2CO.025.00

Offline/Online capable

2CM.057.00

2CJ.166.01

2CM.059.00 2CJ.161.00

2CJ.167.01

2CM.036.00

2CJ.167.00

2CJ.152.00

2CJ.166.00

ONE_LANG & DISPLAY

2CJ.153.00

2CO.008.00



ONLINE ONLY or OFFLINE/ONLINE CAPABLE

2CM.042.01 2CJ.195.00

2CM.045.02 2CT.012.01

2CA.025.00

2CJ.178.00

2CJ.195.01

2CM.048.00 2CT.013.00

2CA.025.01

2CJ.180.00

2CJ.195.02

2CK.013.00

2CA.025.02

2CJ.182.00

2CJ.195.03

2CO.028.00

2CJ.181.01

2CJ.183.00

2CJ.197.00

2CO.031.00

2CT.017.01

2CT.020.00

2CA.026.00

2CJ.187.00

2CJ.197.01

2CO.034.00

2CT.021.00

2CA.062.01

2CJ.187.01

2CJ.197.02

2CJ.002.08

2CT.022.00

2CA.063.00

2CJ.187.02

2CJ.199.00

2CO.035.00

2CT.023.00

2CI.031.00

2CJ.188.00

2CJ.200.00

2CO.035.01

2CT.024.00

2CJ.151.01

2CJ.188.01

2CJ.200.01

2CO.035.02

2CT.025.00

2CL.059.00

2CJ.188.02

2CJ.202.00

2CO.036.00

2CT.026.00

2CJ.189.00

2CK.006.00

2CO.036.01

2CT.027.00

2CJ.190.00

2CK.008.00

2CO.036.02

2CT.028.00

2CJ.202.01

2CK.010.00

2CS.007.00

2CT.029.00

2CJ.159.01

2CK.017.00

2CK.015.00

2CK.018.00

2CT.030.00

2CJ.160.00

2CJ.192.00

2CK.016.00

2CT.011.00

2CT.031.00

2CJ.192.01

2CM.035.00 2CT.011.01

2CT.032.00

2CJ.193.00

2CM.038.00 2CT.011.02

2CT.033.00

2CJ.193.01

2CM.043.00 2CT.011.03

2CJ.193.02

2CM.045.00 2CT.011.04

2CJ.194.00

2CM.045.01 2CT.012.00

NO CDA & (OFFLINE ONLY or OFFLINE/ONLINE CAPABLE)

2CL.056.00

NO CDA & (ONLINE ONLY or OFFLINE/ONLINE CAPABLE)

2CL.057.00

ONLINE F & Attended

2CM.079.00

Online Only

2CJ.160.01

2CJ.002.12

[Online Only] supported AND [Skip Default Action Code processing] 2CJ.157.01 [Online Only or Offline/Online capable] supported AND [Issuer Script device limit => 128 bytes]

2CO.034.02

Offline/Online capable OR [Online Only & Normal Default Action Cdoe Processing] OR [ Offline Only & Process Default Action st Codes after 1 GENERATE AC]

2CJ.154.00

PIN

2CA.034.02

2CA.041.01

2CA.034.07

2CA.103.00

2CJ.107.00

2CM.018.00 2CS.004.00

2CA.040.00

2CJ.073.00

2CJ.108.00

2CM.129.00 2CJ.096.00

2CO.034.03

2CJ.088.00

2CJ.115.00


2CM.130.00

Page 1772

EMVCo Type Approval - Terminal Level 2 - Test Cases 2CM.028.01

PIN & Attended

2CM.140.00

PIN & NO ENC PIN

2CJ.103.02

PIN OR ENC PIN

2CJ.002.05

PIN & SGN

2CJ.090.00

2CJ.114.00

PRINT

2CM.107.00

2CO.017.00

2CO.018.00

PSE

2CA.004.00

2CA.096.00

2CB.013.00

2CE.003.01

2CL.005.00

2CA.004.01

2CA.099.01

2CB.016.00

2CE.003.04

2CL.005.01

2CB.023.01

2CA.099.02

2CB.016.01

2CE.003.06

2CL.006.00

2CB.023.02

2CA.100.01

2CB.017.00

2CL.001.00

2CL.029.00

2CA.033.02

2CA.100.02

2CB.017.01

2CL.002.00

2CL.029.01

2CB.022.00

2CB.002.00

2CB.017.02

2CL.003.00

2CL.029.05

2CA.093.00

2CB.004.00

2CB.021.00

2CL.003.05

2CL.037.00

2CA.094.00

2CB.005.00

2CB.023.00

2CL.004.00

2CL.037.01

2CA.095.00

2CB.012.00

2CB.054.00

2CL.004.01

REVOC & CDA & CDA failure detected prior TAA

2CC.058.01

REVOC & CDA & CDA failure not detected prior TAA & (Offline Only OR Online/offline Capable)

2CC.058.03

REVOC & CDA & CDA failure not detected prior TAA & Online Only & CDA request at GENAC1, ARQC

2CC.058.10

REVOC & CDA & Online Only & CDA never at GENAC1, ARQC & Normal Default Action Code processing & CDA failure not detected prior TAA

2CC.058.12

REVOC & CDA & Online Only & CDA request at GENAC1, ARQC & Normal Default Action Code processing & CDA failure not detected prior TAA

2CC.058.13

REVOC & CDA & CDA failure not detected prior TAA & Online Only & CDA never at GENAC1, ARQC & CDA request at GENAC2, TC

2CC.058.11

REVOC & CDA

2CC.058.06

2CC.058.07

REVOC & DDA

2CC.058.00

2CC.058.04

2CC.058.05



REVOC & ENC PIN

2CC.058.02

2CC.058.08

2CC.058.09

REVOC & SDA

2CC.023.00

2CC.023.01

2CC.023.02

SDA

2CC.003.00

2CC.015.00

2CC.029.00

2CI.023.00

2CL.019.00

2CC.004.00

2CC.017.00

2CC.030.00

2CJ.012.01

2CL.021.00

2CC.006.00

2CC.018.00

2CC.031.00

2CJ.018.00

2CL.023.00

2CC.007.00

2CC.019.00

2CC.032.00

2CJ.019.00

2CL.023.01

2CC.008.00

2CC.020.00

2CC.032.01

2CJ.020.00

2CM.092.00

2CC.009.00

2CC.021.00

2CC.033.00

2CJ.025.00

2CJ.002.01

2CC.010.00

2CC.022.00

2CC.060.00

2CJ.028.00

2CS.015.00

2CC.011.00

2CC.024.00

2CH.001.00

2CJ.029.00

2CS.015.01

2CC.012.00

2CC.026.00

2CH.003.00

2CJ.030.00

2CS.016.00

2CC.014.00

2CC.028.00

2CI.014.00

2CJ.032.00

2CT.035.00

2CJ.024.03

2CC.144.00

SDA & DDA & CDA

2CJ.022.02

2CJ.023.01

SDA & DDA & NO CDA

2CJ.022.01

2CJ.023.00

SDA & NO DDA & NO CDA

2CJ.022.00

2CJ.024.01

(SDA OR DDA OR CDA OR ENC PIN) and CAPK supported

2CN.016.00

SDA & ENC PIN

2CT.008.00

SGN

2CJ.075.00

2CJ.093.00

2CJ.113.00

2CM.025.00 2CJ.096.01

Floor Limit

2CJ.123.00

2CJ.127.00

2CJ.148.00

2CJ.002.09

2CJ.124.00

2CJ.128.00

2CI.028.00

FLoor LImit & Velocity Checking

2CJ.116.00

Random Transaction Selection

2CI.028.00

2CJ.081.02

2CJ.081.04

2CJ.081.01

2CJ.081.03

2CJ.148.00

2CA.029.05

2CJ.137.00

2CJ.140.01

Velocity Checking

2CJ.002.11

2CJ.143.00

2CJ.147.01

2CA.070.00

2CJ.138.00

2CJ.140.02

2CJ.144.00

2CJ.148.00

2CA.071.00

2CJ.138.01

2CJ.140.03

2CJ.145.00

2CL.013.00

2CI.020.00

2CJ.139.00

2CJ.141.00

2CJ.146.00

2CL.014.00

2CI.028.00

2CJ.140.00

2CJ.142.00

2CJ.147.00

2CS.006.00

2CA.029.08

2CA.029.09

2CT.038.00

2CT.038.01

2CJ.140.04

2CJ.002.10

TT1x & (FLoor Limit OR Velocity Checking

2CM.060.00


Page 1774

EMVCo Type Approval - Terminal Level 2 - Test Cases OR Random Transaction Selection OR Exception File OR Transaction Log)

TT2x

2CM.001.00

(Offline Only OR Offline/Online capable) & Internal Date Mangement

2CM.094.00

Online Only & NO Internal Date Mangement

2CM.094.01

PIN Bypass & Attended Terminal & ((Offline Plaintext PIN & Offline Enciphered PIN) OR (Offline Plaintext PIN & Online Enciphered PIN) OR (Offline Enciphered PIN & Online Enciphered PIN)) & NO Subsequent PIN Bypass

2CM.024.01

(Subsequent PIN Bypass & PIN Bypass & Attended Terminal) & ((Offline Plaintext PIN & Offline Enciphered PIN) OR (Offline Plaintext PIN & Online Enciphered PIN) OR (Offline Enciphered PIN & Online Enciphered PIN))

2CM.024.00

2CM.002.00 2CM.061.00

< End Of The Document>


L2 Test Cases v41e

Recommend Documents