We have a Magento Community e-commerce website built in 2012, hosted on Simple Helix with Sucuri security features, version 1.9.01 that we'd like updated to the latest version of Magento (1.9.2), it also has elements/plugins supported by Wordpress, which we'd also like updated to the latest version (4.5).
There are some security patches that need to be run and our credit card processing company has some requirement changes that may need to be completed. We're also receiving an error currently when payment is submitted (that may relate to the upcoming Authorize.net requirement changes). This is first priority, as we're having issues with credit card processing on the site right now.
The site needs to be upgraded and developed away from our current production environment, so there is minimal disruption to our business. When the upgrade and development is complete we can complete a review and sign off. We need to then move it to production with minimal downtime.
We need the work done now, so really hope to find a partner that has the flexibility of doing the project now.
Required work with Authorize.net payments:
1) Currently experiencing issues with payment processing. When a customer attempts to order, he/she receives the following error - "Could not open the page, too many redirects".
Need to ensure set-up is set-up properly for upcoming mandatory changes by Authorize.net:
1) Using Akamai SureRoute will be mandatory starting in June (need to ensure this works asap)
2) RC4 cipher suite in the sandbox will be disabled April 29, 2016, and in the production environment on May 31, 2016.
3) In the coming weeks, due to system updates, it will be possible to receive Authorize.Net IDs (Transaction ID, Batch ID, etc.) that are not in sequential order.
For example, 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 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.
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.
If you have a solution that relies on RC4 to communicate with our servers, please update it to a current, high-security cipher as soon as possible. Please review our API best practices blog post for more information.
** IMPORTANT: One may not upload any files exceeding our hosting company's requirements (100GB) or they will be charged for it, this will be reduced from payment. With the bandwidth usage there would be an overage fee which is equal to $0.15/GB used over our limit.