Authorize.net Changes
From NewHaven Software Wiki
Russ horton (Talk | contribs) (→Changes Announced August 2105) |
Russ horton (Talk | contribs) |
||
| (One intermediate revision not shown) | |||
| Line 1: | Line 1: | ||
| - | ==[http://now.eloqua.com/es.asp?s=986383348&e=912954&elq=faa2b137cdd94d58bbfa65b41153fb6f Changes Announced August | + | ==[http://now.eloqua.com/es.asp?s=986383348&e=912954&elq=faa2b137cdd94d58bbfa65b41153fb6f Changes Announced August 2015]== |
Authorize.net announced they have started to phase in new processing URL's with Akamai. This is being done to improve the reliability/up-time of their processing network. To be clear, these URL's are the addresses CMS uses to communicate with Authorize.net's payment gateway servers. | Authorize.net announced they have started to phase in new processing URL's with Akamai. This is being done to improve the reliability/up-time of their processing network. To be clear, these URL's are the addresses CMS uses to communicate with Authorize.net's payment gateway servers. | ||
| - | Authorize.net is currently running their | + | Authorize.net is currently running their legacy URL's in parallel with their new ones but, in June of 2016, they will be redirecting their current URL's to the new ones. In other words there will be no interruption in service and the URL's used by CMS in v9 and earlier will continue to work even after June 2016. |
That said, there are benefits to using their new URL's now so we've decided to be proactive and implement them immediately in [http://updates.newhavensoftware.com/v10release_notes.htm CMS TEN] (as of 10.0.0.157). CMS 9.x and earlier will continue to use the current URL's. | That said, there are benefits to using their new URL's now so we've decided to be proactive and implement them immediately in [http://updates.newhavensoftware.com/v10release_notes.htm CMS TEN] (as of 10.0.0.157). CMS 9.x and earlier will continue to use the current URL's. | ||
| Line 14: | Line 14: | ||
*TLS remediation | *TLS remediation | ||
*Akamai (discussed above) | *Akamai (discussed above) | ||
| + | *RC4 Cipher | ||
| - | Click this link to see the full [http://app.payment.authorize.net/e/es.aspx?s=986383348&e= | + | Click this link to see the full [http://app.payment.authorize.net/e/es.aspx?s=986383348&e=1086337 communication from Authorize.net] regarding these changes. |
===CV3 Response=== | ===CV3 Response=== | ||
Current revision as of 22:31, 13 April 2016
Changes Announced August 2015
Authorize.net announced they have started to phase in new processing URL's with Akamai. This is being done to improve the reliability/up-time of their processing network. To be clear, these URL's are the addresses CMS uses to communicate with Authorize.net's payment gateway servers.
Authorize.net is currently running their legacy URL's in parallel with their new ones but, in June of 2016, they will be redirecting their current URL's to the new ones. In other words there will be no interruption in service and the URL's used by CMS in v9 and earlier will continue to work even after June 2016.
That said, there are benefits to using their new URL's now so we've decided to be proactive and implement them immediately in CMS TEN (as of 10.0.0.157). CMS 9.x and earlier will continue to use the current URL's.
You can read more about Authorize.net's phased implementation by clicking their announcement link above and their FAQ page.
Authorize.net announced other changes in August 2015 as well but no changes need to be made to CMS to address them. Those changes have either already been made or do not apply to CMS's integration with Authorize.net including:
- Security Certificate Upgrades
- Transaction ID Changes
- TLS remediation
- Akamai (discussed above)
- RC4 Cipher
Click this link to see the full communication from Authorize.net regarding these changes.
CV3 Response
We contacted CommerceV3 to get a statement from them on where they are at regarding the Authorize.net changes. Their response was:
"At this time there is no action required on your part. We are aware of the planned changes and our development team is investigating to determine whether there will be any impact to CV3’s integration with Authorize.net. If any action is needed on your end, we will certainly let you know."'
