Support Forum
Customer had declined transaction and second attempt said the purchase would be a duplicate. - Thu - Sep 1, 2011 - 12:06pm
-
Declined Reason: A duplicate transaction has been submitted
Authorize.net has a function to prevent a duplicate transaction from taking place for the customer's protection. This is their way of saying:
"Oops, it looks like you submitted the same transaction twice, and we want to stop you before you get charged twice."
Typically, the duplicate time frame is set for 2 minutes. So, if a customer attempts to purchase tickets, their card is declined, and they attempt to purchase tickets again on the same screen with the same credit card and billing address (all within a 2 minute time period from the initial attempt), it's possible that they will see a message on the screen stating that it is a duplicate transaction.
For more information about this function, refer to your gateway's support forum. If your customers try the purchase again after several minutes have passed, they should not receive an error.
View Our Video Tutorials
Related Discussions
Do I need to complete a questionnaire for PCI compliance?
How do I connect my Authorize.net gateway with ThunderTix?
Where can I get my Verified Gateway Seal for my checkout page?
Declined Card, but Pending Charges on Bank Account
How do I connect my Moneris account with ThunderTix?
What credit card readers will work with Thundertix?
Authorize.net error - "The merchant login ID or password is invalid or the account is inactive"