NMI vs Authorize.Net High-Risk Gateway Comparison

By E-commerce 4 Internet Marketers Editorial

Review. This article compares Network Merchants, Inc. (NMI) and Authorize.net as ecommerce payment gateways for website owners and developers who sell regulated or high-risk products and need specialty acquiring. The angle is feature breadth, partner and reseller paths, ACH and bank-payment rails, and how those choices interact with high-risk merchant underwriting. Facts below are attributed to NMI product, FAQ, Collect.js, Merchant Central, and Dwolla acquisition pages, plus Authorize.net Accept, eCheck, Automated Recurring Billing (ARB), reseller, and Support Center materials. This is not legal, underwriting, PCI, or fee advice. Neither vendor publishes a public guarantee that any named vertical will be approved, and this article never invents underwriting outcomes or fee schedules that are not published on the cited pages.

Facts. What each company is selling

NMI's homepage and payment gateway product page describe NMI as a white-label, embedded payments platform aimed at independent sales organizations (ISOs), software vendors, and similar channel partners. The gateway page states that partners can white-label the platform (logo, colors, custom URL), support online, in-store, self-service, and mobile payments, manage multiple merchant identification numbers (MIDs) on a single gateway account, and integrate with 200+ payment processors and 125+ shopping carts. NMI's FAQ repeats the over-200-processor and 125+ cart figures, and states that NMI is a gateway for most use cases, with NMI Payments as a separate acquiring option for partners who want a more integrated setup.

Authorize.net's homepage positions the product as a payments solution for businesses and partners, listing online payments that include credit and debit cards, eChecks, and digital wallets such as Apple Pay, Google Pay, and PayPal, plus Virtual Terminal, smartphone payments, and Simple Checkout buttons. Authorize.net is part of the Visa payments ecosystem through CyberSource. Visa's 2010 CyberSource acquisition announcement states that CyberSource included Authorize.net as a wholly owned subsidiary.

Facts. Features merchants and developers actually integrate

NMI documents Collect.js as a JavaScript library that tokenizes card and bank data in the browser and returns a payment_token for server-side Payment API calls. Collect.js documentation states that tokens cover credit and debit cards plus US and Canadian ACH bank fields, that tokens are single-use and expire after 24 hours, and that card, eCheck, Apple Pay, and Google Pay can support recurring and one-time flows when the processor allows it. The gateway product page also lists Customer Vault (token vault for repeat charges), Automatic Card Updater, recurring billing, webhooks, batch processing, Collect Checkout hosted pages, P2PE, and advanced fraud protection. NMI's FAQ describes network tokens with Customer Vault, Automatic Card Updater across processors, and fraud tools that include rule filters plus optional Kount-powered advanced screening.

Authorize.net's Accept documentation describes Accept.js, Accept.js with UI, Accept Hosted, Accept Customer, and Accept Mobile SDKs, and publishes a feature matrix with documented PCI self-assessment questionnaire (SAQ) pathways when products are used as described (for example SAQ A for Accept Hosted and Accept.js with UI, SAQ A-EP for Accept.js own form). Accept.js and Accept Hosted support payment card and, where listed, eCheck.Net. Authorize.net Automated Recurring Billing documents scheduled installment payments for payment card or eCheck.Net without the merchant storing sensitive payment data on its own servers, with subscriptions processed on a schedule (documented as approximately 2:00 a.m. Pacific Time on scheduled dates). Authorize.net also documents Customer Information Manager (customer profiles) for stored payment profiles charged on demand, and Advanced Fraud Detection Suite (AFDS) as a rules-based filter product covered in separate Support Center articles.

Facts. Partner, ISO, and reseller models

NMI's public materials emphasize a partner-first distribution model. The homepage and NMI Payments pages address ISOs and software companies that white-label payments, onboard merchants, and share payment revenue. Merchant Central (formerly IRIS CRM) is documented as a payments CRM for ISOs, banks, and software providers covering pipeline, onboarding, underwriting support, residuals, reporting, and a white-label merchant portal. NMI's FAQ states that NMI operates through a partner channel and does not directly onboard individual merchants as end users in the ordinary gateway model. Partners keep merchant accounts with processors that integrate with NMI, or use NMI Payments when they want acquiring bundled through NMI's partner program.

Authorize.net publishes a Become a reseller program that complements a partner's own merchant-account offering with the Authorize.net gateway. That page states there is no cost to become a partner, that Authorize.net delivers a competitive buy rate and the reseller sets sell pricing, that residuals are paid monthly on the difference, that Authorize.net handles merchant support and billing for the gateway, and that the reseller program offers the gateway solution and does not offer merchant accounts. Merchants who need a bundled merchant account plus gateway are directed to the reseller directory, which lists preferred resellers that combine a merchant account with Authorize.net. The directory entry for GatewayOnly states that GatewayOnly does not offer merchant accounts and is "processor neutral," so merchants can keep the Authorize.net gateway and switch processors.

Facts. ACH and bank payment rails

Authorize.net documents eCheck as its electronic check solution for customers with US bank accounts using Automated Clearing House (ACH) rails. The API uses createTransactionRequest with bank fields and echeckType values ARC, BOC, CCD, PPD, TEL, or WEB. Support Center article KA-04421 states that Account Owners apply for eCheck in the Merchant Interface, that underwriting can take from a few minutes up to about three business days when more review is needed, that funds are typically considered collected after a seven-day clearing phase, and that merchants must retain ACH authorizations. KA-04421 also quotes the eCheck service agreement language that Authorize.net may cancel eCheck services if a business is deemed high risk, and lists prohibited goods and services that include (among others) adult-oriented material, gambling, debt consolidation, outbound telemarketing, and other categories Authorize.net may determine to possess excessive risk.

NMI documents ACH collection in Collect.js for US and Canadian bank account fields, and states in its FAQ that ACH (eCheck) processing is supported through the Dwolla acquisition and through third-party ACH processor integrations, with a separate application and approval. On 19 May 2026, NMI announced it acquired Dwolla to add API-first account-to-account infrastructure, real-time payments, open banking, and many-to-many funds flow into NMI's white-labeled platform. NMI's FAQ Money Movement section describes Money Movement by Dwolla as supporting standard ACH, same-day ACH, and real-time rails for payouts, pay-ins, user-to-user transfers, and Me-to-Me flows for U.S.-registered businesses. A March 2021 NMI news post separately documents an iStream partnership to offer card and ACH on a single gateway platform for ISO and ISV partners.

Facts. High-risk relevance that is published, and what is not

Neither NMI nor Authorize.net publishes a public scorecard that says "this gateway always underwrites CBD, nutraceuticals, telehealth, firearms, or nicotine." Gateway choice still matters for high-risk stacks because specialty ISOs and acquirers often standardize on specific gateways, because multi-MID routing and processor flexibility affect how backup or split processing is engineered, and because ACH and wallet rails may be approved or denied on a product-by-product basis.

Published Authorize.net eCheck materials do state that high-risk determinations can cancel eCheck services and list prohibited categories in the agreement language quoted by KA-04421. That is a documented ACH-product constraint, not a statement about every Authorize.net card MID. NMI's published materials stress processor choice, multi-MID management, and partner-led underwriting through Merchant Central and connected processors, without publishing a matching public prohibited-vertical list for every ACH path in the pages cited here.

Interpretation. How high-risk teams usually weigh the choice

The following points are editorial interpretation grounded in the documented product and channel differences above. They are not vendor promises about any named merchant's approval, pricing, or reserve terms.

Interpretation. Merchants whose specialty acquirer or ISO already boards on NMI often get faster technical fit on multi-MID routing, white-label portals, and processor swaps without changing checkout tokenization. Merchants whose bank or preferred reseller already packages Authorize.net often get a simpler all-in path through the reseller directory, with Accept-hosted PCI pathways and mature ARB and customer-profile tooling.

Interpretation. Processor-agnostic gateway design is the practical reason many high-risk ISOs favor NMI when they need to move a merchant between acquiring banks while keeping vault tokens and cart integrations. Authorize.net can also sit in front of different processors through resellers and GatewayOnly-style setups, but the public reseller FAQ is explicit that the Authorize.net reseller program itself does not sell merchant accounts.

Interpretation. ACH strategy should be evaluated as a separate underwriting product. Authorize.net eCheck has a documented application path, ACH type matrix, funding and return behavior, and a published high-risk cancellation clause with prohibited categories. NMI ACH availability depends on Dwolla Money Movement enablement and/or third-party ACH processors attached to the gateway, which can be advantageous for bank payouts and account-to-account flows, but still requires its own approval.

Interpretation. For subscription and continuity brands common in supplements and telehealth, both platforms document recurring tools (NMI recurring billing plus Customer Vault and card updater, Authorize.net ARB plus customer profiles and Account Updater). The engineering difference is less "which one can bill monthly" and more which vault, updater, and decline-recovery path your ISO already operates in production.

Interpretation. Developers building custom regulated checkouts (age gates, license capture, FFL locators, consult-then-fulfillment splits) often care about browser tokenization control. Collect.js and Accept.js both keep card data off the merchant server when implemented as documented. Hosted options (Collect Checkout, Accept Hosted / Accept.js UI) trade design control for simpler PCI questionnaire pathways described by each vendor.

Practical comparison checklist for specialty merchants

Confirm which gateway your specialty ISO or acquirer already certifies and supports for your MCC and vertical. Ask whether card MID, ACH, and wallets are separate applications. Map checkout to Collect.js or Accept (hosted versus own-form) based on PCI questionnaire goals agreed with your QSA or acquirer. If you need backup MIDs, ask how multi-MID routing or processor changes affect vault tokens. If ACH is material to average ticket or recurring bank drafts, read Authorize.net eCheck rules and NMI/Dwolla ACH enablement requirements before promising bank-pay on the storefront. Treat published fee tables from unofficial blogs as unverified unless your reseller or partner quotes them in writing.

What this article omitted as unverified

Specific gateway monthly fees, per-transaction gateway fees, or ACH discount rates for either vendor (account-specific and often reseller-set). Any claim that NMI or Authorize.net will approve or decline a named high-risk vertical. Exact processor connection inventories beyond the "200+" / "125+ carts" figures NMI publishes and the reseller-directory processor relationships Authorize.net references without a full public matrix in the pages fetched for this review. Conversion-rate or authorization-rate percentages for either vault or network-token product. Guarantees about same-day ACH availability for every NMI merchant.

NMI vs Authorize.Net for High-Risk Ecommerce Gateways