RMS and PcCharge Payment Server

We've had this exact problem. We're using RMS 1.3 PcCharge 5.71 Release B. We've also had it where the amount didn't go through. So, you can go into PcCharge and look up the transaction amount and it shows it went through, right? Sorry no advice, but you're not alone.

Any insight into reducing these time out issues?

"James Froxylia" wrote:

We have always dealt with this problem with no solution. Once RMS gives the request to PCcharge, it has no control over how accurately that request gets processed. Sometimes the signal gets lost on the way to the bank and the card doesn't get charged, sometimes gets lost on the way back and the card does get charged but no notice received. The duplication error is a good indication that the customer already paid, but the only way to make sure is to check the pccharge report and compare totals to the settlement inquiry.

Our current workaround when the case happens that the card processes but leaves RMS in the lurch: sell the transaction to cash, get an imprint and signature for chargeback protection, then add the money to the correct batch tender totals which will show an overage in the card tender and shortage in cash but should still balance.

Probably the better solution would be to use the RMS built in connection to a Vital account.

Matt

How often does this happen. I've not seen this on my system.

Ed

"Matt Hurst" wrote:

Why don't you rid off pc charge and use rms software for payment transaction also. You can use wells fargo,city,boa or chase. or Use mercury they are very good on RMS.

I have 42 stores - and this happens to at least 4 stores a week.

Hello Ladies and Gentlemen, I'm having a unique problem that I have a hit a wall with. Please Help! First lets start off with the software that I'm running, Microsoft RMS 2.0 SP1 and PcCharge Payment Server 5.7.1 I Sp9a. Second lets talk about the problem. A customer walks through the line uses a Credit Card or Debit Card and the transaction times out - the cashier reruns the transaction and receives the Duplicate Transaction error message. On the back end I can look at the PcCharge logs and the transaction is sent from RMS to PcCharge. PcCharge sends it to the payment processor and receives the acknowledgement that the card is good. Presumably PcCharge sends the ack to RMS, but RMS doesn't receive it. So the real problem is that PcCharge is capturing the money but RMS isn't getting the message.

Anyone else having a similar problem? Thanks for your time, Jim

Ive read all thes eposts and this is just the way PCCharge works. IF PcCharge send back a return file that RMS doesnt recognize like a time out, it will aprrove the transaction and you the merchant dont get paid. There is a simple way to avoid all this and its not to use PcCharge or ICterrify, We strictly use Hypercom Smart client, or Hypercom server and the RMS addon from hypercom. These situation dont happen using this software and also opens up other signature capture device not supported in RMS.

Not sure if you have this option but what you should be able to do is if you have a dup transaction (that was approved in PCCharge but not in RMS) is have the option to accept the dub in RMS as an approval (ideally even get back the dup approval code back to post in RMS). This is what we added to the TPI Software RMS plug-in