The Authorize.Net integrations for WooCommerce were among some of the earliest plugins we built at SkyVerge. At that time, Authorize.Net had several different APIs that allowed you to do different things: the AIM API handled directly processing payments, the CIM API handled securely tokenizing saved methods, the DPM API handled embedded payment forms, and the SIM API handled off-site transactions.
As a result of all of this separation, there were 4 different extensions to do different types of payment processing for your WooCommerce store. While this ensured that a merchant could use the exact feature set they needed, it also meant it was confusing to know which plugin to choose, and as developers, we had a lot of duplicate code to maintain (the basic plugin structure and transaction handling was pretty consistent).
The Authorize.Net team has made amazing progress over the past couple of years to unify their APIs and improve their payment processing offering as a whole. Today, there’s just “Authorize.Net API” for payment processing, so we’re streamlining our integration, too! We’re happy to say that, going forward, we’ll be working on a single unified WooCommerce Authorize.Net gateway. ????
This plugin takes all of the best parts of the AIM, CIM, and SIM integrations our team had built, rolling them up into one plugin. Over the next couple of months, we’ll be migrating all WooCommerce sites to this new unified extension.
How to upgrade
Existing CIM plugin users have just seen this as a version 3.0 upgrade, so you’re probably using the unified plugin already!
For AIM and SIM users, we’ll need a couple additional steps. First, over the next month, we’re working with the WooCommerce.com team to add subscriptions for the unified plugin to your account (to match, then replace, your current plugin subscription).
When this process is completed and every WooCommerce Authorize.Net merchant has a subscription for the unified plugin, we’ll begin to roll out updates for AIM and SIM users. This update will offer a one-click migration: when you upgrade, you’ll be asked to migrate, and when you’re ready, the new plugin will be installed, activated, and connected to WooCommerce.com. It will migrate all settings and transaction information seamlessly, so with a single click, you’ll be ready to move forward with the latest and greatest from Authorize.Net!
Payment form improvements
If you’ve already been using the CIM extension and upgraded to Authorize.Net version 3.0, the great news is you may already see these features. Check out what you can now do as of version 3.0 below.
In older versions of our plugin, you could enable Accept.js from Authorize.Net to improve the security of your payment forms (meeting SAQ A-EP levels of PCI compliance). There was a setting for this because it required extra configuration in your Authorize.Net account.
No more! Authorize.Net has made this configuration available via their API, so Accept.js can come standard for all stores. When you connect to Authorize.Net, the plugin automatically configures Accept.JS, so the inline payment form security is improved transparently. As a result, you’ll see we’ve removed these Accept.js settings in the plugin.
Speaking of improvements, you’ll also see a new type of payment form for credit cards! When you upgrade, you might be interested in checking out the new lightbox payment form from Authorize.Net. This form meets the highest standards of PCI compliance (SAQ A), so you can maximize security by switching to the lightbox credit card form rather than the inline form. Here’s a snapshot of what it looks like at checkout:
Using eChecks as well? We’ve also added a new eCheck form with increased security. You can now enable a hosted eCheck form that meets SAQ A levels of compliance, or continue with the inline form, which now meets SAQ A-EP compliance, too. ????
If you switch to the hosted eCheck form, your customers will not be presented with payment fields at checkout.
Instead, these are securely embedded in the payment page following checkout for your customers to complete payment.
Don’t want to change your payment experience? That’s okay, too! The inline payment forms that have always been present will still be available, and you can leave your settings untouched to continue to use them.
For the future
Our first priority now is to migrate all existing Authorize.Net merchants on WooCommerce to use the unified plugin. Once everyone is using a single codebase, we can upgrade the Authorize.Net experience faster without duplicating work! We’re already at work with Authorize.Net to plan the next evolution of this integration. ????