CloudPOS SDK: Difference between revisions
| Line 19: | Line 19: | ||
*[http://{{SERVERNAME}}/wizarposapi/ API Spec] | *[http://{{SERVERNAME}}/wizarposapi/ API Spec] | ||
*[[Java Samples|Samples]] | *[[Java Samples|Samples]] | ||
*[[ftp://sdkuser:wizsdkar@ftp.wizarpos.com/cloudpossdk.aar | *[[ftp://sdkuser:wizsdkar@ftp.wizarpos.com/cloudpossdk.aar CloudPOS SDK AAR Download]] | ||
== Payment EMV == | == Payment EMV == | ||
Revision as of 09:29, 21 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.
- Permissions defination
- WizarPOS printer ESC commands