Maitre’D Software Version Requirements

• Maitre’D version 7.08.000.280 or later.

Software Requirements

• Any supported Windows operating system with all latest updates.

• Java SE Runtime Environment.

• Microsoft .NET Framework 3.5.

• Retail Terminal Interface for Semi-Integrated Payment Applications (RTI-SIPA) plugin. (Included with the STPISecure Installer

Hardware Requirements

• SecurePay-Compatible Payment terminal(s)

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

• WiFi network (802.11 ac or better)

• High-Speed Internet connection.

Installation Process 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 RTI-SIPA plugin.

4. Configure your POS System.

5. Connect, power up and configure payment terminals.

Before you begin

By default, the payment terminals using SecurePay 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.

Install Java for Windows

he 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, Here.

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

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.

1. Within the Control Panel app, click on Programs.

1. Under Programs and Features, select Turn Windows features on or off.

1. The Windows Features list will appear.

1. Look for the feature called .NET Framework 3.5 (includes .NET 2.0 and 3.0).

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

b. If you see a black square in this checkbox, .NET Framework 3.5 is already enabled and no further action is required.

c. 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

or 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:

Microsoft .NET Framework 3.5 SP1

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

The following instructions describes the installation and configuration process for the Maitre’D POS System.

RTI-SIPA Plugin installation

Note for Maitre'D POS users

On a Maitre'D POS system, the latest version of the STPISecure Installer is bundled with each service pack update. To obtain the latest compatible version of the STPI Secure Installer and ensure optimal compatibility, please install the latest service pack update for your Maitre'D POS system.

Once the Maitre'D service pack update is installed, the STPISecure installer will be located here:

C:\POSERA\MaitreD\PRG\Setup

1. Locate the STPISecureX.X.X.X.exe file, then right-click the file and select Run as administrator.

1. You may see a UAC prompt. Click Yes.

1. Please read the End-User Licence Agreement. If you agree with the terms, select I accept the agreement and click Next>.

1. Select the installation destination for STPISecure files. Accept the default path by clicking Next>.

1. Select the components you wish to install and click Next>. A brief description of each available component is provided below. Install only what you need.

STPISecure Component selection

STPI Client v2.x.x.x

This component is required to use the SecureTable application with wireless payment terminals in a table service environment, with a POS system like Maitre'D, Veloce and others. It can be installed alone or alongside RTI-SIPA v1.xx.x.x if a combination of Wireless PATT terminals and fixed terminals are used.

• TPI Client v1.x.x

  This component is only required with older versions of Maitre'D, such as 7.05.x.x. Do NOT install this component with newer versions of Maitre'D.

  Client InstallAsService Guide

  This component is optional and copies documents to the install folder with instructions on how to setup various clients as services.

  MTI v2.30

  This component is required for the Micros POS system only.

  TPixel Client v1.0.12

  This component is required for the Pixel Point POS system only.

  TPosi Client v1.1.0

  This component is required for the Positouch POS system only.

  VirtualTerminal v1.0.1

  This is an optional component that allows for the software to be tested and demonstrated.

  RTI-SIPA v1.xx.x.x

  This component installs the Retail Terminal Interface for Semi-Integrated Payment Application (RTI-SIPA) plugin files for use with the SecurePay application. This component needs to be installed on the POS system's main Back-Office PC as well as on all POS workstations that will manage a payment terminal. It can be installed alone or alongside STPI Client v2.x.x.x if a combination of Wireless PATT terminals and fixed terminals are used.

1. Select the All Others (POS 4) option and click Next>.

1. Fill in the settings for the RTI-SIPA plugin:

Terminal IP address

Type in the IP address of the payment terminal that will be managed by the POS Workstation where this instance of the RTI-SIPA plugin is being installed.

License merchant token

Type in the License Token that was supplied with the STPISecure license.

License postal code / zip code

Type the Canadian Postal Code or U.S. Zip Code of the merchant.

License store ID

Type the store ID or store name as it appears on the documentation that came with the STPI license.

1. The setup wizard is now ready to begin the automated installation process. Review your settings and click the Install button.

1. You will see various progress bars during the installation process. This could take a few minutes.

a. During the installation, you could see the installation of required components like Microsoft C++ 2008 Redistributables. This will only appear if the component is missing from your system. Otherwise, you will not see this.

b. Select I have read and accept the license terms and click Install.

c. A progress bar will be displayed during the installation process.

d. When the process completes, a confirmation will appear. Click Finish.

1. Once the installation completes, you will see the screen pictured below. Click the Finish button.

Generic Media Type Mapping For SecurePay

Before you begin

This configuration is optional for most merchants. Before proceeding, make sure that the main media type and individual media type mappings are created for each accepted card brand.

A generic media type mapping may be required to cover the rare cases where a customer may pay with a card that is accepted by the merchant, but not already configured as a mapping in Maitre'D media types. If a dedicated media type mapping does not already exist, the payment would be recorded against the main media type, generally called "CREDIT/DEBIT". The goal of the generic mapping is to have such payments recorded against a media type with a more meaningful name, something like "Other Card Payment" for instance.

Creating the Generic mapping

1. Logon to the Maitre’D Back-Office with appropriate credentials. (Distributor or System Owner)

1. Start the Point of Sale Control Module.

1. 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. For the Generic mapping, this could be Other Card Payments or something similar. 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.

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.

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

1. Click on the Card Property branch.

EFT Category

Set this drop-down list to Other EFT.

Type

Set this drop-down list to Credit.

Discount Rate

This option is not supported with EMV protocols and semi-integrated protocols like SecureTable or SecurePay. Leave this value at 0.00.

Tips Credit Fees

Enter the percentage of tips paid to the waiters that will be withheld to cover for fees charged by payment processors. If you do not wish to use this feature, leave it at 0.00.

Electronic Funds Transfer

Enable this option. This option needs to be enabled to block operations that are not compatible with EMV payments, such as Cancel/Reopen Check.

Hide Card Number

Enable this option. It automatically becomes enabled when Electronic Funds Transfer is enabled, so leave it enabled.

Show on Merchant Copy

Disable this option. This option was used by older, non-integrated protocols and caused the credit card number to be printed on the merchant copy of EFT transaction records. This option has no effect with any Electronic Funds Transfer protocol, semi-integrated protocols, SecureTable or SecurePay.

Credit Only

This option is not usable (grayed-out) with most EFT protocols. It is only used with the Datacap - DSIEMVUS semi-integrated protocols to allow Pre-Authorization and PreAuth Capture with select processors that support this feature.

Validation

Disable this option. Validation is only used with fully integrated EFT protocols and has no effect with semi-integrated protocols such as SecureTable or SecurePay.

Expiration

Disable this option. This option automatically becomes enabled when Electronic Funds Transfer is enabled. Make sure to DISABLE it. Otherwise, the POS will request the credit card’s expiration date, which will slow down your operations. This information is already checked by the payment terminal and does not need to be re-validated by the POS.

Debit Card

Disable this option for the generic media type mapping.

Card Validation

All the options in this section must be cleared. Make sure to clear the Custom Card checkbox as well as all the fields in the Card Validation section.

1. Click OK to save changes. The new media type will appear in the list.

The configuration of the generic media type mapping is now completed.

Assign a Payment Terminal to POS Workstation

Each payment terminal using SecurePay needs to be assigned to a POS Workstation. Note that each POS workstation can only drive one payment terminal, therefore the number of payment terminals using SecurePay shouldn't exceed the number of POS workstations.

The following procedure is required to assign a specific payment terminal to a specific POS workstation in Maitre'D.

Procedure

1. Logon to the Maitre’D Back-Office with appropriate credentials. (Distributor or System Owner)

1. Start the Point of Sale Control Module.

1. Click the Workstation menu, and select Options...

1. The list of available POS workstations will appear. Select the POS Workstation to which you want to assign a payment terminal and click Modify.

1. The POS workstation's options will appear. Click the Devices branch on the left of the window, then click the Add button to start adding a new device.

1. In the Add Device dialog, select PIN Pad and click the Setup button.

1. Setup the device as follows:

Type

Select Network from the drop-down list.

Port

This setting is disabled and cannot be configured. Ignore it.

Driver

Select External from the drop-down list.

IP Address

Enter the IP address of the payment terminal.

Port Number

Enter the TCP port number used by the payment terminal. The default value for SecurePay is 9999.

ID

This setting is disabled and cannot be configured. Ignore it.

Idle Message

This setting is disabled and cannot be configured. Ignore it.

Identity

Enter the payment terminal's identity, which is supplied by the payment processor. This is also referred to as Terminal ID or TID.

Prompt for tip

This option has no effect with SecurePay payment termimals, as it will be overridden by the configuration of the SecurePay application installed on the payment terminal.

Print Tip Line

This setting is disabled and cannot be configured. Ignore it.

1. Click OK on the Device Setup dialog to save your changes. The new device will appear in the list:

1. Click OK to save changes to the workstation setup and close this window.

2. Close the POS workstation list, or select another POS workstation and repeat steps 4 to 9 to configure more payment terminals.

Make sure that each payment terminal using SecurePay is assigned to a POS workstation.

Overview

Purpose of this document

This document will cover the configuration required to operate SecurePay with integration to POS systems through the Retail Terminal Interface for Semi-Integrated Payment Applications (RTI-SIPA) plugin.

SecurePay Application

The SecurePay Android application is a bi-directional interface which links the PayFacto payment application to a POS system such as Maitre'D or Veloce. SecurePay automates some operations which previously had to be carried out by the clerk, such as the entry of the sales amount and card brand selection. SecurePay is especially well-suited to quick service environments and drive-through windows, with or without tip management.

Retail Terminal Interface for Semi-Integrated Payment Applications (RTI-SIPA) Plugin

The RTI-SIPA plugin is part of the STPISecure installer package and can be installed as a standalone component. RTI-SIPA's main purpose is to link the POS system and its POS workstations to the SecurePay application which resides on each payment terminal. This plugin will be installed on the POS system's main back-office PC as well as each POS workstation where a payment terminal will be used.

Accurate payment reporting

The integration of SecurePay with various POS systems allows the payment terminal to retrieve guest check data from the POS System. Once a payment has been processed by the payment terminal, SecurePay 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 SecureTable

SecureTable and SecurePay 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. SecureTable and SecurePay share a similar user interface which provides a consistent user experience for customers and employees.

Starting the SecurePay Application

If the SecurePay application does not start automatically, simply touch the appropriate icon on the Android home screen. A splash screen will briefly be displayed, followed by the SecurePay home screen.

Basic Navigation

Settings

The Settings button is used to access SecurePay's configuration options. This icon appears in the top-right corner of the SecurePay home screen.

Home

When available, the Home button will appear in the top-right corner of the screen. Use it to jump directly to the SecurePay home screen without saving changes.

Back

When available, the Back button will appear in the top-left corner of the screen. Use it to go back to the previous screen without saving changes.

Default Password

The SecurePay application settings are protected by a password. The default password on a new installation is 1234

Exit the SecurePay Application

1. To exit the SecurePay application, swipe the terminal's screen either from the top edge going down, or the bottom edge going up, then touch the Android Home (circle) button.

2. You will be prompted to enter a passcode to exit the application. Enter the passcode and touch the OK button.

Related Topics

1. SecurePay Application Configuration

2. SecureTable Installation on Android Terminals

After the Retail Terminal Interface for Semi-Integrated Payment Application (RTI-SIPA) plugin has been installed, configured and running properly on the POS system's Back-Office and POS workstations, make sure that all payment terminals are properly configured so they can communicate with the POS system and the Internet. Android payment terminals are generally shipped with all the necessary applications pre-installed by PayFacto, including the latest version of SecurePay and the latest version of the Payment application. If the SecurePay application appears to be missing, install it using the instructions below.

PAX A920 and A80 Android Payment Terminals

The instructions below were created using the PAX A920 and PAX A80 Android-based Payment terminals and the PAX store. However, the instructions are the same for all Android-based payment terminals, such as other models offered by PAX, AMP terminals or Clover Flex. For brands other than PAX, the mechanism they use to install apps may look different, but the general principle should remain the same.

PAX A920 PAX A80

Before you begin

Before installing SecurePay on your payment terminal, please make sure that the appropriate payment application is installed and configured properly. You may also want to check out our documentation on the PAX A920, A920Pro or A80 terminals or any other Android-based terminal you may be using with SecurePay.

PayFacto Payment Application (For the Canadian market):

Android PayFacto Application - Manual setup of application

PayFacto - Clerk Management

PayFacto Quick Reference Guide

BroadPOS Payment application (For the US market):

Link