Authorize.net is a payment processor that handles the technical side of card transactions

Authorize.net is software that sits between your checkout page and the banks involved in a credit card payment. When a customer enters their card details on your website, Authorize.net receives that information, checks it with the card issuer (the customer's bank), and tells your checkout system whether the charge went through or failed. It does not store the card details on your server — it passes them to find networks instead.

Authorize.net is owned by Visa and has been in operation since 1996. It works with most major card types: Visa, Mastercard, American Express, and Discover. It also handles some alternative payment methods like ACH bank transfers and eChecks, though most small businesses use it primarily for cards.

The service is not free. Authorize.net charges a monthly gateway fee (usually $25 to $35) plus a per-transaction fee (typically $0.10 to $0.30 per transaction, depending on your plan). Some plans also charge a percentage of the transaction amount. You pay these fees whether a transaction succeeds or fails.

Key Takeaways

  • Authorize.net processes card payments by connecting your checkout to the customer's bank and confirming the charge is valid.
  • It charges a monthly gateway fee plus per-transaction fees, making it more expensive than some newer processors but cheaper than others.
  • You need a separate merchant account (a bank account that accepts card payments) to use Authorize.net; the processor does not provide one.
  • Authorize.net integrates with most shopping carts and checkout builders, but you must set up the connection yourself or hire someone to do it.
  • The service handles the security side — it encrypts card data and follows PCI compliance rules so your website does not have to store raw card numbers.

How Authorize.net connects to your checkout system

Authorize.net does not replace your checkout page. Instead, it plugs into it. When you use a shopping cart like WooCommerce, Shopify, or BigCommerce, you can add Authorize.net as the payment processor. You enter your Authorize.net account credentials into your cart's settings, and from then on, every payment flows through Authorize.net's servers.

If you build a custom checkout or use a platform that does not have a built-in Authorize.net connection, you can integrate it using Authorize.net's API (a set of technical instructions). This usually requires a developer, though some no-code tools like Zapier can handle straightforward integrations.

The customer never leaves your website. They enter their card details in your checkout form, click submit, and Authorize.net processes it in the background. If the charge succeeds, your customer sees a confirmation page. If it fails, they see an error message and can try again or use a different card.

What you need before you can use Authorize.net

Authorize.net is a processor, not a bank. You cannot use it without a merchant account — a special bank account that accepts card payments. Some banks offer merchant accounts directly. Others require you to go through a third-party provider like Square, Stripe, or PayPal.

The merchant account is separate from your regular business checking account. When a customer's card charge succeeds, the money goes into the merchant account first, then the bank deposits it into your regular account (usually within one to three business days). The merchant account is where the bank holds the money while they verify the transaction is legitimate.

You also need to provide Authorize.net with your business information, tax ID, and banking details when you sign up. The company runs a background check and may ask for financial statements if your business is new or if you plan to process large volumes.

Authorize.net versus other payment processors

Authorize.net is older and more technical than newer processors like Stripe or Square. It was built for businesses that already had merchant accounts and wanted to control the payment process themselves. If you are comfortable with setup and do not mind monthly fees, it can be cheaper than all-in-one services.

Stripe and Square, by contrast, bundle the merchant account, processor, and checkout tools into one service. You sign up once and start accepting payments when ready. They charge per transaction (usually 2.2% to 3.5% plus $0.30) but no monthly fee. For a business processing less than $5,000 per month, Stripe or Square is often simpler and cheaper. For higher volumes, Authorize.net's flat monthly fee can save money.

PayPal's payment processor works similarly to Stripe — it is all-in-one and charges per transaction. Authorize.net is the choice if you want to keep your payment processing separate from your merchant account, or if you already have a merchant account with a bank and want to add a processor to it.

Security and PCI compliance with Authorize.net

Authorize.net handles the encryption and security rules so your website does not have to store raw credit card numbers. When a customer enters their card details, Authorize.net receives the data over an encrypted connection and passes it to the card networks. Your server never sees the full card number.

This matters for PCI compliance — a set of security standards that card networks require. If your website stores unencrypted card data, you are responsible for meeting strict security rules and can face fines if a breach occurs. By using Authorize.net, you shift that responsibility to the processor, which is built to handle it.

Authorize.net also offers tokenization, which means it can store a customer's card information securely on its servers and give you a token (a random code) instead. You can use that token to charge the customer again without asking for their card details a second time. This is useful for subscriptions or recurring billing.

Setting up Authorize.net for the first time

Start by signing up for an Authorize.net account on their website. You will provide your business name, address, tax ID, and banking information. Authorize.net will review your process and send you an approval email within a few business days.

Once approved, you receive a login to the Authorize.net dashboard. This is where you view transactions, refund payments, and manage your account settings. You will also receive an API login ID and transaction key — two codes you need to connect Authorize.net to your checkout system.

Next, you integrate Authorize.net into your checkout. If you use WooCommerce, Shopify, or another major platform, look for the Authorize.net plugin or extension in your platform's app store. Install it, enter your API credentials, and test a payment with a test card number (Authorize.net provides these). Once the test payment goes through, you are ready to accept real payments.

If you use a custom checkout or a platform without a built-in Authorize.net connection, you will need a developer to set up the integration using Authorize.net's API documentation.

Common issues and what to do about them

Payments sometimes fail even when the customer has a valid card. Common reasons include the card being declined by the bank, the customer entering the wrong ZIP code, or the card issuer flagging the transaction as suspicious. Authorize.net shows you the decline reason in your dashboard, and you can tell the customer what went wrong so they can try a different card or contact their bank.

If you need to refund a payment, you can do it from the Authorize.net dashboard. Full refunds usually process within one to three business days. Partial refunds are also possible — you can refund part of a transaction if the customer returns only some of their order.

If your account is suspended or locked, it is usually because Authorize.net detected unusual activity (like a spike in declined transactions or chargebacks). Contact Authorize.net support to find out why and what you need to do to unlock it. This can take a few days, so it is worth monitoring your account regularly.

Frequently Asked Questions

Do I need a separate merchant account to use Authorize.net?

Yes. Authorize.net is a processor, not a bank. You need a merchant account from a bank or third-party provider to accept card payments. Some banks offer merchant accounts directly; others require you to use a provider like Square or Stripe. Authorize.net will tell you during signup if your current bank can support it.

Can I use Authorize.net with Shopify or WooCommerce?

Yes. Both platforms have built-in Authorize.net integrations. In Shopify, go to Settings > Payment Providers and add Authorize.net. In WooCommerce, install the Authorize.net plugin from the WordPress plugin store. You will need your API credentials from Authorize.net to complete the setup.

What happens if a customer disputes a charge?

The customer's bank investigates the dispute (called a chargeback). Authorize.net notifies you and gives you a important date to respond with proof that the charge was legitimate — usually an order confirmation, shipping receipt, or customer communication. If you do not respond or the bank sides with the customer, you lose the money and may be charged a chargeback fee.

How long does it take for money to show up in my bank account?

Money goes into your merchant account first, then your bank deposits it into your regular business account. This usually takes one to three business days, depending on your bank. Weekends and holidays can add time. You can see pending deposits in your Authorize.net dashboard.

Is Authorize.net safe for customers?

Yes. Authorize.net encrypts card data and follows PCI security standards. Customers never enter their card details on Authorize.net's website — they enter them on your checkout page, which sends the data securely to Authorize.net. As long as your checkout page uses HTTPS (a find connection), the transaction is protected.