Windcave | Connectivity | EFTPOS | Payment Gateway | Online Credit & Debit Card Processing

Connectivity

Connectivity details for Windcave customers.

Card Accepter connectivity

Windcave provides two separate testing and general use environments for the pinpads, and unattended SCR card readers provided 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_cfg.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

                <HostInterface>
                                <Id>1</Id>
                                <Name>SEC HTTPS</Name>
                                <Priority>2</Priority>
                                <Enabled>1</Enabled>
                                <Type>HTTP</Type>
                                <Address>https://sec.windcave.com/scr.aspx</Address>
                                <Port>443</Port>
                </HostInterface>
                <HostInterface>
                                <Id>2</Id>
                                <Name>SCR TCP</Name>
                                <Priority>1</Priority>
                                <Enabled>1</Enabled>
                                <Type>TCP</Type>
                                <Address>scr.windcave.com</Address>
                                <Port>65</Port>
                </HostInterface>

Test transaction environment

	  
<HostInterface>
                                <Id>1</Id>
                                <Name>UAT HTTPS</Name>
                                <Priority>2</Priority>
                                <Enabled>1</Enabled>
                                <Type>HTTP</Type>
                                <Address>https://uat.windcave.com/scr.aspx</Address>
                                <Port>443</Port>
                </HostInterface>
                <HostInterface>
                                <Id>2</Id>
                                <Name>UAT TCP</Name>
                                <Priority>1</Priority>
                                <Enabled>1</Enabled>
                                <Type>TCP</Type>
                                <Address>uatscr.windcave.com</Address>
                                <Port>65</Port>
                </HostInterface>

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 IPP/IWL and Windcave, however all communication between the POS and Windcave must be performed using HTTPS Posts.

Live transaction environment

HTTPS Communication to/from POS:

Address https://sec.windcave.com/hit/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/hit/pos.aspx

Port 443

TCP Communication to/from terminal:

Address uatscr.windcave.com

Port 65

Ecom connectivity

REST API connectivity

All requests should follow HTTP/1.1 specification; full reference available here: https://tools.ietf.org/rfc/rfc2616.txt

HTTPS is used exclusively; connections using HTTP only will fail. You will need to support TLS1.2 or better currently.

Windcave domains are detailed here

For more details and specifications, please refer to the Windcave REST API reference

Legacy APIs connectivity

Details can be found below -

Note: windcave.com is the domain that should be used.

We recommend that any endpoints using the paymentexpress.com domain be changed to windcave.com.

sec.paymentexpress.com --> sec.windcave.com

scr.paymentexpress.com --> scr.windcave.com

IP Ranges

For merchants who restrict traffic to specific IP or endpoints, please email support.

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.