Resolving Credit Card Processing Problems

User often have issues with PC Charge and X-Charge that are not PC Charge or X-Charge failures. This document helps resolve Credit Card Processing issues.

Ensure you have internet connection.

Go to your internet browser to bring up google.com. If you can view this page, you have verified your internet connection. If the page does not show up, restart your router, and internet modem.

Make sure your Card Reader is Working

Test the card reader by swiping a card into note pad. DO NOT SAVE THIS INFORMATION *

If the card does not read, then you have a bad card reader, or a bad card. If the card reads only one track, then it may be a bad card or reader.

If the card reader reads improperly, try another card. If it continues to read badly, unplug the reader and plug it back in. If the same events occur after this, try another reader.

For PC Charge - Turn on Debugging.

IODebug.log The IODebug.log is a text file created by the PCCharge that can be used to view the transaction requests and responses that are processed by PCCharge. Logging to the IODebug.log file is disabled by default. To activate IO Logging, either use the command line switch (/IOL) or, from the PCCharge GUI, hold down the Shift key and then hit the F11 key. For more information on the PCCharge command line switches, see the section Command Line Switches (see page 88). Once logging has been enabled, the text “IOLog Enabled“ will appear in the title bar of PCCharge. While logging is enabled, every transaction request and response (whether submitted from the PCCharge GUI or via integration) will be placed in the file IODebug.log. This file will be located in the PCCharge directory. The following is an example of the type of information that will appear in the IODebug.log file:

Trace: • iodebug