Authorize.net is a payment gateway, not a merchant account. Your MID is the constraint.
Authorize.net (Visa-owned since 2010) is a gateway — it routes transactions to whatever merchant account you're boarded on. For high-risk operators, that acquirer relationship is where every real constraint lives: reserves, chargeback thresholds, MATCH exposure. Authorize.net's own AUP echoes Visa's restricted-merchant list, so high-risk verticals either can't use it or can't find an acquirer that will pair with it.
For US-domestic small business e-commerce with a compatible acquirer (Chase Merchant Services, First Data, Global Payments), Authorize.net is a stable gateway with mature integrations. That combination doesn't exist for most high-risk verticals.
As a Visa subsidiary, Authorize.net's AUP mirrors Visa's restricted list. iGaming, adult, cannabis, peptides, firearms, and multi-level marketing are prohibited or require specialized acquirer approvals that most merchants can't obtain.
Merchants shopping for Authorize.net compatibility often end up on high-risk acquirers with 12–24 month reserve terms, VAMP-tier chargeback exposure, and full MATCH liability. The gateway is stable; the underwriting relationship is not.
The typical high-risk operator using Authorize.net pays a monthly gateway fee ($25–$99), per-transaction gateway fee ($0.10–$0.15), plus 4–10% blended acquirer discount. Total cost of processing frequently exceeds 12% at the smaller volume tiers.
Row-by-row: what Authorize.net actually charge you
Up to 540 days for certain categories. Merchant bears CNP liability by default. Mastercard ECM fines run $1k–$200k/month once thresholds trip.
Stablecoin transfers are non-reversible once confirmed. No dispute window, no representment burden.
High-risk merchants routinely surrender 10%+ of gross volume, released on a lag. Additional post-termination hold of another 180 days after MID closure.
Non-custodial rails — no acquirer sits between you and the payment.
Mastercard MATCH termination sticks for 5 years and locks you out of every mainstream acquirer. Acquirer-side freezes routinely precede network thresholds.
Operator settles to a wallet the operator controls. USDT/USDC blacklists exist but target OFAC / mule addresses, not merchant flows.
Standard e-com is T+1–2. High-risk verticals slip to T+3–7 or longer during review. Reserve carve-out lands on top of this.
TRC20 finalizes in roughly 3 seconds per block; Solana in ~400ms; Ethereum in ~1–5 minutes.
Add rolling-reserve capital cost, $8/dispute VAMP fees, PCI compliance fees, and ECM penalty tiers.
No dispute fees, no reserve capital cost, no MID monthly fees, no chargeback penalties.
Peptides / nutra (MCC 5122) categorically rejected by Stripe, PayPal, Square, Adyen. iGaming MCC 7995 sees 20–40% issuer declines, sometimes 50%+ regionally.
Stablecoin rails have no equivalent classification system; the rail cannot be gated by category code.
12+ months of processing statements, UBO documentation, personal guarantee, website / TOS / refund-policy review before boarding.
No underwriting file. No 12-month statement history. No license-acquirer combination gate.
iGaming card top-up conversion averages ~40% vs. ~65% for local A2A rails. Payment friction eats 15–30% of potential revenue.
Fresh address per transaction. Screenshot + cross-rail verification for Cash App / Zelle / Apple Pay routes.
Post-VAMP (October 2025), acquirer relationships paired with Authorize.net for high-risk verticals tightened faster than domestic-low-risk pairings.
Merchants report acquirer-initiated notices even when Authorize.net's integration is stable — the gateway keeps working, but the underlying MID doesn't. Cycling through 2–3 paired acquirers per year became routine for high-risk operators using Authorize.net through 2024–2025.
- One rail, one relationship — no gateway/acquirer split.
- No AUP inheritance from Visa's prohibited list.
- No monthly gateway fee, no per-transaction gateway markup.
- Acquirer stability is not the constraint — there is no acquirer.
Questions operators ask about this comparison.
The cashier ships with a REST API and webhook model that maps cleanly onto Authorize.net's transaction lifecycle (auth, capture, void, refund). Most integrations migrate in under a week; the customer-facing checkout is the largest surface area to update.
Yes. Parallel-rail deployments are the common pattern. Route by geography, product line, or customer preference — the cashier is not exclusive.
The cashier tokenizes wallet-to-customer mappings via its own vault. Recurring payments run against tokenized wallet authorizations rather than tokenized card numbers, but the operational shape (one-click reorder, subscription flows) is the same.
$ decide --path forward