Skip to main content

Network issues

  • Updated

General information

To use Softpay app the device is required to have an active and stable internet connection for both continuous operation as well as during processing.

The basic tests below can be performed by anyone to test the most common connectivity issues.

Basic connectivity tests

If Softpay app cannot reach Softpay online services, try the following

  • switch off device WiFi and use cellular only (4G, 5G, etc.) and try again in Softpay.
  • switch on device WiFi and switch cellular off and try again in Softpay.
  • Verify whether you can open https://api.softpayapp.io/api-gateway/v1/public in a browser on the device. If succesful the page will show a technical message like {"requestId":"..."}.

Basic network stability testing

A quick and basic test is to use e.g. https://packetstats.com/ while walking around with a device to ensure that there is continuous network coverage in all areas where these devices are intended to be used. Do note that this only provides a basic light-weight test for network coverage at that particular moment in time as the noise floor for wireless networks will change based on customer footfall.

Commercial solutions are recommended for proper network quality assurance.

Firewall rules

As a minimum Softpay app must be able to contact the following domains outgoing on port 443:

  • Sandbox: api.sandbox.softpay.io
  • Production: api.softpayapp.io
  • Sandbox & Production: googleapis.com

Further we recommend opening port 443 for outgoing to:

  • Sandbox & Production: crashlytics.com

IP based rules?

Softpay does not offer IP-based rules for firewall allow-listing / white-listing. Please use domain-based rules.

Testing

Use curl with the verbose flag set to call the domains listed.

Example using api.softpayapp.io:

curl -v https://api.softpayapp.io

Failure is defined by: "Failed to connect"
Success is defined by: "Connected to..."

Proxy

To enable proxy support in-app go to Settings and enable Proxy. The app will restart and now supports the proxy defined on the network interface.

The proxy being used must support SSL pinning for proxy connections to function properly.

Testing a proxy connection

Use curl with verbose flag and proxy settings to get api.softpayapp.io and look for the certificate details to verify that the Softpay certificate makes it all the way.

curl -v --proxy "http://proxy_server:proxy_port" https://api.softpayapp.io/

Replace proxy_server:proxy_port with your proxy server IP and port.

Response should look like the following (at time of writing) and can be verified by visiting softpayapp.io in your browser and comparing the information.

* Server certificate:
*  subject: C=DK; L=K�benhavn; O=Softpay ApS; CN=api.softpayapp.io
*  start date: Jul 29 00:00:00 2025 GMT
*  expire date: Aug 29 23:59:59 2026 GMT
*  subjectAltName: host "api.softpayapp.io" matched cert's "api.softpayapp.io"
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
*  SSL certificate verify ok.

 

Related articles