0

I'm not sure this is a good question. That said, I don't know exactly what question I should be asking, so if I can just find out that piece of information, I think this will have been worthwhile...

At work, we have a machine that takes CC payments. The screen times out after 150 seconds, and if the CC gateway hasn't come back with an auth code at that point, the machine (stupidly) declares the transaction failed. The user is then apt to try again. Problem: the transaction may actually go through (or have already gone through), resulting in a double charge.

What would be an intelligent way to deal with this situation? We looked into voiding any transaction not already seen as successful at the point of timeout, but we need data from the response in order to do that. If we had the response, we wouldn't have a problem.

  • Regarding time required to process: we don't have any idea why it takes so long to process. That's entirely out of our hands; we communicate with the gateway via the internet (HTTPS) and they talk to the processor on their own. –  May 03 '13 at 17:11
  • Further note: the average time required for processing is on the order of 3-5 seconds. Some of these broken transactions are taking more like 3-5 *minutes*. –  May 03 '13 at 17:12

1 Answers1

0

I wrote up a vague answer to a vague question but I think we need more information to be of much help. Possibly the first course of action is figuring out why it's taking so long to process.

StoneStone
  • 31
  • 5