Authorize.net Changes - Revision history

Russ horton at 22:31, 13 April 2016

2016-04-13T22:31:07Z

← Older revision		Revision as of 22:31, 13 April 2016
Line 16:		Line 16:
	*RC4 Cipher		*RC4 Cipher

	Click this link to see the full [http://app.payment.authorize.net/e/es.aspx?s=986383348&e=~~945849&elq=3e3c776c44ce4c138117e5911028087b~~ communication from Authorize.net] regarding these changes.		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===

Russ horton at 20:41, 17 March 2016

2016-03-17T20:41:42Z

← Older revision		Revision as of 20:41, 17 March 2016
Line 1:		Line 1:
	==[http://now.eloqua.com/es.asp?s=986383348&e=912954&elq=faa2b137cdd94d58bbfa65b41153fb6f Changes Announced August ~~2105~~]==		==[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 ~~current~~ 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.		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=945849&elq=3e3c776c44ce4c138117e5911028087b communication from Authorize.net] regarding these changes.		Click this link to see the full [http://app.payment.authorize.net/e/es.aspx?s=986383348&e=945849&elq=3e3c776c44ce4c138117e5911028087b communication from Authorize.net] regarding these changes.

Russ horton: /* Changes Announced August 2105 */

2015-09-02T23:35:34Z

Changes Announced August 2105

← Older revision		Revision as of 23:35, 2 September 2015
Line 8:		Line 8:
	You can read more about Authorize.net's phased implementation by clicking their announcement link above and their [http://www.authorize.net/support/akamaifaqs/ FAQ page].		You can read more about Authorize.net's phased implementation by clicking their announcement link above and their [http://www.authorize.net/support/akamaifaqs/ FAQ page].

	Authorize.net announced other changes ~~just this week~~ 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:		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		*Security Certificate Upgrades

Russ horton: /* CV3 Response */

2015-08-21T21:52:12Z

CV3 Response

← Older revision		Revision as of 21:52, 21 August 2015
Line 19:		Line 19:
	===CV3 Response===		===CV3 Response===
	We contacted CommerceV3 to get a statement from them on where they are at regarding the Authorize.net changes. Their response was:		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."'
			''"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."'

Russ horton: /* CV3 Response */

2015-08-21T21:50:31Z

CV3 Response

← Older revision		Revision as of 21:50, 21 August 2015
Line 19:		Line 19:
	===CV3 Response===		===CV3 Response===
	We contacted CommerceV3 to get a statement from them on where they are at regarding the Authorize.net changes. Their response was:		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.''		''"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."'

Russ horton: /* CV3 Response */

2015-08-21T21:49:26Z

CV3 Response

← Older revision		Revision as of 21:49, 21 August 2015
Line 19:		Line 19:
	===CV3 Response===		===CV3 Response===
	We contacted CommerceV3 to get a statement from them on where they are at regarding the Authorize.net changes. Their response was:		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.''		''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.''

Russ horton: /* Changes Announced August 2105 */

2015-08-21T21:49:13Z

Changes Announced August 2105

← Older revision		Revision as of 21:49, 21 August 2015
Line 16:		Line 16:

	Click this link to see the full [http://app.payment.authorize.net/e/es.aspx?s=986383348&e=945849&elq=3e3c776c44ce4c138117e5911028087b communication from Authorize.net] regarding these changes.		Click this link to see the full [http://app.payment.authorize.net/e/es.aspx?s=986383348&e=945849&elq=3e3c776c44ce4c138117e5911028087b 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.''

Russ horton: /* Changes Announced August 2105 */

2015-08-21T01:24:13Z

Changes Announced August 2105

← Older revision		Revision as of 01:24, 21 August 2015
Line 1:		Line 1:
	=[http://now.eloqua.com/es.asp?s=986383348&e=912954&elq=faa2b137cdd94d58bbfa65b41153fb6f Changes Announced August 2105]=		==[http://now.eloqua.com/es.asp?s=986383348&e=912954&elq=faa2b137cdd94d58bbfa65b41153fb6f Changes Announced August 2105]==
	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.

Russ horton: /* Changes Announced August 2105 */

2015-08-21T01:24:02Z

Changes Announced August 2105

← Older revision		Revision as of 01:24, 21 August 2015
Line 6:		Line 6:
	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.

	You can read more about Authorize.net's phased implementation by clicking their announcement link above and their FAQ page.		You can read more about Authorize.net's phased implementation by clicking their announcement link above and their [http://www.authorize.net/support/akamaifaqs/ FAQ page].

	Authorize.net announced other changes just this week 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:		Authorize.net announced other changes just this week 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:

Russ horton: /* Changes Announced August 2105 */

2015-08-21T01:17:40Z

Changes Announced August 2105

← Older revision		Revision as of 01:17, 21 August 2015
Line 4:		Line 4:
	Authorize.net is currently running their current 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.		Authorize.net is currently running their current 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.		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.

	You can read more about Authorize.net's phased implementation by clicking their announcement link above and their FAQ page.		You can read more about Authorize.net's phased implementation by clicking their announcement link above and their FAQ page.