zrsPOSManual
HomePricingAppsPortuguês
Contents

Put SAGE on the internet

A guided task for the merchant or their SAGE partner. Every "SAGE can't be reached" problem in SAGE connection opens it with Show me how.

Why it is needed. Your Sage 50c runs on your own network; zrsPOS runs in the cloud. For zrsPOS to issue documents, the SmartAPI must answer on the internet.

What must be true at the end

  1. The SmartAPI answers on a fixed public address: a static IP or a DDNS name that always points to your connection.
  2. The address starts with https and the certificate is valid: not self-signed, not expired, and issued for the name used.
  3. The address does not redirect to another address; the one you save in SAGE connection is the final one.
  4. The API key is issued and kept private.

You do not need to allow any zrsPOS address in the firewall. zrsPOS does not call from a fixed address, so there is none to allow. What protects the API is the key and https.

Steps for whoever manages the network

  1. Find the port the SmartAPI listens on (for example 5581) and check it works from inside the network.
  2. Give the connection a fixed public address: ask your provider for a static IP, or set up a DDNS name.
  3. On the router or firewall, forward that port to the server where Sage runs.
  4. Put a valid https certificate on the address (a certificate for the DDNS or domain name used). A reverse proxy in front of the SmartAPI is a common way to do it.
  5. Test from outside your network, for example from a phone on mobile data: the address should answer.
  6. Give the merchant the address and the access key. In SAGE connection they enter both and press Save: it tests them first.

In zrsPOS

The page Put SAGE on the internet lists the same four steps: send your SAGE partner their page, ask them for the address and the access key, enter them in SAGE connection and save, then press Check again here. Check again is the connection test: it says SAGE answered. This is done., or why not yet.

If it still fails

Each failure has its own page; SAGE connection shows the one that applies:

Still stuck? Write to support@zrspos.com with the address (never the key) and the title the page shows.