This document is intended as a reference guide with instructions, recommendations and/or best practices of the Appetize Technologies, Inc. (herein referred to as “Appetize”) platform. This document is intended for use by any personnel involved with installation, use, support, and/or maintenance of the Appetize platform. The reader should be familiar with the Appetize platform, current technology, and basic networking concepts.

• Data Flow Diagram
• Network Connectivity
• Network Bandwidth
• Network Endpoints
  • Ports
  • IP Addresses
  • Appetize DNS Dependencies
  • Device Management
  • Elo Devices
• Payment Device Management Technical Resources

Warranties

Appetize Technologies, Inc. makes no warranty with regard to this material. Any information in this guide is subject to change without notice. No part of this guide may be reproduced or transmitted in any form or by any means without expressed written permission of Appetize Technologies, Inc. Best efforts will be made to ensure the information in this guide is correct and complete, however Appetize Technologies, Inc. shall not be liable for errors contained herein or for damages in connection with the use of this guide.

Please contact Appetize Technologies, Inc. for a copy of the current version of this guide and all other documentation.

Trademarks

All trademarks are property of their respective owners.

Contact

Appetize Technologies, Inc.
6601 Center Dr W, Los Angeles, CA 90094
support@appetize.com

Data Flow Diagram

Network Connectivity

Appetize hardware communicates directly with the server to perform nearly all functions. The Appetize client hardware communicates with the server over a standard network connection, using 802.3 wired Ethernet, 802.11 wireless networking or cellular technology. Traffic sent over a secure connection always uses the currently recommended security protocol, which is, as of the date of this document, TLS 1.2 across all endpoints.

Network Bandwidth

A variety of variables contribute to the bandwidth requirements which can be estimated more concisely through the Appetize estimation process.  Generally, bandwidth required to support the Appetize system is estimated at approximately 30Kbps per terminal.

Network Endpoints

Ports

This is the current list of ports used by the Appetize platform as of the date of this document.

IP Addresses

This is the current list of URLs and IP addresses used by the Appetize platform as of the date of this document. Hostname or URL is strongly preferred since most of the services are load-balanced and can return a different IP via DNS lookups.

Appetize DNS Dependencies

Previously, when looking up “api.appetizeapp.com”, a single IP would be returned, even though three were assigned to api.appetizeapp.com: 1.2.3.4, 1.2.3.5, 1.2.3.6, for example. A firewall could do a lookup and get "54.85.232.179", and would whitelist that IP. However, the POS client doing the same lookup would get: 34.195.45.87, but the firewall would block it, because it only opened up the 54. IP.

Currently, when looking up api.appetizeapp.com, all three IPs are returned, and one is selected and utilized at random. If that one fails, it automatically tries the second, and so forth.

Device Management

This is the current list of endpoints used for device management which could include features such as application installation, software upgrades, remote device updates and other administrative tasks. While these endpoints are not required for the operation of the Appetize platform per se, it is strongly recommended to allow these connections.

As with the Appetize IP addresses above, these could change if there is a CDN or load balancer used to deliver the service.

Gateway (FuseBox) End-Points:

• Simplify uses port 7000 to reach out to Fusebox gateway, in all versions, using TLS1.2 over TCP/IP.
• Custom application calls DIRECTLY to Fusebox gateway need to use port 7500 instead, with TLS1.2 over TCP/IP.