...
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 belowabove:
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 InterfaceAgnosGE is linked onto the GPI 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.
...