Terminal Type Approval

EMV® Terminal Type Approval

Book A & B

Test Cases

Version 2.6a February 2017

Legal Notice

The EMV® Specifications are provided “AS IS” without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in these Specifications. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON- INFRINGEMENT, AS TO THESE SPECIFICATIONS.

EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to the Specifications. EMVCo undertakes no responsibility to determine whether any implementation of the EMV® Specifications may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of the EMV® Specifications should consult an intellectual property attorney before any such implementation.

Without limiting the foregoing, the Specifications may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement these Specifications is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for any party’s infringement of any intellectual property rights in connection with the EMV® Specifications.

Version History

Version Date Revision Description 2.1 June 24, 2011 First version 2.2a November, 2012 Correction of Kernel ID, Data settings, Adding Tests for Contactless Symbol Checking and for UN testing Test Cases pass criteria updated: 2EC.001 .02, 2EC.001.03 2EC.001.04 Test Case 2eb.014.00, case 02 and 04 , LTsetting updated Update following SB112 bulletin 2ED.012.08 added with new [Termsetting13] and [Ltsetting1.93], [Ltsetting1.94], [Ltsetting1.95], [Ltsetting1.96] 2ED.019.00 updated : case 03 added with new [Ltsetting6.17] 2EF.003.00 updated: case 03 added with new [Ltsetting2.41] 2.3a November 2013 • Support of version 2.3 of the specification • Delete test 2ED.006.00; 2ED.006.01 and update 2ED.007.00 to cover wrong AID on 4 bytes • Add Kernel C-5 • Autorun Parameter is defined as optional • Add Test Kernel TK5 in Termsettings and review the test cases to add subcases using this TK5 (2EA.001.00 2EA.006.02 2EA.014.00 2EB.001.00 2EB.003.00 2EB.004.01 2EB.005.00 2EB.006.00 2EB.007.00 2EB.008.00 2EB.009.01 2EB.010.00 2EB.012.00 2EB.013.00 2EB.014.00 2EB.015.00 2EB.016.02 2EB.017.00 2EB.018.00 2EC.001.00 2ED.001.01 2ED.009.04 2ED.009.05 2ED.009.14 2ED.009.15 2ED.011.00 2ED.012.04 2ED.012.05 2ED.012.10 2ED.013.00 2ED.014.00 2ED.015.00 2ED.018.00 2ED.019.00 2EE.002.00 2EF.003.00)

• Clarification on kernel ID , amount, and limit coding in section 9.3

• LTSetting 1.23 and 1.29 in the detailed definition to state online data is ‘ANY’ for test 2EA.016.00

• TermSetting10 correction

o Ltsetting1.15], [Ltsetting1.24] : UI Request on Restart Present: No

• Ltsetting1.43],:hold time=10s added

• Test Case 2EB.007.00: pass criteria on subcase 2 updated

• Test Case 2EB.015.00: [Ltsetting1.97] is replaced by [Ltsetting1.100]

• Test Case 2ED.013.00: editorial update

2.4a November 2014 • Support of version 2.4 of the specification • Kernel ID and AID management change • Introduction of C-6 and C-7 2.5a November 2015 • Support of version 2.5 of the specification

2.6a November 2016 • Review consistency Kernel ID, Kernel Identifier between Test Plan and EMVCo book B specifications • Annex B and section 7.1.3: Create a new proprietary tag ‘D7’ for Kernel ID in Test Kernel (different from Kernel Identifier in PPSE select response) • Annex C and sections 9.6 and 9.5: replace in all Ltsettings which contains tag ‘9F2A’ in PDOL for Kernel ID by tag ‘D7’, it impacts all tests 2ED.xxx.xx where Kernel ID value is checked in pass criteria • Delete of ‘Restart A’ related subcases

Versioning policy of the present document: Current version is 2.6a follows the current Entry Point Specification revision number, and where .a is incremented (a, b, c, …) for each new revision of the present document issued to correct any issues, or to incorporate Type Approval Bulletins.

Table of Contents

1. SCOPE ...... 11 2. REFERENCED DOCUMENTS ...... 12 3. ABBREVIATIONS AND NOTATIONS ...... 13 4. GLOBAL GLOSSARY ...... 14 5. DOCUMENT OVERVIEW ...... 15 6. TERMINAL TEST ENVIRONMENT ...... 16 6.1. TEST KERNEL DEFINITION ...... 16 6.2. TEST PAYMENT APPLICATION ...... 24 6.3. TEST KERNEL ID DEFINITION ...... 24 6.4. TERMINAL DATA CONFIGURATIONS (‘TERMSETTING’) ...... 25 7. LT (CARD) TEST ENVIRONMENT ...... 28 7.1. LT TEST KERNEL FOR TEST KERNEL ...... 28 7.2. LT TEST KERNELS FOR KERNEL C-1 TO C-7 ...... 31 7.3. LT (CARD) DATA CONFIGURATION (LTSETTING) ...... 33 8. TEST STRUCTURE ...... 34 8.1. TEST NUMBERING AND ASSOCIATED SUB CASES ...... 34 8.2. TEST CATEGORY ...... 34 8.3. TEST CASE FORMAT ...... 35 9. TEST CASES ...... 37 9.1. GENERAL REQUIREMENTS ...... 37 2EA.001.00 Entry of Amount Authorized ...... 38 2EA.002.00 Entry of Amount Authorized and Transaction Type ‘Purchase’ ...... 40 2EA.002.01 Entry of Amount Authorized and Transaction Type ‘Cash Advance’ ...... 41 2EA.002.02 Entry of Amount Authorized and Transaction Type ‘Refund’ ...... 42 2EA.003.00 Entry of Amount Authorized, Amount Other ...... 43 2EA.004.00 Restart flag cleared at new transaction ...... 44 2EA.005.00 Field off at new transaction (Autorun = ’No’) ...... 45 2EA.005.01 Reader status Idle at new transaction (Autorun = ’No’) ...... 46 2EA.006.00 Field on at new transaction (Autorun = ’Yes’) ...... 47 2EA.006.01 Reader status Ready to Read at new transaction (Autorun = ’Yes’) ...... 48 2EA.006.02 Terminal EMV Data available for Kernel for a Purchase transaction ...... 49 2EA.006.03 Terminal EMV Data available for Kernel for a Purchase with Cashback transaction ..... 51 2EA.006.04 Terminal EMV Data available for Kernel for a Cash Advance transaction ...... 53 2EA.006.05 Terminal EMV Data available for Kernel for a Refund transaction ...... 55 2EA.007.00 Unpredictable Number different at each transaction ...... 57 2EA.010.00 Contactless interface powered down when contact interface activated ...... 59 2EA.010.01 Contactless interface powered down during a contact transaction ...... 60 2EA.011.00 User Interface Request Hold Time ...... 61 2EA.012.00 User Interface Request using Language Preference ...... 62 2EA.012.01 User Interface Request using Default Language ...... 64 2EA.013.00 User Interface Request Amount or Balance displayed ...... 66

2EA.013.01 User Interface Request Amount or Balance displayed (2) ...... 68 2EA.014.00 Restart after an Outcome (Response with EMV data) ...... 69 2EA.014.01 Restart after an Outcome (card removed) ...... 73 2EA.015.00 Removal Timeout set and timeout occurs ...... 75 2EA.016.00 Restart after an Outcome (Online Response Data parameter set to ANY) ...... 76 2EA.017.00 RFU bytes and bits ...... 79 2EA.017.01 RFU bytes and bits (2) ...... 81 2EA.018.00 Presence of Data ignored ...... 82 2EA.019.00 Receipt ...... 84 2EA.020.00 Padding ...... 85 2EA.021.00 Order of Data Elements ...... 87 2EA.022.00 EMVCO Contactless Symbol Compliance ...... 88 9.2. PRE-PROCESSING ...... 92 2EB.001.00 All Pre-Processing indicators set to zero at beginning of Pre-Processing ...... 93 2EB.002.00 Terminal Transaction Qualifier set in Entry Point configuration copied during Pre- Processing ...... 95 2EB.003.00 Status Check present and set, Amount = 1 ...... 97 2EB.003.01 Status Check present and set, Amount = 1 and Transaction Type ‘Purchase’ ...... 99 2EB.003.02 Status Check present and set, Amount = 1 and Transaction Type ‘Refund’ ...... 100 2EB.004.00 Status Check present and not set ...... 101 2EB.004.01 Status Check present and not set with Transaction Type ‘Purchase’ ...... 102 2EB.004.02 Status Check present and not set with Transaction Type ‘Cash Advance’ ...... 103 2EB.005.00 Status Check not present ...... 104 2EB.005.01 Status Check not present and Transaction Type ’Purchase’ ...... 105 2EB.006.00 Status Check present and set, Amount different from 1 ...... 106 2EB.006.01 Status Check present and set, Amount different from 1 with Transaction Type ‘Purchase’ ...... 108 2EB.007.00 Zero Amount not allowed ...... 109 2EB.007.01 Zero Amount not allowed with Transaction Type ‘Purchase’ ...... 110 2EB.008.00 Zero Amount allowed ...... 111 2EB.008.01 Zero Amount allowed with Transaction Type ‘Purchase’ ...... 112 2EB.008.02 Zero Amount allowed with Transaction Type ‘Refund’ ...... 113 2EB.009.00 Zero Amount allowed flag not present ...... 114 2EB.009.01 Zero Amount allowed flag not present with Transaction Type ‘Purchase’ ...... 115 2EB.009.02 Zero Amount allowed flag not present with Transaction Type ‘Cash Advance’ ...... 117 2EB.010.00 Reader Contactless Transaction Limit exceeded ...... 118 2EB.010.01 Reader Contactless Transaction Limit exceeded with Transaction Type ‘Purchase’ ...... 119 2EB.011.00 Reader Contactless Transaction Limit not exceeded ...... 120 2EB.011.01 Reader Contactless Transaction Limit not exceeded with Transaction Type ‘Refund’ ..... 121 2EB.011.02 Reader Contactless Transaction Limit not exceeded with Transaction Type ‘Purchase with Cashback’ ...... 122 2EB.012.00 Reader Contactless Transaction Limit not present ...... 123 2EB.012.01 Reader Contactless Transaction Limit not present ...... 124 2EB.013.00 Reader Contactless Floor Limit present, Amount Authorized greater than limit ...... 125 2EB.013.01 Reader Contactless Floor Limit present, Amount Authorized greater than limit with Transaction Type ‘Purchase’ ...... 127 2EB.013.02 Reader Contactless Floor Limit present, Amount Authorized greater than limit with Transaction Type ‘Refund’ ...... 128 2EB.014.00 Reader Contactless Floor Limit present, Amount Authorized less than limit ...... 129 2EB.014.01 Reader Contactless Floor Limit present, Amount Authorized less than limit with Transaction Type ‘Purchase’ ...... 131 2EB.014.02 Reader Contactless Floor Limit present, Amount Authorized less than limit with Transaction Type ‘Refund’ ...... 132

2EB.015.00 Reader Contactless Floor Limit not present, Terminal Floor Limit present ...... 133 2EB.015.01 Reader Contactless Floor Limit not present, Terminal Floor Limit present with Transaction type ‘Purchase’ ...... 135 2EB.015.02 Reader Contactless Floor Limit not present, Terminal Floor Limit present with Transaction type ‘Purchase with Cashback’ ...... 137 2EB.016.00 Reader Contactless Floor Limit and Terminal Floor Limit not present ...... 139 2EB.016.01 Reader Contactless Floor Limit and Terminal Floor Limit not present with Transaction Type ‘Purchase’ ...... 140 2EB.016.02 Reader Contactless Floor Limit and Terminal Floor Limit not present with Transaction Type ‘Cash Advance’ ...... 141 2EB.017.00 Reader CVM Required Limit present, Amount Authorized greater or equal to limit ...... 142 2EB.017.01 Reader CVM Required Limit present, Amount Authorized greater than limit with Transaction Type ‘Purchase’ ...... 144 2EB.017.02 Reader CVM Required Limit present, Amount Authorized greater than limit with Transaction Type ‘Cash Advance’ ...... 145 2EB.018.00 Reader CVM Required Limit present, Amount Authorized less than limit ...... 146 2EB.018.01 Reader CVM Required Limit present, Amount Authorized less than limit with Transaction Type ‘Purchase’ ...... 147 2EB.018.02 Reader CVM Required Limit present, Amount Authorized less than limit with Transaction Type ‘Refund’ ...... 148 2EB.019.00 Reader CVM Required Limit not present ...... 149 2EB.019.01 Reader CVM Required Limit not present with Transaction Type ‘Purchase’ ...... 150 2EB.019.02 Reader CVM Required Limit not present with Transaction Type ‘Refund’ ...... 151 2EB.020.00 Zero Amount indicator set with TTQ (online capable reader) ...... 152 2EB.020.01 Zero Amount indicator set with TTQ (online capable reader) with Transaction Type ‘Purchase’ ...... 153 2EB.021.00 Zero Amount indicator set with TTQ (offline only reader) ...... 154 2EB.022.00 Contactless Application Not Allowed for all combinations after Pre-Processing ...... 155 9.3. PROTOCOL ACTIVATION ...... 156 2EC.001.00 All Pre-Processing indicators set to zero when Pre-Processing not performed ...... 157 2EC.001.01 All Pre-Processing indicators set to zero when Pre-Processing not performed with Transaction Type ‘Purchase’ ...... 159 2EC.001.02 All Pre-Processing indicators set to zero when Pre-Processing not performed with Transaction Type ‘Purchase with Cashback’ ...... 160 2EC.001.03 All Pre-Processing indicators set to zero when Pre-Processing not performed with Transaction Type ‘Cash Advance’ ...... 161 2EC.001.04 All Pre-Processing indicators set to zero when Pre-Processing not performed with Transaction Type ‘Refund’ ...... 162 2EC.002.00 Restart flag set and UI Request on Restart present ...... 163 2EC.003.00 Restart flag set and UI Request on Restart not present ...... 164 2EC.004.00 Restart flag not set , Message ‘PRESENT CARD’ ...... 165 2EC.005.00 Field powered and polling ...... 166 2EC.006.00 Protocol Activation Collision ...... 167 2EC.007.00 Protocol Activation Collision ...... 168 9.4. AID AND KERNEL SELECTION ...... 169 2ED.001.00 Entry point Activation at Start B with Issuer Authentication Data or Issuer Script present ...... 170 2ED.001.01 Entry point Activation at Start B with Issuer Authentication Data or Issuer Script present with Extended Selection ...... 173 2ED.002.00 Entry point Activation at Start C (Restart) ...... 176 2ED.002.01 Entry point Activation at Start C (Restart) with Extended Selection ...... 177 2ED.003.00 PPSE selection ...... 178 2ED.003.01 PPSE with additional data ...... 179

2ED.003.02 ASRPD Data support ...... 181 2ED.004.00 PPSE selection rejected ...... 185 2ED.005.00 PPSE select response without Directory Entry ...... 186 2ED.007.00 PPSE select response with a Directory Entry wrongly coded on ADF name and another correctly coded ...... 187 2ED.007.01 PPSE select response with a Directory Entry with ADF name missing and another correctly coded ...... 188 2ED.008.00 PPSE select response having a Directory Entry with AID not matching ...... 189 2ED.009.00 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = Visa AID, TK3 Kernel ID = ’03’) ...... 190 2ED.009.01 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = Visa AID, TK3 Kernel ID not equal to ’03’ ) ...... 191 2ED.009.02 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = MasterCard AID, TK2 Kernel ID = ’02’) ...... 192 2ED.009.03 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = MasterCard AID, TK2 Kernel ID not equal to ’02’) ...... 193 2ED.009.04 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = JCB AID, TK1 Kernel ID = ’05’) ...... 194 2ED.009.05 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = JCB AID, TK1 Kernel ID not equal to ’05’) ...... 195 2ED.009.06 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = AMEX AID, TK4 Kernel ID = ’04’) ...... 196 2ED.009.07 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = AMEX AID, TK4 Kernel ID not equal to ’04’) ...... 197 2ED.009.10 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = Visa AID, TK3 Kernel ID = ’03’) ...... 198 2ED.009.11 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = Visa AID, TK3 Kernel ID not equal to ’03’) ...... 199 2ED.009.12 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = MasterCard AID, TK2 Kernel ID = ’02’) ...... 200 2ED.009.13 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = MasterCard AID, TK2 Kernel ID not equal to ’02’) ...... 201 2ED.009.14 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = JCB AID, TK1 Kernel ID = ’05’) ...... 202 2ED.009.15 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = JCB AID, TK1 Kernel ID not equal to ’05’) ...... 203 2ED.009.16 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = AMEX AID, TK4 Kernel ID = ’04’) ...... 204 2ED.009.17 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = AMEX AID, TK4 Kernel ID not equal to ’04’) ...... 205 2ED.009.18 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = DISCOVER AID, TK6 Kernel ID = ’06’) ...... 206 2ED.009.19 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = DISCOVER AID, TK6 Kernel ID not equal to ’06’ ) ...... 207 2ED.009.20 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = DISCOVER AID, TK6 Kernel ID = ’06’) ...... 208 2ED.009.21 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = DISCOVER AID, TK6 Kernel ID not equal to ’06’) ...... 209 2ED.009.22 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = CUP AID, TK7 Kernel ID = ’07’) ...... 210 2ED.009.23 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = CUP AID, TK7 Kernel ID not equal to ’07’ ) ...... 211

2ED.009.24 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = CUP AID, TK7 Kernel ID = ’07’) ...... 212 2ED.009.25 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = CUP AID, TK7 Kernel ID not equal to ’07’) ...... 213 2ED.009.26 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = DISCOVER AID, TK6 Kernel ID = ’06’) ...... 214 2ED.009.27 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = DISCOVER AID, TK6 Kernel ID not equal to ’06’ ) ...... 215 2ED.009.28 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = DISCOVER AID, TK6 Kernel ID = ’06’) ...... 216 2ED.009.29 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = DISCOVER AID, TK6 Kernel ID not equal to ’06’) ...... 217 2ED.010.00 PPSE select response having a Directory Entry with Kernel Identifier wrong length ...... 218 2ED.011.00 PPSE select response having a Directory Entry with Kernel Identifier not matching ...... 219 2ED.012.00 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = Visa AID, TK3 Kernel ID = ’03’) ...... 221 2ED.012.01 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = Visa AID, TK3 Kernel ID not equal to ’03’) ...... 222 2ED.012.02 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = MasterCard AID, TK2 Kernel ID = ’02’) ...... 223 2ED.012.03 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = MasterCard AID, TK2 Kernel ID not equal to ’02’) ...... 224 2ED.012.04 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = JCB AID, TK5 Kernel ID = ’05’) ...... 225 2ED.012.05 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = JCB AID, TK5 Kernel ID not equal to ’05’) ...... 226 2ED.012.06 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = AMEX AID, TK4 Kernel ID = ’04’) ...... 227 2ED.012.07 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = AMEX AID, TK4 Kernel ID not equal to ’04’) ...... 228 2ED.012.08 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID, Kernel ID = domestic Kernel) ...... 229 2ED.012.10 Matching combination with International or Domestic Kernel ID ...... 231 2ED.012.11 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = DISCOVER AID, TK6 Kernel ID = ’06’) ...... 234 2ED.012.12 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = DISCOVER AID, TK6 Kernel ID not equal to ’06’) ...... 235 2ED.012.13 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = CUP AID, TK7 Kernel ID = ’07’) ...... 236 2ED.012.14 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = CUP AID, TK7 Kernel ID not equal to ’07’) ...... 237 2ED.012.15 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = DISCOVER AID, TK6 Kernel ID = ’06’) ...... 238 2ED.012.16 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = DISCOVER AID, TK6 Kernel ID not equal to ’06’) ...... 239 2ED.013.00 PPSE select response having each Directory Entry with different priority set ...... 240 2ED.014.00 PPSE select response having several Directory Entries with same highest priority set ... 243 2ED.015.00 PPSE select response having Directory Entries with priority=’00’ or no priority set ..... 245 2ED.016.00 Candidate List empty ...... 247 2ED.017.00 Extended selection present in Directory Entry but Extended Selection Support flag not present or not set in Reader Combination ...... 248 2ED.017.01 Extended selection present in Directory Entry but Extended Selection not supported in ICS ...... 249

2ED.018.00 Extended selection present in Directory Entry and Extended Selection Support flag set in Reader Combination ...... 250 2ED.019.00 Final selection rejected (restart flag = 0) ...... 252 2ED.019.01 Final selection rejected (restart flag = 1) ...... 254 2ED.020.00 Visa Kernel 3 replaced by Kernel 1 ...... 255 2ED.021.00 Visa Kernel 3 not allowed ...... 256 2ED.022.00 Communication error during final selection ...... 257 9.5. KERNEL ACTIVATION ...... 258 2EE.001.00 FCI and Status Word to kernel ...... 259 2EE.002.00 Kernel Activation of the Selected Combination ...... 260 9.6. OUTCOME PROCESSING ...... 262 2EF.001.00 Outcome with UI Request and Field Off ...... 263 2EF.001.01 Outcome with UI Request and Field Off (2) ...... 265 2EF.002.00 Outcome Try Again ...... 266 2EF.003.00 Outcome Select Next ...... 267 ANNEX A: TERMINAL SETTINGS DEFINITION ...... 269 [TERMSETTING1] ...... 269 [TERMSETTING2] ...... 271 [TERMSETTING3] ...... 274 [TERMSETTING4] ...... 277 [TERMSETTING5.X] ...... 280 [TERMSETTING6] ...... 283 [TERMSETTING7] ...... 286 [TERMSETTING8] ...... 287 [TERMSETTING10] ...... 289 [TERMSETTING13] ...... 294 ANNEX B: PDOL DEFINITION ...... 296 ANNEX C: LT (CARD) CONFIGURATIONS DEFINITION ...... 297 [LTSETTING1.X]: SINGLE AID ...... 297 [LTSETTING2.X]: MULTI AID (FULL MATCHING) ...... 443 [LTSETTING3.X] CHARACTERISTICS: MULTI AID WITH PARTIAL MATCH ...... 530 [LTSETTING4.X]: NO MATCH ON KERNEL ID OR AID ...... 545 [LTSETTING5.X]: KERNEL IDENTIFIER NOT PRESENT OR ‘00’ IN PPSE ...... 551 [LTSETTING6.X]: FORMAT ERROR, RESPONSE ERROR, NO RESPONSE ...... 578 [LTSETTING7.X] CHARACTERISTICS: DEFAULT LANGUAGE PREFERENCE ...... 607 [LTSETTING8.X] CHARACTERISTICS: CURRENCY CODE ...... 615 [LTSETTING9.N]: SINGLE AID SUPPORTED WITH C-N KERNELS ...... 617 [LTSETTING10.X]: SINGLE AID SUPPORTED WITH C-REGX KERNEL ...... 631 ANNEX D: TEST CASES APPLICABLE DEPENDING ON THE TERMINAL OPTIONS ...... 632 < END OF THE DOCUMENT> ...... 648

1. Scope

EMV Contactless Specifications for Payment Systems – Book A and Book B, defines the terminal requirements necessary to select an EMV Contactless Application in an international interchange environment and provides for backward compatibility with already existing Contactless Applications. The present document, 'EMVCo Type Approval – Book A & Book B - Test Cases’, describes:

• Test Kernel requirements: describes the test kernel software to be loaded in the device for the purpose of EMV Contactless Type Approval testing, • POS System Environment requirements: describes the requirements of the POS System in order to submit the EMV Contactless Type Approval testing, • A set of test cases which when applied to the terminals, are designed to determine whether the terminal meets the requirements stated in [Book A] and [Book B]. Test cases are defined for unitary tests and functional tests. If any special conditions are required for a specific test case, these conditions are described in the test case. The intended audiences for this document are EMVCo accredited laboratories, Entry Point and Contactless application providers, acquiring members or merchants. Although acquiring members and merchants may reference this document, type approval testing oriented toward Entry Point and Contactless application providers.

2. Referenced Documents

[N1] EMV Integrated Circuit Card Specification for Payment Version 4.3 – Systems – Book 1 – Application Independent ICC to November 2011 Terminal Interface Requirements

[N2] EMV Integrated Circuit Card Application Specification Version 4.3 – for Payment Systems – Book 2 – Security and Key November 2011 Management

[N3] EMV Integrated Circuit Card Terminal Specification for Version 4.3 – Payment Systems – Book 3 – Application Specification November 2011

[N4] EMV Integrated Circuit Card Terminal Specification for Version 4.3 – Payment Systems – Book 4 – Cardholder, Attendant, November 2011 and Acquirer Interface Requirements

[Book EMV Contactless Specifications for Payment Systems Latest version available A] – Book A – Architecture and General Requirements

[Book EMV Contactless Specifications for Payment Systems Latest version available B] – Book B – Entry Point Specification

[Book EMV Contactless Specifications for Payment Systems Latest version available C-n] – Book C-n – kernel Specification, where x refers to Kernel 1 to 7

[ICS] EMVCo Type Approval Contactless Product - Latest version available Implementation Conformance Statement

[Symb] Contactless Symbol Reproduction Guidelines Latest version available

3. Abbreviations and Notations

ADF Application Definition File

AID Application Identifier

CVM Cardholder verification Method

EP Entry Point (refers to Book B Specifications)

FCI File Control Information

GPO GET PROCESSING OPTIONS

ICC Integrated Circuit Card

ID Identifier

LT Lower tester (Card Simulator)

MSG Message

NA Not Applicable (or specific value assigned)

PDOL Processing Options Data Object List

PPSE Proximity Payment System Environment

POS Point Of Sale

RFU Reserved for Future Use

SFI Short File Identifier

TLV Tag Length Value

TTQ Terminal Transaction Qualifier

UI User Interface

4. Global Glossary

Implementation conformance statement (ICS) - A form completed by the product provider. The written statement lists all optional functions as specified in the reference specification implemented [Book A] & [Book B].

Kernel: A software Module that may refer to

• a (Payment System) Kernel: the kernel complies with one of the [Book C-n] specifications (so EMVCo C-n Kernel only). By default a ‘kernel’ refers to a ‘Payment System Kernel’. • a Test Kernel: a software module simulating a Kernel C-n that must be present in the product under test for testing reason. The Test Kernel shall be in accordance with the section ‘6.1. Test Kernel definition’.

• a Kernel C-REGX: a proprietary kernel software present in the Contactless Product where x is a Kernel ID which has been registered following EMVCo kernel ID registration process. C-REGX does not refer to the Payment System Kernels. Laboratory - A facility that performs type approval testing. Lower Tester – Card simulator of the test tool that communicates with the product under test. The LT shall be in accordance with section 7 of the present document. POS System - a POS System is the physical architecture of the Product under test. It is the device that communicates with contactless cards, processes contactless transactions, and may support other payment functionalities such as magnetic stripe or contact chip transactions. The physical architecture can be any of the following:

• Fully integrated terminal: all elements included in a single device.

• Intelligent card reader: The reader handles most of the contactless transaction processing, passing the results for completion by the terminal.

• Combination of terminal and transparent card reader: The reader provides communication with the card, whilst kernels and other processes are in the terminal. Test Kernel – Software simulating a Contactless Kernel C-n that must be present in the product under test for testing reason. The Test Kernel present shall be in accordance with section 6.1 of the present document.

Test Payment Application – Software simulating a Payment Application that must be present in the product under test for testing reason. The test payment application shall be in accordance with the section 7 of the present document.

5. Document Overview

The document part below is organized in four chapters, completed by annexes: o Section 7 specifies the Terminal Test Environment; it includes the Test Kernel specification and a high level of the Terminal Data Configuration, which is detailed in Annex A. o Section 8 specifies the LT (Card) Test Environment; it includes the LT Test kernel and a high level of the LT Data Configuration, which is detailed in Annex B and C. o Section 9 specifies the Test Structure and the Test Categories. o Section 10 contains all the Test Cases definition. This section is divided in 6 subsections to cover all requirements of [Book A] & [Book B].

1. General Requirements

2. Pre-Processing 3. Protocol Activation 4. AID and Kernel Selection 5. Kernel Activation 6. Outcome Processing

6. Terminal Test Environment

6.1. Test Kernel definition This section described the functional requirement of the Terminal Test Kernel ‘TK’ to be loaded in a device in order to perform Book A & Book B software Type Approval Level 2.

6.1.1 General requirements This Terminal Test kernel must be provided by the device vendors and must be capable of meeting the minimum functionality described below:

¨ Simulating 7 (or more) vendor developed test kernels, each being fully independent from the others, having their own unique checksum and Kernel ID ¨ The test kernel shall be able to record and present all flags and data element listed in the Book A and Book B specifications. ¨ The test kernel shall be able to verify the PDOL and build a GPO command accordingly using Kernel or Entry Point data to report those data to the LT. ¨ The test kernel shall be able to generate User Interface Request ¨ The test kernel shall be able to generate Outcome and be restarted after online processing ¨ The test kernels are wholly independent from the payment system kernels ¨ Each kernel may be independently loaded into the terminal or all applications can be loaded into the terminal at one time.

The below figure shows the Test kernel in the POS System environment:

GPO

Test Kernel:

- Send GPO to LT according to PDOL - Recieve data for Outcome and UI

Response Data

Prepare Outcome and UI request

6.1.2 EP data recording

The test kernel must be capable of reflecting the result of the pre-processing and kernel activation process by the Entry Point application. This means that the activated test kernel shall record and output when requested, the following data:

• Internal flags,

• Status Check requested flag,

• Zero Amount flag

• Contactless Application Not allowed flag,

• Terminal Transaction Qualifier.

• Amount Authorized,

• Unpredictable Number

• Restart flag For the purpose of verifying flags the test kernel shall support a proprietary Tag ‘D1’, called ‘Test flags’ in the test environment and capable of mapping above listed data onto Tag ‘D1’ according to the bit setting in Table 1. The Test Flags data element has the following format:

b8 B7 b6 b5 b4 b3 b2 b1 Meaning

0 Reader Contactless Floor Limit Not Exceeded 1 Reader Contactless Floor Limit Exceeded

0 Reader Contactless Transaction Limit Not Exceeded

1 Reader Contactless Transaction Limit Exceeded

0 Reader CVM Required Limit Not Exceeded

1 Reader CVM Required Limit Exceeded

0 Status Check Not Requested

1 Status Check Requested

0 Not Zero Amount

1 Zero Amount

0 Contactless Application Allowed

1 Contactless Application Not Allowed

RFU

Table 1: Tag ’D1’, Test Flags data format – Byte 1

b8 B7 b6 b5 b4 B3 b2 b1 Meaning

0 Restart Flag is 0

1 Restart Flag is 1

RFU

Table 2: Tag ‘D1’, Test Flags data format – Byte 2 Where:

• Terminal Contactless Floor Limit exceeded or not: the bit 8 reflect the setting of the pre-processing internal flag ‘Terminal Contactless Floor Limit exceeded’ of the Entry Point Software as described in section 5.2.1 and 5.2.2 of the EP specification.

• Terminal Contactless Transaction Limit exceeded or not: the bit 7 reflect the setting of the pre-processing internal flag ‘Terminal Contactless Transaction Limit exceeded’ of the Entry Point Software as described in section 5.2.1 and 5.2.2 of the EP specification.

• Terminal CVM Required Limit exceeded or not: the bit 6 reflect the setting of the pre-processing internal flag ‘Terminal CVM Required Limit exceeded’ of the Entry Point Software as described in section 5.2.1 and 5.2.2 of the EP specification.

• Status Check requested or not: the bit 5 reflect the setting of the pre-processing flag ‘Status Check Support’ has requested or not requested, of the Entry Point Software as described in section 5.2.1 and 5.2.2 of the EP specification.

• Zero Amount or not Zero Amount: the bit 4 reflect the setting of the pre-processing flag ‘Zero Amount’ has allowed or not allowed, of the Entry Point Software as described in section 5.2.1 and 5.2.2 of the EP specification.

• Contactless Application not Allowed the bit 3 reflect the setting of the pre- processing flag ‘Contactless Application Not Allowed’ of the Entry Point Software as described in section 5.2.1 and 5.2.2 of the EP specification.

• Restart Flag reflect the setting of the ‘restart flag’

6.1.3 Test data reporting Upon kernel activation when the control is handed over from Entry Point to the selected test kernel, the test kernel must be able to provide all Test data out through a Get Processing Option Command. Following data must be retrievable from the selected Test kernel:

• Test Flags data, with Terminal Transaction Qualifier when provided by EP,

• Amount Authorized,

• Unpredictable Number,

• Kernel ID of the selected Test kernel by EP,

• FCI of the AID selected (this is against EMV and is for testing purposes only) The Get Processing Option Command of the test kernels shall be coded as follows

Code Value

CLA ‘80’

INS ‘A8’

P1 ‘00’

P2 ‘00’

Lc Var.

Data PDOL Related Data

Le ‘00’

Table 3: Get Processing Command Format for the Test kernels

Data field in send in the command message: The data field of the command message is a data object coded according to the PDOL provided by the LT (Card), as defined in EMV section 5.4, and is introduced by the tag '83'. The minimum data to be supported in PDOL are defined in Annex B; it includes the following: - Tag ‘D1’: 2 bytes of Test Flags data according to Table 1,

- Tag ‘9F66’: 4 bytes - TTQ (this tag is not returned when data not present, to be filled with zeroes), - Tag ‘9F02’: 6 bytes – Amount Authorized,

- Tag ‘9F37’: 4 bytes – Unpredictable Number, - Tag ’D7’ with variable length in Binary format - Kernel ID data, indicates the Kernel ID of the selected test kernel - Tag ‘6F’ FCI Template with variable length of the Selected AID. - Tag ‘91’: Authorization Response, with variable length, in case that previous transaction has required a restart. - Tag ‘71’: issuer Script, with variable length, in case that previous transaction has required a restart. - Tag ‘72’: issuer Script, with variable length, in case that previous transaction has required a restart. The length in the PDOL returned in the FCI for the Kernel ID data and FCI template must be set in the LT in such a way that it corresponds to the length supported by the terminal to be tested.

6.1.4 Terminal Test kernel process

This section specifies the Terminal Test kernel process.

1. The Terminal Test kernel is activated according to Book B, section kernel activation. 2. The Terminal Test kernel shall get the FCI Select Response, the Status Word, and also all Entry Point data at activation, and shall record these data.

3. The Terminal Test kernel shall generate a GPO command using the PDOL retrieved in FCI (if present) and send the command to the LT according to the PDOL setting. The data objects supported in PDOL are defined in Annex B.

4. The Terminal Test kernel waits for the LT (card) response which can answer one of the following response:

o Case01: the card response specifies an Outcome without any User Interface Request

o Case02: the card response specifies an Outcome with a User Interface Request on Outcome

o Case03: the card response specifies an Outcome with a User Interface Request on Restart

o Case04: the card response specifies an Outcome with a User Interface Request on Outcome and a User Interface Request on Restart

o Case05: no card response, or no outcome or wrong response format 4.1. When a User Interface Request on Outcome is present, the following parameters specific to User Interface Request on Outcome shall be present:

o Message Identifier

o Status o Hold Time (integer multiple of 100ms) o Language Preference (as per EMV tag '5F2D' according to ISO 639) o Value Qualifier o Value

o Currency Code (numeric value as per ISO 4217). The Terminal Test kernel shall process this User Interface Request and continue. 4.2. When a User Interface Request on Restart is present, the same parameters as for User Interface Request on Outcome shall be present: 4.3. When an Outcome is present, with the following parameters specific to Outcome shall be present:

o Start

o Online Response Data

o CVM

o UI Request on Outcome

o UI Request on Restart

o Data Record Present

o Discretionary Data Present

o Alternate Interface Preference

o Receipt

o Field Off Request o Removal Timeout The Terminal Test kernel shall send this Outcome with User Interface Request on Restart (if present) to Entry Point. 4.4. When no card response, or no outcome or wrong response format, the Terminal Test kernel closes the session 5. If ‘Start’ Parameter is set to ‘NA’, the Test kernel closes the session. If ‘Start’ Parameter is set to ‘A’, ‘B’, ‘C’, the test kernel shall wait for a new activation from the Entry Point (with the Select AID response) and go to Step 2 If ‘Start’ Parameter is set to ‘D’, the test kernel shall wait for a new activation from the Entry Point (start ‘D’) with online response and shall generate a GPO command using the PDOL retrieved in FCI (if present) and send the command to the card and go to Step 4. Note: The Terminal Test kernel software receives from EP software, all EP data. The way these data are transmitted from EP to the selected contactless kernel is not defined in the EP specification. However for testing purpose these data transmitted to the selected test kernel, must be transmitted by the EP software in the same way and using the same format as for a payment system kernel.

6.2. Test Payment Application For testing purpose, the Test (or real) payment application loaded in the POS system at the time of testing shall support the following requirements:

• Been able to perform transactions will all the kernels C-1 to C-7 present

• Been able to perform functionality of the test kernels instanced with the associated kernel ID and AIDs.

• Been able to store all transactions performed by the kernel C-1 to C-7 present, in log records under the format specified by each kernels,

• The Test Tool shall have access to these logs, in order to check that:

o all transactions performed are logged

o the format and the content of each logs is correct

6.3. Test Kernel ID definition

When a Payment System Kernel C-i is present in a Terminal Data Configuration, the Test Kernel cannot use the Kernel ID values ’01, ‘02’, ‘03’, ‘04’, ‘05’, ‘06’ or ‘07’, so a dynamic allocation of the test kernel ID (called ‘TKi’) has been defined with the following rules:

o TK1 = ‘01’ if the Kernel C-1 (Kernel ID = ’01’) is not present. TK1 = ‘3F’ if the Kernel C-1 (Kernel ID = ’01’) is present

o TK2 = ‘02’ if the Kernel C-2 (Kernel ID = ’02’) is not present. TK2 = ‘3E’ if the Kernel C-2 (Kernel ID = ’02’) is present

o TK3 = ‘03’ if the Kernel C-3 (Kernel ID = ’03’) is not present. TK3 = ‘3D’ if the Kernel C-3 (Kernel ID = ’03’) is present

o TK4 = ‘04’ if the Kernel C-4 (Kernel ID = ’04’) is not present. TK4 = ‘3C’ if the Kernel C-4 (Kernel ID = ’04’) is present

o TK5 = ‘05’ if the Kernel C-5 (Kernel ID = ’05’) is not present. TK5 = ‘3B’ if the Kernel C-5 (Kernel ID = ’05’) is present

o TK6 = ‘06’ if the Kernel C-6 (Kernel ID = ’06’) is not present. TK6 = ‘3A’ if the Kernel C-6 (Kernel ID = ’06’) is present

o TK7 = ‘07’ if the Kernel C-7 (Kernel ID = ’07’) is not present. TK7 = ‘39’ if the Kernel C-7 (Kernel ID = ’07’) is present

6.4. Terminal Data Configurations (‘Termsetting’) Several terminal data configurations are needed to test Book A & Book B. These data configurations are used in the Test Cases. These Terminal data configurations are referenced as [TermsettingX], where X reflects one of the Terminal Setting below. The product under test may contain at the time of testing one or several payment system Kernels, according to the ICS. The data setting related to the kernel present is needed according to the termsetting below.

Terminal setting 1 [Termsetting1]:

o Covers the Kernel ID coding (international/domestic kernel)

o International and Domestic AID

o All Pre-Processing features activated (pre-processing parameter with the same value for all combinations not depending on the Transaction Type)

o Kernels C-1 to C-7, when present (according to the ICS), are not activated (so the test Kernels setting: Tki=i)

Terminal setting 2 [Termsetting2]:

o 7 kernel ID and international AIDs (including AMEX, Union Pay, DISCOVER, JCB, MasterCard and VISA) and 20 combinations available not depending of the Transaction Type

o Pre-Processing parameters specific to each combination

Terminal setting 3 [Termsetting3]:

o Same combination Kernel ID/AID as [Termsetting2] o Pre-Processing not activated

o Data setting related to the Kernel C-1 to C-7, which are loaded at the time of testing, according to the ICS.

Terminal setting 4 [Termsetting4]:

o 5 kernels ID and international AIDs and 10 combinations available depending of the Transaction Type

o Pre-Processing parameters specific to each combination

Terminal setting 5 [Termsetting5]:

o Same combination Kernel ID/AID as [Termsetting4] o Pre-Processing not activated

Terminal setting 6 [Termsetting6]:

o Same as [Termsetting2] but Kernel ID 1 is not supported and less AIDs.

o Kernels C-1 to C-7, when present (according to the ICS), are not activated (so the test Kernels setting: Tki=i)

Terminal setting 7 [Termsetting7]:

o Same as [Termsetting3] but Kernel ID 1 is not supported and less AIDs.

o Kernels C-1 to C-7, when present (according to the ICS), are not activated (so the test Kernels setting: Tki=i)

Terminal setting 8 [Termsetting8]:

o Same as [Termsetting1] but several TTQ RFU bits are set to 1.

Terminal setting 9 [Termsetting9]:

o Same as [Termsetting10] but with each Kernel C-1 to C-7 present is associated to several AIDs.

Terminal setting 10 [Termsetting10]:

o Each kernel present C-1 to C-7 has it own limits, o When present, kernels C-1 to C-7 shall be activated o When Kernel C-2 present, detailed values for Kernel C2 AID A0 00 00 00 04 10 10 are provided in “Kernel C-2 Testing Environment” (Terminal Products).

o If Contactless Kernel(s) C-REGX with Registered Kernel ID is (are) present(s), all Kernel(s) C-REGX shall be activated.

o If the Contactless Product contains a Contact Level 2 Kernel following the Modular Architecture, it shall be activated with setting as described in the Contact Level 2 Test Plan.

Terminal setting 11 [Termsetting11] (if Autorun is supported only):

o Same as [Termsetting10] but Autorun Parameter is set to ‘yes’

Terminal setting 13 [Termsetting13]:

o Same kernel IDs as [Termsetting1] but preprocessing is not supported (Autorun Parameter: ‘Yes’, if Autorun Option is supported), and each AID is associated to a single Kernel ID

Please refer to Annex A for more details about each Terminal setting.

7. LT (Card) test environment

7.1. LT Test kernel for Test kernel This section describes the functional requirement of the LT (Card) Test kernel to perform Book A & B Type Approval, when using Test kernels.

Three commands shall be supported:

• Select PPSE

• Select AID

• Get Processing Options

7.1.1 Select PPSE Format For the Select PPSE command, several responses shall be supported:

• A correctly formatted FCI coded accorded EMV (including one or several template 61, with or without optional data elements). A response length until 252 bytes shall be supported.

• A wrongly formatted FCI

• An Error Status Word

• No response to the Select PPSE command

• For each LT (Card) data configuration, a single Select PPSE response is specified.

7.1.2 Select AID format

For the Select AID command, several responses shall be supported:

• A correctly formatted FCI coded accorded EMV (with partial or full AID, with or without PDOL, with or without optional data element). A response length until 252 bytes shall be supported.

• An Error Status Word

• No response to the Select AID command

• For each LT (Card) data configuration, a single Select AID response is specified per AID present in the card. LT (Card) with a single to 4 AIDs shall be supported. The PDOL content is defined in Annex B.

7.1.3 Get Processing Options format

For the Get Processing Options command, several responses shall be supported:

7.1.3.1 Template response: The Template response is a TLV (Tag ‘77’) constructed data element formatted as follow:

• Outcome data: A TLV coded data element (tag ‘D4’), which contain the Kernel Outcome that the LT is requested. The test kernel will then pass this Outcome to Entry Point. This TLV data contains the following data element (values only):

o Outcome Value (1 byte), coded in Hex: reflecting the various Outcome value of [Book A] Table 6-1. First line of the Table has the value ‘01’ (Select Next), second the value ‘02’ (Try Again), etc

The below data element are the parameters related to the above Outcome:

o Start value (1 byte): reflecting line 1 (Start) of [Book A] Table 6-2: value ‘0A’, 0B’, ‘0C’ ‘0D’ for A, B, C and D restart, and value’00’ for N/A.

o Online Response Data (1 byte): reflecting line 2 (Online Response Data) of [Book A] Table 6-2: value ‘01’ for EMV Data, value ‘02’ for Any and value’00’ for N/A

o CVM value (1 byte): reflecting line 3 (CVM) of [Book A] Table 6-2: value ‘01’, 02’, ‘03’ ‘04’ for Online PIN, Conf Code Verified, Obtain Signature, No CVM, and value’00’ for N/A.

o Alternate Interface Preference value (1 byte): reflecting line 8 (Alternate Interface) of [Book A] Table 6-2: value ‘01’, 02’, ‘03’ for Contact Chip, Mag- Stripe and both, and value’00’ for N/A.

o Receipt value (1 byte): reflecting line 9 (Receipt) of [Book A] Table 6-2: value ‘01’ for provide a receipt, and value’00’ for N/A.

o Field Off Request value (2 bytes): reflecting line 10 (Field Off request) of [Book A] Table 6-2: hold time unit coded in Hexadecimal (‘FFFF’ for N/A).

o Removal Timeout value (2 bytes): reflecting line 11 (Removal Timeout) of [Book A] Table 6-2: time out unit coded in Hexadecimal.

• Online Response Data 1: A TLV coded data element (tag ‘91’), which contain the EMV tag 91 data element which might be present in case of restart

• Online Response Data 2: A TLV coded data element (tag ‘71’), which contain the EMV tag 71 data element which might be present in case of restart

• Online Response Data 3: A TLV coded data element (tag ‘72’), which contain the EMV tag 72 data element which might be present in case of restart

• UI Request on Outcome: A TLV coded data element (tag ‘D5’), which contain the UI request on Outcome that the LT request (TLV coded). This TLV data contains the following data element (values only) of Table 7-1:

o Message ID value (1 byte): reflecting [Book A] Table 9-5.

o Status value (1 byte): coded in Hex: reflecting the various status value of [Book A] Table 9-1. First line of the Table has the value ‘01’, second the value ‘02’, etc

o Hold Time value (2 bytes): reflecting line 3 (Hold Time) of [Book A] Table 7-1: hold time unit coded in Hexadecimal.

o Language Preference value (2 bytes): reflecting line 4 of [Book A] Table 7-1: value of EMV tag ‘5F2D’. When no language preference is supported then the value is ‘0000’.

o Value Qualifier value (1 byte): reflecting line 5) of [Book A] Table 7-1: value ‘01’ is for Amount and value ‘02’ is for Balance. ‘00’ means Value Qualifier is not present.

o Value (6 bytes): reflecting line 6 (Value) of [Book A] Table 7-1: follow description of table 7-1. When Value Qualifier is not present (set to ‘00’), this filed must be filled with zero’s.

o Currency Code (2 bytes): reflecting line 7 (Currency Code) of [Book A] Table 7-1: follow description of table 7-1. When Value Qualifier is not present (set to ‘00’), this filed must be filled with zero’s.

• UI Request on Restart A TLV coded data element (tag ‘D6’), which contain the UI request on Outcome that the LT request (TLV coded). Same coding as above.

• Data Record Present A TLV coded constructed data element (tag ‘E1’), which contain the transaction record for clearing that the LT request (TLV coded). This field contain is any TLV EMV data element.

8.1.3.2 No response to the GPO command The GPO response from LT can be empty (for time out testing purpose).

Also For each LT (Card) data configuration, two GPO responses may be specified per AID present in the card.

• A response when Restart = 0

• A response when Restart = 1

7.2. LT Test kernels for kernel C-1 to C-7

This section described the functional requirement of the LT (Card) Test kernels to perform Multi Kernels Independency Type Approval Level 2. Seven different LT Test kernels must be supported by the LT:

7.2.1 LT Test Payment Application for kernel C-1

Physical Cards or card emulator with Test Payment Application for kernel C-1 with data setting [LTsetting9.1] and [LTsetting9.5] will be provided to Laboratories. See Appendix C for the data setting of these cards.

7.2.2 LT Test Payment Application for kernel C-2

Physical Cards or card emulator with Test Payment Application for kernel C-2 with data setting [LTsetting9.2x] and [LTsetting9.6] will be provided to Laboratories. See Appendix C for the data setting of these cards.

7.2.3 LT Test Payment Application for kernel C-3 Physical Cards or card emulator with Test Payment Application for kernel C-3 with data setting [LTsetting9.3] and [LTsetting9.7] will be provided to Laboratories. See Appendix C for the data setting of these cards.

7.2.4 LT Test Payment Application for kernel C-4

Physical Cards or card emulator with Test Payment Application for kernel C-4 with data setting [LTsetting9.4x] and [LTsetting9.8] will be provided to Laboratories. See Appendix C for the data setting of these cards.

7.2.5 LT Test Payment Application for kernel C-5

Physical Cards or card emulator with Test Payment Application for kernel C-5 with data setting [LTsetting9.9x] will be provided to Laboratories. See Appendix C for the data setting of these cards.

7.2.6 LT Test Payment Application for kernel C-6

Physical Cards or card emulator with Test Payment Application for kernel C-6 with data setting [LTsetting9.10x] will be provided to Laboratories. See Appendix C for the data setting of these cards.

7.2.7 LT Test Payment Application for kernel C-7 Physical Cards or card emulator with Test Payment Application for kernel C-7 with data setting [LTsetting9.20x] will be provided to Laboratories. See Appendix C for the data setting of these cards.

7.3. LT (Card) data configuration (LTsetting) For the purpose of running the tests 7 groups of LT (Card) data configuration have been defined. Each group will contain several LT data configuration. The LT data configurations, called [LTsettingY.X], are used by the test case to simulate a specific set of data of the card:

• [LTsetting1.x]: single AID

• [LTsetting2.x]: multi AID (full matching)

• [LTsetting3.x]: multi AID (partial matching)

• [LTsetting4.x]: no match on kernel Identifier or AID

• [LTsetting5.x]: kernel Identifier is ‘00’ or not present in PPSE

• [LTsetting6.x]: format error, response error, no response

• [LTsetting7.x]: Language preference not supported

• [LTsetting8.x]: Currency Code

• [LTsetting9.n]: Kernel C-n support where n is the kernel 1 to 7. Each LTsetting will contain a single Application.

• [LTsetting10.x]: Contactless Kernel C-REGX support where x is a registered Kernel ID value (so not the kernel 1 to 5). The LTsetting will contain a single Application based on this Contactless Kernel C-REGX. Please refer to Annex C for all details of each setting.

8. Test Structure

8.1. Test numbering and associated sub cases Test Numbers are structured as follow:

2Ex.yyy.zz Version: 1 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 Cases are present, reference to a specific sub case in a test case can be seen as follow: 2Ex.yyy.zz.ss, where ss is the number of the sub case.

8.2. Test Category

The Test Cases listed in this document are categorized. This rule is not strictly followed however, as depending on the objective of the test, it may happen that a test listed in a specific category also covers functions listed in another category. Test Cases are divided into the following categories:

• 2EA, General Requirements: The intent of the test cases in this category is to verify the general requirements in accordance with [Book A] and [Book B] section 3.6

• 2EB, Pre-Processing: The intent of the test cases in this category is to verify the Pre-Processing requirements in accordance with [Book B] section 3.1

• 2EC, Protocol Activation: The intent of the test cases in this category is to verify the Protocol Activation requirements in accordance with [Book B] section 3.2

• 2ED, AID and Kernel Selection: The intent of the test cases in this category is to verify the AID and Kernel Selection requirements in accordance with [Book B] section 3.3

• 2EE, Kernel Activation: The intent of the test cases in this category is to verify the AID and Kernel Selection requirements in accordance with [Book B] section 3.4

• 2EF, Outcome Processing: The intent of the test cases in this category is to verify the AID and Kernel Selection requirements in accordance with [Book B] section 3.5.

• 2LA, Multi-kernel Independency Requirements: The intent of the test cases in this category is to verify the independency of each kernels, and that there is no side effect of a kernel to another one.

• 2LB, Modular Approach Requirements: The intent of the test cases in this category is to verify that when a product has been recognized as modular, it follow the quality criteria defined by EMV.

8.3. Test Case Format Means the number of sub Cases associated to this test. Each sub Case could be seems 2EA.001.00 Test Name as a separate Case

Test No: - Revision 1 – Number of sub Cases: n

Objective:

Reference Book A – version 2.3 - Requirement xxxxx BOOK A/B: Book B – version 2.3 - Requirement yyyyy

Terminal Configuration:

Conditions:

Action: If a section is empty it is filled with ‘NA’ Procedure:

Pass Criteria:

• Objective: Describes the EMV requirements that will be tested. It may contain a single or several requirements coming from the EMV books. • Reference BOOK A/B: Reference to the sections of the EMV books where the previous requirements are coming from. • Terminal Configuration: describes the Terminal Options that are needed for this test, if they are different from the default setting. Options: means the options that the terminal support according to the ICS. • Conditions: describes the test conditions needed to reach the pass criterias. • Procedure: describe the test procedure needed to perform this test until reaching the conditions described in the ‘Conditions’ section of the test.

• Pass Criteria: describes the pass criterias to reach in order to achieve the test.

Notes: The Terminal Configuration field filled with ‘NA’ means that the test will be always executed. When Kernel ID or Kernel identifier is set with a value different from TKn or Kernel C-n, the value must be interpreted in hexadecimal. The amounts defined in this document are such that an amount ‘45’ must be translated to a ‘9F02’ tag (‘Amount authorized’) value ‘000000 000045’ whatever the currency used. Of course the ‘Amount Other’ and ‘Limits’ follow the same logic, so a CVM Required Limit defined as ‘120’ in the test plan must be configured as ‘000000 000120’ in the terminal under test. Some tests require the amount to be a ‘single unit of currency’. In such tests the ‘9F02’ tag value will of course be different when the currency exponents are different. A single unit of currency has the value of 1 of the (major) unit of currency as defined in ISO 4217. As an example a single unit of currency for Euro is 1.00.

9. Test Cases

9.1. General requirements

2EA.001.00 Entry of Amount Authorized

Test No: - Revision 2.3a - Number of sub cases: 3

Objective: To ensure that when Autorun is ‘No’, or Autorun option not supported, and a single type of transaction is supported, the Amount Authorized entered in the terminal is correctly retrieved in the kernel data.

Reference Book A – version 2.3 - Requirement 8.1.1.3 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [LTsetting1.1] with an Amount Authorized of 10. • Case02: Entry Point transaction is performed with[ LTsetting1.2] with an Amount Authorized of 75. • Case03: Entry Point transaction is performed with[ LTsetting1.97] with an Amount Authorized of 45. Action: NA

Procedure: Entry Point transactions are performed for [Termsetting2] with different LT settings

Pass Criteria: • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Authorized = 10 • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Transaction Type = value supported for the configuration • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Other = 0 • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Authorized = 75 • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Transaction Type = value supported for the configuration • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Other = 0 • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Authorized = 45

2EA.001.00 Entry of Amount Authorized

• Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Transaction Type = value supported for the configuration • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Other = 0

2EA.002.00 Entry of Amount Authorized and Transaction Type ‘Purchase’

Test No: - Revision 2.3a - Number of sub cases: 0

Objective: To ensure that when Autorun is ‘No’, or Autorun option not supported, and Type of Transaction ’Purchase’ is supported the Amount Authorized and the Transaction Type entered in the terminal are correctly retrieved in the kernel data.

Reference Book A – version 2.3 - Requirement 8.1.1.3 BOOK A/B:

Terminal [Purchase] supported Configuration:

Conditions: An Amount Authorized of 10 is entered and Transaction Type = ‘Purchase’ (00)

Action: NA

Procedure: Entry Point transactions are performed for [Termsetting4] with [LTsetting1.3]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Authorized = 10, • The LT shall receive in the GET PROCESSING OPTIONS data field: Transaction Type = ’Purchase’ (00), • The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Other = 0

2EA.002.01 Entry of Amount Authorized and Transaction Type ‘Cash Advance’

Test No: - Revision 2.3a - Number of sub cases: 0

Objective: To ensure that when Autorun is ‘No’, or Autorun option not supported, and Type of Transaction ‘Cash Advance’ is supported, the Amount Authorized and the Transaction Type entered in the terminal are correctly retrieved in the kernel data.

Reference Book A – version 2.3 - Requirement 8.1.1.3 BOOK A/B:

Terminal [Cash Advance] supported Configuration:

Conditions: An Amount Authorized of 20 is entered and Transaction Type = ‘Cash Advance’ (01)

Action: NA

Procedure: Entry Point transactions are performed for [Termsetting4] with [LTsetting1.1].

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Authorized = 20, • The LT shall receive in the GET PROCESSING OPTIONS data field: Transaction Type = ‘Cash Advance’ (01), • The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Other = 0

2EA.002.02 Entry of Amount Authorized and Transaction Type ‘Refund’

Test No: - Revision 2.3a - Number of sub cases: 0

Objective: To ensure that when Autorun is ‘No’, or Autorun option not supported, and Type of Transaction ‘Refund’ is supported, the Amount Authorized and the Transaction Type entered in the terminal are correctly retrieved in the kernel data.

Reference Book A – version 2.3 - Requirement 8.1.1.3 BOOK A/B:

Terminal [Refund] supported Configuration:

Conditions: An Amount Authorized of 30 is entered and Transaction Type = ‘Refund’ (20)

Action: NA

Procedure: Entry Point transactions are performed for [Termsetting4] with [LTsetting1.4].

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Authorized = 30, • The LT shall receive in the GET PROCESSING OPTIONS data field: Transaction Type = ‘Refund’ (20), • The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Other = 0

2EA.003.00 Entry of Amount Authorized, Amount Other

Test No: - Revision 2.3a - Number of sub cases: 2

Objective: To ensure that when Autorun is ‘No’, or Autorun option not supported, and the Type of Transaction ‘Purchase with cashback’ is supported, the Amount Authorized and Amount Other entered in the terminal are correctly retrieved in the kernel data.

Reference Book A – version 2.3 - Requirement 8.1.1.3 BOOK A/B:

Terminal [Purchase with cashback] supported Configuration:

Conditions: • Case01: a Purchase Amount of 20, and Cashback Amount of 10 are entered • Case02: a Purchase Amount of 50, and Cashback Amount of 20 are entered Action: NA

Procedure: Entry Point transactions are performed for [Termsetting4] with [LTsetting1.3].

Pass Criteria: • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Authorized = 30 (sum of Purchase Amount and Cashback Amount) • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Transaction Type = ’Purchase with Cashback’ (00 or 09) • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Other = 10 (Cashback Amount) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Authorized = 70 (sum of Purchase Amount and Cashback Amount) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Transaction Type = ’Purchase with Cashback’ (00 or 09) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Other = 20 (Cashback Amount)

2EA.004.00 Restart flag cleared at new transaction

Test No: - Revision 1 - Number of sub cases: 2

Objective: To ensure that when a new transaction is started, the Restart flag is cleared.

Reference Book A – version 2.3 - Requirement 8.1.1.4 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting2]

• Case02: Entry Point transaction is performed with [Termsetting3] Action: NA

Procedure: Entry Point transaction is performed for different Term settings with [LTsetting1.1]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Restart Flag is set to 0

2EA.005.00 Field off at new transaction (Autorun = ’No’)

Test No: - Revision 2.3a - Number of sub cases: 0

Objective: To ensure that when AutoRun is 'No', or Autorun option not supported and a new transaction is started, the field is off and the request message ’14’ (Welcome) is displayed.

Reference Book A – version 2.3 - Requirement 8.1.1.5 BOOK A/B:

Terminal NA Configuration:

Conditions: NA Action: NA

Procedure: Entry Point transaction is started for [Termsetting2] with [LTsetting1.2]

Pass Criteria: • The field is off (i.e. no RF field is active) when Entry point transaction is started • The terminal shall display Message Identifier ‘14’ (Welcome) at least until a card is presented in the field

2EA.005.01 Reader status Idle at new transaction (Autorun = ’No’)

Test No: - Revision 2.3a - Number of sub cases: 0

Objective: To ensure that when AutoRun is 'No', or Autorun option not supported, the Reader Status is “Idle”,until a new transaction is started.

Reference Book A – version 2.3 - Requirement 8.1.1.5 BOOK A/B:

Terminal NA Configuration:

Conditions: No amount is entered but a card is presented Action: NA

Procedure: Entry Point transaction is started for [Termsetting2] with [LTsetting1.2]

Pass Criteria: • The field is off (i.e. no RF field is active) when Entry point transaction is started until the transaction amount is entered (even if a card is presented)

2EA.006.00 Field on at new transaction (Autorun = ’Yes’)

Test No: - Revision 2.3a - Number of sub cases: 0

Objective: To ensure that when AutoRun is 'Yes' and a new transaction is started, the field is on and the request message ’15’ (Present Card) is displayed

Reference Book A – version 2.3 - Requirement 8.1.1.6 BOOK A/B:

Terminal [Autorun] supported Configuration:

Conditions: NA Action: NA

Procedure: Entry Point transaction is performed for [Termsetting3] with [LTsetting1.3]

Pass Criteria: • The field is on when Entry point transaction is started • The terminal shall display Message Identifier ‘15’ (Present Card) until a card is presented in the field

2EA.006.01 Reader status Ready to Read at new transaction (Autorun = ’Yes’)

Test No: - Revision 2.3a - Number of sub cases: 0

To ensure that when AutoRun is 'Yes', the Reader Status is “Ready to Read” when a new transaction is started. Objective:

Reference Book A – version 2.3 - Requirement 8.1.1.6 BOOK A/B:

Terminal [Autorun] supported Configuration:

Conditions: Entry Point transaction is started, with a card present in the field Action: NA

Procedure: Entry Point transaction is performed for [Termsetting3] with [LTsetting1.2]

Pass Criteria: • The field is on when Entry point transaction is started • the Select PPSE command is received by the card.

2EA.006.02 Terminal EMV Data available for Kernel for a Purchase transaction

Test No: - Revision 2.3a - Number of sub cases: 2

Objective: To ensure that each time a Kernel is activated for a Purchase transaction, the terminal data defined below are available for the Kernel selected:

o Acquirer Identifier

o Additional Terminal Capabilities

o Application Identifier (AID) – terminal

o Application Version Number

o Interface Device (IFD) Serial Number

o Merchant Category Code

o Merchant Identifier

o Merchant Name and Location

o Point-of-Service (POS) Entry Mode

o Terminal Capabilities

o Terminal Country Code

o Terminal Identification

o Terminal Type

o Transaction Date

o Transaction Sequence Counter

o Transaction Status Information

o Transaction Time

o Transaction Type

Reference Book A – version 2.3 - Requirement 8.1.1.7 BOOK A/B:

Terminal [Purchase] supported Configuration:

2EA.006.02 Terminal EMV Data available for Kernel for a Purchase transaction

Conditions: • Case01: Entry Point transaction is performed with [LTsetting1.90] with (GPO requesting all data defined above) Transaction Type = ’Purchase’ (‘00’), and Amount = 2 • Case02: Entry Point transaction is performed with [LTsetting1.98] with (GPO requesting all data defined above) Transaction Type = ’Purchase’ (‘00’), and Amount = 5 Action: NA

Procedure: An Entry Point transaction is performed for [Termsetting4] with different LT settings.

Pass Criteria: • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field, the correct Terminal data values for Transaction Type = ’Purchase’ (‘00’) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field, the correct Terminal data values for Transaction Type = ’Purchase’ (‘00’)

2EA.006.03 Terminal EMV Data available for Kernel for a Purchase with Cashback transaction

Test No: - Revision 1 - Number of sub cases: 0

Objective: To ensure that each time a Kernel is activated for a Purchase with Cashback transaction, the terminal data defined below are available for the Kernel selected:

o Acquirer Identifier

o Additional Terminal Capabilities

o Application Identifier (AID) – terminal

o Application Version Number

o Interface Device (IFD) Serial Number

o Merchant Category Code

o Merchant Identifier

o Merchant Name and Location

o Point-of-Service (POS) Entry Mode

o Terminal Capabilities

o Terminal Country Code

o Terminal Identification

o Terminal Type

o Transaction Date

o Transaction Sequence Counter

o Transaction Status Information

o Transaction Time

o Transaction Type

Reference Book A – version 2.3 - Requirement 8.1.1.7 BOOK A/B:

Terminal [Purchase with Cashback] supported Configuration:

2EA.006.03 Terminal EMV Data available for Kernel for a Purchase with Cashback transaction

Conditions: • Entry Point transaction is performed with (GPO requesting all data defined above) Transaction Type = ’Purchase with Cashback’, and Amount = 2, Amount Other = 1

Action: NA

Procedure: An Entry Point transaction is performed for [Termsetting4] with [LTsetting1.91]

Pass Criteria: • the LT shall receive in the GET PROCESSING OPTIONS data field, the correct Terminal data values for Transaction Type = ’Purchase with Cashback’ (‘00’ or ‘09’)

2EA.006.04 Terminal EMV Data available for Kernel for a Cash Advance transaction

Test No: - Revision 1 - Number of sub cases: 0

Objective: To ensure that each time a Kernel is activated for a Cash Advance transaction, the terminal data defined below are available for the Kernel selected:

o Acquirer Identifier

o Additional Terminal Capabilities

o Application Identifier (AID) – terminal

o Application Version Number

o Interface Device (IFD) Serial Number

o Merchant Category Code

o Merchant Identifier

o Merchant Name and Location

o Point-of-Service (POS) Entry Mode

o Terminal Capabilities

o Terminal Country Code

o Terminal Identification

o Terminal Type

o Transaction Date

o Transaction Sequence Counter

o Transaction Status Information

o Transaction Time

o Transaction Type

Reference Book A – version 2.3 - Requirement 8.1.1.7 BOOK A/B:

Terminal [Cash Advance] supported Configuration:

2EA.006.04 Terminal EMV Data available for Kernel for a Cash Advance transaction

Conditions: • Entry Point transaction is performed with (GPO requesting all data defined above) Transaction Type = ’Cash Advance’ (‘01’), and Amount = 2

Action: NA

Procedure: An Entry Point transaction is performed for [Termsetting4] with [LTsetting1.90]

Pass Criteria: • the LT shall receive in the GET PROCESSING OPTIONS data field, the correct Terminal data values for Transaction Type = ’Cash Advance’ (‘01’)

2EA.006.05 Terminal EMV Data available for Kernel for a Refund transaction

Test No: - Revision 1 - Number of sub cases: 0

Objective: To ensure that each time a Kernel is activated for a Refund transaction, the terminal data defined below are available for the Kernel selected:

o Acquirer Identifier

o Additional Terminal Capabilities

o Application Identifier (AID) – terminal

o Application Version Number

o Interface Device (IFD) Serial Number

o Merchant Category Code

o Merchant Identifier

o Merchant Name and Location

o Point-of-Service (POS) Entry Mode

o Terminal Capabilities

o Terminal Country Code

o Terminal Identification

o Terminal Type

o Transaction Date

o Transaction Sequence Counter

o Transaction Status Information

o Transaction Time

o Transaction Type

Reference Book A – version 2.3 - Requirement 8.1.1.7 BOOK A/B:

Terminal [Refund] supported Configuration:

2EA.006.05 Terminal EMV Data available for Kernel for a Refund transaction

Conditions: • Entry Point transaction is performed with (GPO requesting all data defined above) Transaction Type = ’Refund’ (‘20’), and Amount = 2

Action: NA

Procedure: An Entry Point transaction is performed for [Termsetting4] with [LTsetting1.91]

Pass Criteria: • the LT shall receive in the GET PROCESSING OPTIONS data field, the correct Terminal data values for Transaction Type = ’Refund’ (‘20’).

2EA.007.00 Unpredictable Number different at each transaction

Test No: - Revision 2.1a - Number of sub cases: 2

Objective: To ensure that each time a Kernel is activated (including the result of Select Next and Try Again Outcomes), the Unpredictable Number (Tag ‘9F37’) shall have a new value.

Reference Book A – version 2.3 - Requirement 8.1.1.8 BOOK A/B:

Terminal NA Configuration:

Conditions: • For each transaction performed the test tool shall store the Terminal Unpredictable Number provided via the GET PROCESSING OPTIONS data field.

• Case01: 500 Entry Point transactions are performed with [Termsetting2] consecutively without resetting the terminal.

• Case02: 500 Entry Point transactions are performed with [Termsetting3] consecutively without resetting the terminal.

Action: NA

Procedure: • For each transaction performed in the test cases a different LT setting shall be used: [LTsetting1.1] for the transaction 1, [LTsetting1.2] for transaction 2, [LTsetting2.40] for transaction 3, and loop these 3 LT setting for the 500 transactions.

• Case01 and Case02 shall be performed consecutively.

• Terminal shall be resetted between Case01 and Case02.

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field, Unpredictable Number values different for each transaction • For each transaction, the Terminal Unpredictable Number (9F37) stored shall: o Not be a duplicated value of previous Unpredictable Number values (both sequences of 500 transactions included) o None of the bits is fixed, i.e. the ith bit is not the same for all 1,000 UNs (1≤i≤32)

2EA.007.00 Unpredictable Number different at each transaction

o The average hamming weight shall be between 15 and 17 (i.e. the number of bits set to '1' in the total of 32,000 bits shall be between 15,000 and 17,000).

2EA.010.00 Contactless interface powered down when contact interface activated

Test No: - Revision 2.5a - Number of sub cases: 2

Objective: To ensure that when the presence of a card with a contact interface is detected during a contactless transaction, the contactless transaction is terminated and the contactless interface is powered down, and keep it powered down for the duration of the transaction.

Reference Book A – version 2.5 - Requirement 8.1.1.10 BOOK A/B:

Terminal [contact] supported Configuration:

Conditions: • Case 01: Entry Point transaction is performed with [Termsetting1] and a Contact card is introduced in the contact reader during the Entry point transaction (Contactless Card Interaction not completed)

• Case02: Entry Point transaction is performed th [Termsetting3] and a Contact card is introduced in the contact reader during the Entry point transaction (Contactless Card Interaction not completed),

Action: NA

Procedure: Entry Point transaction is started in contactless mode for different Term settings with [LTsetting1.1]

Pass Criteria: • The field is powered off and keeps powered off for the duration of the transaction done in contact mode.

2EA.010.01 Contactless interface powered down during a contact transaction

Test No: - Revision 2.5a - Number of sub cases: 0

Objective: To ensure that when a transaction is started with a contact interface, the contactless interface is powered down prior to initiating a contact chip transaction and keep it powered down for the duration of the contact transaction.

Reference Book A – version 2.5 - Requirement 8.1.1.10 BOOK A/B:

Terminal [contact] supported Configuration:

Conditions: Contact card is introduced in the contact reader Action: NA

Procedure: Entry Point transaction is started in contact mode

Pass Criteria: • The field is powered off and keeps powered off for the duration of the transaction done in contact mode.

2EA.011.00 User Interface Request Hold Time

Test No: - Revision 2.6a - Number of sub cases: 3

Objective: To ensure that If the request includes a hold time, then any subsequent User Interface Requests received during this period shall not be processed until the hold time has elapsed.

Reference Book A – version 2.6 - Requirement 8.1.1.16 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [LTsetting1.60] (Outcome ‘Approved’ with UI Request ‘Approved’ and hold Time = 100 Units (10 seconds)) and Amount = 2 • Case02: Entry Point transaction is performed with [LTsetting1.61] (Outcome ‘Declined’ with UI Request ‘Not Authorized’ and hold Time = 200 Units (20 seconds)) and Amount = 2 • Case03: Entry Point transaction is performed with [LTsetting1.62] (First Outcome ‘online request’ with UI Request on Restart ‘PRESENT CARD AGAIN’ and hold Time = 100 Units (10 seconds) and Final Outcome ‘Approved’) and Amount = 2 Action: NA

Procedure: Entry Point transaction is performed with [Termsetting1]

Pass Criteria: • Case01: The UI Request on Outcome: MSG ID 03 ‘Approved’ is correctly displayed during 10 seconds at end of the transaction • Case02: The UI Request on Outcome: MSG ID 07 ‘Not Authorized’ is correctly displayed during 20 seconds at end of the transaction • Case03: The UI Request on Outcome: MSG ID 21 ‘PRESENT CARD AGAIN’ is correctly displayed during 10 seconds before the display of the MSG ID 03 ‘Approved’ at end of the transaction

2EA.012.00 User Interface Request using Language Preference

Test No: - Revision 2.6a - Number of sub cases: n (where n = Number of Language supported according to ICS)

Objective: To ensure that If Language Preference is supported by the terminal and the UI Request includes Language Preference, and the reader and/or terminal support the language, then the message and all subsequent messages to the user shall be displayed in this language until the transaction concludes.

Reference Book A – version 2.6 - Requirement 8.1.1.17 BOOK A/B:

Terminal [Language Preference] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [LTsetting1.70] (Language preference = Language 1, Outcome ‘Approved’ with UI Request ‘Approved’ and) and Amount = 2 • Case02: Entry Point transaction is performed with [LTsetting1.71] (Language preference = Language 2, 1st Outcome ‘Try Again’ with UI Request ‘See Phone for Instructions ‘, 2nd Outcome ‘Declined’ with UI Request ‘Not Authorized’) and Amount = 2 • .. • Case x: Entry Point transaction is performed with [LTsetting1.7x] (Language preference = Language x, Outcome ‘Approved’ with UI Request ‘Approved’ and) and Amount = 2 • Case x+1: Entry Point transaction is performed with [LTsetting1.7x+1] (Language preference = Language x+1, 1st Outcome ‘Try Again’ with UI Request ‘See Phone for Instructions ‘, 2nd Outcome ‘Declined’ with UI Request ‘Not Authorized’) and Amount = 2 • .. Action: NA

Procedure: Entry Point transactions are performed for [Termsetting1] with different LT settings (one configuration for each Language Preference supported defined in [List of Language supported]).

Pass Criteria: • Case01: The UI Request on Outcome: MSG ID 03 ‘Approved’ is correctly displayed using the expected Language 1

2EA.012.00 User Interface Request using Language Preference

• Case02: In the first transaction, the UI Request on Outcome is: MSG ID 20 ‘See Phone for Instructions’ and in the second transaction, message MSG ID 07 ‘Not Authorized’ are correctly displayed using the expected Language 2 • .. • Case x: The UI Request on Outcome: MSG ID 03 ‘Approved’ is correctly displayed using the expected Language x • Case x+1: In the first transaction, the UI Request on Outcome is: MSG ID 20 ‘See Phone for Instructions’ and in the second transaction, message MSG ID 07 ‘Not Authorized’ are correctly displayed using the expected Language x+1 • ..

2EA.012.01 User Interface Request using Default Language

Test No: - Revision 2.6a - Number of sub cases: m (where m = total of Language defined in ISO 639-1 – n (Language supported according to ICS))

Objective: To ensure that If Language Preference is supported by the terminal and the UI Request includes Language Preference, and the reader and/or terminal does not support the language, then the message and all subsequent messages to the user shall be displayed in the default language supported according to EMV 4.2.

Reference Book A – version 2.6 - Requirement 8.1.1.17 BOOK A/B: EMV 4.2 Book 3 - Annex A EMV 4.2 Book 4 – section 11.1

Terminal [Language Preference] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [LTsetting7.00] (Language preference = Unsupported Language 1, Outcome ‘Approved’ with UI Request ‘Approved’ and) and Amount = 2 • Case02: Entry Point transaction is performed with [LTsetting7.01] (Language preference = Unsupported Language 2, 1st Outcome ‘Try Again’ with UI Request ‘See Phone for Instructions ‘, 2nd Outcome ‘Declined’ with UI Request ‘Not Authorized’) and Amount = 2 • .. • Case x: Entry Point transaction is performed with [LTsetting7.x] (Language preference = Unsupported Language x, Outcome ‘Approved’ with UI Request ‘Approved’ and) and Amount = 2 • Case x+1: Entry Point transaction is performed with [LTsetting7.x+1] (Language preference = Unsupported Language x+1, 1st Outcome ‘Try Again’ with UI Request ‘See Phone for Instructions ‘, 2nd Outcome ‘Declined’ with UI Request ‘Not Authorized’) and Amount = 2 • .. Action: NA

Procedure: Entry Point transactions are performed for [Termsetting1] with different LT settings (one configuration for each Language Preference not supported in ICS).

2EA.012.01 User Interface Request using Default Language

Pass Criteria: • Case01: The UI Request on Outcome: MSG ID 03 ‘Approved’ is correctly displayed using the default Language • Case02: In the first transaction, the UI Request on Outcome is: MSG ID 20 ‘See Phone for Instructions’ and in the second transaction, message MSG ID 07 ‘Not Authorized’ are correctly displayed using the default Language • .. • Case x: The UI Request on Outcome: MSG ID 03 ‘Approved’ is correctly displayed using the default Language • Case x+1: In the first transaction, the UI Request on Outcome is: MSG ID 20 ‘See Phone for Instructions’ and in the second transaction, message MSG ID 07 ‘Not Authorized’ are correctly displayed using the default Language • ..

2EA.013.00 User Interface Request Amount or Balance displayed

Test No: - Revision 2.6a - Number of sub cases: 3

Objective: To ensure that If Amount or Balance display is supported: If the Value Qualifier is present and the Currency Code is recognized, the value shall be displayed in conjunction with the message as follows. • If Value Qualifier is "Amount", the Value shall be displayed as the transaction amount. • If Value Qualifier is "Balance", the Value shall be displayed as a balance. • In both cases, the Value shall be represented according to the Currency Code as described in ISO 4217 with leading zeros suppressed whilst leaving at least one significant digit.

Reference Book A – version 2.6 - Requirement 8.1.1.18 BOOK A/B:

Terminal [Amount/Balance display] and [Value Qualifier] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [LTsetting1.80] (Outcome ‘Approved’ with UI Request ‘Approved’ Value Qualifier = ’Amount’, currency Code is supported by the terminal and decimal value = 1.23) and Amount Authorized = 2

• Case02: Entry Point transaction is performed with [LTsetting1.81] (Outcome ‘Approved (with balance)’ with UI Request ‘Approved’, Value Qualifier = ’Balance’, currency Code is supported by the terminal and decimal value = 0.12) and Amount Authorized = 2 • Case03: Entry Point transaction is performed with [LTsetting1.82] (Outcome ‘Approved’ with UI Request ‘Approved’ Value Qualifier = ’Amount’, currency Code is supported by the terminal and integer value = 123456) and Amount Authorized = 2

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with different LT settings.

Pass Criteria: • Case01: The UI Request on Outcome: MSG ID 03 ‘Approved’ is correctly displayed and the value 1.23 is displayed as an amount. • Case02: The UI Request on Outcome: MSG ID 03 ‘Approved’ is correctly displayed and the value 0.12 is displayed as a balance.

2EA.013.00 User Interface Request Amount or Balance displayed

• Case03: The UI Request on Outcome: MSG ID 03 ‘Approved’ is correctly displayed and the value 123456 is displayed as an amount.

2EA.013.01 User Interface Request Amount or Balance displayed (2)

Test No: - Revision 2.6a - Number of sub cases: n (where n correspond to the number of currency code present in the ICS)

Reference Book A – version 2.6 - Requirement 8.1.1.18 BOOK A/B:

Terminal [Amount/Balance display] and [Value Qualifier] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [LTsetting8.00] (Outcome ‘Approved (with balance)’ with UI Request ‘Approved’, Value Qualifier = ’Balance’, currency Code 1 present in the ICS is supported by the terminal integer value = 1234) and Amount Authorized = 2 • … • Case n: Entry Point transaction is performed with [LTsetting8.n] (Outcome ‘Approved (with balance)’ with UI Request ‘Approved’, Value Qualifier = ’Balance’, currency Code n present in the ICS is supported by the terminal integer value = 1234) and Amount Authorized = 2 Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with different LT settings

Pass Criteria: • The UI Request on Outcome: MSG ID 03 ‘Approved’ is correctly displayed and the value 1234 is displayed as a balance.

2EA.014.00 Restart after an Outcome (Response with EMV data)

Test No: - Revision 2.6a - Number of sub cases: 5

Objective: To ensure that the reader shall retain the following Final Outcome parameters for the duration of a transaction (in case required for a restart): • Start • Online Response Data • UI Request on Re-start Present and if 'Yes', the associated User Interface Request To ensure that if the Outcome Parameter Start has a value other than NA, the reader shall set the Restart flag to 1.

To ensure that if the Removal Timeout parameter has a value other than zero, then the reader shall start a timeout function using the value of the parameter and clear (to 0) the timeout indicator. When the reader is informed by the terminal of the results of an online authorisation request, it shall stop the timeout function. Test is done for a Restart A, B, C and D.

Reference Book A – version 2.6 - Requirement 8.1.1.19, 8.1.1.20, 8.1.1.21, BOOK A/B: 8.1.1.22

Terminal NA Configuration:

Conditions: • Case02: Entry Point transaction is performed with [LTsetting1.11] (1st Outcome Start = ’B’, ‘Online Request’, online response data = ‘EMV Data’, UI Request on restart = Yes, Issuer Script Data (tag 71) are received)

• Case03: Entry Point transaction is performed with [LTsetting1.22] (1st Outcome Start = ’C’, ‘Online Request’, online response data = ‘EMV Data’, UI Request on restart = No and Issuer Script Data (tag 72) are received)

• Case04: Entry Point transaction is performed with [LTsetting1.13] (1st Outcome Start = ’D’, ‘Online Request’, online response data = ‘EMV Data’, UI Request on restart = Yes, Issuer Authentication Data (tag 91) and Issuer Script Data (tag 71) are received)

• Case05: Entry Point transaction is performed with [LTsetting1.27] (1st Outcome Start = ’C’, ‘Online Request’, online response data = ‘EMV Data’, UI Request on restart = No and Issuer Authentication Data (tag 91) and Issuer Script Data (tag 72) received)

2EA.014.00 Restart after an Outcome (Response with EMV data)

• Case06: Entry Point transaction is performed with [LTsetting1.99] (1st Outcome Start = ’D’, ‘Online Request’, online response data = ‘EMV Data’, UI Request on restart = Yes, Issuer Authentication Data (tag 91) and Issuer Script Data (tag 72) are received)

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with different LT settings.

Pass Criteria: • Case02: The UI Request on restart: MSG ID 21 ‘Present Card Again’ is correctly displayed at restart. • Case02: At restart, the LT shall receive the Select AID ‘A0000000020002’ (corresponding to the the APP2 AID) without a previous SELECT command with PPSE • Case02: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set). • Case02: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Start is set to ‘B’ • Case02: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Issuer Script Data (tag 71) are set with the value transmitted • Case03: At restart, the LT shall receive the Select AID ‘A0000000030003’ (corresponding to the the APP3 AID) without a previous SELECT command with PPSE • Case03: The LT shall receive in the 2Nd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set). • Case03: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Start is set to ‘C’ • Case03: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Issuer Script Data (tag 72) are set with the value transmitted • Case04: The UI Request on restart: MSG ID 16 ‘PROCESSING’ is correctly displayed at restart. • Case04: The LT shall not receive the SELECT command with PPSE at restart

2EA.014.00 Restart after an Outcome (Response with EMV data)

• Case04: The LT shall not receive the SELECT AID ‘A0000000040004’ (corresponding to the APP4 AID) at restart • Case04: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set). • Case04: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Start is set to ‘D’ • Case04: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Issuer Authentication Data are set with the value transmitted • Case04: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Issuer Script Data (71) are set with the value transmitted • Case05: At restart, the LT shall receive the SELECT AID ‘A0000000030003’ (corresponding to the the APP3 AID) without a previous SELECT command with PPSE • Case05: The LT shall receive in the 2Nd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set). • Case05: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Start is set to ‘C’ • Case05: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Issuer Script Data (tag 72) are set with the value transmitted • Case06: The UI Request on restart: MSG ID 16 ‘PROCESSING’ is correctly displayed at restart. • Case06: The LT shall not receive the SELECT command with PPSE at restart • Case06: The LT shall not receive the SELECT AID ‘A0000000040004’ (corresponding to the APP4 AID) at restart • Case06: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set). • Case06: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Start is set to ‘D’

2EA.014.00 Restart after an Outcome (Response with EMV data)

• Case06: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Issuer Authentication Data are set with the value transmitted • Case06: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Issuer Script Data (72) are set with the value transmitted

2EA.014.01 Restart after an Outcome (card removed)

Test No: - Revision 2.6a - Number of sub cases: 0

Objective: To ensure that the reader shall retain the following Final Outcome parameters for the duration of a transaction in case required for a restart after the card has been removed: • Start • UI Request on Re-start Present and if 'Yes', the associated User Interface Request To ensure that if the Outcome Parameter Start has a value other than NA, the reader shall set the Restart flag to 1.

To ensure that if the Removal Timeout parameter has a value other than zero, then the reader shall start a timeout function using the value of the parameter and clear (to 0) the timeout indicator. When the reader is informed that the cad is removed, it shall stop the timeout function. Test is done for a Restart A, B.

Reference Book A – version 2.6 - Requirement 8.1.1.19, 8.1.1.20, 8.1.1.21, BOOK A/B: 8.1.1.23

Terminal NA Configuration:

Conditions: • Case02: Entry Point transaction is performed with [LTsetting1.35] (1st Outcome Start = ’B’, ‘Restart on card removed’, UI Request on restart = Yes)

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with different LT settings.

Pass Criteria: • Case02: The UI Request on restart: MSG ID 21 ‘Present Card Again’ is correctly displayed at restart. • Case02: The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000020002’ (corresponding to the APP2 AID) at restart • Case02: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set).

2EA.014.01 Restart after an Outcome (card removed)

• Case02: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Start is set to ‘B’

2EA.015.00 Removal Timeout set and timeout occurs

Test No: - Revision 2.6a - Number of sub cases: 3

Objective: To ensure that If the Removal Timeout parameter has a value other than zero, then the reader shall start a timeout function using the value of the parameter and clear (to 0) the timeout indicator. If the timeout occurs, the reader shall: • Send a User Interface Request • Message Identifier: ‘17’ ("CARD READ OK. PLEASE REMOVE CARD") • Status: ‘Card Read Successfully’ set (to 1) the timeout indicator for the kernelTest is done for a Restart A, B, C and D.

Reference Book A – version 2.6 - Requirement 8.1.1.21 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case02: Entry Point transaction is performed with [LTsetting1.18] (Restart = Start B and Removal Timeout expired) • Case03: Entry Point transaction is performed with [LTsetting1.28] (Restart = Start C and Removal Timeout expired) • Case04: Entry Point transaction is performed with [LTsetting1.24] (Restart = Start D and Removal Timeout expired) Action:

Procedure: An Entry Point transaction is performed with restart sequence for [Termsetting1] with different LT settings.

Pass Criteria: • The UI Request on Restart: MSG ID 17 ‘CARD READ OK. PLEASE REMOVE CARD"’ is correctly displayed when timeout occurs (10 seconds)

2EA.016.00 Restart after an Outcome (Online Response Data parameter set to ANY)

Test No: - Revision 2.6a - Number of sub cases: 6

Objective: To ensure that the reader shall activate Entry Point at the start position indicated by the retained Start parameter when: • the Online Response Data parameter is ANY, Test is done for a Restart A, B, C and D.

Reference Book A – version 2.6 - Requirement 8.1.1.22 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case02: Entry Point transaction is performed with [LTsetting1.21] (1st Outcome Start = ’B’, ‘Online Request’, online response data = ‘ANY’, no issuer data received)

• Case03: Entry Point transaction is performed with [LTsetting1.7] (1st Outcome Start = ’C’, ‘Online Request’, online response data = ‘ANY’, no issuer data received)

• Case04: Entry Point transaction is performed with [LTsetting1.23] (1st Outcome Start = ’D’, ‘Online Request’, online response data = ‘ANY’, no issuer data received)

• Case06: Entry Point transaction is performed with [LTsetting1.25] (1st Outcome Start = ’B’, ‘Online Request’, online response data = ‘ANY’, Issuer Script Data (tag 71) received)

• Case07: Entry Point transaction is performed with [LTsetting1.8] (1st Outcome Start = ’C’, ‘Online Request’, online response data = ‘ANY’, and Issuer Authentication Data (tag 91) and Issuer Script Data (tag 71) received)

• Case08: Entry Point transaction is performed with [LTsetting1.29] (1st Outcome Start = ’D’, ‘Online Request’, online response data = ‘ANY’, and Issuer Authentication Data (tag 91) and Issuer Script Data (tag 72) received)

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with different LT settings.

2EA.016.00 Restart after an Outcome (Online Response Data parameter set to ANY)

Pass Criteria: • Case02: The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000020002’ (corresponding to the APP2 AID) before and after restart • Case02: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set). • Case02: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Start is set to ‘B’ • Case03: The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000030003’ (corresponding to the APP3 AID) before restart • Case03: At restart, the LT shall receive the SELECT AID ‘A0000000030003’ (corresponding to the APP3 AID) without any select command for PPSE • Case03: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set). • Case03: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Start is set to ‘C’ • Case04: The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000040004’ (corresponding to the APP4 AID) before restart • Case04: The LT shall not receive the SELECT command with PPSE at restart • Case04: The LT shall not receive the SELECT AID ‘A0000000040004’ (corresponding to the APP4 AID) at restart • Case04: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set). • Case04: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Start is set to ‘D’ • Case06: The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000020002’ (corresponding to the APP2 AID) before restart

2EA.016.00 Restart after an Outcome (Online Response Data parameter set to ANY)

• Case06: At restart, the LT shall receive the SELECT AID ‘A0000000020002’ (corresponding to the APP2 AID) without any select command for PPSE • Case06: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set). • Case06: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Start is set to ‘B’ • Case07: The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000030003’ (corresponding to the APP3 AID) before restart • Case07: At restart, the LT shall receive the SELECT AID ‘A0000000030003’ (corresponding to the APP3 AID) without any select command for PPSE • Case07: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set). • Case07: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Start is set to ‘C’ • Case08: The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000040004’ (corresponding to the APP4 AID) before restart • Case08: The LT shall not receive the SELECT command with PPSE at restart • Case08: The LT shall not receive the SELECT AID ‘A0000000040004’ (corresponding to the APP4 AID) at restart • Case08: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set). • Case08: The LT shall receive in the 2nd GET PROCESSING OPTIONS data field: Start is set to ‘D’

2EA.017.00 RFU bytes and bits

Test No: - Revision 2.6a - Number of sub cases: 3

Objective: To ensure that the reader shall ignore the value of a bit specified as RFU and shall not change its behaviour, unless explicitly stated otherwise.

The data concerned by the tests are:

o Application Priority Indicator o Kernel ID

o TTQ

Reference Book A – version 2.5 - Requirement 8.1.1.9 Book A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed for [Termsetting3] (APP3 AID has the priority indicator set to ‘41’ (highest priority with RFU bits set) and kernel ID = ’2102030405060708’ (RFU bits set)) • Case02: Entry Point transaction is performed for [Termsetting2] (APP2 AID has the priority indicator set to ‘F2’ (highest priority with RFU bits set) and kernel ID = ’24FFFF’ (RFU bits set)) and amount = 121 • Case03: Entry Point transaction is performed for [Termsetting8] (APP3 AID has the priority indicator set to ‘41’ (highest priority with RFU bits set) and kernel ID = ’2102030405060708’ (RFU bits set)) and amount = 2 Action: NA

Procedure: Entry Point transaction is performed for different Term settings with [LTsetting6.10].

Pass Criteria: • Case01: The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000030003’ (corresponding to the APP3 AID) • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 = 21

2EA.017.00 RFU bytes and bits

• Case02: The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000020002’ (corresponding to the APP2 AID) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 = 24 • Case03: The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000030003’ (corresponding to the APP3 AID) • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 = 21 • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ = ‘F72A8A55’

2EA.017.01 RFU bytes and bits (2)

Test No: - Revision 2.6a - Number of sub cases: 0

Objective: To ensure that the reader shall ignore the value of a bit specified as RFU and shall not change its behaviour, unless explicitly stated otherwise.

The data concerned by the tests are:

o Application Priority Indicator o Kernel ID

o TTQ

Reference Book A – version 2.5 - Requirement 8.1.1.9 Book A/B:

Terminal NA Configuration:

Conditions: • Entry Point transaction is performed with amount = 2 Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with [LTsetting2.10].

Pass Criteria: • The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000030003’ (corresponding to the the APP3 AID) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 = 21 • The LT shall receive in the GET PROCESSING OPTIONS data field: FCI with Application Priority Indicator = ’01’ • The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ = ‘B6208000’

2EA.018.00 Presence of Data ignored

Test No: - Revision 2.4a - Number of sub cases: 0

Objective: To ensure that If Entry Point or a Kernel encounters a data object from the card that is designated as terminal or reader sourced; it shall ignore the data object and continue the transaction as if it had not been present.

To ensure that if Entry Point or a Kernel encounters a data object from the card that is not recognized, it shall be ignored and the transaction shall continue as if it had not been present.

Reference Book B – version 2.3 - Requirement 3.6.1.1, 3.6.1.2 BOOK A/B:

Terminal NA Configuration:

Conditions: Entry Point transaction is performed with entry of amount = 2, amount Other = 0,

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with [LTsetting6.11] (Select response with presence of Amount Authorized (tag 9F02, value = ’102030405060’, Amount Other (tag 9F03 value ‘010203040506’, Unpredictable Number (tag 9F37, value ‘11223344’), Unknown tag (DF01, value ‘FF’), Unknown tag (C1, value EE‘EE’), Unknown tag (85, value ‘DD’), Unknown tag (9F25, value ‘CCCC’))

Pass Criteria: • The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000010001’ (corresponding to the the APP1 AID) • The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Authorized = 2 • The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Other = 0 • The LT shall receive in the GET PROCESSING OPTIONS data field: Unpredictable Number is different from ‘11223344’ • The LT shall receive in the GET PROCESSING OPTIONS data field: DF01 value set to ‘00’ • The LT shall receive in the GET PROCESSING OPTIONS data field: C1 value set to ‘0000’

2EA.018.00 Presence of Data ignored

• The LT shall receive in the GET PROCESSING OPTIONS data field: 85 value set to ‘00’ • The LT shall receive in the GET PROCESSING OPTIONS data field: 9F25 value set to ‘0000’

2EA.019.00 Receipt

Test No: - Revision 2.5a - Number of sub cases: 4

Objective: To ensure that If If a receipt is required the terminal shall provide it, with a signature line if CVM signature requested in the Outcome at First Final Outcome or at Second Final Outcome (following an online request) Approved (only relevant for parameter Start = D).

Reference Book A – version 2.5 - Requirement 6.3 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [LTsetting1.5] (Outcome, ‘Approved’, Receipt = Yes, CVM = No CVM) and Amount = 2 • Case02: Entry Point transaction is performed with [LTsetting1.6] (Outcome, ‘Approved’, Receipt = Yes, CVM = Obtain Signature) and Amount = 2 • Case03: Entry Point transaction is performed with [LTsetting1.14] (1st Outcome Start = ’D’, ‘Online Request’, online response data = ‘EMV Data’, UI Request on restart = No, and 2nd Outcome, ‘Approved’, Receipt = Yes, CVM = No CVM and Issuer Authentication Data are received) • Case04: Entry Point transaction is performed with [LTsetting1.13] (1st Outcome Start = ’D’, ‘Online Request’, online response data = ‘EMV Data’, UI Request on restart = No, and 2nd Outcome, ‘Approved’, Receipt = Yes, CVM = Obtain Signature) and Issuer Authentication Data are received Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with different LT settings

Pass Criteria: • a receipt is provided at end of transaction

2EA.020.00 Padding

Test No: - Revision 2.4a - Number of sub cases: 2

Objective: To ensure that the reader shall apply padding according to the format of the data elements and the rules as defined in [N1] Annex B.

Reference Book B – version 2.3 - Requirement 3.6.2.1 BOOK A/B:

Terminal NA Configuration:

Conditions: o Case01: Entry Point transaction is performed with amount = 2, and [LTsetting6.12] (single padding byte ‘00’ in template 6F and A5 of the Select PPSE response and Select ADF response, set in PDOL with data object length higher than standard length: ‘Amount Authorized (tag 9F02) with length = 7, Unpredictable Number (tag 9F37) with length = 5, Terminal Identification with length = , Merchant Identifier with length =16)

o Case02: Entry Point transaction is performed with amount = 2, and [LTsetting6.13] (10 padding bytes ‘00’ in template 6F and A5 of the Select PPSE response and Select ADF response, set in PDOL with data object length higher than standard length: ‘Amount Authorized (tag 9F02) with length = 16, Unpredictable Number (tag 9F37) with length = 14, Terminal Identification with length = 18, Merchant Identifier with length = 25)

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with different LT settings.

Pass Criteria: • Case01: The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000020002’ (corresponding to the APP2 AID) • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Authorized =’00000000000002’ • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Unpredictable Number with the last byte set to ‘00’ • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Terminal Identification with the last byte set to ‘00’

2EA.020.00 Padding

• Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Merchant Identifier with the last byte set to ‘00’ • Case02: The LT shall receive the SELECT command with PPSE before the Select AID ‘A0000000040004’ (corresponding to the the APP4 AID) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Amount Authorized = ’00000000000000000000000000000002’ • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Unpredictable Number with the last 10 bytes set to ‘00’ • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Terminal Identification with the last 10 bytes set to ‘00’ • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Merchant Identifier with the last 10 bytes set to ‘00’

2EA.021.00 Order of Data Elements

Test No: - Revision 2.4a - Number of sub cases: 0

Objective: To ensure that the reader shall accept TLV data elements in any order

Reference Book B – version 2.3 - Requirement 3.6.3.1 BOOK A/B:

Terminal NA Configuration:

Conditions: Entry Point transaction is performed with amount = 2

Action: NA

Procedure: • Entry Point transaction is performed for [Termsetting1] with [LTsetting6.14] (tag 84 after template A5 in template 6F of the Select PPSE response and Select ADF response, and standard tag order inverted in template A5 of Select ADF response)

2EA.022.00 EMVCO Contactless Symbol Compliance

Test No: - Revision 2.6a - Number of sub cases: 0

Objective: To ensure that the Contactless Product comply with the EMVCo Contactless Symbol agreement rules.

Reference Contactless Symbol Reproduction Requirement – version 20 Nov 2016 BOOK A/B:

Terminal NA Configuration:

Conditions: NA

Action: NA

Procedure: • Verify that the Contactless Product features a correct EMV Contactless symbol as defined in the specifications. All the following items shall be verified:

§ The symbol drawing shows the contactless indicator (four semicircle lines from smallest to largest in size, left to right) at the center of the symbol, the hand holding a generic contactless form factor device and an oval key line that wraps the indicator and the hand.

§ The drawing is in white reversed line drawing against any medium to dark background, or in black line drawing against a white or light- colored background.

§ The background is a solid color. It does not feature any graphic pattern.

§ No additional nor modified item is present.

§ The minimum size of the symbol is 13 mm height by 22 mm width.

§ The size of the symbol features a 13/22 height/width ratio.

§ A clear space band having a width of at least a quarter of the height of the symbol exists all around the four sides of the contactless symbol. No other text or graphic element appears in this zone.

0.25 x

x 0.25 0.25 x x

0.25 x

§ The symbol is not rotated nor flipped. The hand is present on the right side of the symbol.

§ There is no text message with the symbol.

PAY HERE

The appropriate section of the test report must be filled with the results of this verification.

2EA.022.00 EMVCO Contactless Symbol Compliance

Pass Criteria: • Contactless Symbol shall be present • Contactless Symbol shall comply to the above verifications • Test report shall include the verification done in this test.

9.2. Pre-processing

2EB.001.00 All Pre-Processing indicators set to zero at beginning of Pre-Processing

Test No: - Revision 2.3a – Number of sub cases: 5

Objective: To ensure that at the start of the Pre-Processing the Entry Point shall clear (to 0) all Pre-Processing indicators: • Status Check Requested • Contactless Application not Allowed • Zero Amount • Reader CVM Required Limit Exceeded • Reader Contactless Floor Limit Exceeded. Reference Book A – version 2.3 – Requirement 8.1.1.2 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.1

Terminal NA Configuration:

Conditions: • Case01: First Entry Point transaction is performed with [Ltsetting1.1] with Amount = Single Unit of Currency • Case01: Second Entry Point transaction is performed with [Ltsetting1.1] with Amount = 2 • Case02: First Entry Point transaction is initialized with [Ltsetting1.2] with Amount Authorized = 121 (greater than the Reader Contactless Transaction Limit) • Case02: Second Entry Point transaction is performed with [Ltsetting1.2] with Amount = 2 • Case03: First Entry Point transaction is performed with [Ltsetting1.3] with Amount = 0 • Case03: Second Entry Point transaction is performed with [Ltsetting1.3] with Amount = 2 • Case04: First Entry Point transaction is performed with [Ltsetting1.4] with Amount Authorized = 16 (greater than the Reader CVM Required Limit and also greater than the Reader Contactless Floor Limit) • Case04: Second Entry Point transaction is performed with [Ltsetting1.4] with Amount = 2

2EB.001.00 All Pre-Processing indicators set to zero at beginning of Pre-Processing

• Case05: First Entry Point transaction is performed with [Ltsetting1.97] with Amount Authorized = 13 (greater than the Reader Contactless Floor Limit) • Case05: Second Entry Point transaction is performed with [Ltsetting1.97] with Amount = 2 Action: NA

Procedure: • A first Entry Point transaction is performed for [Termsetting1] with different LT settings, to set a single Pre-Processing indicator. • A second Entry Point transaction is performed for [Termsetting1] with different LT settings, to check that all Pre-Processing indicators are set to 0.

Pass Criteria: st • Case01: 1 Entry Point transaction: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): Byte 1 bit 5 set to ‘1b’ • Case03: 1st Entry Point transaction: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): set to value ’08 00’. • Case04: 1st Entry Point transaction: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): set to value ‘A0 00’. • Case05: 1st Entry Point transaction: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): set to value ’80 00’. • 2nd Entry Point transaction: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): set to value ’00 00’.

2EB.002.00 Terminal Transaction Qualifier set in Entry Point configuration copied during Pre-Processing

Test No: - Revision 2.6a – Number of sub cases: 3

Objective: To ensure that at the start of the Pre-Processing, the terminal shall copy the Terminal Transaction Qualifiers and reset byte 2, bit 8 and bit 7 in the Copy of TTQ to 00b (‘Online cryptogram not required’ and ‘CVM not required’). To ensure that the reader shall ignore the value of a bit specified as RFU and shall not change its behavior: for TTQ data.

Reference Book A – version 2.3 – Requirement 8.1.1.2 BOOK A/B: Book B – version 2.3 – Requirement 8.1.1.9

Book B – version 2.3 – Requirement 3.1.1.2

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and [Ltsetting1.2] with Amount = 2 • Case02: Entry Point transaction is performed with [Termsetting2] and [Ltsetting1.1] with Amount = 2 • Case03: Entry Point transaction is performed with [Termsetting2] and [Ltsetting1.4] with Amount = 2 Action:

Procedure: A Entry Point transaction is performed for different Term settings with different LT settings

Pass Criteria: • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ (tag ‘9F 66’) = ‘B6208000’ (byte 2 bits 8-7 set to value ‘00’ all others bits from TTQ are identical to preset values). • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ (tag ‘9F 66’) = ‘28000F00’ (byte 2 bits 8- 7 set to value ‘00’ all others bits from TTQ are identical to preset values, including RFU bits). • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ (tag ‘9F 66’) = ‘C4008000’ (byte 2 bits

2EB.002.00 Terminal Transaction Qualifier set in Entry Point configuration copied during Pre-Processing

8-7 set to value ‘00’ all others bits from TTQ are identical to preset values, including RFU bits).

2EB.003.00 Status Check present and set, Amount = 1

Test No: - Revision 2.3a – Number of sub cases: 5

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Status Check Support flag is present and set and if the Amount, Authorised is a single unit of currency, then the terminal shall set the Pre-Processing internal flag ‘Status Check Requested’ for the AID To ensure that if TTQ is present in the combination, and If the ‘Status Check Requested’ indicator is set to 1, then Entry Point shall set byte 2, bit 8 in the Copy of TTQ for the Combination to 1b (‘Online cryptogram required’).

Reference Book B – version 2.3 – Requirement 3.1.1.3, 3.1.1.10 BOOK A/B:

Terminal [Status Check] supported Configuration:

Conditions: • Case01: For [Termsetting1] with [Ltsetting1.2], Entry Point transaction is performed with Amount set to a single unit of currency • Case02: For [Termsetting2] with [Ltsetting1.1], Entry Point transaction is performed with Amount set to a single unit of currency • Case03: For [Termsetting2] with [Ltsetting2.1], Entry Point transaction is performed with Amount set to a single unit of currency • Case04: For [Termsetting2] with [Ltsetting2.3], Entry Point transaction is performed with Amount set to a single unit of currency • Case05: For [Termsetting1] with [Ltsetting1.97], Entry Point transaction is performed with Amount set to a single unit of currency Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 5 set to ‘1b’

2EB.003.00 Status Check present and set, Amount = 1

• Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘1b’ • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘1b’ • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘1b’ • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘1b’

2EB.003.01 Status Check present and set, Amount = 1 and Transaction Type ‘Purchase’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Status Check Support flag is present for the Transaction Type ‘Purchase’ and set and if the Amount, Authorised is a single unit of currency, then the terminal shall set the Pre-Processing internal flag ‘Status Check Requested’ for the AID

To ensure that if TTQ is present in the combination, and If the ‘Status Check Requested’ indicator is set to 1, then Entry Point shall set byte 2, bit 8 in the Copy of TTQ for the Combination to 1b (‘Online cryptogram required’).

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.3, 3.1.1.10

Terminal [Status Check] and [Purchase] supported Configuration:

Conditions: Amount set to a single unit of currency and Transaction Type = ’Purchase’ (00) Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.1].

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 5 set to ‘1b’ • The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘1b’

2EB.003.02 Status Check present and set, Amount = 1 and Transaction Type ‘Refund’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Status Check Support flag is present for the Transaction Type ‘Refund’ and set and if the Amount, Authorised is a single unit of currency, then the terminal shall set the Pre-Processing internal flag ‘Status Check Requested’ for the AID

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.3

Terminal [Status Check] and [Refund] supported Configuration:

Conditions: Amount set to a single unit of currency and Transaction Type = ’Refund’ (20) Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.4].

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 5 set to ‘1b’

2EB.004.00 Status Check present and not set

Test No: - Revision 1 – Number of sub cases: 3

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Status Check Support flag is present and not set and if the Amount, Authorised is a single unit of currency, then the terminal shall not set the Pre-Processing internal flag ‘Status Check Requested’ for the AID

Reference Book B – version 2.3 – Requirement 3.1.1.3 BOOK A/B:

Terminal [Status Check] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Ltsetting1.2] with Amount set to a single unit of currency • Case02: Entry Point transaction is performed with [Ltsetting1.89] with Amount set to a single unit of currency • Case03: Entry Point transaction is performed with [Ltsetting2.2] with Amount set to a single unit of currency Action: NA

Procedure: Entry Point transactions are performed for [Termsetting2] with different LT settings.

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 5 set to ‘0b’

2EB.004.01 Status Check present and not set with Transaction Type ‘Purchase’

Test No: - Revision 2.3a – Number of sub cases: 2

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Status Check Support flag is present and not set and Transaction Type ‘Purchase’ and if the Amount, Authorised is a single unit of currency, then the terminal shall not set the Pre-Processing internal flag ‘Status Check Requested’ for the AID

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.3

Terminal [Status Check] and [Purchase] supported Configuration:

Conditions: Case01: Entry Point transaction is performed with [LTsetting1.2] with an amount set to a single unit of currency and Transaction Type = ’Purchase’ (00) Case02: Entry Point transaction is performed with [LTsetting1.97] with an amount set to a single unit of currency and Transaction Type = ’Purchase’ (00) Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with different LT settings

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 5 set to ‘0b’

2EB.004.02 Status Check present and not set with Transaction Type ‘Cash Advance’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Status Check Support flag is present and not set and Transaction Type ‘Cash Advance’ and if the Amount, Authorised is a single unit of currency, then the terminal shall not set the Pre- Processing internal flag ‘Status Check Requested’ for the AID

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.3

Terminal [Status Check] and [Cash Advance] supported Configuration:

Conditions: Amount set to a single unit of currency, and Transaction Type = ’Cash Advance’ (01) Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.1]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 5 set to ‘0b’

2EB.005.00 Status Check not present

Test No: - Revision 2.3a – Number of sub cases: 3

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Status Check Support flag is supported but not present et and if the Amount, Authorised is a single unit of currency, then the terminal shall not set the Pre-Processing internal flag ‘Status Check Requested’ for the AID

Reference Book B – version 2.3 – Requirement 3.1.1.3 BOOK A/B:

Terminal [Status Check] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Ltsetting1.3] with Amount set to a single unit of currency • Case02: Entry Point transaction is performed with [Ltsetting1.4] with Amount set to a single unit of currency • Case03: Entry Point transaction is performed with [Ltsetting1.97] with Amount set to a single unit of currency Action: NA

Procedure: Entry Point transactions are performed for [Termsetting2] with different LT settings.

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 5 set to ‘0b’

2EB.005.01 Status Check not present and Transaction Type ’Purchase’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Status Check Support flag is supported but not present and Transaction Type ‘Purchase’ and if the Amount, Authorised is a single unit of currency, then the terminal shall not set the Pre- Processing internal flag ‘Status Check Requested’ for the AID

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.3

Terminal [Status Check] and [Purchase] supported Configuration:

Conditions: Amount set to a single unit of currency and Transaction Type = ’Purchase’ (00) Action: NA

Procedure: Entry Point transactions are performed for [Termsetting4] (Purchase transaction) with [Ltsetting1.3]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 5 set to ‘0b’

2EB.006.00 Status Check present and set, Amount different from 1

Test No: - Revision 2.3a – Number of sub cases: 5

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Status Check Support flag is present and set and if the Amount, Authorised is not a single unit of currency, then the terminal shall not set the Pre-Processing internal flag ‘Status Check Requested’ for the AID To ensure that if TTQ is present in the combination, and If the ‘Status Check Requested’ indicator is set to 0, then Entry Point shall set byte 2, bit 8 in the Copy of TTQ for the Combination to 0b (No ‘Online cryptogram required’).

Reference Book B – version 2.3 – Requirement 3.1.1.3, 3.1.1.10 BOOK A/B:

Terminal [Status Check] supported Configuration:

Conditions: • Case01: For [Termsetting1] with [Ltsetting1.2], Entry Point transaction is performed with Amount not set to a single unit of currency (Amount = 2) • Case02: For [Termsetting2] with [Ltsetting1.1], Entry Point transaction is performed with Amount not set to a single unit of currency (Amount = 2) • Case03: For [Termsetting2] with [Ltsetting2.1], Entry Point transaction is performed with Amount not set to a single unit of currency (Amount = 2) • Case04: For [Termsetting2] with [Ltsetting2.3], Entry Point transaction is performed with Amount not set to a single unit of currency (Amount = 2) • Case05: For [Termsetting1] with [Ltsetting1.97], Entry Point transaction is performed with Amount not set to a single unit of currency (Amount = 2) Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 5 set to ‘0b’

2EB.006.00 Status Check present and set, Amount different from 1

• Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘0b’ • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘0b’ • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘0b’ • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘0b’

2EB.006.01 Status Check present and set, Amount different from 1 with Transaction Type ‘Purchase’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Status Check Support flag is present and Transaction Type ‘Purchase’ and set and if the Amount, Authorised is not a single unit of currency, then the terminal shall not set the Pre-Processing internal flag ‘Status Check Requested’ for the AID

To ensure that if TTQ is present in the combination, and If the ‘Status Check Requested’ indicator is set to 0, then Entry Point shall set byte 2, bit 8 in the Copy of TTQ for the Combination to 0b (No ‘Online cryptogram required’).

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.3, 3.1.1.10

Terminal [Status Check] and [Purchase] supported Configuration:

Conditions: Amount not set to a single unit of currency (Amount = 2) and Transaction Type = ’Purchase’ (00) Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.1]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 5 set to ‘0b’ • The LT shall receive in the GET PROCESSING OPTIONS data field TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘0b’

2EB.007.00 Zero Amount not allowed

Test No: - Revision 2.4a – Number of sub cases: 2

Objective: To ensure that when Zero Amount Flag is present and set to 0 for a combination, and the Amount Authorized is set to 0, Entry Point shall set the ’Contactless Application Not Allowed’ indicator for the Combination to 1

Reference Book B – version 2.3 – Requirement 3.1.1.4 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: An amount authorized of 0 is entered. • Case02: An amount authorized of 2 is entered. Action: NA

Procedure: Entry Point transaction is performed for [Termsetting2] with [Ltsetting2.42]

Pass Criteria: • Case01: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000020002), • Case02: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000030003),

2EB.007.01 Zero Amount not allowed with Transaction Type ‘Purchase’

Test No: - Revision 2.4a – Number of sub cases: 2

Objective: To ensure that when Zero Amount Flag is present and set to 0 for a combination and Transaction Type ‘Purchase’ and the Amount Authorized is set to 0, Entry Point shall set the ’Contactless Application Not Allowed’ indicator for the Combination to 1

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.4

Terminal [Purchase] supported Configuration:

Conditions: • Case01: An amount authorized of 0 is entered with Transaction Type = ’Purchase’ (00) • Case02: An amount authorized of 2 is entered with Transaction Type = ’Purchase’ (00) Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting2.4].

2EB.008.00 Zero Amount allowed

Test No: - Revision 2.3a – Number of sub cases: 4

Objective: To ensure that when Zero Amount Flag is present and set to 1 for a combination, Entry Point shall set the ’Zero Amount’ indicator for the Combination to 1 when Amount Authorized is set to 0.

To ensure that when Zero Amount Flag is present and set to 1 for a combination, Entry Point shall set the ’Zero Amount’ indicator for the Combination to 0 when Amount Authorized is not set to 0.

Reference Book B – version 2.3 – Requirement 3.1.1.4 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [LTsetting1.1] with an amount authorized of 0 is entered. • Case02: Entry Point transaction is performed with [LTsetting1.1] with an amount authorized of 2 is entered. • Case03: Entry Point transaction is performed with [LTsetting1.97] with an amount authorized of 0 is entered. • Case04: Entry Point transaction is performed with [LTsetting1.97] with an amount authorized of 2 is entered. Action: NA

Procedure: Entry Point transactions are performed for [Termsetting1] with different LT settings.

Pass Criteria: • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 4 set to ‘1b’ • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 4 set to ‘0b’ • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 4 set to ‘1b’ • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 4 set to ‘0b’

2EB.008.00 Zero Amount allowed

2EB.008.01 Zero Amount allowed with Transaction Type ‘Purchase’

Test No: - Revision 1 – Number of sub cases: 2

Objective: To ensure that when Zero Amount Flag is present and set to 1 for a combination, and Transaction Type ‘Purchase’, Entry Point shall set the ’Zero Amount’ indicator for the Combination to 1 when Amount Authorized is set to 0.

To ensure that when Zero Amount Flag is present and set to 1 for a combination, and Transaction Type ‘Purchase’, Entry Point shall set the ’Zero Amount’ indicator for the Combination to 0 when Amount Authorized is not set to 0.

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.4

Terminal [Purchase] supported Configuration:

Conditions: • Case01: An amount authorized of 0 is entered and Transaction Type = ’Purchase’ (00). • Case02: An amount authorized of 2 is entered and Transaction Type = ’Purchase’ (00). Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.3]

2EB.008.02 Zero Amount allowed with Transaction Type ‘Refund’

Test No: - Revision 1 – Number of sub cases: 2

Objective: To ensure that when Zero Amount Flag is present and set to 1 for a combination, and Transaction Type ‘Refund’, Entry Point shall set the ’Zero Amount’ indicator for the Combination to 1 when Amount Authorized is set to 0.

To ensure that when Zero Amount Flag is present and set to 1 for a combination, and Transaction Type ‘Refund’, Entry Point shall set the ’Zero Amount’ indicator for the Combination to 0 when Amount Authorized is not set to 0.

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.4

Terminal [Refund] supported Configuration:

Conditions: • Case01: An amount authorized of 0 is entered and Transaction Type = ’Refund’ (20). • Case02: An amount authorized of 2 is entered and Transaction Type = ’Refund’ (20). Action: NA

Procedure: Entry Point transaction is performed [Termsetting4] with [Ltsetting1.4]

2EB.009.00 Zero Amount allowed flag not present

Test No: - Revision 1 – Number of sub cases: 2

Objective: To ensure that when Zero Amount Flag is not present for a combination, Entry Point shall set the ’Zero Amount’ indicator for the Combination to 1 when Amount Authorized is set to 0.

To ensure that when Zero Amount Flag is not present for a combination, Entry Point shall set the ’Zero Amount’ indicator for the Combination to 0 when Amount Authorized is not set to 0.

Reference Book B – version 2.3 – Requirement 3.1.1.4 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: An amount authorized of 0 is entered. • Case02: An amount authorized of 2 is entered Action: NA

Procedure: Entry Point transactions are performed for [Termsetting2] with [Ltsetting1.2]

2EB.009.01 Zero Amount allowed flag not present with Transaction Type ‘Purchase’

Test No: - Revision 2.3a – Number of sub cases: 4

Objective: To ensure that when Zero Amount Flag is not present for a combination, and Transaction Type ‘Purchase’, Entry Point shall set the ’Zero Amount’ indicator for the Combination to 1 when Amount Authorized is set to 0.

To ensure that when Zero Amount Flag is not present for a combination, and Transaction Type ‘Purchase’, Entry Point shall set the ’Zero Amount’ indicator for the Combination to 0 when Amount Authorized is not set to 0.

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.4

Terminal [Purchase] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [LTsetting1.2] with an amount authorized of 0 is entered and Transaction Type = ’Purchase’ (00). • Case02: Entry Point transaction is performed with [LTsetting1.2] with an amount authorized of 2 is entered and Transaction Type = ’Purchase’ (00). • Case03: Entry Point transaction is performed with [LTsetting1.97] with an amount authorized of 0 is entered and Transaction Type = ’Purchase’ (00). • Case04: Entry Point transaction is performed with [LTsetting1.97] with an amount authorized of 2 is entered and Transaction Type = ’Purchase’ (00). Action: NA

Procedure: Entry Point transactions are performed for [Termsetting4] with different LT settings.

Pass Criteria: • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 4 set to ‘1b’

2EB.009.01 Zero Amount allowed flag not present with Transaction Type ‘Purchase’

• Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 4 set to ‘0b’ • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 4 set to ‘1b’ • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 4 set to ‘0b’

2EB.009.02 Zero Amount allowed flag not present with Transaction Type ‘Cash Advance’

Test No: - Revision 1 – Number of sub cases: 2

Objective: To ensure that when Zero Amount Flag is not present for a combination, and Transaction Type ‘Cash Advance’, Entry Point shall set the ’Zero Amount’ indicator for the Combination to 1 when Amount Authorized is set to 0.

To ensure that when Zero Amount Flag is not present for a combination, and Transaction Type ‘Cash Advance’, Entry Point shall set the ’Zero Amount’ indicator for the Combination to 0 when Amount Authorized is not set to 0.

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.4

Terminal [Cash Advance] supported Configuration:

Conditions: • Case01: An amount authorized of 0 is entered and Transaction Type = ’Cash Advance’ (01). • Case02: An amount authorized of 2 is entered and Transaction Type =’Cash Advance’ (01) Action: NA

Procedure: Entry Point transactions are performed for [Termsetting4] with [Ltsetting1.1]

2EB.010.00 Reader Contactless Transaction Limit exceeded

Test No: - Revision 2.4a – Number of sub cases: 5

Objective: To ensure that when Reader Contactless Transaction Limit is present and the Amount Authorized is greater than this limit for a combination, Entry Point shall set the ’Contactless Application Not Allowed’ indicator for the Combination to 1

Reference Book B – version 2.3 – Requirement 3.1.1.5 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [LTsetting2.6] with an amount authorized of 199 is entered. • Case02: Entry Point transaction is performed with [LTsetting2.6] with an amount authorized of 200 is entered. • Case03: Entry Point transaction is performed with [LTsetting2.6] with an amount authorized of 300 is entered. • Case04: Entry Point transaction is performed with [LTsetting2.43] with an amount authorized of 199 is entered. • Case05: Entry Point transaction is performed with [LTsetting2.43] with an amount authorized of 200 is entered. • Action: NA

Procedure: Entry Point transaction is performed for [Termsetting2] with different LT settings.

Pass Criteria: • Case01: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000010001), • Case02: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000020002). • Case03: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000020002). • Case04: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000040004), • Case05: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000020002).

2EB.010.00 Reader Contactless Transaction Limit exceeded

2EB.010.01 Reader Contactless Transaction Limit exceeded with Transaction Type ‘Purchase’

Test No: - Revision 2.4a – Number of sub cases: 3

Objective: To ensure that when Reader Contactless Transaction Limit is present and the Amount Authorized is greater than this limit for a combination, and Transaction Type ‘Purchase’, Entry Point shall set the ’Contactless Application Not Allowed’ indicator for the Combination to 1

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.5

Terminal [Purchase] supported Configuration:

Conditions: • Case01: An amount authorized of 199 is entered and Transaction Type = ’Purchase’ (00). • Case02: An amount authorized of 200 is entered and Transaction Type = ’Purchase’ (00). • Case03: An amount authorized of 300 is entered and Transaction Type = ’Purchase’ (00). Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting2.6]

2EB.011.00 Reader Contactless Transaction Limit not exceeded

Test No: - Revision 2.4a – Number of sub cases: 4

Objective: To ensure that when Reader Contactless Transaction Limit is present and the Amount Authorized is less than this limit for a combination, Entry Point shall not set the ’Contactless Application Not Allowed’ indicator for the Combination to 1

Reference Book B – version 2.3 – Requirement 3.1.1.5 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: For [Termsetting1] with [Ltsetting1.3], an amount authorized of 119 (less than Reader Contactless Transaction Limit) is entered. • Case02: For [Termsetting2] with [Ltsetting1.3], an amount authorized of 99 (less than Reader Contactless Transaction Limit) is entered. • Case03: For [Termsetting2] with [Ltsetting1.1], an amount authorized of 199 (less than Reader Contactless Transaction Limit) is entered. • Case04: For [Termsetting2] with [Ltsetting1.89], an amount authorized of 99 (less than Reader Contactless Transaction Limit) is entered. Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings.

Pass Criteria: • Case01: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000030003). • Case02: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000030003). • Case03: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000010001). • Case04: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000040004).

2EB.011.01 Reader Contactless Transaction Limit not exceeded with Transaction Type ‘Refund’

Test No: - Revision 2.4a – Number of sub cases: 0

Objective: To ensure that when Reader Contactless Transaction Limit is present and the Amount Authorized is less than this limit for a combination, and Transaction Type ‘Refund’, Entry Point shall not set the ’Contactless Application Not Allowed’ indicator for the Combination to 1

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.5

Terminal [Refund] supported Configuration:

Conditions: An amount authorized of 99 (less than Reader Contactless Transaction Limit) is entered and Transaction Type = ‘Refund’ (‘20’), Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.2]

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000020002).

2EB.011.02 Reader Contactless Transaction Limit not exceeded with Transaction Type ‘Purchase with Cashback’

Test No: - Revision 2.4a – Number of sub cases: 2

Objective: To ensure that when Reader Contactless Transaction Limit is present and the Amount Authorized is less than this limit for a combination, and Transaction Type ‘Purchase with Cashback’, Entry Point shall not set the ’Contactless Application Not Allowed’ indicator for the Combination to 1

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.5

Terminal [Purchase with Cashback] supported Configuration:

Conditions: • Case 01: an amount authorized of 199 (less than Reader Contactless Transaction Limit), and an amount other of 10 are entered and Transaction Type = ’Purchase with Cashback’ (00).

• Case 02: an amount authorized of 199 (less than Reader Contactless Transaction Limit) and an amount other of 10 are entered and Transaction Type = ’Purchase with Cashback’ (09).

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.3]

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000030003),

2EB.012.00 Reader Contactless Transaction Limit not present

Test No: - Revision 2.4a – Number of sub cases: 2

Objective: To ensure that when Reader Contactless Transaction Limit is not present and the Amount Authorized is set to ’99..99’, Entry Point shall not set the ’Contactless Application Not Allowed’ indicator for the Combination to 1.

Reference Book B – version 2.3 – Requirement 3.1.1.5 BOOK A/B:

Terminal NA Configuration:

Conditions: Case01: Entry Point transaction is performed with [LTsetting1.2] with an amount authorized of 999999999999. Case02: Entry Point transaction is performed with [LTsetting1.97] with an amount authorized of 999999999999. Action: NA

Procedure: Entry Point transaction is performed for [Termsetting2] with different LT settings.

Pass Criteria: Case01: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000020002), Case02: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000030003),

2EB.012.01 Reader Contactless Transaction Limit not present

Test No: - Revision 2.4a – Number of sub cases: 0

Objective: To ensure that when Reader Contactless Transaction Limit is not present and the Amount Authorized is set to ’99..99’, and Transaction Type ‘Refund’, Entry Point shall not set the ’Contactless Application Not Allowed’ indicator for the Combination to 1.

Reference Book B – version 2.3 – Requirement 3.1.1.5 BOOK A/B:

Terminal [Refund] supported Configuration:

Conditions: An amount authorized of 999999999999 is entered and Transaction Type = ’Refund’ (20) Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.4]

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000040004),

2EB.013.00 Reader Contactless Floor Limit present, Amount Authorized greater than limit

Test No: - Revision 2.3a – Number of sub cases: 6

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader Contactless Floor Limit is present and if the Amount Authorised is greater than the limit, then the terminal shall set the Pre-Processing internal indicator ’Reader Contactless Floor Limit Exceeded’ for the AID.

To ensure that if TTQ is present in the combination, and If the ‘Reader Contactless Floor Limit Exceeded’ indicator is set to 1, then Entry Point shall set byte 2, bit 8 in the Copy of TTQ for the Combination to 1b (‘Online cryptogram required’).

Reference Book B – version 2.3 – Requirement 3.1.1.6, 3.1.1.9 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: For [Termsetting1] with [Ltsetting1.2], an amount authorized of 13 (greater than Reader Contactless Floor Limit) is entered. • Case02: For [Termsetting2] with [Ltsetting1.3], an amount authorized of 21 (greater than Reader Contactless Floor Limit) is entered. • Case03: For [Termsetting2] with [Ltsetting1.4], an amount authorized of 51 (greater than Reader Contactless Floor Limit) is entered. • Case04: For [Termsetting1] with [Ltsetting1.97], an amount authorized of 19 (greater than Reader Contactless Floor Limit) is entered. • Case05: For [Termsetting2] with [Ltsetting1.3], an amount authorized of 99 (greater than Reader Contactless Floor Limit) is entered. • Case06: For [Termsetting2] with [Ltsetting1.4], an amount authorized of 123456 (greater than Reader Contactless Floor Limit) is entered. Action: NA

2EB.013.00 Reader Contactless Floor Limit present, Amount Authorized greater than limit

Procedure: Entry Point transactions are performed for different Term settings with different LT settings.

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘1b’ • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘1b’ • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘1b’ • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘1b’ • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘1b’ • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘1b’ • Case06: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘1b’

2EB.013.01 Reader Contactless Floor Limit present, Amount Authorized greater than limit with Transaction Type ‘Purchase’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader Contactless Floor Limit is present and if the Amount Authorised is greater than the limit, and Transaction Type ‘Purchase’, then the terminal shall set the Pre-Processing internal indicator ’Reader Contactless Floor Limit Exceeded’ for the AID.

To ensure that if TTQ is present in the combination, and If the ‘Reader Contactless Floor Limit Exceeded’ indicator is set to 1, and Transaction Type ‘Purchase’, then Entry Point shall set byte 2, bit 8 in the Copy of TTQ for the Combination to 1b (‘Online cryptogram required’).

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.6, 3.1.1.9

Terminal [Purchase] supported Configuration:

Conditions: An amount authorized of 21 (greater than Reader Contactless Floor Limit) is entered with Transaction Type = ’Purchase’ (00).

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.3]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘1b’ • The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘1b’

2EB.013.02 Reader Contactless Floor Limit present, Amount Authorized greater than limit with Transaction Type ‘Refund’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader Contactless Floor Limit is present and if the Amount Authorised is greater than the limit, and Transaction Type ‘Refund’, then the terminal shall set the Pre-Processing internal indicator ’Reader Contactless Floor Limit Exceeded’ for the AID.

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.6

Terminal [Refund] supported Configuration:

Conditions: An amount authorized of 51 (greater than Reader Contactless Floor Limit) is entered with Transaction Type = ’Refund’ (20).

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.4]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘1b’

2EB.014.00 Reader Contactless Floor Limit present, Amount Authorized less than limit

Test No: - Revision 2.4a – Number of sub cases: 5

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader Contactless Floor Limit is present and if the Amount Authorised is less or equal than the limit, then the terminal shall not set the Pre-Processing internal indicator ’Reader Contactless Floor Limit Exceeded’ for the AID.

To ensure that if TTQ is present in the combination, and If the ‘Reader Contactless Floor Limit Exceeded’ indicator is set to 0, then Entry Point shall set byte 2, bit 8 in the Copy of TTQ for the Combination to 0b (No ‘Online cryptogram required’).

Reference Book B – version 2.3 – Requirement 3.1.1.6, , 3.1.1.9 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: For [Termsetting1] with [Ltsetting1.4], an amount authorized of 12 (equal to Reader Contactless Floor Limit) is entered. • Case02: For [Termsetting2] with [Ltsetting1.92], an amount authorized of 20 (equal Reader Contactless Floor Limit) is entered. • Case03: For [Termsetting2] with [Ltsetting1.4], an amount authorized of 50 (equal Reader Contactless Floor Limit) is entered. • Case04: For [Termsetting2] with [Ltsetting1.92], an amount authorized of 15 (less than Reader Contactless Floor Limit) is entered. • Case05: For [Termsetting2] with [Ltsetting1.97], an amount authorized of 45 (less than Reader Contactless Floor Limit) is entered Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘0b’

2EB.014.00 Reader Contactless Floor Limit present, Amount Authorized less than limit

• Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘0b’ • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘0b’ • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘0b’

2EB.014.01 Reader Contactless Floor Limit present, Amount Authorized less than limit with Transaction Type ‘Purchase’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader Contactless Floor Limit is present and if the Amount Authorised is less or equal than the limit, and Transaction Type ‘Purchase’, then the terminal shall not set the Pre-Processing internal indicator ’Reader Contactless Floor Limit Exceeded’ for the AID.

To ensure that if TTQ is present in the combination, and If the ‘Reader Contactless Floor Limit Exceeded’ indicator is set to 0, and Transaction Type ‘Purchase’, then Entry Point shall set byte 2, bit 8 in the Copy of TTQ for the Combination to 0b (No ‘Online cryptogram required’).

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.6, 3.1.1.9

Terminal [Purchase] supported Configuration:

Conditions: an amount authorized of 20 (equal Reader Contactless Floor Limit) is entered, with Transaction Type = ’Purchase’ (00) Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.3]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘0b’ • The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘0b’

2EB.014.02 Reader Contactless Floor Limit present, Amount Authorized less than limit with Transaction Type ‘Refund’

Test No: - Revision 1 – Number of sub cases: 2

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader Contactless Floor Limit is present and if the Amount Authorised is less or equal than the limit, and Transaction Type ‘Refund’, then the terminal shall not set the Pre-Processing internal indicator ’Reader Contactless Floor Limit Exceeded’ for the AID.

To ensure that if TTQ is present in the combination, and If the ‘Reader Contactless Floor Limit Exceeded’ indicator is set to 0, and Transaction Type ‘Refund’, then Entry Point shall set byte 2, bit 8 in the Copy of TTQ for the Combination to 0b (No ‘Online cryptogram required’).

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.6, 3.1.1.9

Terminal [Refund] supported Configuration:

Conditions: Case01: For [Ltsetting1.2], an amount authorized of 20 (equal Reader Contactless Floor Limit) is entered, with Transaction Type = ’Refund’ (20) Case02: For [Ltsetting1.3], an amount authorized of 40 (less than Reader Contactless Floor Limit) is entered, with Transaction Type = ’Refund’ (20) Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with different LT settings

2EB.015.00 Reader Contactless Floor Limit not present, Terminal Floor Limit present

Test No: - Revision 2.3a – Number of sub cases: 6

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader Contactless Floor Limit is not present, but Terminal Floor Limit is present, and if the Amount Authorised is greater than the Terminal Floor Limit, then the terminal shall set the Pre- Processing internal indicator ’Reader Contactless Floor Limit Exceeded’ for the AID

Reference Book B – version 2.3 – Requirement 3.1.1.7 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Ltsetting1.1] and an amount authorized of 26 (greater than Terminal Floor Limit). • Case02: Entry Point transaction is performed with [Ltsetting2.1] and an amount authorized of 50 (greater than Terminal Floor Limit) is entered. • Case03: Entry Point transaction is performed with [Ltsetting1.1] and an amount authorized of 25 (equal to Terminal Floor Limit) is entered. • Case04: Entry Point transaction is performed with [Ltsetting2.1] and an amount authorized of 20 (less than Terminal Floor Limit) is entered. • Case05: Entry Point transaction is performed with [Ltsetting1.100] and an amount authorized of 26 (greater than Terminal Floor Limit). • Case06: Entry Point transaction is performed with [Ltsetting1.100] and an amount authorized of 25 (equal to Terminal Floor Limit) is entered.

Action: NA

Procedure: Entry Point transactions are performed for [Termsetting2] with different LT settings.

2EB.015.00 Reader Contactless Floor Limit not present, Terminal Floor Limit present

Pass Criteria: • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘1b’ • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘1b’ • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘0b’ • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘0b’ • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘1b’ • Case06: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘0b’

2EB.015.01 Reader Contactless Floor Limit not present, Terminal Floor Limit present with Transaction type ‘Purchase’

Test No: - Revision 1 – Number of sub cases: 4

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader Contactless Floor Limit is not present, but Terminal Floor Limit is present, and if the Amount Authorised is greater than the Terminal Floor Limit, and Transaction type ‘Purchase’, then the terminal shall set the Pre-Processing internal indicator ’Reader Contactless Floor Limit Exceeded’ for the AID

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.7

Terminal [Purchase] supported Configuration:

Conditions: • Case01: an amount authorized of 26 (greater than Terminal Floor Limit) is entered. • Case02: an amount authorized of 50 (greater than Terminal Floor Limit) is entered. • Case03: an amount authorized of 25 (equal to Terminal Floor Limit) is entered. • Case04: an amount authorized of 20 (less than Terminal Floor Limit) is entered. Action: NA

Procedure: Entry Point transactions are performed for [Termsetting4] (Purchase transaction) with [Ltsetting1.1]

2EB.015.01 Reader Contactless Floor Limit not present, Terminal Floor Limit present with Transaction type ‘Purchase’

• Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘0b’

2EB.015.02 Reader Contactless Floor Limit not present, Terminal Floor Limit present with Transaction type ‘Purchase with Cashback’

Test No: - Revision 1 – Number of sub cases: 4

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader Contactless Floor Limit is not present, but Terminal Floor Limit is present, and if the Amount Authorised is greater than the Terminal Floor Limit, and Transaction type ‘Purchase with Cashback’, then the terminal shall set the Pre-Processing internal indicator ’Reader Contactless Floor Limit Exceeded’ for the AID

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.7

Terminal [Purchase with Cashback] supported Configuration:

Conditions: • Case01: an amount authorized of 26 (greater than Terminal Floor Limit) and an amount other of 10 are entered. • Case02: an amount authorized of 50 (greater than Terminal Floor Limit) and an amount other of 10 are entered. • Case03: an amount authorized of 25 (equal to Terminal Floor Limit) and an amount other of 10 are entered. • Case04: an amount authorized of 20 (less than Terminal Floor Limit) and an amount other of 10 are entered. Action: NA

Procedure: Entry Point transactions are performed for [Termsetting4] (Purchase with Cashback transaction) with [Ltsetting1.3]

2EB.015.02 Reader Contactless Floor Limit not present, Terminal Floor Limit present with Transaction type ‘Purchase with Cashback’

• Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘0b’

2EB.016.00 Reader Contactless Floor Limit and Terminal Floor Limit not present

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader Contactless Floor Limit and the Terminal Floor Limit are not present, and if the Amount Authorised is set to ’99..99’, then the terminal shall not set the Pre-Processing internal indicator ’Reader Contactless Floor Limit Exceeded’ for the AID

Reference Book B – version 2.3 – Requirement 3.1.1.7 BOOK A/B:

Terminal NA Configuration:

Conditions: An amount authorized of ‘999999999999’. Action: NA

Procedure: Entry Point transactions are performed for [Termsetting2] with [Ltsetting1.2]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘0b’

2EB.016.01 Reader Contactless Floor Limit and Terminal Floor Limit not present with Transaction Type ‘Purchase’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader Contactless Floor Limit and the Terminal Floor Limit are not present, and if the Amount Authorised is set to ’99..99’, and Transaction Type ‘Purchase’, then the terminal shall not set the Pre-Processing internal indicator ’Reader Contactless Floor Limit Exceeded’ for the AID

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.7

Terminal [Purchase] supported Configuration:

Conditions: An amount authorized of ‘999999999999’ with Transaction Type = ‘Purchase’ (00) Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.2]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘0b’

2EB.016.02 Reader Contactless Floor Limit and Terminal Floor Limit not present with Transaction Type ‘Cash Advance’

Test No: - Revision 2.3a – Number of sub cases: 2

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader Contactless Floor Limit and the Terminal Floor Limit are not present, and if the Amount Authorised is set to ’99..99’, and Transaction Type ‘Cash Advance’, then the terminal shall not set the Pre-Processing internal indicator ’Reader Contactless Floor Limit Exceeded’ for the AID

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.7

Terminal [Cash Advance] supported Configuration:

Conditions: Case01: Entry Point transaction is performed with [LTsetting1.1] with an amount authorized of ‘999999999999’ with Transaction Type = ‘Cash Advance’ (01). Case02: Entry Point transaction is performed with [LTsetting1.97] with an amount authorized of ‘999999999999’ with Transaction Type = ‘Cash Advance’ (01). Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with different LT settings.

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 8 set to ‘0b’

2EB.017.00 Reader CVM Required Limit present, Amount Authorized greater or equal to limit

Test No: - Revision 2.3a – Number of sub cases: 4

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader CVM Required Limit is present and if the Amount Authorised is greater or equal to the limit, then the terminal shall set the Pre-Processing internal indicator ’Reader CVM Required Limit Exceeded’ for the AID

To ensure that if TTQ is present in the combination, and If the Reader CVM Required Limit Exceeded’ indicator is set to 1, then Entry Point shall set byte 2, bit 7 in the Copy of TTQ for the Combination to 1b (‘CVM required’).

Reference Book B – version 2.3 – Requirement 3.1.1.8, 3.1.1.12 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: For [Termsetting1] with [Ltsetting1.1], an amount authorized of 16 (greater than Reader CVM Required Limit) is entered. • Case02: For [Termsetting2] with [Ltsetting1.2], an amount authorized of 10 (equal to Reader CVM Required Limit) is entered. • Case03: For [Termsetting2] with [Ltsetting1.4], an amount authorized of 21 (greater than Reader CVM Required Limit) is entered. • Case04: For [Termsetting2] with [Ltsetting1.97], an amount authorized of 20 (equal to Reader CVM Required Limit) is entered. Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings.

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 6 set to ‘1b’ • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 7 set to ‘1b’

2EB.017.00 Reader CVM Required Limit present, Amount Authorized greater or equal to limit

• Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 7 set to ‘1b’ • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 7 set to ‘1b’

2EB.017.01 Reader CVM Required Limit present, Amount Authorized greater than limit with Transaction Type ‘Purchase’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader CVM Required Limit is present and if the Amount Authorised is greater than the limit, and Transaction Type ‘Purchase’, then the terminal shall set the Pre-Processing internal indicator ’Reader CVM Required Limit Exceeded’ for the AID

To ensure that if TTQ is present in the combination, and If the Reader CVM Required Limit Exceeded’ indicator is set to 1, and Transaction Type ‘Purchase’, then Entry Point shall set byte 2, bit 7 in the Copy of TTQ for the Combination to 1b (‘CVM required’).

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.8, 3.1.1.12

Terminal [Purchase] supported Configuration:

Conditions: an amount authorized of 21 (greater than Reader CVM Required Limit) is entered with Transaction Type = ’Purchase’ (00).

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.4]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 6 set to ‘1b’ • The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 7 set to ‘1b’

2EB.017.02 Reader CVM Required Limit present, Amount Authorized greater than limit with Transaction Type ‘Cash Advance’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader CVM Required Limit is present and if the Amount Authorised is greater than the limit, and Transaction Type ‘Cash Advance’, then the terminal shall set the Pre-Processing internal indicator ’Reader CVM Required Limit Exceeded’ for the AID

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.8

Terminal [Cash Advance] supported Configuration:

Conditions: an amount authorized of 11 (greater than Reader CVM Required Limit) is entered with Transaction Type = ’Cash Advance’ (01).

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.1]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 6 set to ‘1b’

2EB.018.00 Reader CVM Required Limit present, Amount Authorized less than limit

Test No: - Revision 2.3a – Number of sub cases: 4

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader CVM Required Limit is present and if the Amount Authorised is less than the limit, then the terminal shall not set the Pre- Processing internal indicator ’Reader CVM Required Limit Exceeded’ for the AID

Reference Book B – version 2.3 – Requirement 3.1.1.8 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Using [Termsetting1] with [Ltsetting1.1], an amount authorized of 14 (less than Reader CVM Required Limit) is entered. • Case02: Using [Termsetting2] with [Ltsetting1.2], an amount authorized of 5 (less than Reader CVM Required Limit) is entered. • Case03: Using [Termsetting2] with [Ltsetting1.4], an amount authorized of 19 (less than Reader CVM Required Limit) is entered. • Case04: Using [Termsetting2] with [Ltsetting1.97], an amount authorized of 19 (less than Reader CVM Required Limit) is entered. Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 6 set to ‘0b’

2EB.018.01 Reader CVM Required Limit present, Amount Authorized less than limit with Transaction Type ‘Purchase’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader CVM Required Limit is present and if the Amount Authorised is less than the limit, and Transaction Type ‘Purchase’, then the terminal shall not set the Pre-Processing internal indicator ’Reader CVM Required Limit Exceeded’ for the AID

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.8

Terminal [Purchase] supported Configuration:

Conditions: an amount authorized of 9 (less than Reader CVM Required Limit) is entered and Transaction Type = ’Purchase’ (00).

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.2]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 6 set to ‘0b’

2EB.018.02 Reader CVM Required Limit present, Amount Authorized less than limit with Transaction Type ‘Refund’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader CVM Required Limit is present and if the Amount Authorised is less than the limit, and Transaction Type ‘Refund’, then the terminal shall not set the Pre-Processing internal indicator ’Reader CVM Required Limit Exceeded’ for the AID

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.8

Terminal [Refund] supported Configuration:

Conditions: an amount authorized of 19 (less than Reader CVM Required Limit) is entered and Transaction Type = ’Refund’ (20).

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.4]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 6 set to ‘0b’

2EB.019.00 Reader CVM Required Limit not present

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader CVM Required Limit is not present, and if the Amount Authorised is set to ’99..99’, then the terminal shall not set the Pre-Processing internal indicator ’Reader CVM Required Limit Exceeded’ for the AID

Reference Book B – version 2.3 – Requirement 3.1.1.8 BOOK A/B:

Terminal NA Configuration:

Conditions: An amount authorized of ‘999999999999’. Action: NA

Procedure: Entry Point transactions are performed for [Termsetting2] with [Ltsetting1.92]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 6 set to ‘0b’

2EB.019.01 Reader CVM Required Limit not present with Transaction Type ‘Purchase’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader CVM Required Limit is not present, and if the Amount Authorised is set to ’99..99’,and Transaction Type ‘Purchase’ then the terminal shall not set the Pre-Processing internal indicator ’Reader CVM Required Limit Exceeded’ for the AID

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.8

Terminal [Purchase] supported Configuration:

Conditions: An amount authorized of ‘999999999999’ with Transaction Type = ’Purchase’ (00). Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.3]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 6 set to ‘0b’

2EB.019.02 Reader CVM Required Limit not present with Transaction Type ‘Refund’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that for each AID, the terminal shall perform the following actions: If the Reader CVM Required Limit is not present, and if the Amount Authorised is set to ’99..99’,and Transaction Type ‘Refund’ then the terminal shall not set the Pre-Processing internal indicator ’Reader CVM Required Limit Exceeded’ for the AID

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.8

Terminal [Refund] supported Configuration:

Conditions: An amount authorized of ‘999999999999’ with Transaction Type = ’Refund’ (20). Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.3]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 6 set to ‘0b’

2EB.020.00 Zero Amount indicator set with TTQ (online capable reader)

Test No: - Revision 1 – Number of sub cases: 2

Objective: To ensure that when ’Zero Amount’ indicator is set to 1 for the Combination, and copy of TTQ indicate ‘Online capable Reader’, Entry Point shall set byte 2, bit 8 in the Copy of TTQ for the Combination to 1b (‘Online cryptogram required’).

Reference Book B – version 2.3 – Requirement 3.1.1.11 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: An amount authorized of 0 is entered. • Case02: An amount authorized of 2 is entered. Action: NA

Procedure: Entry Point transactions are performed for [Termsetting2] with [Ltsetting1.3]

Pass Criteria: • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 4 set to ‘1b’ • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘1b’ • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): byte 1 bit 4 set to ‘0b’ • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): byte 2 bit 8 set to ‘0b’

2EB.020.01 Zero Amount indicator set with TTQ (online capable reader) with Transaction Type ‘Purchase’

Test No: - Revision 1 – Number of sub cases: 2

Objective: To ensure that when ’Zero Amount’ indicator is set to 1 for the Combination, and copy of TTQ indicate ‘Online capable Reader’, and Transaction Type ‘Purchase’, Entry Point shall set byte 2, bit 8 in the Copy of TTQ for the Combination to 1b (‘Online cryptogram required’).

Reference Book A – version 2.3 – Requirement 8.1.1.5 BOOK A/B: Book B – version 2.3 – Requirement 3.1.1.11

Terminal [Purchase] supported Configuration:

Conditions: • Case01: An amount authorized of 0 is entered with Transaction Type = ’Purchase’ (00). • Case02: An amount authorized of 2 is entered with Transaction Type = ’Purchase’ (00). Action: NA

Procedure: Entry Point transaction is performed for [Termsetting4] with [Ltsetting1.3]

2EB.021.00 Zero Amount indicator set with TTQ (offline only reader)

Test No: - Revision 2.4a – Number of sub cases: 2

Objective: To ensure that when ’Zero Amount’ indicator is set to 1 for the Combination, and copy of TTQ indicate ‘Offline only Reader’, Entry Point shall set the ’Contactless Application Not Allowed’ indicator for the Combination to 1

Reference Book B – version 2.3 – Requirement 3.1.1.11 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: An amount authorized of 0 is entered. • Case02: An amount authorized of 2 is entered. Action: NA

Procedure: Entry Point transaction is performed for [Termsetting2] with [Ltsetting2.5]

2EB.022.00 Contactless Application Not Allowed for all combinations after Pre-Processing

Test No: - Revision 2.1a – Number of sub cases: 0

Objective: To ensure that when at end of Pre-Processing, for all the Combinations, the ‘Contactless Application Not Allowed’ indicator is 1, the Entry Point shall provide a Try Another Interface Outcome.

Reference Book B – version 2.3 – Requirement 3.1.1.13 BOOK A/B:

Terminal NA Configuration:

Conditions: An amount authorized of 121 is entered. Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with [Ltsetting2.5]

Pass Criteria: • The terminal shall display Message Identifier ‘18’ (“Please Insert or Swipe Card”) without any previous Select PPSE on the 155contactless interface

9.3. Protocol Activation

2EC.001.00 All Pre-Processing indicators set to zero when Pre- Processing not performed

Test No: - Revision 2.5a – Number of sub cases: 5

Objective: To ensure that if the Restart flag is 0 and the Entry Point is activated by the reader at Start B, • Entry Point shall clear (to 0) all Pre-Processing indicators: • Status Check Requested • Contactless Application not Allowed • Zero Amount • Reader CVM Required Limit Exceeded • Reader Contactless Floor Limit Exceeded. • If TTQ is configured then then Entry Point shall copy the TTQ from Entry Point Configuration Data (see Book A, Table 1) into the Copy of TTQ in the Entry Point Pre-Processing Indicators

Reference Book A – version 2.3 – Requirement 8.1.1.1 BOOK A/B: Book B – version 2.3 – Requirement 3.2.1.1

Terminal [Autorun] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Ltsetting1.1] • Case02: Entry Point transaction is performed with [Ltsetting1.2] • Case03: Entry Point transaction is performed with [Ltsetting1.3] • Case04: Entry Point transaction is performed with [Ltsetting1.4] • Case05: Entry Point transaction is performed with [Ltsetting1.97] Action: NA

Procedure: Entry Point transactions are performed for [Termsetting3] (Pre Processing not activated) with different LT settings.

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): set to value ’00 00’. • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): set to value ‘28000000’.

2EC.001.00 All Pre-Processing indicators set to zero when Pre- Processing not performed

• Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): set to value ‘84008000’. • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): set to value ‘84C08000’. • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): set to value ‘84C08000’.

2EC.001.01 All Pre-Processing indicators set to zero when Pre- Processing not performed with Transaction Type ‘Purchase’

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that if the Restart flag is 0 and the Entry Point is activated by the reader at Start B for a Transaction Type ‘Purchase’, • Entry Point shall clear (to 0) all Pre-Processing indicators: • Status Check Requested • Contactless Application not Allowed • Zero Amount • Reader CVM Required Limit Exceeded • Reader Contactless Floor Limit Exceeded. • If TTQ is configured then then Entry Point shall copy the TTQ from Entry Point Configuration Data (see Book A, Table 1) into the Copy of TTQ in the Entry Point Pre-Processing Indicators

Reference Book B – version 2.3 – Requirement 3.2.1.1 BOOK A/B:

Terminal [Purchase] supported Configuration:

Conditions: NA Action: NA

Procedure: Entry Point transaction is performed for [Termsetting5.1] with [Ltsetting1.1]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): set to value ’00 00’. • The LT shall receive in the GET PROCESSING OPTIONS data field: TTQ Data (tag ‘9F66’): set to value ‘28000000’.

2EC.001.02 All Pre-Processing indicators set to zero when Pre- Processing not performed with Transaction Type ‘Purchase with Cashback’

Test No: - Revision 2.1a – Number of sub cases: 0

Objective: To ensure that if the Restart flag is 0 and the Entry Point is activated by the reader at Start B for a Transaction Type ‘Purchase with Cashback’, • Entry Point shall clear (to 0) all Pre-Processing indicators: • Status Check Requested • Contactless Application not Allowed • Zero Amount • Reader CVM Required Limit Exceeded • Reader Contactless Floor Limit Exceeded. • If TTQ is configured then then Entry Point shall copy the TTQ from Entry Point Configuration Data (see Book A, Table 1) into the Copy of TTQ in the Entry Point Pre-Processing Indicators

Reference Book B – version 2.3 – Requirement 3.2.1.1 BOOK A/B:

Terminal [Purchase with Cashback] supported Configuration:

Conditions : NA Action : NA

Procedure: Entry Point transaction is performed for [Termsetting5.2] with [Ltsetting1.3]

2EC.001.03 All Pre-Processing indicators set to zero when Pre- Processing not performed with Transaction Type ‘Cash Advance’

Test No: - Revision 2.1a – Number of sub cases: 0

Objective: To ensure that if the Restart flag is 0 and the Entry Point is activated by the reader at Start B for a Transaction Type ‘Cash Advance’, • Entry Point shall clear (to 0) all Pre-Processing indicators: • Status Check Requested • Contactless Application not Allowed • Zero Amount • Reader CVM Required Limit Exceeded • Reader Contactless Floor Limit Exceeded. • If TTQ is configured then then Entry Point shall copy the TTQ from Entry Point Configuration Data (see Book A, Table 1) into the Copy of TTQ in the Entry Point Pre-Processing Indicators

Reference Book B – version 2.3 – Requirement 3.2.1.1 BOOK A/B:

Terminal [Cash Advance] supported Configuration:

Conditions : NA Action : NA

Procedure: Entry Point transaction is performed for [Termsetting5.3] with [Ltsetting1.1]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): set to value ’00 00’.

2EC.001.04 All Pre-Processing indicators set to zero when Pre- Processing not performed with Transaction Type ‘Refund’

Test No: - Revision 2.1a – Number of sub cases: 0

Objective: To ensure that if the Restart flag is 0 and the Entry Point is activated by the reader at Start B for a Transaction Type ‘Refund’, • Entry Point shall clear (to 0) all Pre-Processing indicators: • Status Check Requested • Contactless Application not Allowed • Zero Amount • Reader CVM Required Limit Exceeded • Reader Contactless Floor Limit Exceeded. • If TTQ is configured then then Entry Point shall copy the TTQ from Entry Point Configuration Data (see Book A, Table 1) into the Copy of TTQ in the Entry Point Pre-Processing Indicators

Reference Book B – version 2.3 – Requirement 3.2.1.1 BOOK A/B:

Terminal [Refund] supported Configuration:

Conditions : NA Action : NA

Procedure: Entry Point transaction is performed for [Termsetting5.4] with [Ltsetting1.4]

Pass Criteria: • The LT shall receive in the GET PROCESSING OPTIONS data field: Test Flag Data (tag ‘D1’): set to value ’00 00’.

2EC.002.00 Restart flag set and UI Request on Restart present

Test No: - Revision 2.6a – Number of sub cases: 3

Objective: To ensure that if the Restart flag is 1 and the retained UI Request on Restart Present is ‘Yes’, then Entry Point shall send the retained User Interface Request at restart.

Test is done for a Restart A, B, C and D.

Reference Book B – version 2.3 – Requirement 3.2.1.2 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case02: Entry Point transaction is performed with [Ltsetting1.19] (UI Request on Restart Present is ‘Yes’, requesting a Restart B, and Issuer Authentication Data received) • Case03: Entry Point transaction is performed with [Ltsetting1.12] (UI Request on Restart Present is ‘Yes’, requesting a Restart C) • Case04: Entry Point transaction is performed with [Ltsetting1.9] (UI Request on Restart Present is ‘Yes’, requesting a Restart D) Action: NA

Procedure: • An Entry Point transactions are performed with restart sequence for [Termsetting1] with different LT settings

Pass Criteria: • Case02: The UI Request on Restart: MSG ID 21 ‘PRESENT CARD AGAIN’ is correctly displayed at restart (after reception of the Online response)

• Case03: The UI Request on Restart: MSG ID 21 ‘PRESENT CARD AGAIN’ is correctly displayed at restart (after reception of the Online response)

• Case04: The UI Request on Restart: MSG ID 16 ‘PROCESSING’ is correctly displayed at restart (after reception of the Online response)

• The LT shall receive in the GET PROCESSING OPTIONS data field after restart: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set).

2EC.003.00 Restart flag set and UI Request on Restart not present

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Restart flag is 1 and the retained UI Request on Restart Present is ‘No’, then Entry Point shall send a User Interface Request at restart Message Identifier: ’15’ (“PRESENT CARD”)

Test is done for a Restart A, B, C and D.

Reference Book B – version 2.3 – Requirement 3.2.1.2 BOOK A/B:

Terminal NA Configuration:

Conditions: • Entry Point transaction is performed with [Ltsetting1.26] (UI Request on Restart Present is ‘No’, requesting a Restart B and Issuer Authentication Data received) Action: NA

Procedure: • An Entry Point transaction is performed with restart sequence for [Termsetting1] with different LT settings

Pass Criteria: • The UI Request on Restart: MSG ID 15 ‘PRESENT CARD’ is correctly displayed at restart (after reception of the Online response)

• The LT shall receive in the GET PROCESSING OPTIONS data field after restart: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 1 (Restart Flag set).

2EC.004.00 Restart flag not set , Message ‘PRESENT CARD’

Test No: - Revision 1 – Number of sub cases: 2

Objective: To ensure that if the Restart flag is 0 then Entry Point shall send a User Interface Request at restart Message Identifier: ’15’ (“PRESENT CARD”)

Test is done for a Start A, B.

Reference Book B – version 2.3 – Requirement 3.2.1.2 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and [Ltsetting1.1] • Case02: Entry Point transaction is performed with [Termsetting3] and [Ltsetting1.2] Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings

Pass Criteria: • The MSG ID 15 ‘PRESENT CARD’ is correctly displayed at start

• The LT shall receive in the GET PROCESSING OPTIONS data field after start: Test Flag Data (tag ‘D1’): byte 2 bit 8 set to 0 (Restart Flag set).

2EC.005.00 Field powered and polling

Test No: - Revision 1 – Number of sub cases: 4

Objective: To ensure that the field shall be powered up and polling performed as defined in the Main Loop of Book D.

Test is done for a card Type A and B and Start in A and B.

Reference Book B – version 2.3 – Requirement 3.2.1.3 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and [Ltsetting1.1] (card type A) with Amount = 2 • Case02: Entry Point transaction is performed with [Termsetting1] and [Ltsetting1.2] (card type B) with Amount = 2 • Case03: Entry Point transaction is performed with [Termsetting3] and [Ltsetting1.1] (card type A) • Case04: Entry Point transaction is performed with [Termsetting3] and [Ltsetting1.2] (card type B) Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings

Pass Criteria: • The LT shall receive the SELECT command with AID with a file name of ‘2PAY.SYS.DDF01’ as a first command.

2EC.006.00 Protocol Activation Collision

Test No: - Revision 1 – Number of sub cases: 4

Objective: To ensure that a collision as defined in Book D is reported to Entry Point, then Entry Point shall send a User Interface Request with the following parameters:

• Message Identifier: ‘19’ (“PLEASE PRESENT ONE CARD ONLY “) Message is still displayed even if the collision is not indicated

Test is done for a Card Type A, B and Start in A and B.

Reference Book B – version 2.3 – Requirement 3.2.1.4, 3.2.1.5 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and 2 cards [Ltsetting1.1] (card type A) and the cards are withdrawn from the field • Case02: Entry Point transaction is performed with [Termsetting1] and 2 cards [Ltsetting1.2] (card type B) and the cards are withdrawn from the field • Case03: Entry Point transaction is performed with [Termsetting3] and 2 cards [Ltsetting1.1] (card type A) and the cards are withdrawn from the field • Case04: Entry Point transaction is performed with [Termsetting3] and 2 cards [Ltsetting1.2] (card type B) and the cards are withdrawn from the field Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings

Pass Criteria: • The Message Identifier 19 ‘PLEASE PRESENT ONE CARD ONLY’ is displayed at collision detection and stays displayed even if the cards are withdrawn

2EC.007.00 Protocol Activation Collision

Test No: - Revision 1 – Number of sub cases: 4

Objective: To ensure that a collision as defined in Book D is reported to Entry Point, then Entry Point shall send a User Interface Request with the following parameters:

• Message Identifier: ‘19’ (“PLEASE PRESENT ONE CARD ONLY “) Message is still displayed even if the collision is not indicated until one card is removed and the transaction is completed with the remaining card

Test is done for a Card Type A, B and Start in A and B.

Reference Book B – version 2.3 – Requirement 3.2.1.4, 3.2.1.5 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and 2 cards [Ltsetting1.1] (card type A) and one card is withdrawn from the field • Case02: Entry Point transaction is performed with [Termsetting1] and [Ltsetting1.2] (card type B) and one card is withdrawn from the field • Case03: Entry Point transaction is performed with [Termsetting3] and [Ltsetting1.1] (card type A) and one card is withdrawn from the field • Case04: Entry Point transaction is performed with [Termsetting3] and [Ltsetting1.2] (card type B) and one card is withdrawn from the field Action: NA

Procedure: Entry Point transactions are performed for different Term settings and different LT settings

Pass Criteria: • The Message Identifier 19 ‘PLEASE PRESENT ONE CARD ONLY’ is displayed at collision detection.

• The Select PPSE is received by the remaining card.

9.4. AID and Kernel Selection

2ED.001.00 Entry point Activation at Start B with Issuer Authentication Data or Issuer Script present

Test No: - Revision 2.6a – Number of sub cases: 6

Objective: To ensure that if Entry Point is activated by the reader at Start B with Issuer Authentication Data, or Issuer Script present, processing shall continue at requirement 3.3.3.3 of Final Combination Selection with the Combination that was selected during the previous Final Combination Selection. Reference Book B – version 2.3 – Requirement 3.3.2.1 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed for [Termsetting1] with [Ltsetting2.10] (which require a restart B, EMV data), Entry Point transaction is restarted (Start B, Issuer Authentication data (tag ‘91’) present) • Case02: Entry Point transaction is performed for [Termsetting3] with [Ltsetting2.7] (which require a restart B, EMV data) Entry Point transaction is restarted (Start B, Issuer script (tag ‘71’) present) • Case03: Entry Point transaction is performed for [Termsetting1] with [Ltsetting2.17] (which require a restart B, EMV data), Entry Point transaction is restarted (Start B, Issuer script (tag ‘72’) present) • Case04: Entry Point transaction is performed for [Termsetting1] with [Ltsetting2.8] (which require a restart B, EMV data), Entry Point transaction is restarted (Start B, Issuer Authentication data (tag ‘91’) and Issuer script (tag ‘71’) present) • Case05: Entry Point transaction is performed for [Termsetting3] with [Ltsetting2.9] (which require a restart B, EMV data) Entry Point transaction is restarted (Start B, Issuer Authentication data (tag ‘91’) and Issuer script (tag ‘72’) present) • Case06: Entry Point transaction is performed for [Termsetting1] with [Ltsetting2.18] (which require a restart B, EMV data), Entry Point transaction is restarted (Start B, Issuer Authentication data (tag ‘91’), Issuer script (tag ‘71’) and Issuer script (tag ‘72’) present) Action: NA

2ED.001.00 Entry point Activation at Start B with Issuer Authentication Data or Issuer Script present

Procedure: Entry Point transactions are performed with restart in start B with Issuer Authentication Data or Issuer Script present for different Term settings with different LT settings.

Pass Criteria: • Case01: After Restart, the LT shall receive the SELECT command with AID ‘A0000000030003’ (corresponding to the the previous Final Combination Selection), without a previous Select PPSE • Case01: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A0000000030003’ • Case01: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 21. • Case02: After Restart, the LT shall receive the SELECT command with AID ‘A0000000030003’ (corresponding to the the previous Final Combination Selection), without a previous Select PPSE • Case02: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A0000000030003’ • Case02: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 21. • Case03: After Restart, the LT shall receive the SELECT command with AID ‘A0000000010001’ (corresponding to the the previous Final Combination Selection), without a previous Select PPSE • Case03: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A0000000010001’ • Case03: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 23. • Case04: After Restart, the LT shall receive the SELECT command with AID ‘A0000000030003’ (corresponding to the the previous Final Combination Selection), without a previous Select PPSE • Case04: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A0000000030003’ • Case04: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 21.

2ED.001.00 Entry point Activation at Start B with Issuer Authentication Data or Issuer Script present

• Case05: After Restart, the LT shall receive the SELECT command with AID ‘A0000000030003’ (corresponding to the the previous Final Combination Selection), without a previous Select PPSE • Case05: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A0000000030003’ • Case05: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 21. • Case06: After Restart, the LT shall receive the SELECT command with AID ‘A0000000010001’ (corresponding to the the previous Final Combination Selection), without a previous Select PPSE • Case06: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A0000000010001’ • Case06: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 23.

2ED.001.01 Entry point Activation at Start B with Issuer Authentication Data or Issuer Script present with Extended Selection

Test No: - Revision 2.6a – Number of sub cases: 6

Objective: To ensure that if Entry Point is activated by the reader at Start B with Issuer Authentication Data, or Issuer Script present, • processing shall continue at requirement 3.3.3.3 of Final Combination Selection with the Combination that was selected during the previous Final Combination Selection.

Reference Book B – version 2.3 – Requirement 3.3.2.1 BOOK A/B:

Terminal [Extended Selection] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed for [Termsetting1] and [Ltsetting2.11] (Restart B, Issuer Authentication data (tag’91’) present) • Case02: Entry Point transaction is performed with [Termsetting3] and [Ltsetting2.12] (Restart B, Issuer script (tag ‘71’) present) • Case03: Entry Point transaction is performed with [Termsetting1] and [Ltsetting2.13] (Restart B, Issuer script (tag ‘72’) present) • Case04: Entry Point transaction is performed for [Termsetting1] and [Ltsetting2.14] (Restart B, Issuer Authentication data (tag’91’) and Issuer script (tag ‘71’) present) • Case05: Entry Point transaction is performed with [Termsetting3] and [Ltsetting2.15] (Restart B, Issuer Authentication data (tag’91’) and Issuer script (tag ‘72’) present) • Case06: Entry Point transaction is performed with [Termsetting1] and [Ltsetting2.16] (Restart B, Issuer Authentication data (tag’91’), Issuer script (tag ‘71’) and Issuer script (tag ‘72’) present) Action: NA

Procedure: Entry Point transactions are performed with restart in start B with Issuer Authentication Data or Issuer Script present for different Term settings and Ltsettings

Pass Criteria: • Case01: After Restart, the LT shall receive the SELECT command with AID ‘A000000004000404’ (corresponding to the the previous

2ED.001.01 Entry point Activation at Start B with Issuer Authentication Data or Issuer Script present with Extended Selection

Final Combination Selection including extended selection data), without a previous Select PPSE • Case01: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A000000004000404’ • Case01: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 24. • Case02: After Restart, the LT shall receive the SELECT command with AID ‘A000000004000404’ (corresponding to the the previous Final Combination Selection including extended selection data), without a previous Select PPSE • Case02: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A000000004000404’ • Case02: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 24. • Case03: After Restart, the LT shall receive the SELECT command with AID ‘A000000004000404’ (corresponding to the the previous Final Combination Selection including extended selection data), without a previous Select PPSE • Case03: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A000000004000404’ • Case03: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 24. • Case04: After Restart, the LT shall receive the SELECT command with AID ‘A000000004000404’ (corresponding to the the previous Final Combination Selection including extended selection data), without a previous Select PPSE • Case04: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A000000004000404’ • Case04: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 24. • Case05: After Restart, the LT shall receive the SELECT command with AID ‘A000000004000404’ (corresponding to the the previous

2ED.001.01 Entry point Activation at Start B with Issuer Authentication Data or Issuer Script present with Extended Selection

Final Combination Selection including extended selection data), without a previous Select PPSE • Case05: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A000000004000404’ • Case05: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 24. • Case06: After Restart, the LT shall receive the SELECT command with AID ‘A000000004000404’ (corresponding to the the previous Final Combination Selection including extended selection data), without a previous Select PPSE • Case06: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A000000004000404’ • Case06: After Restart, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 25.

2ED.002.00 Entry point Activation at Start C (Restart)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if Entry Point is activated by the reader at Start C (restart mode), processing shall continue at Step 3 with the Final Combination Selection was selected during the previous Final Combination Selection. Reference Book B – version 2.3 – Requirement 3.3.2.1 BOOK A/B:

Terminal NA Configuration:

Conditions: NA Action: NA

Procedure: Entry Point transaction is performed with restart in start C for [Termsetting1] with [Ltsetting2.19] (which require a restart C, Online Response Data: Any)

Pass Criteria: • After Restart C, the LT shall receive the SELECT command with AID ‘A0000000020002’ (corresponding to the the previous Final Combination Selection), without a previous Select PPSE • After Restart C, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A0000000020002’ • After Restart C, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 24

2ED.002.01 Entry point Activation at Start C (Restart) with Extended Selection

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if Entry Point is activated by the reader at Start C (restart mode), processing shall continue at Step 3 with the Final Combination Selection was selected during the previous Final Combination Selection (with Extended Selection activated). Reference Book B – version 2.3 – Requirement 3.3.2.1 BOOK A/B:

Terminal [Extended Selection] supported Configuration:

Conditions : NA Action : NA

Procedure: Entry Point transaction is performed with restart in start C for [Termsetting3] with [Ltsetting2.25] (which require a restart C, Online Response Data: Any)

Pass Criteria: • After Restart C, The LT shall receive the SELECT command with AID ‘A000000004000404’ (corresponding to the the previous Final Combination Selection with extended Selection data), without a previous Select PPSE • After Restart C, the LT shall receive in the GET PROCESSING OPTIONS data field: FCI include AID ‘A000000004000404’ • After Restart C, the LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 24.

2ED.003.00 PPSE selection

Test No: - Revision 1 – Number of sub cases: 2

Objective: To ensure that at step 1 of Combination selection, Entry Point shall send a SELECT command (as described in section 11.3.2 of EMV Book 1) to the card, with a file name of ‘2PAY.SYS.DDF01’. Test is done for Start A and B.

Reference Book B – version 2.3 – Requirement 3.3.2.2 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed for [Termsetting1], and Amount = 2 • Case02: Entry Point transaction is performed for [Termsetting3] Action: NA

Procedure: An Entry Point transactions are performed for different Term settings with [Ltsetting1.1]

Pass Criteria: • The LT shall receive the SELECT command with AID with a file name of ‘2PAY.SYS.DDF01’ as a first command.

2ED.003.01 PPSE with additional data

Test No: - Revision 2.6a – Number of sub cases: 3

Objective: To ensure that the terminal shall not interpret additional data as defined in EMV book 1.

Reference Book B – version 2.3 – Requirement 3.3.2.2 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Ltsetting1.50] (PPSE containing EMV tag ‘88’ located under the FCI Proprietary Template) and Amount = 2 • Case02: Entry Point transaction is performed with [Ltsetting1.51] (PPSE containing all EMV mandatory and optional data (SFI of the Directory Elementary File, Language Preference, Issuer Code Table Index and FCI Issuer Discretionary Data), FCI Issuer Discretionary Data contains Issuer Country Code data object) and Amount = 2

• Case03: Entry Point transaction is performed with [Ltsetting1.52] (PPSE containing a Directory Discretionary Template with tag ‘73’ containing: ‘5F54’ Bank Identifier Code (BIC), ‘5F53’ International Bank Account Number (IBAN), ‘5F55’ Issuer Country Code’, ‘5F56’ Issuer Country Code, and ‘42’ Issuer Identifier Number) and Amount = 2 Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with different LT settings.

2ED.003.01 PPSE with additional data

• Case03: The LT shall receive the SELECT command with AID A0000000030003 • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 21

2ED.003.02 ASRPD Data support

Test No: - Revision 2.6a – Number of sub cases: 12

Objective: To ensure that the presence of ASRPD data object in the data field returned by SELECT ADF command (or in ADF directory entry from PPSE) is ignored when the terminal does not support it, or is accepted when the terminal support it.

Reference Book B – version 2.6 - Requirement 3.3.1.2 BOOK A/B: Book B – version 2.6 - Requirement 3.3.3.8 Book Bulletins - Section SB 183 - Bulletin n°175, Application Selection Registered Proprietary Data (February 2016)

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Ltsetting1.110] (FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID L V)) and Amount = 2 • Case02: Entry Point transaction is performed with [Ltsetting1.111] (FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3 V3).) and Amount = 2 o Case03: Entry Point transaction is performed with [Ltsetting1.112] (FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2,…, IDn Ln Vn) reaching the max length possible (where all FCI optional data are not present and Application Label Length =1 byte) and Amount = 2

• Case04: Entry Point transaction is performed with [Ltsetting1.113] (FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with a single empty instance (ID L where L = 00)) and Amount = 2 • Case05: Entry Point transaction is performed with [Ltsetting1.114] (FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2, ID3 L3 V3 where L2=00)) and Amount = 2 • Case06: Entry Point transaction is performed with [Ltsetting1.115] (ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data

2ED.003.02 ASRPD Data support

field: tag 9F 0A correctly formatted with a single instance (ID L V)) and Amount = 2 • Case07: Entry Point transaction is performed with [Ltsetting1.116] (ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3 V3)) and Amount = 2 • Case08: Entry Point transaction is performed with [Ltsetting1.117] (ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID1 L V). FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID2 L V)) and Amount = 2 • Case09: Entry Point transaction is performed with [Ltsetting1.118] (ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID1 L V1). FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID1 L V2) with same ID but different value)) and Amount = 2 • Case10: Entry Point transaction is performed with [Ltsetting1.119] (ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3 V3). FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID4 L4 V4, ID2 L7 V7, ID6 L6 V6) where ID2 is the same (with different length and value)) and Amount = 2 • Case11: Entry Point transaction is performed with [Ltsetting1.120] (ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data field: tag 9F 0A incorrectly formatted, length = 2 (value is also 2Bytes). FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3 V3)) and Amount = 2 • Case12: Entry Point transaction is performed with [Ltsetting1.121] (ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1, ID2 L2 V2, ID3 L3 V3) where L1=00. FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID4 L4 V4, ID2 L2 V2, ID6 L6 V6) where ID2 is the same (with same value)) and Amount = 2

2ED.003.02 ASRPD Data support

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with different LT settings.

Pass Criteria: • Case01: The LT shall receive the SELECT command with AID A0000000010001 • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 23 Kernel ID • Case02: The LT shall receive the SELECT command with AID A0000000020002 • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 22 Kernel ID • Case03: The LT shall receive the SELECT command with AID A0000000030003 • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 21 Kernel ID • Case04: The LT shall receive the SELECT command with AID A0000000010001 • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 23 Kernel ID • Case05: The LT shall receive the SELECT command with AID A0000000020002 • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 22 Kernel ID • Case06: The LT shall receive the SELECT command with AID A0000000030003 • Case06: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 21 Kernel ID • Case07: The LT shall receive the SELECT command with AID A0000000010001 • Case07: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 23 Kernel ID • Case08: The LT shall receive the SELECT command with AID A0000000020002

2ED.003.02 ASRPD Data support

• Case08: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 22 Kernel ID • Case09: The LT shall receive the SELECT command with AID A0000000030003 • Case09: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 21 Kernel ID • Case10: The LT shall receive the SELECT command with AID A0000000010001 • Case10: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 23 Kernel ID • Case11: The LT shall receive the SELECT command with AID A0000000020002 • Case11: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 22 Kernel ID • Case12: The LT shall receive the SELECT command with AID A0000000030003 • Case12: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 21 Kernel ID

2ED.004.00 PPSE selection rejected

Test No: - Revision 2.5a – Number of sub cases: 2

Objective: To ensure that if the SELECT command with a file name of ‘2PAY.SYS.DDF01’is rejected (Status Word different from 9000), then the Entry Point shall send an End Application Outcome with the following Outcome Parameter values: • End Application: • Start: N/A • Online Response Data: N/A • CVM: N/A • Message on Outcome: ‘1C’ (“Insert, Swipe or Try Another Card”) • Message on Restart: None • Data Record Present: No. Test is done for Start A and B.

Reference Book B – version 2.3 – Requirement 3.3.2.3, 5.3.2.7 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and [Ltsetting6.1] (Select PPSE response without data and Status word: 6A82) and Amount = 2. • Case02: Entry Point transaction is performed with [Termsetting3] and [Ltsetting6.2] (Select PPSE response with data and Status word: 6283). Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings

Pass Criteria: • The Entry Point shall generate an Outcome ‘End Application’

2ED.005.00 PPSE select response without Directory Entry

Test No: - Revision 2.5a – Number of sub cases: 2

Objective: To ensure that if the SELECT PPSE response does not contain any Directory Entry, then the Entry Point shall send an End Application Outcome with the following Outcome Parameter values: • End Application: • Start: N/A • Online Response Data: N/A • CVM: N/A • Message on Outcome: ‘1C’ (“Insert; Swipe or Try Another Card”) • Message on Restart: None • Data Record Present: No. Test is done for Start A and B. Reference Book B – version 2.3 – Requirement 3.3.2.4, 5.3.2.7 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and Amount = 2. • Case02: Entry Point transaction is performed with [Termsetting3]. Action: NA

Procedure: Entry Point transactions are performed for different Term settings with [Ltsetting6.3] (Select PPSE response without any template 61 present)

Pass Criteria: • The Entry Point shall generate an Outcome ‘End Application’

2ED.007.00 PPSE select response with a Directory Entry wrongly coded on ADF name and another correctly coded

Test No: - Revision 2.4a – Number of sub cases: 2

Objective: To ensure that if a Directory Entry in the SELECT PPSE response is wrongly coded on ADF name, then the Entry Point shall drop this Directory Entry and continue with other directory entries. Test is done for Start A and B. Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and Amount = 2. • Case02: Entry Point transaction is performed with [Termsetting3]. Action: NA

Procedure: Entry Point transactions are performed for different Term settings with [Ltsetting6.5] (Select PPSE response with 3 templates 61 (AID 1 with the highest priority wrongly coded on 17 bytes, AID 2 with the middle priority wrongly coded on 4 bytes and AID 3 (APP1) with the lowest priority correctly coded on ADF name)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000010001),

2ED.007.01 PPSE select response with a Directory Entry with ADF name missing and another correctly coded

Test No: - Revision 2.4a – Number of sub cases: 2

Objective: To ensure that if a Directory Entry in the SELECT PPSE response has ADF name missing, then the Entry Point shall drop this Directory Entry and continue with other directory entries. Test is done for Start A and B. Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and Amount = 2. • Case02: Entry Point transaction is performed with [Termsetting3]. Action: NA

Procedure: Entry Point transactions are performed for different Term settings with [Ltsetting6.16] (Select PPSE response with 2 templates 61 (entry 1 with AID missing with the highest priority and entry 2 with AID 2 (APP1) with the lowest priority correctly coded on ADF name)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000010001),

2ED.008.00 PPSE select response having a Directory Entry with AID not matching

Test No: - Revision 2.4a – Number of sub cases: 2

Objective: To ensure that if the AID present in a Directory Entry does not match the AID of the Reader Combination selected, then the Entry Point shall drop the Directory Entry and continue with other Directory Entries. Test is done for Start A and B.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and Amount=2. • Case02: Entry Point transaction is performed with [Termsetting3]. Action: NA

Procedure: Entry Point transactions are performed for different Term settings with [Ltsetting6.6] (Select PPSE response with 3 templates 61 (AID1, 2, 3 (with the highest priority) do not match fully or partially with any AID of the Reader Combination and AID 4 (APP2) with the lowest priority matches with an AID of the Reader Combination)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000020002),

2ED.009.00 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = Visa AID, TK3 Kernel ID = ’03’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = Visa AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-3] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting1] and [Ltsetting5.1] (Single AID VISA (full match) (Kernel Identifier not present)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / [LT setting (AID A0 00 00 00 03 10 10) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘03’

2ED.009.01 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = Visa AID, TK3 Kernel ID not equal to ’03’ )

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = Visa AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-3] supported Configuration:

Conditions: Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.1] (Single AID VISA (full match) (Kernel Identifier not present)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / [LT setting (AID A0000000031010)

2ED.009.02 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = MasterCard AID, TK2 Kernel ID = ’02’)

Test No: - Revision 2.6a – Number of sub cases: 2

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = MasterCard AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-2] not supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting3] and [Ltsetting5.2] (Single AID MasterCard (partial match) (Kernel Identifier not present). • Case02: Entry Point transaction is performed with [Termsetting1] and [Ltsetting5.11] (Multi AID (MasterCard with the Highest priority (partial match) (Kernel Identifier not present) and Amount = 2.

Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings.

Pass Criteria: • Case01: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000004101001) • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘02’ • Case02: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000004101001) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘02’

2ED.009.03 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = MasterCard AID, TK2 Kernel ID not equal to ’02’)

Test No: - Revision 2.6a – Number of sub cases: 2

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = MasterCard AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-2] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting3] and [Ltsetting5.2] (Single AID MasterCard (partial match) (Kernel Identifier not present). • Case02: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.11] (Multi AID (MasterCard with the Highest priority (partial match) (Kernel Identifier not present) and Amount = 2.

Action: NA

Procedure: C-2 transactions are performed for different Term settings with different LT settings.

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000004101001) • In the GET PROCESSIGN OPTIONS command, the terminal shall provide the value ‘02’ for the tag D7

2ED.009.04 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = JCB AID, TK1 Kernel ID = ’05’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = JCB AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-5] not supported Configuration:

Conditions : NA Action : NA

Procedure: Entry Point transaction is performed with [Termsetting3] and [Ltsetting5.3] (Single AID JCB (full match) (Kernel Identifier not present).

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000651010) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘05’

2ED.009.05 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = JCB AID, TK1 Kernel ID not equal to ’05’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = JCB AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-5] supported Configuration:

Conditions: NA Action: NA

Procedure: Entry Point transaction is performed with [Termsetting3] and [Ltsetting5.3] (Single AID JCB (full match) (Kernel Identifier not present).

Pass Criteria: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000651010)

2ED.009.06 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = AMEX AID, TK4 Kernel ID = ’04’)

Test No: - Revision 2.6a – Number of sub cases: 2

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = AMEX AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-4] not supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Ltsetting5.4] (Single AID AMEX (partial match) (Kernel Identifier not present) and Amount = 2.

• Case02: Entry Point transaction is performed with [Ltsetting5.10] (Multi AID (AMEX with the Highest priority (full match) (Kernel Identifier not present) and Amount = 2.

Action: NA

Procedure: Entry Point transactions are performed for different [Termsetting1] with different LT settings.

Pass Criteria: • Case01: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000025101001) • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘04’ • Case02: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000251010) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘04’

2ED.009.07 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = AMEX AID, TK4 Kernel ID not equal to ’04’)

Test No: - Revision 2.6a – Number of sub cases: 2

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = AMEX AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-4] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Ltsetting5.4] (Single AID AMEX (partial match) (Kernel Identifier not present) and Amount = 2.

• Case02: Entry Point transaction is performed with [Ltsetting5.10] (Multi AID (AMEX with the Highest priority (full match) (Kernel Identifier not present) and Amount = 2.

Action: NA

Procedure: Entry Point transactions are performed for [Termsetting2] with different LT settings.

Pass Criteria: • Case01: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000025101001) • Case02: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000251010)

2ED.009.10 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = Visa AID, TK3 Kernel ID = ’03’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier has a zero length in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = Visa AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-3] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting1] and [Ltsetting5.13] (Single AID VISA (partial match) (Kernel Identifier with zero length)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / [LT setting (AID A000000003101001) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘03’

2ED.009.11 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = Visa AID, TK3 Kernel ID not equal to ’03’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier has a zero length in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID=Visa AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-3] supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.13] (Single AID VISA (partial match) (Kernel Identifier with zero length)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / [LT setting (AID A000000003101001)

2ED.009.12 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = MasterCard AID, TK2 Kernel ID = ’02’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier has a zero length in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = MasterCard AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-2] not supported Configuration:

Conditions : NA Action : NA

Procedure: Entry Point transaction is performed with [Termsetting3] and [Ltsetting5.14] (Single AID MasterCard (full match) (Kernel Identifier with zero length).

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000041010) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘02’

2ED.009.13 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = MasterCard AID, TK2 Kernel ID not equal to ’02’)

Test No: - Revision 2.6a – Number of sub cases: 0

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-2] supported Configuration:

Conditions: NA Action: NA

Procedure: Entry Point transaction is performed with [Termsetting3] and [Ltsetting5.14] (Single AID MasterCard (full match) (Kernel Identifier with zero length).

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000041010) • In the GET PROCESSIGN OPTIONS command, the terminal shall provide the value ‘02’ for the tag D7

2ED.009.14 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = JCB AID, TK1 Kernel ID = ’05’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier has a zero length in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = JCB AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-5] not supported Configuration:

Conditions : NA

Action : NA

Procedure: Entry Point transaction is performed with [Termsetting3] and [Ltsetting5.15] (Single AID JCB (partial match) (Kernel Identifier with zero length).

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000065101001) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘05’

2ED.009.15 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = JCB AID, TK1 Kernel ID not equal to ’05’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier has a zero length in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = JCB AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-5] supported Configuration:

Conditions: NA

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting3] and [Ltsetting5.15] (Single AID JCB (partial match) (Kernel Identifier with zero length).

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000065101001)

2ED.009.16 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = AMEX AID, TK4 Kernel ID = ’04’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier has a zero length in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = AMEX AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-4] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting1] and [Ltsetting5.16] (Single AID AMEX (full match) (Kernel Identifier with zero length)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000025101001) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘04’

2ED.009.17 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = AMEX AID, TK4 Kernel ID not equal to ’04’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier has a zero length in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = AMEX AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-4] supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.16] (Single AID AMEX (full match) (Kernel Identifier with zero length)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000025101001)

2ED.009.18 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = DISCOVER AID, TK6 Kernel ID = ’06’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = DISCOVER AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-6] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting1] and [Ltsetting5.17] (Single AID DISCOVER (full match) (Kernel Identifier not present)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / [LT setting (AID A0000001523010) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘06’

2ED.009.19 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = DISCOVER AID, TK6 Kernel ID not equal to ’06’ )

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = DISCOVER AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-6] supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.17] (Single AID DISCOVER (full match) (Kernel Identifier not present)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / [LT setting (AID A0000001523010)

2ED.009.20 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = DISCOVER AID, TK6 Kernel ID = ’06’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier has a zero length in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = DISCOVER AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-6] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting1] and [Ltsetting5.18] (Single AID DISCOVER (full match) (Kernel Identifier with zero length)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000152301001) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘06’

2ED.009.21 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = DISCOVER AID, TK6 Kernel ID not equal to ’06’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier has a zero length in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = DISCOVER AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-6] supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.18] (Single AID DISCOVER (full match) (Kernel Identifier with zero length)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000152301001) •

2ED.009.22 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = CUP AID, TK7 Kernel ID = ’07’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = CUP AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-7] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting1] and [Ltsetting5.19] (Single AID CUP (full match) (Kernel Identifier not present)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / [LT setting (AID A0000003330101) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘07’

2ED.009.23 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = CUP AID, TK7 Kernel ID not equal to ’07’ )

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = CUP AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-7] supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.19] (Single AID CUP (full match) (Kernel Identifier not present)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / [LT setting (AID A0000003330101) •

2ED.009.24 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = CUP AID, TK7 Kernel ID = ’07’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier has a zero length in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = CUP AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-7] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting1] and [Ltsetting5.20] (Single AID CUP (full match) (Kernel Identifier with zero length)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000333010101) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘07’

2ED.009.25 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = CUP AID, TK7 Kernel ID not equal to ’07’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier has a zero length in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = CUP AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-7] supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting1] and [Ltsetting5.20] (Single AID CUP (full match) (Kernel Identifier with zero length)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000333010101)

2ED.009.26 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = DISCOVER AID, TK6 Kernel ID = ’06’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = DISCOVER AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-6] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting1] and [Ltsetting5.23] (Single AID DISCOVER (full match) (Kernel Identifier not present)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / [LT setting (AID A0000003241010) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘06’

2ED.009.27 PPSE select response having a Directory Entry with Kernel Identifier not present (Matching AID = DISCOVER AID, TK6 Kernel ID not equal to ’06’ )

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier is not present in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = DISCOVER AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-6] supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.23] (Single AID DISCOVER (full match) (Kernel Identifier not present)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / [LT setting (AID A0000003241010) •

2ED.009.28 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = DISCOVER AID, TK6 Kernel ID = ’06’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier has a zero length in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = DISCOVER AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-6] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting1] and [Ltsetting5.24] (Single AID DISCOVER (full match) (Kernel Identifier with zero length)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000324101001) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘06’

2ED.009.29 PPSE select response having a Directory Entry with Kernel Identifier with zero length (Matching AID = DISCOVER AID, TK6 Kernel ID not equal to ’06’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that if the Kernel Identifier has a zero length in a Directory Entry, then the Entry Point shall use a Default value for the Requested Kernel ID when Matching AID = DISCOVER AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-6] supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.24] (Single AID DISCOVER (full match) (Kernel Identifier with zero length)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000324101001)

2ED.010.00 PPSE select response having a Directory Entry with Kernel Identifier wrong length

Test No: - Revision 2.6a – Number of sub cases: 2

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier length equal 0 or kernel ID byte 1 bit 8-7 set to 10b or 11b and kernel Identifier length is less than 3 then the Entry Point shall drop the Directory Entry and continue with other Directory Entries. Test is done for Start A and B.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and Amount = 2.

• Case02: Entry Point transaction is performed with [Termsetting3].

Action: NA

Procedure: Entry Point transactions are performed for different Term settings with [Ltsetting6.7] (Select PPSE response with 3 templates 61 (2 templates with the highest priority and a wrong kernel Identifier length and the last one (lowest priority) with a correct kernel Identifier value)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000040004) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 24

2ED.011.00 PPSE select response having a Directory Entry with Kernel Identifier not matching

Test No: - Revision 2.6a – Number of sub cases: 3

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier does not match the kernel ID of the reader combination then the Entry Point shall drop the Directory Entry and continue with other Directory Entries. Test is done for Start A and B, full match and partial match on the AID

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and [Ltsetting4.1] (Select PPSE response with 7 templates 61 (6 templates with the highest priority and a kernel Identifier that does not match any kernel ID of the reader combination of [Termsetting1] and the last one (lowest priority) with a kernel Identifier matching) and Amount = 2.

• Case02: Entry Point transaction is performed with [Termsetting2] and [Ltsetting4.2] (Select PPSE response with 7 templates 61 (6 templates with the highest priority and a kernel Identifier that does not match any kernel ID of the reader combination of [Termsetting2] and the last one (lowest priority) with a kernel Identifier matching) with a correct kernel ID value) and Amount = 2.

• Case03: Entry Point transaction is performed with [Termsetting3] and [Ltsetting4.2] (Select PPSE response with 7 templates 61 (6 templates with the highest priority and a kernel Identifier that does not match any kernel ID of the reader combination of [Termsetting3] and the last one (lowest priority) with a kernel Identifier matching) with a correct kernel ID value).

Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000040004)

2ED.011.00 PPSE select response having a Directory Entry with Kernel Identifier not matching

• The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 24

2ED.012.00 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = Visa AID, TK3 Kernel ID = ’03’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination when Matching AID = Visa AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-3] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.5] (Select PPSE response with Single AID VISA with full match on AID and Kernel Identifier = ’00’)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000031010) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘03‘

2ED.012.01 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = Visa AID, TK3 Kernel ID not equal to ’03’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination when Matching AID = Visa AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-3] supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.5] (Select PPSE response with Single AID VISA with full match on AID and Kernel Identifier = ’00’)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000031010)

2ED.012.02 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = MasterCard AID, TK2 Kernel ID = ’02’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination when Matching AID = MasterCard AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-2] not supported Configuration:

Conditions : NA

Action : NA

Procedure: : Entry Point transaction is performed with [Termsetting3] and [Ltsetting5.6] (Select PPSE response with Single AID MasterCard with partial match on AID and Kernel Identifier = ’00’).

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000004101001) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘02’

2ED.012.03 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = MasterCard AID, TK2 Kernel ID not equal to ’02’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination when Matching AID=MasterCard AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-2] supported Configuration:

Conditions: NA

Action: NA

Procedure: A C-2 transaction is performed with [Termsetting3] and [Ltsetting5.6] (Select PPSE response with Single AID MasterCard with partial match on AID and Kernel Identifier = ’00’).

2ED.012.04 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = JCB AID, TK5 Kernel ID = ’05’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-5] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.7] (Select PPSE response with Single AID JCB with full match on AID and Kernel Identifier = ’00’).

2ED.012.05 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = JCB AID, TK5 Kernel ID not equal to ’05’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-5] supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.7] (Select PPSE response with Single AID JCB with full match on AID and Kernel Identifier = ’00’).

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000651010)

2ED.012.06 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = AMEX AID, TK4 Kernel ID = ’04’)

Test No: - Revision 2.6a – Number of sub cases: 2

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination when Matching AID = AMEX AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-4] not supported Configuration:

Conditions: • Amount = 300

• Case01: Entry Point transaction is performed with [Termsetting3] and [Ltsetting5.8] (Select PPSE response with Single AID AMEX with partial match on AID and Kernel Identifier = ’00’).

• Case02: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.12] (Select PPSE response with multi AID: AMEX with full match on AID and Kernel Identifier = ’00’ and the highest priority)

Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings.

2ED.012.07 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = AMEX AID, TK4 Kernel ID not equal to ’04’)

Test No: - Revision 2.6a – Number of sub cases: 2

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination when Matching AID = AMEX AID.

Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-4] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting3] and [Ltsetting5.8] (Select PPSE response with Single AID AMEX with partial match on AID and Kernel Identifier = ’00’).

• Case02: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.12] (Select PPSE response with multi AID: AMEX with fullmatch on AID and Kernel Identifier = ’00’ and the highest priority) and Amount = 2.

Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings.

2ED.012.08 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID, Kernel ID = domestic Kernel)

Test No: - Revision 2.6a – Number of sub cases: 4

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination when Matching AID. Subcases are defined for several types of Domestic kernel ID. Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Ltsetting1.93] (Select PPSE response with Single AID = ’B0000000010101’ and Kernel Identifier = ’00’).

• Case02: Entry Point transaction is performed with [Ltsetting1.94] (Select PPSE response with Single AID = ’B0000000010102’ and Kernel Identifier = ’00’).

• Case03: Entry Point transaction is performed with [Ltsetting1.95] (Select PPSE response with Single AID = ’B0000000010103’ and Kernel Identifier = ’00’).

• Case04: Entry Point transaction is performed with [Ltsetting1.96] (Select PPSE response with Single AID = ’B0000000010104’ and Kernel Identifier = ’00’).

Action: NA

Procedure: Entry Point transactions are performed for [Termsetting13] with different LT settings.

Pass Criteria: • Case01: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID= ’B0000000010101’) • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘81’ • Case02: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID= ’B0000000010102’) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘BF’

2ED.012.08 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID, Kernel ID = domestic Kernel)

• Case03: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID= ’B0000000010103’) • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘C1’ • Case04: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID= ’B0000000010104’) • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘FF’

2ED.012.10 Matching combination with International or Domestic Kernel ID

Test No: - Revision 2.6a – Number of sub cases: 10

Objective: To ensure that, in a Directory Entry, if a single AID/ Kernel Identifier matches a reader Combination, the combination is selected. Test is done for an International or Domestic Kernel ID, full match and partial match on the AID Reference Book B – version 2.3 – Requirement 3.3.2.5 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Ltsetting1.1] (Select PPSE response with Single AID APP1 with full match on AID and Kernel Identifier = 23) and Amount = 2.

• Case02: Entry Point transaction is performed with [Ltsetting1.2] (Select PPSE response with Single AID APP2 with full match on AID and Kernel Identifier = 22) and Amount = 2.

• Case03: Entry Point transaction is performed with [Ltsetting1.3] (Select PPSE response with Single AID APP3 with full match on AID and Kernel Identifier = 21) and Amount = 2.

• Case04: Entry Point transaction is performed with [Ltsetting1.4] (Select PPSE response with Single AID APP4 with full match on AID and Kernel Identifier = 24) and Amount = 2.

• Case05: Entry Point transaction is performed with [Ltsetting1.84] (Select PPSE response with Single AID APP2 with partial match on AID and Kernel Identifier = ’32’) and Amount = 2.

• Case06: Entry Point transaction is performed with [Ltsetting1.85] (Select PPSE response with Single AID ‘B0000000010101’ with full match on AID and Kernel Identifier = ‘810978’) and Amount = 2.

• Case07: Entry Point transaction is performed with [Ltsetting1.86] (Select PPSE response with Single AID APP4 with partial match on AID and Kernel Identifier = ’ BF0840’) and Amount = 2.

• Case08: Entry Point transaction is performed with [Ltsetting1.87] (Select PPSE response with Single AID ‘B000000001010102’ with

2ED.012.10 Matching combination with International or Domestic Kernel ID

partial match on AID and Kernel Identifier = ‘C11111’) and Amount = 2.

• Case09: Entry Point transaction is performed with [Ltsetting1.88] (Select PPSE response with Single AID APP3 with full match on AID and Kernel Identifier = ’ FF2222’) and Amount = 2.

• Case10: Entry Point transaction is performed with [Ltsetting1.97] (Select PPSE response with Single AID APP3 with full match on AID and Kernel Identifier = 25) and Amount = 2.

Action: NA

Procedure: Entry Point transactions are performed for [Termsetting1] with different LT settings.

Pass Criteria: • Case01: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000010001) • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 23 • Case02: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000020002) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 22 • Case03: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000030003) • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 21 • Case04: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000040004) • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 24 • Case05: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A00000002000201) • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘32’ • Case06: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID B0000000010101)

2ED.012.10 Matching combination with International or Domestic Kernel ID

• Case06: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1-3 set to ‘810978’ • Case07: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A00000004000401) • Case07: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1-3 set to ‘BF0840’ • Case08: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID B000000001010102) • Case08: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1-3 set to ‘C11111’ • Case09: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000030003) • Case09: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1-3 set to ‘FF2222’ • Case10: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000030003) • Case10: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 25

2ED.012.11 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = DISCOVER AID, TK6 Kernel ID = ’06’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination when Matching AID = DISCOVER AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-6] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.21] (Select PPSE response with Single AID DISCOVER with full match on AID and Kernel Identifier = ’00’)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000001523010) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘06’

2ED.012.12 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = DISCOVER AID, TK6 Kernel ID not equal to ’06’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination when Matching AID = DISCOVER AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-6] supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.21] (Select PPSE response with Single AID DISCOVER with full match on AID and Kernel Identifier = ’00’)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000001523010)

2ED.012.13 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = CUP AID, TK7 Kernel ID = ’07’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value the Entry Point will use the Kernel ID of the reader Combination when Matching AID = CUP AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-7] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.22] (Select PPSE response with Single AID CUP with full match on AID and Kernel Identifier = ’00’)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000003330101) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘07’

2ED.012.14 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = CUP AID, TK7 Kernel ID not equal to ’07’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination when Matching AID = CUP AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-7] supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.22] (Select PPSE response with Single AID CUP with full match on AID and Kernel Identifier = ’00’)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000003330101)

2ED.012.15 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = DISCOVER AID, TK6 Kernel ID = ’06’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination when Matching AID = DISCOVER AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-6] not supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.25] (Select PPSE response with Single AID DISCOVER with full match on AID and Kernel Identifier = ’00’)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000003241010) • The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘06’

2ED.012.16 PPSE select response having a Directory Entry with Kernel Identifier=’00’ (Matching AID = DISCOVER AID, TK6 Kernel ID not equal to ’06’)

Test No: - Revision 2.6a – Number of sub cases: 0

Objective: To ensure that, in a Directory Entry, if the Kernel Identifier has a zero value then the Entry Point will use the Kernel ID of the reader Combination when Matching AID = DISCOVER AID.

Reference Book B – version 2.4 – Requirement 3.3.2.5 BOOK A/B:

Terminal [C-6] supported Configuration:

Conditions: • Amount = 2.

Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting5.25] (Select PPSE response with Single AID DISCOVER with full match on AID and Kernel Identifier = ’00’)

Pass Criteria: • The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000003241010)

2ED.013.00 PPSE select response having each Directory Entry with different priority set

Test No: - Revision 2.6a – Number of sub cases: 10

Objective: To ensure that, when the Directory Entries have the priority set then the Entry Point will use the AID/Kernel ID of a reader Combination allowed with the highest priority. Test is done for Start A and B, full match and partial match on the AID, kernel ID international and domestic

Reference Book B – version 2.3 – Requirement 3.3.2.5, 3.3.2.2 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting3] and [Ltsetting2.20] (Select PPSE response with multi AID: full match on AID and Kernel ID, APP3 AID with the highest priority (equal 1) to be selected).

• Case02: Entry Point transaction is performed with [Termsetting2] and [Ltsetting2.20] (Select PPSE response with multi AID: full match on AID and Kernel ID, APP3 AID with the highest priority (equal 1) to be selected) and Amount = 2.

• Case03: Entry Point transaction is performed with [Termsetting2] and [Ltsetting2.20 (Select PPSE response with multi AID: full match on AID and Kernel ID, APP2 AID with priority=2 to be selected and Amount = 121.

• Case04: Entry Point transaction is performed with [Termsetting3] and [Ltsetting2.21] (Select PPSE response with multi AID: full match on AID and Kernel ID, APP1 AID with the highest priority (equal 4) to be selected).

• Case05: Entry Point transaction is performed with [Termsetting2] and [Ltsetting2.21] (Select PPSE response with multi AID: full match on AID and Kernel ID, APP4 AID with the highest priority (equal 5) to be selected) and Amount = 0.

• Case06: Entry Point transaction is performed with [Termsetting3] and [Ltsetting3.1] (Select PPSE response with multi AID: partial match on AID and Kernel ID, APP4 AID with the highest priority (equal 1) to be selected).

2ED.013.00 PPSE select response having each Directory Entry with different priority set

• Case07: Entry Point transaction is performed with [Termsetting2] and [Ltsetting3.1] (Select PPSE response with multi AID: partial match on AID and Kernel ID, APP2 AID with the highest priority (equal 2) to be selected) and Amount = 0.

• Case08: Entry Point transaction is performed with [Termsetting1] and [Ltsetting2.24] (Select PPSE response with multi AID: full match on AID and Kernel ID, APP2 AID with domestic kernel with the highest priority (equal 10) to be selected) and Amount = 2.

• Case09: Entry Point transaction is performed with [Termsetting1] and [Ltsetting3.4] (Select PPSE response with multi AID: partial match on AID and Kernel ID, APP4AID with domestic kernel with the highest priority (equal 3) to be selected) and Amount = 2.

• Case10: Entry Point transaction is performed with [Termsetting2] and [Ltsetting2.44] (Select PPSE response with multi AID: full match on AID and Kernel ID, APP3 AID with the highest priority (equal 4) to be selected) and Amount = 201.

Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings.

Pass Criteria: • Case01: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000030003) • Case01The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 21 • Case02: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000030003) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 21 • Case03: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AIDA000000020002) • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘2B’ • Case04: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000010001)

2ED.013.00 PPSE select response having each Directory Entry with different priority set

• Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 23 • Case05: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000040004) • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 23 • Case06: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A00000004000401 02 03 04 05 06 07 08 09) • Case06: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 24 • Case07: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A00000002000201 02 03 04 05 06 07 08 09) • Case07: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘24 • Case08: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000020002) • Case08: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘810978’ • Case09: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000040004010203040506070809) • Case09: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to ‘FF2222’ • Case10: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A000000030003) • Case10: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 25

2ED.014.00 PPSE select response having several Directory Entries with same highest priority set

Test No: - Revision 2.6a – Number of sub cases: 5

Objective: To ensure that, when several Directory Entries have the same highest priority set, the Entry Point select the Entry corresponding to a Reader combination allowed which occurs first in the Directory Entries. Test is done for Start A and B, full match and partial match on the AID Reference Book B – version 2.3 – Requirement 3.3.2.5, 3.3.2.2 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting3] and [Ltsetting2.22] (Select PPSE response with multi AID: full match on AID and Kernel ID, APP2 AID with the highest priority (equal 1) and occurs first in the Directory Entries).

• Case02: Entry Point transaction is performed with [Termsetting2] and [Ltsetting2.22] (Select PPSE response with multi AID: full match on AID and Kernel ID, APP2 AID with the highest priority (equal 1) occurs first in the Directory Entries) and Amount = 121.

• Case03: Entry Point transaction is performed with [Termsetting3] and [Ltsetting3.2] (Select PPSE response with multi AID: partial match on AID and Kernel ID, APP1 with the highest priority (equal 14) occurs first in the Directory Entries).

• Case04: Entry Point transaction is performed with [Termsetting2] and [Ltsetting3.2] (Select PPSE response with multi AID: full match on AID and Kernel ID, APP4 AID with highest priority (equal 14) occurs first in the Directory Entries) and Amount = 0.

• Case05: Entry Point transaction is performed with [Termsetting2] and [Ltsetting3.6] (Select PPSE response with multi AID: partial match on AID and Kernel ID, APP4 AID with highest priority (equal 8) occurs first in the Directory Entries) and Amount = 2.

Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings.

2ED.014.00 PPSE select response having several Directory Entries with same highest priority set

Pass Criteria: • Case01: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000020002) • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 24 • Case02: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000020002) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 24 • Case03: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000010001010203040506070809) • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 23 • Case04: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000040004010203040506070809) • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 23 • Case05: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000040004010203040506070809) • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 25

2ED.015.00 PPSE select response having Directory Entries with priority=’00’ or no priority set

Test No: - Revision 2.6a – Number of sub cases: 5

Objective: To ensure that, when Directory Entries have priority ‘00’ or priority not present set then the Entry point selects the Entry corresponding to a Reader combination allowed which occurs first in the Directory Entries. Test is done for Start A and B, full match and partial match on the AID

Reference Book B – version 2.3 – Requirement 3.3.2.5, 3.3.2.2 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting3] and [Ltsetting2.23] (Select PPSE response with multi AID: full match on AID and Kernel ID, APP1 AID with the priority (equal 0) and occurs first in the Directory Entries).

• Case02: Entry Point transaction is performed with [Termsetting2] and [Ltsetting2.23] (Select PPSE response with multi AID: full match on AID and Kernel ID, APP3 AID with the priority not present occurs first in the Directory Entries) and Amount = 0.

• Case03: Entry Point transaction is performed with [Termsetting3] and [Ltsetting3.3] (Select PPSE response with multi AID: partial match on AID and Kernel ID, APP1 with the priority (equal 0) occurs first in the Directory Entries).

• Case04: Entry Point transaction is performed with [Termsetting2] and [Ltsetting3.3] (Select PPSE response with multi AID: full match on AID and Kernel ID, APP4 AID with priority not present occurs first in the Directory Entries) and Amount = 0.

• Case05: Entry Point transaction is performed with [Termsetting2] and [Ltsetting3.7] (Select PPSE response with multi AID: partial match on AID and Kernel ID, APP3 AID with the priority not present occurs first in the Directory Entries) and Amount = 2.

Action: NA

2ED.015.00 PPSE select response having Directory Entries with priority=’00’ or no priority set

Procedure: Entry Point transactions are performed for different Term settings with different LT settings.

Pass Criteria: • Case01: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000010001) • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 23 • Case02: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000030003) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 21 • Case03: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000010001010203040506070809) • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 23 • Case04: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000040004010203040506070809) • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 23 • Case05: The terminal shall select the appropriate Combination according to the Terminal / LT setting (AID A0000000030003010203040506070809) • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID byte 1 set to 25

2ED.016.00 Candidate List empty

Test No: - Revision 2.5a – Number of sub cases: 0

Objective: To ensure that if the Candidate List is empty after all Directory Entries analysis, then the Entry Point shall send an End Application Outcome with the following Outcome Parameter values: • End Application: • Start: N/A • Online Response Data: N/A • CVM: N/A • UI Request on Outcome Present: Yes o Message on Outcome: ‘1C’ (“Insert, Swipe or Try Another Card”) o Status: Ready To Read • Message on Restart: None • Data Record Present: No. • Discretionary Data Present: No • Alternate Interface Preference: N/A • Receipt: N/A • Field Off Request: N/A • Removal Timeout: Zero

Reference Book B – version 2.3 – Requirement 3.3.2.6 BOOK A/B:

Terminal NA Configuration:

Conditions: • Amount = 0 (to have No reader combination selected after all Directory Entries analysis). Action: NA

Procedure: Entry Point transaction is performed with [Termsetting2] and [Ltsetting4.2] .

Pass Criteria: • The Entry Point shall generate an Outcome ‘End Application’

2ED.016.00 Candidate List empty

2ED.017.00 Extended selection present in Directory Entry but Extended Selection Support flag not present or not set in Reader Combination

Test No: - Revision 2.4a – Number of sub cases: 2

Objective: To ensure that if the Extended Selection data element (Tag ‘9F29’) is present in the Combination selected, and the Extended Selection Support flag is not present or present and set to0 for this Combination, then the Entry Point shall not append the value contained in Extended Selection to the ADF name in the data field of the SELECT command. Test is done for Start A and B, full match and partial match on the AID Reference Book B – version 2.3 – Requirement 3.3.3.3 BOOK A/B:

Terminal [Extended Selection] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting3] • Case02: Entry Point transaction is performed with [Termsetting2] and Amount = 0 Action: NA

Procedure: An Entry Point transactions are performed for different Term settings with [Ltsetting3.5] (Directory Entries with Extended Selection Data for AID APP1 (partial match) but the Extended Selection Support flag is not present for the reader combination)

Pass Criteria: • Case01: The LT shall receive the SELECT command with AID ‘A000000001000101’ (corresponding to the the APP1 AID without Extended Selection Data) • Case02: The LT shall receive the SELECT command with AID ‘A0000000020002’ (corresponding to the the APP2 AID without Extended Selection Data)

2ED.017.01 Extended selection present in Directory Entry but Extended Selection not supported in ICS

Test No: - Revision 2.4a – Number of sub cases: 0

Objective: To ensure that if the Extended Selection data element (Tag ‘9F29’) is present in the Combination selected, and the Extended Selection is not supported in ICS, then the Entry Point shall not append the value contained in Extended Selection to the ADF name in the data field of the SELECT command.

Reference Book B – version 2.3 – Requirement 3.3.3.3 BOOK A/B:

Terminal [Extended Selection] not supported Configuration:

Conditions : NA Action : NA

Procedure: Entry Point transaction is performed for [Termsetting3] with [Ltsetting3.5] (Directory Entries with Extended Selection Data for AID APP1)

Pass Criteria: • The LT shall receive the SELECT command with AID ‘A000000001000101’ (corresponding to the the APP1 AID without Extended Selection Data)

2ED.018.00 Extended selection present in Directory Entry and Extended Selection Support flag set in Reader Combination

Test No: - Revision 2.6a – Number of sub cases: 5

Objective: To ensure that if the Extended Selection data element (Tag ‘9F29’) is present in the Combination selected, and the Extended Selection Support flag is present and set to 1 for this Combination, then the Entry Point shall append the value contained in Extended Selection to the ADF name in the data field of the SELECT command. Test is done for Start A and B, full match and partial match on the AID

Reference Book B – version 2.3 – Requirement 3.3.3.3 BOOK A/B:

Terminal [Extended Selection] supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and [Ltsetting3.5] (Directory Entries with Extended Selection Data for AID APP1 (partial match)) and Amount = 2 • Case02: Entry Point transaction is performed with [Termsetting2] and [Ltsetting1.30] (Directory Entries with Extended Selection Data for AID APP3 (full match)) and Amount = 2 • Case03: Entry Point transaction is performed with [Termsetting3] and [Ltsetting1.30] (Directory Entries with Extended Selection Data for AID APP3 (full match)) • Case04: Entry Point transaction is performed with [Termsetting1] and [Ltsetting1.31] (Directory Entries with Extended Selection Data for AID B0000000010101 (full match)) and Amount = 2 • Case05: Entry Point transaction is performed with [Termsetting1] and [Ltsetting1.101] (Directory Entries with Extended Selection Data for AID APP4 (full match)) and Amount = 2 Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings.

Pass Criteria: • Case01: The LT shall receive the SELECT command with AID ‘A0000000010001010303’ (corresponding to the APP1 AID with Extended Selection Data)

2ED.018.00 Extended selection present in Directory Entry and Extended Selection Support flag set in Reader Combination

• Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 23. • Case02: The LT shall receive the SELECT command with AID ‘A0000000030003010203040506070809’ (corresponding to the APP3 AID with Extended Selection Data) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 21 • Case03: The LT shall receive the SELECT command with AID ‘A0000000030003010203040506070809’ (corresponding to the APP3 AID with Extended Selection Data) • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 21 • Case04: The LT shall receive the SELECT command with AID ‘B00000000101011122 (corresponding to the AID with Extended Selection Data) • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = ‘C11111’. • Case05: The LT shall receive the SELECT command with AID ‘A0000000040004010203040506070809’ (corresponding to the APP4 AID with Extended Selection Data) • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 25

2ED.019.00 Final selection rejected (restart flag = 0)

Test No: - Revision 2.6a – Number of sub cases: 4

Objective: To ensure that if the Select AID responds with a Status Word different from 9000 and restart flag is set to 0, then the Entry Point shall remove the selected Combination associated with this ADF Name from the Candidate List and shall send a SELECT command for the next AID. Test is done for Start A and B, full match and partial match on the AID

Reference Book B – version 2.5 – Requirement 3.3.3.5, BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting3] and [Ltsetting6.8] (Select AID APP3 and APP2 rejected) and • Case02: Entry Point transaction is performed with [Termsetting2] and [Ltsetting6.8] (Select AID APP2 rejected) and Amount = 121 • Case03: Entry Point transaction is performed with [Termsetting3] and [Ltsetting6.17] (first Select AID APP3 rejected) and Amount = 10 • Case04: Entry Point transaction is performed with [Termsetting2] and [Ltsetting6.18] (Select AID APP3 rejected) and Amount = 2 Action: NA

Procedure: An Entry Point transaction is performed for different Term settings with different LT settings without a restart.

Pass Criteria: • Case01: The LT shall receive the SELECT command with AID ‘A0000000010001’ (corresponding to the APP1 AID after rejection of the Select AID A0000000030003 and A00000000200020101) • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 23 • Case02: The LT shall receive the SELECT command with AID ‘A0000000010001’ (corresponding to the APP1 AID after rejection of the Select AID A00000000200020101) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 23

2ED.019.00 Final selection rejected (restart flag = 0)

• Case03: The LT shall receive the SELECT command with AID ‘A0000000030003’ (corresponding to the APP3 AID after rejection of the Select AID A0000000030003) • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 22 • Case04: The LT shall receive the SELECT command with AID ‘A0000000040004’ (corresponding to the APP4 AID after rejection of the Select AID A0000000030003) • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 25

2ED.019.01 Final selection rejected (restart flag = 1)

Test No: - Revision 2.6a – Number of sub cases: 2

Objective: To ensure that if the Select AID responds with a Status Word different from 9000 and restart flag is set to 1, then the Entry Point shall provide an End Application Outcome.

Test is done for a Restart A, B, C and D.

Reference Book B – version 2.5 – Requirement 3.3.3.5 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case02: Entry Point transaction is performed with [Ltsetting6.20] (UI Request on Restart Present is ‘Yes’, requesting a Restart B, and Issuer Authentication Data received) • Case03: Entry Point transaction is performed with [Ltsetting6.21] (UI Request on Restart Present is ‘Yes’, requesting a Restart C) Action: NA

Procedure: • An Entry Point transactions are performed with restart sequence for [Termsetting1] with different LT settings and at restart the SELECT (AID) response has a Status word different from 9000.

Pass Criteria: • The terminal shall display Message Identifier ‘1C’ (“Insert, Swipe or Try Another Card”) after restart.

2ED.019.01 Final selection rejected (restart flag = 1)

2ED.020.00 Visa Kernel 3 replaced by Kernel 1

Test No: - Revision 2.6a – Number of sub cases: 2

Objective: To ensure that if the Select AID indicates VISA AID and the kernel in the Combination is Kernel 3 and if the PDOL in the FCI is absent or the PDOL in the FCI does not include Tag ‘9F66’, and Kernel 1 is supported, then Entry Point shall change the Kernel ID for this AID from the initial Kernel 3 to Kernel 1 Test is done for Start A and B, full match and partial match on the AID Reference Book B – version 2.3 – Requirement 3.3.3.6 BOOK A/B:

Terminal [C-1] and [C-3] not supported Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting2] and [Ltsetting2.30] (Select AID VISA (full AID) (with kernel 3) returns a PDOL without TTQ) and Amount = 2 • Case02: Entry Point transaction is performed with [Termsetting3] and [Ltsetting2.31] (Select AID VISA (partial AID) (with kernel 3) returns no PDOL) Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings.

Pass Criteria: • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = ‘01’. • Case02: The LT shall receive the GET PROCESSING OPTIONS after the Select AID VISA.

2ED.021.00 Visa Kernel 3 not allowed

Test No: - Revision 2.6a – Number of sub cases: 2

Objective: To ensure that if the Select AID indicates VISA AID and the kernel in the Combination is Kernel 3 and if the PDOL in the FCI is absent or the PDOL in the FCI does not include Tag ‘9F66’, and Kernel 1 is not supported, then Entry Point shall remove the selected Combination associated with this ADF Name from the Candidate List and shall send a SELECT command for the next AID. Test is done for Start A and B, full match and partial match on the AID

Reference Book B – version 2.3 – Requirement 3.3.3.6 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting6] and [Ltsetting2.30] (Select AID VISA (full AID) (with kernel 3) returns a PDOL without TTQ) and Amount = 2 • Case02: Entry Point transaction is performed with [Termsetting7] and [Ltsetting2.31] (Select AID VISA (partial AID) (with kernel 3) returns no PDOL) Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings.

Pass Criteria: • Case01: The LT shall receive the SELECT command with AID ‘A0000000251010’ (corresponding to the AMEX AID after the Select AID A0000000031010) • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = TK4 Kernel ID • Case02: The LT shall receive the SELECT command with AID ‘A0000000251010’ (corresponding to the AMEX AID after the Select AID A000000003101001)

2ED.022.00 Communication error during final selection

Test No: - Revision 2.4a – Number of sub cases: 0

Objective: To ensure that if the Select AID does not respond, then Entry Point shall return to Start B (Protocol Activation, section 3.2.1). Reference Book B – version 2.3 – Requirement 3.3.3.7 BOOK A/B:

Terminal NA Configuration:

Conditions: Entry Point transaction sends the Select AID

Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with [Ltsetting6.9] (no response on Select AID)

Pass Criteria: • The LT shall receive the SELECT PPSE command after the Select AID which has no response

9.5. Kernel Activation

2EE.001.00 FCI and Status Word to kernel

Test No: - Revision 1 – Number of sub cases: 2

Objective: To ensure that if the FCI and the Status Word of Select AID response are provided to the kernel. Reference Book B – version 2.3 – Requirement 3.4.1.3 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting1] and [Ltsetting1.32] (Select AID response with FCI length = 251 bytes and PDOL including FCI tag) and Amount = 2 • Case02: Entry Point transaction is performed with [Termsetting3] and [Ltsetting1.33] (PDOL including FCI tag and Select response Status Word) Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different LT settings.

Pass Criteria: • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Expected FCI with a length of 251 bytes. • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Expected FCI • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Status Word of the Select response (9000)

2EE.002.00 Kernel Activation of the Selected Combination

Test No: - Revision 2.6a – Number of sub cases: 5

Objective: To ensure that Entry Point shall activate the kernel identified in the selected Combination. Test is done for Start A and B.

Reference Book B – version 2.3 – Requirement 3.4.1.1 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting2] and [Ltsetting1.1] (AID APP1 with Kernel ID 23) and Amount = ‘Single Unit of Currency’ • Case02: Entry Point transaction is performed with [Termsetting2] and [Ltsetting1.4] (AID APP4 with Kernel ID 24) and Amount = 51(greater than Reader Contactless Floor Limit and greater than Reader CVM Required Limit) • Case03: Entry Point transaction is performed with [Termsetting3] and [Ltsetting2.10] (multiapplication card: APP3 AID/ Kernel ID 21 has the highest priority) • Case04: Entry Point transaction is performed with [Termsetting2] and [Ltsetting2.10] (multiapplication card: APP2 AID/ Kernel ID 24 has the highest priority when Amount is greater that Reader Contactless Transaction Limit of the APP3AID/21 ) Amount = 121 (greater than Reader Contactless Floor Limit) • Case05: Entry Point transaction is performed with [Termsetting2] and [Ltsetting1.97] (AID APP3 with Kernel ID 25)and an Amount=2 Action: NA

Procedure: Entry Point transactions are performed for different Term settings with different Term settings.

Pass Criteria: • Case01: The LT shall receive the SELECT command with AID ‘A0000000010001’ (corresponding to APP1) • Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 23.

2EE.002.00 Kernel Activation of the Selected Combination

• Case01: The LT shall receive in the GET PROCESSING OPTIONS data field: Pre-Processing Indicators (tag ‘D1’) Byte 1 bit 5 set to ‘1b’. • Case02: The LT shall receive the SELECT command with AID ‘A0000000040004’ (corresponding to APP4) • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 24. • Case02: The LT shall receive in the GET PROCESSING OPTIONS data field: Pre-Processing Indicators (tag ‘D1’) = ‘A0’. • Case03: The LT shall receive the SELECT command with AID ‘A0000000030003’ (corresponding to APP3) • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 21. • Case03: The LT shall receive in the GET PROCESSING OPTIONS data field: Pre-Processing Indicators (tag ‘D1’) = ‘00’. • Case04: The LT shall receive the SELECT command with AID ‘A0000000020002’ (corresponding to APP2) • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 24. • Case04: The LT shall receive in the GET PROCESSING OPTIONS data field: Pre-Processing Indicators (tag ‘D1’) = ‘80’. • Case05: The LT shall receive the SELECT command with AID ‘A0000000030003’ (corresponding to APP3) • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: Kernel ID = 25. • Case05: The LT shall receive in the GET PROCESSING OPTIONS data field: Pre-Processing Indicators (tag ‘D1’) = ‘00’.

9.6. Outcome Processing

2EF.001.00 Outcome with UI Request and Field Off

Test No: - Revision 2.6a – Number of sub cases: 8

Objective: To ensure that if an Outcome has a UI Request on Outcome Present equal to ‘Yes’, then Entry Point shall send the associated User Interface Request. To ensure that if an Outcome parameter Field Off Request has a value other than NA, then the field shall be turned off and shall remain off for the period indicated by the hold time. Test are performed for all Outcomes defined in Annex B of Book A.

Reference Book B – version 2.3 – Requirement 3.5.1.1, 3.5.1.2, 3.5.1.5 BOOK A/B:

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Ltsetting1.1] (Outcome ‘Approved’ with UI Request “Approved”) and Amount = 2 • Case02: Entry Point transaction is performed with [Ltsetting1.40] (Outcome ‘Declined’ with UI Request “Not Authorized’’) and Amount = 2 • Case03: Entry Point transaction is performed with [Ltsetting1.41] (Outcome ‘Try Another Interface’ with UI Request”‘Please insert or swipe card”) and Amount = 2 • Case04: Entry Point transaction is performed with [Ltsetting1.42] (Outcome ‘Online Request’ with UI Request “Authorising, Please Wait”) and Amount = 2 • Case06: Entry Point transaction is performed with [Ltsetting1.47] (Outcome ‘Online Request (Present and Hold)’ with UI Request “Authorising, Please Wait”) and Amount = 2 • Case08: Entry Point transaction is performed with [Ltsetting2.40] (Outcome ‘Select Next’) and Amount = 2 • Case09: Entry Point transaction is performed with [Ltsetting1.49] (Outcome ‘End Application’ with UI Request ‘Insert, Swipe or Try Another Card”) and Amount = 2 • Case10: Entry Point transaction is performed with [Ltsetting1.35] (Outcome ‘End Application (with restart)’ with UI Request ‘Present Card Again”) and Amount = 2

2EF.001.00 Outcome with UI Request and Field Off

Action: NA

Procedure: Entry Point transactions are performed for [Termsetting2] with different LT settings.

Pass Criteria: • Case01: The UI Request on Outcome: MSG ID ‘03’ (“Approved”) is correctly displayed at end of the transaction • Case02: The UI Request on Outcome: MSG ID ‘07’ (“Not Authorised”) is correctly displayed at end of the transaction • Case03: The UI Request on Outcome: MSG ID ‘18’ (“Please insert or swipe card”) is correctly displayed at end of the transaction • Case04: The UI Request on Outcome: MSG ID ‘1B’ (“Authorizing, Please Wait”) is correctly displayed at end of the transaction • Case06: The UI Request on Outcome: MSG ID ‘1B’ (“Authorizing, Please Wait”) is correctly displayed at 1st Outcome • Case06: the field shall remain on after the 1st Outcome • Case06: The UI Request on Restart: MSG ID ‘16’ (“Processing”) is correctly displayed at 1st Outcome Restart • Case08: the field shall remain on after the 1st Outcome • Case09: The UI Request on Outcome: MSG ID ‘1C’ (“Insert, Swipe or Try Another Card”) is correctly displayed at end of the transaction • Case10: The UI Request on Outcome: MSG ID ‘21’ (“Present Card Again”) is correctly displayed at 1st Outcome • Case10: The UI Request on Restart: MSG ID ‘21’ (“Present Card Again”) is correctly displayed at 1st Outcome Restart

2EF.001.01 Outcome with UI Request and Field Off (2)

Test No: - Revision 1 – Number of sub cases: 0

Reference Book B – version 2.3 – Requirement 3.5.1.1, 3.5.1.2, 3.5.1.5 BOOK A/B:

Terminal [Value qualifier] supported Configuration:

Conditions: • Entry Point transaction is performed (Outcome ‘Approved (with Balance)’ Value Qualifier “Balance” with UI Request “Approved”) and Amount = 2 Action: NA

Procedure: Entry Point transaction is performed for [Termsetting2] with [Ltsetting1.45].

Pass Criteria: • The UI Request on Outcome: MSG ID ‘03’ (“Approved”) is correctly displayed at end of the transaction • the field shall be turned off at end of the transaction

2EF.002.00 Outcome Try Again

Test No: - Revision 1 – Number of sub cases: 0

Objective: To ensure that If the Outcome is Try Again, then Entry Point shall return to Start B (Protocol Activation, section 5.2.1) To ensure that if an Outcome has a UI Request on Outcome Present equal to ‘Yes’, then Entry Point shall send the associated User Interface Request. To ensure that if an Outcome parameter Field Off Request has a value NA, then the field shall not be turned off.

Reference Book B – version 2.3 – Requirement 3.5.1.1, 3.5.1.2,3.5.1.3 BOOK A/B:

Terminal NA Configuration:

Conditions: Amount = 2 Action: NA

Procedure: Entry Point transaction is performed for [Termsetting1] with [Ltsetting1.43] (1st Final Outcome ‘Try Again, 2nd Final Outcome ‘Approved’)

Pass Criteria: • The UI Request on Outcome: MSG ID ‘21’ (“Present Card Again”) is correctly displayed • The field shall remain on between 1st Outcome and Restart • The LT shall receive in the Select PPSE after restart,

2EF.003.00 Outcome Select Next

Test No: - Revision 2.6a – Number of sub cases: 4

Objective: To ensure that if the Outcome is Select Next, then Entry Point shall remove the selected Combination associated with this ADF Name from the Candidate List and Entry Point shall return to Start C (Combination Selection Step 3 – requirement 5.3.2.6). Test is done for Start A and B.

Reference Book B – version 2.3 – Requirement 3.5.1.4 :

Terminal NA Configuration:

Conditions: • Case01: Entry Point transaction is performed with [Termsetting2] and [Ltsetting2.40] (Outcome Select Next on AID A0000000030003 before Outcome ‘Approved on AID A0000000020002) and Amount = 0 • Case02: Entry Point transaction is performed with [Termsetting3]and [Ltsetting2.40] (Outcome Select Next on AID A0000000030003 before Outcome ‘Approved on AID A0000000020002). • Case03: Entry Point transaction is performed with [Termsetting3] and [Ltsetting2.41] (Outcome Select Next on AID A0000000030003 before Outcome ‘Approved on AID A0000000030003). • Case04: Entry Point transaction is performed with [Termsetting2] and [Ltsetting2.45] (Outcome Select Next on AID A0000000030003 before Outcome ‘Approved on AID A0000000040004). Action: NA

Procedure: Entry Point transactions are performed for different Term settings and different LT settings.

Pass Criteria: • Case01: The LT shall receive the SELECT command with AID ‘A0000000020002’ (after the Select AID A0000000030003) • Case01: The LT shall receive in the second GET PROCESSING OPTIONS data field: Kernel ID = 22

2EF.003.00 Outcome Select Next

• Case02: The LT shall receive the SELECT command with AID = ‘A0000000020002’ (after the Select AID = A0000000010001 followed by Select AID = A0000000030003) • Case02: The LT shall receive in the 3rd GET PROCESSING OPTIONS data field: Kernel ID = 22 • Case03: The LT shall receive the SELECT command with AID ‘A0000000030003’ (after the Select AID A0000000030003) • Case03: The LT shall receive in the second GET PROCESSING OPTIONS data field: Kernel ID = 22 • Case04: The LT shall receive the SELECT command with AID ‘A0000000040004’ (after the Select AID A0000000030003) • Case04: The LT shall receive in the second GET PROCESSING OPTIONS data field: Kernel ID = 25

Annex A: Terminal Settings Definition

[Termsetting1]

• Kernel ID

o International kernel ID: TK1, TK2, TK3, TK4, TK5, 21, 22, 23, 24, 25, 32 associated to 11 Test Kernel instances.

o Domestic kernel ID (EMVCo format): 810978, BF0840 associated to 2 Test Kernel instances

o Domestic kernel ID (proprietary format): C11111, FF2222 associated to 2 Test Kernel instances

• The following AID (A000000010001, A000000020002, A000000030003, A000000040004, A0000001523010, A0000000031010, A0000000041010, A0000000651010, A0000000251010, B0000000010101) are combined to each above Test Kernel instances and all type of transaction supported

• All preprocessing feature activated (including same values) in all Test Kernel instances: Autorun Parameter: ‘No’

Kernel ID TK1 TK2 TK3 TK4 TK5 TK TK 21 22 23 24 25 32 8109 BF08 C111 FF22 6 7 78 40 11 22 AID

A0000000010001 x x x x x x x

A0000000020002 x x x x x x x x x

A0000000030003 x x x x x x x x x x

A0000000040004 x x x x x x x x x

A0000000031010 x x

A0000000041010 x x x x

A0000000651010 x x x x x

A0000000251010 x x x x

A0000001523010 x

A0000003330101 x

A0000003241010 x

B0000000010101 x x x x x x x x x

Table A.1: Kernel ID/AID combination for [Termsetting1]

Status Check Support flag 1

Zero Amount Allowed flag 1

Reader Contactless Transaction Limit 120

Reader Contactless Floor Limit 12

Terminal Floor Limit -

Reader CVM Required Limit 15

TTQ ‘B6208000’

Extended Selection Support flag 1

Table A.2: Entry Point data for [Termsetting1] ‘-‘ means that the data object is not present. TTQ: Mag-stripe mode supported, EMV mode supported, EMV contact chip supported, Online capable reader, Online PIN supported, Signature supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN supported, Issuer Update Processing supported.

[Termsetting2]

• Autorun Parameter: ‘No’

• Kernel ID/AID (in addition to Kernel ID 1 to 7 associated with Kernel C-1 to C-7 as declared in the ICS.

Kernel ID TK1 TK2 TK3 TK4 TK5 TK6 TK7 21 22 23 24 25 2B

AID

A0000000010001 x x x

A0000000020002 x x x

A0000000030003 x x x

A0000000040004 x x x x

A0000000031010 x x x

A0000000041010 x x x

A0000000651010 x x x

A0000000251010 x x x x

A0000001523010 x

A0000003330101 X

A0000003241010 x

Table A.3: Kernel ID/AID combination for [Termsetting2]

• Entry Point Configuration (not depending of the Transaction Type)

Combination A0000000 A000000 A00000000 A00000002 A00000000 A00000000 A00000006 A00000002 A00000002 651010/TK 0041010/ 31010/TK3 51010/TK4 41010/TK4 31010/TK1 51010/TK2 51010/TK3 51010/2B AID/kernel 1 TK2 A00000000 A00000000 A00000006 A00000000 A00000000 A00000002 A00000000 40004/2B A0000000 A000000 10001/23 51010/TK5 20002/24 10001/21 51010/TK5 40004/23 030003/21 0020002/ A00000015 22 A00000000 A00000000 A00000000 23010/TK6 31010/2B 40004/24 30003/22 A000000 A00000033 0041010/ A00000000 A00000000 A00000000 30101/TK7 2B 10001/2B 30003/25 40004/25 A00000032 A000000 41010/TK6 0020002/ 2B

Status Check - 0 1 - - 0 1 1 0 Support flag

Zero Amount 1 - 0 0 1 - 1 1 - Allowed flag

Reader 120 - 200 - - - 200 - 120 Contactless Transaction Limit

Reader 20 - - 50 20 - - 50 - Contactless Floor Limit

Terminal Floor - - 25 - - - 25 - - Limit

Reader CVM - 10 - 20 - 10 - 20 10 Required Limit

TTQ ‘840080FF’ - ‘28000F00’( ‘C4008000’ ‘84008000’ - ‘28000000’( - - (1) 2) (3) (1) 2)

Extended 1 - 0 1 1 0 - 1 0 Selection Support flag

Table A.4: Entry Point data for [Termsetting2]

‘-‘ means that the data object is not present.

(1) TTQ value ‘840080FF’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported. Byte 4 RFU Bits set to 1 (2) TTQ value ‘28000F00’: Mag-stripe mode not supported, EMV mode supported, EMV contact chip not supported, Offline-only reader, Online PIN not supported, Signature not

© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® Terminal Type Approval Book A & B Test Cases v2.6a Page 273 supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing not supported, Byte 3 RFU Bits set to 1,

(3)TTQ value ‘C4C08000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram required, CVM required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported, Byte 1 RFU Bits set to 1.

[Termsetting3]

• Autorun Parameter: ‘Yes’ (if Autorun Option is supported only)

o Autorun parameters according to ICS: § Transaction Type

§ Amount Authorized

• Kernel ID/AID (in addition to kernel ID 1 to 7 associated with Kernel C-1 to C-7 as declared in the ICS)

Kernel ID TK1 TK2 TK3 TK4 TK5 TK6 TK7 21 22 23 24 25 2B

AID

A0000000010001 x x x

A0000000020002 x x x

A0000000030003 x x x

A0000000040004 x x x x

A0000000031010 x x x

A0000000041010 x x x

A0000000651010 x x x

A0000000251010 x x x x

A0000001532010 X X

A0000003330101 x X

Table A.5: Kernel ID/AID combination for [Termsetting3]

• Entry Point Configuration (not depending of the Transaction Type)

Combination A0000000 A000000 A00000000 A00000002 A00000000 A00000000 A00000006 A00000002 A00000002 651010/TK 0041010/ 31010/TK3 51010/TK4 41010/TK4 31010/TK1 51010/TK2 51010/TK3 51010/2B AID/kernel 1 TK2 A00000000 A00000006 A00000000 A00000000 A00000002 A00000000 A00000000 A0000000 A000000 10001/23 51010/TK5 20002/24 10001/21 51010/TK5 40004/23 40004/2B 030003/21 0020002/ 22 A00000000 A00000000 A00000000 A00000015 31010/2B 40004/24 30003/22 32010/TK6 A000000 0041010/ A00000000 A00000000 A00000000 A00000033 2BA0000 10001/2B 30003/25 40004/25 30101/TK7 0000200 02/2B

Status Check - 0 1 - - 0 1 1 0 Support flag

Zero Amount 1 - 0 0 1 - 1 1 - Allowed flag

Reader 120 - 200 - - - 200 - - Contactless Transaction Limit

Reader 20 - - 50 20 - - 50 100 Contactless Floor Limit

Terminal Floor - - 25 - - - 25 - - Limit

Reader CVM - 10 - 20 - 10 - 20 10 Required Limit

TTQ ‘84008000’ - ‘28000000’( ‘84C08000’ ‘84008000’ - ‘28000000’( - - (1) 2) (3) (1) 2)

Extended 1 - 0 1 1 0 - 1 0 Selection Support flag

Table A.6: Entry Point data for [Termsetting3]

‘-‘ means that the data object is not present.

(2) TTQ value ‘28000000’: Mag-stripe mode not supported, EMV mode supported, EMV contact chip not supported, Offline-only reader, Online PIN not supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing not supported

(3)TTQ value ‘84C08000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram required, CVM required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported

Note that Pre-Processing is not activated, but the Pre-Processing parameters are required to verify that their presence has no impact on the entry point 276template276.

[Termsetting4]

• Autorun Parameter: ‘No’

• 5 kernels with different AID configurations depending of transaction type supported: (in addition to kernel ID 1 to 7 associated with Kernel C-1 to C-7 as declared in the ICS)

o Purchase

o Purchase with Cashback

o Cash Advance

o Refund

Kernel ID 21 22 23 24 25

Type of Transaction

Purchase A0000000030003 A0000000020002 A0000000010001 A0000000040004 A0000000030003

Purchase A0000000030003 with Cashback

Cash A0000000010001 A0000000030003 Advance

Refund A0000000030003 A0000000020002 A0000000040004

Table A.7: Combinations for [Termsetting4]

• Entry Point Configuration

Combination A0000000 A000000 A000000 A000000 A000000 A00000000 A000000 A000000 A000000 030003/21 0020002/ 0010001/ 0040004/ 0020002/ 10001/23 0030003/ 0040004/ 0030003/ AID/kernel/ type 22 23 24 22 21 24 21 of transaction Purchase Refund A00000000 Purchas Refund Refund A000000 Purchas Purchas 30003/25 e with 0030003/ e e Cashbac 25 Cash k Advance Purchas e

Status Check - 0 1 0 - 0 1 1 - Support flag

Zero Amount 1 - 0 0 1 - 1 1 - Allowed flag

Reader - - 200 120 120 - 200 - - Contactless Transaction Limit

Reader 20 - - - 20 - - 50 50 Contactless Floor Limit

Terminal Floor - - 25 - - - 25 - - Limit

Reader CVM - 10 - 20 - 10 - 20 - Required Limit

TTQ ‘84008000’ - ‘2800000 ‘84C0800 ‘8400800 - ‘2800000 - ‘8400800 (1) 0’(2) 0’ (3) 0’ (1) 0’(2) 0’ (1)

Extended 1 - 0 1 1 0 - 1 1 Selection Support flag

Table A.8: Entry Point data for [Termsetting4]

‘-‘ means that the data object is not present. (1) TTQ value ‘84008000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported (2) TTQ value ‘28000000’: Mag-stripe mode not supported, EMV mode supported, EMV contact chip not supported, Offline-only reader, Online PIN not supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing not supported

(3) TTQ value ‘84C08000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not

© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® Terminal Type Approval Book A & B Test Cases v2.6a Page 279 supported, Online cryptogram required, CVM required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported

[Termsetting5.x]

• Autorun Parameter: ‘Yes’ (if Autorun Option is supported only)

o Autorun parameters according to ICS: § Transaction Type:

• Purchase: [Termsetting5.1]

• Purchase with Cashback: [Termsetting5.2]

• Cash Advance: [Termsetting5.3]

• Refund: [Termsetting5.4] § Amount Authorized

• 5 kernels with different AID configurations depending of transaction type supported: (in addition to kernel ID 1 to 7 associated with Kernel C-1 to C-7 as declared in the ICS)

Kernel ID 21 22 23 24 25

Type of Transaction

Purchase A0000000030003 A0000000020002 A0000000010001 A0000000040004 A0000000030003

Purchase with A0000000030003 Cashback

Cash Advance A0000000010001 A0000000030003

Refund A0000000030003 A0000000020002 A0000000040004

Table A.9: Combinations for [Termsetting5.x]

• Entry Point Configuration

Status Check - 0 1 0 - 0 1 1 - Support flag

Zero Amount 1 - 0 0 1 - 1 1 - Allowed flag

Reader - - 200 120 120 - 200 - - Contactless Transaction Limit

Reader 20 - - - 20 - - 50 50 Contactless Floor Limit

Terminal Floor - - 25 - - - 25 - - Limit

Reader CVM - 10 - 20 - 10 - 20 - Required Limit

TTQ ‘84008000’ - ‘2800000 ‘84C0800 ‘8400800 - ‘2800000 - ‘8400800 (1) 0’(2) 0’ (3) 0’ (1) 0’(2) 0’ (1)

Extended 1 - 0 1 1 0 - 1 1 Selection Support flag

Table A.10: Entry Point data for [Termsetting5.x] ‘-‘ means that the data object is not present.

(1) TTQ value ‘84008000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported (2) TTQ value ‘28000000’: Mag-stripe mode not supported, EMV mode supported, EMV contact chip not supported, Offline-only reader, Online PIN not supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing not supported

(3) TTQ value ‘84C08000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram required, CVM required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported

Note that Pre-Processing is not activated, but the Pre-Processing parameters are required to verify that their presence has no impact on the entry point 282template282.

[Termsetting6]

• Autorun Parameter: ‘No’

• Kernel ID/AID

Kernel ID TK2 TK3 TK4 TK5 2B

AID

A0000000031010 x x

A0000000041010 x x x

A0000000651010 x x

A0000000251010 x x x x

Table A.11: Kernel ID/AID combination for [Termsetting6]

• Entry Point Configuration (not depending of the Transaction Type)

Combination A000000 A00000000 A00000002 A00000000 A00000006 A00000002 A00000002 0041010/ 31010/TK3 51010/TK4 41010/TK4 51010/TK2 51010/TK3 51010/2B AID/kernel TK2 A00000006 A00000002 A00000000 51010/TK5 51010/TK5 A000000 31010/2B 0041010/ 2B

Status Check 0 1 - - 1 1 0 Support flag

Zero Amount - 0 0 1 1 1 - Allowed flag

Reader - 200 - 120 200 - - Contactless Transaction Limit

Reader - - 50 20 - 50 100 Contactless Floor Limit

Terminal Floor - 25 - - 25 - - Limit

Reader CVM 10 - 20 - - 20 10 Required Limit

TTQ - ‘28000000’( ‘84C08000’ ‘84008000’ ‘28000000’( - - 2) (3) (1) 2)

Extended - 0 1 1 - 1 0 Selection Support flag

Table A.12: Entry Point data for [Termsetting6]

‘-‘ means that the data object is not present.

(1) TTQ value ‘84C08000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported (2) TTQ value ‘28000000’: Mag-stripe mode not supported, EMV mode supported, EMV contact chip not supported, Offline-only reader, Online PIN not supported, Signature not supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN not supported, Issuer Update Processing not supported (3) TTQ value ‘84C08000’: Mag-stripe mode supported, EMV mode not supported, EMV contact chip not supported, Online capable reader, Online PIN supported, Signature not

© 2017 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. EMV® Terminal Type Approval Book A & B Test Cases v2.6a Page 285 supported, Online cryptogram required, CVM required, (Contact Chip) Offline PIN not supported, Issuer Update Processing supported

[Termsetting7]

• Autorun Parameter: ‘Yes’ (if Autorun Option is supported only)

o Autorun parameters according to ICS: § Transaction Type

§ Amount Authorized

• Kernel ID/AID

Kernel ID TK2 TK3 TK4 TK5 2B

AID

A0000000031010 x x

A0000000041010 x x x

A0000000651010 x x

A0000000251010 x x x x

Table A.13: Kernel ID/AID combination for [Termsetting7] Note that Pre-Processing is not activated, so the Pre-Processing parameters are not required.

[Termsetting8]

• Kernel ID

o International kernel ID: 21, 22, 23, 24, 25, 32 associated to 6 Test Kernel instances.

o Domestic kernel ID (EMVCo format): 810978, BF0840 associated to 2 Test Kernel instances

o Domestic kernel ID (proprietary format): 811111, BF2222 associated to 2 Test Kernel instances.

• The following AID (A0000000010001, A0000000020002, A0000000030003, A0000000040004, B0000000010101) are combined for each above Test Kernel instance and all type of transaction supported

• All preprocessing feature activated (including same values) not depending of the Transaction Type: Autorun Parameter: ‘No’

Kernel ID 21 22 23 24 25 32 810978 BF0840 811111 BF2222

AID

A0000000010001 x x x x x x x

A0000000020002 x x x x x x x x x

A0000000030003 x x x x x x x x x x

A0000000040004 x x x x x x x x X

B0000000010101 x x x x x x x x x

Table A.14: Kernel ID/AID combination for [Termsetting8]

Status Check Support flag 1

Zero Amount Allowed flag 1

Reader Contactless Transaction 120 Limit

Reader Contactless Floor Limit 12

Terminal Floor Limit -

Reader CVM Required Limit 15

TTQ ‘F72A8A55’ (several RFU bits set)

Extended Selection Support flag 1

Table A.15: Entry Point data for [Termsetting8]

‘-‘ means that the data object is not present.

TTQ: Mag-stripe mode supported, EMV mode supported, EMV contact chip supported, Online capable reader, Online PIN supported, Signature supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN supported, Issuer Update Processing supported

[Termsetting10]

• Kernel ID

o International kernel ID: 01, 02, 03, 04, 04, 05, 06, 07, associated to C-1 to C-7 Kernel instances (only when Kernel C-1 to C-7 are supported).

• The following AID (A0000000031010, A0000000041010, A0000000651010, A000000025010403, A0000001523010, A0000003330101, A0000003241010, B0000000010101) are combined to each above Kernel instances and all type of transaction supported

• All preprocessing feature activated in all Kernel instances: Autorun Parameter : ‘No’

Kernel ID 01 02 03 04 05 06 07 AID

A0000000031010 X

A0000000041010 x

A0000000651010 x x

A0000000250104 x 03

A0000001523010 X

A0000003330101 X

A0000003241010 x

B0000000010101 x x x x x x x

Table A.16: Kernel ID/AID combination for [Termsetting10]

Status Check Support flag 1

Zero Amount Allowed flag 1

Reader Contactless Transaction Limit 120

Reader Contactless Floor Limit 12

Terminal Floor Limit -

Reader CVM Required Limit 15

TTQ ‘’According to Kernel C-3’

Extended Selection Support flag 1

Table A.17: Entry Point data for [Termsetting10] (except for Kernel C-1 to C-7)

‘-‘ means that the data object is not present. For the test kernels instance only: TTQ: Mag-stripe mode supported, EMV mode supported, EMV contact chip supported, Online capable reader, Online PIN supported, Signature supported, Online cryptogram not required, CVM not required, (Contact Chip) Offline PIN supported, Issuer Update Processing supported.

Data set when Kernel C-1 is present Contact related data set (present if terminal support contact transaction):

# Parameter Value

1 AID A0000000651010 2 Application Version Number 0x0120/0x0200 3 CA Public Key Index 4 CA Public Key Modulus key index: 11 5 CA Public Key Exponent Maximum Target Percentage to be used 6 99 for Biased Random Selection Threshold Value for Biased Random 7 1 Selection 8 Terminal Action Code-Denial 00 10 00 00 00 9 Terminal Action Code-Online F8 60 AC F8 00 10 Terminal Action Code-Default F8 60 AC A8 00 11 Terminal Floor Limit 0

Contactless related data set (present when kernel C-1 is present):

# Parameter Value 1 Terminal Type 00 Terminal/Reader Contactless 2 3001 Transaction Limit 3 Terminal/Reader CVM Required Limit 3000 Terminal/Reader Contactless Floor 4 3000 Limit 5 CVM Requirements 999999999999 6 VLP Terminal Support Indicator 01 10 JCB CA Public Keys 11 A2583AA40746E3A63C22478F576D1EFC5FB046135A6F C 739E82B55035F71B09BEB566EDB9968DD649B94B6DE D C033899884E908C27BE1CD291E5436F762553297763D A A3B890D778C0F01E3344CECDFB3BA70D7E055B8C760 11 CAPK D 0179A403D6B55F2B3B083912B183ADB7927441BED339 5 A199EEFE0DEBD1F5FC3264033DA856F4A8B93916885 B D42F9C1F456AAB8CFA83AC574833EB5E87BB9D4C006 A 4B5346BD9E17E139AB6552D9C58BC041195336485 12 CAPK Exponent 03 13 Application Identifier A000000065 14 Scheme Identifier (Scheme ID) 61/62

15 CVM Capability No CVM

Data set when Kernel C-2 is present

o Detailed values for Kernel C2 AID A0 00 00 00 04 10 10 are provided in “Kernel C-2 Testing Environment (Terminal Products), provided by MasterCard.

o The Limits (Reader Contactless Transaction Limit, Reader Contactless Floor Limit, Terminal Floor Limit, Reader CVM Required Limit) for this kernel shall not be present in the terminal data set.

Data set when Kernel C-3 is present

Parameter Value Terminal Capabilities N/A

Parameter Value Additional Terminal Capabilities N/A Terminal Type N/A Terminal Action Code – Online N/A Terminal Action Code – Default N/A Terminal Action Code – Denial N/A

Terminal Transaction Qualifiers ’E0 00 00 00’ if EMV & Mag-stripe mode supported ’80 00 00 00’ if Mag-stripe only mode supported

’20 00 00 00’ if EMV only mode supported Contactless Floor Limit Maximum allowed value CVM Required Limit Maximum allowed value Contactless Transaction Limit Maximum allowed value CA PK Index ‘52’ CA PK AFF740F8DBE763F333A1013A43722055C8E22F41779 E219B0E1C409D60AFD45C8789C57EECD71EA4A269 A675916CC1C5E1A05A35BD745A79F94555CE29612 AC9338769665B87C3CA8E1AC4957F9F61FA7BFFE4 E17631E937837CABF43DD6183D6360A228A3EBC73 A1D1CDC72BF09953C81203AB7E492148E4CB774CD DFAAC3544D0DD4F8C8A0E9C70B877EA79F2C22E4 CE52C69F3EF376F61B0F43A540FE96C63F586310C3B 6E39C78C4D647CADB5933 CA PK Exponent ‘03’

Data set when Kernel C-4 is present

Parameter Value Application Selection Indicator ON Kernel 4 Reader Capabilities ‘80’ Terminal Capabilities ‘E0 08 08’ Additional Terminal Capabilities ’60 00 F0 F0 01’ Terminal Type ‘25 Terminal Action Code – Online ‘C4 00 00 00 00’ Terminal Action Code – Default ‘C4 00 00 00 00’ Terminal Action Code – Denial ’00 00 00 00 00’

Contactless Floor Limit Maximum allowed value

Parameter Value CVM Required Limit Maximum allowed value Contactless Transaction Limit Maximum allowed value

Data set when Kernel C-5 is present

Contactless related data set:

# Parameter Value 3 Terminal Type NA 6 Terminal Action Code – Online F8 60 AC F8 00 7 Terminal Action Code – Default F8 60 AC A8 00 8 Terminal Action Code - Denial 00 10 00 00 00 9 Contactless Floor Limit 1000 10 CVM Required Limit 1000 11 Contactless Transaction Limit 1000 12 CAPK Index 11 A2583AA40746E3A63C22478F576 D1EFC5FB046135A6FC739E82B550 35F71B09BEB566EDB9968DD649B 94B6DEDC033899884E908C27BE1 CD291E5436F762553297763DAA3 B890D778C0F01E3344CECDFB3BA 13 CAPK 70D7E055B8C760D0179A403D6B5 5F2B3B083912B183ADB7927441BE D3395A199EEFE0DEBD1F5FC3264 033DA856F4A8B93916885BD42F9 C1F456AAB8CFA83AC574833EB5E 87BB9D4C006A4B5346BD9E17E13 9AB6552D9C58BC041195336485 14 CAPK Exponent 03

Data set when Kernel C-6 is present

Parameter Value D-PAS AID A0 00 00 01 52 30 10 Legacy AID A0 00 00 03 24 30 10

Terminal Application Version Number 0100 Terminal Action Code – Online 00 00 00 00 00 Terminal Action Code – Default 00 00 00 00 00 Terminal Action Code - Denial 00 00 00 00 00 Contactless Transaction Limit 300.00 Contactless Floor Limit 150.00 Contactless CVM Limit 20.00 Terminal Floor Limit (9F1B) 150.00 Status Check Support Flag 01 Zero Amount Allowed Flag 01 Exception List Contains PAN = 6011111111111125 Terminal Capabilities E0 E8 08 B1b3 = 1 (online PIN) B1b2 = 1 (Signature) TTQ B3b7 = 1 (consumer CVM) other bits are set to 1/0 based on reader capability CAPK Index 01 A1 F5 E1 C9 BD 86 50 BD 43 AB 6E E5 6B 89 1E F7 45 9C 0A 24 FA 84 F9 12 7D 1A 6C 79 D4 93 0F 6D B1 85 2E 25 10 F1 8B 61 CD 35 4D B8 3A 35 6B D1 90 B8 8A B8 DF 04 28 4D 02 A4 20 4A 7B 6C B7 C5 55 19 77 A9 B3 CAPK 63 79 CA 3D E1 A0 8E 69 F3 01 C9 5C C1 C2 05 06 95 92 75 F4 17 23 DD 5D 29 25 29 05 79 E5 A9 5B 0D F6 32 3F C8 E9 27 3D 6F 84 91 98 C4 99 62 09 16 6D 9B FC 97 3C 36 1C C8 26 E1 CAPK Exponent 03

[Termsetting13]

• Kernel ID

o International kernel ID: 21, 22, 23, 24, 25, 32 associated to 6 Test Kernel instances.

o Domestic kernel ID (EMVCo format): 810978, BF0840 associated to 2 Test Kernel instances

o Domestic kernel ID (proprietary format): C11111, FF2222 associated to 2 Test Kernel instances

• The following AID (A0000000010001, A0000000020002, A0000000030003, A0000000040004, B0000000010101, B0000000010102, B0000000010103, B0000000010104, B0000000010105) are combined to one or two Test Kernel intances and all type of transaction supported

• No preprocessing feature activated in all Test Kernel instances: Autorun Parameter: ‘Yes’ (if Autorun Option is supported only)

Kernel ID 21 22 23 24 25 32 810978 BF0840 C11111 FF2222

AID

A0000000010001 x

A0000000020002 x

A0000000030003 x x

A0000000040004 x

B0000000010101 x

B0000000010102 x

B0000000010103 x

B0000000010104 x

B0000000010105 x

Table A.18: Kernel ID/AID combination for [Termsetting13]

Annex B: PDOL Definition

The PDOL may include several Entry Point data from the list below:

Data Object Tag Length Comment

Test flags D1 2 Includes Pre- Processing flags and Restart flag

TTQ 9F66 4

Kernel ID D7 var Kernel ID is of variable size and may be one, three, or more bytes (until 8) in length

Amount Authorized 9F02 6

Amount Other 9F03 6

Transaction Type 9C 1

UN 9F37 4

Start Point D2 1 Entry Point Started (‘A’, ‘B’, ‘C’ or ‘D’)

FCI 6F var

Select Response D3 2 Status Word

Issuer 91 Var Authentication Data

Issuer Script 71 71 var

Issuer Script 72 72 var

Table B.1: PDOL data element

Annex C: LT (Card) configurations Definition

[LT setting1.1] to [Ltsetting8.x] are using the LT test kernel according to section 8.1, and [Ltsetting9.x], are using LT test kernel according to section 8.2.

[Ltsetting1.x]: single AID

[Ltsetting1.1] characteristics (card type A):

• Single AID APP1 (with associated Kernel ID = 23)

• PDOL with Pre-Processing indicator, TTQ, Amount, Amount Other, Transaction Type, Unpredictable Number, kernel ID

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”), Field Off Request = NA o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘01’ o PDOL = ‘D1029F66049F02069F03069C019F3704D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’

o Value Qualifier value = ‘00’ o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.1: [Ltsetting1.1]

Data Value

PPSE 6F2D840E325041592E5359532E4444463031A51BBF0C1861164F0 FCI 7A00000000100015004415050318701019F2A0103

AID FCI 6F298407A0000000010001A51E500415050318701019F3812D1029 F66049F02069F03069C019F3704D708

GPO 771DD40A03000000000000000000D50F030500000000000000000 response 000000000

Table C.2: LT responses for [Ltsetting1.1]

[Ltsetting1.2] characteristics (card type B):

• Single AID APP2 (with associated Kernel ID = 22)

• PDOL with Pre-Processing indicator, TTQ, Amount, Amount Other, Transaction Type, Restart flag, Unpredictable Number, Kernel ID

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”)

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’

o PDOL = ‘D1029F66049F02069F03069C019F3704D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.3: [Ltsetting1.2]

[Ltsetting1.3] characteristics:

• Single AID APP3 (with associated Kernel ID = 21)

• PDOL with Pre-Processing indicator, TTQ, Amount, Amount Other, Transaction Type, Restart flag, Unpredictable Number, kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’

o PDOL = ‘D1029F66049F02069F03069C019F3704D708’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.4: [Ltsetting1.3]

[Ltsetting1.4] characteristics:

• Single AID APP4 (with associated Kernel ID = 24)

• PDOL with Pre-Processing indicator, TTQ, Amount, Amount Other, Transaction Type, Restart flag, Unpredictable Number, kernel ID

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”)

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘01’

o PDOL = ‘D1029F66049F02069F03069C019F3704D708’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.5: [Ltsetting1.4]

[Ltsetting1.5] characteristics:

• Single AID APP4 (with associated Kernel ID = 24)

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”) o The Final Outcome ‘Approved’ UI Request on Outcome = Yes, Receipt = Yes, CVM = No CVM

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘01’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘04’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘01’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’

o Value Qualifier value = ‘00’

o Value = ‘000000000000’ o Currency Code = ‘0000’

Table C.6: [Ltsetting1.5]

[Ltsetting1.6] characteristics:

• Single AID APP2 (with associated Kernel ID = 22)

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”) o The Final Outcome ‘Approved’ UI Request on Outcome = Yes, Receipt = Yes, CVM = Obtain Signature

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘03’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘01’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’

o Value Qualifier value = ‘00’

o Value = ‘000000000000’ o Currency Code = ‘0000’

Table C.7: [Ltsetting1.6]

[Ltsetting1.7] characteristics:

• Single AID APP3 (with associated Kernel ID= 21)

• PDOL with Pre-Processing indicator, start Point

• When Restart=0, GPO Response indicates

o the Final Outcome ‘online request’

o start C o Online Response Data: Any

o CVM: NA

o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0C’ o Online Response Data = ‘02’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘03’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘01’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.8: [Ltsetting1.7]

[Ltsetting1.8] characteristics:

• Single AID APP3 (with associated Kernel ID= 21)

• PDOL with Pre-Processing indicator, start Point

• When Restart=0, GPO Response indicates

o the Final Outcome ‘online request’

o start C o Online Response Data: Any (Issuer Data (91) and Issuer script (71) received)

o CVM: NA

o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0C’ o Online Response Data = ‘02’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO o Tag 71 = ‘1112131415161718191A1B1C1D1E1F20’ response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘03’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘01’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.9: [Ltsetting1.8]

[Ltsetting1.9] characteristics:

• Single AID APP3 (with associated Kernel ID= 21)

• When Restart=0, GPO Response indicates

o the Final Outcome ‘online request’ o start D

o Online Response Data: any

o CVM: NA o UI Request on Outcome Present: No

o UI Request on Restart Present: Yes

o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 0 • UI Request on Restart: MSG ID 16 ‘PROCESSING’

• When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0D’ o Online Response Data = ‘02’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’16’ on Restart 1 GPO o Status value = ‘04’ response o Hold Time value = ‘0032’ o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’

o Value = ‘000000000000’ o Currency Code = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘03’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘01’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.10: [Ltsetting1.9]

[Ltsetting1.11] characteristics:

• Single AID APP2 (with associated Kernel ID=22)

• PDOL with Pre-Processing indicator, start Point, Issuer Script 71

• When Restart=0, GPO Response indicates

o the Final Outcome ‘online request’

o start B o Online Response Data: EMV data (Issuer Script 71)

o CVM:NA

o UI Request on Outcome Present: No o UI Request on Restart Present: Yes o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 10s • UI Request on Restart: MSG ID 21 ‘PRESENT CARD AGAIN’

• When Restart=1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’

o PDOL = ‘D102D2017110’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0064’

Online o Tag 71 = ‘1112131415161718191A1B1C1D1E1F20’ Response 1 GPO response

UI Request o Message ID value = ’21’ on Restart 1 GPO o Status value = ‘03’ response o Hold Time value = ‘0032’ o Language Preference value = ‘0000’

o Value Qualifier value = ‘00’ o Value = ‘000000000000’ o Currency Code = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.12: [Ltsetting1.11]

[Ltsetting1.12] characteristics:

• Single AID APP3 (with associated Kernel ID=21)

• When Restart=0, GPO Response indicates

o the Final Outcome ‘online request’ o start C

o Online Response Data: any

o CVM: NA o UI Request on Outcome Present: No

o UI Request on Restart Present: Yes

o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 0 • UI Request on Restart: MSG ID 21 ‘PRESENT CARD AGAIN’

• When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0C’ o Online Response Data = ‘02’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’21’ on Restart 1 GPO o Status value = ‘03’ response o Hold Time value = ‘0032’ o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’

o Value = ‘000000000000’ o Currency Code = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘03’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘01’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.13: [Ltsetting1.12]

[Ltsetting1.13] characteristics:

• Single AID APP4 (with associated Kernel ID = 24)

• PDOL with Pre-Processing indicator, restart, start, Issuer Authentication Data, Issuer script data

• When Restart = 0, GPO Response indicates

o the Final Outcome ‘online request’

o start D

o Online Response Data: EMV data

o CVM:NA

o UI Request on Outcome Present: No

o UI Request on Restart Present: Yes o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 10s • UI Request on Restart: MSG ID 16 ‘PROCESSING’

• When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

o CVM: obtain signature

o Receipt: yes

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘01’

o PDOL = ‘D102D20191107110’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0D’ o Online Response Data = ‘01’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0064’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO o Tag 71 = ‘1112131415161718191A1B1C1D1E1F20’ response

UI Request o Message ID value = ’16’ on Restart 1 GPO o Status value = ‘04’ response o Hold Time value = ‘0032’ o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’ o Value = ‘000000000000’ o Currency Code = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘03’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘01’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.14: [Ltsetting1.13]

[Ltsetting1.14] characteristics:

• Single AID APP3 (with associated Kernel ID = 21)

• When Restart = 0, GPO Response indicates

o the Final Outcome ‘online request’ o start D

o Online Response Data: EMV Data

o CVM: NA o UI Request on Outcome Present: No

o UI Request on Restart Present: No

o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’, Receipt = Yes, CVM = No CVM

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0D’

o Online Response Data = ‘01’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0064’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO response

UI Request o Message ID value = ’16’ on Restart 1 GPO o Status value = ‘04’ response o Hold Time value = ‘0032’ o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’

o Value = ‘000000000000’ o Currency Code = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘04’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘01’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.15: [Ltsetting1.14]

[Ltsetting1.18] characteristics:

• Single AID APP2 (with associated Kernel ID= 22)

• When Restart=0, GPO Response indicates

o the Final Outcome ‘online request’ o start B

o Online Response Data: EMV data (but no EMV data present)

o CVM:NA o UI Request on Outcome Present: No

o UI Request on Restart Present: Yes

o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 10s

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0064’

Table C.19: [Ltsetting1.18]

[Ltsetting1.19] characteristics:

• Single AID APP2 (with associated Kernel ID= 22)

• PDOL with Pre-Processing indicator, start Point

• When Restart=0, GPO Response indicates

o the Final Outcome ‘online request’

o start B o Online Response Data: EMV data (Issuer data 91)

o CVM:NA

o UI Request on Outcome Present: No o UI Request on Restart Present: Yes o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 10s • UI Request on Restart: MSG ID 21 ‘PRESENT CARD AGAIN’

• When Restart=1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’

o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0064’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO response

UI Request o Message ID value = ’21’ on Restart 1 GPO o Status value = ‘03’ response o Hold Time value = ‘0032’ o Language Preference value = ‘0000’

o Value Qualifier value = ‘00’ o Value = ‘000000000000’ o Currency Code = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.20: [Ltsetting1.19]

[Ltsetting1.21] characteristics:

• Single AID APP2 (with associated Kernel ID = 22)

• PDOL with Pre-Processing indicator, Start Point,

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’

o start B o Online Response Data: any (no issuer Data received)

o CVM: NA

o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22

o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’ o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘02’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.22: [Ltsetting1.21]

[Ltsetting1.22] characteristics:

• Single AID APP3 (with associated Kernel ID = 21)

• PDOL with Pre-Processing indicator, TTQ, restart, start, Issuer script data(72)

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’

o start C o Online Response Data: EMV data (Issuer script (72))

o CVM: NA

o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: NA • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘D102D2017210’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0C’ o Online Response Data = ‘01’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Online o Tag 72 = ‘2122232425262728292A2B2C2D2E2F30’ Response 1 GPO response

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.23: [Ltsetting1.22]

[Ltsetting1.23] characteristics:

• Single AID APP4 (with associated Kernel ID = 24)

• PDOL with Pre-Processing indicator, Start Point

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’

o start D o Online Response Data: any (No Issuer Data received)

o CVM: NA

o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24

o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘01’ o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0D’ o Online Response Data = ‘02’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.24: [Ltsetting1.23]

[Ltsetting1.24] characteristics:

• Single AID APP3(with associated Kernel ID= 21)

• When Restart=0, GPO Response indicates

o the Final Outcome ‘online request’ o start D

o Online Response Data: EMV data (but no EMV data present)

o CVM:NA o UI Request on Outcome Present: No

o UI Request on Restart Present: No

o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 10s

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0D’ o Online Response Data = ‘01’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0064’

Table C.25: [Ltsetting1.24]

[Ltsetting1.25] characteristics:

• Single AID APP2 (with associated Kernel ID = 22)

• PDOL with Pre-Processing indicator, Start Point,

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’

o start B o Online Response Data: any ( issuer script received (71))

o CVM: NA

o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22

o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’ o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘02’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Online Response 1 GPO o Tag 71 = ‘1112131415161718191A1B1C1D1E1F20’ response

UI Request o Message ID value = ’21’ on Restart 1 GPO o Status value = ‘03’ response o Hold Time value = ‘0032’ o Language Preference value = ‘0000’

o Value Qualifier value = ‘00’ o Value = ‘000000000000’ o Currency Code = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.26: [Ltsetting1.25]

[Ltsetting1.26] characteristics:

• Single AID APP2 (with associated Kernel ID = 22)

• PDOL with Pre-Processing indicator, Start Point,

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’

o start B o Online Response Data: any ( issuer script received (91))

o CVM: NA

o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22

o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’ o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘02’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.27: [Ltsetting1.26]

[Ltsetting1.27] characteristics:

• Single AID APP3 (with associated Kernel ID = 21)

• PDOL with Pre-Processing indicator, restart, start, Issuer Authentication Data, Issuer script data

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’

o start C

o Online Response Data: EMV data (Issuer Auth Data (91) and Issuer script (72))

o CVM: NA

o UI Request on Outcome Present: No

o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: NA • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’

o API = ‘01’ o PDOL = ‘D102D20191107210’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0C’ o Online Response Data = ‘01’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO o Tag 72 = ‘2122232425262728292A2B2C2D2E2F30’ response

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.28: [Ltsetting1.27]

[Ltsetting1.28] characteristics:

• Single AID APP3 (with associated Kernel ID = 21)

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’ o start C

o Online Response Data: EMV data (but no EMV data present)

o CVM: NA o UI Request on Outcome Present: No

o UI Request on Restart Present: No

o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 10

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0C’ o Online Response Data = ‘01’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0064’

Table C.29: [Ltsetting1.28]

[Ltsetting1.29 ] characteristics:

• Single AID APP4 (with associated Kernel ID = 24)

• PDOL with Pre-Processing indicator, Start Point

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’

o start D o Online Response Data: any (No Issuer Data (91) and Script (72) received)

o CVM: NA

o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24

o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘01’ o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0D’ o Online Response Data = ‘02’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO o Tag 72 = ‘2122232425262728292A2B2C2D2E2F30’ response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.30: [Ltsetting1.29]

[Ltsetting1.30] characteristics:

Select PPSE response with a template 61, AID APP3 with Extension selection present

AID Kernel ID Extended Selection Data

A0000000030003 21 010203040506070809

• PDOL with kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’ o Extended Selection = ‘010203040506070809’

AID FCI 1 o AID = ‘A0000000030003010203040506070809’ o Label = ‘APP3’

o API = ‘01’ o PDOL = ‘D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.31: [Ltsetting1.30]

[Ltsetting1.31] characteristics:

• Select PPSE response with a template 61, Domestic AID with Extension selection present

AID Kernel ID Extended Selection Data

B0000000010101 C11111 1122

• PDOL with kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘B0000000010101’ Directory Entry 1 o Label = ‘domestic’ o Kernel Identifier = ‘C11111’ o API = ‘01’

o Extended Selection = ‘1122’

AID FCI 1 o AID = ‘B00000000101011122’

o Label = ‘domestic’ o API = ‘01’ o PDOL = ‘D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.32: [Ltsetting1.31]

[Ltsetting1.32] characteristics:

• Select PPSE response with a templates 61, AID APP3 with FCI of 251 bytes

• PDOL with FCI

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’ o API = ‘01’

o PDOL = ‘6FFB’ o BF0C = ‘5F5081DA687474703A2F2F61616161612E61616161612E ….6161616161616161 …’ to obtain length of template BF0C set to 221 bytes

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.33: [Ltsetting1.32]

[Ltsetting1.33] characteristics:

• Select PPSE response with a templates 61, AID APP3

• PDOL with FCI and Select response Status Word

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘D3026Fxx’ (xx corresponding to the FCI length)

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.34: [Ltsetting1.33]

[Ltsetting1.35] characteristics:

• Single AID APP2 (with associated Kernel ID=2)

• PDOL with Pre-Processing indicator, start Point

• When Restart=0, GPO Response indicates

o the Final Outcome ‘End Application (With Restart)’

o start B o Online Response Data: NA

o CVM:NA

o UI Request on Outcome Present: Yes o UI Request on Restart Present: Yes o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: NA • UI Request on Outcome: MSG ID 21 ‘PRESENT CARD AGAIN’, Status= Not Ready, Hold Time=1.3s

• UI Request on Restart: MSG ID 21 ‘PRESENT CARD AGAIN’, Status= Ready to Read

• When Restart=1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’

o API = ‘01’ o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’07’ GPO response o Start value = ‘0B’ o Online Response Data = ‘00’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’21’ on Outcome 1 GPO o Status value = ‘01’ response o Hold Time value = ‘000D’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’ o Value = ‘000000000000’ o Currency Code = ‘0000’

UI Request o Message ID value = ’21’ on Restart 1 GPO o Status value = ‘03’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’ o Value = ‘000000000000’ o Currency Code = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.36: [Ltsetting1.35]

[Ltsetting1.40] characteristics:

• Single AID APP2 (with associated Kernel ID = 22)

•

• GPO Response indicates:

o UI request: Message Identifier: ‘07’ (“Not Authorised”)

o The Final Outcome ‘Declined’, UI Request on Outcome = Yes, Field Off Request = NA

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’

Outcome 1 o Outcome Value = ’04’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’07’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’

o Value Qualifier value = ‘00’ o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.37: [Ltsetting1.40]

[Ltsetting1.41] characteristics:

• Single AID APP3 (with associated Kernel ID = 21)

• GPO Response indicates:

o UI request: Message Identifier: ‘18’ (“Please insert or swipe card”)

o the Final Outcome ‘Try Another Interface’, UI Request on Outcome = Yes, Field Off Request = NA

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’ o API = ‘01’

Outcome 1 o Outcome Value = ’06’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’18’ on Outcome 1 GPO o Status value = ‘03’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.38: [Ltsetting1.41]

[Ltsetting1.42] characteristics:

• Single AID APP4 (with associated Kernel ID = 24)

• GPO Response indicates:

o UI request: Message Identifier: ‘1B’ (“Authorising, Please Wait”)

o The Final Outcome ‘Online Request’, UI Request on Outcome = Yes, Field Off Request = NA

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’ o Label = ‘APP4’ o API = ‘01’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’1B’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.39: [Ltsetting1.42]

[Ltsetting1.43] characteristics

• Single AID APP1 (with associated Kernel ID = 23)

• PDOL with Unpredictable Number,TTQ

• GPO Response indicates:

o 1st Final Outcome ‘Try Again’, UI Request on Outcome = Yes, UI request: Message Identifier: ‘21’ (“Present Card Again”), Field Off Request = NA,, Hold time=10s

o 2nd Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘01’ o PDOL = ‘9F37049F6604’

Outcome 1 o Outcome Value = ’02’ GPO response o Start value = ‘0B’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’21’ on Outcome o Status value = ‘03’

1 GPO o Hold Time value = ‘0064’ response o Language Preference value = ‘0000’

o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.40: [Ltsetting1.43]

[Ltsetting1.45] characteristics:

• Single AID APP2 (with associated Kernel ID = 22)

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”), value Qualifier: “Balance” Value = 000000000123, Currency Code = 0826

o The Final Outcome ‘Approved (with balance)’, UI Request on Outcome = Yes, Field Off Request = NA

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome o Status value = ‘05’

1 GPO o Hold Time value = ‘0032’ response o Language Preference value = ‘0000’

o Value Qualifier value = ‘02’

o Value = ‘000000000123’

o Currency Code = ‘0826’

Table C.41: [Ltsetting1.45]

[Ltsetting1.46] characteristics:

• Single AID APP4 (with associated Kernel ID = 24)

• GPO Response indicates:

o UI request: Message Identifier on Outcome: ‘1B’ (“Authorising, Please Wait”)

o UI request: Message Identifier on Restart: ‘21’ (“Present Card Again”) o The Final Outcome ‘Online Request’, UI Request on Outcome = Yes, Field Off Request = NA

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24

o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘01’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO response

UI Request o Message ID value = ’1B’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’ o Language Preference value = ‘0000’

o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

UI Request o Message ID value = ’21’ on Restart 1 GPO o Status value = ‘03’ response o Hold Time value = ‘0032’ o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’ o Value = ‘000000000000’ o Currency Code = ‘0000’

Table C.42: [Ltsetting1.46]

[Ltsetting1.47] characteristics:

• Single AID APP1 (with associated Kernel ID = 23)

• PDOL with TTQ

• GPO Response indicates:

o UI request: Message Identifier on Outcome: ‘1B’ (“Authorising, Please Wait”)

o UI request: Message Identifier on Restart: ‘16’ (“Processing”) o the 1st Final Outcome ‘Online Request’, UI Request on Outcome = Yes, Request on Restart = Yes, Start D, Field Off Request = NA

o 2nd Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’ o Label = ‘APP1’

o API = ‘01’ o PDOL = ‘9F6604’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0D’ o Online Response Data = ‘01’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’1B’ on Outcome o Status value = ‘05’

1 GPO o Hold Time value = ‘0032’ response o Language Preference value = ‘0000’

o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

UI Request o Message ID value = ’16’ on Restart 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’ o Value = ‘000000000000’

o Currency Code = ‘0000’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.43: [Ltsetting1.47]

[Ltsetting1.48] characteristics:

• Single AID APP4 (with associated Kernel ID = 24)

• GPO Response indicates:

o UI request: Message Identifier: ‘20’ (“See Phone for Instructions”)

o the 1st Final Outcome ‘Try Again’, Start B, UI Request on Outcome = Yes, Field Off Request = 13

o 2nd Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’ o Label = ‘APP4’

o API = ‘01’

Outcome 1 o Outcome Value = ’01’ GPO response o Start value = ‘0B’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘0082’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’20’ on Outcome o Status value = ‘06’

1 GPO o Hold Time value = ‘0032’ response o Language Preference value = ‘0000’

o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

UI Request o Message ID value = ’21’ on Restart 1 GPO o Status value = ‘03’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’ o Value = ‘000000000000’

o Currency Code = ‘0000’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.44: [Ltsetting1.48]

[Ltsetting1.49] characteristics:

• Single AID APP3 (with associated Kernel ID = 21)

• GPO Response indicates:

o UI request: Message Identifier: ‘1C’ (“Insert, Swipe or Try Another Card”)

o The Final Outcome ‘End Application, UI Request on Outcome = Yes, Field Off Request = NA

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’ o API = ‘01’

Outcome 1 o Outcome Value = ’07’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’1C’ on Outcome 1 GPO o Status value = ‘06’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.45: [Ltsetting1.49]

[Ltsetting1.50] characteristics

• PPSE containing EMV tag ‘88’ located under the FCI Proprietary Template

• Single AID APP1 (with associated Kernel ID = 23)

• PDOL with , TTQ, kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o Tag 88 = ‘01’ additional Data in template BF0C

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23

o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.46: [Ltsetting1.50]

[Ltsetting1.51] characteristics:

• PPSE containing all EMV mandatory and optional data (SFI of the Directory Elementary File, Language Preference, Issuer Code Table Index and FCI Issuer Discretionary Data), FCI Issuer Discretionary Data contains Issuer Country Code data object

• Single AID APP2 (with associated Kernel ID = 22)

• PDOL with Kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o SFI of Directory Entry :Tag 88 = ‘01’ additional Data in o Language Preference: tag 5F2D = “en” template A5 o Issuer Code Table Index: tag 9F11 =’00’

PPSE o Issuer Country Code:Tag 5F55 = “US” additional Data in template BF0C

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22

o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’ o PDOL = ‘D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.47: [Ltsetting1.51]

[Ltsetting1.52] characteristics:

• PPSE containing a Directory Discretionary Template with tag ‘73’ containing: ‘5F54’ Bank Identifier Code (BIC), ‘5F53’ International Bank Account Number (IBAN), ‘5F55’ Issuer Country Code’, ‘5F56’ Issuer Country Code, and ‘42’ Issuer Identifier Number

• Single AID APP3 (with associated Kernel ID = 21)

• PDOL with Pre-Processing indicator, TTQ,

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”)

o the Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o Bank Identifier Code (BIC): tag 5F54= ‘ABCDEFGH’ additional Data in o International Bank Account Number (IBAN): tag 5F53 = Directory ‘1234567890’ Dicretionary o Issuer Country Code tag 5F55 = “US” template 73 o Issuer Country Code:Tag 5F56 = “USA” o Issuer Identifier Number: tag 42= ‘497200’

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’

o API = ‘01’ o PDOL = ‘D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.48: [Ltsetting1.52]

[Ltsetting1.60] characteristics:

• Single AID APP3 (with associated Kernel ID = 21)

• GPO Response indicates:

o UI request on Outcome: Message Identifier: ‘03’ (“Approved”), hold time = 10s o The Final Outcome ‘Approved’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0064’ o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’

o Value = ‘000000000000’ o Currency Code = ‘0000’

Table C.49: [Ltsetting1.60]

[Ltsetting1.61] characteristics:

• Single AID APP2 (with associated Kernel ID = 22)

• GPO Response indicates:

o UI request: Message Identifier: ‘07’ (“Not Authorised”), hold time = 20s o The Final Outcome ‘Declined’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’07’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘00C8’ o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’

o Value = ‘000000000000’ o Currency Code = ‘0000’

Table C.50: [Ltsetting1.61]

[Ltsetting1.62] characteristics:

• Single AID APP1 (with associated Kernel ID = 23)

• PDOL with TTQ

• When Restart = 0, GPO Response indicates

o The First Outcome ‘online request’

o start A o Online Response Data: any

o CVM: NA

o UI Request on Outcome Present: No o UI Request on Restart Present: Yes o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 0, UI Request on Restart: MSG ID 21 ‘PRESENT CARD AGAIN’, hold time = 10s

• When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

• When Restart = 1, UI request: Message Identifier: ‘03’ (“Approved”)

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’

o API = ‘01’ o PDOL = ‘9F6604’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0A’ o Online Response Data = ‘02’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’21’ on Restart 1 GPO o Status value = ‘03’ response o Hold Time value = ‘0064’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’ o Value = ‘000000000000’ o Currency Code = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 2 GPO o Status value = ‘05’ response

o Hold Time value = ‘0032’ o Language Preference value = ‘0000’

o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.51: [Ltsetting1.62]

[Ltsetting1.70] characteristics:

• Single AID APP1 (with associated Kernel ID = 23, Language Preference = Language 1 (ICS))

• PDOL with TTQ

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”) and Language Preference = Language 1

o The Final Outcome ‘Approved’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘01’ o PDOL = ‘9F6604’ o Language Preference= Language 1 (ICS)

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome

1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = Language 1 (ICS)

o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.52: [Ltsetting1.70]

[Ltsetting1.71] characteristics:

• Single AID APP4 (with associated Kernel ID = 24, Language Preference = Language 2 (ICS) )

• 1st GPO Response indicates:

o UI request: Message Identifier: ‘20’ (“See Phone for Instructions”) and Language preference = Language 2

o The Final Outcome ‘Try Again’, UI Request on Outcome = Yes,

• 2nd GPO Response indicates:

o UI request: Message Identifier: ‘07’ (“Not Authorised”) and Language preference = Language 2

o The Final Outcome ‘Declined’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘01’ o Language Preference= Language 2 (ICS)

Outcome 1 o Outcome Value = ’02’ GPO response o Start value = ‘0B’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’20’ on Outcome 1 GPO o Status value = ‘06’ response o Hold Time value = ‘0064’

o Language Preference value = Language 2 (ICS) o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

Outcome 2 o Outcome Value = ’04’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’07’ on Outcome 2 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’ o Language Preference value = Language 2 (ICS) o Value Qualifier value = ‘00’

o Value = ‘000000000000’ o Currency Code = ‘0000’

Table C.53: [Ltsetting1.71]

[Ltsetting1.7x] characteristics:

• Single AID APP1 (with associated Kernel ID = 23, Language Preference = Language x (ICS) )

• PDOL with TTQ

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”) and Language Preference = Language x (ICS)

o The Final Outcome ‘Approved’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘01’ o PDOL = ‘9F6604’ o Language Preference= Language x (ICS)

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome

1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = Language x (ICS)

o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.54: [Ltsetting1.7x]

[Ltsetting1.7x+1] characteristics:

• Single AID APP4 (with associated Kernel ID = 24, Language Preference = Language x+1(ICS)) )

• 1st GPO Response indicates:

o UI request: Message Identifier: ‘20’ (“See Phone for Instructions”) and Language preference = Language x+1

o The Final Outcome ‘Try Again’, UI Request on Outcome = Yes,

• 2nd GPO Response indicates:

o UI request: Message Identifier: ‘07’ (“Not Authorised”)

o The Final Outcome ‘Declined’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’ o Label = ‘APP4’ o API = ‘01’

o Language Preference= Language x+1 (ICS)

Outcome 1 o Outcome Value = ’02’ GPO response o Start value = ‘0B’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’20’ on Outcome 1 GPO o Status value = ‘06’ response o Hold Time value = ‘0032’

o Language Preference value = Language x+1 (ICS) o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’07’ on Outcome 2 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’ o Language Preference value = Language x+1 (ICS) o Value Qualifier value = ‘00’

o Value = ‘000000000000’ o Currency Code = ‘0000’

Table C.55: [Ltsetting1.7 x+1]

[Ltsetting1.80] characteristics:

• Single AID APP3 (with associated Kernel ID = 21)

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”), Value Qualifier = ’Amount’, currency Code is supported by the terminal and decimal value = 1,23

o The Final Outcome ‘Approved’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’

o Value Qualifier value = ‘01’

o Value = ‘000000000123’ o Currency Code = CURR (ICS)

Table C.56: [Ltsetting1.80]

[Ltsetting1.81] characteristics:

• Single AID APP2 (with associated Kernel ID = 22)

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”), Value Qualifier = ’Balance’, currency Code is supported by the terminal and decimal value = 0,12

o The Final Outcome ‘Approved (with balance)’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’

o Value Qualifier value = ‘02’

o Value = ‘000000000012’ o Currency Code = CURR (ICS)

Table C.57: [Ltsetting1.81]

[Ltsetting1.82] characteristics:

• Single AID APP3 (with associated Kernel ID = 21)

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”), Value Qualifier = ’Amount’, currency Code is supported by the terminal and integer value = 123456

o The Final Outcome ‘Approved’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’

o Value Qualifier value = ‘01’

o Value = ‘000012345600’ o Currency Code = CURR (ICS)

Table C.58: [Ltsetting1.82]

[Ltsetting1.84] characteristics:

• Single AID APP2 extended (‘A000000002000201’) (with associated Kernel ID = 32)

• PDOL with Kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A000000002000201’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = ‘32’

o API = ‘01’

AID FCI 1 o AID = ‘A000000002000201’

o Label = ‘APP2’ o API = ‘01’ o PDOL = ‘D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.59: [Ltsetting1.84]

[Ltsetting1.85] characteristics:

• Single AID ‘B0000000010101’ (with associated Kernel ID = ’810978’)

• PDOL with Kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘B0000000010101’ Directory Entry 1 o Label = ‘Domestic’ o Kernel Identifier = ‘810978’ o API = ‘01’

AID FCI 1 o AID = ‘B0000000010101’ o Label = ‘Domestic’

o API = ‘01’ o PDOL = ‘D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.60: [Ltsetting1.85]

[Ltsetting1.86] characteristics:

• Single AID APP4 extended (‘A000000004000401’) (with associated Kernel ID = ‘BF0840’)

• PDOL with Kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A000000004000401’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = ‘BF0840’ o API = ‘01’

AID FCI 1 o AID = ‘A000000004000401’

o Label = ‘APP4’ o API = ‘01’

o PDOL = ‘D708’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.61: [Ltsetting1.86]

[Ltsetting1.87] characteristics:

• Single AID ‘B000000001010102’ (with associated Kernel ID = ’C11111’)

• PDOL with Kernel ID

• GPO Response indicates:

o the Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘B000000001010102’ Directory Entry 1 o Label = ‘Domestic’ o Kernel Identifier = ‘C11111’ o API = ‘01’

AID FCI 1 o AID = ‘B000000001010102’ o Label = ‘Domestic’

o API = ‘01’ o PDOL = ‘D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.62: [Ltsetting1.87]

[Ltsetting1.88] characteristics:

• Single AID APP3 (with associated Kernel ID = ’FF2222’)

• PDOL with Kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = ‘FF2222’ o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’

o API = ‘01’ o PDOL = ‘D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.63: [Ltsetting1.88]

[Ltsetting1.89] characteristics:

• Single AID APP4 (with associated Kernel ID = 2B)

• PDOL with Pre-Processing indicator

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”)

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = ‘2B’ o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’ o Label = ‘APP4’

o API = ‘01’ o PDOL = ‘D102’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.64: [Ltsetting1.89]

[Ltsetting1.90] characteristics:

• Single AID APP1 (with associated Kernel ID = 23)

• PDOL with Acquirer Identifier, Additional Terminal Capabilities, Application Identifier (AID) – terminal, Application Version Number, Interface Device (IFD) Serial Number, Merchant Category Code, Merchant Identifier, Merchant Name and Location, Point-of-Service (POS) Entry Mode, Terminal Capabilities, Terminal Country Code, Terminal Identification, Terminal Type, Transaction Date, Transaction Sequence Counter, Transaction Status Information, Transaction Time, Transaction Type,TTQ

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = NO,

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘01’ o PDOL = ‘9F01069F40059F06079F09029F1E089F15029F160F9F4E6 09F39019F33039F1A029F1C089F35019A039F41049B029F 21039C019F6604’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.65: [Ltsetting1.90]

[Ltsetting1.91] characteristics:

• Single AID APP3 (with associated Kernel ID = 21)

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = NO,

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘9F01069F40059F06079F09029F1E089F15029F160F9F4E6 09F39019F33039F1A029F1C089F35019A039F41049B029F 21039C01’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.66: [Ltsetting1.91]

[Ltsetting1.92] characteristics :

• Single AID APP2 (with associated Kernel ID = 24)

• PDOL with Pre-Processing indicator,

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 24 o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’ o Label = ‘APP2’ o API = ‘01’

o PDOL = ‘D102’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.67: [Ltsetting1.92]

[Ltsetting1.93] characteristics:

• Single AID ‘B0000000010101’ (with associated Kernel Kernel Identifier = ’00’)

• PDOL with Kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘B0000000010101’ Directory Entry 1 o Label = ‘Domestic’ o Kernel Identifier = ‘00’ o API = ‘01’

AID FCI 1 o AID = ‘B0000000010101’ o Label = ‘Domestic’ o API = ‘01’

o PDOL = ‘D708’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.68: [Ltsetting1.93]

[Ltsetting1.94] characteristics:

• Single AID ‘B0000000010102’ (with associated Kernel Kernel Identifier = ’00’)

• PDOL with Kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘B0000000010102’ Directory Entry 1 o Label = ‘Domestic’ o Kernel Identifier = ‘00’ o API = ‘01’

AID FCI 1 o AID = ‘B0000000010102’ o Label = ‘Domestic’ o API = ‘01’

o PDOL = ‘D708’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.69: [Ltsetting1.94]

[Ltsetting1.95] characteristics:

• Single AID ‘B0000000010103’ (with associated Kernel Kernel Identifier = ’00’)

• PDOL with Kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘B0000000010103’ Directory Entry 1 o Label = ‘Domestic’ o Kernel Identifier = ‘00’ o API = ‘01’

AID FCI 1 o AID = ‘B0000000010103’ o Label = ‘Domestic’ o API = ‘01’

o PDOL = ‘D708’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.70: [Ltsetting1.95]

[Ltsetting1.96] characteristics:

• Single AID ‘B0000000010104’ (with associated Kernel Kernel Identifier = ’00’)

• PDOL with Kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘B0000000010104’ Directory Entry 1 o Label = ‘Domestic’ o Kernel Identifier = ‘00’ o API = ‘01’

AID FCI 1 o AID = ‘B0000000010104’

o Label = ‘Domestic’ o API = ‘01’ o PDOL = ‘D708’

o Removal Timeout value = ‘0000’

Table C.71: [Ltsetting1.96]

[Ltsetting1.97] characteristics:

• Single AID APP3 (with associated Kernel ID = 25)

• PDOL with Pre-Processing indicator, TTQ, Amount, Amount Other, Transaction Type, Restart flag, Unpredictable Number, kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 25

o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘D1029F66049F02069F03069C019F3704D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’ o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.72: [Ltsetting1.97]

[Ltsetting1.98] characteristics:

• Single AID APP3 (with associated Kernel ID = 25)

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = NO,

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 25 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’

o API = ‘01’ o PDOL = ‘9F01069F40059F06079F09029F1E089F15029F160F9F4E6 09F39019F33039F1A029F1C089F35019A039F41049B029F 21039C01’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.73: [Ltsetting1.98]

[Ltsetting1.99] characteristics:

• Single AID APP4 (with associated Kernel ID = 25)

• PDOL with Pre-Processing indicator, restart, start, Issuer Authentication Data, Issuer script data

• When Restart = 0, GPO Response indicates

o the Final Outcome ‘online request’

o start D o Online Response Data: EMV data o CVM:NA o UI Request on Outcome Present: No o UI Request on Restart Present: Yes

o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No o Field Off Request: NA o Removal Timeout: 10s • UI Request on Restart: MSG ID 16 ‘PROCESSING’

• When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

o CVM: obtain signature

o Receipt: yes

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 25

o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘01’

o PDOL = ‘D102D20191107210’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0D’ o Online Response Data = ‘01’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0064’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO o Tag 72 = ‘1112131415161718191A1B1C1D1E1F20’ response

UI Request o Message ID value = ’16’ on Restart 1 GPO o Status value = ‘04’ response o Hold Time value = ‘0032’

o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’ o Value = ‘000000000000’ o Currency Code = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘03’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘01’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.74: [Ltsetting1.99]

[Ltsetting1.100] characteristics:

• Single AID APP4 (with associated Kernel ID = 25)

• PDOL with Pre-Processing indicator, TTQ, Amount, Amount Other, Transaction Type, Restart flag, Unpredictable Number, kernel ID

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”) o The Final Outcome ‘Approved’ UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 25 o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘01’

o PDOL = ‘D1029F66049F02069F03069C019F3704D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’ o Language Preference value = ‘0000’ o Value Qualifier value = ‘00’

o Value = ‘000000000000’ o Currency Code = ‘0000’

Table C.75: [Ltsetting1.100]

[Ltsetting1.101] characteristics: Select PPSE response with a template 61, AID APP4 with Extension selection present

AID Kernel ID Extended Selection Data

A0000000040004 25 010203040506070809

• PDOL with kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 25

o API = ‘01’ o Extended Selection = ‘010203040506070809’

AID FCI 1 o AID = ‘A0000000040004010203040506070809’

o Label = ‘APP4’

o API = ‘01’

o PDOL = ‘D708’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.76: [Ltsetting1.101]

[Ltsetting1.110] characteristics

• FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID L V Single AID APP1 (with associated Kernel ID = 23 Kernel ID)

• PDOL with, TTQ, kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel ID = 23 Kernel ID

o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘01’

o PDOL = ‘9F6604D708’ o FCI Issuer discretionary Data (tag BF0C) contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID L V)

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.46: [Ltsetting1.110]

[Ltsetting1.111] characteristics:

• FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3 V3) ID1 = 00 01

• Single AID APP2 (with associated Kernel ID = 22 Kernel ID)

• PDOL with Kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel ID = 22 Kernel ID o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’

o PDOL = ‘D708’ o FCI Issuer discretionary Data (tag BF0C) contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3 V3) ID1 = 00 01

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.47: [Ltsetting1.111]

[Ltsetting1.112] characteristics:

• FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2,…, IDn Ln Vn) reaching the max length possible, ID1 = 00 01

• Single AID APP3 (with associated Kernel ID = 1)

• PDOL with Pre-Processing indicator, TTQ,

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”)

o the Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel ID = 21 Kernel ID o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’

o PDOL = ‘D708’ o FCI Issuer discretionary Data (tag BF0C) contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2,…, IDn Ln Vn) reaching the max length possible, ID1 = 00 01 (where all FCI optional data are not present and Application Label Length =1 byte)

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.48: [Ltsetting1.112]

[Ltsetting1.113] characteristics

• FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with a single empty instance (ID L where L = 00 and ID = 00 01)

• PDOL with, TTQ, kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel ID = 23 Kernel ID o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘01’ o PDOL = ‘9F6604D708’

o FCI Issuer discretionary Data (tag BF0C) contains ASRPD data field: tag 9F 0A correctly formatted with a single empty instance (ID L where ID = 00 01, L = 00)

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.46: [Ltsetting1.113]

[Ltsetting1.14] characteristics:

• FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2, ID3 L3 V3 where ID1 = 00 01 and L2=00)

• Single AID APP2 (with associated Kernel ID = 22 Kernel ID)

• PDOL with Kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel ID = 22 Kernel ID o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’

o PDOL = ‘D708’ o FCI Issuer discretionary Data (tag BF0C) contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2, ID3 L3 V3 whereID1 = 00 01 and L2=00)

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.xx: [Ltsetting1.114]

[Ltsetting1.115] characteristics:

• ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID L V)

• Single AID APP3 (with associated Kernel ID = 1)

• PDOL with Pre-Processing indicator, TTQ,

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”)

o the Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel ID = 21 Kernel ID o API = ‘01’ o ASRPD: tag 9F 0A correctly formatted with a single instance (ID L V)

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’

o PDOL = ‘D708’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.xx: [Ltsetting1.115]

[Ltsetting1.116] characteristics

• ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3 V3) where ID1 = 00 01

• PDOL with, TTQ, kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel ID = 23 Kernel ID o API = ‘01’ o ASRPD data: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3 V3) where ID1 = 00 01

AID FCI 1 o AID = ‘A0000000010001’ o Label = ‘APP1’

o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.xx: [Ltsetting1.116]

[Ltsetting1.117] characteristics:

• ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID1 L V) where ID1 = 00 01

• FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID2 L V)

• Single AID APP2 (with associated Kernel ID = 22 Kernel ID)

• PDOL with Kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel ID = 22 Kernel ID o API = ‘01’

o ASRPD data: tag 9F 0A correctly formatted with a single instance (ID1 L V) where ID1 = 00 01

AID FCI 1 o AID = ‘A0000000020002’ o Label = ‘APP2’

o API = ‘01’ o PDOL = ‘D708’ o FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID2 L V)

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.xx: [Ltsetting1.117]

[Ltsetting1.118] characteristics:

• ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID1 L V1) where ID1 = 00 01

• FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID1 L V2) with same ID but different value as in directory entry above

• Single AID APP3 (with associated Kernel ID = 1)

• PDOL with Pre-Processing indicator, TTQ,

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”)

o the Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel ID = 21 Kernel ID o API = ‘01’ o ASRPD data: tag 9F 0A correctly formatted with a single instance (ID1 L V1) where ID1 = 00 01

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘D708’

o FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with a single instance (ID1 L V2) with same ID1 (00 01) but different value

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.xx: [Ltsetting1.118]

[Ltsetting1.119] characteristics

• ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3 V3) where ID1 = 00 01.

• FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID4 L4 V4, ID2 L7 V7, ID6 L6 V6) where ID2 is the same as in the drectory entry above (with different length and value)

• PDOL with, TTQ, kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel ID = 23 Kernel ID

o API = ‘01’ o ASRPD data: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3 V3) where ID1 = 00 01

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘01’

o PDOL = ‘9F6604D708’ o FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID4 L4 V4, ID2 L7 V7, ID6 L6 V6) where ID2 is the same (with different length and value)

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’

o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.xx: [Ltsetting1.119]

[Ltsetting1.120] characteristics:

• ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data field: tag 9F 0A incorrectly formatted, length = 2 (value is also 2Bytes).

• FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3 V3) where ID1 = 00 01

• Single AID APP2 (with associated Kernel ID = 22 Kernel ID)

• PDOL with Kernel ID

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel ID = 22 Kernel ID o API = ‘01’ o ASRPD data: tag 9F 0A incorrectly formatted, length = 2 (value is also 2Bytes)

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’ o PDOL = ‘D708’

o FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1 V1, ID2 L2 V2, ID3 L3 V3) where ID1 = 00 01

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.xx: [Ltsetting1.120]

[Ltsetting1.121] characteristics:

• ADF 01 Directory Entry (’61’) in the PPSE contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1, ID2 L2 V2, ID3 L3 V3) where ID1 = 00 01 and L1=00.

• FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID4 L4 V4, ID2 L2 V2, ID6 L6 V6) where ID2 is the same as in the Directionary Entry above (with same value)

• Single AID APP3 (with associated Kernel ID = 1)

• PDOL with Pre-Processing indicator, TTQ,

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”) o the Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel ID = 21 Kernel ID o API = ‘01’ o ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID1 L1, ID2 L2 V2, ID3 L3 V3) whereID1 = 00 01 and L1=00

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’

o API = ‘01’ o PDOL = ‘D708’ o FCI Issuer discretionary Data (tag BF0C) of ADF contains ASRPD data field: tag 9F 0A correctly formatted with multiple instances (ID4 L4 V4, ID2 L2 V2, ID6 L6 V6) where ID2 is the same (with same value)

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’

o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.xx: [Ltsetting1.121

[Ltsetting2.x]: multi AID (full matching) [Ltsetting2.1]characteristics:

• multi AID with full match on a single combination defined in [Termsetting2]

AID Kernel ID Match

A0000000010001 22 No

A0000000020002 21 No

A0000000030003 22 Yes

A0000000040004 21 No

• PDOL with Pre-Processing indicator, TTQ

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 22 o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 21

o API = ‘02’

PPSE o AID = ‘A0000000030003’ Directory Entry 3 o Label = ‘APP3’ o Kernel Identifier = 22 o API = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’

o Kernel Identifier = 21 o API = ‘04’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’

o API = ‘01’

o PDOL = ‘D1029F6604’

AID FCI 2 o AID = ‘A0000000020002’ o Label = ‘APP2’

o API = ‘02’ o PDOL = ‘D1029F6604’

AID FCI 3 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘03’ o PDOL = ‘D1029F6604’

AID FCI 4 o AID = ‘A0000000040004’ o Label = ‘APP4’ o API = ‘04’

o PDOL = ‘D1029F6604’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.77: [Ltsetting2.1]

[Ltsetting2.2] characteristics:

• multi AID with full match on a single combination defined in [Termsetting2]

AID Kernel ID Match

A0000000010001 21 Yes

A0000000020002 21 No

A0000000030003 23 No

A0000000040004 21 No

• PDOL with Pre-Processing indicator, TTQ

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 21

o API = ‘04’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 21 o API = ‘02’

PPSE o AID = ‘A0000000030003’ Directory Entry 3 o Label = ‘APP3’ o Kernel Identifier = 23 o API = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 21

o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘04’

o PDOL = ‘D1029F6604’

AID FCI 2 o AID = ‘A0000000020002’ o Label = ‘APP2’

o API = ‘02’ o PDOL = ‘D1029F6604’

AID FCI 3 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘03’ o PDOL = ‘D1029F6604’

AID FCI 4 o AID = ‘A0000000040004’ o Label = ‘APP4’ o API = ‘01’

o PDOL = ‘D1029F6604’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.78: [Ltsetting2.2]

[Ltsetting2.3] characteristics:

• multi AID with full match on a single combination defined in [Termsetting2]

AID Kernel ID Match

A0000000010001 22 No

A0000000020002 21 No

A0000000030003 23 No

A0000000040004 23 Yes

• PDOL with Pre-Processing indicator, TTQ

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 22

o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 21 o API = ‘02’

PPSE o AID = ‘A0000000030003’ Directory Entry 3 o Label = ‘APP3’ o Kernel Identifier = 23 o API = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 23

o API = ‘04’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘01’

o PDOL = ‘D1029F6604’

AID FCI 2 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘02’

o PDOL = ‘D1029F6604’

AID FCI 3 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘03’ o PDOL = ‘D1029F6604’

AID FCI 4 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘04’ o PDOL = ‘D1029F6604’

o Removal Timeout value = ‘0000’

Table C.79: [Ltsetting2.3]

[Ltsetting2.4] characteristics:

• multi AID with full match: AID 1 (A0000000040004) with the highest priority having ‘Zero Amount Allowed’ flag present and set to 0 (corresponding to Kernel ID = 4), AID 2 (A0000000020002) with the lowest priority having ‘Zero Amount Allowed’ flag not present (corresponding to Kernel ID = 2)

AID Kernel ID Priority

A0000000040004 24 1

A0000000020002 22 2

• PDOL with Pre-Processing indicator, TTQ

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 22

o API = ‘02’

AID FCI 1 o AID = ‘A0000000040004’ o Label = ‘APP4’

o API = ‘01’ o PDOL = ‘D1029F6604’

AID FCI 2 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘02’ o PDOL = ‘D1029F6604’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.80: [Ltsetting2.4]

[Ltsetting2.5] characteristics:

• multi AID with full match: AID 1 (A0000000030003) with the highest priority having ‘Zero Amount Allowed’ flag present and set to 1 and TTQ indicating ‘offline only reader’(corresponding to Kernel ID = 2), AID 2 (A0000000020002) with the lowest priority having ‘Zero Amount Allowed’ flag present and set to 1 and TTQ indicating ‘online reader’ (corresponding to Kernel ID = 4)

AID Kernel ID Priority

A0000000030003 22 1

A0000000020002 24 2

• PDOL with Pre-Processing indicator, TTQ

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 22 API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24 o API = ‘02’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘D1029F6604’

AID FCI 2 o AID = ‘A0000000020002’ o Label = ‘APP2’

o API = ‘02’ o PDOL = ‘D1029F6604’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.81: [Ltsetting2.5]

[Ltsetting2.6] characteristics:

• multi AID with full match: AID 1 (A0000000010001) with the highest priority having ‘Reader Contactless Transaction Limit ‘present (corresponding to Kernel ID = 3), AID 2 (A0000000020002) with the lowest priority having ‘Reader Contactless Transaction Limit‘ not present (corresponding to Kernel ID = 2)

AID Kernel ID Priority

A0000000010001 23 1

A0000000020002 22 2

• PDOL with Pre-Processing indicator, TTQ,

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 22

o API = ‘02’

AID FCI 1 o AID = ‘A0000000010001’ o Label = ‘APP1’

o API = ‘01’ o PDOL = ‘D1029F6604’

AID FCI 2 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘02’ o PDOL = ‘D1029F6604’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.82: [Ltsetting2.6]

[Ltsetting2.7] characteristics:

• multi AID

AID Kernel ID Priority

A0000000030003 21 1

A0000000020002 24 2

A0000000010001 23 3

A0000000040004 24 4

• PDOL with Pre-Processing indicator, TTQ, kernel ID, FCI

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’

o start B o Online Response Data: EMV Data (Issuer Script Data (71)) o CVM: NA o UI Request on Outcome Present: No o UI Request on Restart Present: No

o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘02’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23

o API = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘04’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘02’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A0000000010001’ o Label = ‘APP1’ o API = ‘03’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A0000000040004’

o Label = ‘APP4’

o API = ‘04’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Online o Tag 71 = ‘1112131415161718191A1B1C1D1E1F20’ Response 1 GPO response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.83: [Ltsetting2.7]

[Ltsetting2.8] characteristics:

• multi AID

AID Kernel ID Priority

A0000000030003 21 1

A0000000020002 24 2

A0000000010001 23 3

A0000000040004 24 4

• PDOL with Pre-Processing indicator, TTQ, kernel ID, FCI

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’

o start B o Online Response Data: EMV Data (Issuer Auth Data (91) and Issuer Script Data (71))

o CVM: NA o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No

o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’

o Kernel Identifier = 21 o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘02’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘04’

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’ o API = ‘01’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A0000000020002’ o Label = ‘APP2’

o API = ‘02’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A0000000010001’ o Label = ‘APP1’

o API = ‘03’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A0000000040004’

o Label = ‘APP4’

o API = ‘04’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Online o Tag 71 = ‘1112131415161718191A1B1C1D1E1F20’ Response 1 GPO o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.84: [Ltsetting2.8]

[Ltsetting2.9] characteristics:

• multi AID

AID Kernel ID Priority

A0000000030003 21 1

A0000000020002 24 2

A0000000010001 23 3

A0000000040004 24 4

• PDOL with Pre-Processing indicator, TTQ, kernel ID, FCI

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’

o start B o Online Response Data: EMV Data (Issuer Auth Data (91) and Issuer Script Data (72))

o CVM: NA o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No

o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’

o Kernel Identifier = 21 o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘02’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘04’

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’ o API = ‘01’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A0000000020002’ o Label = ‘APP2’

o API = ‘02’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A0000000010001’ o Label = ‘APP1’

o API = ‘03’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A0000000040004’

o Label = ‘APP4’

o API = ‘04’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO o Tag 72 = ‘2122232425262728292A2C2D2E2F30’ response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.85: [Ltsetting2.9]

[Ltsetting2.10] characteristics:

• multi AID

AID Kernel ID Priority

A0000000030003 21 1

A0000000020002 24 2

A0000000010001 23 3

A0000000040004 24 4

• PDOL with Pre-Processing indicator, TTQ, kernel ID, FCI

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’

o start B o Online Response Data: EMV Data (Issuer auth (91) o CVM: NA o UI Request on Outcome Present: No o UI Request on Restart Present: No

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘02’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23

o API = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘04’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘02’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A0000000010001’ o Label = ‘APP1’ o API = ‘03’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A0000000040004’

o Label = ‘APP4’

o API = ‘04’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.86: [Ltsetting2.10]

[Ltsetting2.11] characteristics:

• multi AID

AID Kernel ID Priority Extended selection Data

A0000000030003 21 4 ‘01’

A0000000020002 24 3 ‘02’

A0000000010001 23 2 ‘03’

A0000000040004 24 1 ‘04’

• PDOL with Pre-Processing indicator, TTQ, restart flag, FCI, kernel ID

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’ o start B o Online Response Data: EMV Data (Issuer Auth Data (91)) o CVM: NA

o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘04’ o Extended Selection Data = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘03’ o Extended Selection Data = ‘02’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘02’ o Extended Selection Data = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’ o Extended Selection Data = ‘04’

AID FCI 1 o AID = ‘A000000003000301’

o Label = ‘APP3’ o API = ‘04’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A000000002000202’

o Label = ‘APP2’

o API = ‘03’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A000000001000103’

o Label = ‘APP1’

o API = ‘02’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A000000004000404’

o Label = ‘APP4’ o API = ‘01’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.87: [Ltsetting2.11]

[Ltsetting2.12] characteristics:

• multi AID

AID Kernel ID Priority Extended selection Data

A0000000030003 21 4 ‘01’

A0000000020002 24 3 ‘02’

A0000000010001 23 2 ‘03’

A0000000040004 24 1 ‘04’

• PDOL with Pre-Processing indicator, TTQ, restart flag, FCI, kernel ID

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’ o start B o Online Response Data: EMV Data (Issuer Script Data (71)) o CVM: NA

o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘04’ o Extended Selection Data = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘03’ o Extended Selection Data = ‘02’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘02’ o Extended Selection Data = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’ o Extended Selection Data = ‘04’

AID FCI 1 o AID = ‘A000000003000301’

o Label = ‘APP3’ o API = ‘04’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A000000002000202’

o Label = ‘APP2’

o API = ‘03’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A000000001000103’

o Label = ‘APP1’

o API = ‘02’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A000000004000404’

o Label = ‘APP4’ o API = ‘01’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Online o Tag 71 = ‘1112131415161718191A1B1C1D1E1F20’ Response 1 GPO response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.88: [Ltsetting2.12]

[Ltsetting2.13] characteristics:

• multi AID

AID Kernel ID Priority Extended selection Data

A0000000030003 21 4 ‘01’

A0000000020002 24 3 ‘02’

A0000000010001 23 2 ‘03’

A0000000040004 24 1 ‘04’

• PDOL with Pre-Processing indicator, TTQ, restart flag, FCI, kernel ID

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’ o start B o Online Response Data: EMV Data (Issuer Script Data (72)) o CVM: NA

o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘04’ o Extended Selection Data = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘03’ o Extended Selection Data = ‘02’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘02’ o Extended Selection Data = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’ o Extended Selection Data = ‘04’

AID FCI 1 o AID = ‘A000000003000301’

o Label = ‘APP3’ o API = ‘04’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A000000002000202’

o Label = ‘APP2’

o API = ‘03’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A000000001000103’

o Label = ‘APP1’

o API = ‘02’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A000000004000404’

o Label = ‘APP4’ o API = ‘01’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Online o Tag 72 = ‘2122232425262728292A2C2D2E2F30’ Response 1 GPO response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.89: [Ltsetting2.13]

[Ltsetting2.14] characteristics:

• multi AID

AID Kernel ID Priority Extended selection Data

A0000000030003 21 4 ‘01’

A0000000020002 24 3 ‘02’

A0000000010001 23 2 ‘03’

A0000000040004 24 1 ‘04’

• PDOL with Pre-Processing indicator, TTQ, restart flag, FCI, kernel ID

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’ o start B o Online Response Data: EMV Data (Issuer Auth Data (91) and Issuer Script Data (71))

o CVM: NA o UI Request on Outcome Present: No

o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘04’ o Extended Selection Data = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘03’ o Extended Selection Data = ‘02’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘02’ o Extended Selection Data = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’ o Extended Selection Data = ‘04’

AID FCI 1 o AID = ‘A000000003000301’

o Label = ‘APP3’ o API = ‘04’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A000000002000202’

o Label = ‘APP2’

o API = ‘03’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A000000001000103’

o Label = ‘APP1’

o API = ‘02’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A000000004000404’

o Label = ‘APP4’ o API = ‘01’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO o Tag 71 = ‘1112131415161718191A1B1C1D1E1F20’ response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.90: [Ltsetting2.14]

[Ltsetting2.15] characteristics:

• multi AID

AID Kernel ID Priority Extended selection Data

A0000000030003 21 4 ‘01’

A0000000020002 24 3 ‘02’

A0000000010001 23 2 ‘03’

A0000000040004 24 1 ‘04’

• PDOL with Pre-Processing indicator, TTQ, restart flag, FCI, kernel ID

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’ o start B o Online Response Data: EMV Data (Issuer Auth Data (91) and Issuer Script Data (72))

o CVM: NA o UI Request on Outcome Present: No

o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘04’ o Extended Selection Data = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘03’ o Extended Selection Data = ‘02’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘02’ o Extended Selection Data = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’ o Extended Selection Data = ‘04’

AID FCI 1 o AID = ‘A000000003000301’

o Label = ‘APP3’ o API = ‘04’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A000000002000202’

o Label = ‘APP2’

o API = ‘03’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A000000001000103’

o Label = ‘APP1’

o API = ‘02’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A000000004000404’

o Label = ‘APP4’ o API = ‘01’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO o Tag 72 = ‘2122232425262728292A2C2D2E2F30’ response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.91: [Ltsetting2.15]

[Ltsetting2.16] characteristics:

• multi AID

AID Kernel ID Priority Extended selection Data

A0000000030003 21 4 ‘01’

A0000000020002 24 3 ‘02’

A0000000010001 23 2 ‘03’

A0000000040004 25 1 ‘04’

• PDOL with Pre-Processing indicator, TTQ, restart flag, FCI, kernel ID

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’ o start B o Online Response Data: EMV Data (Issuer Auth Data (91) , Issuer Script Data (71) and Issuer Script Data (72))

o CVM: NA o UI Request on Outcome Present: No

o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘04’ o Extended Selection Data = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘03’ o Extended Selection Data = ‘02’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘02’ o Extended Selection Data = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 25 o API = ‘01’ o Extended Selection Data = ‘04’

AID FCI 1 o AID = ‘A000000003000301’

o Label = ‘APP3’ o API = ‘04’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A000000002000202’

o Label = ‘APP2’

o API = ‘03’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A000000001000103’

o Label = ‘APP1’

o API = ‘02’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A000000004000404’

o Label = ‘APP4’ o API = ‘01’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO o Tag 71 = ‘1112131415161718191A1B1C1D1E1F20’ response o Tag 72 = ‘2122232425262728292A2C2D2E2F30’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.92: [Ltsetting2.16]

[Ltsetting2.17] characteristics:

• multi AID

AID Kernel ID Priority

A0000000030003 21 2

A0000000020002 24 3

A0000000010001 23 1

A0000000040004 24 4

• PDOL with Pre-Processing indicator, TTQ, FCI, kernel ID

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’

o start B o Online Response Data: EMV Data ‘(Issuer Script Data(72)) o CVM: NA o UI Request on Outcome Present: No o UI Request on Restart Present: No

o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference, NA o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘02’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘03’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23

o API = ‘01’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘04’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘02’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘03’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A0000000010001’ o Label = ‘APP1’ o API = ‘01’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A0000000040004’

o Label = ‘APP4’

o API = ‘04’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Online o Tag 72 = ‘2122232425262728292A2C2D2E2F30’ Response 1 GPO response

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.93: [Ltsetting2.17]

[Ltsetting2.18] characteristics:

• multi AID

AID Kernel ID Priority

A0000000030003 21 2

A0000000020002 24 3

A0000000010001 23 1

A0000000040004 24 4

• PDOL with Pre-Processing indicator, TTQ, FCI, kernel ID

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’

o start B o Online Response Data: EMV Data ‘( Issuer Auth Data (91), Issuer Script Data(71, 72))

o CVM: NA o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No

o Discretionary Data Present: No o Alternate Interface Preference, NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’

o Kernel Identifier = 21 o API = ‘02’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘03’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘04’

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’ o API = ‘02’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A0000000020002’ o Label = ‘APP2’

o API = ‘03’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A0000000010001’ o Label = ‘APP1’

o API = ‘01’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A0000000040004’

o Label = ‘APP4’

o API = ‘04’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO o Tag 71 = ‘1112131415161718191A1B1C1D1E1F20’ response o Tag 72 = ‘2122232425262728292A2C2D2E2F30’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.94: [Ltsetting2.18]

[Ltsetting2.19] characteristics:

• multi AID

AID Kernel ID Priority

A0000000030003 21 3

A0000000020002 24 1

A0000000010001 23 3

A0000000040004 24 2

• PDOL with Pre-Processing indicator, TTQ, restart flag, FCI, kernel ID

• When Restart=0, GPO Response indicates

o The Final Outcome ‘online request’

o start C o Online Response Data: Any o CVM: NA o UI Request on Outcome Present: No o UI Request on Restart Present: No

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘03’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘01’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23

o API = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘02’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘03’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A0000000010001’ o Label = ‘APP1’ o API = ‘03’

o PDOL = ‘D1029F6604D7086Fxx’(xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A0000000040004’

o Label = ‘APP4’

o API = ‘02’

o PDOL = ‘D1029F6604D7086Fxx’(xx corresponding to the FCI length)

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0C’ o Online Response Data = ‘02’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.95: [Ltsetting2.19]

[Ltsetting2.20] characteristics:

• multi AID, full match on AID and kernel ID for [Termsetting2] or [Termsetting3] highest priority = 1

AID Kernel ID Priority

A0000000010001 23 3

A0000000030003 21 1

A0000000020002 2B 2

A0000000040004 24 4

• PDOL with kernel ID, TTQ

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘03’

PPSE o AID = ‘A0000000030003’ Directory Entry 2 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 3 o Label = ‘APP2’ o Kernel Identifier = ‘2B’ o API = ‘02’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24

o API = ‘04’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’

o API = ‘03’

o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘02’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000040004’ o Label = ‘APP4’

o API = ‘04’

o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.96: [Ltsetting2.20]

[Ltsetting2.21] characteristics:

• multi AID, full match on AID, highest priority = 4

AID Kernel ID Priority

A0000000030003 21 7

A0000000020002 24 0

A0000000010001 23 4

A0000000040004 23 5

• PDOL with kernel ID,TTQ

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘07’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24 o API = ‘00’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘04’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 23

o API = ‘05’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘07’

o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘00’

o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘04’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘05’ o PDOL = ‘9F6604D708’

o Removal Timeout value = ‘0000’

Table C.97: [Ltsetting2.21]

[Ltsetting2.22] characteristics:

• multi AID, full match on AID several entries with highest priority = 1

AID Kernel ID Priority

A0000000010001 23 3

A0000000020002 24 1

A0000000040004 24 1

A0000000030003 22 1

• PDOL with kernel ID,TTQ

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23

o API = ‘03’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24 o API = ‘01’

PPSE o AID = ‘A0000000040004’ Directory Entry 3 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’

PPSE o AID = ‘A0000000030003’ Directory Entry 4 o Label = ‘APP3’ o Kernel Identifier = 22

o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘03’

o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’

o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘01’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘9F6604D708’

o Removal Timeout value = ‘0000’

Table C.98: [Ltsetting2.22]

[Ltsetting2.23] characteristics:

• multi AID, full match on AID entries with priority = 0 or not present

AID Kernel ID Priority

A0000000010001 23 Not present

A0000000030003 21 0

A0000000020002 24 0

A0000000040004 24 Not present

PDOL with kernel ID,TTQ

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23

PPSE o AID = ‘A0000000030003’ Directory Entry 2 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘00’

PPSE o AID = ‘A0000000020002’ Directory Entry 3 o Label = ‘APP2’ o Kernel Identifier = 24 o API = ‘00’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000030003’

o Label = ‘APP3’

o API = ‘00’

o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000020002’ o Label = ‘APP2’

o API = ‘00’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000040004’

o Label = ‘APP4’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.99: [Ltsetting2.23]

[Ltsetting2.24] characteristics:

• multi AID, full match on AID and kernel ID for [Termsetting1] highest priority = 10

AID Kernel ID Priority

A0000000010001 23 12

A0000000030003 BF0840 11

A0000000020002 810978 10

A0000000040004 24 14

• PDOL with kernel ID,TTQ

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23

o API = ‘0C’

PPSE o AID = ‘A0000000030003’ Directory Entry 2 o Label = ‘APP3’ o Kernel Identifier = ‘BF0840’ o API = ‘0B’

PPSE o AID = ‘A0000000020002’ Directory Entry 3 o Label = ‘APP2’ o Kernel Identifier = ‘810978’ o API = ‘0A’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24

o API = ‘0E’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘0C’

o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘0B’

o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘0A’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘0E’ o PDOL = ‘9F6604D708’

o Removal Timeout value = ‘0000’

Table C.100: [Ltsetting2.24]

[Ltsetting2.25] characteristics:

• multi AID

AID Kernel ID Priority Extended selection Data

A0000000030003 21 4 ‘01’

A0000000020002 24 3 ‘02’

A0000000010001 23 2 ‘03’

A0000000040004 24 1 ‘04’

• PDOL with Pre-Processing indicator, TTQ, FCI, kernel ID

• When Restart = 0, GPO Response indicates

o The Final Outcome ‘online request’ o start C o Online Response Data: Any o CVM: NA

o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 0 • When Restart = 1, GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘04’ o Extended Selection Data = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘03’ o Extended Selection Data = ‘02’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘02’ o Extended Selection Data = ‘03’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’ o Extended Selection Data = ‘04’

AID FCI 1 o AID = ‘A000000003000301’

o Label = ‘APP3’ o API = ‘04’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 2 o AID = ‘A000000002000202’

o Label = ‘APP2’

o API = ‘03’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 3 o AID = ‘A000000001000103’

o Label = ‘APP1’

o API = ‘02’

o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

AID FCI 4 o AID = ‘A000000004000404’

o Label = ‘APP4’ o API = ‘01’ o PDOL = ‘D1029F6604D7086Fxx’ (xx corresponding to the FCI length)

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0C’ o Online Response Data = ‘02’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.101: [Ltsetting2.25]

[Ltsetting2.30] characteristics

• multi AID VISA (full AID associated Kernel ID = 3) with the highest priority PDOL with Kernel ID, NO TTQ

AID Kernel ID Priority

A0000000031010 3 1

A0000000251010 4 2

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000031010’ Directory Entry 1 o Label = ‘VISA’ o Kernel Identifier = 3 o API = ‘01’

PPSE o AID = ‘A0000000251010’ Directory Entry 2 o Label = ‘AMEX’ o Kernel Identifier = TK4 Kernel ID o API = ‘02’

AID FCI 1 o AID = ‘A0000000031010’

o Label = ‘VISA’ o API = ‘01’

o PDOL = ‘D708’

AID FCI 2 o AID = ‘A0000000251010’

o Label = ‘AMEX’ o API = ‘02’

o PDOL = ‘D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’

o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.102: [Ltsetting2.30]

[Ltsetting2.31] characteristics

• multi AID VISA (full AID associated Kernel ID = 3) with the highest priority, No PDOL

AID Kernel ID Priority

A000000003101001 3 1

A0000000251010 4 2

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A000000003101001’ Directory Entry 1 o Label = ‘VISA’ o Kernel Identifier = 3

o API = ‘01’

PPSE o AID = ‘A0000000251010’ Directory Entry 2 o Label = ‘AMEX’ o Kernel Identifier = TK4 Kernel ID o API = ‘02’

AID FCI 1 o AID = ‘A000000003101001’

o Label = ‘VISA’ o API = ‘01’

AID FCI 2 o AID = ‘A0000000251010’ o Label = ‘AMEX’ o API = ‘02’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.103: [Ltsetting2.31]

[Ltsetting2.40] characteristics:

• multi AID, full match on AID and kernel ID for [Termsetting2], [Termsetting3]

AID Kernel ID Priority Outcome

A0000000010001 23 1 Select Next

A0000000030003 21 2 Select Next

A0000000020002 22 3 Approved

• PDOL with TTQ, kernel ID , Unpredictable Number

• GPO Response indicates the Final Outcome

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

PPSE o AID = ‘A0000000030003’ Directory Entry 2 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘02’

PPSE o AID = ‘A0000000020002’ Directory Entry 3 o Label = ‘APP2’ o Kernel Identifier = 22

o API = ‘03’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘01’ o PDOL = ‘9F6604D7089F3704’

AID FCI 2 o AID = ‘A0000000030003’

o Label = ‘APP3’

o API = ‘02’

o PDOL = ‘9F6604D7089F3704’

AID FCI 3 o AID = ‘A0000000020002’

o Label = ‘APP2’

o API = ‘03’

o PDOL = ‘9F6604D7089F3704’

Outcome 1 o Outcome Value = ’01’ GPO response o Start value = ‘0C’ (for AID FCI o Online Response Data = ‘00’ 1) o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Outcome 2 o Outcome Value = ’01’ GPO response o Start value = ‘0C’ (for AID FCI o Online Response Data = ‘00’ 2) o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Outcome 3 o Outcome Value = ’03’ GPO response o Start value = ‘00’ (for AID FCI o Online Response Data = ‘00’ 3)

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.104: [Ltsetting2.40]

[Ltsetting2.41] characteristics:

• multi AID, full match on AID and kernel ID for [Termsetting2], [Termsetting3]

AID Kernel ID Priority Outcome

A0000000030003 21 1 Select Next

A0000000030003 22 2 Approved

• PDOL with kernel ID

• GPO Response indicates the Final Outcome

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

PPSE o AID = ‘A0000000030003’ Directory Entry 2 o Label = ‘APP3’ o Kernel Identifier = 22 o API = ‘02’

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’

o API = ‘01’ o PDOL = ‘D708’

AID FCI 2 o AID = ‘A0000000030003’

o Label = ‘APP3’

o API = ‘02’

o PDOL = ‘D708’

o Removal Timeout value = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ (for AID FCI o Online Response Data = ‘00’ 2) o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.105: [Ltsetting2.41]

[Ltsetting2.42] characteristics:

• multi AID with full match: AID 1 (A0000000030003) with the highest priority having ‘Zero Amount Allowed’ flag present and set to 0 (corresponding to Kernel ID = 5), AID 2 (A0000000020002) with the lowest priority having ‘Zero Amount Allowed’ flag not present (corresponding to Kernel ID = 2)

AID Kernel ID Priority

A0000000030003 25 1

A0000000020002 22 2

• PDOL with Pre-Processing indicator, TTQ

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 25 o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘02’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘01’ o PDOL = ‘D1029F6604’

AID FCI 2 o AID = ‘A0000000020002’ o Label = ‘APP2’ o API = ‘02’

o PDOL = ‘D1029F6604’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.106: [Ltsetting2.42]

[Ltsetting2.43] characteristics:

• multi AID with full match: AID 1 (A0000000040004) with the highest priority having ‘Reader Contactless Transaction Limit ‘present (corresponding to Kernel ID = 5), AID 2 (A0000000020002) with the lowest priority having ‘Reader Contactless Transaction Limit‘ not present (corresponding to Kernel ID = 2)

AID Kernel ID Priority

A0000000040004 25 1

A0000000020002 22 2

• PDOL with Pre-Processing indicator, TTQ,

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 25 o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 22

o API = ‘02’

AID FCI 1 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘01’

o PDOL = ‘D1029F6604’

AID FCI 2 o AID = ‘A0000000020002’

o Label = ‘APP2’

o API = ‘02’

o PDOL = ‘D1029F6604’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.107: [Ltsetting2.43]

[Ltsetting2.44] characteristics:

• multi AID, full match on AID and kernel ID for [Termsetting2]

• highest priority = 3

AID Kernel ID Priority

A0000000010001 23 3

A0000000030003 25 4

A0000000020002 2B 5

A0000000040004 24 6

• PDOL with kernel ID, TTQ

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23

o API = ‘03’

PPSE o AID = ‘A0000000030003’ Directory Entry 2 o Label = ‘APP3’ o Kernel Identifier = 25 o API = ‘04’

PPSE o AID = ‘A0000000020002’ Directory Entry 3 o Label = ‘APP2’ o Kernel Identifier = ‘2B’ o API = ‘05’

PPSE o AID = ‘A0000000040004’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘06’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘03’

o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘04’ o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘05’

o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000040004’

o Label = ‘APP4’

o API = ‘06’

o PDOL = ‘9F6604D708’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.108: [Ltsetting2.44]

[Ltsetting2.45] characteristics:

• multi AID, full match on AID and kernel ID for [Termsetting2]

AID Kernel ID Priority Outcome

A0000000030003 22 1 Select Next

A0000000040004 25 2 Approved

• PDOL with kernel ID

• GPO Response indicates the Final Outcome

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 22

o API = ‘01’

PPSE o AID = ‘A0000000040004’ Directory Entry 2 o Label = ‘APP4’ o Kernel Identifier = 25

o API = ‘02’

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’

o API = ‘01’ o PDOL = ‘D708’

AID FCI 2 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘02’ o PDOL = ‘D708’

Outcome 1 o Outcome Value = ’01’ GPO response o Start value = ‘0C’ (for AID FCI o Online Response Data = ‘00’ 1) o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Outcome 2 o Outcome Value = ’03’ GPO response o Start value = ‘00’ (for AID FCI o Online Response Data = ‘00’ 2)

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.109: [Ltsetting2.45]

[Ltsetting3.X] characteristics: multi AID with partial match [Ltsetting3.1] characteristics:

• multi AID, partial match on some AID

AID Kernel ID Priority

A0000000030003 21 4

A0000000020002010203040506070809 24 2

A0000000010001 23 3

A0000000040004010203040506070809 24 1

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘04’

PPSE o AID = ‘A0000000020002010203040506070809’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘02’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘03’

PPSE o AID = ‘A0000000040004010203040506070809’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 24

o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’

o API = ‘04’

o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000020002010203040506070809’ o Label = ‘APP2’

o API = ‘02’ o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘03’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000040004010203040506070809

o Label = ‘APP4’ o API = ‘01’

o PDOL = ‘9F6604D708’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.110: [Ltsetting3.1]

[Ltsetting3.2] characteristics:

• multi AID , partial match on some AID several entries with highest priority = 14

AID Kernel ID Priority

A0000000020002 24 0

A0000000010001010203040506070809 23 14

A0000000040004010203040506070809 23 14

A0000000030003 22 14

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘00’

PPSE o AID = ‘A0000000010001010203040506070809’ Directory Entry 2 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘0E’

PPSE o AID = ‘A0000000040004010203040506070809’ Directory Entry 3 o Label = ‘APP4’ o Kernel Identifier = 23 o API = ‘0E’

PPSE o AID = ‘A0000000030003’ Directory Entry 4 o Label = ‘APP3’ o Kernel Identifier = 22

o API = ‘0E’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘00’

o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000010001010203040506070809’

o Label = ‘APP1’ o API = ‘0E’

o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000040004010203040506070809’

o Label = ‘APP4’ o API = ‘0E’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘0E’ o PDOL = ‘9F6604D708’

o Removal Timeout value = ‘0000’

Table C.111: [Ltsetting3.2]

[Ltsetting3.3] characteristics:

• multi AID, partial match on some AID with priority = 0 or not present

AID Kernel ID Priority

A0000000010001010203040506070809 23 0

A0000000040004010203040506070809 23 Not present

A0000000030003 21 0

A0000000020002 24 Not present

• PDOL with Pre-Processing indicator, TTQ, restart flag, FCI, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000010001010203040506070809’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23

o API = ‘00’

PPSE o AID = ‘A0000000040004010203040506070809’ Directory Entry 2 o Label = ‘APP4’ o Kernel Identifier = 23

PPSE o AID = ‘A0000000030003’ Directory Entry 3 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘00’

PPSE o AID = ‘A0000000020002’ Directory Entry 4 o Label = ‘APP2’ o Kernel Identifier = 24

AID FCI 1 o AID = ‘A0000000010001010203040506070809’

o Label = ‘APP1’ o API = ‘00’

o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000040004010203040506070809’

o Label = ‘APP4’

o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000030003’ o Label = ‘APP3’

o API = ‘00’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000020002’

o Label = ‘APP2’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.112: [Ltsetting3.3]

[Ltsetting3.4] characteristics:

• multi AID, full match on AID and kernel ID for [Termsetting1] highest priority = 3

AID Kernel ID Priority

A0000000010001 23 12

A0000000030003 21 11

A0000000020002 810978 10

A0000000040004010203040506070809 FF2222 3

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23

o API = ‘0C’

PPSE o AID = ‘A0000000030003’ Directory Entry 2 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘0B’

PPSE o AID = ‘A0000000020002’ Directory Entry 3 o Label = ‘APP2’ o Kernel Identifier = ‘810978’ o API = ‘0A’

PPSE o AID = ‘A0000000040004010203040506070809’ Directory Entry 2 o Label = ‘APP4’ o Kernel Identifier = ‘FF2222’

o API = ‘03’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘0C’

o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘0B’

o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘0A’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000040004010203040506070809’

o Label = ‘APP4’ o API = ‘03’ o PDOL = ‘9F6604D708’

o Removal Timeout value = ‘0000’

Table C.113: [Ltsetting3.4]

[Ltsetting3.5] characteristics:

• Select PPSE response with 2 templates 61 Extension selection present

AID Kernel ID Priority Extended Selection Data

A000000001000101 23 1 0303

A0000000020002 22 2 0202

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A000000001000101’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

o Extented Selection Data = ‘0303’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘02’ o Extented Selection Data = ‘0202’

AID FCI 1 o AID = ‘A0000000010001010303’

o Label = ‘APP1’ o API = ‘01’ o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A00000000200020202’

o Label = ‘APP2’

o API = ‘02’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.114: [Ltsetting3.5]

[Ltsetting3.6] characteristics:

• multi AID , partial match on some AID several entries with highest priority = 8

AID Kernel ID Priority

A0000000020002 24 9

A0000000040004010203040506070809 25 8

A0000000010001010203040506070809 23 8

A0000000030003 22 8

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 24

o API = ‘09’

PPSE o AID = ‘A0000000040004010203040506070809’ Directory Entry 2 o Label = ‘APP4’ o Kernel Identifier = 25

o API = ‘08’

PPSE o AID = ‘A0000000010001010203040506070809’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23

o API = ‘08’

PPSE o AID = ‘A0000000030003’ Directory Entry 4 o Label = ‘APP3’ o Kernel Identifier = 22 o API = ‘08’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘09’ o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000040004010203040506070809’ o Label = ‘APP4’

o API = ‘08’ o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000010001010203040506070809’

o Label = ‘APP1’ o API = ‘08’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000030003’ o Label = ‘APP3’

o API = ‘08’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.115: [Ltsetting3.6]

[Ltsetting3.7] characteristics:

• multi AID, partial match on some AID with priority = 0 or not present

AID Kernel ID Priority

A0000000030003010203040506070809 25 Not present

A0000000040004010203040506070809 23 0

A0000000030003 21 0

A0000000020002 24 Not present

• PDOL with Pre-Processing indicator, TTQ, restart flag, FCI, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003010203040506070809’ Directory Entry 1 o Label = ‘APP3’

o Kernel Identifier = 25

PPSE o AID = ‘A0000000040004010203040506070809’ Directory Entry 2 o Label = ‘APP4’ o Kernel Identifier = 23

o API = ‘00’

PPSE o AID = ‘A0000000030003’ Directory Entry 3 o Label = ‘APP3’ o Kernel Identifier = 21

o API = ‘00’

PPSE o AID = ‘A0000000020002’ Directory Entry 4 o Label = ‘APP2’ o Kernel Identifier = 24

AID FCI 1 o AID = ‘A0000000030003010203040506070809’

o Label = ‘APP3’ o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000040004010203040506070809’

o Label = ‘APP4’ o API = ‘00’ o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000030003’ o Label = ‘APP3’

o API = ‘00’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000020002’

o Label = ‘APP2’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.116: [Ltsetting3.7]

[Ltsetting4.x]: no match on kernel ID or AID [Ltsetting4.1] characteristics:

• Select PPSE response with 7 templates 61 (6 templates with the highest priority and a kernel ID that does not match any kernel ID of the reader combination of [Termsetting1] and the last one (lowest priority) with a kernel ID matching.

AID Kernel ID Priority AID/kernel ID matching

A0000000030003 6 1 No

A0000000020002 62 1 No

A0000000010001 810977 1 No

A000000003000301 BF0841 1 No

A000000002000201 811110 1 No

A000000001000101 BF2223 1 No

A0000000040004 24 2 Yes

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 6

o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = ‘62’ o API = ‘01’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = ‘810977’

o API = ‘01’

PPSE o AID = ‘A000000003000301’ Directory Entry 4 o Label = ‘APP3’ o Kernel Identifier = ‘BF0841’

o API = ‘01’

PPSE o AID = ‘A000000002000201’ Directory Entry 5 o Label = ‘APP2’ o Kernel Identifier = ‘811110’ o API = ‘01’

PPSE o AID = ‘A000000001000101’ Directory Entry 6 o Label = ‘APP1’ o Kernel Identifier = ‘BF2223’ o API = ‘01’

PPSE o AID = ‘A0000000040004’ Directory Entry 7 o Label = ‘APP4’ o Kernel Identifier = 24

o API = ‘02’

AID FCI 7 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘02’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.117: [Ltsetting4.1]

[Ltsetting4.2] characteristics:

• Select PPSE response with 7 templates 61 (6 templates with the highest priority and a kernel ID that does not match any kernel ID of the reader combination of [Termsetting2], [Termsetting3] and the last one (lowest priority) with a kernel ID matching

AID Kernel ID Priority AID/kernel ID matching

A0000000030003 23 1 No

A0000000020002 25 1 No

A0000000010001 22 1 No

A000000004000402 21 1 No

A000000003000301 24 1 No

A000000002000201 23 1 No

A0000000040004 24 2 Yes

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 23 o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 25 o API = ‘01’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 22

o API = ‘01’

PPSE o AID = ‘A000000004000402’ Directory Entry 4 o Label = ‘APP4’ o Kernel Identifier = 21

o API = ‘01’

PPSE o AID = ‘A000000003000301’ Directory Entry 5 o Label = ‘APP3’ o Kernel Identifier = 24 o API = ‘01’

PPSE o AID = ‘A000000002000201’ Directory Entry 6 o Label = ‘APP2’ o Kernel Identifier = 23 o API = ‘01’

PPSE o AID = ‘A0000000040004’ Directory Entry 7 o Label = ‘APP4’ o Kernel Identifier = 24

o API = ‘02’

AID FCI 7 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘02’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.118: [Ltsetting4.2]

[Ltsetting5.X]: kernel Identifier not present or ‘00’ in PPSE [Ltsetting5.1] characteristics:

• Single AID VISA (full match) (Kernel Id not present)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000031010’ Directory Entry 1 o Label = ‘VISA’ o API = ‘01’

AID FCI 1 o AID = ‘A0000000031010’ o Label = ‘VISA’

o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.119: [Ltsetting5.1]

[Ltsetting5.2] characteristics:

• Single AID MasterCard ‘A000000004101001’ (partial match) (Kernel ID not present)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A000000004101001’ Directory Entry 1 o Label = ‘MASTERCARD’ o API = ‘01’

AID FCI 1 o AID = ‘A000000004101001’

o Label = ‘MASTERCARD’ o API = ‘01’ o PDOL = ‘D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.120: [Ltsetting5.2]

[Ltsetting5.3] characteristics:

• Single AID JCB (full match) (Kernel Identifier not present)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000651010’ Directory Entry 1 o Label = ‘JCB’ o API = ‘01’

AID FCI 1 o AID = ‘A0000000651010’

o Label = ‘JCB’ o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.121: [Ltsetting5.3]

[Ltsetting5.4] characteristics:

• Single AID AMEX ‘A000000025101001 (partial match) (Kernel Identifier not present)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A000000025101001’ Directory Entry 1 o Label = ‘AMEX’ o API = ‘01’

AID FCI 1 o AID = ‘A000000025101001’

o Label = ‘AMEX’ o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.122: [Ltsetting5.4]

[Ltsetting5.5] characteristics:

• Single AID VISA with full match on AID and Kernel Identifier = ’00’

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000031010’ Directory Entry 1 o Label = ‘VISA’ o Kernel Identifier = ‘00’ o API = ‘01’

AID FCI 1 o AID = ‘A0000000031010’

o Label = ‘VISA’ o API = ‘01’ o PDOL = ‘9F6604D708’

o Removal Timeout value = ‘0000’

Table C.123: [Ltsetting5.5]

[Ltsetting5.6] characteristics:

• Single AID MasterCard ‘A000000004101001’ with partial match on AID and Kernel Identifier = ’00’

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A000000004101001’ Directory Entry 1 o Label = ‘MASTERCARD’ o Kernel Identifier = ‘00’ o API = ‘01’

AID FCI 1 o AID = ‘A000000004101001’

o Label = ‘MASTERCARD’ o API = ‘01’ o PDOL = ‘D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.124: [Ltsetting5.6]

[Ltsetting5.7] characteristics:

• Single AID JCB with full match on AID and Kernel Identifier = ’00’

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000651010’ Directory Entry 1 o Label = ‘JCB’ o Kernel Identifier = ‘00’ o API = ‘01’

AID FCI 1 o AID = ‘A0000000651010’

o Label = ‘JCB’ o API = ‘01’ o PDOL = ‘9F6604D708’

o Removal Timeout value = ‘0000’

Table C.125: [Ltsetting5.7]

[Ltsetting5.8] characteristics:

• Single AID AMEX ‘A000000025101001 with partial match on AID and Kernel Identifier = ’00’

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A000000025101001’ Directory Entry 1 o Label = ‘AMEX’ o Kernel Identifier = ‘00’ o API = ‘01’

AID FCI 1 o AID = ‘A000000025101001’

o Label = ‘AMEX’ o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.126: [Ltsetting5.8]

[Ltsetting5.10] characteristics:

• multi AID: full aid match; kernel ID not present with highest priority

AID Kernel ID Priority

A0000000651010 TK1 Kernel ID 4

A0000000041010 TK4 Kernel ID 3

A0000000031010 TK3 Kernel ID 3

A0000000251010 Not present 1

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000651010’ Directory Entry 1 o Label = ‘JCB’ o Kernel Identifier = TK1 Kernel ID

o API = ‘04’

PPSE o AID = ‘A0000000041010’ Directory Entry 2 o Label = ‘MASTERCARD’ o Kernel Identifier = TK4 Kernel ID o API = ‘03’

PPSE o AID = ‘A0000000031010’ Directory Entry 3 o Label = ‘VISA’ o Kernel Identifier = TK3 Kernel ID o API = ‘03’

PPSE o AID = ‘A0000000251010’ Directory Entry 4 o Label = ‘AMEX’ o API = ‘01’

AID FCI 1 o AID = ‘A0000000651010’

o Label = ‘JCB’

o API = ‘04’

o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000041010’

o Label = ‘MASTERCARD’

o API = ‘03’

o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000031010’ o Label = ‘VISA’

o API = ‘03’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000251010’

o Label = ‘AMEX’ o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.127: [Ltsetting5.10]

[Ltsetting5.11] characteristics:

• multi AID: partial aid match; kernel ID not present with highest priority

AID Kernel ID Priority

A0000000651010 TK1 4

A00000000410100101 Not present 1

A0000000031010 TK3 3

A0000000251010 TK4 2

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000651010’ Directory Entry 1 o Label = ‘JCB’ o Kernel Identifier = TK1 Kernel ID

o API = ‘04’

PPSE o AID = ‘A000000004101001’ Directory Entry 2 o Label = ‘MASTERCARD’ o API = ‘01’

PPSE o AID = ‘A0000000031010’ Directory Entry 3 o Label = ‘VISA’ o Kernel Identifier = TK3 Kernel ID o API = ‘03’

PPSE o AID = ‘A0000000251010’ Directory Entry 4 o Label = ‘AMEX’ o Kernel Identifier = TK4 Kernel ID

o API = ‘02’

AID FCI 1 o AID = ‘A0000000651010’

o Label = ‘JCB’

o API = ‘04’

o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A000000004101001’

o Label = ‘MASTERCARD’

o API = ‘01’

o PDOL = ‘D708’

AID FCI 3 o AID = ‘A0000000031010’ o Label = ‘VISA’

o API = ‘03’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000251010’

o Label = ‘AMEX’ o API = ‘02’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.128: [Ltsetting5.11]

[Ltsetting5.12] characteristics:

• multi AID: full AMEX AID matches kernel ID with highest priority

AID Kernel ID Priority

A0000000651010 TK1 2

A0000000251010 0 1

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000651010’ Directory Entry 1 o Label = ‘JCB’ o Kernel Identifier = TK1 Kernel ID o API = ‘02’

PPSE o AID = ‘A0000000251010’ Directory Entry 2 o Label = ‘AMEX’ o Kernel Identifier = ‘00’ o API = ‘01’

AID FCI 1 o AID = ‘A0000000651010’ o Label = ‘JCB’

o API = ‘02’ o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000251010’

o Label = ‘AMEX’ o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.129: [Ltsetting5.12]

[Ltsetting5.13] characteristics:

• Single AID VISA ‘A000000003101001’ (partial match) (Kernel Identifier with zero length)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A000000003101001’ Directory Entry 1 o Label = ‘VISA’ o Kernel Identifier = ‘’ o API = ‘01’

AID FCI 1 o AID = ‘A000000003101001’

o Label = ‘VISA’ o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.130: [Ltsetting5.13]

[Ltsetting5.14] characteristics:

• Single AID MasterCard (full match) (Kernel Identifier with zero length)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000041010’ Directory Entry 1 o Label = ‘MASTERCARD’ o Kernel Identifier = ‘’ o API = ‘01’

AID FCI 1 o AID = ‘A0000000041010’

o Label = ‘MASTERCARD’ o API = ‘01’ o PDOL = ‘D708’

o Removal Timeout value = ‘0000’

Table C.131: [Ltsetting5.14]

[Ltsetting5.15] characteristics:

• Single AID JCB ‘A000000065101001’ (partial match) (Kernel Identifier with zero length)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A000000065101001’ Directory Entry 1 o Label = ‘JCB’ o Kernel Identifier = ‘’ o API = ‘01’

AID FCI 1 o AID = ‘A000000065101001’

o Label = ‘JCB’ o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.132: [Ltsetting5.15]

[Ltsetting5.16] characteristics:

• Single AID AMEX (full match) (Kernel Identifier with zero length)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A000000025101001’ Directory Entry 1 o Label = ‘AMEX’ o Kernel Identifier = ‘’ o API = ‘01’

AID FCI 1 o AID = ‘A000000025101001’

o Label = ‘AMEX’ o API = ‘01’ o PDOL = ‘9F6604D708’

o Removal Timeout value = ‘0000’

Table C.133: [Ltsetting5.16]

[Ltsetting5.17] characteristics:

• Single AID DISCOVER (full match) (Kernel Identifier not present)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000001523010’ Directory Entry 1 o Label = ‘DISCOVER’ o API = ‘01’

AID FCI 1 o AID = ‘A0000001523010’

o Label = ‘DISCOVER’ o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.134: [Ltsetting5.17]

[Ltsetting5.18] characteristics:

• Single AID DISCOVER ‘A000000152301001’ (partial match) (Kernel Identifier with zero length)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A000000152301001’ Directory Entry 1 o Label = ‘DISCOVER’ o Kernel Identifier = ‘’ o API = ‘01’

AID FCI 1 o AID = ‘A000000152301001’

o Label = ‘DISCOVER’ o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.135: [Ltsetting5.18]

[Ltsetting5.19] characteristics:

• Single AID CUP (full match) (Kernel Identifier not present)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000003330101’ Directory Entry 1 o Label = ‘CUP’ o API = ‘01’

AID FCI 1 o AID = ‘A0000003330101’

o Label = ‘CUP’ o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.136: [Ltsetting5.19]

[Ltsetting5.20] characteristics:

• Single AID CUP ‘A000000333010101’ (partial match) (Kernel Id with zero length)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A000000333010101’ Directory Entry 1 o Label = ‘CUP’ o Kernel Identifier = ‘’ o API = ‘01’

AID FCI 1 o AID = ‘A000000333010101’

o Label = ‘CUP’ o API = ‘01’ o PDOL = ‘9F6604D708’

o Removal Timeout value = ‘0000’

Table C.137: [Ltsetting5.20]

[Ltsetting5.21] characteristics:

• Single AID DISCOVER with full match on AID and Kernel Identifier = ’00’

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000001523010’ Directory Entry 1 o Label = ‘DISCOVER’ o Kernel Identifier = ‘00’ o API = ‘01’

AID FCI 1 o AID = ‘A0000001523010’

o Label = ‘DISCOVER’ o API = ‘01’ o PDOL = ‘9F6604D708’

o Removal Timeout value = ‘0000’

Table C.138: [Ltsetting5.21]

[Ltsetting5.22] characteristics:

• Single AID CUP with full match on AID and Kernel Identifier = ’00’

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000003330101’ Directory Entry 1 o Label = ‘CUP’ o Kernel Identifier = ‘00’ o API = ‘01’

AID FCI 1 o AID = ‘A0000003330101’

o Label = ‘CUP’ o API = ‘01’ o PDOL = ‘9F6604D708’

o Removal Timeout value = ‘0000’

Table C.139: [Ltsetting5.22]

[Ltsetting5.23] characteristics:

• Single AID DISCOVER (full match) (Kernel Identifier not present)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000003241010’ Directory Entry 1 o Label = ‘DISCOVER’ o API = ‘01’

AID FCI 1 o AID = ‘A0000003241010’

o Label = ‘DISCOVER’ o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.140: [Ltsetting5.23]

[Ltsetting5.24] characteristics:

• Single AID DISCOVER ‘A000000324101001’ (partial match) (Kernel Identifier with zero length)

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A000000324101001’ Directory Entry 1 o Label = ‘DISCOVER’ o Kernel Identifier = ‘’ o API = ‘01’

AID FCI 1 o AID = ‘A000000324101001’

o Label = ‘DISCOVER’ o API = ‘01’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.141: [Ltsetting5.24]

[Ltsetting5.25] characteristics:

• Single AID DISCOVER with full match on AID and Kernel Identifier = ’00’

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000003241010’ Directory Entry 1 o Label = ‘DISCOVER’ o Kernel Identifier = ‘00’ o API = ‘01’

AID FCI 1 o AID = ‘A0000003241010’

o Label = ‘DISCOVER’ o API = ‘01’ o PDOL = ‘9F6604D708’

o Removal Timeout value = ‘0000’

Table C.142: [Ltsetting5.25]

[Ltsetting6.X]: format error, response error, no response [Ltsetting6.1] characteristics:

• Select PPSE response without data and Status word: 6A82

[Ltsetting6.2] characteristics:

• Select PPSE response with data and Status word: 6283

[Ltsetting6.3] characteristics:

• Select PPSE response without any Template 61 present

[Ltsetting6.4] characteristics:

• Select PPSE response with 2 templates 61 wrongly coded on ADF name (ADF name on 4 bytes and ADF name on 17 bytes

Data Value

PPSE o AID = ‘A0000000’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

PPSE o AID = ‘A00000000400040102030405060708090A’ Directory Entry 2 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘02’

Table C.143: [Ltsetting6.4]

[Ltsetting6.5] characteristics:

• Select PPSE response with 3 templates 61 (AID 1 with the highest priority wrongly coded on 17 bytes, AID 2 with the highest priority wrongly coded on 4 bytes, and AID 3 (APP1) with the lowest priority correctly coded on ADF name

Data Value

PPSE o AID = ‘A00000000400040102030405060708090A’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24

o API = ‘01’

PPSE o AID = ‘A0000000’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘02’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = ‘00’

o API = ‘03’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘03’ o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.144: [Ltsetting6.5]

[Ltsetting6.6] characteristics:

• Select PPSE response with 4 templates 61 (3 templates with the highest priority and a AID value not matching with reader combination and the last one (lowest priority) with a correct AID value)

AID Kernel ID Priority Comment

A0000000661010 21 1 Aid not match

A000000005 22 1 Aid not match

A000000006101001 22 1 Aid not match

A0000000020002 22 2 AID match

• PDOL with TTQ, kernel ID • GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000661010’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 21 o API = ‘01’

PPSE o AID = ‘A000000005’ Directory Entry 2 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

PPSE o AID = ‘A000000006101001’ Directory Entry 3 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

PPSE o AID = ‘A0000000020002’ Directory Entry 4 o Label = ‘APP2’ o Kernel Identifier = 22

o API = ‘02’

AID FCI 4 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘02’

o PDOL = ‘9F660D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.145: [Ltsetting6.6]

[Ltsetting6.7] characteristics:

• Select PPSE response with 3 templates 61 (2 templates with the highest priority and a wrong kernel ID length and the last one (lowest priority) with a correct kernel ID value

AID Kernel ID Priority

A00000000200020101 ‘80’: Byte 1 bit 8-7 = 10b and 1 length = 1 (wrong length)

A0000000010001 ‘C001’: Byte 1 bit 8-7 = 11b and 1 length = 2 (wrong length)

A0000000040004 24 2

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A000000002000201’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = ‘80’ o API = ‘01’

PPSE o AID = ‘A0000000010001’ Directory Entry 2 o Label = ‘APP1’ o Kernel Identifier = ‘C001’

o API = ‘01’

PPSE o AID = ‘A0000000040004’ Directory Entry 3 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘02’

AID FCI 3 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘02’

o PDOL = ‘9F6604D708’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.146: [Ltsetting6.7]

[Ltsetting6.8] characteristics:

• Select PPSE response with several templates 61 (Select AID of the two highest priority responds with Status word different from 9000 and the last one (lowest priority) with a correct Select AID response

AID Kernel ID Select AID Response Priority

A00000000200020101 22 6283 (with FCI) 2

A0000000040004 24 9000 4

A0000000010001 23 9000 (with FCI) 3

A0000000030003 21 6A82 (without FCI) 1

• PDOL with TTQ, kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A00000000200020101’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘02’

PPSE o AID = ‘A0000000040004’ Directory Entry 2 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘04’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘03’

PPSE o AID = ‘A0000000030003’ Directory Entry 4 o Label = ‘APP3’

o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A000000002000201’

o Label = ‘APP2’

o API = ‘02’

o PDOL = ‘9F6604D708’

o SW = ‘6283’

AID FCI 2 o SW = ‘9000’

AID FCI 3 o AID = ‘A0000000010001’ o Label = ‘APP1’

o API = ‘03’ o PDOL = ‘9F6604D708’

AID FCI 4 o SW = ‘6A82’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.147: [Ltsetting6.8]

[Ltsetting6.9] characteristics:

• Select PPSE response one templates 61 (Select AID does not respond (timeout)

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22

o API = ‘01’

AID FCI 1 o No response (timeout)

Table C.148: [Ltsetting6.9]

[Ltsetting6.10] characteristics:

• Select PPSE response with several templates 61 (RFU bits of the priority indicator set, RFU bits set on Kernel Identifier)

AID Kernel ID Priority

A0000000020002 ‘24FFFF’ F2

A0000000040004 ‘240000’ 4

A0000000010001 ‘23FF00FF00FF00FF’ FF

A0000000030003 ‘2102030405060708’ 41

• PDOL with kernel ID, and TTQ

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = ‘24FFFF’ o API = ‘F2’

PPSE o AID = ‘A0000000040004’ Directory Entry 2 o Label = ‘APP4’ o Kernel Identifier = ‘240000’

o API = ‘04’

PPSE o AID = ‘A0000000010001’ Directory Entry 3 o Label = ‘APP1’ o Kernel Identifier = ‘23FF00FF00FF00FF’ o API = ‘FF’

PPSE o AID = ‘A0000000030003’ Directory Entry 4 o Label = ‘APP3’ o Kernel Identifier = ‘2102030405060708’

o API = ‘41’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘F2’

o PDOL = ‘9F6604D708’

AID FCI 2 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘04’

o PDOL = ‘9F6604D708’

AID FCI 3 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘FF’ o PDOL = ‘9F6604D708’

AID FCI 4 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘41’ o PDOL = ‘9F6604D708’

o Removal Timeout value = ‘0000’

Table C.149: [Ltsetting6.10]

[Ltsetting6.11] characteristics

• Single AID APP1 (with associated Kernel ID = 23)

• Select response with presence of Amount Authorized (tag 9F02, value = ’102030405060’, Amount Other (tag 9F03 value ‘010203040506’, Unpredictable Number (tag 9F37, value ‘11223344’ and unknown tag (DF01 with a value ‘FF’), Unknown tag (C1, value EE‘EE’), Unknown tag (85, value ‘DD’), Unknown tag (9F25, value ‘CCCC’)

• PDOL with Amount Authorized, Amount Other, Unpredictable Number, DF01, C1, 85, 9F25

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”), Field Off Request = NA

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’ o Label = ‘APP1’ o API = ‘01’

o PDOL = ‘9F66049F02069F03069F3704DF0101C10285019F2502’

o Amount Autorized (tag 9F02) = ‘102030405060’ o Amount Other (tag 9F03) = ‘010203040506’ o Unpredictable number (tag 9F37) = ‘11223344’ o Unknown tag (DF01) = ‘FF’ o Unknown tag (C1)n = ‘EE‘EE’

o Unknown tag (85) = ‘DD’ o Unknown tag (9F25) = ‘CCCC’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.150: [Ltsetting6.11]

[Ltsetting6.12] characteristics

• Single AID APP2 (with associated Kernel ID = 22)

• PPSE Select response with a single padding byte ‘00’ in template 6F and A5

• ADF Select response with single padding byte ‘00’ in template 6F and A5

• PDOL with: ‘Amount Authorized (tag 9F02) with length = 7, Unpredictable Number (tag 9F37) with length = 5, Merchant Identifier (tag 9F16) with length = 16, Terminal Identification (tag 9F1C) with length=9

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE 6F o Padding byte ‘00’ before template A5 template

PPSE A5 o Padding byte ‘00’ before and after template BF0C template

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’ o Padding byte ‘00’ before template A5 o Label = ‘APP2’

o API = ‘01’ o Padding byte ‘00’ before and after tag API o PDOL = ‘9F02079F37059F16109F1C09’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’

o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.151: [Ltsetting6.12]

[Ltsetting6.13] characteristics

• Single AID APP4 (with associated Kernel ID = 24)

• PPSE Select response with 10 padding bytes ‘00’ in template 6F and A5

• ADF Select response with 10 padding bytes ‘00’ in template 6F and A5

• PDOL with: ‘Amount Authorized (tag 9F02) with length = 16, Unpredictable Number (tag 9F37) with length = 14, Merchant Identifier (tag 9F16) with length = 25, Terminal Identification (tag 9F1C) with length=18

• GPO Response indicates:

o the Final Outcome ‘Approved’ UI Request on Outcome=Yes

Data Value

PPSE 6F o Padding byte ‘00000000000000000000’ before template A5 template

PPSE A5 o Padding byte ‘00000000000000000000’ before and after template template BF0C

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’ o Padding byte ‘00000000000000000000’ before template A5 o Label = ‘APP4’

o API = ‘01’ o Padding byte ‘00000000000000000000’ before and after tag API

o PDOL = ‘9F02109F370E9F16199F1C12’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’

o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.152: [Ltsetting6.13]

[Ltsetting6.14] characteristics

• Single AID APP3 (with associated Kernel ID= 21)

• PPSE Select response with tag 84 after template A5

• ADF Select response with tag 84 after template A5 and standard tag order inverted in template A5

• PDOL with: ‘Amount Authorized (tag 9F02)

• GPO Response indicates:

o The Final Outcome ‘Approved’ UI Request on Outcome = Yes

Data Value

PPSE 6F o Template A5 template o Tag 84

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID 6F o Template A5 template o Tag 84 = ‘A0000000030003’

AID A5 o PDOL = ‘9F0206’ template o API = ‘01’ o Application Label = ‘APP3’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.153: [Ltsetting6.14]

[Ltsetting6.15] characteristics:

• Select PPSE response with 2 templates 61 wrongly coded on ADF name (ADF name missing)

Data Value

PPSE o Label = ‘APP1’ Directory Entry 1 o Kernel Identifier = 23 o API = ‘01’

PPSE o Label = ‘APP4’ Directory Entry 2 o Kernel Identifier = 24 o API = ‘02’

Table C.154: [Ltsetting6.15]

[Ltsetting6.16] characteristics:

• Select PPSE response with 2 templates 61 (entry 1 with AID missing with the highest priority and entry 2 with AID 2 (APP1) with the lowest priority correctly coded on ADF name)

Data Value

PPSE o Label = ‘APP4’ Directory Entry 1 o Kernel Identifier = 24 o API = ‘01’

PPSE o AID = ‘A0000000010001’ Directory Entry 2 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘02’

AID FCI 2 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘02’ o PDOL = ‘D1029F66049F02069F03069C019F3704D708’

o Removal Timeout value = ‘0000’

Table C.155: [Ltsetting6.16]

[Ltsetting6.17] characteristics:

• Select PPSE response with several templates 61 (Select AID of the highest priority responds with Status word different from 9000 and the last one (lowest priority) with a correct Select AID response

AID Kernel ID Select AID Response Priority

A0000000030003 22 9000 (with FCI) 2

A0000000030003 21 6A82 (without FCI) 1

• PDOL kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 22 o API = ‘02’

PPSE o AID = ‘A0000000030003’ Directory Entry 2 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’

o Label = ‘APP3’ o API = ‘02’ o PDOL = ‘D708’

AID FCI 2 o SW = ‘6A82’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.156: [Ltsetting6.17]

[Ltsetting6.18] characteristics:

AID Kernel ID Select AID Response Priority

A0000000040004 25 9000 (with FCI) 2

A0000000030003 25 6A82 (without FCI) 1

• PDOL kernel ID

• GPO Response indicates the Final Outcome ‘Approved’

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 25 o API = ‘02’

PPSE o AID = ‘A0000000030003’ Directory Entry 2 o Label = ‘APP3’ o Kernel Identifier = 25 o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘02’

o PDOL = ‘D708’

AID FCI 2 o SW = ‘6A82’

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’ o CVM value = ‘00’

o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

Table C.157: [Ltsetting6.18]

[Ltsetting6.20] characteristics:

• Single AID APP2 (with associated Kernel ID= 22)

• PDOL with Pre-Processing indicator, start Point

• When Restart=0, GPO Response indicates

o the Final Outcome ‘online request’

o start B o Online Response Data: EMV data (Issuer data 91)

o CVM:NA

o UI Request on Outcome Present: No o UI Request on Restart Present: No o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA

o Receipt: No o Field Off Request: NA o Removal Timeout: 10s • SELECT AID response on restart indicates a Status Word 6282 with no data

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22

o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’

o Label = ‘APP2’ o API = ‘01’ o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0B’ o Online Response Data = ‘01’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0064’

Online o Tag 91 = ’0102030405060708090A0B0C0D0E0F10’ Response 1 GPO response

Table C.159: [Ltsetting6.20]

[Ltsetting6.21] characteristics:

• Single AID APP3 (with associated Kernel ID=21)

• When Restart=0, GPO Response indicates

o the Final Outcome ‘online request’ o start C

o Online Response Data: any

o CVM: NA o UI Request on Outcome Present: No

o UI Request on Restart Present: No

o Data Record Present: No o Discretionary Data Present: No o Alternate Interface Preference: NA o Receipt: No

o Field Off Request: NA o Removal Timeout: 0 • SELECT AID response on restart indicates a Status Word 6A83 with no data

Data Value

PPSE o AID = ‘A0000000030003’ Directory Entry 1 o Label = ‘APP3’ o Kernel Identifier = 21 o API = ‘01’

AID FCI 1 o AID = ‘A0000000030003’ o Label = ‘APP3’

o API = ‘01’ o PDOL = ‘D102D201’

Outcome 1 o Outcome Value = ’05’ GPO response o Start value = ‘0C’ o Online Response Data = ‘02’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’

o Receipt value = ‘00’

o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

Table C.160: [Ltsetting6.21]

[Ltsetting7.X] characteristics: default Language preference [Ltsetting7.00] characteristics:

• Single AID APP1 (with associated Kernel ID = 23, Language Preference = unsupported Language 1 (not present in ICS))

• PDOL with TTQ

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”) and Language Preference = unsupported Language 1

o The Final Outcome ‘Approved’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23

o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘01’ o PDOL = ‘9F6604’ o Language Preference= unsupported Language 1

Outcome 1 o Outcome Value = ’03’ GPO response o Start value = ‘00’ o Online Response Data = ‘00’

o CVM value = ‘00’ o Alternate Interface Preference value = ‘00’ o Receipt value = ‘00’ o Field Off Request value = ‘FFFF’

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value =unsupported Language 1

o Value Qualifier value = ‘00’

o Value = ‘000000000000’ o Currency Code = ‘0000’

Table C.162: [Ltsetting7.00]

[Ltsetting7.01] characteristics:

• Single AID APP4 (with associated Kernel ID = 24, Language Preference = Unsupported Language 2 (not present in ICS))

• 1st GPO Response indicates:

o UI request: Message Identifier: ‘20’ (“See Phone for Instructions”) and Language preference = Unsupported Language 2

o The Final Outcome ‘Try Again’, UI Request on Outcome = Yes,

• 2nd GPO Response indicates:

o UI request: Message Identifier: ‘07’ (“Not Authorised”) and Language preference = Language 2

o The Final Outcome ‘Declined’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’

o Label = ‘APP4’ o API = ‘01’ o Language Preference= Unsupported Language 2

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’20’ on Outcome 1 GPO o Status value = ‘06’ response o Hold Time value = ‘0064’

o Language Preference value = Unsupported Language 2 o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’07’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’ o Language Preference value = Unsupported Language 2 o Value Qualifier value = ‘00’

o Value = ‘000000000000’ o Currency Code = ‘0000’

Table C.163: [Ltsetting7.01]

[Ltsetting7.x] characteristics:

• Single AID APP1 (with associated Kernel ID = 23, Language Preference = unsupported Language x (not present in ICS))

• PDOL with TTQ

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”) and Language Preference = Unsupported Language x

o The Final Outcome ‘Approved’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000010001’ Directory Entry 1 o Label = ‘APP1’ o Kernel Identifier = 23 o API = ‘01’

AID FCI 1 o AID = ‘A0000000010001’

o Label = ‘APP1’ o API = ‘01’ o PDOL = ‘9F6604’ o Language Preference= Unsupported Language x

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome

1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’

o Language Preference value = Unsupported Language x

o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

Table C.164: [Ltsetting7.x]

[Ltsetting7.x+1] characteristics:

• Single AID APP4 (with associated Kernel ID = 24, Language Preference = Unsupported Language x+1 (not present in ICS))

• 1st GPO Response indicates:

o UI request: Message Identifier: ‘20’ (“See Phone for Instructions”) and Language preference = Unsupported Language x+1

o The Final Outcome ‘Try Again’, UI Request on Outcome = Yes,

• 2nd GPO Response indicates:

o UI request: Message Identifier: ‘07’ (“Not Authorised”)

o The Final Outcome ‘Declined’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000040004’ Directory Entry 1 o Label = ‘APP4’ o Kernel Identifier = 24 o API = ‘01’

AID FCI 1 o AID = ‘A0000000040004’ o Label = ‘APP4’ o API = ‘01’

o Language Preference= Unsupported Language x+1

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’20’ on Outcome 1 GPO o Status value = ‘06’ response o Hold Time value = ‘0032’

o Language Preference value = Unsupported Language x+1 o Value Qualifier value = ‘00’

o Value = ‘000000000000’

o Currency Code = ‘0000’

o Field Off Request value = ‘FFFF’ o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’07’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’ o Language Preference value = Unsupported Language x+1 o Value Qualifier value = ‘00’

o Value = ‘000000000000’ o Currency Code = ‘0000’

Table C.165: [Ltsetting7.x+1]

[Ltsetting8.x] characteristics: Currency Code [Ltsetting8.n] characteristics:

• Single AID APP2 (with associated Kernel ID = 22)

• GPO Response indicates:

o UI request: Message Identifier: ‘03’ (“Approved”), Value Qualifier = ’Balance’, currency Code (n) (present in ICS) and integer value = 1234

o The Final Outcome ‘Approved (with balance)’, UI Request on Outcome = Yes,

Data Value

PPSE o AID = ‘A0000000020002’ Directory Entry 1 o Label = ‘APP2’ o Kernel Identifier = 22 o API = ‘01’

AID FCI 1 o AID = ‘A0000000020002’ o Label = ‘APP2’ o API = ‘01’

o Removal Timeout value = ‘0000’

UI Request o Message ID value = ’03’ on Outcome 1 GPO o Status value = ‘05’ response o Hold Time value = ‘0032’ o Language Preference value = ‘0000’

o Value Qualifier value = ‘02’ o Value = ‘000000123400’

o Currency Code = CURR n (ICS)

Table C.166: [Ltsetting8.n]

[Ltsetting9.n]: Single AID supported with C-n kernels [Ltsetting9.1] characteristics (card type A or B):

• Single AID JCB (with associated Kernel ID = TK1 Kernel ID)

Contact Specific Data Application Default Action 5600 (ADA) Application File Locator - Application Identifier - Application Interchange 7C00 Profile Card Action Analysis Support 7F4E80 Information (CAASI) Card Action Code (CAC) - 000000000000000002011E031F03 Cardholder Verification Online Enciphered PIN for ATM Method List (CVM List) Signature No CVM Card Risk Management Data 9F02069F03069F1A0295055F2A029A039C019F37049F35019F5C029F150 Object List 1 (CDOL1) 29F5201 Card Risk Management Data 8A029F02069F03069F1A0295055F2A029A039C019F3704 Object List 2 (CDOL2) Cumulative Total Transaction 000000000000 Amount Limit Cumulative Total Transaction 000000000000 Amount Upper Limit Dynamic Data Authentication 9F37049F1C089F1A029A03 Data Object List (DDOL) 6F218407A0000000651010A516500A4A4342204372656469748701015F2D File Control Information (FCI) 047A68656E

File Control Information(PSE) - Issuer Action Code (IAC) 0010000000 Denial Issuer Action Code (IAC) F8488CF800 Online Issuer Action Code (IAC) F8408C2800 Default Issuer Authentication 00 Indicator Issuer Payment Type - Issuer Payment Type Online - Request JIS 2 Equivalent Data - Lower Consecutive Domestic 00 Offline Limit Lower Consecutive 00 International Offline Limit Lower Consecutive Offline 00 Limit

Maximum Domestic Offline 000000000000 Transaction Amount PIN Try Limit - Reference PIN Data - Service Code 0201 Specified Category - Transaction Amount Limit Specified Category - Transaction Counter Limit Specified Goods Code List - Specified Merchant Category - Code List Static Data Authentication 82 (SDA) Tag List Track 1 Discretionary Data 303030303030303030303030303030303030303030303030 Transaction Currency - Conversion Table Upper Consecutive Domestic FF Offline Limit Upper Consecutive FF International Offline Limit Upper Consecutive Offline FF Limit Application Currency Code 0901 Application Effective Date - Application Expiration Date 151231 Application PAN 3569990010082211 Application PAN Seq Number 00 Application Usage Control FFC0 Application Version Number 0200 CA Public Key Index 11

Cardholder Name 4A43422F54455354202020202020202020202020202020202020 Cryptogram Version Number 01 (CVN) Issuer Country Code 0158

Track 2 Equivalent Data 3569990010082211D15122010000000000000F Derivation Key Index (DKI) No Shared Derivation Key Index (DKI) 01 Value(Contact) Derivation Key Index (DKI) 02 Value(Contactless) Issuer Public Key Shared No Issuer Public Key Certificate 204912 Expiration Date (Contact) Issuer Public Key Length 1152 (Contact) Issuer Public Key Exponent 03 (Contact)

Issuer Public Key Certificate 204912 Expiration Date (Contactless) Issuer Public Key Length 1152 (Contactless) Issuer Public Key Exponent 03 (Contactless) ICC Public Key Shared No ICC Public Key Certificate 204912 Expiration Date (Contact) ICC Public Key Length 768 (Contact) ICC Public Key Exponent 03 (Contact) ICC Public Key Certificate 204912 Expiration Date (Contactless) ICC Public Key Length 1024 (Contactless) ICC Public Key Exponent 03 (Contactless) Contactless Specific Data Card Contactless Floor Limit 000000030000 Application Interchange 3800 Profile Application File Locator – CL

Offline Application File Locator – CL

Online Card Action Analysis Support C10038 Information (CAASI) Card Risk Management Data 9F02069F03069F1A0295055F2A029A039C019F3704 Object List 1 (CDOL1) 00000000000000001E0302031F00 Cardholder Verification Online Enciphered PIN for ATM Method List (CVM List) Signature No CVM Dynamic Data Authentication 9F3704 Data Object List (DDOL) 6F308407A0000000651010A525500A4A4342204372656469748701019F38 File Control Information (FCI) 0C9F1A029F7A019F02065F2A025F2D047A68656E

File Control 6F2F840E325041592E5359532E4444463031A51DBF0C1A61184F07A0000 Information(PPSE) 000651010500A4A434220437265646974870101

VLP Funds Limit 900000000000 VLP Issuer Authentication 4A4342313233 Code

[Ltsetting9.2x] characteristics (card type A or B):

[Ltsetting9.21] characteristics (card type A):

• Single AID MasterCard (with associated Kernel ID = TK2)

• MagStripe Mobile “with On device cardholder verification is supported”

• The following table provides with values for data critical to the tests using this Ltsetting. Missing data and values must be defined by the tool vendor following the Kernel C-2 specification to simulate a valid card.

Data Value

PPSE o AID = ‘A0000000041010’ Directory Entry o Label = ‘MASTERCARD’ o Kernel Identifier = TK2 Kernel ID

o API = ‘01’

AID FCI o AID = ‘A0000000041010’

o Label = ‘MASTERCARD’ o API = ‘01’ o PDOL = ‘9F4005’

o Other Data as per specification

GPO o AIP = ’0200’ response (Format 2) o AFL = ‘08010100’

ReadRecor Only SFI 1 Record 1 d responses o 9F6C 02 0001 o 9F62 06 000000380000 o 9F63 06 00000000E0E0 o 56 34 42353431333333393030303030313531335E202F5E313231 3232303133333030303333333030303232323232303030313 1313130

o 9F64 01 03 o 9F65 02 000E o 9F66 02 0E70 o 9F6B 13 5413339000001513D12122019000990000000F

o 9F67 01 03

CCC o Consistent with the Kernel C-2 compatible cardholder product responses indicating a successful mobile transaction

Table C.167: [Ltsetting9.21]

[Ltsetting9.22] characteristics (card type A):

• Single AID MasterCard (with associated Kernel ID = TK2 Kernel ID by default)

• M/Chip card supporting Torn Transaction recovery

Data Value

PPSE o AID = ‘A0000000041010’ Directory Entry o Label = ‘MASTERCARD’ o API = ‘01’

AID FCI o AID = ‘A0000000041010’ o Label = ‘MASTERCARD’

o API = ‘01’ o PDOL = ‘9F4005’ o Other Data as per specification

GPO o AIP = ’5980’ response (Format 2) o AFL consistent

ReadRecor In record(s) different from SFI 1 Record 1 d responses o 9F51 03 9F3704 o 5A 08 5413339000001513

o 5F34 01 02 All other data must be consistent and compliant with a card to allow successful transactions with the Kernel C-2 under test

RSA Keys o CA Key Length 144 bytes and Exponent 3

o ISS Key Length 144 bytes and Exponent 3

o ICC Key Length 96 bytes and Exponent 3

Other o Consistent with the Kernel C-2 compatible cardholder product commands when successfully performing a payment transaction responses

Table C.168: [Ltsetting9.22]

[Ltsetting9.23] characteristics (card type A):

• Single AID MasterCard (with associated Kernel ID = TK2 Kernel ID)

• Second M/Chip card supporting Torn Transaction recovery

Data Value

PPSE o AID = ‘A0000000041010’ Directory Entry o Label = ‘MASTERCARD’ o Kernel Identifier = TK2 Kernel ID o API = ‘01’

AID FCI o AID = ‘A0000000041010’

o Label = ‘MASTERCARD’ o API = ‘01’ o PDOL = ‘9F4005’

o Other Data as per specification

GPO o AIP = ’5980’ response o AFL consistent (Format 2)

ReadRecor In record(s) different from SFI 1 Record 1 d responses o 9F51 03 9F3704

o 5A 08 5413339000001513

o 5F34 01 03

o AUC with byte 1 bit 8 set to ‘1’ and AUC with byte 2 bit 8 set to ‘1’

All other data must be consistent and compliant with a card to allow successful transactions with the Kernel C-2 under test

RSA Keys o CA Key Length 144 bytes and Exponent 3 o ISS Key Length 144 bytes and Exponent 3

o ICC Key Length 96 bytes and Exponent 3

Other o Consistent with the Kernel C-2 compatible cardholder product commands when successfully performing a payment transaction responses

Table C.169: [Ltsetting9.23]

[Ltsetting9.24] characteristics (card type A):

• Single AID MasterCard (with associated Kernel ID = TK2 Kernel ID)

• M/Chip Card triggering Data Exchange (DataStorage)

Data Value

PPSE o AID = ‘A0000000041010’ Directory Entry o Label = ‘MASTERCARD’ o Kernel Identifier = TK2 Kernel ID

o API = ‘01’

AID FCI o AID = ‘A0000000041010’

o Label = ‘MASTERCARD’ o API = ‘01’

o PDOL = ‘9F5C089F4005’

o Under BF0C - 9F5E0B5413339000001513010000 - 9F5D03010100

- 9F4D020B0A

o Other Data as per specification

GPO o AIP = ’5980’ response (Format 2) o AFL consistent o Need a data to engage data storage

o 9F5F = ‘C0’ (DS Slot Availability) o 9F7F = ‘18273645’ (DS Unpredictable Number) o 9F7D = ‘0000000000000000’ (DS Summary 1)

ReadRecor In record(s) different from SFI 1 Record 1 d responses o 9F51 03 9F3704 o 9F5B 0C DF6008DF6108DF6201DF63A0

All other data must be consistent and compliant with a card application compatible with Kernel C-2 and supporting IDS to allow successful transactions (Payment + IDS) with Kernel C-2 under test

RSA Keys o CA Key Length 144 bytes and Exponent 3

o ISS Key Length 144 bytes and Exponent 3 o ICC Key Length 96 bytes and Exponent 3

Other o Consistent with the Kernel C-2 compatible cardholder product commands when successfully performing a payment transaction with IDS responses

Table C.170: [Ltsetting9.24]

[Ltsetting9.25] characteristics (card type A):

• Single AID MasterCard (with associated Kernel ID = TK2)

• M/Chip Card requiring a large volume of transaction logging

Data Value

PPSE o AID = ‘A0000000041010’ Directory Entry o Label = ‘MASTERCARD’ o Kernel Identifier = TK2 Kernel ID o API = ‘01’

AID FCI o AID = ‘A0000000041010’

o Label = ‘MASTERCARD’ o API = ‘01’ o PDOL = ‘9F4005’ o Other Data as per specification

GPO o AIP = ’5980’ response (Format 2) o AFL consistent

ReadRecor In record(s) different from SFI 1 Record 1 d responses o 9F51 03 9F3704 o 5A 08 54133390000015135F34 01 03 o CA Public Key must be 248-byte CA key (index 6) provided in “Kernel C-2 Testing Environment (Terminal Products)”

o Length of Issuer Public Key is 247 bytes o Length of ICC Public Key is 238 bytes

o The personalization must be such that the Static Data to be Authenticated is 2048 byte long

All other data must be consistent and compliant with a card application compatible with Kernel C-2 to allow a successful transaction

RSA Keys o CA Key Length 144 bytes and Exponent 3

o ISS Key Length 144 bytes and Exponent 3

o ICC Key Length 96 bytes and Exponent 3

Other o Consistent with the Kernel C-2 compatible cardholder product commands when successfully performing a payment transaction responses

Table C.171: [Ltsetting9.25]

[Ltsetting9.26] characteristics (card type A):

• Single AID MasterCard (with associated Kernel ID = TK2)

• M/Chip Mobile rejecting the first transaction attempt asking for an Offline PIN verification and approving the following transaction attempt considering the Offline PIN successful

Data Value

PPSE o AID = ‘A0000000041010’ Directory Entry o Label = ‘MASTERCARD’ o Kernel Identifier = TK2 Kernel ID o API = ‘01’

AID FCI o AID = ‘A0000000041010’

o Label = ‘MASTERCARD’ o API = ‘01’ o PDOL = ‘9F4005’

o Other Data as per specification

GPO o AIP = ’5B80’ response AFL consistent (Format 2)

ReadRecor In record(s) different SFI 1 Record 1 d responses o 5A 08 5413339000001513

o 5F34 01 02 All other data must be consistent and compliant with a card to allow successful transactions with the Kernel C-2 under test

RSA Keys o CA Key Length 144 bytes and Exponent 3

o ISS Key Length 144 bytes and Exponent 3 o ICC Key Length 96 bytes and Exponent 3

CCC Two behaviors

o 1st Transaction attempt rejected with POS Cardholder Interaction Information DF4B 03 000100

o 2nd Transaction attempt approved with POS Cardholder Interaction Information DF4B 03 001000

1st Generate Two behaviors AC o 1st Transaction attempt rejected with POS Cardholder Interaction Information DF4B 03 000100

o 2nd Transaction attempt approved

Other o Consistent with the Kernel C-2 compatible cardholder product commands when successfully performing a payment transaction responses

Table C.172: [Ltsetting9.26]

[Ltsetting9.27] characteristics (card type B):

• Identical to [Ltsetting9.21] but using Type B.

[Ltsetting9.3] characteristics (card type A or B):

• Single AID A0000000031010 data set provided by VISA.

[Ltsetting9.4x] characteristics (card type A or B): [Ltsetting9.41] characteristics:

• Single AID A00000002501 on an AXP Dual Card: Dual interface – Supports contact & contactless interfaces. Contactless interface supports both EMV & MSD mode transactions.

• Sample physical Cards provided by AXP for test purposes.

[Ltsetting9.42] characteristics:

• Single AID A00000002501 on a AMEX MSD only Card: MSD only – Supports contactless interface only. Contactless interface supports MSD mode only.

• Sample physical Cards provided by AXP for test purposes.

[Ltsetting9.43] characteristics:

• Single AID A00000002501 on an AXP Dual Card: Dual interface – Supports contact & contactless interfaces. Contactless interface supports both EMV & MSD mode transactions.

• Sample physical Cards provided by AXP for test purposes.

[Ltsetting9.44] characteristics:

• Single AID A00000002501 on a AMEX MSD only Card: MSD only – Supports contactless interface only. Contactless interface supports MSD mode only.

• Sample physical Cards provided by AXP for test purposes.

[Ltsetting9.5] characteristics (card type A or B):

• Single AID B0000000011010 data set provided by JCB.

[Ltsetting9.6] characteristics (card type A or B):

• Single AID B0000000021010 data set provided by MasterCard. Rest of the data are identical to [Ltsetting9.23].

[Ltsetting9.7] characteristics (card type A or B):

• Single AID B0000000031010 data set provided by VISA

[Ltsetting9.8] characteristics (card type A or B):

• Single AID B0000000041010 on an AXP Dual Card: Dual interface – Supports contact & contactless interfaces. Contactless interface supports both EMV & MSD mode transactions.

• Sample physical Cards provided by AXP for test purposes.

[Ltsetting9.91] characteristics (card type A or B):

• Single AID JCB (with associated Kernel ID = TK5 Kernel ID)

[Ltsetting9.92] characteristics (card type A or B):

• Single AID B0000000651010 data set provided by JCB.

[Ltsetting9.93] characteristics:

• Single AID JCB on a Magstripe mode only.

[Ltsetting9.94] characteristics:

• Single AID JCB on a Legacy mode only.

[Ltsetting9.100] characteristics:

• Single AID Discover A0000001523010.

• Sample physical Cards provided by DFS for test purposes

[Ltsetting9.101] characteristics (card type A or B):

• Single AID Discover (with associated Kernel ID = TK6 Kernel ID)

[Ltsetting9.102] characteristics (card type A or B):

• Single AID B0000001523010 data set provided by Discover.

[Ltsetting9.103] characteristics:

• Single AID Discover A0000003241010.

• Sample physical Cards provided by DFS for test purposes

[Ltsetting9.104] characteristics:

• Same as [LTsetting9.100] but supporting MS mode only.

[Ltsetting9.200] characteristics:

• Single AID Union Pay.

• Sample physical Cards provided by CUP for test purposes

[Ltsetting9.201] characteristics (card type A or B):

• Single AID CUP A0000003330101 (with associated Kernel ID = TK7 Kernel ID)

[Ltsetting9.202] characteristics (card type A or B):

• Single AID B0000003330101data set provided by Union Pay.

[Ltsetting10.x]: Single AID supported with C-REGX kernel [Ltsetting10.x] characteristics (card type A or B):

• Single AID (not AXP, JCB, MasterCard or VISA AID) with associated Kernel ID = x

Annex D: Test cases applicable depending on the terminal options

Test case (with subcase) Terminal Configuration Setting

2EA_001_00_01 [All] [Termsetting2] with [Ltsetting1.1]

2EA_001_00_02 [All] [Termsetting2] with [Ltsetting1.2].

2EA_001_00_03 [All] [Termsetting2] with [Ltsetting1.97].

2EA_004_00_01 [All] [Termsetting2] with [Ltsetting1.1]

2EA_004_00_02 [All] [Termsetting3] with [Ltsetting1.1]

2EA_005_00_00 [All] [Termsetting2] with [Ltsetting1.2]

2EA_005_01_00 [All] [Termsetting2] with [Ltsetting1.2]

[Termsetting2] with [Ltsetting1.2], 2EA_007_00_01 [All] [LTsetting1.1] and [LTsetting2.40]

[Termsetting3] with [Ltsetting1.2] , 2EA_007_00_02 [All] [LTsetting1.1] and [LTsetting2.40]

2EA_011_00_01 [All] [Termsetting1] with [Ltsetting1.60]

2EA_011_00_02 [All] [Termsetting1] with [Ltsetting1.61]

2EA_011_00_03 [All] [Termsetting1] with [Ltsetting1.62]

2EA_014_00_02 [All] [Termsetting1] with [Ltsetting1.11]

2EA_014_00_03 [All] [Termsetting1] with [Ltsetting1.22]

2EA_014_00_04 [All] [Termsetting1] with [Ltsetting1.13]

2EA_014_00_05 [All] [Termsetting1] with [Ltsetting1.27]

2EA_014_00_06 [All] [Termsetting1] with [Ltsetting1.99]

2EA_014_01_02 [All] [Termsetting1] with [Ltsetting1.35]

2EA_015_00_02 [All] [Termsetting1] with [Ltsetting1.18]

2EA_015_00_03 [All] [Termsetting1] with [Ltsetting1.28]

2EA_015_00_04 [All] [Termsetting1] with [Ltsetting1.24]

2EA_016_00_01 [All] [Termsetting1] with [Ltsetting1.10]

2EA_016_00_02 [All] [Termsetting1] with [Ltsetting1.21]

2EA_016_00_03 [All] [Termsetting1] with [Ltsetting1.7]

2EA_016_00_04 [All] [Termsetting1] with [Ltsetting1.23]

2EA_016_00_06 [All] [Termsetting1] with [Ltsetting1.25]

2EA_016_00_07 [All] [Termsetting1] with [Ltsetting1.8]

2EA_016_00_08 [All] [Termsetting1] with [Ltsetting1.29]

2EA_017_00_01 [All] [Termsetting3] with [Ltsetting6.10]

2EA_017_00_02 [All] [Termsetting2] with [Ltsetting6.10]

2EA_017_00_03 [All] [Termsetting8] with [Ltsetting6.10]

2EA_017_01_00 [All] [Termsetting1] with [Ltsetting2.10]

2EA_018_00_00 [All] [Termsetting1] with [Ltsetting6.11]

2EA_019_00_01 [All] [Termsetting1] with [Ltsetting1.5]

2EA_019_00_02 [All] [Termsetting1] with [Ltsetting1.6]

2EA_019_00_03 [All] [Termsetting1] with [Ltsetting1.14]

2EA_019_00_04 [All] [Termsetting1] with [Ltsetting1.13]

2EA_020_00_01 [All] [Termsetting1] with [Ltsetting6.12]

2EA_020_00_02 [All] [Termsetting1] with [Ltsetting6.13]

2EA_021_00_00 [All] [Termsetting1] with [Ltsetting6.14]

2EA_022_00_00 [All] Any

2EB_001_00_01 [All] [Termsetting1] with [Ltsetting1.1]

2EB_001_00_02 [All] [Termsetting1] with [Ltsetting1.2]

2EB_001_00_03 [All] [Termsetting1] with [Ltsetting1.3]

2EB_001_00_04 [All] [Termsetting1] with [Ltsetting1.4]

2EB_001_00_05 [All] [Termsetting1] with [Ltsetting1.97]

2EB_002_00_01 [All] [Termsetting1] with [Ltsetting1.2]

2EB_002_00_02 [All] [Termsetting2] with [Ltsetting1.1]

2EB_002_00_03 [All] [Termsetting2] with [Ltsetting1.4]

2EB_007_00_01 [All] [Termsetting2] with [Ltsetting2.42]

2EB_007_00_02 [All] [Termsetting2] with [Ltsetting2.42]

2EB_008_00_01 [All] [Termsetting1] with [Ltsetting1.1]

2EB_008_00_02 [All] [Termsetting1] with [Ltsetting1.1]

2EB_008_00_03 [All] [Termsetting1] with [Ltsetting1.97]

2EB_008_00_04 [All] [Termsetting1] with [Ltsetting1.97]

2EB_009_00_01 [All] [Termsetting2] with [Ltsetting1.2]

2EB_009_00_02 [All] [Termsetting2] with [Ltsetting1.2]

2EB_010_00_01 [All] [Termsetting2] with [Ltsetting2.6]

2EB_010_00_02 [All] [Termsetting2] with [Ltsetting2.6]

2EB_010_00_03 [All] [Termsetting2] with [Ltsetting2.6]

2EB_010_00_04 [All] [Termsetting2] with [Ltsetting2.43]

2EB_010_00_05 [All] [Termsetting2] with [Ltsetting2.43]

2EB_011_00_01 [All] [Termsetting1] with [Ltsetting1.3]

2EB_011_00_02 [All] [Termsetting2] with [Ltsetting1.3]

2EB_011_00_03 [All] [Termsetting2] with [Ltsetting1.1]

2EB_011_00_04 [All] [Termsetting2] with [Ltsetting1.89]

2EB_012_00_01 [All] [Termsetting2] with [Ltsetting1.2]

2EB_012_00_02 [All] [Termsetting2] with [Ltsetting1.97]

2EB_013_00_01 [All] [Termsetting1] with [Ltsetting1.2]

2EB_013_00_02 [All] [Termsetting2] with [Ltsetting1.3]

2EB_013_00_03 [All] [Termsetting2] with [Ltsetting1.2]

2EB_013_00_04 [All] [Termsetting1] with [Ltsetting1.97]

2EB_013_00_05 [All] [Termsetting2] with [Ltsetting1.3]

2EB_013_00_06 [All] [Termsetting2] with [Ltsetting1.4]

2EB_014_00_01 [All] [Termsetting1] with [Ltsetting1.4]

2EB_014_00_02 [All] [Termsetting2] with [Ltsetting1.92]

2EB_014_00_03 [All] [Termsetting2] with [Ltsetting1.4]

2EB_014_00_04 [All] [Termsetting2] with [Ltsetting1.92]

2EB_014_00_05 [All] [Termsetting2] with [Ltsetting1.97]

2EB_015_00_01 [All] [Termsetting2] with [Ltsetting1.1]

2EB_015_00_02 [All] [Termsetting2] with [Ltsetting2.1]

2EB_015_00_03 [All] [Termsetting2] with [Ltsetting1.1]

2EB_015_00_04 [All] [Termsetting2] with [Ltsetting2.1]

2EB_015_00_05 [All] [Termsetting2] with [Ltsetting1.100]

2EB_015_00_06 [All] [Termsetting2] with [Ltsetting1.100]

2EB_016_00_00 [All] [Termsetting2] with [Ltsetting1.2]

2EB_017_00_01 [All] [Termsetting1] with [Ltsetting1.1]

2EB_017_00_02 [All] [Termsetting2] with [Ltsetting1.2]

2EB_017_00_03 [All] [Termsetting2] with [Ltsetting1.4]

2EB_017_00_04 [All] [Termsetting2] with [Ltsetting1.97]

2EB_018_00_01 [All] [Termsetting1] with [Ltsetting1.1]

2EB_018_00_02 [All] [Termsetting2] with [Ltsetting1.2]

2EB_018_00_03 [All] [Termsetting2] with [Ltsetting1.4]

2EB_018_00_04 [All] [Termsetting2] with [Ltsetting1.97]

2EB_019_00_00 [All] [Termsetting2] with [Ltsetting1.92]

2EB_020_00_01 [All] [Termsetting2] with [Ltsetting1.3]

2EB_020_00_02 [All] [Termsetting2] with [Ltsetting1.3]

2EB_021_00_01 [All] [Termsetting2] with [Ltsetting2.5]

2EB_021_00_02 [All] [Termsetting2] with [Ltsetting2.5]

2EB_022_00_00 [All] [Termsetting1] with [Ltsetting2.5]

2EC_002_00_02 [All] [Termsetting1] with [Ltsetting1.19]

2EC_002_00_03 [All] [Termsetting1] with [Ltsetting1.12]

2EC_002_00_04 [All] [Termsetting1] with [Ltsetting1.9]

2EC_003_00_02 [All] [Termsetting1] with [Ltsetting1.26]

2EC_004_00_01 [All] [Termsetting1] with [Ltsetting1.1]

2EC_004_00_02 [All] [Termsetting3] with [Ltsetting1.2]

2EC_005_00_01 [All] [Termsetting1] with [Ltsetting1.1]

2EC_005_00_02 [All] [Termsetting1] with [Ltsetting1.2]

2EC_005_00_03 [All] [Termsetting3] with [Ltsetting1.1]

2EC_005_00_04 [All] [Termsetting3] with [Ltsetting1.2]

2EC_006_00_01 [All] [Termsetting1] with [Ltsetting1.1]

2EC_006_00_02 [All] [Termsetting1] with [Ltsetting1.2]

2EC_006_00_03 [All] [Termsetting3] with [Ltsetting1.1]

2EC_006_00_04 [All] [Termsetting3] with [Ltsetting1.2]

2EC_007_00_01 [All] [Termsetting1] with [Ltsetting1.1]

2EC_007_00_02 [All] [Termsetting1] with [Ltsetting1.2]

2EC_007_00_03 [All] [Termsetting3] with [Ltsetting1.1]

2EC_007_00_04 [All] [Termsetting3] with [Ltsetting1.2]

2ED_001_00_01 [All] [Termsetting1] with [Ltsetting2.10]

2ED_001_00_02 [All] [Termsetting3] with [Ltsetting2.7]

2ED_001_00_03 [All] [Termsetting1] with [Ltsetting2.17]

2ED_001_00_04 [All] [Termsetting1] with [Ltsetting2.8]

2ED_001_00_05 [All] [Termsetting3] with [Ltsetting2.9]

2ED_001_00_06 [All] [Termsetting1] with [Ltsetting2.18]

2ED_002_00_00 [All] [Termsetting1] with [Ltsetting2.19]

2ED_003_00_01 [All] [Termsetting1] with [Ltsetting1.1]

2ED_003_00_02 [All] [Termsetting3] with [Ltsetting1.1]

2ED_003_01_01 [All] [Termsetting1] with [Ltsetting1.50]

2ED_003_01_02 [All] [Termsetting1] with [Ltsetting1.51]

2ED_003_01_03 [All] [Termsetting1] with [Ltsetting1.52]

2ED_003_01_01 [All] [Termsetting1] with [Ltsetting1.110]

2ED_003_01_02 [All] [Termsetting1] with [Ltsetting1.111]

2ED_003_01_03 [All] [Termsetting1] with [Ltsetting1.112]

2ED_003_01_04 [All] [Termsetting1] with [Ltsetting1.113]

2ED_003_01_05 [All] [Termsetting1] with [Ltsetting1.114]

2ED_003_01_06 [All] [Termsetting1] with [Ltsetting1.115]

2ED_003_01_07 [All] [Termsetting1] with [Ltsetting1.116]

2ED_003_01_08 [All] [Termsetting1] with [Ltsetting1.117]

2ED_003_01_09 [All] [Termsetting1] with [Ltsetting1.118]

2ED_003_01_10 [All] [Termsetting1] with [Ltsetting1.119]

2ED_003_01_11 [All] [Termsetting1] with [Ltsetting1.120]

2ED_003_01_12 [All] [Termsetting1] with [Ltsetting1.121]

2ED_004_00_01 [All] [Termsetting1] with [Ltsetting6.1]

2ED_004_00_02 [All] [Termsetting3] with [Ltsetting6.2]

2ED_005_00_01 [All] [Termsetting1] with [Ltsetting6.3]

2ED_005_00_02 [All] [Termsetting3] with [Ltsetting6.3]

2ED_007_00_01 [All] [Termsetting1] with [Ltsetting6.5]

2ED_007_00_02 [All] [Termsetting3] with [Ltsetting6.5]

2ED_007_01_01 [All] [Termsetting1] with [Ltsetting6.16]

2ED_007_01_02 [All] [Termsetting3] with [Ltsetting6.16]

2ED_008_00_01 [All] [Termsetting1] with [Ltsetting6.6]

2ED_008_00_02 [All] [Termsetting3] with [Ltsetting6.6]

2ED_010_00_01 [All] [Termsetting1] with [Ltsetting6.7]

2ED_010_00_02 [All] [Termsetting3] with [Ltsetting6.7]

2ED_011_00_01 [All] [Termsetting1] with [Ltsetting4.1]

2ED_011_00_02 [All] [Termsetting2] with [Ltsetting4.2]

2ED_011_00_03 [All] [Termsetting3] with [Ltsetting4.3]

2ED_012_08_01 [All] [Termsetting13] with [Ltsetting1.93]

2ED_012_08_02 [All] [Termsetting13] with [Ltsetting1.94]

2ED_012_08_03 [All] [Termsetting13] with [Ltsetting1.95]

2ED_012_08_04 [All] [Termsetting13] with [Ltsetting1.95]

2ED_012_10_01 [All] [Termsetting1] with [Ltsetting1.1]

2ED_012_10_02 [All] [Termsetting1] with [Ltsetting1.2]

2ED_012_10_03 [All] [Termsetting1] with [Ltsetting1.3]

2ED_012_10_04 [All] [Termsetting1] with [Ltsetting1.4]

2ED_012_10_05 [All] [Termsetting1] with [Ltsetting1.84]

2ED_012_10_06 [All] [Termsetting1] with [Ltsetting1.85]

2ED_012_10_07 [All] [Termsetting1] with [Ltsetting1.86]

2ED_012_10_08 [All] [Termsetting1] with [Ltsetting1.87]

2ED_012_10_09 [All] [Termsetting1] with [Ltsetting1.88]

2ED_012_10_10 [All] [Termsetting1] with [Ltsetting1.97]

2ED_013_00_01 [All] [Termsetting3] with [Ltsetting2.20]

2ED_013_00_02 [All] [Termsetting2] with [Ltsetting2.20]

2ED_013_00_03 [All] [Termsetting3] with [Ltsetting2.20]

2ED_013_00_04 [All] [Termsetting3] with [Ltsetting2.21]

2ED_013_00_05 [All] [Termsetting2] with [Ltsetting2.21]

2ED_013_00_06 [All] [Termsetting3] with [Ltsetting3.1]

2ED_013_00_07 [All] [Termsetting2] with [Ltsetting3.1]

2ED_013_00_08 [All] [Termsetting1] with [Ltsetting2.24]

2ED_013_00_09 [All] [Termsetting1] with [Ltsetting3.4]

2ED_013_00_10 [All] [Termsetting2] with [Ltsetting2.44]

2ED_014_00_01 [All] [Termsetting3] with [Ltsetting2.22]

2ED_014_00_02 [All] [Termsetting2] with [Ltsetting2.22]

2ED_014_00_03 [All] [Termsetting3] with [Ltsetting3.2]

2ED_014_00_04 [All] [Termsetting2] with [Ltsetting3.2]

2ED_014_00_05 [All] [Termsetting2] with [Ltsetting3.6]

2ED_015_00_01 [All] [Termsetting3] with [Ltsetting2.23]

2ED_015_00_02 [All] [Termsetting2] with [Ltsetting2.23]

2ED_015_00_03 [All] [Termsetting3] with [Ltsetting3.3]

2ED_015_00_04 [All] [Termsetting2] with [Ltsetting3.3]

2ED_015_00_05 [All] [Termsetting2] with [Ltsetting3.7]

2ED_016_00_00 [All] [Termsetting2] with [Ltsetting4.2]

2ED_019_00_01 [All] [Termsetting3] with [Ltsetting6.8]

2ED_019_00_02 [All] [Termsetting2] with [Ltsetting6.8]

2ED_019_00_03 [All] [Termsetting3] with [Ltsetting6.17]

2ED_019_00_04 [All] [Termsetting2] with [Ltsetting6.18]

2ED_019_01_02 [All] [Termsetting1] with [Ltsetting6.20]

2ED_019_01_03 [All] [Termsetting1] with [Ltsetting6.21]

2ED_021_00_01 [All] [Termsetting6] with [Ltsetting2.30]

2ED_021_00_02 [All] [Termsetting7] with [Ltsetting2.31]

2ED_022_00_00 [All] [Termsetting1] with [Ltsetting6.9]

2EE_001_00_01 [All] [Termsetting1] with [Ltsetting1.32]

2EE_001_00_02 [All] [Termsetting3] with [Ltsetting1.33]

2EE_002_00_01 [All] [Termsetting2] with [Ltsetting1.1]

2EE_002_00_02 [All] [Termsetting2] with [Ltsetting1.4]

2EE_002_00_03 [All] [Termsetting3] with [Ltsetting2.10]

2EE_002_00_04 [All] [Termsetting2] with [Ltsetting2.10]

2EE_002_00_05 [All] [Termsetting2] with [Ltsetting1.97]

2EF_001_00_01 [All] [Termsetting2] with [Ltsetting1.1]

2EF_001_00_02 [All] [Termsetting2] with [Ltsetting1.40]

2EF_001_00_03 [All] [Termsetting2] with [Ltsetting1.41]

2EF_001_00_04 [All] [Termsetting2] with [Ltsetting1.42]

2EF_001_00_05 [All] [Termsetting2] with [Ltsetting1.46]

2EF_001_00_06 [All] [Termsetting2] with [Ltsetting1.47]

2EF_001_00_07 [All] [Termsetting2] with [Ltsetting1.48]

2EF_001_00_08 [All] [Termsetting2] with [Ltsetting2.40]

2EF_001_00_09 [All] [Termsetting2] with [Ltsetting1.49]

2EF_001_00_10 [All] [Termsetting2] with [Ltsetting1.35]

2EF_002_00_00 [All] [Termsetting1] with [Ltsetting1.43]

2EF_003_00_01 [All] [Termsetting2] with [Ltsetting2.40]

2EF_003_00_02 [All] [Termsetting3] with [Ltsetting2.40]

2EF_003_00_03 [All] [Termsetting3] with [Ltsetting2.41]

2EF_003_00_04 [All] [Termsetting2] with [Ltsetting2.45]

[Amount/Balance display] and [Value 2EA_013_00_01 Qualifier] [Termsetting1] with [Ltsetting1.80]

[Amount/Balance display] and [Value 2EA_013_00_02 Qualifier] [Termsetting1] with [Ltsetting1.81]

[Amount/Balance display] and [Value 2EA_013_00_03 Qualifier] [Termsetting1] with [Ltsetting1.82]

[Amount/Balance display] and [Value 2EA_013_01_00 Qualifier] [Termsetting1] with [Ltsetting8.n]

2EA_006_00_00 [Autorun] [Termsetting3] with [Ltsetting1.3]

2EA_006_01_00 [Autorun] [Termsetting3] with [Ltsetting1.3]

2EC_001_00_01 [Autorun] [Termsetting3] with [Ltsetting1.1]

2EC_001_00_02 [Autorun] [Termsetting3] with [Ltsetting1.2]

2EC_001_00_03 [Autorun] [Termsetting3] with [Ltsetting1.3]

2EC_001_00_04 [Autorun] [Termsetting3] with [Ltsetting1.4]

2EC_001_00_05 [Autorun] [Termsetting3] with [Ltsetting1.97]

2ED_020_00_01 [C-1] and [C-3] not supported [Termsetting2] with [Ltsetting2.30]

2ED_020_00_02 [C-1] and [C-3] not supported [Termsetting3] with [Ltsetting2.31]

2ED_009_02_01 [C-2] not supported [Termsetting3] with [Ltsetting5.2]

2ED_009_02_02 [C-2] not supported [Termsetting1] with [Ltsetting5.11]

2ED_009_12_00 [C-2] not supported [Termsetting3] with [Ltsetting5.14]

2ED_012_02_00 [C-2] not supported [Termsetting3] with [Ltsetting5.6]

2ED_009_03_01 [C-2] [Termsetting3] with [Ltsetting5.2]

2ED_009_03_02 [C-2] [Termsetting1] with [Ltsetting5.11]

2ED_009_13_00 [C-2] [Termsetting3] with [Ltsetting5.14]

2ED_012_03_00 [C-2] [Termsetting3] with [Ltsetting5.6]

2ED_009_00_00 [C-3] not supported [Termsetting1] with [Ltsetting5.1]

2ED_009_10_00 [C-3] not supported [Termsetting1] with [Ltsetting5.13]

2ED_012_00_00 [C-3] not supported [Termsetting2] with [Ltsetting5.5]

2ED_009_01_00 [C-3] [Termsetting1] with [Ltsetting5.1]

2ED_009_11_00 [C-3] [Termsetting1] with [Ltsetting5.13]

2ED_012_01_00 [C-3] [Termsetting2] with [Ltsetting5.5]

2ED_009_06_01 [C-4] not supported [Termsetting1] with [Ltsetting5.4]

2ED_009_06_02 [C-4] not supported [Termsetting1] with [Ltsetting5.10]

2ED_009_16_00 [C-4] not supported [Termsetting1] with [Ltsetting5.16]

2ED_012_06_01 [C-4] not supported [Termsetting3] with [Ltsetting5.8]

2ED_012_06_02 [C-4] not supported [Termsetting2] with [Ltsetting5.12]

2ED_009_07_01 [C-4] [Termsetting1] with [Ltsetting5.4]

2ED_009_07_02 [C-4] [Termsetting1] with [Ltsetting5.10]

2ED_009_17_00 [C-4] [Termsetting1] with [Ltsetting5.16]

2ED_012_07_01 [C-4] [Termsetting3] with [Ltsetting5.8]

2ED_012_07_02 [C-4] [Termsetting2] with [Ltsetting5.12]

2ED_009_04_00 [C-5] not supported [Termsetting3] with [Ltsetting5.3]

2ED_009_14_00 [C-5] not supported [Termsetting3] with [Ltsetting5.15]

2ED_012_04_00 [C-5] not supported [Termsetting2] with [Ltsetting5.7]

2ED_009_05_00 [C-5] [Termsetting3] with [Ltsetting5.3]

2ED_009_15_00 [C-5] [Termsetting3] with [Ltsetting5.15]

2ED_012_05_00 [C-5] [Termsetting2] with [Ltsetting5.7]

2ED_009_18_00 [C-6] not supported [Termsetting1] with [Ltsetting5.17]

2ED_009_20_00 [C-6] not supported [Termsetting1] with [Ltsetting5.18]

2ED_009_26_00 [C-6] not supported [Termsetting1] with [Ltsetting5.23]

2ED_009_28_00 [C-6] not supported [Termsetting1] with [Ltsetting5.24]

2ED_012_11_00 [C-6] not supported [Termsetting2] with [Ltsetting5.21]

2ED_012_15_00 [C-6] not supported [Termsetting2] with [Ltsetting5.25]

2ED_009_19_00 [C-6] [Termsetting1] with [Ltsetting5.17]

2ED_009_21_00 [C-6] [Termsetting1] with [Ltsetting5.18]

2ED_009_27_00 [C-6] [Termsetting1] with [Ltsetting5.23]

2ED_009_29_00 [C-6] [Termsetting1] with [Ltsetting5.24]

2ED_012_12_00 [C-6] [Termsetting2] with [Ltsetting5.21]

2ED_012_16_00 [C-6] [Termsetting2] with [Ltsetting5.25]

2ED_009_22_00 [C-7] not supported [Termsetting1] with [Ltsetting5.19]

2ED_009_24_00 [C-7] not supported [Termsetting1] with [Ltsetting5.20]

2ED_012_13_00 [C-7] not supported [Termsetting2] with [Ltsetting5.22]

2ED_009_23_00 [C-7] [Termsetting1] with [Ltsetting5.19]

2ED_009_25_00 [C-7] [Termsetting1] with [Ltsetting5.20]

2ED_012_14_00 [C-7] [Termsetting2] with [Ltsetting5.21]

2EA_002_01_00 [Cash Advance] [Termsetting4] with [Ltsetting1.1].

2EA_006_04_00 [Cash Advance] [Termsetting4] with [Ltsetting1.90]

2EB_009_02_01 [Cash Advance] [Termsetting4] with [Ltsetting1.1]

2EB_009_02_02 [Cash Advance] [Termsetting4] with [Ltsetting1.1]

2EB_016_02_01 [Cash Advance] [Termsetting4] with [Ltsetting1.1]

2EB_016_02_02 [Cash Advance] [Termsetting4] with [Ltsetting1.97]

2EB_017_02_00 [Cash Advance] [Termsetting4] with [Ltsetting1.1]

2EC_001_03_00 [Cash Advance] [Termsetting5.3] with [Ltsetting1.1]

2EA_010_00_01 [contact] [Termsetting1] with [Ltsetting1.1]

2EA_010_00_02 [contact] [Termsetting3] with [Ltsetting1.1]

2EA_010_01_00 [contact] Any

2ED_017_01_00 [Extended Selection] not supported [Termsetting3] with [LTsetting3.5]

2ED_001_01_01 [Extended Selection] [Termsetting1] with [LTsetting2.11]

2ED_001_01_02 [Extended Selection] [Termsetting3] with [LTsetting2.12]

2ED_001_01_03 [Extended Selection] [Termsetting1] with [LTsetting2.13]

2ED_001_01_04 [Extended Selection] [Termsetting1] with [LTsetting2.14]

2ED_001_01_05 [Extended Selection] [Termsetting3] with [LTsetting2.15]

2ED_001_01_06 [Extended Selection] [Termsetting1] with [LTsetting2.16]

2ED_002_01_00 [Extended Selection] [Termsetting3] with [LTsetting2.25]

2ED_017_00_01 [Extended Selection] [Termsetting3] with [LTsetting3.5]

2ED_017_00_02 [Extended Selection] [Termsetting2] with [LTsetting3.5]

2ED_018_00_01 [Extended Selection] [Termsetting1] with [LTsetting3.5]

2ED_018_00_02 [Extended Selection] [Termsetting2] with [LTsetting1.30]

2ED_018_00_03 [Extended Selection] [Termsetting3] with [LTsetting1.30]

2ED_018_00_04 [Extended Selection] [Termsetting1] with [LTsetting1.31]

2ED_018_00_05 [Extended Selection] [Termsetting1] with [LTsetting1.101]

2EA_012_00_00 [Language Preference] [Termsetting1] with [LTsetting1.7x]

2EA_012_01_00 [Language Preference] [Termsetting1] with [LTsetting7.x]

2EA_003_00_01 [Purchase with cashback] [Termsetting4] with [LTsetting1.3].

2EA_003_00_02 [Purchase with cashback] [Termsetting4] with [LTsetting1.3].

2EA_006_03_00 [Purchase with cashback] [Termsetting4] with [LTsetting1.91]

2EB_011_02_01 [Purchase with cashback] [Termsetting4] with [LTsetting1.3]

2EB_011_02_02 [Purchase with cashback] [Termsetting4] with [LTsetting1.3]

2EB_015_02_01 [Purchase with cashback] [Termsetting4] with [LTsetting1.3]

2EB_015_02_02 [Purchase with cashback] [Termsetting4] with [LTsetting1.3]

2EB_015_02_03 [Purchase with cashback] [Termsetting4] with [LTsetting1.3]

2EB_015_02_04 [Purchase with cashback] [Termsetting4] with [LTsetting1.3]

2EC_001_02_00 [Purchase with cashback] [Termsetting5.2] with [LTsetting1.3]

2EA_002_00_00 [Purchase] [Termsetting4] with [LTsetting1.3]

2EA_006_02_01 [Purchase] [Termsetting4] with [LTsetting1.90]

2EA_006_02_02 [Purchase] [Termsetting4] with [LTsetting1.98]

2EB_007_01_01 [Purchase] [Termsetting4] with [LTsetting2.4].

2EB_007_01_02 [Purchase] [Termsetting4] with [LTsetting2.4].

2EB_008_01_01 [Purchase] [Termsetting4] with [LTsetting1.3]

2EB_008_01_02 [Purchase] [Termsetting4] with [LTsetting1.3]

2EB_009_01_01 [Purchase] [Termsetting4] with [LTsetting1.2]

2EB_009_01_02 [Purchase] [Termsetting4] with [LTsetting1.2]

2EB_009_01_03 [Purchase] [Termsetting4] with [LTsetting1.97]

2EB_009_01_04 [Purchase] [Termsetting4] with [LTsetting1.97]

2EB_013_01_00 [Purchase] [Termsetting4] with [LTsetting1.3]

2EB_014_01_00 [Purchase] [Termsetting4] with [LTsetting1.3]

2EB_015_01_01 [Purchase] [Termsetting4] with [LTsetting1.1]

2EB_015_01_02 [Purchase] [Termsetting4] with [LTsetting1.1]

2EB_015_01_03 [Purchase] [Termsetting4] with [LTsetting1.1]

2EB_015_01_04 [Purchase] [Termsetting4] with [LTsetting1.1]

2EB_016_01_00 [Purchase] [Termsetting4] with [LTsetting1.2]

2EB_017_01_00 [Purchase] [Termsetting4] with [LTsetting1.4]

2EB_018_01_00 [Purchase] [Termsetting4] with [LTsetting1.2]

2EB_019_01_00 [Purchase] [Termsetting4] with [LTsetting1.3]

2EB_020_01_01 [Purchase] [Termsetting4] with [LTsetting1.3]

2EB_020_01_02 [Purchase] [Termsetting4] with [LTsetting1.3]

2EC_001_01_00 [Purchase] [Termsetting5.1] with [LTsetting1.1]

2EB_010_01_01 [Purchase] [Termsetting4] with [LTsetting2.6]

2EB_010_01_02 [Purchase] [Termsetting4] with [LTsetting2.6]

2EB_010_01_03 [Purchase] [Termsetting4] with [LTsetting2.6]

2EA_002_02_00 [Refund] [Termsetting4] with [LTsetting1.4].

2EA_006_05_00 [Refund] [Termsetting4] with [LTsetting1.91]

2EB_008_02_01 [Refund] [Termsetting4] with [LTsetting1.4]

2EB_008_02_02 [Refund] [Termsetting4] with [LTsetting1.4]

2EB_011_01_00 [Refund] [Termsetting4] with [LTsetting1.2]

2EB_012_01_00 [Refund] [Termsetting4] with [LTsetting1.4]

2EB_013_02_00 [Refund] [Termsetting4] with [LTsetting1.4]

2EB_014_02_01 [Refund] [Termsetting4] with [LTsetting1.2]

2EB_014_02_02 [Refund] [Termsetting4] with [LTsetting1.3]

2EB_018_02_00 [Refund] [Termsetting4] with [LTsetting1.4]

2EB_019_02_00 [Refund] [Termsetting4] with [LTsetting1.3]

2EC_001_04_00 [Refund] [Termsetting5.4] with [LTsetting1.4]

2EB_004_01_01 [Status Check] and [Purchase] [Termsetting4] with [LTsetting1.2]

2EB_004_01_02 [Status Check] and [Purchase] [Termsetting4] with [LTsetting1.97]

2EB_005_01_00 [Status Check] and [Purchase] [Termsetting4] with [LTsetting1.3]

2EB_004_02_00 [Status Check] and [Cash Advance] [Termsetting4] with [LTsetting1.1]

2EB_003_01_00 [Status Check] and [Purchase] [Termsetting4] with [LTsetting1.1].

2EB_006_01_00 [Status Check] and [Purchase] [Termsetting4] with [LTsetting1.1]

2EB_003_02_00 [Status Check] and [Refund] [Termsetting4] with [LTsetting1.4].

2EB_003_00_01 [Status Check] [Termsetting1] with [LTsetting1.2]

2EB_003_00_02 [Status Check] [Termsetting2] with [LTsetting1.1]

2EB_003_00_03 [Status Check] [Termsetting2] with [LTsetting2.1]

2EB_003_00_04 [Status Check] [Termsetting2] with [LTsetting2.3]

2EB_003_00_05 [Status Check] [Termsetting1] with [LTsetting1.97]

2EB_004_00_01 [Status Check] [Termsetting2] with [LTsetting1.2]

2EB_004_00_02 [Status Check] [Termsetting2] with [LTsetting1.89]

2EB_004_00_03 [Status Check] [Termsetting2] with [LTsetting2.2]

2EB_005_00_01 [Status Check] [Termsetting2] with [LTsetting1.3]

2EB_005_00_02 [Status Check] [Termsetting2] with [LTsetting1.4]

2EB_005_00_03 [Status Check] [Termsetting2] with [LTsetting1.100]

2EB_006_00_01 [Status Check] [Termsetting1] with [LTsetting1.2]

2EB_006_00_02 [Status Check] [Termsetting2] with [LTsetting1.1]

2EB_006_00_03 [Status Check] [Termsetting2] with [LTsetting2.1]

2EB_006_00_04 [Status Check] [Termsetting2] with [LTsetting2.3].

2EB_006_00_05 [Status Check] [Termsetting1] with [LTsetting1.97].

2EF_001_01_00 [Value qualifier] [Termsetting2] with [LTsetting1.45].

< End Of The Document>