TransAction+ Documentation (Cheesecake) WIP
- Alger Alama
TransAction+ is a payment processor with internal software that integrates with NorthStar Order Entry in order for clients utilizing it to be able to take credit card payments at their point of sale.
Table of Contents
ECM Configuration
Please speak to a CBS representative to turn on feature flag for LoyaltyV2 for account to have access to this set up.
TransAction+ Payment Processor
This setup allows for TransAction+ to be utilized as a credit card processor for ECM payment setup.
Log into ECM.
Navigate to Sites > Sites and Groups
Edit a Site.
Click on Payment tab.
Click on Add Processor.
Click on TransAction+ processor.
Set TransAction+ as main Credit Card processor along with Display Name and provided Store Id.
Payment Device Configuration
Navigate to the Peripherals Tab.
Add a new payment device
Add a name (Usually the brand and model of payment hardware), then select ‘type’ and choose transaction+
Enter a Terminal Id after selecting TransAction+. (This can be any number the user account wants, but they should be keeping track of this.)
Navigate to Devices → Edit the Device you want to add the Payment Device to → Add the payment device.
Completed ECM setup.
Terminal and Payment Device Prep
Prepping the terminal is important to make sure all the hardware and software is installed correctly and functions properly
Attaching Payment Device
On the Terminal, open the Device Manager in Windows OS.
Open the drop-down for Ports - Should show all available ports not being used.
Attach the payment device to an open port. - New device should immediately display in Device Manager. - Example here is an Ingenico Lane 3000 payment device.
IMPORTANT - Make note of the COM # that displays for attached device.
Install Device Manager by GK Software.
Upload this GK Software Device Manager zip file to the C:\CBS folder of the terminal. -
Unzip the file.
Navigate into unzipped Device Manager file and install the GKSoftware.PATT.Service.Install.572 software to the terminal.
Click Next.
Click Install.
Complete installation of software.
Open services.msc and check for GK T+ Device HQ service, and verify it is running.
Installation is completed and verified.
Configure Device Manager software.
Make sure Device Manager from GK Software is installed first before starting this step.
Navigate to C:\Program Files (x86)\GK Software\Device Manager.
Right-click on GKSoftware.PATT.Service file and run as an administrator.
A warning will display that the software service is running in the background and click OK.
The TransAction+ Device Manager GUI will display. Click on Settings.
The Application Settings will display.
T+ Address - IP Address that T+ will be installed on.
T+ Backup - IP Address that T+Backup will be installed on.
POS Type - Point of Sale options.
Fake POS API - Used for testing. (Use this if this is the initial setup and testing.)
POSitouch - Legacy POS software.
SPCWIN - IP Address of POSitouch main server. (Leave this by default.)
Default EMV - Options depend on hardware.
Options with the word production at the end are ONLY FOR PRODUCTION and actual credit card charging.
EMV FDMS NoCVMSignature test - Choose this for testing and training.
Default Template - Will change depending on the choice set from Default EMV
Mobile - Should be default option.
Under the Devices tab click on the +Add option.
The Device Settings will display.
Enabled - Make sure this is checked if setting up a payment device in this Device Manager software.
Name - Name of payment device.
Payment Profile - Several options here that depends on how site wants to take payment on device.
Remote Pay (default) - Choose this option for training and testing.
Device Type - Brand and model of payment device.
Device Connection - Connection type of payment device.
TCPIP - IP based device.
If chosen, these options will display and need to be filled.
SerialOrUSB - Serial or USB based device. (Remember noted COM # from Attaching Payment Device section earlier)
If chosen, the COM # options will display.
T+ Store Id - Number depends whatever the user account wants it to be.
Terminal Id - This number should match what’s set up in the Payment Device Configuration step previously.
Logging Profile - Default Log4Net. (Set as default)
Capabilities tab will change depending on how the site wants the device to take payments.
EMV Enabled - Is device EMV enabled?
Quick Chip - Is device Quick Chip enabled?
Emv Profile - Should match Default EMV setting from previous Device Settings.
Contactless Mode - Several options here depending on payment device.
EMV - Default choice for both production and testing.
Signature Capture - Does user want device to capture signatures?
No signature for EMV - Do you not want signatures for EMV
Disable Manual Entry - Does user want to disable manual entry of cards on device?
Custom Form Config - Normal or None options only.
None - Default option for testing
Normal -
Allow PIN Bypass - Circumvent PIN number.
Verify Device S/N - Does user want device to verify the serial number?
Pay at the Table tab depends on how user wants device to funciton at a table.
Remote Pay tab depends on how user wants device to function as a remote payment.
Suppress Amount Ok - Set this for testing to stop asking if amount is ok on payment device.
Click return when completed.
The Tips tab setting will depend on how they want tip percentages set for the device.
The Services tab depends on how the users want to set up the device ports.
HTTP Reset Timeout - Set this to 60 seconds for testing.
Receipt Info tab depends on site address and information.
Redundancy tab depends if site wants to set up redundancy for payment device.
Click Save once completed.
Open services.msc and restart GK T+ Device HQ service after all change have been applied and saved in TransAction+ Device Manager.
Device Manager configuration completed.
TransAction+ Software
Similar to NetePay, the user can install the TransAction+ software on either the main server or on a separate terminal/pc. It must still be on the same network or TransAction+ will not function.
Installation of TransAction+
Upload this file to the server that will be running TransAction+ and unzip the file.
Two files will unzip.
FakeNet folder - Contains fake testing credentials.
txnp-76-2_0_p15-silent - TransAction+ Installer.
Right-click on txnp-76-2_0_p15-silent installer and install T+ software.
Click OK on following options during installation process. (It all goes by fairly quickly.)
From the unzipped FakeNet folder, copy the two files in there DBSEFTM.CFG and DbsLicense.lic and paste/replace them into C:\Txnplus\Admin folder.
Navigate to C:\Txnplus\Admin and right-click on DbsEft.exe file and run as an administrator.
TransAction+ windows will display.
Click on View.
Click on Options.
A license warning will display after a new install - Click Ok for now.
Options tab will have several options.
Processors - You can add the specific processor that will be utilized through TransAction+.
Quick Training - Click this to apply immediate test/training credentials. Click OK when prompted about this.
Training Mode Password - 1234 and today’s date backwards. (Example, if today’s date was July 21, the PW would be “123412”
Set Days Limit to however long you want to have training set.
Training Mode will display the processors after completion.
Modems - If site still uses a modem, set it up here.
Card Types - Set up specific card types accepted by the merchant along with tender types. (Should be filled with the test card data already from the files transferred from FakeNet folder earlier.)
POSitouch - Exclusive options for POSi point of sale software.
System - System options for wherever this T+ software is installed.
Alerts - Add alerts to the system if needed.
Mirroring - Allow for mirroring of T+.
Click OK when completed. T+ will apply and load all configurations.
Open services.msc and verify that DBS T+ TransactionPlus and NorthStar services are RESTARTED and are running.
Completed.