Hello
I need an answer for the following questions:
1) After the update on September 21st, any website or payment solution that connects via api.authorize.net that cannot validate SHA-2 signed certificates will fail to connect to Authorize.Net's servers, I do have this question: I’m using DPM (Direct Payment Method), do I have to worry about this or do I have to update something? As far as I remember I never worked with certificates during all my coding with DPM.
2) Are all these changes going to affect the Relay Response Basics or the part of my coding that get the response back from authorize.net?
3) In reference to TLS Remediation for PCI DSS Compliance, if I read well from one of the Authorize.net post, this is something that my provider has to take care of on the server; therefore this is out of my control. Am I correct on this one? Should I contact my provider for questions on this issue?
4) For the Akamai implementation issues it is my understanding that I should change my present URLs for transaction processing that at the present time looks like this: https://secure.authorize.net/gateway/transact.dll to any of the new Akamai transaction URLs that are available now. These three are:
https://api2.authorize.net/xml/v1/request.api
https://api2.authorize.net/soap/v1/Service.asmx
https://secure2.authorize.net/gateway/transact.dll
Thanks for your time and help
09-11-2015 08:47 AM
Hi AuthComm25,
1) Since you are using DPM you should be fine because you do not even connect directly to Authorize.Net. Instead, you direct your customers to our site and the SSL connection is managed by their individual web browsers. Any reasonably up-to-date web browser will easily support the changes that we have announced. With the error 99 you are getting this is not related to the SHA2 update this just indicates that your transaction key is invalid.
2) Relay Response is not affected with these updates.
3) Yes you are correct.
4) Specifically secure2.auth.net, since that's for the API used with DPM.
Thank you,
Joy
09-11-2015 03:59 PM
I have changed the URL from "https://apitest.authorize.net/xml/v1/request.api" to https://api2.authorize.net/xml/v1/request.api for upgrade to ssh2. I have regenared the transaction key . But i am getting the follwoing error "User authentication failed due to invalid authentication values.". Please help on this
@AuthComm25 wrote:Hello
I need an answer for the following questions:
1) After the update on September 21st, any website or payment solution that connects via api.authorize.net that cannot validate SHA-2 signed certificates will fail to connect to Authorize.Net's servers, I do have this question: I’m using DPM (Direct Payment Method), do I have to worry about this or do I have to update something? As far as I remember I never worked with certificates during all my coding with DPM.
2) Are all these changes going to affect the Relay Response Basics or the part of my coding that get the response back from authorize.net?
3) In reference to TLS Remediation for PCI DSS Compliance, if I read well from one of the Authorize.net post, this is something that my provider has to take care of on the server; therefore this is out of my control. Am I correct on this one? Should I contact my provider for questions on this issue?
4) For the Akamai implementation issues it is my understanding that I should change my present URLs for transaction processing that at the present time looks like this: https://secure.authorize.net/gateway/transact.dll to any of the new Akamai transaction URLs that are available now. These three are:
https://api2.authorize.net/xml/v1/request.api
https://api2.authorize.net/soap/v1/Service.asmx
https://secure2.authorize.net/gateway/transact.dll
Thanks for your time and help
09-14-2015 04:34 AM
https://api2.authorize.net/xml/v1/request.api are for production account.
test/sandbox account don't use those.
09-14-2015 05:12 AM
Thanks for help. What is the url for test/sandbox
09-14-2015 05:43 AM
You already using it, that one didn't change.
09-14-2015 05:52 AM
Is api change is enough for production? or Do we need to change any other settings
09-14-2015 06:01 AM