cancel
Showing results for 
Search instead for 
Did you mean: 

Who Me Too'd this topic

Disabling TLS 1.0 breaks DPM Integration - works fine w/ TLS 1 enabled

Ever since taking measures to increase PCI security (namely, disabling TLS v 1.0), Authorize.net seems to be unable to post data back to my website. 

 

The message the customer recives, on AuthNet's gateway/transact.dll page, is

 

"An error occurred while trying to report this transaction to the merchant. An e-mail has been sent to the merchant informing them of the error. The following is the result of the attempt to charge your credit card.

      This transaction has been approved.

It is advisable for you to contact the merchant to verify that you will receive the product or service."

 

The message I receive via email is 

 

"Authorize.Net Merchant,

Your script timed out while we were trying to post transaction results to it."

 

The timeout happens very quickly. 

 

My x_relay_url is https://domain.com/wc-api/WC_Gateway_Authorize_DPM/. Could the issue be that Authorize.net is unable to post to https://, and therefore I should somehow force http:// on the x_relay_url? Then why would it work with TLS 1 enabled, and not when disabled? 

 

This is a very frustrating issue since the only solutions I have seen online (and on this board) was for the merchant to find another payment gateway altogether. Thanks in advance for any insight. 

choffm12
Member
Who Me Too'd this topic