- joeykikerAsked on January 27, 2017 at 03:02 PM
Using Authorize.net they gave us the following feedback that might prevent this from happening again. Can not find a setting in JotForm that allows this:
Response Reason Code: 11
Response Reason Text: A duplicate transaction has been submitted.
Notes: A transaction with identical amount and credit card information was submitted within the Duplicate Transaction Window.
The error indicates that a transaction request was submitted within a few minutes of a previous attempt with the same information. Authorize.Net identifies duplicate transactions by matching the data provided with the transaction.
The data fields that are validated are:
API Login IDx_loginCredit Card Numberx_card_numExpiration Datex_exp_dateTransaction Typex_typeBank Account Numberx_bank_acct_num
Routing Numberx_bank_aba_codePurchase Order Numberx_po_numAmountx_amountInvoice Numberx_invoice_numCustomer IDx_cust_idFirst Namex_first_nameLast Namex_last_nameCompanyx_companyAddressx_addressCityx_cityStatex_statePostal Codex_zipCountryx_countryDuplicate Windowx_duplicate_window
If any of the fields change from one transaction to the next, Authorize.Net will not view the transactions as duplicates.
The duplicate transaction window will always be two minutes for all transactions submitted through the Virtual Terminal. If you wish to adjust the duplicate transaction window for transactions submitted from your software, such as a website or shopping cart, you may do so by adding the field x_duplicate_windowto your website script.
If you are unable to adjust or add this variable to your shopping cart settings, please contact your shopping cart support team for additional assistance in this regard. The variable x_duplicate_window tells us, in seconds, how much time we should check for duplicates after a transaction is submitted.
The largest value we will accept for x_duplicate_window is 28800, which equals eight hours. If a value greater than 28800 sent, the payment gateway will default to 28800. If x_duplicate_window is set to 0 or to a negative number, no duplicate transaction window will be enforced for your software's transactions. If no value is sent, the default value of 120 (two minutes) would be used.
For example, if you wished to set a duplicate transaction window of five minutes, you would set x_duplicate_window to 300, as there are 300 seconds in five minutes.
Note: By submitting x_duplicate_window with your online transactions, we will return further details along with this error response, including:
• The original transaction ID that was duplicated;
• AVS and CVV responses for the original transaction;
• The original authorization code, if the transaction was authorized;
• The MD5 hash, if a MD5 hash value was generated for the original transaction.
If you do not submit the x_duplicate_window field, we will not return any details from the original transaction, even if you submit a duplicate transaction.Page URL:
- JotForm SupportMike_GAnswered on January 27, 2017 at 06:04 PM
To my understanding, one of your donors submitted the form only once but was charged 20 times or there are 20 transactions showing in Authorize.Net for that donor, is that correct? As that should not be possible, may we request you to provide us more information about that particular submission, please? And if I understand it correctly also, that the submission was made on the form embedded on the website you included in your post (https://1bsa.org/donate/pay.php)
With regards to the Duplicate Transaction feedback, if a duplicate transaction has been submitted to Authorize.Net, we don't have such feature on our Authorize.Net integration. I can submit a feature request on your behalf, but I cannot guarantee that it will be implemented soon.
We can prevent duplicate submissions through our forms, please check the guides below to learn how to.