SB n° 286: Update for EMV Book C-5. SW:6F00
EMV® Specification Bulletin No. 286 First Edition February 2023 Update for EMV Book C-5 Change to the Processing Requirement of Status Word ’6F00’
Applicability
This Specification Bulletin applies to:
- EMV® Contactless Specifications for Payment Systems, Book C-5 – Kernel 5 Specification, Version 2.9, March 2020
- EMV® Contactless Specifications for Payment Systems, Book C-5 – Kernel 5 Specification, Version 2.10, March 2021
Related Documents
- None Effective date ⚫ Immediate
Description
Currently, if the Status Word returned in the response to any command are different from ‘9000’, the Kernel is required to terminate the transaction and provide a Select Next Outcome as described in section 3.12.10. This specification bulletin changes the requirements when the Status Word ‘6F00’ is returned to Get Processing Options command as described below. Details of Changes ✓ Replace the sections from 3.3.1.3 to 3.3.1.7 under “Requirement – GPO Response Analysis” with the following.
countries.
Requirement – GPO Response Analysis 3.3.1.3 3.3.1.4 3.3.1.5 3.3.1.6 If the Status Word returned by the card is ‘6F00’, Then the Kernel shall terminate the transaction and provide 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 Message Identifier: '06' (“CARD ERROR”) Status: Ready to Read UI Request on Restart Present: No Data Record Present: No Discretionary Data Present: No Alternate Interface Preference: N/A Receipt: N/A Field Off Request: N/A Removal Timeout: Zero If the Status Word returned by the card is different from ‘9000’ and ‘6F00’, Then the Kernel shall terminate the transaction and provide a Select Next Outcome as described in Section 3.12.10. If the AIP (Tag ‘82’) is absent from the GET PROCESSING OPTIONS response, Then the Kernel shall terminate the transaction and provide a Select Next Outcome as described in Section 3.12.10. If the Transaction Mode is equal to ‘Undefined Mode’, Then If the AIP (Tag ‘82’) returned by the card has Byte 2 Bit 8 set to ‘1’ (‘EMV Mode Selected’), And the Terminal Compatibility Indicator Byte 1 Bit 2 is set to ‘1’ (‘EMV Mode Supported’), Then the Kernel shall set Transaction Mode to ‘EMV Mode’. Else the Kernel shall terminate the transaction and provide a Select Next Outcome as described in Section 3.12.10.
3.3.1.7 If the AFL (Tag ‘94’) is absent from the data returned to the GET PROCESSING OPTIONS response Then the Kernel shall terminate the transaction and provide a Select Next Outcome as described in Section 3.12.10.
countries.
Requirement – GPO Response Analysis 3.3.1.8 If the AFL (Tag ‘94’) is present in the GET PROCESSING OPTIONS RESPONSE And its value is incorrectly formatted (e.g. not multiple of 4 bytes, invalid SFI value...), Then the Kernel shall terminate the transaction and provide a Select Next Outcome as described in Section 3.12.10 3.3.1.9 If any of the conditions below is true: the Transaction Mode is equal to ‘Legacy Mode’ the Transaction Mode is equal to ‘EMV Mode’ and Offline Data Authentication (implementation or acquirer option) is not supported the Transaction Mode is equal to ‘EMV Mode’ and the AIP (Tag ‘82’) indicates that CDA is not supported (Byte 1 bit 1 is ‘0’) Then the Kernel shall set TVR Byte 1 bit 8 (‘Offline Data Authentication was not performed’) to ‘1’. ✓ In section 4.4, under “Processing State Returned in the Response Message”, insert the following description after “‘6A80’ indicates that the command is incorrectly formatted.”: ‘6F00’ indicates that an unexpected error has occurred.
countries.
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
countries.