Vending (WiFi or Ethernet) Network Requirements
Updated
Print

Purpose

This document explains the basic, high-level network requirements for connecting an AirVend, PicoVend, or PicoVend Mini to a local network via WiFi or Ethernet.

The following provides all essential networking, port, and IP requirements for a network engineer to make necessary changes to a host network.  All the following Fully Qualified Domain Names (FQDN) or specific IP address listed below are required for the vending devices to function correctly.

 

Network Requirements

All connections are initiated from the vending device and the below FQDN, IPs, and Ports need to be open for outgoing bidirectional communication

Google Cloud Messaging: For security purposes, the IP address for the Google Cloud Messaging service is constantly changing and is not a fixed address. Also, there is no official publication of the IP addresses. We normally advise against defining IP addresses on the firewall for this purpose. Instead, we suggest either allowing all outbound connections to http & https or defining the DNS addresses as permitted destinations for traffic through the firewall.

SERVICE DESCRIPTION DESTINATION FQDN/IP PORTS
AV Live Back-end communication including product info and sales transactions

live.app.air-vend.com (173.45.110.115)

services.air-vend.com (173.45.110.114)

products.air-vend.com (173.45.110.114)

prod.nutrition.air-vend.com (173.45.110.114)

TCP: 80,443
       
Google Cloud Messaging Real-time push updates & remote device commands   TCP: 5228, 5229, 5230
       

Heartland Payment Systems (HPS)

(PCI 3.1 Compliant)

(not needed for industrial vending applications)

Credit Card Processing

Test credit cards: https://posgateway.cert.secureexchange.net/Hps.Exchange.PosGateway/PosGatewayService.asmx

Production charging of cards: https://posgateway.secureexchange.net/Hps.Exchange.PosGateway/PosGatewayService.asmx

TCP: 443