What is the correct sandbox URL?

[maverickbluer1]

I would like to test my TLS1.2 upgrade using the Sandbox which I understand is already using 1.2.

I'm confused about the URL.  Customer support via chat gave me:

https://sandbox.authorize.net/gateway/transact.dll

That URL returns a 404.

https://test.authorize.net/gateway/transact.dll  works fine but I'm not sure it's using TLS1.2.

Could you clear up my confusion?

[RichardH]

Hello @maverickbluer1

https://test.authorize.net/gateway/transact.dll is the correct sandbox endpoint, and it only accepts a TLS 1.2 connection.

Richard

[NexusSoftware]

That link text is https://test.authorize.net/gateway/transact.dll, correct URL, but the href is https://sandbox.authorize.net/gateway/transact.dll 

[omaclay]

According to the API doc, the endpoints are https://apitest.authorize.net/xml/v1/request.api and https://api.authorize.net/xml/v1/request.api for production.

I still have a page using SIM which uses 

https://test.authorize.net/gateway/transact.dll and 

https://secure.authorize.net/gateway/transact.dll for production.

In test, I have often gotten a 'connection refused'. After a few retries, I'll get a response.

I'm using php fsockopen to make connections.

My questions are:

1. endpoints: is there any agreement on endpoints?

2. connection refused: is this because of the wrong tls version? server busy temporarily?

3. is there currently any test gateway which uses only TLS 1.2?

4. is there any way to find out which tls version the authorize net server is seeing?

I confess i missed the test yesterday. my bad.

thanks for any help you can offer.

Otis Maclay

[NexusSoftware]

The endpoints https://apitest.authorize.net/xml/v1/request.api and https://api.authorize.net/xml/v1/request.api for production are the correct and preferred URLs.

The others are old and deprecated. 

All Sandbox endpoints only accept TLS 1.2 connections and have for some time. 

[omaclay]

then the mystery for me is why I get 'connection refused'.

is there any explanation for that?

thanks,

O.

[NexusSoftware]

Check your sever's TLS configuration with the information at : 

https://community.developer.authorize.net/t5/Integration-and-Testing/TLS-1-2-Migration/m-p/61582/hig...

[omaclay]

thanks. shows curl using 1.0

is there any way to access with fsockopen?

i'm sending

GET /a/check HTTP 1.1

Host: www.howsmyssl.com

Accept: text/plain

Accept-Language: en-us

Connection: close

it connects but returns a 400 : Bad Request.

I hope I didn't make it angry....

[NexusSoftware]

Try 

$fp = fopen('https://howsmyssl.com/a/check', 'r');
if ($fp) {
    fpassthru($fp);
}