CloudPOS SDK: Difference between revisions
Line 18: | Line 18: | ||
There are three layers of device API: C API, JNI API and Java API.<br> | There are three layers of device API: C API, JNI API and Java API.<br> | ||
=== Java API === | === Java API === | ||
Java API is packaged as an AAR library file | 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. | ||
*[http://{{SERVERNAME}}/wizarposapi/ API Spec] | *[http://{{SERVERNAME}}/wizarposapi/ API Spec] |
Revision as of 10:20, 13 March 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.
开发普通支付应用,请参考Device API > Java API, 先获取最新的aar实现包,阅读API Spec,并参考Samples. 开发EMV支付应用,请参考EMV Payment. 扫码,请参考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 wrappers the C API to help the Java developer to use C API.
Now we recommended you to use Java API instead of JNI API.
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. For example, the EMV library can use C API.
Permissions
To get the access of any financial devices of terminal, the application must apply the relevant permissions in the manifest file.
- Permissions definition
Printer Usage
The printer of terminal support ESC commands. Please refer to the specification: