Open

Introduction

Point‐of‐Sale (POS) systems that process sensitive payment information are required to certify their payment applications to the Payment Application Data Security Standard (PA‐DSS). The addition of EMV certification and continued need for both encryption and tokenization has become a concern for both merchants and integrators. Instituting and maintaining these standards requires significant financial and employee resources in order to adhere to the Payments Card Industry Data Security Standards (PCI DSS) compliance requirements. Subsequently, any changes made in the POS system, may require a partial or full recertification, which increases the cost and time to market. BridgePay has engaged these issues through our product line, the Pay Guardian suite, to better serve the needs of our integrators and merchants.

PayGuardian is a light weight, highly secure client application that integrates seamlessly into POS applications. PayGuardian facilitates the transaction process by handling the collection and transmission of sensitive payment information as an out of scope PA-DSS solution, thereby offloading the certification responsibility from merchants and integrators. PayGuardian is EMV enabled, handles point to point encryption, and tokenizes all transactions to ensure transaction processing is seamless and secure.

The PayGuardian Installation Guide describes a typical installation and configuration of the PayGuardian client application by merchants and reseller partners. Please contact BridgePay Network Solutions at gateway.support@bridgepaynetwork.com with any questions, or to request further assistance. For a more in-depth look at PayGuardian, please reference our PayGuardian Desktop User Guide.

Open

Requirements

The minimum requirements to successfully install and operate PayGuardian are described in the following sections. Failure to the meet these requirements can result in PCI non-compliance and revocation of BridgePay support.

Operating Systems

PayGuardian has PA‐DSS certification for the following operating systems:

• Windows 7 Professional 32‐bit

• Windows 7 Professional 64‐bit

• Windows 8.1 Professional 32‐bit

• Windows 8.1 Professional 64‐bit

• Windows 10 Professional 32‐bit

• Windows 10 Professional 64‐bit

• Windows Server 2008 R2 64-bit

• Windows Server 2012 R2 64-bit

• Windows Server 2016 64-bit

Browsers

BridgePay only guarantees full support for PayGuardian using the Operating System (OS) native browser for Windows – Internet Explorer version 11 and above.

Java

BridgePay only guarantees full support for PayGuardian using Java version 8, Update 77 and above.

Hardware

BridgePay only guarantees full support using the minimum requirements listed below to successfully run PayGuardian.

• 1GHz Processor

• 4GB RAM

• 1GB Hard Disk Space

• Gigabit Network Adaptor

PayGuardian Installation

PayGuardian is available as both a client application for desktop installation (PayGuardian), or as a browser based version (PayGuardianWEB). This section describes the installation process for both PayGuardian and PayGuardianWEB products.

Note: Please see Appendix A.7 for instructions on installing the RMS Plug-in feature.

Launch Installation Wizard

PayGuardian

Launch the Installation Wizard for PayGuardian by following the steps as outlined below.

• Select PayGuardian 2.X.X and then select PayGuardian.exe.

• Choose “Extract All” and extract to the directory where the file was downloaded.

• Run .exe in Administrator mode (i.e., Right click on the .exe and choose “Run as Administrator” or log onto the computer as Administrator).

Note: Anti-virus software should be disabled before proceeding with the install.

• Click Next, and accept the screen defaults. Click through the following screens and accept the End-User License Agreement.

The RMS Plug-in feature will be installed when the checkbox ‘Click to Install RMS Plug-In’ is selected. Please see Appendix A.7 for configuration instructions.

• Click Finish, to complete the installation process and Start PayGuardian. The Start PayGuardian checkbox is enabled by default. Uncheck the checkbox if you want to start PayGuardian at a later time.

Once “Finish” is clicked, a Blue loading screen will appear before the registration of your product begins. If the registration process does not start and you are given an error that you are unable to connect to the local database, please restart the PayGuardian Service and try again. If that does not work, you may need to update the SSL certificate of PayGuardian to continue.

Registration

Once registration starts, you will be asked to provide information specific to your organization. With the exception of the Registration Key, none of this information is validated. You are able to input specific information true to the current installation you are working on.

Note: The Registration screen will not display if the silent install was used with the Settings.xml file. 

• Enter the Registration Key provided by BridgePay Integrations. If you are unsure about the Registration Key, please contact Gateway Support for assistance. The test registration key is H75RCGRV.

• Enter the general setup information as indicated by the red asterisks (required fields).

Login Credentials

Setup Login Credentials

On the next screen of registration, you will be creating the Master Admin user for PayGuardian as well as set the security question for this account. This login will be able to access your account specific information for your gateway as well as be able to troubleshoot your credit card terminal. This user is unique to you and will never be provided to you by BridgePay or Integrator Support.

Note: The creation of two separate Admin users is recommended for PayGuardian, so that in the event one user account is temporarily locked, the additional Admin user account would still be accessible.

• Complete the “Register” screen by completing the information as indicated by the red asterisks (required fields).

Enter Login Credentials

Enter the same user credentials for PayGuardian created or entered on the “Register” screen.

Setting Up Your Installation

Admin

When you login, you will be taken to the Admin Tab of PayGuardian. This screen will allow you to be able to create secondary admin accounts (that have the same accesses as the first admin account) as well as create “Clerk” users that would only have access to the Virtual POS option of PayGuardian Desktop.

NOTE: If you are setting up an integration to PayGuardian Desktop through a Cashiering-type setup, the use of a “Clerk” user is recommended for that integration.

Adding A User

When clicking “Add User” a pop-up box appears.

User Name: This field is where you would input the username you are attempting to create. Only alphanumeric characters only.

Role: The permissions this user will have. The roles to choose from are:

• ADMIN - a user that allows you to fully troubleshoot PayGuardian, including creating new users, add new payment server information, and connect credit card terminals.

• CLERK - a user that is only allowed to process transactions through the Virtual POS.

Password: Password should consist of 8-30 characters with alphanumeric characters and at least one special character.

Confirm Password: Duplication of the password you entered above it

Security Question: You are able to choose between one of five security questions that you will use on the Forgot Password screen if you ever needed to change your password without knowing it. The questions available are:

• What is your childhood nickname?

• What is your favorite place to visit?

• What was your dream job as a child?

• Who was your childhood hero?

• What was the name of your first car?

Answer: The answer to the question above. Your answer must be between 5 and 40 characters.

Connecting Your Gateway Account

After you have created the user accounts necessary for your integration, next you will want to connect your gateway account to allow for transactions to flow from your point-of-sale solution to PayGuardian and then to your merchant account boarded within MyBridgePay. Connecting this account is done under the Payment Server option.

To connect your account, click Add Account on this screen. A new pop-up will appear.

On this pop-up window, you are asked for a User ID and a Password. For User ID, this is what is typically referred to as your API username, or the username associated to your Merchant Account within MyBridgePay. For Password, you will enter the password that is associated with the above username. If your username and password combination is correct, you will get a success message when you click Ok. If your credentials are incorrect, please reach out to Integration Support or our CSM team to validate those credentials.

Setting Up Your Credit Card Terminal

You’ve created your user account and connected PayGuardian to your merchant account. Now it is time to make sure that your PayGuardian installation can speak to the credit card terminal that is plugged into a USB port on your workstation. You will make all of your setup decisions under the Hardware tab.

Before making any decisions on this screen, it is best practice to validate which COM port your device is connected to. To easily determine this, you will need to access Device Manager on your Windows machine. Once Device Manager is open you will search for the option for Ports (COM & LPT). Click on the > to the left of the option to expand the dropdown. Under Ports, you should see your credit card terminal listed with the port number listed to the far right of the device in parentheses. Once you have this information, you will be able to continue setting up your device within PayGuardian Desktop.

When you click on Hardware, you will see options for various functions that your credit card terminal may utilize. For specific terminal installation setups, please contact Gateway Support to see which settings will best correspond with your terminal.

For each option you see, there is a dropdown that lists the supported devices for PayGuardian Desktop. If you choose your terminal in the dropdown, you will be activating that portion of your terminal.

Pin Pad - will activate the use of the physical Pin Pad on your device, allowing for users to press the keys found on your device for credit card processing.

Manual Card - will allow for the ability to manually process a credit card on PayGuardian Desktop without a card being presented to the terminal.

Signature Capture - will allow for the screen and stylus to be used to have your cardholder sign for their transactions.

Card Reader - will allow for cards to be swiped on the device itself.

PayGuardian also allows for the use of Printers and MICR Readers. For Printer Usage, often times that connectivity is set up with your POS system that integrates with PayGuardian. You will not need to connect in multiple places as if you do, you will have copies be printed from multiple points of your cardholder’s transaction.

After you have your device chosen for each of your top four selections, you will need to click Advanced to ensure you’re connected properly. Each section, you will need to make sure the following:

1. Your device type is set to RS232.

2. Your ComPort is set to what was listed in Device Manager.

Pin Pad, Manual Card, and Signature Capture are identical under Advanced. Under Card Reader, there are extra settings that appear.

• Enable EMV is the ability to accept CHIP Inserted card payments on your terminal.

• Enable Contactless is the ability to accept Mobile Wallet payments through your terminal.

• EMV Contactless is the ability to accept CHIP Tapped payments on your terminal.

Once you have checked your options, click Save. Click Advanced again and click on Download Form. You will see your terminal change its screen and say “File Downloading.” Once it is done, your PayGuardian screen will show “File Successfully Downloaded” and you can click Okay. Wait until your terminal fully reboots to click Save. Clicking early will cause a faulty “Connect Failed” error. Click Save again to allow your settings to successfully save.

Importing/Exporting Settings

After you have successfully setup your first install of PayGuardian, you can Export those settings to be imported into subsequent installs of PayGuardian. Please note that for the Importing and Exporting of settings to be optimized, be sure to import settings from the same version of PayGuardian. Importing settings from an older version of PayGuardian into a newer version will remove certain functionality that may be vital to the functionality of PayGuardian.

Exporting is very simple. Click Export Settings and click Okay on the pop-up window.

When you click Okay, you will be prompted to Open or Save a settings.zip file. Save this file to your workstation and then move it to a Shared drive or a thumb drive that you can transport to every workstation for importing. Things included in the Export are:

• Admin Users Created

• Hardware Settings

• Payment Server Accounts

• Options chosen under Settings

Importing is much of the same. Before clicking Import Settings, you will need to extract the .zip file that was downloaded from Export Settings. Once it’s exported, click Import Settings and click Browse. Select the settings.exe file and your settings will fully import. Double check through the other options of PayGuardian to insure settings are carried over.

NOTE: You will need to have PayGuardian installed on the workstation before this Import process can take place, which also includes the creation of your first Admin user.

PayGuardian Uninstall

Follow the step-by-step instructions to uninstall and remove PayGuardian from the system.

•  Open the Control Panel and select ‘Programs and Features’.

• Highlight PayGuardian.

• Click the Uninstall/Change button.

The PayGuardian/PayGuardianWEB Setup Wizard will launch.

Click on the “Remove” icon.

Click on the “Remove” button.

Click the “Finish” button.

Verify that PayGuardian is no longer listed under Programs and Features.

Troubleshooting

This chapter offers basic troubleshooting techniques and responses to common questions and reported issues.

Q1: Not able to add merchant account in the Payment Server tab (If you are in ‘Virtual POS’, first select ‘Admin Settings’ from the menu bar at the top of the screen in order to select the Payment Server tab)

A: The SSL certificate could be missing in JRE. PayGuardian/PayGuardianWEB should prompt to automatically install the SSL certificate. Accept the prompt to download and install the certificate.

Q2: No response or errors from payment processing

A: Ensure that your Internet connection is working correctly and the firewall is allowing the PayGuardian/PayGuardianWEB URL through.

Q3: Device is configured in Hardware settings. When trying to accept a payment, or trying to “Download Form” the following error is displayed: “Problem in Opening the Device”

A:

• Unplug the device’s USB cable from the computer or laptop and plug it back in.

• Reboot the device (hold down yellow key and “#” or yellow key and “-“). Instructions are dependent upon the device you are using.

• Verify the PayGuardian service has been stopped on the computer or laptop where the device is connected.

• Install the Ingenico device driver 2.8, which can be downloaded from the following directory: C:\Program Files (x86)\BridgePay\PayGuardian\drivers

• Leave the device attached to the computer and reboot the computer.

• If you are still unable to connect to the terminal, contact BridgePay for assistance at http://is.bridgepaynetwork.com/ and include as much information as possible. Include screen shots with any error messages and indicate which steps above have been completed.

How to Change Comm Settings

PayGuardian primarily supports one communication mode for Ingenico integrated credit card terminals. USB-CDC mode is the recommended communication method for PayGuardian. USB-CDC mode connects using the USB port, but utilizes a COM port. USB-HID mode is currently only being used for PayGuardian Terminal Services.

 The recommended communication mode is USB-CDC (also referred to as ‘USB<>Serial Conv’ in the credit card terminal menu), which is not only faster than USB-HID mode, but is also more reliable. This setting uses a COM port on the PC or register system. For USB-CDC mode to function, the Ingenico driver must be installed on the PC or register system connected to the credit card terminal. When installing the Ingenico driver, be sure to force the COM port to COM 8 if available and not in use. COM 8 is not required, but is used for consistency. Please enter the COM Port configuration that you’ve selected when completing the PayGuardian Hardware setup.

1.  Restart the pin pad by pressing [-] and Yellow [Clear] simultaneously until the pin pad beeps.

   1. On the iPP3xx and iSMP/iCMP, restart the pin pad by pressing [.,#*] and the Yellow [Clear] keys simultaneously until the pin pad beeps.

2. Wait for the pin pad to display the RBA or UIA initialization screen which will look similar to the screen below.

3. When RBA or UIA initialization screen appears press…

   1. iSC350, iSC250, and iUP250

      1. [2] [6] [3] [4] [Enter] [+] [+]

   2. iPP3xx and iSMP

      1. [2] [6] [3] [4] [Green Key] [F] [F]

4. If successful, the Functions menu should appear (below). If the Functions menu does not appear then please repeat step 1.

5. For iSC and iUP models, use the “+” and “-“ to scroll to “TDA Menu” and press “Enter” (green key). For iPP models, use the “F2” and “F3“ Down arrow and Up arrow keys to scroll to “TDA Menu” and press “Enter” (green key).

6. Select “Configuration” and press “Enter”.

7. Select “Communication” and press “Enter”.

8. Select “Select Comm. Type” and press “Enter”.

9. Once you have selected your communication setting press “Enter”.

10. Press “Cancel” 3 times. You will then be prompted to save your changes at which time you should press “Enter” and then the terminal will restart on its own and apply the changes made.

How to View Injection Slots

1. Restart the pin pad by pressing [-] and Yellow [Clear] simultaneously until the pin pad beeps.

   1. On the iPP3xx and iSMP, restart the pin pad by pressing [.,#*] and the Yellow [Clear] keys simultaneously until the pin pad beeps.

2. Wait for the pin pad to display the RBA or UIA initialization screen which will look similar to the screen shot below.

3. When RBA or UIA initialization screen appears press…

   1. iSC350, iSC250, and iUP250

      1. [2] [6] [3] [4] [Enter] [+] [+]

   2. iPP3xx and iSMP

      1. [2] [6] [3] [4] [Green Key] [F] [F]

4. If successful the Functions menu should appear (below). If the Functions menu does not appear then please go back to step 1.

5. For iSC and iUP models, use the “+” to scroll to “TSA Menu” and press “Enter” (green key). For iPP models, use the “F2” and “F3“ Down arrow and Up arrow keys to scroll to “TSA Menu” and press “Enter” (green key).

6. For iSC and iUP models, scroll down using the “-“ to DUKPT KSN and press “Enter”. For iPP models, scroll down using the F2 down arrow key to DUKPT KSN. Press “Enter”.

7. For iSC and iUP models, scroll down using the “-“ to DUKPT 4 and DUKPT 5. For iPP models, scroll down using the F2 down arrow key to DUKPT 4 and DUKPT 5. The slot (DUKPT) that has a series of numbers and letters displayed is where the encryption key is loaded. The picture below shows the encryption key in Slot 5.

8. After determining where the encryption key resides, restart the pin pad by pressing

   1. [-] and Yellow [Clear] simultaneously until the pin pad beeps.

   2. On the iPP3xx and iSMP, restart the pin pad by pressing [.,#*] and the Yellow [Clear] keys simultaneously until the pin pad beeps.

Solving Power Issues - iPP320/iPP350

Ingenico iPP320 and iPP350 Power/Continuous Rebooting Issue Resolution:

 The following steps should resolve the communication power issue with Windows 8.1 and Windows 10 in HID mode for the iPP320 and iPP350 devices.

1. Connect the iPP320/iPP350 to the computer.

2. Open Device Manager.

3. Expand the Human Interface Devices. The device will probably show as a USB Input Device. Depending on how many devices you have connected there may be several listed. Check each USB device listed to determine which one is the iPP3xx. This can be done by selecting each USB Input Device, right-click, select Properties, then the Details tab, pull down Property and select Hardware ID’s.

4. The values for an iPP320 are USB/VID_0800&PID_0071 and for the iPP350 are USB/VID_0800&PID_0072 (it may not match exactly).

5. From the tile or search screen, type “regedit.exe” and right-click “Run as Administrator”.

6. In Regedit, click on HKEY_LOCAL_MACHINE

7. Then SYSTEM, CurrentControlSet, Enum, USB

8. Within USB locate the folder that matches the name from Step 3 (iPP350 - HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\USB\VID_0B00&PID_0072

9. You should see a number or combination of numbers and letters. Open that folder and locate ‘Device Parameters’.

10. Click on the device parameters folder and to the right there will be 6 or 7 entries listed.

11. One of these entries should be EnhancedPowerManagementEnabled. Double click on this entry.

12. In this pop-up, under “Value data:” change the value to 0 zero. Click OK.

13. The device will disconnect and reconnect once more; the issue should now be resolved.

Verify Contactless (NFC) is Enabled

1. Restart the pin pad by pressing [-] and Yellow [Clear] simultaneously until the pin pad beeps.

   1. On the iPP3xx and iSMP restart the pin pad by pressing [.,#*] and the Yellow [Clear] keys simultaneously until the pin pad beeps.

2. Wait for the pin pad to display the RBA or UIA initialization screen which will look similar to the screen shot below.

3. When RBA or UIA initialization screen appears press…

   1. iSC350 and iSC250

      1. [2] [6] [3] [4] [Enter] [+] [+]

   2. iPP3xx and iSMP

      1. [2] [6] [3] [4] [Green Key] [F] [F]

4. If successful the Functions menu should appear (below) if the Functions menu does not appear then please go back to step 1.

5. Select TELIUM MANAGER Then scroll down to INITIALIZATION.

6. Select INITIALIZATION with the “Green” key.

7. Then select PARAMETERS with the “Green” key.

8. Scroll to Contactless and select it with the “Green” key.

9. Confirm that Contactless is set to “Yes”. If not, change to “Yes”, select Internal, and save changes.

Silent Install

The silent install feature can be used to load both the Ingenico hardware driver and PayGuardian settings, with or without the Settings.xml file.

Note: if the settings file is not used, then the registration process must be completed manually.

1. Make sure you have the current and correct Export file of the Settings.xml’ file to use for the installation. If no settings file is used, you will need to register and setup PayGuardian manually. The Import function can be used with the’ Settings.xml’, after the manual registration is complete.

2. If performing a silent install for the Ingenico driver, the Ingenico driver file, the PayGuardian executable file, and the Settings.xml file, all need to be located in the same file directory. Installation will be facilitated via the DOS prompt. Right click on the Windows icon on the bottom left of the desktop screen.

3. In Windows, open the Command Prompt (Admin). The user must be logged in as administrator. Change the directory to the root directory by using ‘cd /’ and the change the directory to where the PayGuardian executable, the Settings.xml, and the Ingenico driver files are located.

4. Below, are the two commands used for loading the Ingenico driver and the PayGuardian executable file.

   1. Ingenico silent install: IngenicoUSBDrivers_2.80_setup.exe /S /leave_usbser /PORT=8

   2. PayGuardian Silent Install: PayGuardian-2.3.0.exe /qb SETTINGS_FILE=%CD%\Settings.xml

If no settings file is being used for the PayGuardian silent install, then use:

PayGuardian-2.3.0.exe /qb (This will required a manual registration and then either a settings import file or manual setup)

Device Connectivity Troubleshooting

Please use the steps below to troubleshoot connectivity issues between PayGuardian and the Ingenico devices (iSC250, iSC350, iSC480, iPP320, and iPP350).

Restart the PayGuardian Service

Windows 10 Users

1. From the Desktop, select ‘PayGuardian’ from the Application list.

2. Next, select ‘Restart PayGuardian Service’ to restart the service.

Windows 7 Users

1. From the Desktop, select ‘PayGuardian’ from the Programs list.

2. Next, select ‘Restart PayGuardian Service’ to restart the service.

Device Manager

1. Access the Device Manager, then under the Ports (COM & LPT) option, double click on

   the Ingenico device listed (if none is listed, then Windows doesn’t recognize the device – try rebooting both the computer and the device).

2. Next, click on ‘Force COM Port’ and verify that the checkbox for ‘Force COM Port Feature enabled’ is selected. An 8 should appear in the bottom left box. All other boxes should be empty.

3. If the Ingenico device or Ports (COM & LPT) are not listed, then check to verify that the Ingenico 2.80 driver is installed. The device will also need to be configured for USB-CDC mode with UIA 15.0.2 firmware installed (Bluefin iSC250 PCI P2PE requires RBA 15.0.4).

PayGuardian Configuration Settings

1. Verify that the Ingenico device model is selected for each configuration setting appropriate for all processing options on the Hardware configuration tab.

2. Select the ‘Advanced’ button for each setting and verify that the ComPort is set to COM8. Click the ‘Save’ button before exiting the Advanced settings.

3. Click the ‘Save’ button before exiting the Hardware configuration.

4. If the device is still unable to connect, try unchecking the ‘Contactless’ option in the ‘Card Reader’ Advanced menu. Click the ‘Save’ button in the Advanced settings, then click the ‘Save’ button at the bottom of the Hardware configuration menu.

5. If the device is still unable to connect, reboot the computer and the device and try to connect again.

Miscellaneous

1. If the device is connected and the forms download properly, but payments (Swipe or EMV) will not process, make sure the P2PE key is in slot 5. For steps on how to view and verify the injection slots, see the PayGuardian Installation Guide - Appendix A2. If the P2PE key is in slot 4, use the “UIA Update Tool” to update the BridgePay data pack for slot 5.

2. Make sure an AC power adapter is used to power the device.

3. If the device is showing up in System devices in Device Manager, but it is set to USB-CDC, then double click on the device entry, and delete the driver.

4. If the device is plugged into the front port of a tower computer, try moving it to a back port. Make sure a USB hub isn’t being used.

5. If PayGuardian can be installed on another computer, try connecting using a different PC.

PayGuardian RMS Plug-in

Please use the steps below to configure the RMS Plug-in during the PayGuardian installation process after the PayGuardian settings have been configured in the previous sections of this guide. The plug-in is an integrated bridge enabling Microsoft RMS to process transactions through PayGuardian. Configuration components include the setup of payment Tender Types, various communication settings, and the PayGuardian receipt template in Microsoft’s RMS point-of-sale system.

Supported Software

BridgePay only guarantees full support for the PayGuardian RMS Plug-in using:

•  Microsoft RMS version 2.0 or higher.

Setup and Configuration

 During the PayGuardian installation process, there is an option to install the RMS Plug-in. By selecting the ‘Click to Install RMS Plug-In’ checkbox, the RMS Plug-in configuration tab will appear on the Admin setup screen of PayGuardian.

The PayGuardian RMS Setup screen has selected default settings that can be modified as needed, the descriptions of which are listed below.

Note: Once the selections from the list below have been made, clicking the Set RMS Hooks button will save the settings in the Microsoft RMS registry files, enabling the changes to take effect.

• Available Tenders – By default all Tender Types are selected, but can be deselected as needed.

• Advanced Credit Card Settings – The ‘Credit Card’ tender type is set as the default, however you can modify this selection to create individual Credit Card brands as Tender Types for setup in Microsoft RMS, by deselecting the default option, and selecting the individual Card brands as needed.

• Session Variables – Do not touch.

• Interface Features – RMS operational features enabled/disabled through the RMS Plug-in settings.

  • Disable Approved prompt – Allows for the disabling of a ‘popup message’ from displaying that the transaction has been approved with the transaction reference message,

    requiring the user to click ‘OK’.

  • Auto Populate AVS – Enabled by default; allows for the auto-population of stored customer address information for a selected customer while the transaction is processed.

  • Restart service button – Allows the ‘Restart Service’ button to appear in the RMS Store Operations POS, enabling the ability for a user to restart the PayGuardian service as needed.

  • Signature only Processing – Disables the ability to skip the signature capturing process after a transaction has been completed.

  • Authorize Quotes – Intended for future use.

• Hook Status - Registers the configured settings and imports them into Microsoft RMS as described.

Microsoft RMS Setup Completion Process

 Once the PayGuardian RMS Plug-in settings have been configured and the Set RMS Hooks button has been initiated, a popup message will display for new configurations with additional steps to complete the Tender Type setup. This popup message will only appear for new configurations without previously configured Tender Types.

Please follow the steps below to finalize the RMS Hooks Setup registration process.

•  Open the Store Operations POS in Microsoft RMS and log in with your user credentials.

• Click the F5 button: Open/Close.

• Select ‘Print Z Report’ and follow the screen prompts.

• Click the keyboard ESC button to exit. When you restart the Microsoft RMS Store Operations POS, the changes and new tender type options will have taken effect.

Note: If you selected the GIFT tender, you will need to restart Microsoft RMS in order for the Gift Inquiry button to appear. A restart is not necessary for any other function.

Setup Receipt Templates in Microsoft RMS

You have the option of configuring a new receipt template to incorporate the PayGuardian RMS Plug-in tender types and PayGuardian configuration settings. Follow the steps below to create a new receipt template.

• Open the Retail Management Systems Store Operations Manager.

• Go to Database -> Registers -> Receipt Formats. This should open the Receipt Formats window.

• Copy your current RMS receipt template by using the ‘Copy’ button. (Alternatively you can create a new template by pressing the ‘New’ button.)

• Give the new template a meaningful Title and Description.

• Press the browse button (magnifying glass icon), and find the XML receipt template file you wish to load.

• Press ‘Open’.

• Press ‘Yes’ at the prompt: Would you like to update all transaction types that are currently set to 'Receipt Template Name'?, unless you have a particular reason not to do so.

• Optionally you can update settings within the template by clicking the ‘Properties’ button. When finished making your modifications, press ‘OK’ to close the Receipt Format Properties window.

• Next, configure your register(s) to use the new receipt template. Go to Database -> Registers -> Register List.

• Select each register you wish to update, from the selection list, in turn.

• Click Properties.

• Inside the Register Properties window, select the Receipt Printer 1 tab.

• Under the Receipt Format section, click the browse button (magnifying glass icon), and choose the newly created receipt template.

• Press ‘OK’.

• If Microsoft RMS Point of Sale is open during this process, you will need to close it and then reopen, for the changes to take effect.

Terms of Use Agreement

ACKNOWLEDGMENT AND ACCEPTANCE OF AGREEMENT

The Terms of Use Agreement “TOU” is provided by BridgePay to you as an end user “USER” of the information obtained from BridgePay, any amendments thereto, and any operating rules or policies that may be published from time to time by BridgePay, all of which are hereby incorporated by reference. The TOU comprises the entire agreement between USER and BridgePay and supersedes any prior agreements pertaining to the subject matter contained herein.

DESCRIPTION OF SPECIFICATIONS AND INFORMATION

BridgePay is providing USER with the information concerning the technical requirements or allowing point of sale software to send and receive electronic transaction data to the BridgePay network for authorization and/or settlement. To utilize the Specifications, USER must: (i) provide for USER's own access to the World Wide Web and pay any fees associated with such access, and (ii) provide all equipment necessary for USER to make such connection to the World Wide Web, including a computer, modem and Web browser.

USER'S REGISTRATION OBLIGATIONS

In consideration of use of the Specifications, USER agrees to: (i) provide true, accurate, current, and complete information about USER as requested on the Registration Form, and (ii) to maintain and update this information to keep it true, accurate, current and complete. This information about a USER shall be referred to as "Registration Data". If any information provided by USER is untrue, inaccurate, not current, or incomplete, BridgePay has the right to terminate USER's access to the Specifications and refuse any and all current or future use of the Specifications.

MODIFICATIONS TO AGREEMENT

BridgePay may change the TOU from time to time at its sole discretion. Changes to the TOU will be announced and publicly available to all USERs.

MODIFICATIONS TO SPECIFICATIONS

BridgePay reserves the right to modify or discontinue, temporarily or permanently, the use of any of the Specifications with or without notice to USER. USER agrees that BridgePay shall not be liable to USER or any third party for any modification or discontinuance of a Specification.

USER ACCOUNT, PASSWORD AND SECURITY

USER will receive a password when registering their company (account) to become a Partner. Upon approval, that password will allow USER access into the Partner Portal. USER is responsible for maintaining the confidentiality of the password and account, and is fully responsible for all activities that occur under USER's password or account. USER agrees to immediately notify BridgePay of any unauthorized use of USER's password or account or any other breach of security.

LICENSE GRANT

a.       Subject to the terms and conditions of this Agreement, BridgePay hereby grants to USER a personal, limited, perpetual, non‐exclusive, non‐ transferable, annual subscription license to make and use the SOFTWARE accompanying this TOU to be installed on CPUs residing on Licensee's premises, solely for Licensee's internal use. BridgePay and its suppliers shall retain title and all ownership rights to the product and this Agreement shall not be construed in any manner as transferring any rights of ownership or license to the SOFTWARE or to the features or information therein, except as specifically stated herein. use and reproduce the following solely to develop, manufacture, test and support the products: (i) in object code form (except as may be agreed by the parties in writing or as otherwise set forth in this Agreement), (ii) the applicable software in object code form, except as may be agreed by the parties in writing or as otherwise set forth in this Agreement, (iii) BridgePay materials which shall include all documentation.

 b.    Upon the annual anniversary date of the activation of the license, the USER will be responsible the renewal of the subscription of the license either through their RESELLER or directly to BridgePay.

TRADEMARKS

USER acknowledges that BridgePay owns exclusive rights in the BridgePay trademarks. USER will not use BridgePay as part of any of its product, service, domain or company names and will not take nor authorize any action inconsistent with BridgePay's’ exclusive trademark rights during the term of this Agreement or thereafter. Nothing in this Agreement grants USER ownership or any rights in or to use the BridgePay trademarks except in accordance with this license. USER will use a legend on its website and, where commercially feasible, on all printed materials and products bearing the BridgePay trademarks similar to the following: “(USER name) uses the BridgePay™ mark under express license from BridgePay, LLC.”

USER OBLIGATIONS

 a.       USER shall utilize its BridgePay assigned developer ID in each application utilizing the BridgePay specification

 b.       USER shall not reverse‐engineer, reverse‐compile or disassemble any BridgePay software or otherwise attempt to derive the source code to any BridgePay software.

 c.       USER shall have no right to (i) disclose any BridgePay source code or BridgePay source code or BridgePay source code documentation other than as permitted or contemplated by this Agreement. No licenses are granted by BridgePay to USER by implication or estoppels to the BridgePay source code or BridgePay source code documentation.

 d.       USER shall comply with all applicable card association regulations, applicable federal, state and local statutes and BridgePay required procedures and identified best practices. USER agrees (i) not to use the Specifications for illegal purposes; and (ii) to comply with all applicable laws regarding the transmission of technical data exported from the United States.

DISCLAIMER OF WARRANTIES

USER expressly agrees that use of the Specifications is at USER's sole risk. The Specifications are provided on an "as is" basis.

 a.       BRIDGEPAY EXPRESSLY DISCLAIMS ALL WARRANTIES OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON‐INFRINGEMENT

 b.       BRIDGEPAY MAKES NO WARRANTY THAT THE SPECIFICATION WILL MEET USER'S REQUIREMENTS, NOR DOES BRIDGEPAY MAKE ANY WARRANTY AS TO THE RESULTS THAT MAY BE OBTAINED FROM THE USE OF THE SPECIFICATIONS OR AS TO THE ACCURACY OR RELIABILITY OF ANY INFORMATION OBTAINED THROUGH USE OF THE SPECIFICATIONS. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF CERTAIN WARRANTIES, SO SOME OF THE ABOVE EXCLUSIONS MAY NOT APPLY TO YOU.

 TERMINATION BY BridgePay

USER agrees that BridgePay may terminate USER’s password, account or use of the Specifications:

a.       If BridgePay determines in its sole discretion that USER has violated or acted inconsistently with the letter or spirit of the TOU;

b.       If the USER has violated the rights of BridgePay, or that USER's continued use of the Specifications poses a material threat to the security, stability or ongoing operation of the System or Specifications.

 c.       BridgePay may terminate this Agreement for cause at any time upon providing not less than ten (10) business day’s prior written notice to USER. USER acknowledges and agrees that any termination of access privileges to the Specifications under any provision of the Agreement may be effected without prior notice.

 d.       BridgePay shall in the event that a license has not been renewed and BridgePay has not received and validated payment from either the USER or the RESELLER within 30 days of the anniversary date of the original activation the deactivate or terminate the usage of the license.

LIMITATION OF LIABILITY

In no event shall BridgePay be liable to USER for any incidental, consequential or punitive damages related to this Agreement or the use of BridgePay software or specifications. The liability of BridgePay hereunder shall be limited to the fees paid to BridgePay pursuant to this Agreement. USER agrees that BridgePay shall not be liable for any direct, indirect, incidental, special, or consequential damages, resulting from the use or the inability to use the Specifications, including but not limited to, damages for loss of profits, use, data or other intangibles, even if BridgePay has been advised of the possibility of such damages. Some jurisdictions do not allow the limitation or exclusion of liability for incidental or consequential damages so some of the above limitations may not apply to you.

NOTICE: Any notice to USER or to BridgePay shall be made via either e‐mail or regular mail. BridgePay may also provide notices of changes to the TOU or other matters by displaying notices to USERs, generally on the Specifications.

SPECIAL DAMAGES

In no event will BridgePay be liable to the USER, consequential or punitive damages, including but not limited to, lost profits, even if such party knew of the possibility of such damages.

INDEMNIFICATION

 a.       USER shall be liable to and shall indemnify and hold BridgePay, its employees, representatives, successors and permitted assigns harmless from and against any and all claims, demands by third parties, losses, liability, cost, damage and expense, including litigation expenses and reasonable attorneys’ fees and allocated costs for in house legal services, to which BridgePay, its employees, representatives, successors and permitted assigns may be subjected or which it may incur in connection with any claims which arise from or out of or as the result of (i) USER’s breach of this Agreement, (ii) the performance by USER of its duties and obligations under this Agreement or (iii) the negligent or willful misconduct of USER, its officers, employees, agents and affiliates in the performance of their duties and obligations under this Agreement.

PROTECTION OF CONFIDENTIAL INFORMATION

All information of a business nature relating to the BridgePay specification, software, application interfaces, services, processes, merchant and cardholder data, product or programming techniques of either party shall be deemed confidential (“Confidential Information”). This shall not prohibit each party from disclosing such Confidential Information to persons required to have access thereto for the performance of this Agreement; provided, however, that such persons shall be required to keep such Confidential Information confidential to the same standard that the disclosing party is obligated to keep the Confidential Information confidential.

FORCE MAJEURE

In no event shall BridgePay be liable with respect to the failure of its duties and obligations under this Agreement (other than an obligation to pay money) which is attributable to acts of God, war, terrorism, conditions or events of nature, civil disturbances, work stoppages, equipment failures, power failures, fire or other similar events beyond its control.

GENERAL

a.       The Specifications Agreement and the relationship between USER and BridgePay shall be governed by the laws of the State of Illinois without regard to its conflict of law provisions.

 b.       The failure of BridgePay to exercise or enforce any right or provision of the TOU shall not constitute a waiver of such right or provision. If any provision of the TOU is found by a court of competent jurisdiction to be invalid, the parties nevertheless agree that the court should endeavor to give effect to the parties' intentions as reflected in the provision, and the other provisions of the TOU remain in full force and effect.

 c.       USER agrees that regardless of any statute or law to the contrary, any claim or cause of action arising out of or related to use of the Specifications or the Specifications

 Agreement must be filed within ninety (90) days after such claim or cause of action arose or be forever barred.

 SECTION TITLES

The section titles in the TOU are for convenience only and have no legal or contractual effect.

Table of Contents