Why choose Agnos


Electronic Payment, the fabric of commerce

Developing, certifying and maintaining an EMV acceptance stack has become critical since the emergence of EMVCo contactless specifications for payment systems and the rise of mobile payment. Legacy organizations, Fin-Tech startups, and new players going after new business opportunities have had to deal with increasing complexity in implementing EMV payment acceptance equipment and solutions due to a very demanding RegTech environment.

Agnos' promise is to protect these solution providers from this complexity by abstracting it, offering generic EMV Level 2 APIs, test automation means, and streamlining certification stages. Standardization, commoditization, and simplification are at the core of the Agnos project. 

Take control 

Adopting Agnos allows organizations to take control of their EMV software by removing technical dependencies with respect to hardware platforms, and by avoiding strong coupling with processing/acquiring infrastructure.

Agnos fast-forwards EMV acceptance on new products targeting fast moving markets. It is also a strategic move that reduces development costs related to a technology that currently requires increasing long term investments in IP, expertise, and tools.


State of the art 

Since 2009, a dedicated team of software architects and payment experts has been developing a global Framework and the APIs to address customer needs in different markets and regions.

Today, Agnos EMV acceptance stack is a state-of-the-art software component which normalizes the integration of contact and contactless card processing across diverse payment brands and device form factors. Agnos has become a key component in enabling electronic payment at merchant stores worldwide.



The average time to integrate and qualify the Agnos Framework on a new platform is approximately 4 months. Agnos has been integrated on all major silicon platforms (AMD, Atmel, Avago/Broadcom, Intel, Maxim, NXP, STMicroelectronics, TI, etc.), and all popular OS (Android, FreeRTOS, Linux, Windows Embedded/CE, Windows 10).


Letter of Approval

The average time to get a first EMV L2 Type Approval LoA with a new platform integrating Agnos is about 7 months.  Once Level 1 certification has been granted, a CPI test session (Combination/Performance/Integration) is performed before entering into an official TA session.



The average time to deploy a first device in the field integrating Agnos and at least 3 kernels is approximately 16 months Agnos has been deployed in Asia, Australia, Europe, Middle-East, and North America since 2013.


Terminal Approval 

More than 80 EMV L2 Terminal Type Approval sessions have been successfully passed worldwide using the Agnos Framework.


Integration projects

More than 20 different platforms have been integrated ranging from highly constrained devices to PV Based kiosks, mPOS dongles, ATMs, transport solutions, tablets, and stand-alone payment systems. Most of the projects include services to support organizations designing firmware architectures, addressing custom functional or security requirements, and meeting acquirer/processor specific integration needs (aka L3 integrations).


Customers projects

Over 40 projects use the Agnos Framework and Kernels, take advantage of Agnos consulting services, or partner with the Agnos team to develop innovative solutions and tools.


A wide variety of platforms with diverse OSs have been integrated, certified and deployed with the Agnos EMV Level 2 stack worldwide, from common embedded platforms to pure exotic hardware.. The Agnos EMV stack runs on top of a HAL - The Generic Platform Interface (GPI) - which allows Agnos software to be deployed with any EMV Level1 ready hardware. The GPI platform instance covers services required to support EMV card processing and acquirer/processor security requirements. The GPI is the cornerstone of Agnos, and enables the development of generic, platform & OS abstract payment applications.

Duality contact/contactless

A normative approach was adopted across the EMV standard and Payment Network legacy specifications to define a common set of services and parameters. A single library implements common EMV Level2 mechanisms from application selection to cryptogram generation. It shares a common data model with supporting acquirer/processor EMV parameters for any merchant context.


Agnos logical architecture supports different physical deployments such as standalone acceptance systems, ATMs, light mobile payment solutions, or even more complex client/server architectures. No assumptions have been made regarding the ICS and payment system regionalization during the architecture and design stages so Agnos may be adapted to any merchant context, for a smooth and sustainable EMV migration.


Agnos offers various levels of security that are integrated during the certification target stages. EMV security relies on PK infrastructure cryptography that is implemented using software or hardware services (depending on platform capabilities). Acquirer/processor security requirements are separated in order to integrate any local or specific needs. They typically rely on Symmetric Key cryptography and key management schemes. Several services have been abstracted to comply with the wide variety of global and local requirements. PCI related services include SRED primitives, and many algorithms such as DUKPT, Master/Session, AES, ECC.


Software maintenance is crucial in the context of a RegTech environment like EMV Level2 certification.  Agnos integrates test procedures to detect potential regressions and a combination of automated and integration tests are used.


Agnos is a fully functional and qualified EMV stack, ready to be submitted to Laboratories for the TA certification process. It includes all global Kernels and most local ones (American Express, Union Pay, Discover, EFTPOS, EMVCo, Gemalto, JCB, Interac, MasterCard, Visa, …). The precondition to passing a TA is GPI integration (all hardware services must be connected to the HAL before entering the TA stage). The Agnos Framework and its kernel libraries are constantly qualified and reflect  the most up-to-date test plans and accredited test tool libraries.

"Innovation has value only if it opens a space allowing limitation on the entropy of our activities."

Emmanuel Haydont