Troubleshooting Errors

Most PCCharge Payment Server errors are displayed as either "Connection Error" or "Invalid Track Data". Payment processor responses such as DECLINE are not shown below. This topic discusses only configuration errors in Amigo Pos or PCCharge Payment Server. Common errors encountered when testing the Amigo Pos PCCharge Payment Server interface are:

•	Connection Error

•	Invalid Track Data

•	Invalid User Id

•	Invalid Processor

•	Transaction Type Not Supported

•	User In Use

Connection Error

The "Connection Error" message (sometimes shown as error #10061) is caused by one of the following:

1.	PCCharge Payment Server is not configured to accept TCP/IP communications. Refer to the PCCharge Payment Server configuration topic for additional information.

Enable TCP/IP Communications in PCCharge Payment Server

2.	The correct IP Address of the pc running PCCharge Payment Server is not entered in Amigo Pos Back Office. Refer to the PCCharge Payment Server configuration topic for additional information.

Type IPCONFIG at a command prompt to determine the IP address of the PC hosting PCCharge Payment Server

3.	The correct network port is not entered in Amigo Pos Back Office. Refer to the back office settings topic for additional information.

Enable TCP/IP Communications and note the Local Port Number

4.	Windows Firewall is blocking the PCCharge Payment Server communications port. Refer to the back office settings topic for additional information.

Windows Firewall Exception for PCCharge Payment Server

^Top

Invalid Track Data

The "Invalid Track Data" error is caused by incorrect magnetic card reader configuration. Mostly likely the card reader is sending carriage returns between tracks so that PCCharge Payment Server only receives Track 1 data, although there are other causes for this error, such as sending additional characters between tracks. Refer to this help topic for instructions on programming the card reader. Note that this error will not prevent Amigo Pos from sending manually entered transactions to PCCharge Payment Server.

Right!

%B9991112223334445^PUBLIC/JOHN Q^1112223334445557778881112223331?;3444555777888999=88999000111222333444?

Example 1: A properly formatted swipe

Wrong!

%B8768010000381411^PUBLIC/JOHN Q

^0807101006510000000000381000000?

;8768010000381411=08071010381000065100?

Example 2: An improperly formatted swipe

^Top

Invalid User Id

The PCCharge Payment Server User Id entered in back office is either incorrect or doesn't exist in PCCharge Payment Server. Note that the User Id is case-sensitive, so that user1 is not the same as User1. Refer to the back office settings topic for additional information.

Back Office PCCharge Payment Server User Id

^Top

Invalid Processor

The PCCharge Payment Server User Id entered in back office is either incorrect or doesn't exist in PCCharge Payment Server. Note that the User Id is case-sensitive so that Visa is not the same as VISA. Refer to the back office settings topic for additional information.

Back Office PCCharge Payment Server Processor Id

^Top

Transaction Type Not Supported

This transaction error message may appear when attempting to add a gratuity to a Sale transaction. Such transactions are referred to as "Restaurant" transactions and are not supported by all processors. If the payment processor does not support Restaurant transactions, change the processing type to Pre-Auth/Capture.

Back Office PCCharge Payment Server Transaction Type

^Top

User In Use

Amigo Pos may receive a response “Not Captured: User In Use” from PCCharge Payment Server. There are a couple scenarios where this may happen:

There are multiple pos stations and more than one sends transactions with the same User ID. The User In Use response is letting the merchant know that the User ID is being used by another system at that time. In addition, if the PCCharge Payment Server user interface is open, the user logged in to PCCharge must not be in use by any pc running Amigo Pos. Obtain an additional user id to correct this issue.

The other time this response is seen is when the network connection between the POS and PCCharge Payment Server is disrupted as soon as the transaction is sent. The next transaction will return a “Not Captured: User In Use” response. This alerts you that the previous transaction may have been processed. PCCharge Payment Server does not want to process any further transactions until you review the transactions to make sure it was either Captured or Declined. Then, PCCharge Payment Server must be restarted to clear up the “User In Use” response. Once that is done, transactions will begin to process as usual.

^Top

Page url: http://www.amigopos.com/help/html/index.html?pccharge_troubleshooting_errors.htm