Payment App: Difference between revisions

Latest revision as of 05:18, 13 February 2026

Quick Start

Demo Video

paymentapptest.mp4

User Guide

PaymentInterfaceAppUserGuide.pdf

Demonstration steps(Connect terminal to PC, test through by serial port)

Install Payment Apps, apps can install through by ADB, or push through by TMS.
Set protocal type in Payment app, refer to PaymentInterfaceAppUserGuide.pdf
Connect terminal to PC
Start serial port tool in PC
Send handshake command data through by serial port tool, refer to TestData
Send Transaction command data through by serial port tool, refer to TestData

Debug tools in Windows

Serial port tool-- Download from Microsoft Store
Serial/Socket tool -- Payment Serial/Socket debug tool Spec of the tool

Develop resource

Protocol

Please refer to the protocol which communicate with payment app.

WIZARPOSPaymentAppIntegrationProtocolV2.2.2.6.pdf

Payment Apps

The two payment apps need install to terminal firstly.

Local Integration(No need develop POS APP)

Suitable for scenarios where no application development on the POS terminal is needed. Instead, the Vendor Machine communicates directly with the OPC. In this case, communication between the POS terminal and the Vendor Machine supports serial port, MDB (Multi-Drop Bus), and Socket protocols.

Reference for data packaging and unpacking of VM：Serial&SocketDemo240910.zip
See also, local-integration

Internal Integration(develop POS APP)

It is suitable for developing normal applications on the terminal. It can call the AIDL interface provided by the PAYwizard application to do different transaction. It communicate with the Vendor Machine.

Reference for calling PAYwizard AIDL interface：APP project:PayMentAIDLDemo-guide to call PAYwizard aidl interface
Download APK
See also, internal-integration

Payment App development

It is suitable for developing payment application on the terminal. This payment application interacts with the bank and provides the AIDL interface of the payment function to the PAYwizard to call.

A simple service demo which provided AIDL interface.

WIZARPOSPaymentAppAIDLManualV1.0.5.pdf, if running above service demo, the bind package name should be com.wizarpos.aidlservicedemo.

OPCPaymentIntegrationScheme2025.pdf, description of the scheme.

Others

Cloud Mode

Best practice for payment in D22(D3)/Q3(Q2)

Install the new accessory agent on D22(D3)/Q3(Q2)
Install initconnectionmode on D22/Q3, configure master and slave. This step is usually pre-initialized at the factory and does not require further configuration by the customer.
Install PAYwizard app on D22/Q3
Set protocal of PAYwizard to DEFAULT on D22, and set the payment package name to com.wizarpos.opc
Set protocal of PAYwizard to USB ACCESSORY on Q3, and set the payment package name to com.wizarpos.paywizard.demo

MDB Internal Communication Protocol

MDB_Version_4-3.pdf

FAQ

Simple prototype file, generally, configure this file in TMS, Simple parameters-Prototype xml file. Package name of the payment app is "com.wizarpos.paywizard.demo"
Full prototype file, don't use this file, just for a reference, Full parameters-Prototype xml file
To configure app paramter, pelase read this "Configure a Parameter File with a Template" chapter of the spec, package name which accept the parameter is "com.wizarpos.opc".
learn-kiosk-mode
Kiosk+Home+Launcher demo
Disable home button
SDK AAR
cloudpossdkV1.7.5.1_javaDoc.zip
serial-port-development
Install APP
Apply APP Certificate
Sign APP
Apply TMS Account
TMS Manual

@@ Line 4: / Line 4: @@
 ===User Guide===
 * [https://ftp.wizarpos.com/payment/PaymentInterfaceAppUserGuide.pdf PaymentInterfaceAppUserGuide.pdf]
-===Demonstration steps(Connect terminal to PC)===
+===Demonstration steps(Connect terminal to PC, test through by serial port)===
 * Install Payment Apps, apps can install through by ADB, or push through by TMS.
 * Set protocal type in Payment app, refer to PaymentInterfaceAppUserGuide.pdf
@@ Line 11: / Line 11: @@
 * Send handshake command data through by serial port tool, refer to [https://ftp.wizarpos.com/advanceSDK/test.txt TestData]
 * Send Transaction command data through by serial port tool, refer to [https://ftp.wizarpos.com/advanceSDK/test.txt TestData]
 ===Debug tools in Windows===
 * Serial port tool-- Download from Microsoft Store
-* Serial/Socket tool -- [https://drive.google.com/file/d/1zDeboNelN5zhDsjldgXw7fCt5FgEhOw6/view?usp=sharing Payment Serial/Socket debug tool] [https://ftp.wizarpos.com/payment/windowsserial&socketguide.docx Spec of the tool]
+* Serial/Socket tool -- [https://ftp.wizarpos.com/techsupport/ticket/OPC_DEMO_RELEASE_20260203.rar Payment Serial/Socket debug tool] [https://ftp.wizarpos.com/payment/windowsserial&socketguide.docx Spec of the tool]
 ==Develop resource==
 ===Protocol===
 Please refer to the protocol which communicate with payment app.
-* [https://ftp.wizarpos.com/advanceSDK/PaymentApp/WIZARPOSPaymentAppIntegrationProtocolV2.2.2.pdf WIZARPOSPaymentAppIntegrationProtocolV2.2.2.pdf]
+* [https://ftp.wizarpos.com/payment/WIZARPOSPaymentAppIntegrationProtocolV2.2.2.6.pdf WIZARPOSPaymentAppIntegrationProtocolV2.2.2.6.pdf]
 ===Payment Apps===
 The two payment apps need install to terminal firstly.
-* [https://ftp.wizarpos.com/payment/PayWizard_Demo_V2.1.3_2512111.apk PayWizard_Demo_V2.1.3_2512111.apk]
+* [https://ftp.wizarpos.com/payment/PayWizard_Demo_V2.2.5_2602121.apk Payment Emulator]
-* [https://ftp.wizarpos.com/payment/OPC_V2.1.5-global-release.apk OPC_V2.1.5-global-release.apk]
+* [https://ftp.wizarpos.com/payment/OPC_V2.4.0-global-release.apk PAYwizard2.4.0.apk]
-=== Local Integration ===
+=== Local Integration(No need develop POS APP) ===
-Suitable for scenarios where no application development on the POS terminal is needed. Instead, the Vendor Machine communicates directly with the Payment App. In this case, communication between the POS terminal and the Vendor Machine supports serial port, MDB (Multi-Drop Bus), and Socket protocols.
+Suitable for scenarios where no application development on the POS terminal is needed. Instead, the Vendor Machine communicates directly with the OPC. In this case, communication between the POS terminal and the Vendor Machine supports serial port, MDB (Multi-Drop Bus), and Socket protocols.
 * Reference for data packaging and unpacking of VM：[https://ftp.wizarpos.com/advanceSDK/PaymentApp/Serial&SocketDemo240910.zip Serial&SocketDemo240910.zip]
 * See also, [https://smartpossdk.gitbook.io/paywizard-open-api/semi-integration/local-integration local-integration]
-===Internal Integration===
+===Internal Integration(develop POS APP)===
-It is suitable for developing applications on the terminal. When this application uses the payment function, it only calls the payment AIDL interface provided by the payment application. Other functions of the application are implemented by the application itself.
+It is suitable for developing normal applications on the terminal. It can call the AIDL interface provided by the PAYwizard application to do different transaction. It communicate with the Vendor Machine.
-* Reference for calling payment AIDL interface：[https://github.com/SmartPOSSamples/PayMentAIDLDemo PayMentAIDLDemo]
+* Reference for calling PAYwizard AIDL interface：[https://github.com/SmartPOSSamples/PayMentAIDLDemo APP project:PayMentAIDLDemo-guide to call PAYwizard aidl interface]
+* [https://ftp.wizarpos.com/payment/PayMentAidlDemo_release_V1.0.6_20260114.apk Download APK]
 * See also, [https://smartpossdk.gitbook.io/paywizard-open-api/semi-integration/internal-integration internal-integration]
 ===Payment App development===
-It is suitable for developing payment application on the terminal. This payment application interacts with the bank and provides the AIDL interface of the payment function to the terminal payment OPC call. Please contact sales for guidance from the development team.
+It is suitable for developing payment application on the terminal. This payment application interacts with the bank and provides the AIDL interface of the payment function to the PAYwizard to call.
+[https://github.com/SmartPOSSamples/AidlServiceDemo A simple service demo which provided AIDL interface].
-[https://ftp.wizarpos.com/advanceSDK/PaymentApp/AIDLServiceDemo240910(ProvidedAIDLtoOPC).zip A simple service demo which provided AIDL interface].
+[https://ftp.wizarpos.com/techsupport/ticket/WIZARPOSPaymentAppAIDLManualV1.0.5.pdf  WIZARPOSPaymentAppAIDLManualV1.0.5.pdf, if running above service demo, the bind package name should be com.wizarpos.aidlservicedemo].
-[https://ftp.wizarpos.com/advanceSDK/PaymentApp/IntegrationdocwithOPC.zip IntegrationdocwithOPC.zip(include above demo and the protocal document)].
+[https://ftp.wizarpos.com/payment/OPCPaymentIntegrationScheme2025.pdf  OPCPaymentIntegrationScheme2025.pdf, description of the scheme].
 ==Others==
+===Cloud Mode===
+* Integrate flow, please refer to https://smartpossdk.gitbook.io/paywizard-open-api/cloud-api/quick-start-cloud-api
+* [https://github.com/SmartPOSSamples/PaywizardCloudAPIDemo.git A simple android demo which access the cloud API to do transaction. Actually, users can develop any http project to access Cloud API, the demo is only a reference].
+* [https://github.com/SmartPOSSamples/PaywizardDemo A simple java demo which access the cloud API to do transaction. Actually, users can develop any http project to access Cloud API, the demo is only a reference].
+===Best practice for payment in D22(D3)/Q3(Q2)===
+* Install [https://ftp.wizarpos.com/payment/AccessoryAgentHostService-master-release-v1.0.30-r20251208115422-q1_platform.apk the new accessory agent] on D22(D3)/Q3(Q2)
+* Install initconnectionmode on D22/Q3, configure master and slave. This step is usually pre-initialized at the factory and does not require further configuration by the customer.
+* Install PAYwizard app on D22/Q3
+* Set protocal of PAYwizard to DEFAULT on D22, and set the payment package name to com.wizarpos.opc
+* Set protocal of PAYwizard to USB ACCESSORY on Q3, and set the payment package name to com.wizarpos.paywizard.demo
+===MDB Internal Communication Protocol===
 * [https://ftp.wizarpos.com/advanceSDK/MDB_Version_4-3.pdf MDB_Version_4-3.pdf]
 ==FAQ==
-*Simple prototype file, generally, configure this file in TMS, [https://ftp.wizarpos.com/payment/opc-v2.1.5-config-simple-20251119.xml Parameters-Prototype xml file：opc-v2.1.5-config-simple-20251119.xml]. Package name of the payment app is "com.wizarpos.paywizard.demo"
+*Simple prototype file, generally, configure this file in TMS, [https://ftp.wizarpos.com/payment/opc-v2.2.5-config-simple-20251217.xml Simple parameters-Prototype xml file]. Package name of the payment app is "com.wizarpos.paywizard.demo"
-*Full prototype file, don't use this file, just for a reference, [https://ftp.wizarpos.com/payment/opc-v2.1.5-config-all-20251119.xml Parameters-Prototype xml file：opc-v2.1.5-config-all-20251119.xml]
+*Full prototype file, don't use this file, just for a reference, [https://ftp.wizarpos.com/payment/opc-v2.4.0-config-all-20260130.xml Full parameters-Prototype xml file]
-*To configure app paramter, pelase read this "Configure a Parameter File with a Template" chapter of the [https://smartpossdk.gitbook.io/cloudpossdk/faq/tms-wizarview/accept-tms-file-downloads spec], please use prototype file- opc-v1.7.0-config-simplify-20250814.xml, package name which accept the parameter is "com.wizarpos.opc".
+*To configure app paramter, pelase read this "Configure a Parameter File with a Template" chapter of the [https://smartpossdk.gitbook.io/cloudpossdk/faq/tms-wizarview/accept-tms-file-downloads spec], package name which accept the parameter is "com.wizarpos.opc".
 *[https://smartpossdk.gitbook.io/cloudpossdk/faq/advance-sdk/learn-kiosk-mode learn-kiosk-mode]
 *[https://github.com/SmartPOSSamples/KioskDemo.git Kiosk+Home+Launcher demo]