What we do
Tools
Industries
Department
How we workLet's talk →
Home/Authorize.net
Authorize.net API

The Authorize.net API: Which Piece You Need, and How It Authenticates

Authorize.net's developer site lists Accept.js, Accept Hosted, Customer Profiles, recurring billing, webhooks and reporting side by side. Most integrations need two or three of them. Here's which ones match the job on your desk, then the credentials and the one endpoint they all share.

Where Authorize.net stops

Failed charges mean decoding error codes by hand, then matching what settled to the right order or invoice.

Stuck on Authorize.net? Let's solve it →

Pick the part of the Authorize.net API by the job

The job Use Worth knowing
Take cards on your own checkout page Accept.js in the browser, then createTransactionRequest from your server Accept.js swaps the card for a one-time nonce (opaqueData) that's valid for 15 minutes. Your server never sees the card number. Authorize.net describes this as an SAQ A-EP setup.
Keep card entry off your site entirely Accept Hosted Your server requests a token, then redirects to or embeds Authorize.net's own payment form. Less control over the look of the page.
Charge returning customers without storing cards Customer Profiles (Accept Customer) Authorize.net stores the payment method and gives you profile IDs to charge later.
Bill the same amount on a schedule Automated Recurring Billing (ARB) Authorize.net runs the schedule. Your system still needs to hear when a payment in it fails.
React when a charge, refund or void happens Webhooks Notifications carry part of the transaction. Call getTransactionDetails for the full record.
Reconcile what actually settled Transaction Reporting: getSettledBatchList, then getTransactionList per batch Settlement is batch by batch, so this is the report that should match the deposit, not the day's approvals.

Credentials and the one endpoint

Server-side calls authenticate with your API Login ID and Transaction Key, sent in a merchantAuthentication block inside each request. You'll find both in the Merchant Interface under Account, Settings, Security Settings, API Credentials & Keys. The same page holds the Signature Key for webhooks, and Accept.js uses a separate Public Client Key that's safe to put in a web page.

Every API request goes to one URL: https://api.authorize.net/xml/v1/request.api in production and apitest.authorize.net in the sandbox, which has its own account and its own credentials. Requests can be JSON or XML. Webhooks are managed through a separate REST endpoint, /rest/v1/webhooks, or in the Merchant Interface. For sandbox card numbers and decline triggers, see Authorize.net test cards.

Where the order, the gateway and the books stop agreeing

The webhook is treated as the whole record

How you'll know: Orders get marked refunded or paid with missing fields, or with a status that changed since the notification went out.

Fix: Treat the webhook as a nudge. Look the transaction up with getTransactionDetails before updating anything.

Webhooks quietly went inactive

How you'll know: Events stopped arriving some time ago and nothing raised an alarm.

Fix: Authorize.net retries a failed delivery up to 10 times over a widening schedule, then marks the webhook inactive. Return a 200 first and do the work afterward, and alert on a gap in events.

Anyone can post to your listener

How you'll know: The endpoint accepts any request that looks like a notification.

Fix: Recompute the HMAC-SHA512 of the body with your Signature Key and compare it with the X-ANET-Signature header. Drop any request where the two differ.

Approvals are booked as if they'd settled

How you'll know: The books show the day's approvals, and the deposit never matches them.

Fix: Book from settled batches instead. Voids drop out, refunds land in later batches, and the batch total is the number to line up with the bank.

A parts retailer that matched batches by hand

Regional parts retailer · Authorize.net for web and phone orders

Before

Each settled batch was matched to its orders by hand, and a short deposit could go unnoticed for weeks.

After

Settled batches are now matched line by line to orders and reach accounting already reconciled.

A short deposit now surfaces the same day, not weeks later.

Questions people ask

What is Authorize.net?

A payment gateway owned by Visa. It authorizes, captures and settles card and eCheck transactions for websites, apps and points of sale, and it usually sits alongside a separate merchant account. Its API has been around a long time and most eCommerce platforms support it.

How do I get my Authorize.net API credentials or transaction key?

In the Merchant Interface, open Account, then Settings, Security Settings, API Credentials & Keys. Your API Login ID is shown there, and you can generate a new Transaction Key. A new key replaces the old one, so update every system that uses it.

How much does Authorize.net cost?

There's a monthly gateway fee plus a per-transaction fee, on top of whatever your merchant account charges for processing. The numbers vary by plan and change, so check Authorize.net's own pricing page.

Is Authorize.net safe to use?

Yes. It's PCI DSS compliant, Accept.js and Accept Hosted keep raw card numbers off your servers, and its fraud filters can hold suspicious charges for review. How safe your integration is still depends on how it stores keys and checks webhook signatures.

Does Authorize.net work with WooCommerce?

Yes, through a gateway extension that handles checkout, authorization and capture. What happens to the transaction after checkout, such as matching it to stock or your books, is where custom work usually starts.

Is Authorize.net better than Stripe?

They're built differently. Stripe includes the merchant account; Authorize.net is a gateway that usually pairs with one, which can suit some volumes and means more pieces to set up. n-frames works with whichever one a business already runs.

Does Authorize.net integrate with QuickBooks?

Connector apps can sync basic transaction data. Matching each payment to its invoice with fees, refunds and chargebacks handled properly usually takes a custom integration built on the reporting API, and that's the part n-frames builds.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.