Authorize.net Network change

[debasishbose2k]

We got an information regarding the network change 

https://support.authorize.net/s/article/Authorize-Net-Network-Change-FAQ?utm_campaign=19Q4+AkamaiEOL...

We are using the endpoint 

• https://api.authorize.net/xml/v1/request.api (in prod)  and 

• https://apitest.authorize.net/xml/v1/request.api (in test/sandbox)

The instruction indicates that for Prod , we do not have to make any changes , but for the test call, we need to have the public cert from the website Entrust.net in our cacerts (using java to call the APIS) on or before October 15th 2019 (impacted as part of phase 2)  

Is that a correct observation ? Can somebody confirm that the impact is

a> only on the sandbox

b> and the impact is only to have the public cert in our trsutstore ? 

[debasishbose2k]

Can anybody please provide some insights on this one ? 

[zcosandbox2]

Hi,

I am also having this issue.I am also using the Akamai end point for the transaction (https://api2.authorize.net/xml/v1/request.api). Did you got any more information about this change.

I have mailed my concers to developer@authorize.net and  got a  reply.

Reply from Authorize.net.

"

You will need to ensure a modern browser is used.  You will need to install the Entrust L1 K certificate: https://support.authorize.net/s/article/How-do-I-obtain-Authorize-Nets-SSL-Certificate-for-my-host-s...

[ChipNCharge]

Where do we install the certificate?

[zcosandbox2]

I believe that it will be on our server. I am also confussed about this change.

Because my production site is using the akamai endpoint and my site is already having a an SSL.

I just mailed my concerns to ANET support. Fom ANET i got a reply to ensure the L1K ertificate installation.

Previously i  just planned to change the endpoint to non akamai.My php SDK having the following endpoints.

const CUSTOM = "http://wwww.myendpoint.com";
const SANDBOX = "https://apitest.authorize.net";
const PRODUCTION = "https://api2.authorize.net";