HEAD TO HEAD
NMI vs USAePay: one owner, two different products
NMI acquired USAePay in February 2021, but the two gateways were built two decades apart for slightly different jobs, and both still operate as distinct platforms with distinct consoles. Here's how they line up for a partner deciding where to place new merchant volume.
| Category | NMI | USAePay |
|---|---|---|
| Acquirer / processor flexibility | A 200+ certified connections, processor-agnostic by design | B Long-standing certifications (TSYS, Global Payments, Worldpay, EPX) via a narrower, curated list |
| White-label depth | A Full rebrand for ISOs, ISVs, and banks | A Reseller console purpose-built around channel partners |
| Developer tooling / APIs | B Modern SDKs and hosted-fields options, steeper initial integration | B Mature, long-documented API and developer center |
| Fit for a single small merchant | C Built for partners first; direct-merchant experience depends on the reseller | B Reseller console historically more merchant-management-friendly |
| Onboarding speed (direct) | C Partner-mediated underwriting, not same-day self-serve | B Faster where the reseller has streamlined onboarding |
| Omnichannel / device coverage | A Broad EMV and unattended-device certification list | B Solid retail, mobile, and MOTO coverage |
Where they overlap
Both platforms are gateways, not payment facilitators: neither underwrites merchants or holds a master merchant account the way Stripe or Square does. Both sell almost entirely through a partner channel — ISOs, ISVs, and resellers — rather than direct self-serve signup, and both set pricing at the partner level rather than publishing one flat rate. And since 2021, both sit under the same parent company, which has meant closer infrastructure alignment over time even as the two brands and consoles stay separate.
Where they diverge
NMI's pitch is acquirer breadth: 200+ processor connections built explicitly so a partner isn't locked into one backend. USAePay's history is more about the reseller relationship itself — a console and support model built up over 25+ years of working with the same channel partners, with a narrower but deeply certified processor list. In practice, an ISV building new embedded-payments infrastructure from scratch tends to lean toward NMI's flexibility; an ISO or reseller with an established merchant book already running on USAePay usually has little reason to migrate.
How to decide
- Building new, need acquirer choice: NMI's processor-agnostic model gives more room to negotiate acquiring terms later.
- Already on USAePay with a working reseller relationship: the acquisition doesn't force a migration; evaluate switching costs before moving.
- Evaluating both from zero: ask each about buy rates, revenue share, and which specific acquirers are certified for your vertical — see our pricing guide and gateway selection guide.