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:
| Terminal API for booking and data communication |
| Content Delivery Network (CDN) for static assets such as images, fonts, and application resources. |
| Endpoint for app updates and health checks. |
Adyen Payment Processing
For payment terminals managed via Adyen, the following network rules must be in place:
| Primary domain for Adyen payment processing services. |
| Secondary domain for Adyen's payment-related operations |
Local port | 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
EloView 3 (EV3)
Elo devices managed through EloView 3 require the following network configuration and whitelisting to ensure full communication.
| API endpoint for device communication |
| Management portal for device configuration and administration |
| Content delivery for digital signage |
| Endpoint for device-specific operations and firmware updates. |
| Data synchronisation queue handling |
| Elo server IP Address |
| Elo server IP Address |
| Content Delivery Network and security services utilised by Elo systems |
EloView 4 (EV4)
Elo devices managed through EloView 4 require the following URLs whitelisted to ensure full communication.
| API endpoint for token management, OTA updates, and OS360 warranty checks |
| Provisioning service for device setup and enrollment |
| MQTT Broker for real-time device communication |
| Endpoint for log uploads, OTA builds, and private content transfer |
| Content delivery service for device icons and assets |
| OAuth service for device authentication and login |
| Recommended AWS Cognito identity service for device management |
| Recommended AWS Cognito user pool service for authentication |
| Recommended S3 bucket for promotional content delivery |
| Recommended S3 bucket for scanning and related content delivery |
| NTP service for device time synchronisation |
| Alternative NTP service for device time synchronisation |
| Remote support and device access service used for troubleshooting |
| 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:
| Main domain for Google Cloud services |
| Google APIs required for operational and logging purposes |
| 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.