...
Identity: the ability to certify a L2 system is linked to the ability to define it. There is no existing definition of a card processing stack. The different specifications released by payment networks don’t provide a common view on the L2. Agnos identity is defined by its structure (see Data model section), and its behavior (see Open L2 API [1]). This concept answers to the question ‘’WHAT shall we certify’’.
Testability: given the lack of definition of the L2 across payment networks’ specifications, there are different ways to test a L2 system. Testability is proprietary and differs from labs to labs, from tools to tools, from stack to stack. Hence, Agnos requires a specific testing environment, ACE, that is provided to labs to certify the software. So, the testability is the responsibility of the stack provider. This concept answers to the question ‘’HOW shall we certify’’.
Stability across the time: the stability of a L2 system dependents of its maturity ad is important in regards with re-certification rules. L3 requirements are very challenging and sometimes could impact some L2 implementations (for example, see regional EMV applications selection requirements). Consequently, L2 stack providers must anticipate or they may need to modify their implementations once L2 LoA are granted with the risk to go through a re-certification process. This concept answers to the question ‘’WHEN shall we certify’’.
IntegrabilityIntegrability
The integrability of a card processing system is its ability to provide a series of services so it can be seamlessly integrated into a payment application without impacting the certificability. That characteristic is at the core of this documentation (see Open L2 API [1]). There is no common API shared across “L2” providers and payment system vendors. OLA is a proposition of normalization in the objective to improve the underlying productivity of “L3” developments.
...