Connectivity

Connectivity details for Payment Express customers.

Ecommerce connectivity

Payment Express provides two separate environments for the testing and general use of ecommerce solutions. Each solution connects to Payment Express using a different endpoint.

Live transaction environment

PxPay https://sec.paymentexpress.com/pxaccess/pxpay.aspx

PxPost https://sec.paymentexpress.com/pxpost.aspx

Web Service https://sec.paymentexpress.com/WS/PXWS.asmx

PxFusion https://sec.paymentexpress.com/pxf/pxf.svc

Test transaction environment

PxPay https://uat.paymentexpress.com/pxaccess/pxpay.aspx

PxPost https://uat.paymentexpress.com/pxpost.aspx

Web Service https://uat.paymentexpress.com/WS/PXWS.asmx

PxFusion https://uat.paymentexpress.com/pxf/pxf.svc

Card Accepter connectivity

Payment Express provides two separate testing and general use environments for the IPP350, IWL250, and unattended SCR card readers provided by Payment Express. 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

                <HostInterface>
                                <Id>1</Id>
                                <Name>SEC HTTPS</Name>
                                <Priority>2</Priority>
                                <Enabled>1</Enabled>
                                <Type>HTTP</Type>
                                <Address>https://sec.paymentexpress.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.paymentexpress.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.paymentexpress.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>uat.paymentexpress.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 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.paymentexpress.com/pxmi3/pos.aspx

Port 443

TCP Communication to/from terminal:

Address scr.paymentexpress.com

Port 65

Test transaction environment

HTTPS Communication to/from POS:

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

Port 443

TCP Communication to/from terminal:

Address uat.paymentexpress.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.0/23 (203.207.60.1 -> 203.207.61.254)

103.232.204.0/23 (103.232.204.1 -> 103.232.205.254)

202.167.253.113/28 (202.167.253.113 -> 202.167.253.126)

45.75.195.0/27 (45.75.195.1 -> 45.75.195.30)

4.15.244.193/27 (4.15.244.193 -> 4.15.244.222)

38.125.44.0/24 (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 Payment Express 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.