• WooCommerce
  • Block and classic checkout

Gateway Wizard with Authorize.net for WooCommerce

Accept credit and debit cards in WooCommerce with your Authorize.net merchant account.

  • Full card numbers go straight to Authorize.net and never touch your server.
  • Saved cards, Subscriptions and Pre-Orders with Pro.
  • Bank payments (eCheck) when Authorize.net turns them on for your account.

Get Pro

PRO
How many sites?
Buy Pro · $79 a year

Renews yearly. Cancel any time. Priority email support included.

Not ready? Try the free version

Take credit and debit card payments in WooCommerce with your Authorize.net account.

Full card numbers are sent from the customer’s browser straight to Authorize.net with Accept.js and come back as a one-time token, so they never reach your server. That keeps you out of SAQ D, the long questionnaire that comes with forms that post card numbers to your site.

It uses the current Authorize.net API, and works with both the block checkout and the classic shortcode checkout.

Free and Pro

FeatureFreePro
Block and classic checkout
Works with the WooCommerce checkout block and the classic checkout.
✓✓
Card fields hosted by your gateway
Full card numbers go straight to Authorize.net and never touch your server.
✓✓
Double-charge protection
If the gateway times out, the order is held and checked before the customer can pay again.
✓✓
Full and partial refunds
Refund from the order screen. Unsettled charges are voided automatically.
✓✓
Authorize now, capture later
Capture by hand, or automatically when the order moves to Processing or Completed. Cancelling releases the hold.
✓✓
Choose accepted card brands
Show only the card brands your merchant account takes.
✓✓
Address and CVV results in order notes
See each order's address and security code checks without leaving WooCommerce.
✓✓
Order details sent to your gateway
Line items, shipping address and your statement descriptor appear in Authorize.net's reports.
✓✓
Gateway email receipts
Have Authorize.net send its own receipt to customers.
✓✓
Safe debug log
Keys and card data are removed before anything is logged.
✓✓
Saved cards
Returning customers pay with a card stored in Authorize.net's vault. Nothing sensitive is stored on your site.
–✓
WooCommerce Subscriptions
Automatic renewals, free trials, and customers updating their card.
–✓
WooCommerce Pre-Orders
Save the card at checkout and charge it automatically when the product is released.
–✓
Bank payments (eCheck)
US checking and savings accounts, refundable from the order screen.
–✓
Add a card from My Account
Customers can save a card without placing an order.
–✓
Works with popular extensions
Tested with Deposits, Bookings, Memberships, Bundles, Composite Products, Gift Cards, CartFlows, FunnelKit and more.
–✓
Priority email support
Help from the people who build the plugin, including a check of your gateway setup.
–✓

Pro uses the same settings as the free version, so upgrading keeps your setup.

Setup

  1. Install and activate the plugin.
  2. Go to WooCommerce > Settings > Payments and open Authorize.net.
  3. Enter your API Login ID, Transaction Key and Public Client Key.
  4. Choose whether to charge right away or authorize and capture later, then save.
  5. Place a test order. A sandbox account is the easiest way to test: sign up free at developer.authorize.net and check “Sandbox account”.

What you need

  • A merchant account with Authorize.net. A free sandbox account works for testing.
  • Your API Login ID, Transaction Key and Public Client Key.
  • WooCommerce 11.1 or newer and PHP 8.1 or newer.

Questions

Where do I find my API Login ID and keys?

In the Authorize.net Merchant Interface, go to Account > Settings > Security Settings. “API Credentials & Keys” has the API Login ID and lets you create a Transaction Key. “Manage Public Client Key” has the Public Client Key.

Does this support the old AIM integration?

No. AIM sends the full card number through your server, which puts your store in the strictest PCI category. This plugin uses Accept.js and the current Authorize.net API instead.

Do card numbers touch my server?

No. Full card numbers and security codes go from the shopper’s browser straight to Authorize.net. Your site receives a one-time token, the card type, the expiry date and a masked number (first six and last four digits). It keeps only the last four digits with each order, for refunds and order records. With Pro’s saved cards, it also keeps the card type and expiry, while the card itself is stored at Authorize.net.

Why does a refund need the last four digits?

Authorize.net requires them for refunds. The plugin stores the last four digits with each order, so refunds from the order screen just work.

How do refunds work before a charge settles?

Authorize.net settles charges once a day. Before that, a charge can only be voided, so a full refund of an unsettled charge is sent as a void automatically.

Can customers pay from a bank account?

Yes, with Pro. Pro adds a “Bank account (ACH)” payment option that uses Authorize.net eCheck.Net, which Authorize.net must turn on for your account first. Account and routing numbers go from the customer’s browser straight to Authorize.net. Bank payments can be refunded from the order screen like cards.

Does it support 3D Secure?

No. Authorize.net doesn’t offer 3D Secure 2 to stores that connect through its API.

Need a merchant account?

Easy Pay Direct sets up merchant accounts for online stores, and their team handles approval and setup.

Some "apply for an account" links on this site are referral links. Gateway Wizard may be paid a referral fee if you open an account through one. It costs you nothing extra.

Ready to take Authorize.net payments on your store?

Pro starts at $79 a year for one site. If you ever stop renewing, your checkout keeps working.

Buy Pro