CloudPOS SDK: Difference between revisions

From wizarPOS
No edit summary
No edit summary
Line 1: Line 1:
== Device API ==
== Device API ==
There are three layers of device API, the lower layer is C, the device provid C interface, and the third app to write their own JNI source by calling the C interface.
There are three layers of device API, the lower layer is C, the device provides C interface, and the third-party app writes their own JNI source by calling the C interface.
The middle layer is JNI interface, wizarPOS write JNI source and generate the device so files, so the third app just use the JNIInterface to finish the calling.
The middle layer is JNI interface, wizarPOS writes JNI source and generates the device so files, so the third-party app just uses the JNIInterface to finish the calling.
The upper layer is Java interface, wizarPOS provide Java interface for the third app, the third app only need to import the .aar pakcage to their libs.
The upper layer is Java interface, wizarPOS provides Java interface for the third-party app, the third-party app only needs to import the .aar pakcage to their libs.
The app should request [[permissions]] in manifest file.  
The app should request [[permissions]] in manifest file.  
*[[permissions]] defination
*[[permissions]] defination

Revision as of 02:14, 19 November 2018

Device API

There are three layers of device API, the lower layer is C, the device provides C interface, and the third-party app writes their own JNI source by calling the C interface. The middle layer is JNI interface, wizarPOS writes JNI source and generates the device so files, so the third-party app just uses the JNIInterface to finish the calling. The upper layer is Java interface, wizarPOS provides Java interface for the third-party app, the third-party app only needs to import the .aar pakcage to their libs. The app should request permissions in manifest file.

C API

JNI API

Java API

Payment EMV

Barcode

Full Screen

Advance SDK