Internal Integration (POS App Development)

From wizarPOS
Revision as of 09:40, 20 March 2026 by Mahong (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

It is suitable for developing normal applications on the terminal. The application can call the AIDL interface provided by the PAYWizard application to perform different types of transactions. In this mode, PAYWizard does not communicate with the Vendor Machine; the self-developed application is responsible for communicating with the Vendor Machine.

Here is a demo app that calls the PAYWizard AIDL interface: PayMentAIDLDemo

Please send and receive data according to this protocal document:Core Protocol

Here is a flowchart

PayMentAidlDemo_release_V1.0.6_20260114

See also, internal-integration

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

For developing applications on the D22.

  • 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
Retrieved from "http://sdkwiki.wizarpos.com/index.php?title=Internal_Integration_(POS_App_Development)&oldid=5515"