Versions Compared

Old Version 3

changes.mady.by.user Olivier Chauvineau

Saved on

compared with

New Version 4

changes.mady.by.user Olivier Chauvineau

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.

Image Added

Native Option 

Pros

  • To enforce a physical model that clearly separates the POS from the POI functions leading to a better stability of the payment stack (improves integrability from POS perspective)

  • To structure the development of a generic payment stack independent from the merchant environment and the platform (enables reusability)

  • To enable complex payment architectures development such as centralized payment function

Cons

  • To implement a Sales to Payment protocol or Interface (integrator may leverage on existing protocols)

 

 

Java Option

Pros

  • Faster implementation (lower short-term costs)

  • Java expertise is more common in the Android community (mitigates staffing risk)

Cons

  • The “L3”

certificability is exposed as new POS features might impact the certified POI mechanisms (exposes certificability)

  • The payment stack is coupled with the underlying technology (no JVM available on secure payment terminals but C tool chain available on Android)