Purpose

The purpose of this article is to outline the Network Requirements for U1F Castle Credit Card Reader for Dining Installations. For full Network Requirements pertaining to Dining, please see Network Requirements - 365Dining, ReadyTouch, and MM6 Mini Dining.

Please Note: The U1F Castle Reader must have a wired Ethernet Cable connection.

 

Process

General Network Configuration Guidelines

• Device must be connected to the same router as the kiosk.
• Device should not be routed through a switch where possible.
• Device cannot be linked to Client’s network.
   

IP Addressing Requirements

The device supports DHCP configuration. Options include:

1. DHCP (Recommended)
   • Automatically assigns IP address, subnet mask, gateway, and DNS.
   • Simplifies deployment.
   • Ensure available DHCP scope on correct VLAN.
2. Static IP (Optional)
   • For fixed installations where devices must be addressable internally (for management, monitoring or firewall rules), support or professional services will assign a static IP.
   • Ensure the IP is outside the DHCP range of your network to avoid conflicts.
      

Firewall & Port Requirements

The following outbound network access must be permitted:

• TCP 443 (HTTPS) – Required for secure payment communication
• UDP/TCP 53 (DNS) – Required for hostname resolution
• UDP 123 (NTP) – Required for time synchronization
   

Power

The following power supply configurations are supported:

1. Dedicated Power Brick (Recommended).
   • The reader can be powered using a dedicated power adapter (power brick) installed inside the kiosk.
   • The power brick connects to the internal kiosk power source.
      
2. Spliced from Monitor Power Supply.
   • The reader may be powered by splicing into the existing monitor power supply within the kiosk.
     • Splice cable will be provided.
   • Provides space for additional equipment that needs power.
      

Network Diagram