Configure Your Network

This guide covers what the payment terminal needs to communicate with Market Pay: outbound firewall access to our services, and how the terminal gets an IP address on your network. For the local link between your POS and the terminal, see Connect your terminal to POS.

There are two things to set up here, plus an option for staying online:

  • Firewall access: so terminals and POS apps can reach Market Pay services.
  • The terminal's IP address: so it can authorize payments and your POS can reach it.
  • Connectivity resilience: how to keep taking payments if the internet drops.

1. Allow outbound access to Market Pay services

Terminals and POS applications must reach three Market Pay services over outbound HTTPS. Whitelist the hostnames below in your firewall.

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

Environment Hostname IP addresses TCP ports
Preproduction tntms.novelpay.pl 135.125.51.112 443, 8453, 4747, and 14747
Production ntms.novelpay.pl 176.119.39.127

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

Environment Hostname IP addresses TCP ports
Preproduction preprod.mpg.market-pay.com 185.203.232.51 and 185.203.233.51 50456, 50460, and 50457
Production prod.mpg.market-pay.com 185.203.232.52 and 185.203.233.52

RKI (Remote Key Injection) — enables remote encryption-key injection.

Environment Hostname
Production rki.paxitalia.com

Warning

Whitelist by hostname, not by IP address : Market Pay's IP addresses can change over time, and hard-coded IPs will eventually break connectivity.

2. Give the terminal an IP address

The terminal needs a valid IP address to authorize payments online. How it should get that address depends on how your POS communicates with it:

If your integration uses… Assign the IP by…
Cloud communications Dynamic IP, without DHCP reservation
Local communications DHCP reservation, or a static IP

Tip

Where you use DHCP, set the lease time to 24 hours or more so the terminal keeps a stable address.

Methods for IP assignment

  • Dynamic IP: your DHCP server issues an address to the terminal on the fly.
  • DHCP reservation: you bind a fixed address to the terminal's MAC address on the DHCP server, so it always receives the same one, a scalable alternative to static IPs across many terminals.
  • Static IP: you enter the address and network details manually on the terminal.

Note

You cannot mix dynamic and static. The terminal, DNS server, and router addresses must be all dynamic or all static. DHCP is enabled by default.

Set a static IP on the terminal

If you use local communications and cannot use DHCP reservation, disable DHCP and set a static IP:

  1. On the connected terminal, open the NTMS Agent.
  2. Select Settings and enter the Admin & Settings passcode.
  3. Enter your network details:
    1. Terminal IP address (unique on the network)
    2. Subnet mask
    3. Router IP address
    4. Preferred (DNS1) and alternate (DNS2) DNS server addresses
  4. Select Save to confirm.

Note

For a USB (local) link, the terminal also exposes a fixed interface at 192.168.42.129. Setting that up is covered in Connect your terminal to POS.

3. Keep taking payments when the internet drops

If a transaction is declined because of a connection problem, there are two ways to keep processing while your primary internet is unavailable:

  • Cellular failover: transactions run over the cellular connection of a 4G terminal (with an activated SIM) or a cellular router when the primary link fails.
  • Offline transactions: continue processing with no store internet at all. Contact your Account Manager to enable this.
    • Availability: offline payments are supported only for local communications or App-to-App integrations.

Warning

With offline payments, you are fully liable for the risk of failed captures, chargebacks, and disputes.

Next steps