Payment App: Difference between revisions

From wizarPOS
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==
===Protocol===
Please refer to the protocol which communicate with payment app.
* [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.2.5_2602121.apk Payment Emulator]
* [https://ftp.wizarpos.com/payment/OPC_V2.4.0-global-release.apk PAYwizard2.4.0.apk]


=== 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.

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.

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

FAQ

Chinese Document