Reply
Highlighted
Member
Posts: 1
Registered: ‎01-28-2015
Accepted Solution

Preventing duplicate transaction errors by including more information

We have a system with some recurring transactions. These transactions can be scheduled either monthly or weekly and are processed in batch. We have one customer who scheduled both weekly and monthly transactions of the same amount. Currently, we are only sending the amount, customerProfileId and customerPaymentProfileId, so of course the second transaction is identified as a duplicated.

 

I'm aware that I could turn the duplicate check off by using x_duplicate_window, but I assume this check exists for a reason. I'd rather just include more information to help ADN recognize that the transactions are different. Which fields should I include in my transaction requests to help distinguish them?

 

Calling createCustomerProfileTransactionRequest with profileTransAuthCapture. Getting the message "A duplicate transaction has been submitted."

 

I'm hoping that I can include an invoiceNumber in the order node. Each of these weekly/monthly transactions have their own record in our database, so I could just send the record id as the invoice number. Would that be sufficient? Which other fields are used during the duplicate check (in case the business decides they don't want to use invoiceNumber)?


Accepted Solutions
Highlighted
Solution
Accepted by topic author hkevqdon
‎08-21-2015 01:58 AM
Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: Preventing duplicate transaction errors by including more information

http://community.developer.authorize.net/t5/Integration-and-Testing/Duplicate-Transactions-AIM/m-p/2...

 

It said AIM, but they use the same fields to detemine duplicate for CIM transaction too.

View solution in original post


All Replies
Highlighted
Solution
Accepted by topic author hkevqdon
‎08-21-2015 01:58 AM
Expert
Posts: 4,525
Registered: ‎03-08-2010

Re: Preventing duplicate transaction errors by including more information

http://community.developer.authorize.net/t5/Integration-and-Testing/Duplicate-Transactions-AIM/m-p/2...

 

It said AIM, but they use the same fields to detemine duplicate for CIM transaction too.