CloudPOS SDK: Difference between revisions
Line 50: | Line 50: | ||
== wizarView == | == wizarView == | ||
* [ftp://sdkuser:wizsdkar@ftp.wizarpos.com/ | * [ftp://sdkuser:wizsdkar@ftp.wizarpos.com/device/TMSManual.pdf wizarView User Guide] |
Revision as of 07:31, 7 September 2020
Introduction
For developing payment applications, please refer to Device API > Java API. For the development of EMV payment application, please refer to EMV Payment . For code scanning, please refer to Bar code > Scanning Service Usage.
EMV Payment
Bar code
Device API
There are three layers of device API: C API, JNI API and Java API.
Java API
The Java API is packaged as an AAR library file that Android developers can easily use. You can download the latest AAR library file from the link below.
JNI API
The JNI interface wraps the C API to help Java developers use the C API. We recommend that you use the Java API instead of the JNI API.
C API
C API related header files and so libraries have been included in the system. Application developers can create native so libraries through C API to implement their business logic. As a result, the implementation will be more secure than the Java implementation. For example, the EMV library can use the C API.
Permissions
To access any financial devices of the terminal, the application must apply the relevant permissions in the manifest file.
- Permissions definition
Printer Usage
The printer of the terminal supports ESC command. Please refer to the following specifications:
Full Screen
- Using system API to make full screen
- Use the API provided by Android to make full screen
- Disable home key