Local Integration (External Device): Difference between revisions

From wizarPOS
No edit summary
No edit summary
 
Line 1: Line 1:
Suitable for scenarios where no application development on the POS terminal is needed. Instead, the Vendor Machine communicates directly with the PAYWizard. In this case, communication between the POS terminal and the Vendor Machine supports serial port, MDB (Multi-Drop Bus), and Socket protocols.  
Suitable for scenarios where no application development on the POS terminal is needed. Instead, the Vendor Machine communicates directly with the PAYWizard. In this case, communication between the POS terminal and the Vendor Machine supports serial port, MDB (Multi-Drop Bus), and Socket protocols.  
Apart from the MDB communication method, all data transmission and reception shall be carried out in accordance with the protocol document:[[Core Protocol]].
* Reference for data packaging and unpacking of VM:[https://ftp.wizarpos.com/advanceSDK/PaymentApp/Serial&SocketDemo240910.zip Serial&SocketDemo240910.zip]
* Reference for data packaging and unpacking of VM:[https://ftp.wizarpos.com/advanceSDK/PaymentApp/Serial&SocketDemo240910.zip Serial&SocketDemo240910.zip]
* See also, [https://smartpossdk.gitbook.io/paywizard-open-api/semi-integration/local-integration local-integration]
* See also, [https://smartpossdk.gitbook.io/paywizard-open-api/semi-integration/local-integration local-integration]

Latest revision as of 05:59, 5 March 2026

Suitable for scenarios where no application development on the POS terminal is needed. Instead, the Vendor Machine communicates directly with the PAYWizard. In this case, communication between the POS terminal and the Vendor Machine supports serial port, MDB (Multi-Drop Bus), and Socket protocols. Apart from the MDB communication method, all data transmission and reception shall be carried out in accordance with the protocol document:Core Protocol.