...
Tiers1 ≅ EMV Level1: level covering all platform related services. It includes card coupling (CT and CL)
Tiers2 ≅ EMV Level2: level covering card processing services. It covers EMVCo L2 CT , EMVCo L2 CL, and payment networks' CL specifications
Tiers3 ≅ EMV Level3: level covering payment services. It covers all applications or libraries providing services to sales systems, or using services from TMS, or acquirer/processing systems
Tiers1 - EMV Level1
See GPI page.
Agnos Framework runs on top of a HAL, the GPI interface (see release notes or gpi.c for versioning). Depending on the platform’s constraints, a GPI may have different structures (single static lib, single dynamic lib, one or more dynamic lib, client/server architecture, etc…). However, it always provides the same API to higher abstraction levels (i.e. Level2 and Level3).
...
It may require between 4 and 10 weeks to implement and to test the features related to xGPI.
Tiers2 - EMV Level2
See AGNOS page
See AGNOSEP page
Agnos Framework L2's core includes Agnos and AgnosDB. These parts of the package have been certified against EMVCo latest specifications. Agnos and AgnosDB are systematically tested against different contact ICS.
...
Compilation options aligned on projects requirements and RAM constraints (see Symbols, options, and constants)
Physical model to deploy (i.e what are the units of compilation)
Performance, and platform integration requirements (fallback to other interface(s), displays, UX, …) (see Agnos Framework QKB)
Tiers3 - EMV Level3
See AGNOSMW page.
...