Amadis

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

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.

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 where the payment application is installed.

There are 4 levels of integration to consider when building a EMV L3 application onto the Arkos Framework for each specific platform:

  1. Platform Integration (L2-L3):

  2. Arkos Framework Integration:

  3. Arkos Interface Integration:

  4. Security Integration:

  • No labels