Skip to main content

Network Configuration for Terminal Device Connectivity

Allow access to required domains, IPs, and ports to ensure proper terminal device connectivity and system performance.

Updated over 2 weeks ago

To ensure that all connected terminal devices work properly within your environment, you must allow network access to specific domains, IP addresses and ports.

This guide outlines the necessary endpoints and services that must be permitted through your firewall and network settings.


Ventrata Services

The following domains must be accessible to ensure proper operation of the Ventrata terminal app:

https://api.ventrata.com

Terminal API for booking and data communication

https://cdn.ventrata.com

Content Delivery Network (CDN) for static assets such as images, fonts, and application resources.

https://app.ventrata.com

Endpoint for app updates and health checks.


Adyen Payment Processing

For payment terminals managed via Adyen, the following network rules must be in place:

*.adyen.com

Primary domain for Adyen payment processing services.

*.adyenpayments.com

Secondary domain for Adyen's payment-related operations

Local port 8443

Required for secure local communication between Adyen payment terminals and connected devices.

πŸ“’ NOTE

The asterisk (*) means that all subdomains must be allowed under the specified domain.


Elo Device Management

Elo devices require access to the following endpoints for device management, content updates, and synchronisation:

io.eloview.com

API endpoint for device communication

manage.eloview.com

Management portal for device configuration and administration

content.eloview.com

Content delivery for digital signage

device.eloview.com

Endpoint for device-specific operations and firmware updates.

dsq.eloview.com

Data synchronisation queue handling

74.120.218.144

Elo server IP Address

74.120.218.143

Elo server IP Address

*.cloudflare.com

Content Delivery Network and security services utilised by Elo systems

πŸ“’ NOTE

The asterisk (*) means that all subdomains must be allowed under the specified domain.


Logging and Monitoring Services

To ensure proper error tracking and logging functionality, the following services must be reachable:

cloud.google.com

Main domain for Google Cloud services

*.googleapis.com

Google APIs required for operational and logging purposes

*.sentry.io

Sentry services for real-time error reporting and monitoring

πŸ“’ NOTE

The asterisk (*) means that all subdomains must be allowed under the specified domain.


Additional Recommendations

  • Whitelist vs Open Access: It is highly recommended to specifically whitelist the above domains and IPs rather than broadly opening internet access.

  • SSL Inspection Considerations: If your network uses SSL inspection (HTTPS decryption), ensure that these domains are exempt to avoid connection disruptions.

  • Network Stability: Periodically verify connectivity to these endpoints, especially after firewall updates or changes to your network security policies.

Did this answer your question?