Interoperability Bulletin No. I0092
Extracted document text
EMVCo's index flattens the document's layout, so this text is best used for searching and comparing versions rather than reading end-to-end.
EMV® Interoperability Bulletin No. I0092 First Edition January 2024 Field Issue with T=1/D=4 cards at Automatic Fuel Dispensers Applicability The following interoperability issue has been reported to IWG. EMVCo Identifier Issue Identifier Status Date Opened Description Findings I0092 Transaction Severity ●=High ○ I0092 Volume Severity Resolution in progress – EMVCo, Payment System =Low Feb 15, 2023 EMVCo was made aware of an interoperability issue in the US market affecting Automated Fuel Dispensers (AFD) installed in Nidec Instruments product when they are used with chip cards using T=1 D=4. The issue causes the terminal to time out and lock the card inside the reader. This is an issue as the merchant must shut down the pump to release the card, causing acceptance issues in the field. The root cause is the S(IFSreq) communication block sent by the ISO module that is called prior to the EMV transaction (the AFD accepts non- EMV ISO7816 cards as well). This block, only used when using T=1 protocol, is sent without applying the bit rate adjustment factor of D=4 resulting in a transmission error. The waiting time for the module between retries is quite long resulting in the payment application to time out the transaction. This proprietary “ISO module” was not activated by Nidec Instruments on samples supplied for the EMVCo Type Approval as assumed to be incompatible with the testing tools. Terminal Information Nidec Instruments (previously known as Sankyo) IFM330-0600A LoA # 13044 0414 400 21 FMT. Corrective Action Preventative Action Additional Comments: Impacted Nidec Instruments terminals need to be updated with a firmware fix from Nidec Instruments pending EMVCo testing. According to Nidec Instruments, the card reader version of the AFD which requires the update is: version 4464-01S or before. Version 446401U or later should have no issues. EMVCo will release a Type Approval Bulletin with guidance on how to best manage product type approvals when products support proprietary and additional protocol sequences that the EMVCo test tool does not accommodate. None. © 2024 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Page 1
Legal Notice This document summarizes EMVCo’s present plans for evaluation services and related policies and issubject to change by EMVCo at any time. This document does not create any binding obligations uponEMVCo or any third party regarding the subject matter of this document, which obligations will exist, ifat 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 particularproduct 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 providedsolely by the parties selling or otherwise providing such products or services, and not by EMVCo, andEMVCo 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 ALLREPRESENTATIONS 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 thirdparties 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 othertechnology, 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 toany 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 withthis document. © 2024 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Page 2