| Table of Contents |
|---|
Logical Model
Following industry’s paradigm, Agnos Framework is made of 3 distinct layers aligned on EMVCo definitions and industry certification processes cycles:
...
Note: Payment applications are not necessarily clearly identified in that 3-tier model. Level3 Level 3 is not an official term used in the industry. In that document, it is used to discriminate what pertains to the low level layer (i.e. platform services) versus the EMV contact certifiable libraries (i.e. the “kernels”). Level 3 may be hosted on a mobile phone, a secured payment device, a remote host server or split between an acceptance client and a server depending on architecture and security constraints of the payment solution. Agnos supports any type of architecture and has been ported onto different platforms, OS, and device contexts.
...
GPI is the sole library depending on the hardware platform (OS & Firmware). It behaves as a HAL. It is linked onto the operating system’s API provided by the device manufacturer
Agnos is linked onto the GPI Interface
AgnosMW is linked onto the GPI Interface, and AGNOS Interface
AgnosEP is linked onto the GPI Interface, AGNOS Interface and AGNOSMW Interface
OLA is linked onto the GPI Interface, AGNOS Interface and AGNOSMW Interface
It is up to the application developer to interface with any of the 5 interfaces available when developing Level3 applications. An EMV contact development project doesn't need the entry point.
Note: OLA has been designed to support NexoFast dynamic. Hence, most of the Level 3 applications should use OLA for a seamless integration.
Integration Process
The success of an Agnos project lies – at least – on a good understanding of Agnos Framework, underlying EMV concepts, and configuration model. However, the product has been designed to avoid having a deep knowledge on the EMV and payment network specifications. Key components have been certified against major organizations of the industry like American Express, Discover, EMVCo, Interac, MasterCard, Visa, … so that they can be reused in customers’ specific environments.
However, it is important to understand that the product is independent from acquirers/processors infrastructures meaning that the major questions to address during the design stage are:
...