Authorize.net Plugin for EBooking / Membership Pro

Will you be updating the Event Booking, & Membership Pro payment plugins for Authorize.net according to these changes announced by Authorize.net? See below from an email from Authorize.net:

---

Akamai Network Technology
Over the coming months, Authorize.Net will be upgrading access to the Internet connections that serve our data centers. Instead of allowing direct connections, all Internet traffic will be routed through Akamai, a third-party cloud network service that routes and delivers Internet traffic.
Using Akamai network technology will help decrease latency and improve the reliability of our payment gateway. It will also help safeguard against interruptions caused by issues beyond Authorize.Net's direct control, such as Internet congestion, fiber cable cuts and other similar issues. Additionally, come October, merchants connected to Akamai should no longer be affected by planned downtimes.
Implementation Plan And Timeline
We are implementing Akamai's technology into our network in two phases.
• Phase One (Now through June 2016) — We have created three new URLs for transaction processing that are hosted by Akamai. You can update your website or payment solution to point to the new transaction URLs today, which will provide you with the immediate benefits detailed above. Come October, you should no longer be affected by planned downtimes.
• Phase Two (June 2016) — We will automatically direct all of our existing transaction processing URLs to connect through Akamai in June of 2016. After this change, all transaction URLs will connect to Authorize.Net through Akamai.
IMPORTANT: To take advantage of the uptime benefits Akamai offers, we recommend you proactively update your website or payment solution during Phase One rather than waiting to be automatically updated during Phase Two.
Updating Your Solution
The new Akamai transaction URLs that are available now are:
• api2.authorize.net/xml/v1/request.api
• api2.authorize.net/soap/v1/Service.asmx
• secure2.authorize.net/gateway/transact.dll
Please contact your web developer or solution provider for assistance in updating to one of these new Akamai URLs.

---

What do we need to do? Will you be providing an updated plugin?

Thanks in advance.
-Chris

I also received this notice. Please advise what we need to do on our end. Thank you!

I received this notice from Authorize.net today regarding Security Certificate upgrades. I was wondering if users of Event Booking 1.7.4 and Membership Pro 1.6.6 are affected by this. Please see snippet from email below:

Security Certificate Upgrades to api.authorize.net
As part of our continuous upgrades to enhance system performance and security, on September 21, 2015, we are upgrading api.authorize.net to new security certificates, which are signed using Security Hash Algorithm 2 (SHA-2) and 2048-bit signatures.
These upgrades were already completed on secure.authorize.net in May. If your website or payment solution connects to api.authorize.net and any updates are necessary to use the new certificates, please refer to this blog post in our Developer Community, which has all of the certificate information you and your developer will need for this update. Our sandbox environment has already been updated so that you can validate that your solution will continue to work using SHA-2 signed certificates, prior to September 21st.
After the update is complete 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.

---

Please let us know what needs to be done to adhere to these changes.
Thanks!
-Chris

Hi Chris

From what I see, there is no need to change in our extensions. The changes if needed however, belong to the hosting provider you are using

So please contact your hosting provider and send them this information too (I don't have experience with server settings, so I am not sure the changes from hosting provider needed, please just contact them just in case any changes is needed from their side)

Tuan

Tuan,

Thanks for your reply. I have another question regarding the notice. There was this attached to it as well regarding transaction id numbers. Does this effect Ebooking or Membership Pro in anyway?
---
Transaction ID Changes
In October of this year, due to system updates, it will be possible to receive Authorize.Net IDs (Transaction ID, Batch ID, etc.) that are not in sequential order.
Currently, if you receive a Transaction ID of "1000," you could expect that the next Transaction ID would not be less than 1000. However, after the updates, it will be possible to receive a Transaction ID less than the one you previously received.
If your system has any functionality that expects Authorize.Net-generated IDs to be sequential, please update it immediately so that you will not see any disruptions to your solution.
Additionally, please make sure that your solution does not restrict any Authorize.Net ID field to 10 characters. If you are required to define a character limit when storing any of our IDs, the limit should be no less than 20 characters.
---

Please let me know. Thanks!
- Chris

This change won't affect the extensions, too.

Tuan

Tuan,

Thanks for checking.

- Chris

Tuan,

I received a reminder about this notification regarding Authorize.net changing their platform to Akamai. I just wanted to double check with you that this wont effect Event Booking or Membership Pro using the Authorize.net payment. I have older versions running Event Booking .1.7.1, and 1.7.4 and Membership Pro 1.6.6. In the email below they reference AIM/SIM.
----

Dear Authorize.Net Merchant:

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: api2.authorize.net/xml/v1/request.api
• Authorize.Net API, SOAP format: api2.authorize.net/soap/v1/Service.asmx
• AIM/SIM merchants, name/value pair format: 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.


---

Please clarify. Thanks! - Chris

Hi Chris

From what I see, if you don't make the change, everything will still working as how it is at the moment. However, you won't be able to use advanced feature of Akamai technology (I don't know the details behind it)

I updated Events Booking to use this feature. For Membership Pro and other extensions, we are going to work on the update during this month

All our extensions should be ready with this change before the end of this month

Tuan

Tuan,

Okay I need to be sure. Your saying the extensions I'm currently leveraging will still continue to work after the change date mentioned below of June 30th this year? Please clarify.

Reading the email from Authorize.NET It sounds like the change is mandatory. I need to know for sure so I don't have any interruption in transactions and can take the appropriate measures to be sure everything works going forward. Can you please clarify this. Thanks.

- Chris