Entry Point – Frequently Asked Questions (FAQ)

FAQ – Entry Point 1. Why does Entry Point support pre-processing that was previously handled by legacy kernels ? A: Pre-processing has been introduced at the Entry Point level to make it EMV generic and make the pre-processing results available to any kernel. It does not negatively impact “card in the field” transaction time. 2. How do payment industry applications relate to transport applications? A: The two approaches are fundamentally different. Transport applications are typically local applications, using symmetric key cryptography; payment applications have global acceptance and use public key cryptography. Both approaches can be supported independently on the same physical platform. 3. How can a scenario be supported that requires multiple interactions with the card, such as payment followed by loading of tokens? A: Such a scenario can be broken down in different steps. The kernel decides to deal with the different steps in one go or to deal with one step at a time. In case of the latter, the kernel hands back control to the Entry Point after each step. For the customer, this results in the terminal proposing two or more “taps”. In case of the former, it may result in a “tap & hold” experience. Note that requirements related to the different steps need to be handled by the kernel – the Entry Point will not remember the last card selected, nor confirm that the same card is presented again. 4. Will it be necessary for existing contactless kernels to be rewritten/updated to support the Entry Point specification? A: Yes, existing kernels will require software and/or architecture modifications to support the Entry Point specification. 5. Does the Entry Point specification only support PPSE application selection? A: No. The Entry Point specification specifies application selection process through PPSE but permits proprietary selection processing as well. For information on the proprietary selection processing, please see the explanation before section 5.1 of the Entry Point specification. This document contains proprietary information of EMVCo LLC. Copyright ©2008. All rights reserved