Integration and Testing

[ShekharPosham]

Hi Team,

We have the Auth.Net Hosted payment page integrated in our application. We need to change the "duplicateWindow" time from default 2mins to 15 mins.

I didn't see any option/setting to change the duplicate window for the hosted payment form in the API documentation. 

Could you please assist me on this?? how and where this can be changed?

This is a HIGH priority for us, please help us on this ASAP.

Thank you

[ShekharPosham]

Hi Auth.Net Team,

Any update on this issue/request???

[Renaissance]

@ShekharPosham

What is this? What is a duplicate window? Is this a iframe setting?

[ShekharPosham]

Hi,

There is a setting in TransactionSettings to set the duplicateWindow for the Hosted payment form. While adding this setting getting below error.

And is there any way to change the Duplicate transaction message to something else??

Current Message : "A duplicate transaction has been submitted." -->Needs to change this to "A duplicate transaction has been submitted with in 15 mins."

Error:

{"messages":{"resultCode":"Error","message":[{"code":"E00003","text":"The element 'transactionRequest' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd' has invalid child element 'transactionSettings' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'. List of possible elements expected: 'surcharge, merchantDescriptor, subMerchant, tip, processingOptions, subsequentAuthInformation, otherTax, shipFrom, authorizationIndicatorType' in namespace 'AnetApi/xml/v1/schema/AnetApiSchema.xsd'."}]}}

[Renaissance]

Typing on an iPad. You have multiple issues. The duplicate transaction would be in your merchant interface if it is adjustable. Note that if auth.net doesn't allow you to alter this, you can do it in the source code of your web app.

the Error message at first glance appears to be the result of sending the request using xml. If you send in xml you have to match the schema in the order of nodes. You need to send your transaction request components in a different order or you are missing some.

[ShekharPosham]

Thanks for the update.

I got the solution, the error was due to order mismatch of the attributes in transactionRequest. We need to add the fields in the same order mentioned in the API document.

Would be great, if there is an option/field to change the duplicate tranasaction message (custom message).

Thank you

[Aurelio]

Did you have a fix on this issue? I have the same problem with Facing same issue but no response from anyone and couldnt find this topic troubleshooting in google One Vanilla

[ShekharPosham]

The solution is, we need to add the attributes in specified order in API document. If we miss the order, will get a different error.

Follow the order of the attributes as mentioned below link.

https://community.developer.authorize.net/t5/Integration-and-Testing/Duplicate-Transaction-error/m-p...

Settings for Duplicate window:

JsonDictionaryDTO<string, string> transactionSetting = new JsonDictionaryDTO<string, string>();

JsonDictionaryDTO<string, object> transactionSettings = new JsonDictionaryDTO<string, object>();

transactionSetting.Add("settingName", "duplicateWindow");

transactionSetting.Add("settingValue", "900");

transactionSettings.Add("setting", transactionSetting);

transactionRequest.Add("transactionSettings", transactionSettings);