NMI

NMI is an embedded-payments platform for ISOs, software companies, and payment facilitators building payment acceptance into services for merchants. It suits partners that want branded checkout across several sales channels, but merchants generally need a certified reseller or ISO to configure the gateway and manage the account.

Overview

NMI combines payment acceptance, checkout tools, developer resources, and merchant-management capabilities for online, in-store, mobile, and self-service payments. Its gateway has been part of its payments offering since 2001. The partner-oriented model gives businesses room to shape the merchant experience, but makes NMI a less direct fit for a merchant seeking a standalone, self-serve payment app.

Key features

Checkout and payment operations

The gateway supports recurring billing, batch processing, webhooks, transaction routing, a virtual terminal, and QR-code payment links. It handles EMV and contactless payments as well as online, in-store, mobile, and self-service transactions. Checkout choices span hosted payment pages, a customizable Payment Component, and a REST API for custom experiences. This range can serve partners with merchants operating across channels; custom API checkout is better suited to teams able to build and maintain an integration.

The Payment Component tokenizes payment details in the browser, keeping sensitive payment data off the integrator’s servers. NMI also offers SDKs for iOS, Android, Windows, and Linux, plus a browser-based customer-present solution that works across operating systems. This is useful flexibility for software providers supporting varied devices, though it does not remove the work of integrating and operating a payment flow.

Partner and merchant tools

Partners can apply their logos, colors, and custom URLs to the gateway and portals. Merchant Central brings CRM and underwriting tools together to support merchant onboarding and ongoing account management. That combination is most relevant to businesses building a payments program, rather than merchants who only need to accept transactions.

NMI says the gateway supports major card brands, Apple Pay, and Google Pay, with USD, CAD, and other currencies depending on the processor. It connects to more than 200 payment processors and 125+ shopping carts. Bill Connect links payment acceptance with accounting software such as QuickBooks and Xero. However, NMI says integrations documented for third-party products are not developed, maintained, or supported by NMI, so partners should account for that boundary when relying on them.

Security and support

NMI says it has maintained PCI DSS Level 1 certification since 2005 and undergoes annual independent security assessments. Gateway security options include point-to-point encryption, remote key injection, and remote terminal management. A key caveat is that merchants using the Payment API should have passed a PCI vulnerability scan before using that integration method; teams should factor that requirement into implementation planning. NMI provides a support portal for searching answers, submitting requests, and tracking open requests.

Pricing

NMI is paid software with custom pricing: prospective partners need to contact sales rather than compare a published standard rate. That makes budgeting less immediate than with a public per-month or per-transaction price. No plan tiers, seat limits, trial period, or renewal terms are stated.

Platforms

NMI supports Android, iOS, Linux, Windows, web, and API use. Its platform-specific SDKs and browser-based customer-present option give developers several ways to serve different devices and operating systems.

Who it's for

NMI is best suited to ISOs, software companies, and payment facilitators that want to embed and brand payments, manage merchant relationships, and support a mix of online and physical channels. Merchants can benefit from the gateway’s payment and checkout options, but typically access them through a certified reseller or ISO. Businesses wanting a direct merchant account without a partner relationship should look elsewhere.

Pros and cons

• Pros: White labeling and Merchant Central let partners shape the merchant-facing experience and manage onboarding in one platform.
• Pros: Multiple checkout methods, payment channels, and developer SDKs support varied merchant and device needs.
• Pros: Processor and shopping-cart integrations, along with recurring billing and marketplace payments, give partners flexibility in building payment services.
• Cons: Merchants generally depend on a certified reseller or ISO to configure the gateway and handle the account.
• Cons: Pricing is custom, so buyers cannot assess a standard rate before contacting sales.
• Cons: Payment API users face a PCI vulnerability scan requirement, and NMI does not support the third-party integrations in its documentation.

Alternatives

For a wider view of the category, compare Embedded Payments Platforms, Virtual Terminal Software, and Payment Gateways.

• Checkout.com may suit charities seeking free payment processing in the countries where it operates; its other pricing is tailored.
• Stripe Connect is worth considering when a platform wants no platform fees and Stripe to set and collect connected-account processing fees.
• PayPal Multiparty Payments is an alternative for businesses prepared to seek platform or marketplace approval.
• Flute Embedded Payments offers partner pricing based on revenue share from processing fees, with terms to discuss by quote.
• Stax Connect is another option for buyers willing to contact sales for pricing.
• DreamPay is another paid option for web, iOS, and Android.
• J.P. Morgan Embedded Payments is an API-focused alternative for businesses contacting J.P. Morgan to begin integration.
• WePay is another paid option for web, iOS, and Android.

Verdict

Choose NMI if you are a payments partner that needs branded checkout, broad channel support, and tools to manage merchants alongside payment integrations. Its partner-oriented breadth is the main draw; custom pricing, reseller dependence for merchants, and the Payment API scan requirement are reasons to look elsewhere if you need a direct, simpler route to payment acceptance.