General
- A supported payment terminal
- An available network cable (RJ-45 end on a CAT-5/6/6e cable) connected to an existing network.
NOTE: Some credit card terminals support a wireless connection, this is possible to use, but wired is always preferred for reliability. - LAN connections should have a 1ms ping response time with less than 0.1% packet loss on average.
- Internet connections for having a ping response time to Google of less than 50ms and less than 0.5% packet loss on average.
- If you are providing a “segmented” network to separate the POS terminals from the payment devices you MUST:
- Be able to ping the payment terminal from the POS device
- Be able to ping the IP of the credit card processing company from the payment terminal
- These need to be tested and operational before we will start our work
- If you don’t know what a “segmented” network is, then this likely does not apply to you
- If you restrict outbound traffic with a firewall see the Firewall Ports section below and attached are the list of Ports, URL's and IP Addresses that required by PAX.
Firewall Ports
Description | Web Address | Port |
---|---|---|
Card Defender Activation | api.card-defender.com eapi.cloudretailer.com | 443 |
PAX Store Configuration URL | t.paxstore.us | 9080 |
PAX BroadPOS Configuration URL | t.broadpos.com | 9120 |
North (Formerly NAB) Authorization URL | secure.epx.com | 8075 |
TSYS Authorization URLs | ssl2.vitalps.net ssl3.vitalps.net | 5003 5003 |
TSYS BroadPOS Configuration URL | 40.128.76.76 | 9020 |
Heartland Authorization URLs | api2.heartlandportico.com api2-e.heartlandportico.com | 443 443 |
Heartland BroadPOS Configuration URL | 184.73.218.146 | |
FirstData Authorization URL | prod.dw.us.fdcnet.biz/sd/srsxml.rc | 443 |