Authorize.Net Shopping Cart Integrations: Shopify, WooCommerce and More

Shopify rebuilt how outside payment providers plug into its checkout. Authorize.Net's answer is a new payments app, listed in the Shopify App Store under the developer name Visa Acceptance Solutions (Visa owns Authorize.Net). The listing, checked September 27, 2026, shows it launched January 12, 2024, and is free to install.

Authorize.Net's Shopify update page told merchants to install the new app and turn off the old one, and says Shopify extended the migration deadline to August 31, 2025. That date has passed, so any Shopify store taking cards through Authorize.Net today should be on the new app.

What the new app does and doesn't do

If you sell subscriptions on Shopify, plan around a subscription app rather than Authorize.Net's own recurring tools. The app listing also carries a note that merchants already using Shopify Subscriptions should "stay with legacy app for now." Check with the app's support team and your subscription app before you change anything. Our Authorize.Net recurring billing guide explains what ARB and CIM do on other carts.

Shopify's third-party transaction fee

Shopify charges its own fee on each sale when you use a payment provider other than Shopify Payments. Shopify's U.S. pricing page, checked September 27, 2026, lists:

• Basic: 2%
• Grow: 1%
• Advanced: 0.6%
• Plus: 0.2%

That fee is Shopify's, on top of your processing costs and your gateway fee. On a Basic plan it can wipe out the savings from a lower-cost merchant account, so run the numbers at your monthly sales. Our Authorize.Net pricing guide covers the gateway side of the bill.

Setup tips from Shopify and Authorize.Net

• Test mode. Shopify's help page says Authorize.Net's test servers "aren't compatible with Shopify," so turn off Test Mode in your Authorize.Net account before you activate the app. To test first, Shopify says to use a separate Authorize.Net sandbox account with the app's "Use test mode" box. Authorize.Net warns that test-mode orders never reach your processor, so they're never paid out.
• Refund errors. Shopify says a refund can fail with a message like "Bill To Last Name is required" when fields on your Authorize.Net hosted payment form are set to required. Set them to not required.
• Your account. The app asks for your API Login ID and Transaction Key. Whether it works with your particular merchant account and processor is a question for your provider. Ask before you migrate.

WooCommerce is free WordPress software, so there's no platform transaction fee. You add Authorize.Net with a plugin. The one sold on the WooCommerce Marketplace is "Authorize.net, a Visa solution for WooCommerce," built by SkyVerge and listed under "Official payments." As of September 27, 2026, the page shows:

• Price: $79 for a 1-year plan.
• Countries: Australia, Canada, New Zealand and the United States.
• Saved payment methods: customers can store cards and eChecks, held on Authorize.Net's servers. The page says you need the CIM service turned on for all features.
• Subscriptions and pre-orders: "Full Support" for the WooCommerce Subscriptions and Pre-Orders extensions, paid by card or eCheck.
• eCheck: for customers with U.S. bank accounts. You need an active Authorize.Net eCheck account.
• Refunds, voids and captures from the WooCommerce order screen.
• Accept.js: card data goes straight to Authorize.Net, not through your server. The page puts this at the PCI SAQ A-EP level.

Wallets are less simple. In a reply on the same page, SkyVerge says Apple Pay needs developer setup and counts as a customization outside its standard support.

Other Authorize.Net plugins for WooCommerce are sold on WordPress.org and vendor sites. Some are free. They vary a lot in what they support, so run any of them through the feature checklist below. Whichever you use, you're responsible for keeping WordPress, WooCommerce and the plugin updated.

Adding eCheck? Read our guide to Authorize.Net eCheck processing for fees and the U.S.-only rule.

BigCommerce Authorize.Net. Authorize.Net is one of BigCommerce's built-in gateways. BigCommerce's developer documentation, checked September 27, 2026, lists Authorize.net as compatible with its Payments API for both stored payment instruments (saved cards) and raw card data. The same docs say refunds can be issued from the store control panel.

Magento Authorize.Net. Adobe's release notes for Magento Open Source 2.4.0 say: "the Authorize.Net payment method integration has been removed from core code. Merchants should migrate to the official extension that is available on the Commerce Marketplace." If your store runs Magento 2.4 or Adobe Commerce, Authorize.Net comes from an extension. A search of the Adobe Commerce Marketplace on September 27, 2026, returned more than a dozen. Check who maintains the one you pick and whether it supports your Magento version.

Here's how the main platforms compare:

Other platforms may connect too. Check the platform's own help center for the current connection, not a list that could be years old. Selling from Canada? Our Authorize.Net in Canada guide covers currencies and carts for Canadian stores.

Many older carts, including older osCommerce and Zen Cart installs and custom-built checkouts, connect through Authorize.Net's original methods: SIM, AIM and DPM. Authorize.Net has deprecated all three. It says SIM and DPM are "supported but no longer actively maintained," which means bug fixes but no new features. It hasn't announced a shutdown date.

If your checkout still works, you don't have to panic. But these connectors are where things tend to break, such as the old MD5 hash that Authorize.Net stopped sending in 2019. Signs your cart uses one:

• The plugin settings mention SIM, AIM, DPM, "Direct Post" or an MD5 hash.
• The plugin hasn't been updated in years.
• Your developer mentions transact.dll or "relay response."

The fix is usually a current plugin, or a rebuild on Accept Hosted, Accept.js or the Authorize.Net API. Our guide to moving off SIM, AIM and DPM explains what replaces each one.

"Works with Authorize.Net" can mean anything from a full-featured plugin to a basic card form. Ask these questions before you buy or build:

1. Saved cards. Does it store cards as Authorize.Net CIM tokens (so they stay at Authorize.Net), or in the cart's own vault? It matters if you ever change carts. See how Authorize.Net saved cards work.
2. Recurring billing. Does it use Authorize.Net's ARB, the cart's own subscription tool or a separate app? Know which system charges your customers and which one sends failed-payment notices.
3. eCheck. Can customers pay from a U.S. bank account at checkout? You'll also need eCheck added to your Authorize.Net account.
4. Apple Pay and Google Pay. The plugin has to support them, and so does the processor behind your merchant account. Authorize.Net lists which processors support each wallet. See Authorize.Net digital wallet setup.
5. Refunds and voids from the cart. Can staff refund from the order screen, or do they log in to Authorize.Net each time?
6. Held transactions. Authorize.Net's Fraud Detection Suite can hold a payment for review. Find out how the cart shows a held order, so no one ships it before you approve it. See Authorize.Net fraud filters.
7. How card data is collected. Authorize.Net rates its hosted payment form (Accept Hosted) at PCI SAQ A, the shortest self-assessment. Accept.js with your own form is SAQ A-EP. A plugin that sends card numbers through your server puts more of your site in scope. See PCI compliance basics.
8. Upkeep. When was it last updated, and does it support your cart's current version?

A gateway plugin doesn't decide what you're allowed to sell. Two other parties do. The acquiring bank behind your merchant account approves your business. Your cart platform has its own rules for what stores it will host. Being approved for one doesn't cover the other, so read your platform's terms before you build.

If you sell something banks treat as higher risk, get the merchant account approved for your actual products first, then connect the gateway. Our guide to choosing a high risk payment gateway covers how Shopify, WooCommerce and BigCommerce fit, and which fraud and checkout features matter most.

Whatever you sell, your site needs the basics underwriters check: clear prices, a refund policy and contact details. See website requirements for accepting credit cards.

START sets up the merchant account and the Authorize.Net gateway together. We've worked with Authorize.Net for more than 20 years and set up over 60,000 Authorize.Net accounts. For the rest of the gateway's features, see our Authorize.Net payment gateway overview.