Skip to content

PC Charge integration setup

Configuring Go Software PC-Charge Pro with ProfitSystem

Discontinued service as of November 2015

NOTE: Before attempting to set up ProfitSystem for use with PC-Charge, make sure that the PC-Charge software is installed and configured first. You must be able to successfully process a credit card directly through the PC-Charge application. If you cannot successfully process a credit card directly through the PC-Charge application,you will not be able to process a credit card charge through ProfitSystem.

The PC Charge setup includes the creation of users & cashiers. The number of user accounts setup in PCCharge should match the user level purchased. For example if a 10 user license of PCCharge was purchased, then you should add ten user accounts. Users should be given names within PCCharge like, USER01, USER02, USER03 ..etc. Use this naming convention tor successful ProfitSystem integration.

PCCharge version 5.8 and newer requires another user type created called Cashiers. Cashiers are given permissions to perform tasks in PCCharge, like to process card credit cards. Cashiers must be given secure passwords that are PCI compliant and changed every 90 days (automatically enforced by PCCharge software). PCCharge requires a Cashier to be created called SYSTEM. This cashier cannot charge credit cards. They also suggest optionally a cashier called MANAGER which has all security turned off so that the SYSTEM Cashier can perform any task. For ProfitSystem integration we recommend a Cashier be created called APICASHIER & given permissions to perform any electronic payment function. ProfitSystem only requires one Cashier for all registers and this APICASHIER username and password will be entered into ProfitSystem in a single location - see below the instructions.

To configure ProfitSystem to process credit card Sale and Credit transactions with Go Software’s PC-Charge Pro, follow these steps:

Step 1

From the ProfitSystem Main Menu, choose Main->Housekeeping->General Setup->Stores-> Options Tab.(for multistore implementations this must be completed for each store) On the Options tab' Locate Credit Card Processing from list – Choose GO (Go Software, makers of PCCharge was acquired by Verifone) Locate Bank Processor – Choose from processors in the list Locate Merchant ID – Enter the same merchant ID that was put into PC-Charge Locate Credit Card Processing Path – Enter the folder path location where PC-Charge will look for the *.INX file that ProfitSystem will create whenever a credit card payment is taken. This is usually the same folder that PC Charge was installed to.

For multi-users, we recommend using a UNC-type path to the PC-Charge program (example: \PROGRAM FILES\PCCW). Note: This assumes your PC-Charge folder has been shared on your computer and has been configured with full read-write accessibility.

For single-users, the direct path may be used (example: C:\PROGRAM FILES\PCCW)

Cashier: Cashier name, sent in request file if it's non-empty. Required for PC Charge 5.8 or newer. For older versions leave blank Password: Cashier password, sent in request file if it's non-empty. Required for PC Charge 5.10. For older versions leave blank Req file prefix: If this field is left blank, request file will be named STA[credit card ID].INX. This is compatible with older versions of ProfitSystem and PC Charge. For new installations, it should be set to USER This will cause the request file to be called User[Credit card ID] which will match the users created within PC Charge.

Note The Credit Card ID mentioned above is set for each register in the Register setup form described below. Credit Card IDs must be unique for each ProfitSystem register and cannot exceed the total user license purchased for PCCharge, i.e. you purchased a 10 user license of PCCharge you cannot enter or provide a Register credit card ID of 11, 12,13 etc. .

Step 2

Before exiting and restarting ProfitSystem, click on the Register Setup button. Housekeeping->General Setup->Register. Here, a Credit Card ID must be entered for each register within ProfitSystem. Chances are Credit Card IDs will appear but all should be reviewed to determine if correct. To do this: Click on a register name to highlight it on the list tab. Next click the Details tab at the top. Locate the field labeled Credit Card ID found in the upper-right corner of the form and enter a number you wish to use for the register’s ID. For example 1, 2, 3 ..etc. This number should equal or be less than the number of users you have licensed/purchased for PC Charge. Each station number must be unique for each register. Click the Save button. Click on the List tab at the top, select the next register name and set the Credit Card ID number for that register. Continue until all ProfitSystem registers have unique IDs set. When complete, exit out of the ProfitSystem program, then re-start. When a credit card is processed in ProfitSystem, a request file will be created in the directory path that was specified in Step 1 above. ProfitSystem will prepend the letters set within the Req. file prefix field in step 1 above. If blank ProfitSystem will prepend STA for backward compatibility with older ProfitSystem/PCCharge installations. In addition, if the Credit card ID from the register file setup is a single-digit number, a “0” will be prepended to the number when the request file is created. Below are two examples: 1. A credit card is processed on a register configured as Credit Card ID 1, ProfitSystem will create a request file named STA01.INX. 2. When a credit card is processed on a register configured as Credit Card ID 10, ProfitSystem will create a request file named STA10.INX.

PCCharge is set to look for requests files that instructs the software to perform specific payment tasks. When completed PCCharge will give ProfitSystem back a response file with the payment results.

Note

The Test Credit Card integration button tests the specified integration PATH. Two tests are performed. 1) To insure the path is valid, ie it exits, 2) That the user currently logged into ProfitSystem can write to the path. Wether or not a user can write to a folder in the entered path is a operating system permissions setting. If the tests fail then you may need the help of a network IT person to help increase the permissions of all users / registers that will be performing electronic payments.