We are using PCCharge Payment Server 5.7.1 F, installed on a server machine. We have two RMS POS workstations. We have configured our EDC settings to point to PCCharge on that server.
Over the weekend, we discovered that there were several transactions duplicated in PCCharge. They had the same TroutD, and initially they looked like they had the same authorization code. Using a utility program given to me by PCCharge support, I looked at the raw batch data, and saw that the duplicates were sent within 1 - 2 seconds of each other. They had the same TroutD, but they did have different (sequential) authorization codes.
Has anyone ever encountered this problem before, when one copy of PCCharge is serving multiple RMS POS workstations?
During the interim, we have changed our tender types in RMS from Credit Card to Other. When our cashiers have a credit card transaction, they bring the card into the office,whre PCCharge Payment Server is running, and run the card directly through PCCharge. We've done this for two days, with no duplicates.
One concern is the time delay from the time we swipe the card in RMS to the time PCCharge sends back the authorization. In our current environment, with PCCharge on a server machine, the time from card swipe to authorization in RMS is about 5-7 seconds. During my testing, when I had RMS and PCCharge on the same box, the time was
2-3 seconds. One suggestion that PCCharge gave me was to install a copy of the payment server software on each workstation, so that time delay would disappear. I know there are several people here who have multiple registers hitting one copy of PCCharge. What sort of timing from swipe to authorization are you experiencing?Bill Yater The Worth Collection snipped-for-privacy@worthltd.com