...
Note: the interface between the two systems can be either implemented through an API or a protocol.
Design Considerations
So, depending on integrator’s architecture, there are two possible ways to integrate Agnos:
Develop the payment application at Native level
Develop the payment application at Java level
Native Architecture
The native architecture consists in deploying all the payment related components at the NDK level where a C tool chain is available. A JNI bridge (blue) is required at the Java level to enable communication between the two levels and connect the Sales Logic (yellow) to the “L3” Application (green). POS services are exclusively in the Java layer.
...
Java Architecture
The Java architecture consists in deploying exclusively the card processing related components at the NDK level where a C tool chain is available. A JNI bridge (blue) is required at the Java level to enable communication between the two levels and connect the “L3” Application (green) to the OLA API. POS and POI services are deployed in the Java layer.
Native Option
Pros |
|
Cons |
|
Java Option
Pros |
|
Cons |
certificability is exposed as new POS features might impact the certified POI mechanisms (exposes certificability)
|