PCI Watch

Tracking changes across the Payment Card Industry

TTA Bulletin nº 229: Terminal Level 2 Test Cases EMV® Contact Kernel Output

v4 Type Approval Bulletins
ChipContact Acceptance Device

EMV<sup>®</sup> Terminal Type Approval Bulletin No. 229 Fourth Edition, January 2021 Terminal Level 2 Test Cases EMV<sup>®</sup> Contact Kernel Output

Applicability

This Bulletin applies to:

  • EMV<sup>®</sup> Terminal Type Approval - Level 2 Test Cases – version 4.3i

Related Documents

  • Specification Bulletin 220 – EMV<sup>®</sup> Contact Kernel Output, Second Edition April 2020.

Effective Date

  • January 31st 2021

Description

EMVCo updated the Specification Bulletin – EMV Contact Kernel Output. Related to this update, related tests cases have been changed accordingly. Update to EMVCo Type Approval Terminal Level 2 Test Cases v4.3i Revised test cases: 2CA.143.00 New test cases: 2CA.143.01 2CA.143.02 Deleted test cases: None

countries.

2CA.143.00 Kernel Data Output Test No: 2CA.143.00 - Revision 43j - Number of sub cases: 0 Objective: To ensure that the Kernel outputs the mandated Data Objects as per SB220:

  • Amount, Authorized (Numeric) ('9F02')
  • Application Cryptogram ('9F26')
  • Application Effective Date ('5F25')
  • Application Expiration Date ('5F24')
  • Application Interchange Profile ('82')
  • Application Label ('50')
  • Application PAN ('5A')
  • Application PAN Sequence Number ('5F34')
  • Application Preferred Name ('9F12')
  • Application Transaction Counter ('9F36')
  • Application Usage Control ('9F07')
  • Application Version Number ('9F09')
  • Cardholder Name ('5F20')
  • Cardholder Name Extended ('9F0B')
  • Cryptogram Information Data ('9F27')
  • CVM List ('8E')
  • CVM Results ('9F34')
  • DF Name ('84')
  • Interface Device Serial Number ('9F1E')
  • Issuer Action Codes ('9F0D', '9F0E', '9F0F')
  • Issuer Application Data ('9F10')
  • Issuer Code Table Index ('9F11')
  • Issuer Country Code ('5F28')
  • Language Preference ('5F2D')
  • Merchant Category Code ('9F15')
  • Merchant Identifier ('9F16')
  • Payment Account Reference ('9F24')
  • Terminal Capabilities ('9F33')
  • Terminal Country Code ('9F1A')
  • Terminal Identification ('9F1C')
  • Terminal Type ('9F35') countries. 2CA.143.00 Kernel Data Output
  • Terminal Verification Results ('95')
  • Track 2 Equivalent Data ('57')
  • Transaction Currency Code ('5F2A')
  • Transaction Date ('9A')
  • Transaction Status Information (‘9B’)
  • Transaction Time ('9F21')
  • Transaction Type ('9C')
  • Unpredictable Number ('9F37') Reference EMV 4.3: Book Bulletins - Section SB 220 - Bulletin n°220, EMV Contact Kernel Output (April 2020) Terminal Configuration: Terminal [NA] Configuration (New format): Conditions:
  • Action: NA Card Data listed in the objective of this test will be set with values different from zero in LT. Transaction is performed in a way such that the ‘kernel output mandated data objects’ are not zero. Procedure: Application in LT is selected and transaction is performed with LT. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC either a 1st or 2nd Generate AC.
  • The data output from the Kernel shall contain the mandated Data Object from SB220 with the corresponding values different from zero. However, Transaction Type may be zero if the terminal only supports Goods & Services countries. 2CA.143.01 Kernel Data Output Test No: 2CA.143.01 - Revision 43j - Number of sub cases: 0 Objective: To ensure that the Kernel outputs the mandated Data Objects as per SB220:
  • Amount, Other (Numeric) ('9F03') Reference EMV 4.3: Book Bulletins - Section SB 220 - Bulletin n°220, EMV Contact Kernel Output (April 2020) Terminal Configuration: Terminal [Cashback] Configuration (New format): Conditions:
  • Transaction is performed in a way such that the ‘kernel output mandated data objects’ listed in the test case objective is not zero. Action: NA Procedure: Application in LT is selected and transaction is performed with LT. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC either a 1st or 2nd Generate AC.
  • The data output from the Kernel shall contain the mandated Data Object from SB220 with the corresponding values different from zero. countries. 2CA.143.02 Kernel Data Output Test No: 2CA.143.02 - Revision 43j - Number of sub cases: 0 Objective: To ensure that the Kernel outputs the mandated Data Objects as per SB220:
  • Issuer Script Results (-) Reference EMV 4.3: Book Bulletins - Section SB 220 - Bulletin n°220, EMV Contact Kernel Output (April 2020) Terminal Configuration: Terminal [Online Only] OR [Offline/Online Capable] Configuration (New format): Conditions:
  • LT parameters are set so that transaction is performed on-line
  • Transaction is performed in a way such that the ‘kernel output mandated data objects’ are not zero. Action: NA Procedure: Application in LT is selected and transaction is performed with LT. Pass Criteria:
  • The terminal shall accept the card and process the transaction until completion, by requesting a TC at 2nd Generate AC.
  • The data output from the Kernel shall contain the mandated Data Object from SB220 with the corresponding values different from zero. countries.

Legal Notice

This document summarizes EMVCo’s present plans for evaluation services and related policies and is subject to change by EMVCo at any time. This document does not create any binding obligations upon EMVCo or any third party regarding the subject matter of this document, which obligations will exist, if at all, only to the extent set forth in separate written agreements executed by EMVCo or such third parties. In the absence of such a written agreement, no product provider, test laboratory or any other third party should rely on this document, and EMVCo shall not be liable for any such reliance. No product provider, test laboratory or other third party may refer to a product, service or facility as EMVCo approved, in form or in substance, nor otherwise state or imply that EMVCo (or any agent of EMVCo) has in whole or part approved a product provider, test laboratory or other third party or its products, services, or facilities, except to the extent and subject to the terms, conditions and restrictions expressly set forth in a written agreement with EMVCo, or in an approval letter, compliance certificate or similar document issued by EMVCo. All other references to EMVCo approval are strictly prohibited by EMVCo. Under no circumstances should EMVCo approvals, when granted, be construed to imply any endorsement or warranty regarding the security, functionality, quality, or performance of any particular product or service, and no party shall state or imply anything to the contrary. EMVCo specifically disclaims any and all representations and warranties with respect to products that have received evaluations or approvals, and to the evaluation process generally, including, without limitation, any implied warranties of merchantability, fitness for purpose or non-infringement. All warranties, rights and remedies relating to products and services that have undergone evaluation by EMVCo are provided solely by the parties selling or otherwise providing such products or services, and not by EMVCo, and EMVCo will have no liability whatsoever in connection with such products and services. This document is provided "AS IS" without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in this document. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AS TO THIS DOCUMENT. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to this document. EMVCo undertakes no responsibility to determine whether any implementation of this document may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of this document should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, this document may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement this document is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for any party's infringement of any intellectual property rights in connection with this document.

countries.