Versions Compared

Old Version 33

changes.mady.by.user Olivier Chauvineau

Saved on

compared with

New Version Current

changes.mady.by.user Catherine Boundjia

Saved on

Key

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

Overview

The Arkos Framework is defined at a global level so that there is no hypothesis made on the type of platforms running it. Basically, Arkos provides a set of interfaces that facilated the build and the integration of a card payment acceptance application on any platform.

When choosing Arkos, there are 3 levels of integration to consider:

  • Arkos API, Arkos' Payment API : a set of services driving the Payment as an extension of a Sale function

  • Arkos CallBacks, Arkos' Payment CallBacks : a set of callbacks extending Arkos' behavior so it can be ported onto a specific platform

  • Open L2 API, OLA API : a set of services driving the card processing

For more information about the Arkos API, please go to the https://teamamadis.atlassian.net/wiki/spaces/ADG .

Component

Description

MerchantApp

The Merchant Application is responsible for:

  • UI Interface

  • Input of Amount, service and additionnal payment parameters to start a transaction

  • Printing

  • Configuration of the merchant application

  • Input of TMS Host information for configuration

Arkos Inteface

The Arkos interface provides a set of JNI functions and callbacks between the MerchantApp and the Arkos Framework.

Arkos Framework

The Arkos Framework includes the Arkos Payment Core library coded in C/C++. It is responsible for:

  • Communicating with TMS Host to get payment configuration

  • Receiving Transaction Request from Merchant Application

  • Execute Payment transaction according to local schemes requirements (based on nexo-FAST)

  • Card detection and interaction with L2 EMV

  • Communicating with the Acquirer Host for authorization

  • Persisting transactions records for later actions (cancellation, transaction completion, reversal in case of problems, reconciliation at the end of the day, etc.)

Platform

Physical device on which the payment application is installed.

...

Activity

Description

Roles

MerchantApp Development

Developement of a Merchant Application including UI/UX, business logic, amnd integration of platform services. Arkos framework is 100% independent from its context of execution. It provides API and callbacks to provide the payment as a commodity (API) and extend its behavior to match a specific context (callbacks).

  • See Basic Sequence Flow

Customer or Third-Party

Arkos Integration (L3-L2)

  • See Arkos' Payment API

  • See Arkos' Payment CallBacks

Amadis or Third-Party

Platform Integration (Security)

  • See OLA API

  • Security (eg. Key Loading…) To be described…

Customer or Third-Party

...