Arkos is a software framework that can be used to build any L3 payment acceptance system. It requires good software skills, basic EMV/payment expertises, and a good knowledge of the API to start. In average, between 8 and 12 weeks are required to port the software onto a new platform.
The advantages of using the Arkos 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 Level 3 contexts
The system’s version that is purchased is maintained against the very last specs and frequent test plans
See Acronyms, Terms and Definitions L3 for information about the Acronyms, Terms and Definitions common in development of an EMV Level 3 application.
Standard Project steps
Step 1: Qualification Phase
Plaform qualification
The purpose of the platform qualification is to assess the use of the platform, and to identify any constraints or challenges that might arise at the course of the project.
For each targeted platofrm, we would need:
EMV Level 2 Letter-Of-Approval (LOA)
Platform Product Datasheet
SDK
Documentation
Some payment devices (nice-to-have)
Processing Host qualification
The purpose of the processing host qualification is to assess the effort to support the processor’s requirements as well as to validate their compatibility with the standard card payment business processes between an acceptor and a processor.
For each targeted processor, we would need:
Exchange Protocol Specifications
Transport Protocol Specifications
Security Specifications (if applicable)
Maintenance Host qualification (if applicable)
Note: Not this step is not required if the Terminal Manager System is compatible with Nexo TMS specifications.
The purpose of the Maintenance host qualification is to assess the effort to support the TMS’s requirements as well as to validate their compatibility with the standard maintenance and monitoring business processes between an acceptor and a TMS.
For each targeted processor, we would need:
Exchange Protocol Specifications
Transport Protocol Specifications
Security Specifications (if applicable)
Sale System qualification (if applicable)
Note: Not this step is not required if the Sale System is compatible with Nexo Retailer specifications.
The purpose of the Sale System qualification is to assess the effort to support the Sale System’s requirements as well as to validate their compatibility with the standard sale business processes between a sale system and an acceptor.
For each targeted Sale System, we would need:
Exchange Protocol Specifications
Transport Protocol Specifications
Step 2: Project Execution
Solution Requirements
Development
Step 3: Project Acceptance
User Acceptance Test
Certification