topic Re: Will TLS 1.0 and TLS 1.1 be disabled for SIM and Accept Hosted methods too? in Integration and Testing

Will TLS 1.0 and TLS 1.1 be disabled for SIM and Accept Hosted methods too?

cjo30080 — Wed, 19 Jul 2017 20:35:42 GMT

If possible, I'd like a definitive answer to this question, because I'm getting different answers from different Authorize.Net customer service representatives.

The first representive I spoke with suggested that, since our application connects to Authorize.Net servers via TLS 1.0, we can switch from AIM to either SIM or AcceptHosted to get around the requirement to connect via TLS 1.2. On the other hand, today, the representative told me that we would not be able to connect to SIM or Accept Hosted via TLS 1.0.

To be clear, I understand that TLS 1.2 will soon be required for API connections utilizing the Advanced Integration Method (AIM), in which cardholder data is transmitted from the client server to the Authorize.Net server.

However, will TLS 1.0 connections also be disabled for connections to hosted payment pages via either the Server Integration Method (SIM) or Accept Hosted methods?

Please, I hoping for a definitive answer to this question from an Authorize.Net representative, so we can determine how to move forward.

Thanks in advance!

Re: Will TLS 1.0 and TLS 1.1 be disabled for SIM and Accept Hosted methods too?

NexusSoftware — Wed, 19 Jul 2017 20:31:15 GMT

Any API calls will require a TLS 1.2 connection.

Re: Will TLS 1.0 and TLS 1.1 be disabled for SIM and Accept Hosted methods too?

harsha950 — Mon, 24 Jul 2017 16:07:26 GMT

Since Accept Hosted method relates to payment page being hosted on the Authorize.net side, is there a way to get to the payment page using TLS 1.0?

Re: Will TLS 1.0 and TLS 1.1 be disabled for SIM and Accept Hosted methods too?

RichardH — Mon, 24 Jul 2017 19:14:20 GMT

Hello @harsha950

Accept Hosted will soon require a TLS 1.2 connection to initiate the hosted payment form, when updated in production, it will no longer allow a TLS 1.0 or 1.1 connection.

Richard