I’m meeting some problem understanding how my current Payment Gateway(ProcessPink) identify duplicate transactions. The “document man” says:
If there are 2 transactions for the same credit card, with the same
amount happen within 20 minutes, then they would be considered
duplicate. An error would be returned.
Personally I think this is a too-simple technique, which prevent our customers issue 2 orders: for example, there are 2 things with the same price in our online store, how can I tell that people should wait 20 minutes before trying to buy the second one?
Here’s my questions:
1) Is this a popular practice for payment gateway? Or is there any alternative?
2) How can I work around this problem? I have thought of a shopping cart, but it doesn’t fit my context. In short, my application need to perform 2 or more separate transactions (from the same card and with the same amount) within 20 minutes.
Any help would be appreciated.
Yes, but usually the time window is smaller and adjustable. Authorize.Net’s is 3 minutes by default and you can change that with a parameter during the transaction.
Do an authorization only on the second purchase and then capture it after 20 minutes. It’s a pain in the butt to set up and do but I can’t see any other user-friendly way around this.