Integrating Agnos - or Developing a payment application (L3) relies on:
A previous successful platform integration (DEVICE realization) validated from unit tests vectors execution
A first L2 qualification demonstrating that the system is mature enough to start L3 development (i.e. a full L2 TA is not required to start as long as significant use cases can be executed)
Agnos programmation paridigm is systematic:
Set pre-conditions
Trigger a transaction
Get post-conditions
Agnos provides a rich API. The following gives some hints to built from scratch a first application integrating Agnos.
Set pre-conditions
System Initialization
This level of initialization shall be performed only once usually at system’s start-up time.
gpiMain
gpiInitializeHSM
gpiInitializeDisplay
gpiInitPolling
Transaction Initialization
Trigger a transaction
Magstripe
Contact
Contactless
Get post-conditions
Sessions Management