The interface of EMVL2 focuses on the functions required by the EMV specification, encapsulating the relevant interfaces of the POS and card interaction process. Each L2 kernel has a set of EMVL2 interfaces. If you want to use the EMVL2 interface well, you need to have a good understanding of the EMV specification.
EMVL3 is a layer of encapsulation based on EMVL2. It provides a unified interface that encapsulates the processing details related to EMVL2. People who do not know the EMV specification can also use the EMVL3 interface to complete card transactions. EMVL3 provides a standard EMV process for interaction between POS and cards, but it is only limited to the card interaction link. The higher-level transaction process needs to be organized by developers themselves.
PaymentService provides higher-level service functions on top of EMVL3, encapsulating the process of various transaction processing, providing application transaction-level services. If you don't care about how to handle Payment/Refund transactions, then using PaymentService is the most suitable option.
Of course, this is just a simple description of the relationship between the three. Which interface is more suitable for you still needs to be analyzed specifically. Some people are familiar with the EMV specification and our EMVL3 interface, but they still choose to use our PaymentService.
No matter which interface you choose to use, we will provide corresponding technical support.
No.
PaymentService already includes EMVL3 functionality and does not require additional links to the EMVL3 SDK. However, NSDK needs to be linked during application development, such as using NSDK APIs for some security functions.
