CloudPOS SDK: Difference between revisions

From wizarPOS
(Undo revision 1520 by Jeff (talk))
(Undo revision 1521 by Jeff (talk))
Line 37: Line 37:
*[[error code|Error code]]
*[[error code|Error code]]
*[[header files|Header files]]
*[[header files|Header files]]
*[[JNI Samples|Samples]]
*[[C API Samples|Samples]]


=== Permissions ===
=== Permissions ===

Revision as of 13:08, 14 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 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 get the access of any financial devices of terminal, the application must apply the relevant permissions in the manifest file.

Printer Usage

The printer of terminal support ESC commands. Please refer to the specification:

Full Screen

Wizarview