CloudPOS SDK: Difference between revisions

From wizarPOS
Line 24: Line 24:
* [[EMV Flow]]
* [[EMV Flow]]
* [http://www.emvlab.org/emvtags/ EMV tag info]
* [http://www.emvlab.org/emvtags/ EMV tag info]
* [ftp://sdkuser:wizsdkar@ftp.wizarpos.com/EMVSample_180511.zip EMV Sample]
* [ftp://sdkuser:wizsdkar@ftp.wizarpos.com/EMVSample_180525.zip EMV Sample]


== Barcode ==
== Barcode ==

Revision as of 08:42, 20 June 2018

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. 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 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 app should request permissions in manifest file.

C API

JNI API

Java API

Payment EMV

Barcode

Full Screen

Advance SDK