Transaction Settings

FranciscanMedia — Mon, 04 May 2020 16:09:58 GMT

I have a duplicate window setting defined for the transaction setting in an api, using c# and the authorizeNet SDK. Below is the relevant code.

"
....
//transaction setting Duplicate Check
var transactionSettings = new settingType[] {
new settingType
{
settingName = settingNameEnum.duplicateWindow.ToString(),
settingValue = "120"
}
};
//end transaction setting Duplicate Check

var transactionRequest = new transactionRequestType
{

transactionType = transactionTypeEnum.authCaptureTransaction.ToString(), // charge the card

amount = amount,
payment = paymentType,
billTo = billingAddress,
lineItems = lineItems,
userFields = userFields,
order = order,
transactionSettings = transactionSettings
};
...
"
in testing, in the sandbox the setting does not work. Several testers were able to create more than one transaction within the 120 sec defined window.

Re: Transaction Settings

mmcguire — Mon, 11 May 2020 22:31:13 GMT

The transaction request fields listed in the article below would need to match the previous request exactly to trigger the duplicate transaction window check.

https://support.authorize.net/s/article/Error-11-A-duplicate-transaction-has-been-submitted

If any of the fields differ in subsequent requests it is not considered a duplicate and it will be allowed.

The setting works the same way in both the sandbox and in production.

topic Re: Transaction Settings in Integration and Testing

Transaction Settings

Re: Transaction Settings