Agnos is a software framework that can be reused to build any acceptance system. It requires good software skills, basic EMV payment expertise, and a good knowledge of the API to start (reading documentation should be enough even if we recommend to follow a course). In average, between 8 and 12 weeks are required to port the system onto a new platform to be ready to start a qualification
The advantages of using that framework are:
The system has already been certified in the past on different platforms
The system is already deployed on the field in major markets
The system is versatile and may be adapted to any Level3 contexts
The system’s version that is purchased is maintained against the very last specs and test plans updates (that are frequent)
However, note that:
The system is complex and usually requires a 3-day training session
The system needs to be qualified before being submitted to a TA
The system doesn’t implement any specific processor/acquirer security scheme (not standardized)
This section provides a high level description of the framework:
Amadis Ecosystem model
Development Steps presentation
Development Environment presentation
Memory Foot Print example
Development Steps
Here are the major steps to cross in order to port the framework in preparation to qualification tests.
Step 1: Read Manuals
This step is used to know what the documents contain to use them later as reference.
The Wiki is the main source of information. There are 2 others documents available for implementation purposes:
[1]: Agnos Framework - L1 - Integration & Certification Guide (provided on demand) ⇒ to get details on GPI primitives
[4]: Agnos Framework - L3 - ACE2P Protocol (provided on demand) ⇒ to integrate ACE protocol
Don’t forget that the code is also a good source of information to know how a software system works: use header files to understand API contracts (especially for the GPI and Agnos).
In order to improve our manuals, please use them as references to send us requests for support on API integration. To help us , send questions by emails and include some of the following artifacts (depending on the context):
Tagged email’s object (mandatory): [Company name][Project name][Software component] Topic
Reference of the unclear / incomplete section of a document
Software components versions (mandatory)
EMV Logs
Card’s reference that is used
Configuration files
Step 2: Play with the AVT
See Agnos Virtual Terminal page.
Step 3: Study the Logical Model
Step 4: Study the Physical Model
Step 5: Start Porting
See Agnos Framework Porting and/or Agnos CL Kernel Porting pages.
Integration Environment
According to the license agreement, a corresponding set of artifacts is delivered. Software components have been prepared to fit to your platform and operating system:
Use binary components for your deployment model implementation
Use binary and development components for your implementation
The most popular platforms and operating systems of the industry are supported by Agnos (WinCE/Wndows7/Linux/Android/iOS/FreeRTOS), and proprietary environments have already been targeted. Note that all the components described above can be packaged to support your development (Eclipse IDE along with Eclipse projects) on flexible platforms like PC (Windows/Linux). Thanks to the level of abstraction that Agnos provides, it is recommended to develop on such platforms to accelerate development and test phases: AVT is a reference implementation available on Windows that can be used along with a specific Agnos integration project targeting an embedded platform. Also, systematic use of the GPI abstraction layer is a must to achieve high level of portability.