CloudPOS SDK: Difference between revisions

From wizarPOS
Line 1: Line 1:
== Device API ==
== 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.
There are three layers of device API, C API, JNI API and Java API.
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.
Using any devices of terminal, the application must declare the permission in the manifest file.
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|Permissions]] defination
*[[permissions|Permissions]] defination

Revision as of 09:32, 22 November 2018

Device API

There are three layers of device API, C API, JNI API and Java API. Using any devices of terminal, the application must declare the permission in the manifest file. The app should request permissions in manifest file.

C API

The C API offers header files definition and the relevant so library is already included in the system. The application developers can create the native so library by the C API to implement their business logic. So the implementation will be more secure than Java implementation.

JNI API

we offer JNI interface to wrapper the C API to help the developer to use C API. Now we recommended you to use Java API instead of JNI API.

Java API

Java API is packaged as an aar library file, it can be used by Android developer easily. You can download the latest aar library file from below link.

Payment EMV

Barcode

Full Screen

Retrieved from "http://sdkwiki.wizarpos.com/index.php?title=CloudPOS_SDK&oldid=709"