...
Open L2 API interface is an abstraction of the card processing (alias L2. See also here More On Card Processing ), for EMV contact and EMV contactless systems. It is based on a simple set of primitives to ease L2 integration onto a payment application (alias L3).
...
Pin pad management: refer to manufacturer’s SDK to integrated use cases related to pin entry. Most of the time, proprietary callbacks must be defined using specific software signatures
Transit features: use manufacturer’s SDK to realize transit use cases. For example, if using Agnos Framework, refer to Callbacks API.
Table to be updated
Product Version | Online API Documentation | Update | Comments |
|---|---|---|---|
OLA 2.1.6 | First online API version |
...
Our Agnos for COTS architecture allows customers having their own EntryPoint to integrate our kernels .
Customer API makes direct call to OLA API via Kotlin language .
Customer EntryPoint will do SELECT and FINAL SELECT . Once FCI + Kernel ID identified , this will be sent to AMADIS OLA API (via ola_contactless_add_aid_supported) via Customer API (please see confluence page for normal flowAgnos for COTS Integration Guidance - Application selection bypass )
Link beetween between GPI and Agnos L2 Stack :
if customer wants to go to L2 Certification , Amadis Agnos L2 stack provides events sends via callback to the GPI , customer will need to create Link beetween between GPI and Customer Middleware which allow via a Listener to implement special events like BIP , message DISPLAY , LED .
See the confluence page below for more details regarding Application Selection bypass
...