Nets / Baxi

Install and configure the Nets bridge (OmniumNetsBridge) for Nets card terminals connected via ethernet or USB.

Architecture

[In-Store App]
      │ HTTP :5100 (localhost only)
      ▼
[OmniumNetsBridge]         ← Windows service, C:\OmniumNetsBridge
      │ XML/TCP :6000
      ▼
[BaxiAgent]                ← Windows service from Nets
      │ TCP :6001 (ethernet) or USB/serial
      ▼
[Nets terminal]
      │ TCP :9670
      ▼
[Nets servers 91.102.24.111]

Port	Listened by	Connected by	Purpose
`5100`	OmniumNetsBridge	In-Store App	REST payment API
`6000`	BaxiAgent	OmniumNetsBridge	ECR protocol
`6001`	BaxiAgent	Nets terminal	Terminal connection (ethernet)
`9670`	Nets servers	BaxiAgent	Card authorisation

Step 1 — OMS: add the payment method

Log in to Omnium back office
Go to Settings → Payment methods
Add a payment method named exactly NetsTerminal
Assign it to the correct market and store

The name is case sensitive — NetsTerminal must be written exactly as shown.

Step 2 — Install BaxiAgent

Run the BaxiAgent MSI installer from Nets. Installs to C:\Program Files (x86)\Nets\NetsBaxi\.

Step 3 — Install OmniumNetsBridge

Prerequisites: Windows 10 or later (64-bit), Administrator access

Download omnium-nets-baxi-bridge-<version>.zip from the Omnium installation files folder in Google Drive
Extract the zip file — this gives you a publish-win folder
Open PowerShell as Administrator and allow script execution for this session:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

Navigate to the extracted folder and run the installer:

cd C:\path\to\publish-win
.\install-bridge.ps1

On first install, appsettings.json opens automatically in Notepad. Set TerminalId to the serial number printed on the back of the terminal. Save and close.
When asked whether to delete the source folder, answer y — the bridge files are copied to C:\OmniumNetsBridge.

appsettings.json is always preserved when updating. Run install-bridge.ps1 again to update.

Step 4 — Open firewall ports

New-NetFirewallRule -DisplayName "OmniumNetsBridge" -Direction Inbound -Protocol TCP -LocalPort 5100 -Action Allow
New-NetFirewallRule -DisplayName "BaxiAgent ECR"    -Direction Inbound -Protocol TCP -LocalPort 6000 -Action Allow

The terminal and cashier PC must be on the same network. The PC needs a fixed IP — either via a DHCP reservation in the router, or a static IP set in Windows (ncpa.cpl → adapter properties → TCP/IPv4).

Additional firewall rule:

New-NetFirewallRule -DisplayName "BaxiAgent Terminal" -Direction Inbound -Protocol TCP -LocalPort 6001 -Action Allow

Configure BaxiAgent for ethernet — open C:\Program Files (x86)\Nets\NetsBaxi\appsettings.json:

{
  "BaxiSettings": {
    "AgentServerPort": 6000,
    "BaxiCorePort": 6001,
    "LinkTimeout": 7000,
    "UseSerialPort": false
  },
  "HostSettings": {
    "HostPort": 9670,
    "HostIpAddress": "91.102.24.111"
  }
}

HostSettings points to Nets' servers. The IP above is for the test environment. For production, Nets provides the correct HostIpAddress.

On the terminal, set:

Field	Value
ECR IP	IP address of the cashier PC
ECR Port	`6001`

The terminal has two IP fields. ECR IP = the cashier PC's IP. Host IP = Nets' server IP — do not change this.

Restart BaxiAgent after saving:

Restart-Service BaxiAgentService

USB / serial

Open Device Manager → Ports (COM & LPT) and note the COM port number. Then configure BaxiAgent:

{
  "BaxiSettings": {
    "AgentServerPort": 6000,
    "BaxiCorePort": 6001,
    "LinkTimeout": 7000,
    "UseSerialPort": true,
    "SerialPort": "COM3"
  },
  "HostSettings": {
    "HostPort": 9670,
    "HostIpAddress": "91.102.24.111"
  }
}

Replace COM3 with the actual port number. Restart BaxiAgent after any config change:

Restart-Service BaxiAgentService

Step 6 — Configure the In-Store App

In the app, go to Settings → Terminal and set:

Setting	Value
Terminal type	Nets / Baxi
Bridge address	`127.0.0.1`
Bridge port	`5100`
Payment method name	`NetsTerminal`

Verification

# Services running
sc query OmniumNetsBridge
sc query BaxiAgentService
 
# Ports listening
netstat -ano | findstr "5100\|6000"
 
# Terminal connected via ethernet (should show ESTABLISHED)
netstat -ano | findstr "6001"

Bridge status check — open in a browser on the cashier PC:

http://127.0.0.1:5100/payment/status

A response of {"isConnected":true,"isReady":true} confirms the bridge is up and the terminal is ready.

Updating

Download the new zip from Google Drive Omnium installation files, extract it, and run install-bridge.ps1 again. appsettings.json is always preserved on update.

Logs

Component	Log location
OmniumNetsBridge	`C:\OmniumNetsBridge\logs\bridge-YYYYMMDD.log`
BaxiAgent	`C:\baxi\logfiles\agent\Agent_YYYY-MM-DD.log`

Stream the current log live (replace date):

Get-Content C:\OmniumNetsBridge\logs\bridge-20260521.log -Wait

Troubleshooting

Bridge service not starting

Run the exe directly to see error output in the console:

Stop-Service OmniumNetsBridge
cd C:\OmniumNetsBridge
.\Omnium.Nets.BaxiBridge.exe

Terminal not connecting — ethernet

Check	Command
BaxiAgent running?	`sc query BaxiAgentService`
Firewall rule for port 6001?	`netsh advfirewall firewall show rule name="BaxiAgent Terminal"`
ECR IP set correctly on terminal?	Must be the PC's IP — not Nets' host IP
Terminal and PC on same network?	`ping <terminal-ip>`

Terminal not connecting — USB

Open Device Manager — the COM port number may have changed after a restart
Confirm "UseSerialPort": true and the correct "SerialPort" value in BaxiAgent config

Reconfigure the bridge

# Edit C:\OmniumNetsBridge\appsettings.json, then:
Restart-Service OmniumNetsBridge

BaxiAgent logs

C:\baxi\logfiles\agent\Agent_YYYY-MM-DD.log
C:\baxi\logfiles\baxilogAppl_YYYY-MM-DD.log
C:\baxi\logfiles\baxilogLink_YYYY-MM-DD.log