USAePay is a payment gateway owned by NMI, which acquired it in 2020. It offers five integration methods — a modern REST API, a legacy SOAP API, the client-side Pay.js library, a Payment Engine Terminal API, and a Transaction API — and is the platform CARDZ3N uses for merchant boarding.

Is USAePay different from NMI?

USAePay is an NMI-owned brand, part of the same corporate family since NMI's 2020 acquisition, but it operates as a distinct platform with its own developer portal and API. It's not a rebrand of NMI's gateway — the two remain operationally separate even while sharing ownership.

What is USAePay used for in CARDZ3N's process?

CARDZ3N boards merchants on USAePay specifically. It is not the primary gateway for day-to-day processing — that preference order is FluidPay first, then NMI — but it plays a foundational role in getting a new merchant account set up within CARDZ3N's stack.

Does USAePay have a REST API?

Yes. USAePay's REST API is organized by resource, with separate endpoints for transactions, tokens, batches, customers, payment methods, recurring schedules, products, and inventory, plus dedicated PHP, .NET, and Python guides — a more granular design than a single request-driven endpoint.

What fraud protection does USAePay offer?

USAePay's documented fraud tools run through Threat Metrix — a different vendor than the Kount-based tools referenced in NMI's own compliance material — alongside end-to-end encryption and AVS/CVV checks.

Does CARDZ3N sell USAePay directly?

No. CARDZ3N is always the quoting and selling party — every USAePay account used for merchant boarding is configured, quoted, and supported through CARDZ3N, the same as every other service and terminal CARDZ3N provides.

USAePay Payment Gateway Integration

On this page

What Is USAePay

USAePay's Role in the Stack

A Developer-Friendly API

Fraud Tools and Brand Status

USAePay at a Glance

Frequently Asked Questions

USAePay Payment Gateway

“

USAePay is a payment gateway owned by NMI — NMI acquired USAePay in 2020, and it remains an operationally distinct platform inside the same corporate family. CARDZ3N boards merchants on USAePay specifically; for the core gateway relationship the preference order is FluidPay first, then NMI. Every USAePay account a CARDZ3N merchant runs is quoted and sold through CARDZ3N — never USAePay or NMI directly.

USAePay's Role in the CARDZ3N Stack

USAePay is not CARDZ3N's primary gateway for the core processing relationship — that preference order is FluidPay first, then NMI. USAePay's role is specifically merchant boarding: it's the platform CARDZ3N uses to get new merchant accounts set up and configured within its stack. That makes USAePay a foundational, behind-the-scenes part of how a merchant gets onboarded, distinct from the gateway that ultimately handles day-to-day transaction processing.

USAePay shares a corporate family with NMI, the gateway CARDZ3N already offers as part of its own lineup — both are part of the same acquisition history, with Ben Goretsky listed as Head of USAePay in NMI's own corporate materials. That shared ownership is part of why USAePay integrates cleanly into CARDZ3N's boarding process rather than sitting off to the side as an unrelated third-party tool.

A Developer-Friendly, Resource-Based API

USAePay offers five integration methods: a modern REST API, a legacy SOAP API (v1.7), the client-side Pay.js library, a dedicated Payment Engine Terminal API, and a low-level Transaction API. The REST API is organized as separate, per-resource endpoints — /transactions, /tokens, /batches, /customers, /methods, /schedules, /products, and /inventory — with dedicated language guides for PHP, .NET, and Python.

That per-resource design is notably more granular than either NMI's classic gateway API or Authorize.net's single request-driven endpoint, which handles every transaction type through one unified URL. USAePay's structure makes it easier for a development team to reason about a specific resource — tokens, batches, or recurring schedules — without routing every request type through the same generic call.

Despite being NMI's oldest acquisition, USAePay is the most RESTful gateway in the CARDZ3N-affiliated stack — its per-resource API design outpaces both NMI's own classic API and Authorize.net's single-endpoint approach.

Fraud Tools and Brand Status

USAePay's documented fraud tools run through Threat Metrix, a different vendor than the Kount-based fraud tooling NMI's own VAMP compliance material references. Alongside Threat Metrix, USAePay documents end-to-end encryption, AVS/CVV checks, and a dedicated sandbox environment with test credentials for building and validating fraud-handling logic before going live.

USAePay's public marketing brand has been folded into NMI's main site — usaepay.com now redirects straight to nmi.com, and NMI's own homepage doesn't mention USAePay by name. The developer documentation portal at help.usaepay.info, however, remains separately live and actively maintained, which is the resource CARDZ3N's own integration work draws on. USAePay's consumer-facing identity has been absorbed into NMI, but it persists as an operationally distinct platform CARDZ3N actually uses for boarding.

USAePay at a Glance

The technical detail that matters most for merchants and developers evaluating USAePay through CARDZ3N:

✓
Five integration methods: REST API, SOAP API, Pay.js, Payment Engine Terminal API, and Transaction API
✓
NMI-owned gateway brand, acquired in 2020, sharing NMI's corporate family
✓
Per-resource REST endpoints for transactions, tokens, batches, customers, methods, schedules, products, and inventory
✓
Used by CARDZ3N specifically for merchant boarding within its processing stack

Frequently Asked Questions

Common questions merchants and developers ask about USAePay's role in CARDZ3N's processing setup.

USAePay Gateway Features for Merchant Boarding and Developer Integration

Who Uses USAePay Through CARDZ3N

USAePay Payment Gateway

USAePay's Role in the CARDZ3N Stack

A Developer-Friendly, Resource-Based API

Fraud Tools and Brand Status

USAePay at a Glance

Frequently Asked Questions

Ready to Sign Up?

Pages

Follow