Authorize.net integrations by platform

Sandbox run evidence

UAT-Ops ran the directory's canonical card flow against Authorize.net's sandbox on 2026-09-11: 5 passed, 1 expected rejection. Every request went to the real sandbox through the workbench's ordinary execution path. Keys, object ids, request and response bodies were removed before publication; the status word in the last column is the provider's own.

Step	Request	HTTP	Latency	Result	Provider status
create customer	`POST xml/v1/request.api`	200	527 ms	Pass	status=ok
authorize	`POST xml/v1/request.api`	200	666 ms	Pass	status=ok
capture	`POST xml/v1/request.api`	200	330 ms	Pass	status=ok
partial refund	`POST xml/v1/request.api`	200	318 ms	Expected rejection — not yet settled: Authorize.net answered response code 54, whose documented causes include an unsettled transaction, and the flow refunds seconds after capture, before any settlement batch	status=error
authorize for void	`POST xml/v1/request.api`	200	650 ms	Pass	status=ok
void	`POST xml/v1/request.api`	200	435 ms	Pass	status=ok

Platform pages

BigCommerce Built-in connector
Shopify Vendor plugin
WooCommerce Third-party plugin

About Authorize.net

Authorize.net is a payment gateway owned by Visa; its pricing page also describes it as a registered ISO of PNC Bank, N.A. It is one of the older gateways still in wide use, and its customers are mainly US small and mid-sized merchants taking card, ACH and wallet payments online, by phone or in person. A merchant can buy it with a merchant account included (All-in-One, 2.9% + 30 cents per transaction) or as Gateway Only for an existing merchant account (10 cents per transaction plus a 10-cent daily batch fee); every published plan carries a $25 monthly fee.

The API predates modern REST conventions. Almost everything is an XML or JSON document sent by HTTPS POST to one endpoint, /xml/v1/request.api, on apitest.authorize.net for the sandbox and api.authorize.net for production, authenticated by an API Login ID and Transaction Key. That single endpoint covers charges, authorizations, captures, refunds, voids, eCheck, Apple Pay, Google Pay, PayPal Express Checkout, stored customer profiles (CIM), recurring billing (ARB), Level 2/3 data and reporting. Webhook management is a separate REST API under /rest/v1/webhooks; notifications carry an X-ANET-Signature header, an HMAC-SHA512 keyed with a Signature Key distinct from the Transaction Key. Accept.js tokenizes card data in the browser to keep a merchant-built form within SAQ A-EP; the hosted form is positioned as SAQ A.

The sandbox is free and self-serve, with its own credentials. Two details catch people: sandbox and production credentials never cross over (mixing them returns response reason code 13), and the sandbox account should stay in Live Mode, because Test Mode stores nothing and returns a transaction ID of zero.

What we checked

Developers can sign up for a free sandbox account through a self-service form; the sandbox simulates card network connections and processes no real payments.¹
Sandbox and production credentials are not interchangeable; mixing them always returns response reason code 13, and the testing guide lists sandbox-only test card numbers.²
The payment API accepts XML or JSON over HTTPS POST, with sandbox at apitest.authorize.net/xml/v1/request.api and production at api.authorize.net/xml/v1/request.api, authenticated by API Login ID and Transaction Key.³
The API reference covers cards, Apple Pay, Google Pay, PayPal Express Checkout, ACH/eCheck, stored customer profiles (CIM), recurring billing (ARB), partial refunds and Level 2/3 data.³
Webhook notifications carry an X-ANET-Signature header, an HMAC-SHA512 of the body keyed with the merchant's Signature Key, which is separate from the Transaction Key used to call the webhook REST API.⁴
Accept.js tokenizes card data into a one-time payment nonce; a merchant-built form with Accept.js is positioned as SAQ A-EP, while the embedded hosted form or Accept Hosted is positioned as SAQ A.⁵
All three published plans carry a $25 monthly fee; All-in-One charges 2.9% + 30 cents per transaction, and Gateway Only charges 10 cents per transaction plus a 10-cent daily batch fee.⁶
The pricing page describes Authorize.net as a Visa solution and a registered ISO of PNC Bank, N.A.⁶

Sources

https://developer.authorize.net/hello_world/sandbox.htmlofficial documentation · checked 2026-09-10
https://developer.authorize.net/hello_world/testing_guide.htmlofficial documentation · checked 2026-09-10
https://developer.authorize.net/api/reference/index.htmlofficial documentation · checked 2026-09-10
https://developer.authorize.net/api/reference/features/webhooks.htmlofficial documentation · checked 2026-09-10
https://developer.authorize.net/api/reference/features/acceptjs.htmlofficial documentation · checked 2026-09-10
https://www.authorize.net/sign-up/pricing.htmlvendor pricing page · a claim here is implied by this source, not stated · checked 2026-09-10

Last verified 2026-09-12 · Reviewed by a person 2026-09-24

Integration capabilities, requirements, pricing, availability, and vendor policies may change over time. UAT-Ops documents information based on the authoritative sources and testing available at the time of review.

Where newer information, testing, or vendor documentation materially changes a published claim, UAT-Ops may revise the page to reflect the most current verified information. Readers should confirm time-sensitive requirements with the relevant vendor before making production or purchasing decisions.