Authorize.net

Also called Authorize.Net, Auth.net, AuthorizeNet

The gateway everyone has heard of, owned by Visa, ubiquitous and aging. Merchants ask for it by name more than they should.

What it is

Authorize.net is one of the oldest payment gateways in the United States and is owned by Visa. It sits between a merchant's website or virtual terminal and the processor, handling authorization, the customer information manager for stored cards, recurring billing, fraud filters and reporting. Its integration footprint is enormous: nearly every shopping cart, invoicing tool and legacy ERP built for US small business supports it, which is the main reason it persists. Authorize.net runs four partner programs — a Reseller program on a buy-rate model, a Technology Partner program, a Certified Solution Partner track and Business Services — though it publishes no economics on the partner page. Merchant-facing gateway pricing similarly is not published on the partner side. In 2026 the practical positioning is defensive rather than aspirational. Authorize.net works, it's trusted, and it's what a merchant's web developer or bookkeeper will name unprompted. What it can't do is be branded by a local provider, and its feature velocity trails newer gateways on things like network tokens, orchestration and modern developer tooling.

Why it matters to your business

If your web developer or your accountant asks for Authorize.net, they usually mean "something that will definitely integrate," not "this specific gateway." It's worth asking whether a modern alternative supports your cart, because gateway fees and per-transaction charges vary enormously by reseller and newer gateways bundle features you may be buying separately. And if you keep it — which is often reasonable — check what you're paying. A gateway monthly fee plus a per-transaction gateway fee on top of your processing per-transaction fee is a stack most merchants have never separated out.

Where it gets contested

The core structural point about Authorize.net is ownership: it belongs to Visa. A gateway owned by a card network is not neutral infrastructure in the way an independent gateway is, and merchants and ISOs should understand that the entity operating their routing layer also has interests in how transactions are routed and tokenized. The practical merchant complaints are older and more mundane: monthly gateway fees plus per-transaction fees that vary widely by reseller, a dated interface, and support quality that depends heavily on whether you bought direct or through a reseller. Because it's resold by thousands of ISOs, the same gateway carries very different prices — the same variance problem Clover has on the hardware side. The fair defense is that Authorize.net's reliability and integration breadth are genuine assets. For a merchant with a ten-year-old shopping cart or an accounting integration that only supports one gateway, Authorize.net isn't nostalgia — it's the thing that works. Replacing it for feature reasons alone often costs more in developer time than it saves in fees.

How to check it yourself

On your statement, find the gateway monthly fee and the gateway per-transaction fee separately from your processing fees. Multiply the per-transaction gateway fee by your monthly transaction count. That total, plus the monthly, is what your gateway costs — and it's frequently more than merchants assume.

Receipts

Claims above that are checkable, with where to check them. Published so you do not have to take anyone's word for it.

Authorize.net runs four partner programs including a Reseller program on a buy-rate model, with no economics published on the partner page
authorize.net ↗
Authorize.net is owned by Visa and remains one of the most broadly integrated gateways in US small business
authorize.net ↗