Reply
Highlighted
Member
Posts: 1
Registered: ‎05-04-2020
Accepted Solution

Transaction Settings

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.
 

Accepted Solutions
Highlighted
Solution
Accepted by topic author FranciscanMedia
‎05-19-2020 04:14 AM
Administrator
Posts: 145
Registered: ‎11-29-2017

Re: Transaction Settings

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.

View solution in original post


All Replies
Highlighted
Solution
Accepted by topic author FranciscanMedia
‎05-19-2020 04:14 AM
Administrator
Posts: 145
Registered: ‎11-29-2017

Re: Transaction Settings

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.