Skip to content

Stores accounts Credit Card gift Card

Action: STORES

Credit Card/Gift Card Tab

Optional setup. Used when electronic payments, like credit card processing, are integrated with ProfitSystem.

Fields

Credit card processing...The software you are using for credit card processing, only applicable if you have the credit card processing integration. Select IC-Verify, IC-Verify3 (if you are using IC-Verify version3 or later), or Go (PC Charge) or IPCh

arge/Payware Connect, ChargeIT, or Authorize.net. Otherwise, select None.

IC-Verify and IC-Verify3 Processor...Select your processor from the list. Additional processor codes may be added to the system when needed from the Credit Card Processors form.

Merchant ID...RIFY by default.

Credit card processing path...The PCCharge folder location where PCCharge is configuredto look for its request and response files. Typically this is in the \PROGRAM FILES\PCCW folder.

GO (PC Charge) PC Charge is installed locally and processes credit cards on behalf of the Profit System.

Processor...Select your processor from the list. Additional processor codes may be

added to the system when needed from the Credit Card Processors form.

Merchant ID...Enter your merchant ID.

Credit card processing path...The folder where IC-Verify looks for request files.

Cashier...The cashier user name from PC-Charge

Password...The cashier password from PC-Charge.

Req file prefix...By default, the integration will create a request file called STA[work station number].INX. For example, if the workstation number is 1, then the request file name is STA1.INX. This setting allows the STA prefix to be replaced. Enter the alternate prefix (such as USER) In PC-Charge the request file name must match a username. So, if the request file name was STA1.INX, then there must be user STA1 in PC-Charge. If, however, the user in PC-Charge was USER1, then this field should be set to USER, so the request file name would be USER1.INX

Test CC integration...For ICVerify & PCCharge software integration testing. The credit card integration should be tested after it is set up for the first time, or if any changes are made. This button will test the integration by sending a credit card charge to the processing software. If successful, a message will appear: 'RESPONSE:', followed by the actual response from the processing software. The credit card will actually be declined because it is invalid. However, if the response is received it means that the communication between ProfitSystem and the processing software is working. If a 'NO RESPONSE:' message is shown, it means that therequest file created by ProfitSystem is not being processed by the processing software. ProfitSystem will display a message as it is waiting for a response from the processing software, once it creates the request file. This message will show the path where the request file is created. This is useful to troubleshoot problems.

IPCharge (Payware)

IPCharge is an internet based payment service and it requires login information. These fields of information will be provided by the bank processor and should be completed for each store that will be using IPCharge for electronic payments.

User Name...

Password...

Merchant ID...

Merchant Key...

Technical notes: If a file called paywaretest.txt is present in the ProfitSystem install folder, the Payware integration will use Payware test URL's rather than the production URLs. These URLS are used for troubleshooting and testing and should only be used by BBL technical support.

Auth.Net (Authorize.net) Obtain your account by signing up for service at this url: http://reseller.authorize.net/application/?id=5555631A

Authorize.net can provide a merchant account or you may use an existing merchant account. When selecting an account type select CARD NOT PRESENT account. The provides several benefits 1) you may use authorize.net for ProfitSystem to process cards in the store 2) You may use the account on a eCommerce site to process cards and 3) You may save customer credit cards for later use by adding the Customer Information Manager option to the service. Authorize.Net is an internet based payment service and it requires login information. These coded fields of information can be retrieved from the Authorize.net web console. Once Logged in, choose Accounts-> Settings-> API Login ID and Transaction key to acquire the needed info.

Login...

Trans Key...

Technical notes: If a file called authtest.txt is present in the ProfitSystem install folder, the Authorize.net integration will use Authorize.nets test URL's rather than the production URLs. These URLS are used for troubleshooting and testing and should only be used by BBL technical support.

ChargeIT

ChargeIT requires one or more POSLynx units to be connected to the local area network via network cable. Each POSLynx unit can support one serial type pin-pad, and up to 10 network based pin-pads. The POSLynx unit should be connected to the network and turned on, and all the pin-pads should be connected and activated before setting up ChargeIT in the ProfitSystem.

Once you are signed up with ChargeIT, you will receive your hardware and your set up details. You should have one or more ChargeIT URL's, a Lane for each pin-pad, and a pass phrase. The Lane identifies the pin-pad/terminal. You will go to Register Set up to configure what Lane will be used to process charges for each register.

If an actual terminal (MX915 or VX820 for example) is used with a register, then the Lane for that terminal should be entered in the Register Setup. The Process on Terminal option at charge time will only appear if a Lane is set up for the Register. Even if no Lane is specified, the card can still be entered manually or swiped using a un-encrypted keyboard swipe.

Gravity/ChargeItPro

Gravity used to be called ChargeItPro.

Once you are signed up with Gravity Payments, you will receive your hardware and your set up details.

Emergepay/Clover Devices

Emergepay requires no special service to run on a computer. Emergepay uses Clover terminals.

On the Register Setup form, enter the OID, HMAC, and Auth Token to enable Emergepay payments. The OID, HMAC, and Auth Token are usually the same for registers at the same store.

Enter a Clover device name to enable a physical terminal.

Credit cards can be manually entered in the pin-pad/terminal for phone orders. Also, manual entry of credit cards via keyboard is available. When processing a charge, click the Manual Entry button on-screen to enter a card directly.

The web-based Gravity Payments dashboard is located at https://dashboard.gravitypayments.com and can be used to view transaction reports and review charges.

Cloud Hardware/PAX Devices

The ChargeItPro Cloud Hardware service should be installed on one computer. It is configured from the url http://localhost:8010. ChargeitPro will assist with installation and configuration.

You should have a device name and a location code for each terminal/pin-pad. The Device name identifies the pin-pad/terminal. The Location code is normally the same for all devices, and identifies the store location.

Using the Register Setup form, enter the device name and location code to be used at each ProfitSystem register.

Credit cards can be manually entered in the pin-pad/terminal for phone orders. Also, manual entry of credit cards into the ProfitSystem can be enabled as well. By default, manual entry into the ProfitSystem is not enabled, as it's less secure than entry into the pin-pad/terminal. However, if needed, it can be enabled on this form.

The web-based Gravity Payments dashboard is located at https://mp.chargeitpro.com and can be used to view transaction reports and review charges. To view all transactions for a day, go to Reports, and click All Activity. If All Activity is not selected, then Voids will not be shown.