Authorize.Net Merchant Account: Do You Need One and How to Get It

No. Two different things have to be in place before you can take a card payment online:

• The payment gateway (Authorize.Net). Software that takes the card details from your checkout page, cart or virtual terminal and sends them securely to the processor. It also gives you the tools around the payment: fraud filters, recurring billing, saved cards and reports.
• The merchant account. An account with an acquiring bank (the bank that accepts card payments on your behalf). The bank approves your business, carries the risk of your sales and pays the money out to your business bank account.

In short, the gateway moves the transaction and the merchant account moves the money. You need both, and Authorize.Net's own support article says the merchant account must come from a provider "based in the United States or Canada."

So the real question isn't whether you need a merchant account for Authorize.Net. It's where yours comes from. For a tour of the gateway's features, see our Authorize.Net payment gateway overview.

Each route gets you the same gateway. What changes is who approves you, who you call when something goes wrong, and how you're priced.

All-in-One. Authorize.Net's pricing page, checked September 27, 2026, lists All-in-One at $25 a month plus 2.9% + 30¢ per transaction, with the merchant account included. The same page says the merchant account "may have separate terms," so read those as well as the gateway agreement.

Gateway Only. If you already have a merchant account, Authorize.Net lists Gateway Only at $25 a month, 10¢ per transaction and a 10¢ daily batch fee. Your card processing fees come from your merchant account provider on top of that. Authorize.Net's own page makes the case for this route: you can negotiate interchange-plus pricing, which it says often lands "closer to 2.2% - 2.5%."

Provider bundle. A merchant services provider (Authorize.Net calls them reseller partners) sets up the merchant account and the Authorize.Net gateway together. The provider sets its own gateway fee, so get every fee in writing: monthly, per transaction, batch and setup. START has worked with Authorize.Net for more than 20 years and set up over 60,000 Authorize.Net accounts. We price the merchant account on interchange-plus: the card network's cost plus a fixed markup. That's the route we recommend: an account in your business's name, matched to a bank that approves what you sell, with pricing that doesn't stay flat as you grow.

That's the only place the fee numbers appear here. For the full list, the free add-ons and a flat-rate vs interchange-plus example, read Authorize.Net pricing and fees. For how interchange-plus works, see interchange-plus pricing explained.

Whichever route you choose, the merchant account goes through underwriting: the bank's review of your business before it agrees to process your cards. The gateway itself doesn't approve you. The questions are much the same everywhere:

• Business details: legal name, address, tax ID (EIN, or SSN for a sole owner), business type and how long you've been open.
• Owner details: name, home address, date of birth and a government-issued ID for each owner. Most banks also run a credit check.
• A business bank account for deposits, usually confirmed with a voided check or a bank letter.
• What you sell and how: your products, average sale, expected monthly volume and whether sales are online, by phone or in person.
• Your website, if you sell online: clear prices, a refund and return policy, shipping terms and contact details. Our list of website requirements for accepting credit cards covers what reviewers look for.
• Processing statements from the last few months, if you already take cards. They show your volume and chargeback history.

A complete file is the fastest file. Missing documents and a website without a refund policy are two of the most common reasons an application stalls.

Selling something banks call high risk, such as CBD, firearms, vape products, subscriptions with free trials or travel? Expect more questions and a closer look at your chargeback history. Read how to get approved for a high risk merchant account before you apply.

Here's how to set up Authorize.Net from application to first sale. The order is the same on every route. How long each step takes depends on your provider and your file.

1. Apply. Send the business, owner, bank and website details above.
2. Get approved. The bank approves the merchant account, sometimes with conditions such as a processing limit.
3. Get your gateway login. Once the gateway account is built, you sign in to the Authorize.Net Merchant Interface (the online account where you see transactions, issue refunds and change settings) with a username and password.
4. Create your API credentials. In the Merchant Interface, go to Account › Security Settings › API Credentials & Keys to create your API Login ID and Transaction Key. These connect your website or cart to the gateway. Authorize.Net says they are "not valid for logging into the Merchant Interface." Treat them like a password and share them only with whoever sets up your cart.
5. Connect how you'll take payments. Enter the API credentials in your shopping cart's payment settings, or have your developer add them to your site. To take phone and mail orders, use the virtual terminal inside the Merchant Interface; no website needed. See Authorize.Net shopping cart integrations and the Authorize.Net virtual terminal guide.
6. Set your fraud filters and users. Turn on the fraud filters that fit your business and add a separate login for each staff member. Our guide to the Authorize.Net Fraud Detection Suite has starter settings.
7. Run a live test. Make sure the account isn't in test mode. Then run a small real sale with your own card, check it in the Merchant Interface and refund it (or void it before it settles). Confirm the deposit reaches the right bank account.

Building a custom checkout rather than using a cart? Read Authorize.Net integration methods first. Some older connection methods are deprecated.

Maybe you started on All-in-One and outgrew the flat rate, or you want to leave your current provider. Either way, the gateway can stay Authorize.Net while the merchant account behind it changes. Plan for these before you move:

• Ask whether you keep your gateway account or get a new one. It depends on the providers involved, so ask your new provider directly and plan for either answer. A new gateway account means a new API Login ID and Transaction Key in your cart, and fresh settings for fraud filters, users and notifications.
• Saved cards and subscriptions live in the gateway account. Stored customer payment profiles and Automated Recurring Billing (ARB) subscriptions sit in your Authorize.Net gateway account, not in your merchant account. If you're getting a new gateway account, ask how those will move before you close anything. See how saved cards (CIM) work.
• Check your contract. Authorize.Net's pricing page says it has no early termination fee. Your current merchant account provider may have its own terms, so read them.
• Run both until the new one works. Don't cancel the old account until the new one has processed and settled real sales and the money has reached your bank. Keep the old login long enough to issue refunds on past sales and download your reports.

For the full switch-over checklist, including termination fees and equipment leases, see how to switch merchant services providers.

Moving off a payment app instead? See Authorize.Net vs Stripe, PayPal and Square, which covers why businesses switch and how to move without a gap.

On All-in-One, the merchant account comes from Authorize.Net's bank program, and it's approved "subject to eligibility." If that merchant account is closed, often after a review of what you sell or a rise in chargebacks, you can usually still use an Authorize.Net gateway. You need a merchant account from a provider whose bank approves your type of business.

• Ask for the reason in writing, and ask when any held funds will be released.
• Ask what happens to your gateway account, saved cards and subscriptions, and export your customer and transaction reports while you can still sign in.
• Apply for a new merchant account with the full story. Underwriters see past closures anyway, so explaining what changed helps.

Our guide on what to do when a payment provider shuts you down covers held funds and the first 48 hours. If you sell high-risk products, read how a high risk payment gateway works: the gateway doesn't approve you, the merchant account does.

Canadian businesses can use Authorize.Net with a merchant account from a U.S. or Canadian provider, and each gateway account runs in one currency. Read Authorize.Net in Canada for CAD, USD and setup.