cancel
Showing results for 
Search instead for 
Did you mean: 

DPM fails to post back to x_relay_url after TLS v 1.0 is disabled

The transactions and posting back to our server has been working.

We disabled TLS 1.0 on the server and only allow TLS 1.1 or TLS 1.2

 

This broke the post back and get the following

"An error occurred while trying to report this transaction to the merchant" on https://secure.authorize.net/gateway/transact.dll

 

The transaction is taken/recorded by Authorize.net. It just fails to post back/load the x_relay_url

 

The x_relay_url, page it should post back to, is on port 443(https)

It is a .net webforms page that has a javascript redirect on it.

 

Any ideas why this change would break the post back?

 

Environment:

Windows Server 2008, IIS 7.5

 

 

vincet
Contributor
22 REPLIES 22

@Lilith

Sent the ciphers to Richard at developer@authorize.net.

 

Was there ever an update or resolution for this?

 

Thanks

No we have not.

 

We decided to pursue a different payment solution outside of Authorize.net.

vincet
Contributor