Oliver POS doesn't have a partnership with Authorize.Net. It supports Authorize.Net the same way any WooCommerce store does — through Authorize.Net's official WooCommerce plugin, opened inside Oliver's in-POS browser view at the counter. Authorize.Net authorises the card against the merchant's existing acquirer, WooCommerce records the order, and Oliver is the till. This guide is aimed at established US merchants who already run Authorize.Net through an ISO and want a WooCommerce-first counter experience.
What Authorize.Net is, exactly
Authorize.Net is one of the oldest US payment gateways, founded in 1996 and acquired by Visa in 2010. It is a gateway in the strict sense: it authorises card transactions and passes them to an acquiring bank (Wells Fargo, Chase Paymentech, Worldpay, Elavon, and many ISOs), rather than acting as the acquirer itself. Hundreds of thousands of US small and mid-sized businesses use it, typically with a merchant account sourced from an Independent Sales Organisation (ISO).
Accept Hosted is Authorize.Net's hosted payment page — an Authorize.Net-owned URL where the customer enters the card. The merchant's site never touches the card data, which keeps PCI scope at SAQ A. That's the page Oliver opens at the counter.
How Oliver POS opens Authorize.Net at the counter
The Authorize.Net WooCommerce POS flow inside Oliver is the same hosted-checkout pattern as every other gateway in this series:
- The cashier rings the sale on the Oliver register and taps Charge.
- Oliver writes a pending WooCommerce order against the Authorize.Net gateway.
- Oliver opens the Authorize.Net Accept Hosted page in the in-POS browser view — a full-screen webview locked to that one sale.
- The cashier rotates the tablet to the customer. The customer enters the card on the Authorize.Net page.
- Authorize.Net authorises against the merchant's acquirer and posts the result back to WooCommerce. The order flips to processing.
- Oliver picks up the confirmation, closes the browser view, and prints the receipt.
Funds settle from the merchant's acquiring bank to the merchant's deposit account on whatever terms are in the ISO contract — usually next business day. Oliver never sits in the funds flow.
The Authorize.Net WooCommerce plugin — what Oliver rides on
The plugin Oliver rides on is the Authorize.Net for WooCommerce extension. The most widely deployed free build is wordpress.org/plugins/payment-gateway-for-authorize-net-for-woocommerce, which supports Accept Hosted, Accept.js card forms, and eCheck (ACH). A paid Authorize.Net extension is also available from WooCommerce.com for stores that want subscriptions and tokenised re-billing in one bundle.
Configuration is the same regardless of channel: install the plugin, enter the API Login ID and Transaction Key from the Authorize.Net merchant interface, and enable Accept Hosted under WooCommerce → Settings → Payments. Oliver auto-detects any enabled gateway and lists Authorize.Net as a tender option on the register. If Authorize.Net works for the online store, the same credentials drive Authorize.Net at the counter.
Why Authorize.Net is a good fit (or what to know)
Authorize.Net is rarely a brand-new merchant's first gateway. It is, however, often the right answer for a specific profile of merchant:
- Established US merchants with ISO contracts. If the merchant already has a Visa/Mastercard merchant account with an ISO at interchange-plus pricing, Authorize.Net is the gateway most ISOs default to. Rates are set in the ISO contract; the gateway fee itself is around $25/month plus $0.10 per transaction at list, often less under negotiated deals.
- Visa-owned, very stable. Visa's ownership since 2010 means deep card-network plumbing and uptime tracking that most newer gateways can't match.
- eCheck / ACH. Authorize.Net supports US bank ACH payments through the same plugin. That can matter for higher-ticket counter sales — furniture, equipment, B2B — where the customer would prefer a bank pull to a card.
- Fraud Detection Suite. Authorize.Net's FDS adds velocity, geolocation, and AVS-based rules at no extra cost.
- Tokenisation. Customer Information Manager (CIM) stores tokenised payment methods inside Authorize.Net so a returning counter customer can be charged against a saved card without re-entering it.
What this is NOT
Oliver POS is not an Authorize.Net partner. There is no co-marketing agreement, no revenue share, and no special Authorize.Net rates for Oliver merchants. Oliver does not charge a markup on Authorize.Net transactions; the merchant pays Authorize.Net (and the underlying acquirer) directly on whatever rates are in the merchant's existing contract. Authorize.Net is the gateway of record and the merchant's acquirer is the merchant of record; the deposit account, refund flow, dispute handling, and 1099-K all stay where they already are. Oliver is the POS software sitting on top.
Setup in 4 steps
- Install an Authorize.Net WooCommerce plugin — for example payment-gateway-for-authorize-net-for-woocommerce — on your WooCommerce store.
- Enter your Authorize.Net API Login ID and Transaction Key, enable Accept Hosted, and (optionally) enable eCheck under WooCommerce → Settings → Payments.
- Install Oliver POS, sign in on the counter tablet, and pick the Authorize.Net gateway from the tender list — Oliver auto-detects it from WooCommerce.
- Run a small live test sale at the counter and confirm the order appears in WooCommerce, in the Authorize.Net merchant interface, and on the printed receipt.
FAQ
Does Oliver POS partner with Authorize.Net?
No. Oliver POS is not an Authorize.Net partner. Authorize.Net is supported because there are official-grade WooCommerce plugins that any WooCommerce store can install, and Oliver opens that gateway in our in-POS browser view at the counter.
Does Oliver charge a markup on Authorize.Net?
No. Your Authorize.Net and ISO contract rates are what they are. You pay your acquirer and Authorize.Net directly. Oliver's pricing is a flat monthly POS software fee, independent of gateway choice.
Can I take ACH (eCheck) at the counter?
Yes, if eCheck is enabled in your Authorize.Net account and turned on in the plugin. ACH appears as a separate option on the Accept Hosted page Oliver opens, and the customer enters routing and account numbers there.
Do I keep my existing ISO contract?
Yes — that's the whole point. Oliver does not replace your merchant account or your ISO. Your existing acquirer remains the merchant of record, and the only thing that changes is that the WooCommerce-driven Authorize.Net register sale now also runs through that same gateway, opened by Oliver.
Try Oliver POS free for 30 days at /demo/ — bring your existing WooCommerce store and your existing Authorize.Net account.