Configure Your Network

This guide provides the necessary network specifications and steps for configuring your terminals and POS applications to communicate securely with Market Pay services.

1. Firewall whitelisting rules

To ensure secure communication, you must configure your firewall to whitelist outgoing HTTPS traffic from your POS applications and terminals to the following services.

NTMS (Nexo Terminal Management System): Manages all terminal settings and application updates.

MPG (Market Pay Gateway): Processes and routes all transactions.

RKI (Remote Key Injection): Enables remote key injections for encryption.

⚠️ Warning: do not hard-code Market Pay's IP addresses, as these can change over time

2. Configuring the Terminal IP Address

To send payments for online authorization, the terminal must have a valid IP address.

Methods for IP Assignment

• Dynamic IP: Your DHCP server issues an IP address to the terminal on the fly.

• DHCP Reservation: On the DHCP server, you bind a specific IP address to the terminal's MAC address. The DHCP server then assigns that exact same IP address each time. This is an alternative to using static IP addresses, especially with a large number of terminals.

• Static IP: You enter the IP address and other network configuration details manually on the terminal.

Important: You cannot use a mix of dynamic and static IPs. The IP addresses for the terminal, DNS server, and router must be either all dynamic or all static. By default, DHCP is enabled on the payment terminal.

Recommendations

• DHCP Lease Time: If possible, set the DHCP lease time on your DHCP server to 24 hours or more.

• Cloud Communications: Use dynamic IP addresses without DHCP reservation.

• Local Communications: Use DHCP reservation or manually configure static IP addresses.

Define a Static IP Address in the Terminal

If you are using a local communications integration and cannot use DHCP reservation, you must disable DHCP and define a static IP address.

1. On the connected terminal, open the NTMS Agent.

2. Select Settings and enter the Admin & Settings passcode.

3. Enter your network details:

   • IP address of the terminal (must be unique in the network)

   • Subnet mask of the network

   • IP address of the router

   • IP addresses of the preferred DNS server (DNS1) and the alternate DNS server (DNS2)

4. Select Save to confirm.

Dedicated Local Interface (USB/RNDIS)

In addition to the standard LAN communication setup, your payment terminal exposes a dedicated network interface over USB for local communications. This interface uses a fixed, private IP address and port that can be used to communicate to between POS and POI over USB. Your terminal will require to have a direct internet connection through an ethernet cable (RJ45).

• IP Address: 192.168.42.129

• Port:

  • For integrated mode (with launcher): 7778

  • For mixed mode (payment application directly): 7777

Launcher blocks access to Android menu, settings and payment application for customer, this is the common use cases for POI installed in supermarkets or on Self Check-Out devices. Usage is limited to operation coming from the POS.  

Handling Loss of Internet Connectivity

When a transaction is declined due to a network connection issue, you have two main ways to continue processing transactions when your primary internet connection is unavailable:

• Cellular Failover Connection: Transactions are processed using the cellular connection of 4G payment terminal (if SIM activated) or a cellular router when the primary internet fails.

• Enable Offline Transactions: This allows you to continue processing transactions when the store has no internet connection. Reach out to your Account Manager to enable such feature.

  • Availability: Offline payments are only available for integrations that use local communications or app to app.

    Risk: You are fully liable for the risk of failed captures, chargebacks, and disputes related to offline payments.