Exchanging Message Data
In this section you will learn about the protocol for exchanging message data between the merchant's client application and ANYpay POS.
Exchanging Messages with ANYpay POS
The integration of a merchant's system with ANYpay POS is facilitated by socket based XML message interchange in accordance with an XML schema definition.
Single Socket Option
The single socket option enables a merchant to open a connection to ANYpay POS, send a transaction and then the socket is closed by ANYpay POS. The merchant’s system must send an XML transaction request message directly to a defined port on the ANYpay POS workstation or server. Message data must be wrapped in the ASCII STX and ETX control characters. The format is . After sending the request, the client must maintain the IP connection and begin listening for the response. The client must not close the connection until a response is received.
Multiple Socket Option
The multiple socket option enables a merchant to use an open socket connection for a specified period of time configured during setup so that multiple transactions can be sent before the socket is closed by ANYpay POS. Message data must be wrapped in the ASCII STX and ETX control characters.The format is .
HTTP(S) Option
The single http(s) option enables a merchant to open a http(s) connection via a specific url on ANYpay POS, send a transaction and wait for the response from ANYpay POS. The merchant’s system must send an XML transaction request message directly to a url using POST on the ANYpay POS workstation or server. The client must not close the connection until a response is received.
Updated almost 5 years ago