Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Here is a quick overview of the entire installation and setup process:
Install/enable Microsoft .NET Framework 3.5 SP1.
Install the latest version of Oracle’s Java for Windows.
Use the STPISecure to installer to install the RTI-SIPA plugin.
Configure your POS System.
Connect, power up and configure payment terminals.
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.
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.
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.
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.
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.
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.
Maitre’D version 7.08.000.280 or later.
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
SecurePay-Compatible Payment terminal(s)
1 Gbps (Gigabit) Ethernet (wired) network or better.
WiFi network (802.11 ac or better)
High-Speed Internet connection.
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.
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:
Click on the Windows 10 Start button and type Control Panel.
The Control Panel app should appear as a search result. Click on Open.
Within the Control Panel app, click on Programs.
Under Programs and Features, select Turn Windows features on or off.
The Windows Features list will appear.
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.
NOTE: The black square in the check box means that the feature itself is enabled, but that some optional components are disabled. The optional components are not required for STPISecure or RTI-SIPA, so leave them disabled.
Click OK on the Windows Features list. This will close the list and apply any changes.
Files may be copied and you may be required to restart the PC.
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.
IMPORTANT! If the link provided here does not work, please use your preferred search engine and look for "Microsoft .NET Framework 3.5". Be sure to download the files from the official Microsoft download site. For security reasons, please avoid non-Microsoft sources.
Installation Process Overview
Install Microsoft .NET Framework 3.5 SP1
Install Java for Windows
Install the RTI-SIPA Plugin
The following instructions describes the installation and configuration process for the Maitre’D POS System.
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
Locate the STPISecureX.X.X.X.exe file, then right-click the file and select Run as administrator.
You may see a UAC prompt. Click Yes.
Please read the End-User Licence Agreement. If you agree with the terms, select I accept the agreement and click Next>.
Select the installation destination for STPISecure files. Accept the default path by clicking Next>.
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.
NOTE: If you don't use wireless payments terminals with SecureTable, you don't need to install this component.
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.
Select the All Others (POS 4) option and click Next>.
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.
The setup wizard is now ready to begin the automated installation process. Review your settings and click the Install button.
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.
Once the installation completes, you will see the screen pictured below. Click the Finish button.
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.
Logon to the Maitre’D Back-Office with appropriate credentials. (Distributor or System Owner)
Start the Point of Sale Control Module.
Click the Workstation menu, and select Options...
The list of available POS workstations will appear. Select the POS Workstation to which you want to assign a payment terminal and click Modify.
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.
In the Add Device dialog, select PIN Pad and click the Setup button.
Setup the device as follows:
Select Network from the drop-down list.
This setting is disabled and cannot be configured. Ignore it.
Select External from the drop-down list.
Enter the IP address of the payment terminal.
Enter the TCP port number used by the payment terminal. The default value for SecurePay is 9999.
This setting is disabled and cannot be configured. Ignore it.
This setting is disabled and cannot be configured. Ignore it.
Enter the payment terminal's identity, which is supplied by the payment processor. This is also referred to as Terminal ID or TID.
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.
This setting is disabled and cannot be configured. Ignore it.
Click OK on the Device Setup dialog to save your changes. The new device will appear in the list:
Click OK to save changes to the workstation setup and close this window.
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.
Main Media Type for SecurePay
With semi-integrated protocols such as SecurePay, a main media type is required to start processing any card payment. The purpose of this media type is to activate the payment terminal and initiate the transaction process.
IMPORTANT! The media type described here is essential to process card payments. While it is technically possible to process card payments without any additional media types configured, media types known as "mappings" are required to generate accurate reporting data for each card brand accepted by the merchant. See Media Type Mappings for SecurePay for more details.
Logon to the Maitre’D Back-Office with appropriate credentials. (Distributor or System Owner)
Start the Point of Sale Control Module.
Click the Payments menu, and select the Media Types… option.
The list of all current media types will be displayed. Click the Add button.
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 be as generic as possible, as the sole purpose of this media type is to initiate a card payment with any card brand. A common name used for this media type is simply CREDIT/DEBIT.
Payment Type
Select the External Pinpad 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 customer’s needs and preferences.
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.
Configure remaining options per the customer’s needs and preferences.
Click on the Card Property branch.
EFT Category
Set this drop-down list to Others.
Type
Set this drop-down list to Other.
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.
NOTE: Some jurisdictions don't allow transaction or credit card processing fees to be passed down to employees. Please verify your local regulations before using this feature.
Electronic Funds Transfer
Disable this option. This option needs to be disabled on the main EMV Credit media type. Leaving it enabled will cause unwanted effects.
Hide Card Number
Disable this option. This option needs to be disabled on the main EMV Credit media type. Leaving it enabled will cause unwanted effects.
Show on Merchant Copy
Disable this option. It should be grayed-out anyways.
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. This option needs to be disabled on the main EMV Credit media type. Leaving it enabled will cause unwanted effects.
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.
Click OK to save changes. The new media type will appear in the list.
Click the Close button to close this list and return to the POS Control module.
This completes the configuration of the main media type used to activate the payment terminal and initiate the transaction process.
While it is technically possible to start processing card payments right away without creating additional media types, doing so is not recommended. Without additional mappings, all card payments will report under the generic media type. This means that data and statistics for each card brand will not be available, therefore you will not be able to differentiate Visa, Mastercard, Amex, Debit or any other type of card payment.
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.
NOTE: SecureTable and SecurePay can be used at the same time on the same POS system. Therefore, the merchant can have any combination of stationary terminals using SecurePay and mobile terminals using SecureTable. Both types of terminals will share the same media type mappings.
Logon to the Maitre’D Back-Office with appropriate credentials. (Distributor or System Owner)
Start the Point of Sale Control Module.
Click the Payments menu, and select the Media Types… option.
The list of all current media types will be displayed. Click the Add button.
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.
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.
NOTE: Print Receipt, Check on Receipt and Open Drawer options have no effect on wireless payment terminals using SecureTable. However, payment terminals with SecurePay will be affected.
Configure remaining options per the merchant’s needs and preferences.
Click on the Card Property branch.
EFT Category
Set this drop-down list to whichever card brand that needs to be mapped to this media type.
Type
This drop-down list is used to determine the type of payment for the purpose of Sales Recording Modules and fiscal printers. The available settings are described below.
Cash
Select the Cash option for the default cash payment and any other payment involving cash, such as foreign currencies.
Credit
Select this option for all credit card payments.
Debit
Select this option for U.S. Debit and Canadian debit (Interac) payments.
Other
Select this option for all payments which do not fall in any of the above categories. Gift card purchases and Gift Card redeem are common examples of media types where Other needs to be selected.
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.
NOTE: Some jurisdictions don't allow transaction or credit card processing fees to be passed down to employees. Please verify your local regulations before using this feature.
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
This option automatically becomes enabled when Electronic Funds Transfer is enabled. 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
Enable this option if you are creating a mapping for U.S. Debit or Canadian Debit (Interac).
Disable this option for credit card brand mappings (Visa, Mastercard, American Express, Discover, etc.).
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.
Click OK to save changes. The new media type will appear in the list.
Repeat the previous steps until all required mappings are created. At the end of the process, you should have one mapping for each card brand that is accepted by the merchant.
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, .
Please download and install the latest version of Java for Windows for your specific Windows edition (32-bit or 64-bit)
NOTE: Please consult Oracle's Java website for detailed licensing conditions and support.