Payment App: Difference between revisions
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
==[[Core Protocol]]== | ==[[Core Protocol]]== | ||
==[[Payment Apps]]== | ==[[Payment Apps]]== | ||
==[[Local Integration (External Device)]]== | |||
==[[Internal Integration (POS App Development)]]== | |||
==[[Payment App Development]]== | |||
==[[Cloud Mode Integration]]== | |||
==Develop resource== | ==Develop resource== | ||
=== Local Integration(No need develop POS APP) === | === Local Integration(No need develop POS APP) === | ||
Revision as of 02:34, 5 March 2026
Quick Start
Windows Debug Tools
Core Protocol
Payment Apps
Local Integration (External Device)
Internal Integration (POS App Development)
Payment App Development
Cloud Mode Integration
Develop resource
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.
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
- 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 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
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