Third-party plugin
Yes. The WooCommerce Marketplace sells a paid extension, Authorize.net, a Visa solution for WooCommerce, which is developed by SkyVerge rather than by Woo or Authorize.net. It takes cards through Accept.js and also handles eChecks, saved cards and WooCommerce Subscriptions. It has supported the block checkout since version 3.10.0.1
Connects through Paid WordPress extension from the WooCommerce Marketplace; card fields tokenized in the browser with Authorize.net Accept.js, stored cards via the CIM API. Biggest gotcha: The requirement numbers disagree.
| Capability | On this integration | Notes |
|---|---|---|
| Cards | Yes1 | Credit and debit cards through Accept.js, so card data goes straight to Authorize.net. Payment action can be Charge or Authorization. |
| ACH bank payments | Yes1 | eChecks work, but only after Authorize.net underwriting enables the WEB eCheck type on the account. |
| Saved cards (vault) | Yes1 | Saved payment methods are stored as Authorize.net CIM customer profiles; CIM must be enabled on the account. |
| Subscriptions | Yes1 | Fully supports WooCommerce Subscriptions and Pre-Orders, with renewals charged against CIM profiles. |
| Partial refunds | Yes3 | Partial refunds work after the charge settles. Before settlement the plugin tries a void, and Authorize.net does not allow partial voids. |
| 3-D Secure | No3 | The plugin does not support 3D Secure; Woo's docs point merchants who need PSD2/SCA to a CyberSource integration. |
| Apple Pay | Limited3 | Works only in the classic shortcode checkout, not the Cart and Checkout blocks, and Woo treats enabling it as a developer-level customization outside standard support rather than a toggle. |
| Google Pay | Not verified here4 | |
| PayPal | Not verified here4 | |
| Level 2 / Level 3 data | Not verified here4 |
Capability status reflects the integration and documentation available at the time of verification, not necessarily every capability of the underlying gateway or platform.
Open a separate Authorize.net sandbox account (it has its own login and API credentials). Put the plugin in test mode and enter the sandbox API Login ID, Transaction Key and Signature Key under WooCommerce > Settings > Payments; live keys fail in test mode. The store needs SSL even for local testing. Use the sandbox test cards from Authorize.net's testing guide. The Signature Key enables the webhooks that tell the store when a customer or payment profile is deleted, so the dev store needs a public HTTPS URL for them to arrive. Assert that the order status changes, an Authorization-mode order can be captured, a partial refund works after settlement, and a Subscriptions renewal charges the saved CIM profile.3
UAT-Ops runs integration flows like this against the real sandbox and keeps the evidence. Get one email when it opens.
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.
Source: dzv365zjfbd8v.cloudfront.net2
The 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.
Source: woocommerce.com3
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.
Source: woocommerce.com3
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.
Source: woocommerce.com3
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.
Source: woocommerce.com7
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.