Connectivity

Connectivity details for Windcave customers.


Card Accepter connectivity

Windcave provides two separate testing and general use environments for the attended and unattended SCRs, Secure Card Readers, provisioned by Windcave. Please note that terminals are set up to work in either the production or the testing environment and cannot be used to access the other. All terminals should use HTTPS and use TCP as back up.

The pxscrcontroller_cgf.txt file contains XML, which allows merchants to configure the settings of their terminal; correct set up for the live and testing environments will have the following tags.

Live transaction environment

Test transaction environment

By default, both HTTPS and TCP are enabled. If there are issues with HTTPS, the connection will fail over to TCP; the Priority tag controls this behavior.


Host Initiated Transaction API connectivity

Please note that transactions using the HIT API can only be performed using TCP connection between the card readers and PX, however all communication between the POS and PX must be performed using HTTPS Posts.

Live transaction environment

HTTPS Communication to/from POS:

Address https://sec.windcave.com/pxmi3/pos.aspx

Port 443

TCP Communication to/from terminal:

Address scr.windcave.com

Port 65

Test transaction environment

HTTPS Communication to/from POS:

Address https://uat.windcave.com/pxmi3/pos.aspx

Port 443

TCP Communication to/from terminal:

Address uat.windcave.com

Port 65


IP Ranges

For merchants who restrict traffic to specific endpoints, please ensure the below IP ranges are white listed.

203.207.60.1 -> 203.207.61.254

103.232.204.1 -> 103.232.205.254

202.167.253.113 -> 202.167.253.126

89.187.105.193 -> 89.187.105.206 (To be removed after 25 June 2019 21:00 UTC)

45.75.195.1 -> 45.75.195.30 (Replacing above range as of 25 June 2019 21:00 UTC)

4.15.244.193 -> 4.15.244.222

38.125.44.1 -> 38.125.44.254

IMPORTANT: If you restrict traffic and the IP ranges listed are not allowed, this could impact connectivity to us.

Although this list should not change often, if you do restrict outbound IPs please be aware that any changes of this nature are announced via our Status Page.

We recommend that you subscribe to stay up-to-date with important changes.

DNS Cache

Some applications may cache DNS for extended periods. We would advise for any applications, which connect to Windcave endpoints that you confirm your applications DNS cache settings. As an example, older Java versions will never refresh DNS entries and will only pick up DNS changes after the application is restarted. Other applications may ignore the TTL values entirely and set their own values. We recommend that you check your application DNS cache/TTL settings to ensure the application will honor the DNS TTL values provided.