News

NCR Secure Pay moving to use AWS (Amazon Web Services) *Updated 1/24/18*

 

Secure Pay Moving to AWS - Action Required

NCR Secure Pay has moved the production service to use AWS, effective 10/16/2018.  

The IP addresses for our public DNS names have changed, but the host names themselves will remain the same – ps.ncrsecurepay.com  and ws.ncrsecurepay.com.

AWS provides a pool of public IP addresses that may be assigned to our servers. The full list can be found below and should be used for firewall rules and whitelisting purposes where needed. The list may seem long, but we do not have control over the public IPs assigned by AWS. For those who would like more information on AWS’s public IPs, visit https://docs.aws.amazon.com/general/latest/gr/aws-ip-ranges.html. 

Now that we have made the move to AWS, merchants need to have their systems already configured for the new AWS IP ranges to ensure uninterrupted processing through Secure Pay.

 

AWS IP Ranges: 

18.208.0.0/13
52.95.245.0/24
54.196.0.0/15
216.182.224.0/21
216.182.232.0/22
107.20.0.0/14
67.202.0.0/18
184.73.0.0/16
3.80.0.0/12
54.80.0.0/13
54.221.0.0/16
54.156.0.0/14
54.236.0.0/15
54.226.0.0/15
52.90.0.0/15
100.24.0.0/13
54.210.0.0/15
54.198.0.0/16
52.20.0.0/14
52.200.0.0/13
54.160.0.0/13
35.153.0.0/16
52.70.0.0/15
52.94.248.0/28
52.54.0.0/15
54.152.0.0/16
54.92.128.0/17
52.0.0.0/15
184.72.128.0/17
23.20.0.0/14
18.204.0.0/14
54.88.0.0/14
54.204.0.0/15
52.86.0.0/15
52.44.0.0/15
18.232.0.0/14
54.174.0.0/15
50.16.0.0/15
35.168.0.0/13
174.129.0.0/16
72.44.32.0/19
34.224.0.0/12
54.224.0.0/15
75.101.128.0/17
34.192.0.0/12
54.208.0.0/15
54.242.0.0/15
216.182.238.0/23
54.234.0.0/15
54.144.0.0/14
52.2.0.0/15
184.72.64.0/18
204.236.192.0/18
52.4.0.0/14
52.72.0.0/15
52.95.255.80/28
50.19.0.0/16
54.172.0.0/15
52.94.248.160/28
13.58.0.0/15
52.15.0.0/16
18.220.0.0/14
18.191.0.0/16
52.14.0.0/16
18.216.0.0/14
18.188.0.0/16
18.224.0.0/14
52.95.251.0/24
3.16.0.0/14

 

Note: This range of IP addresses does use CIDR notation ("/n") on the addresses to include the full range of IP addresses. If your router does not allow CIDR notation to be entered with the IP address a firmware update or new hardware that will allow this may be necessary

 

Support Notes:

  • Refer to the Counterpoint.log on the station with the failed connection error, to determine the IP that is currently being assigned by AWS for a each affected merchants’ NSP communications, ensure that IP is opened on the firewall, if they must be configured by IP (and cannot be configured by URL/DNS names). NOTE: This IP could change in the future at any time.   

    If this has not been done, error that is returned in Counterpoint is: Error: Connection Timeout. 

    To help identify the current IP addresses being used, in a cmd prompt type: nslookup ps.ncrsecurepay.com to get the current IPs. Note this can change at any time without warning, It is recommended that the full list of IPs / Blocks listed above be opened to avoid payment disruptions in the even this IP changes in the future. 

 

  • For a complete list of IPs to ensure, in the event the IP does change, and to know what range of IPs need to be opened on the firewall, refer to: https://www.site24x7.com/tools/ipv4-subnetcalculator.html and enter the above IP/Blocks from the list above.  

    The entire list of ranges was sent out in the original announcement of the move (also noted above).  There may have been some confusion on how the ranges were listed.  For example 107.20.0.0/14 means that there are 14 bits of variance to that IP address.  107.20.0.0/14 covers all IP addresses between 107.20.0.1 through 107.23.255.254.  This means that all IPs in that range would need to be listed individually, if you are not able to specify a range.

     

 

Posted on: Tue, Oct 16, 2018 at 10:13 AM. This news has been viewed 880 times.