PAX S300

PAX S300 Reference Photos

PAX S300

The left wire is the power cable, ethernet plugs into thered port

Installing a PAX S300

The installation process for a S300 is fairly simple on the POS side. In most cases one simply needs to specify the IP address that each POS station needs to send its credit card transactions to.

Currently Hotsauce only supports TSYS processing on PAX devices. The setup for TSYS TransIT/Multipass merchants requires an additional setup to set up. Please see the TSYS TransIT/Multipass section of the documentation for additional steps.

Setting up each POS station

In order to assign a chip reader to each POS station we must first adjust the .ini file on each POS station.

The ini. file can be found through File Explorer -> C: -> Hotsauce -> Hotsauce.ini

At the very bottom of the .ini file there is a field specifying a terminal's emv DeviceID. By default a terminal's DeviceID corresponds with its POS number (ie. POS1 has DeviceID=1, POS2 has DeviceID=2, etc.). If there is a chip reader for the SERVER, it will have the highest DeviceID.

If this field does not exist in the .ini you can add it to the very bottom. Below is a sample of what it will look like:

Setting up the database

Now that we've assigned a DeviceID to each terminal, we need to specify the IP address of the chip reader that it points to. These DeviceID to IP Address settings is stored in a SQL table call tblEmvDevices. There are two ways to edit this table: through merchant setup in Back Office or through SQL Server Management Studio (SSMS).

Device Config through Back Office is only available on Hotsauce version 7.2.6.9 and later. To access it, login and go to Hotsauce -> System -> System Config -> Credit Card Setup -> Device Config. You will be prompted for a password.

To add a new device select 'ADD'. A setup through Device Config is shown to the right:

To setup a device through SSMS, login go to hotsauce -> Tables -> tblEmvDevices -> Edit Top 2000 Rows. To add a device, simply start filling out the fields in order starting with device_type. Once each relevant field is entered, select 'Execute' at the top or right click the red exclamation point and select 'Execute'. creation_time, creation_use, update_time, and update_user will all auto populate upon executing. Below is a sample entry on tblEmvDevices.

Note that IP addresses by default are static and start at .131 corresponding to POS number

Setting up the chip reader

Now that we've set up the database we just configure each chip reader to the proper IP address. Follow the steps below to set each chip reader to a static IP address:

1) Menu

2) Password is the current date: MMDDYYYY

3) Down. Communication.

4) Password is the current date: MMDDYYYY

5) Down. Down. LAN Parameters

Once we've gotten to the LAN parameters setting, we will need to adjust a few fields:

6) LAN Type -> Static

7) IP Address -> 192.168.XXX.13X Where X is your IP scheme and POS number

8) Subnet Mask -> 255.255.255.0

9) Gateway -> 192. 168.XXX.1 Where X is your IP scheme. Run ipconfig in cmd to check for weird setups

10) DNS1 -> 192.168.XXX.1 Same as your gateway

11) DNS2 -> 8.8.8.8.

For PAX S300 devices there is an additional step that we must take to ensure that it is communicating using the proper method. To set the ECR Comm Type of each device follow the steps below:

1) Menu

2) Password is the current date: MMDDYYYY

3) Down. Communication.

4) Password is the current date: MMDDYYYY

5) Down. Down. ECR Comm Type

6) Ethernet

7)Port 10009

8) TCP/IP

In order to test that each chip reader is connected properly to the Hotsauce network, run an IP/Network Scan. You should also try and ping the IP of each chip reader from their corresponding POS station to ensure it is able to communicate with the chip reader.

Switching to EMV

For merchants using chip readers for the first time you will have to enable EMV from Back Office. Remember to restart FOH on all POS terminals after switching to EMV. Be sure to check if the merchant needs tabs functionality and enable those settings when switching to EMV.

Testing the Chip Reader

If possible we ALWAYS want to test the following functionalities of a chip reader:

1) Transaction

2) Void

3) Tip Adjustment

4) Settlement

The first 3 can always be done but the last we can only really attempt at the start or end of a merchant's business day.

Page updated

Report abuse