Vendor pluginLast verified 2026-09-25 · Reviewed by a person 2026-09-25
Yes, two ways. Authorize.net publishes its own free plugin, Authorize.net Payments for WooCommerce, on WordPress.org: cards and eCheck, saved payment details through Authorize.net's Customer Information Manager, its fraud screening and WooCommerce Subscriptions. The older route is a paid WooCommerce Marketplace extension built by SkyVerge, which is further along on checkout options but does not do 3D Secure. Authorize.net's own plugin only arrived in February 2026, so much of what is written about this pairing predates it.1
Documentation review only; UAT-Ops has not run the Authorize.net + WooCommerce integration itself
Sources checked: 21 claims from 5 sites, listed at the foot of the page.
Connects through Free WordPress plugin from Authorize.net, connected with the account's API Login ID, Transaction Key and Client Key. The paid alternative, SkyVerge's Marketplace extension, tokenizes cards in the browser with Accept.js and stores them as CIM profiles. Biggest gotcha: There are two Authorize.net plugins, and the free one is Authorize.net's own.
How it connects
Method
Free WordPress plugin from Authorize.net, connected with the account's API Login ID, Transaction Key and Client Key. The paid alternative, SkyVerge's Marketplace extension, tokenizes cards in the browser with Accept.js and stores them as CIM profiles.1
Maintained by
Authorize.net, for its own free plugin; SkyVerge builds the paid Marketplace alternative1
WordPress 6.4 and PHP 8.0 for Authorize.net's plugin; SkyVerge's lists WooCommerce 3.9.4 (its docs say 3.5+)1
PCI scope
Depends on the checkout mode you choose; see the gotchas below.3
What works on this platform
Yes: a source confirms it on this integration. Limited: supported, but only under meaningful conditions or through a subset of connector paths. Not verified here: the gateway supports it, but no source confirms this integration exposes it. No: not available. A capability with no source either way is left off.
SkyVerge's extension does not support 3D Secure; Woo's docs point merchants who need PSD2/SCA to a CyberSource integration. Authorize.net's own plugin says nothing either way.
In SkyVerge's extension, only in the classic shortcode checkout, and Woo treats enabling it as a developer-level customization. Authorize.net's own plugin does not mention Apple Pay.
Authorize.net supports this; no source confirms it on this integration.
Capability status reflects the integration and documentation available at the time of verification, not necessarily every capability of the underlying gateway or platform.
Testing it
Open a separate Authorize.net sandbox account, which has its own login and API credentials. For Authorize.net's plugin, set it to the Sandbox environment and enter the sandbox API Login ID, Transaction Key and Client Key, then place orders with a valid billing address and the test cards from Authorize.net's testing guide. SkyVerge's extension also takes a Signature Key, which enables the webhooks that report deleted customer or payment profiles, so its dev store needs a public HTTPS URL. With either plugin, assert that the order status changes, a partial refund works after settlement, and a Subscriptions renewal charges the saved CIM profile.1
UAT-Ops runs integration flows like this against the real sandbox and keeps the evidence. Get one email when it opens.
Gotchas
There are two Authorize.net plugins, and the free one is Authorize.net's own
Authorize.net publishes its own plugin, Authorize.net Payments for WooCommerce, free on WordPress.org since February 2026. The long-standing option is a paid extension on the WooCommerce Marketplace, sold as "Authorize.net, a Visa solution for WooCommerce" and built by SkyVerge, which Authorize.net has promoted on its own blog. Guides, forum answers and comparison posts written before 2026 describe only SkyVerge's, so a merchant can easily pay for an extension without knowing a free first-party one exists. The free plugin is young: version 1.0.5, no public ratings yet. SkyVerge's has the longer record and documents its limits in detail, including no 3D Secure. Use one or the other, never both at once.
For SkyVerge's extension, the Marketplace listing gives WooCommerce 3.9.4 and PHP 7.2 as the minimums. The product documentation says WooCommerce 3.5+ and PHP 7.4+. The changelog backs the documentation on PHP: version 3.8.0 (December 2022) raised the requirement to PHP 7.4. Plan for PHP 7.4 or later and a current WooCommerce. Recent releases were tested up to WooCommerce 11.0.1, and several recent patches fixed PHP 8.x warnings.
SkyVerge's extension: no 3D Secure, and Apple Pay only on the classic checkout
SkyVerge's extension does not do 3D Secure, so it cannot meet PSD2/SCA. Woo's docs point stores that need SCA to CyberSource. Authorize.net supports Apple Pay on the web, but here it works only in the classic shortcode checkout and needs developer-level certification. Woo treats that as a customization outside standard support. A store that has switched to the Cart and Checkout blocks loses Apple Pay.
In SkyVerge's extension, if a partial refund is issued before the transaction settles (usually within about 24 hours), the plugin tries to void it instead, and Authorize.net rejects partial voids. Wait for settlement, or void the whole amount. Subscription renewals also depend on CIM being enabled, which can cost extra each month. Renewals most often fail because customer or payment profile IDs don't match, and sharing one set of API credentials across several sites causes exactly that.
Showing the eCheck option in WooCommerce is not enough. Authorize.net underwriting has to enable the WEB eCheck type and lift funding holds, and they usually ask for proof of SSL and a privacy policy. Until then, eCheck payments are declined even though the checkout shows the option.
SkyVerge used to ship separate AIM, CIM and SIM extensions. The AIM and Accept Hosted (SIM) extensions are now retired, and their docs are frozen. Stores still running them are on unmaintained code, and Accept Hosted's iframe put them at SAQ A. The current plugin's Accept.js form is SAQ A-EP, so moving to it changes the store's PCI paperwork.
Listed automatically from the capability table: every row marked Limited, External only or Not verified here. It points at what to confirm for your own case; it is not a recommendation.
Last verified 2026-09-25 · Reviewed by a person 2026-09-25
Integration capabilities, requirements, pricing, availability, and vendor policies may change over time. UAT-Ops documents information based on the authoritative sources and testing available at the time of review.
Where newer information, testing, or vendor documentation materially changes a published claim, UAT-Ops may revise the page to reflect the most current verified information. Readers should confirm time-sensitive requirements with the relevant vendor before making production or purchasing decisions.