Page 1 of 1

authorize.net change on June 30, 2016

Posted: Fri Jun 03, 2016 2:36 am
by silkcamel
Dear folks,

Opencart version 2.2.0.0

I added credit cart gateway for Authorize.net (AIM). And I just got email from authorize.net said they are using Akamai now and need me to contact web developer (see below email).

what should I upgrade for opencart? Thank you very much!


*************************************************************************************************************************
Thank you for using Authorize.Net for your transaction processing.

Authorize.Net is now using Akamai to optimize our Internet traffic routing, which includes your transaction requests. Akamai helps safeguard against interruptions caused by issues beyond Authorize.Net’s direct control, such as Internet congestion, fiber cable cuts and other similar issues.

Using Akamai is currently optional, but will be mandatory for all merchants on June 30th. Upgrade your website or payment solution today to take immediate advantage of Akamai’s benefits.

The new Akamai transaction URLs that are available now are:


• Authorize.Net API, XML/JSON format: https://api2.authorize.net/xml/v1/request.api
• Authorize.Net API, SOAP format: https://api2.authorize.net/soap/v1/Service.asmx
• AIM/SIM merchants, name/value pair format: https://secure2.authorize.net/gateway/transact.dll

If you have not already, please review the announcement and the Akamai FAQs to determine what action you should take for your particular solution. If your solution uses a firewall, please pay particular attention to this section of the FAQs to avoid disruptions to your transaction processing.

Re: authorize.net change on June 20, 2016

Posted: Fri Jun 03, 2016 5:37 am
by straightlight
Take note that their JSON API is still BETA and not recommended for production.

Re: authorize.net change on June 20, 2016

Posted: Fri Jun 03, 2016 6:16 am
by silkcamel
Straightlight,

but they said it will be mandatory for all merchants on June 30th....

I don't know what change opencart need make to avoid any problem based on below information.

any problem if we do nothing? Thanks.

Bill

Re: authorize.net change on June 20, 2016

Posted: Fri Jun 03, 2016 11:08 pm
by straightlight
Based on the posted page above, the XML version seem to be the most stable one OR the transact.dll version (pretty old though).
any problem if we do nothing? Thanks.
Only by the reported problems, answers will be delivered and provided on that end.

Re: authorize.net change on June 20, 2016

Posted: Sat Jun 04, 2016 12:58 am
by kirkhall
silkcamel wrote:Straightlight,

but they said it will be mandatory for all merchants on June 30th....

I don't know what change opencart need make to avoid any problem based on below information.

any problem if we do nothing? Thanks.

Bill
Authorize.net has been sending out this message for what seems to me like a year.

I don' t know if you are asking for help with this or not but I changed the url in catalog/controller/payment/authorize.net_aim.php to https://secure2.authorize.net/gateway/transact.dll along time ago and it works fine.

Re: authorize.net change on June 30, 2016

Posted: Sat Jun 04, 2016 6:38 am
by silkcamel
Straightlight,
Thanks. I'm not quite understand your answer. do you mean only reported problem will be directed to that dll link?

Kirkhall,

Yes, I do ask for help. if it is just one or two code changes in one document, please help me point it out.

Of course, if it will take more than 15 min for developer working on this. I'll be more than happy to have your experts help me with pay. Please send private message to me for your hourly charge and let me know how long it takes.

when you say you changed the url, did you mean you replace the original "https://secure.authorize.net/gateway/transactdll" to "https://secure2.authorize.net/gateway/transact.dll" on file catalog/controller/payment/authorize.net_aim.php?

is that the only code we need change for this problem? any other code changes for below two items? and which file?:

• Authorize.Net API, XML/JSON format: https://api2.authorize.net/xml/v1/request.api
• Authorize.Net API, SOAP format: https://api2.authorize.net/soap/v1/Service.asmx

I'm not technical person, just don't want to get any problem after June 30, 2016. if authorize.net send this message one year ago, probably I can ignore it. but I just register with them last week, and they stated that I need web developer to get this done.

Thank you very much.

Re: authorize.net change on June 30, 2016

Posted: Sat Jun 04, 2016 8:37 am
by kirkhall
silkcamel wrote:Straightlight,
[..]

when you say you changed the url, did you mean you replace the original "https://secure.authorize.net/gateway/transactdll" to "https://secure2.authorize.net/gateway/transact.dll" on file catalog/controller/payment/authorize.net_aim.php?
That is exactly what I mean if you are indeed using Authorize.Net (AIM). Change that one url making sure you leave the quotes (') around it and you should be good to go. If you can do that, save it and upload it to the correct location replacing the file that is there now you won't need an expert. Maybe run a test order through on a low cost test item just to be sure after you do so but that's all you need to do.
Alternately you can just comment out the one that is there now and add the new one like this.

Code: Select all

//	$url = 'https://secure.authorize.net/gateway/transact.dll';
	  $url = 'https://secure2.authorize.net/gateway/transact.dll';