Payment App: Difference between revisions

From wizarPOS
Line 4: Line 4:
===User Guide===
===User Guide===
* [https://ftp.wizarpos.com/payment/PaymentInterfaceAppUserGuide.pdf PaymentInterfaceAppUserGuide.pdf]
* [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.
* Install Payment Apps, apps can install through by ADB, or push through by TMS.
* Set protocal type in Payment app, refer to PaymentInterfaceAppUserGuide.pdf
* 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 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]
* Send Transaction command data through by serial port tool, refer to [https://ftp.wizarpos.com/advanceSDK/test.txt TestData]
===Debug tools in Windows===
===Debug tools in Windows===
* Serial port tool-- Download from Microsoft Store
* Serial port tool-- Download from Microsoft Store

Revision as of 07:12, 4 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

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

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

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.

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

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.

IntegrationdocwithOPC.zip(include above demo and the protocal document).

Others

FAQ

Chinese Document

Retrieved from "http://sdkwiki.wizarpos.com/index.php?title=Payment_App&oldid=5439"