...
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:
|
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 3 levels of integration to consider when building a EMV L3 application onto the Arkos Framework for each a given merchant and a specific platform:
Platform Intergration:
Arkos Framework Integration:
Arkos API Integration (Payment):
Arkos API Integration (Security)
...
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).
| Customer or Third-Party |
Arkos Integration |
| Amadis or Third-Party |
Platform Integration |
| Customer or Third-Party |