Installation Process Overview

Quick overview

Here is a quick overview of the entire installation and setup process:

1. Install/enable Microsoft .NET Framework 3.5 SP1.

2. Install the latest version of Oracle’s Java for Windows.

3. Use the STPISecure to installer to install the STPIClient software.

4. Install the STPIClient license.

5. Start the STPIClient application for the first time.

6. Configure the STPIClient to start as a service (Optional).

7. Configure your POS System.

8. Connect, power up and configure payment terminals.

Before you begin

By default, the payment terminals using SecureTable will communicate with the POS system over TCP port 9999.

• Open TCP port 9999 on the corporate firewall.

• Open TCP port 9999 on the Windows Defender Firewall on the POS system's Back-Office as well as on all POS workstations.

• The wireless network (for wireless payment terminals) needs to be able to communicate with the POS System.

• Each payment terminal needs access to the Internet.

Requirements

• Maitre’D Enhanced EFT option.

Software Requirements

• Any supported Windows operating system with all latest updates.

• Java SE Runtime Environment.

• Microsoft .NET Framework 3.5.

• STPI Client software (included with the STPISecure Installer)

Hardware Requirements

• Payment terminal(s) compatible with the Secure Payment application

• 1 Gbps (Gigabit) Ethernet (wired) network or better.

• WiFi network (802.11 ac or better)

• High-Speed Internet connection.

Install Java for Windows

The STPISecure Installer, the STPISecure client software for SecureTable and the RTI-SIPA plugin for SecurePay requires the installation of Java for Windows software. This can be downloaded and installed for free from Oracle’s Java website.

Please download and install the latest version of Java for Windows for your specific Windows edition (32-bit or 64-bit).

Download PDF

Activate the STPI Secure License

Purchasing a License

Before a license can be activated, it needs to be purchased and created for you. Please contact the PayFacto Boarding team or your local Sales Representative to purchase a STPISecure license.

STPISecure License File

After you have purchased a STPISecure license, the license file will be sent to you as a text file attachment via e-mail. The e-mail will come from the PayFacto Boarding Team or your local Sales Representative.

Install the License File

1. Save the file from the e-mail to your Windows Desktop. Typically, the file is named something like "Licdefault_12345.txt".

2. Rename the file to "Lic.txt". To achieve this, you can right-click the file and select the Rename option, or select the file and press the F2 key on your keyboard.

1. Move the file to the following folder:

C:\Program Files (x86)\PayFacto\STPISecure\STPIClient\

The license activation process is now complete.

Install Microsoft .NET Framework 3.5 SP1

The .NET Framework (pronounced as "dot net") is a software framework developed by Microsoft that runs primarily on Microsoft Windows. Microsoft .NET Framework version 3.5 Service Pack 1 is required before the STPISecure installer can be used to install the STPISecure client or other components, such as the RTI-SIPA plugin.

Enabling Microsoft .NET Framework 3.5 SP1 for Windows 10

On Windows 10, starting with version 1809, Microsoft .NET Framework 3.5 SP1 is included as a standard Windows feature and enabled by default. However, older versions of Windows 10, Enterprise or IoT editions, could be missing this essential component. Here is the procedure to check whether .NET Framework 3.5 SP1 is installed and how to enable it on Windows 10:

1. Click on the Windows 10 Start button and type Control Panel.

2. The Control Panel app should appear as a search result. Click on Open.
3. Within the Control Panel app, click on Programs.
4. Under Programs and Features, select Turn Windows features on or off.
5. The Windows Features list will appear.
6. Look for the feature called .NET Framework 3.5 (includes .NET 2.0 and 3.0).

   1. If this feature is not listed, install .NET Framework manually. (See below)

   2. If you see a black square in this checkbox, .NET Framework 3.5 is already enabled and no further action is required.
   3. If the checkbox is blank, enable it.

1. Click OK on the Windows Features list. This will close the list and apply any changes.

2. Files may be copied and you may be required to restart the PC.

Installing Microsoft .NET Framework 3.5 SP1 manually

For versions of Windows prior to Windows 10 1809, or for some older Enterprise or IoT editions, Microsoft .NET Framework 3.5 SP1 may need to be downloaded and installed manually.

The full installer can be obtained from the official Microsoft download site here:

Download the file and double-click it to start the installation process. Follow the on-screen instructions and restart your PC as required.

Overview

Purpose of this document

This document will cover the configuration required to operate the SecureTable module using the Maitre’D direct integration to the STPI client.

SecureTable

The SecureTable module is a universal middleware platform that provides an EMV-Compliant, Pay at the Table (PATT) processing solution that can be connected to a POS (Point of Sale) system. The solution can work in standalone mode as well as integrated to a Point of Sale (POS) system such as Maitre’D, Veloce, Squirrel, Aloha and Micros among other.

“Pull” architecture

The SecureTable module uses a “Pull” architecture. This means that a payment terminal using the SecureTable module can initiate the transaction process by Pulling check data from the POS system. In other words, after the guest checks are printed and handed to customers, there is no need for the server to walk back to the POS workstation to apply payments and close guest checks. All payments, including credit, debit and cash, can be applied at the table side, and checks are closed automatically.

By comparison, a traditional "Push" architecture is a system where the transaction would be initiated from the POS system, and check data pushed to the payment terminal. In a table-service restaurant, this process often required the customers to get up and walk to the POS workstation to insert their payment card and enter their PIN using a tethered payment terminal.

Accurate payment reporting

The integration of the SecureTable module with various POS systems allows the payment terminal to retrieve guest check data from the POS System. After the payment terminal processes a payment, the SecureTable module sends the payment data back to the POS System for reporting purposes. Payment amounts, tip amounts and card brand used are all automatically transmitted to the POS system to allow for accurate reporting.

Compatible with the SecurePay module

The SecureTable and SecurePay modules can both be used on the same POS system. This allows merchants to use any combination of stationary Pay-at-the-Counter terminals and wireless Pay-at-the-Table terminals. The SecureTable and SecurePay modules share a similar user interface which provides a consistent user experience for customers and employees.

Compatibility with third-party payment terminals

If a third-party solution with tethered (wired) payment terminals is already in place and integrated to the POS system, the SecureTable module can still be used without worry. A configurable table-locking or invoice-locking mechanism prevents accidentally accessing guest checks that are being processed by a payment terminal through the SecureTable module. This means that establishments can, for example, use wireless payment terminals with the SecureTable module in the dining room while using tethered payment terminals for the cashier station, bar, pickup counter and drive-through windows.

Full-featured solution through direct integration

With a direct integration, Maitre’D communicates directly with the SecureTable module’s STPI client through a secure socket connection without using drop-files. This allows Maitre’D to take advantage of all the features offered by the SecureTable module, without the limitations imposed by using the former TPI client middleware.

Topics that are included:

Configuration Settings

The Secure Payment application's SecureTable module has multiple configurable features and functions. The features and functions apply to all Secure Payment modules you may use, including standalone Payment, SecurePay, Gateway (GID), and Gift Cards.

For the SecureTable module, the feature you will most likely need to configure is tipping, but you can access the following configuration menus:

• Accessing Configuration Settings

  • Connection Settings

  • Duplicate Transaction Options

  • Table Search Options

  • Split Calculation Options

  • Select POS Type

• Transaction Management

  • Print Detailed Transaction Report

  • Print Batch Summary Report

• Application Configuration

  • Passwords

  • Tipping and Cashback

  • Printing Options

• Help and Training Tools

  • Training Mode

  • Getting Support

  • Exiting the Application

  • About Secure Payment

Start the STPI Client for the first time

STPI Secure Shortcuts

After the STPISecure installation process, a folder called STPI Shortcuts was created on your Windows Desktop. This folder contains the shortcut that will be used to start the STPI Client software.

Setup the shortcut to run with Administrative privileges

To run correctly, the STPI Secure Client needs to run with Windows Administrative privileges. To achieve this:

1. From the Windows desktop, open the folder called STPI Shortcuts by double-clicking on it.
2. Two shortcuts allow you to start the STPI Client. You can use either STPIClient (Hidden) or STPIClient. Select the shortcut which better meets your desired use case:

   STPIClient

   This shortcut makes the STPI Client run with the command prompt window visible on the screen. This takes up space on the screen and on the Windows taskbar, but allows you to see all the operations going through the STPI Client in real-time.

   STPIClient (Hidden)

   This shortcut allows the STPI Client to run with the command prompt window hidden from view. This frees up space on the screen and Windows taskbar, but the operations going through the STPI Client are not visible.

3. Right-click the shortcut called STPIClient or STPIClient (Hidden), and select the Properties option.
4. The STPIClient or STPIClient (Hidden) shortcut's properties page opens to the Shortcut tab. Click the Advanced... button.
5. Activate the Run as administrator checkbox and click OK.
6. You will be back to the STPIClient (or STPIClient (Hidden)) shortcut's properties page. Click OK to close it.

With this setup, the STPI Secure client will always start with administrative privileges whenever you use this shortcut.

Make the STPIClient start automatically as Windows starts

You can add a copy of the STPIClient or STPIClient (Hidden) shortcut to the Windows startup folder to force the STPI client to start automatically as Windows starts. Here is the procedure to follow with Windows 10:

1. Make sure that hidden files and folders are visible:

   a. From Windows explorer, click on the View menu and make sure that the Hidden Items option is selected from the Show/Hide section.
2. Browse to the following folder:

   C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp

3. Copy the STPISecure or STPISecure (Hidden) shortcut to the StartUp folder.

With this setup, the STPI Client application with automatically start itself if Windows is restarted.

Start the STPI Client application manually

1. Double-click the STPIClient or STPISecure (Hidden) shortcut.

2. you will see a UAC warning. Click Yes.
3. If you selected the regular STPISecure shortcut, a command prompt window will appear, with the Running Admin shell header. You will see text scrolling on the window. If you used the STPISecure (Hidden) instead, you will not see this window and skip directly to the next step.
4. The very first time the STPIClient starts, you will see a Windows Security Alert from the Windows Defender Firewall.

   1. Enable the Domain networks, such as a workplace network option (available only if your PC is part of an Active Directory domain).

   2. Enable the Private networks, such as my home or work network option.

   3. Disable the Public networks option.

   4. Click Allow access.

5. If you selected the STPISecure shortcut, the command prompt window will remain on the screen. You may minimize it, but do not close it.

6. An icon will also be added to the Windows system tray.

Stopping the STPI Client application

Closing the command prompt window

If you are using the STPISecure shortcut, simply close the command prompt window by clicking the "X" in the upper-right corner.

Using the system tray icon

You can also right-click the STPI icon in the system tray and select the Exit option.

Congratulations!

The STPI Client software is now up-and-running on your system.

Media Type mappings for SecureTable or SecurePay

Before you begin

In order to get accurate reporting data with SecureTable or SecurePay, media types known as mappings need to be created for each card brand that will be accepted by the merchant. Before beginning, gather information on all the card brands and payment types that are accepted at the restaurant. Obtain this information from the restaurant owner and managers, and from the restaurant’s credit card processor.

Creating mappings for each card brand

1. Start the Point of Sale Control Module.
2. Click the Payments menu, and select the Media Types… option.

1. The list of all current media types will be displayed. Click the Add button.

1. A blank Media Type window will open directly on the Media Type branch. Configure according to the information below:

Media Type ID #

The Media Type ID number is automatically determined by Maitre’D when the Media Type is created. Maitre’D will always use the lowest available number between #2 and #23 inclusively.

Description

Enter a meaningful description for this media type. This should generally be a card brand name such as Visa, MasterCard, AMEX, etc. This description will be shown on customer receipts and media reports.

Payment Type

Select the Charge option from the drop-down list.

Payment Surplus

• Select Tip Entry if the merchant accepts tips for servers.

• Select NULL if the merchant does not accept tips.

Configure remaining options per the merchant’s needs and preferences.

1. Click on the Option branch.

Print Receipt (Optional)

Enable this option to allow for a receipt to be printed after the transaction has been processed.

Check on Receipt (Optional)

Enable this option to have the detailed check print on the receipt.

Folio

Disabled. This option needs to be disabled for cards to be read properly.

Keyboard Input

Disabled. This option cannot be used since the Folio option above also needs to be disabled.

Included in Report

Enable this option so that this media type is shown in Back-Office reports (Recommended). Disabling this option will cause this media type to be hidden in the reports (NOT recommended).

Open Drawer (Optional)

Enable this option to make the cash drawer open when this media type is used.