Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In this page:

Table of Contents
maxLevel2

...

Introduction

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.

...

See _Acronyms, Terms and Definitions for information about the terms common in the development of an EMV EMVCo 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 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

  • 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.

...

  • 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.

...

  • 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:

  1. EMVCo Level 1 (L1) covers the physical, electrical and transport level interfaces of the hardware.

  2. EMVCo Level 2 (L2) ensures the compliance of the payment kernel.

  3. EMVCo Level 3 (L3) ensures that network specifications and acquirer requirements have been met.

Arkos Framework is part of the L3 Certification scope.

Below is a non-exchaustive list of card

Card networks or Processors

Terminal Integration Tests

Visa

ADVT (Acquirer Device Validation Toolkit)

CDET (Contactless Device Evaluation Toolkit)

VPTP (Visa's payWave Test Tool kit)

MasterCard

M-TIP (Mastercard Terminal Integration Process)

AMEX

AEIPS (American Express ICC Payment Specifications)

Nexo Standards

NIS (Nexo Implementaton Scope)