The short answer
- It is a paid extension. WooCommerce.com showed CAD $114 for a one-year plan when we read it, with a 30-day money-back guarantee.
- Canada is on its country list. The listing names Australia, Canada, New Zealand and the United States.
- You choose charge or authorize. "Charge" captures at checkout and is the default. "Authorization" holds the money until you capture it.
- Saved cards need CIM. CIM is Authorize.Net's card vault. Subscriptions, Pre-Orders and saved cards all need it, and Authorize.Net may charge a monthly fee for it.
- Refunds start in WooCommerce. Staff refund from the Edit Order screen. Unsettled payments are voided instead.
- Other Authorize.Net plugins exist. WooCommerce.com also lists "Authorize.net for WooCommerce" by Authorize.Net. It is a different extension, so check its own docs.
How a payment travels
The customer types the card on your checkout page. Accept.js, a script from Authorize.Net, turns it into a one-time token in the browser, so the card number never touches your server. The extension then sends the token to Authorize.Net.
- WooCommerce checkout (Accept.js)
- Authorize.Net
- Charge or authorization
- Capture when the order is paid
- Renewals charged to the saved card
| Step | Where it happens | Who controls it |
|---|---|---|
| Customer enters card | Your WooCommerce checkout | You and your theme |
| Card becomes a token | Accept.js in the browser | Authorize.Net |
| Charge or authorization sent | The extension | SkyVerge's code, your settings |
| Card saved for later, if chosen | CIM on Authorize.Net's servers | Authorize.Net |
| Approval and settlement | The processor | Your merchant account provider |
| Capture, refund or void | WooCommerce Edit Order screen | Your staff |
What WooCommerce does with Authorize.Net
| Feature | What the extension's documentation says |
|---|---|
| Transaction type | "Charge" captures right away. "Authorization" needs a capture later, in WooCommerce or in Authorize.Net |
| Capture on order status | With "Capture Paid Orders" on, it captures when an order moves to a paid status |
| Manual capture | A "Capture Charge" action on the Edit Order screen |
| Virtual-only orders | Can be charged at once, even in authorization mode |
| Refunds | Full or partial, from the Edit Order screen, for card payments |
| Voids | Automatic when a payment is not yet captured or settled. No partial voids |
| Saved cards | Stored as tokens in CIM. Customers add, remove and pick a default under My Account |
| WooCommerce Subscriptions | All Subscriptions features, by card or eCheck |
| WooCommerce Pre-Orders | Saves the payment method up front and charges it when the pre-order is released |
| Checkout form | Inline form (PCI SAQ A-EP) or lightbox (PCI SAQ A). Works with Cart and Checkout blocks |
| Webhooks | Optional. Tell the site when profiles are deleted in Authorize.Net |
| Test mode | Uses a separate Authorize.Net sandbox account with its own login and keys |
| eCheck | US bank accounts only, and needs an Authorize.Net eCheck account |
| Not documented | Level 2 or Level 3 card data, Interac, multi-currency routing, partial capture |
Canada and Canadian dollars
The listing names Canada and says the extension supports all Authorize.Net merchant account regions. Its documentation does not mention Canadian dollars or currency settings. The currency comes from your Authorize.Net account. Authorize.Net sets each account to one currency, as our Authorize.Net in Canada page explains. If you sell in CAD and USD, the docs do not say how this extension would send each order to the right account. Confirm that with SkyVerge before you plan two accounts.
The eCheck option runs on US bank accounts. It is not a way to debit Canadian bank accounts.
CleverPays can open both, a CAD Authorize.Net account and a USD one, and add American Express to them.
Limits to know before you rely on it
- Authorizations expire. Authorize.Net expires an uncaptured authorization after 30 days. You can capture once, for no more than the authorized amount. For pre-orders, the docs describe a charge to the saved card on release.
- Renewals fail if card codes are required. Authorize.Net cannot store the security code for renewals. If your account demands one, subscription renewals fail. The docs explain how to drop that rule.
- Do not share API keys across sites. The docs warn that one set of credentials on two sites can break profile sync and renewals.
- Update cards on the site, not in Authorize.Net. The extension pushes changes to Authorize.Net but is not told about changes made there. A card updated by phone in Authorize.Net can leave renewals pointing at an old token.
- Partial refunds wait for settlement. Within about 24 hours of the charge, a partial refund fails because a void must be for the full amount.
- No 3D Secure, and Apple Pay is extra work. The docs say 3D Secure is not supported. Apple Pay needs a developer and does not work with the checkout blocks.
Who this fits
These are example scenarios, not CleverPays customers.
A wholesale order portal for trade buyers
A Québec food distributor runs a login-only WooCommerce store for restaurant accounts. Staff set the extension to "Authorization" and turn on "Capture Paid Orders". Each order is held at checkout and captured when it is marked paid after picking. Short-shipped lines can be refunded from the order screen once the charge settles.
A subscription box
An Ontario coffee roaster ships a box each month through WooCommerce Subscriptions. Renewals charge the card saved in CIM. Customers swap cards through the subscription's "Change Payment" step. Simply adding a new card to their account does not move the subscription.
A store that takes pre-orders
A Vancouver outdoor-gear shop sells a jacket two months before stock lands. WooCommerce Pre-Orders saves the customer's card at checkout. The extension charges it when the pre-order is released, which avoids the 30-day authorization limit.
Changing the processor behind WooCommerce
If you keep the same Authorize.Net account and change only the processor, Authorize.Net says your API connection is not affected. Your API Login ID, keys and CIM profiles stay where they are, so saved cards and subscriptions keep their tokens. Refunds on older orders go to the new processor, so keep the old merchant account open until those are done. The parent page's processor change plan lists the steps.
Moving to a new Authorize.Net account is a bigger job. The extension stores customer and payment profile IDs on each WordPress user. Those IDs point at the old account's CIM, and the docs say renewals fail when IDs do not match. Plan that move before you promise anything about saved cards.
Where CleverPays fits
SkyVerge builds and supports the extension. WooCommerce.com sells it and handles the subscription billing for it. Authorize.Net runs the gateway and the CIM vault. The processor approves and settles each payment. CleverPays does not make, certify or support the extension.
We can review your current statement with you, open the Authorize.Net account and the Canadian merchant account behind it, and connect it to your WooCommerce store with you. We can test a charge, a capture, a refund and the first deposit before you go live. We can stay your contact after launch, in English and French. We can also open a USD account and add American Express.
Sources
- WooCommerce.com: Authorize.net, a Visa solution for WooCommerce (SkyVerge), read 6 October 2026
- WooCommerce.com: WooCommerce Authorize.net documentation, read 6 October 2026
- WooCommerce.com: Authorize.net for WooCommerce (a different extension), read 6 October 2026
- Authorize.Net: payment transactions, authorization and capture, read 6 October 2026
- Authorize.Net: processors and currencies, read 6 October 2026
- Authorize.Net: what happens when you update your processor, read 6 October 2026
Product and company names on this page are trademarks of their respective owners. CleverPays is not affiliated with or endorsed by them.
