...
Note: Payment applications are not necessarily clearly identified in that 3-tier model. Level3 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.
Integration Process
The success of an Agngos 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:
...
Note: Payment brands CL specifications are constantly changing. Agnos Framework is base-lined once a year to reflect the most up-to-date requirements validated during CL TA sessions, and to provide improvements on API. However, it’s impossible to have an on-the-shelf product matching all very last requirements all along the year because each brand moves at different a pace. So, Agnos and underlying CL payment applications are part of an internal qualification process to keep them in sync with the specifications. The product can’t be base-lined every month (to costly to do so) but there is a systematic monitoring on specs changes and maintenance on current base-line to avoid gaps. Consequently, customers’ project dates will define which versions are going to be used depending on the project timing and specs sunsets/releases. Updates will be delivered on purpose.
Logical Model
As depicted below:
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. See [3] for more details on integration
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
AgnosGE is linked onto the GPI interface
...