{"id":4232,"date":"2016-10-20T08:34:03","date_gmt":"2016-10-20T13:34:03","guid":{"rendered":"http:\/\/3dmerchant.com\/blog\/?p=4232"},"modified":"2021-12-03T03:23:53","modified_gmt":"2021-12-03T08:23:53","slug":"authorize-net-duplicate-transaction-settlement-error","status":"publish","type":"post","link":"https:\/\/3dmerchant.com\/blog\/merchant-processing-industry-news\/authorize-net-duplicate-transaction-settlement-error","title":{"rendered":"Authorize.net Duplicate Transaction Settlement Error"},"content":{"rendered":"

Authorize.Net experienced an issue during a system update on October 17th that caused a subset of previously settled transactions from September to be sent for settlement again between October 17th and 18th. This issue is no longer occurring.<\/p>\n

Authorize.Net is currently working to address any duplicate transactions in order to resolve the duplicate funding to merchants and potential duplicate transactions to their customers. We have already contacted your affected merchants and will continue to do so as we have updates.<\/p>\n

If your merchants contact you about this issue, please advise them to NOT take any action on these transactions while we work to address them.<\/p>\n

We will follow up with you with any further information, including information on potential reimbursements, as it becomes available.<\/p>\n

To locate these transactions, please have your merchants follow these steps:
\nLog into the Merchant Interface at https:\/\/account.authorize.net\/.
\nClick Search from the main toolbar.
\nClick Search by Batch from the menu on the left.
\nSelect October 18 and October 17 in the From and To drop-down boxes in the Settlement Date section.
\nClick Search.
\nAny impacted transactions will have a Submit Date from September 20-25.<\/p>\n

We apologize for this error and any inconvenience it may have caused. If you have any questions regarding this email, please contact support.<\/p>\n

Sincerely,
\nAuthorize.Net<\/p>\n

###<\/p>\n

Blogger Note: While uncommon, duplicate transaction and duplicate settlement issues do happen. They can emanate from anywhere in the transaction chain, though the payment gateway, or payment processor are likely more common causes. Because of that, merchants are advised to do nothing and the party that caused the problem usually reverses all the errors on behalf of merchants, typically within a day or two.<\/p>\n","protected":false},"excerpt":{"rendered":"

Authorize.Net experienced an issue during a system update on October 17th that caused a subset of previously settled transactions from September to be sent for settlement again between October 17th and 18th. This issue is no longer occurring. Authorize.Net is … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":11,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[10,537],"tags":[43],"class_list":["post-4232","post","type-post","status-publish","format-standard","hentry","category-merchant-processing-industry-news","category-payment-gateway","tag-authorizenet"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t