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, /wiki/spaces/agnoswiki/pages/953286709 : 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
Component | Description |
---|---|
MerchantApp | The Merchant Application is responsible for:
|
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:
|
Platform | Physical device on which the payment application is installed. |
There are 5 levels of integration to consider when building a EMV L3 application onto the Arkos Framework for each specific platform:
Activity | Description | Roles |
---|---|---|
Merchant App Development | Developement of a Merchant Application including UI/UX, business logic | Customer or Third-Party |
Arkos Interface Integration into the Merchant-App | See Arkos' Payment API and See Arkos' Payment CallBacks | Customer |
Platform Integration (L2-L3) | See OLA API | Amadis or Third-Party |
Arkos Framework Integration | Customer or Third-Party | |
Security Integration | (eg. Key Loading…) To be described. | Customer or Third-Party |