In this page, you will find:
| Table of Contents | ||
|---|---|---|
|
...
Introduction
Arkos is a software that eases and accelerates to build any payment acceptance system. Developing a payment application using our framework requires good software skills, basic EMV/payment expertises, and a good knowledge of the API to start.
See Acronyms, Terms, and Definitions for information about the terms common in the development of an EMVCo Level 3 application.
Accept payments anywhere with a universal solution.
Arkos is a state-of-art solution that serves secure payment acceptance services and can be deployed into any topologies, whatever the context and the constraints (operational, environment, system architecture, devices), with a minimum of adaptations and by reducing merchants’ costs and risks.
Arkos provides merchants with a solution supporting payment card processing and additional features such as configuration, online processing, batch processing, UI management…
...
Arkos is defined at a global level so that there is no hypothesis made on:
The type of merchants using it,
The type of platforms running it,
The surrounding physical architectures, and the business/regulatory contexts (technologies, regions, security schemes, business processes, …)
Basically:
Arkos is defined as a payment solution that can be deployed following different physical models (alias typologies) with a minimum of adaptations;
The goal is to supply an appropriate product by reducing merchants’ costs and risks.
This section of the Wiki is meant to help technical teams to integrate, and to implement payment solutions using Arkos. It provides a global perspective of the framework.
Visit our Wiki pages to learn more about Arkos.
Why using Arkos?
The advantages of using the Arkos 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 EMVCo Level 3 contexts
The system’s version that is purchased is maintained against the very last specs and frequent test plans
How it works?
The Wiki sections provide all the necessary information to understand how to use the Arkos framework.
Topology Models
Standard Project steps
Step 1: Qualification Phase
Platform 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. In average, between 8 and 12 weeks are required to port the software onto a new platform.
...
EMVCo Level 2 Letter-Of-Approval (LOA) to ensure the compliance of the payment kernels
Platform Product Datasheet to validate the device technical characteristics
SDK and SDK Documentation
Payment devices
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.
...
Exchange Protocol Specifications
Transport Protocol Specifications
Security Specifications
Maintenance Host qualification (if applicable)
Note: Not this step is not required if the Terminal Manager System is compatible with Nexo TMS specifications.
...
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.
...
Exchange Protocol Specifications
Transport Protocol Specifications
Step 2: Project Execution
Solution Requirements
Development
Step 3: Project Acceptance
User Acceptance Test
Step 4: Certification
There are three levels of testing requirements prior to deploy a standard payment terminal:
...