Payment App: Difference between revisions
No edit summary |
|||
| Line 36: | Line 36: | ||
* See also, [https://smartpossdk.gitbook.io/paywizard-open-api/semi-integration/internal-integration internal-integration] | * 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. | |||
[https://github.com/SmartPOSSamples/AidlServiceDemo 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]. | |||
==Others== | |||
===Cloud Mode=== | ===Cloud Mode=== | ||
* Integrate flow, please refer to https://smartpossdk.gitbook.io/paywizard-open-api/cloud-api/quick-start-cloud-api | * Integrate flow, please refer to https://smartpossdk.gitbook.io/paywizard-open-api/cloud-api/quick-start-cloud-api | ||
| Line 47: | Line 55: | ||
* Set OPC to DEFAULT on D22, and set the payment packet name to com.wizarpos.opc | * Set OPC to DEFAULT on D22, and set the payment packet name to com.wizarpos.opc | ||
* Set OPC to USB ACCESSORY on Q3, and set the payment packet name to com.wizarpos.paywizard.demo | * Set OPC to USB ACCESSORY on Q3, and set the payment packet 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] | * [https://ftp.wizarpos.com/advanceSDK/MDB_Version_4-3.pdf MDB_Version_4-3.pdf] | ||
Revision as of 06:27, 19 January 2026
Quick Start
Demo Video
User Guide
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.
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 OPC application to do different transaction. It communicate with the Vendor Machine.
- Reference for calling payment(OPC) AIDL interface：APP project:PayMentAIDLDemo-guide to call OPC 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 terminal payment OPC call. Please contact sales for guidance from the development team.
A simple service demo which provided AIDL interface.
Others
Cloud Mode
- Integrate flow, please refer to https://smartpossdk.gitbook.io/paywizard-open-api/cloud-api/quick-start-cloud-api
- 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.
- 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 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 OPC on D22/Q3
- Set OPC to DEFAULT on D22, and set the payment packet name to com.wizarpos.opc
- Set OPC to USB ACCESSORY on Q3, and set the payment packet name to com.wizarpos.paywizard.demo
MDB Internal Communication Protocol
FAQ
- Simple prototype file, generally, configure this file in TMS, Parameters-Prototype xml file：opc-v2.2.5-config-simple-20251217.xml. Package name of the payment app is "com.wizarpos.paywizard.demo"
- Full prototype file, don't use this file, just for a reference, Parameters-Prototype xml file：opc-v2.3.2-config-all-20260116.xml
- To configure app paramter, pelase read this "Configure a Parameter File with a Template" chapter of the spec, please use prototype file- opc-v1.7.0-config-simplify-20250814.xml, 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