An Agnos Framework integration project doesn't follow a linear process even if it is possible to present a step-by-step approach to define the global task. But still, Agnos Framework is a wide API that covers many topics that shall be addressed by iterations. There are 4 possible levels of integration onto the framework:
GPI/Device integration: This step consists in “connecting” abstracted GPI services to a platform's API
ACE integration: This step consists in “connecting” Kizis (Level3 application) to a communication layer connected onto ACE UI. ACE UI is the tool provided to submit Agnos to TA
Level3 integration: This step depends on acquirer/processor contexts. It consists in implementing terminal specifications related to merchants and regional payment networks requirements. It aims to target integration certification like Mastecard's mTIP, or Visa's ADVT
CL Kernel integration: This step is not common. Some projects may need to develop their own kernels onto Agnos Framework, or to integrate an Agnos kernel onto their own framework.
