Page 6 of 27
2 Operation
The POS initiates a transaction request to Windcave by sending an HTTPS POST request as an XML message to the
appropriate URL. See below section 2.1 (Endpoints & Firewall Considerations) for a list of URLs.
Windcave responds to the request, either immediately or after a congurable timeout period of a few seconds; after
receiving a response, the POS will continue to make Status requests until the Status response indicates that the
transaction is Complete (Complete value is returned as “1”) in Result.
Status responses from Windcave may contain instructions for the POS to permit information to be displayed for the
merchant (DL1, DL2) and enablement of buttons that may be used by the POS to interrupt the transaction or provide
feedback for example signature capture.
Note: For any new integrations, the POS must handle the entry of new users. POS applications are typically used by
many different customers.
As each customer has one or more HIT API users, a key part of POS development is ensuring that new user HIT
API credentials can be easily added into the POS and that the development credentials are not hard coded in any
way. Please ensure the API credentials conguration within the POS are also password protected or has some lev-
el of authorised access challenge.
2.1 Endpoints & Firewall Considerations
The POS can communicate with the Payment Host using HTTPS on the addresses below. Please ensure that your
network can accommodate this access.
Production: https://sec.windcave.com/pxmi3/pos.aspx
Test: https://uat.windcave.com/pxmi3/pos.aspx
The Windcave HIT terminal communicates with the Windcave Host using TCP on the addresses below. Please en-
sure that your network can accommodate this access.
Production: scr.windcave.com port 65
Test: uat.windcave.com port 65
To Next Page
Loading...