In order to pass the “L2” certification stage, a “L2” implementer shall provide a testing environment along with a test application. That test application depends on the “L2” API and is not identified by payment networks as a specific software component. Hence, its design and its implementation depend on the “L2” definition made by the implementer. Also, the test application has to be replaced by the actual payment application once the “L2” LoA has been granted. So, this means that a card processing stack lives in two different contexts:

• The certification context implemented to target “L2” certification (TA tests)

• The production context implemented to target “L3” certification (integrated tests)

For the purpose of Agnos certification, labs use ACE installed on a Windows PC and communicating with the device. Example: a mobile phone dedicated to CPOC certification:

Open

2 test tools (ACE and Agnos Automation) are used to support development, qualification, and certification. Kizis is a portable Level3 application that implements many services useful for debug, integration and non regression testing. When switching from a test tool to another, there is no need to change the acceptance system. Hence, the same system is always tested being under ACE or Agnos Automation analysis.

Open

ACE

See Agnos Certification Environment page.

Agnos Automation

Agnos Automation is a system used to test any EMV stack supporting a similar architecture model. It automates most of the tests from the following test plans:

• EMVCo contact

• C-2/Mastercard

• C-3/Visa

• C-4/American Express

• C-7/CUP

GUTS

Additionally, a third tool is available: GUTS. This tool allows to test GPI integrations. It is not ready yet for commercial purpose but it is internally used in a beta version.