Moneris is conducting an infrastructure update that will change external facing Internet Protocol (IP) addresses to improve our systems and services.
Moneris sends notices of such updates using the merchant notification contact emails listed on file in the Moneris Gateway Merchant Resource Center (MRC).
To see the list of contacts on file for your account please proceed to:
Once logged in, please select the Admin menu à Notification. This page displays all emails on file for this account that will receive direct email communications from Moneris. To add more contacts for future notifications, please do so here.
Moneris also posts notices of such changes on the Moneris Developer Portal and Community Blog page.
Links for these posts can be found below:
NOTE: The command may vary based on Windows vs Linux vs other OS/system
Email communications were sent out to all notification contact email addresses on September 12, 2017 with a follow-up reminder on October 26, 2017. An additional email was sent on February 28 advising that the new IPs would be published on March 28.
Moneris will be changing the Moneris Gateway Canada and US external facing IPs (Internet Protocol) on Wednesday, March 28th, 2018.
Table below shows the old IPs and the new IPs.
Moneris Gateway CA Production
Moneris Gateway US Production
Moneris changed the Moneris Gateway Canada and US external facing IPs (Internet Protocol) in QA on Monday, October 9, 2017.
Table below shows the old IPs and the new IPs that were updated in QA.
Moneris Gateway CA QA
Moneris Gateway US QA
No. The following host addresses remain unchanged and should still be used:
DNS Host URL
This change is applicable to merchants using Moneris Gateway Canada and/or Moneris Gateway US.
Merchants with the following network settings will be impacted:
All Moneris Gateway integration options are impacted, including:
Please consult with:
Please provide these stakeholders with this FAQ.
After the IPs are changed it can take up to 48 hours to take effect as the new IPs are updated across the internet.
This means you may see the impact at different times based on your location and network setup.
For those using the DNS host address, please ensure firewall rules include both the old IPs and new IPs to ensure a smooth transition. Doing so will ensure that your connectivity will not be affected when the new IPs are propagated to your network. We recommend leaving the rules for the old IPs in place as a precaution.
There are 2 scenarios:
How to identify?
What change will merchant need to make?
Merchants using IPs as destination host (i.e., as opposed to DNS host URL)
Merchant connects to Moneris using the IP instead of the DNS host address.
API static IP example:
Connect using https://220.127.116.11/gateway2/servlet/MpgRequest
Update to use the appropriate DNS host URL instead of IP. This is the recommended method of connecting to Moneris.
Canada Production DNS Host URL: www3.moneris.com
US Production DNS Host URL: esplus.moneris.com
NOTE: If you choose to continue to use static IPs to connect, then you must update to the new IPs provided.
Merchant uses whitelisted IPs
In this instance, a Merchant must identify and speak with a network administrator that manages the network to verify if firewall rules have been setup to block internet traffic.
Merchant must white list the new IPs. This means firewall rules need to be setup, internal routing set up, etc.
This change will only impact merchants using static IPs or whitelists. In these cases, if the IPs are not properly updated, merchant will not be able to connect to Moneris Gateway. Failure to update could cause the following errors:
Unfortunately Moneris cannot revert back. All merchants must use the new IPs and must update their systems appropriately.
All merchant must use the new IPs. However, Moneris recommends that you keep the firewall rules for the old IPs in place as a precaution.
Use the below commands to help identify if the IP changes have been applied to your environment.
To run these commands in a Windows environment click on the Start button and type cmd in the search box to open the Windows Command Line.
telnet 18.104.22.168 443
You may also perform the trace route command if allowed in your environment. Perform the below trace route examples and compare OLD IP trace to NEW IP trace to see what the last hop that you are able to hit.
Command Line Command
telnet 22.214.171.124 443 gives blank screen as mentioned below.
After the change telnet 126.96.36.199 443 should give blank screen
telnet 188.8.131.52 443 gives blank screen as mentioned below.
Perform the below command to see what your system is resolving the IP address to.
Perform the following command to see what your system is resolving the IP address to:
Nslookup www3.moneris.com is resolved to 184.108.40.206 as mentioned below.
After the change Nslookup www3.moneris.com should be resolved to 220.127.116.11
Nslookup esplus.moneris.com is resolved to 18.104.22.168 as mentioned below.
After the change Nslookup esplus.moneris.com should be resolved to 22.214.171.124