NMI review

NMI is an embedded-payments platform: a vendor-operated set of payment and merchant-management products that ISOs and software vendors can offer to their own customers. It is not presented as a standalone open-source library or a command-line tool. Its product set includes Payments, a white-label Payment Gateway, and Merchant Central, which combines CRM and underwriting tools.

In a software stack, NMI sits between a partner's product and payment processing, with merchant onboarding and management alongside payment acceptance. The homepage describes support for card, bank, and real-time payment rails. Partners can use the platform to qualify, acquire, and onboard merchants, then manage merchant lifecycles. NMI positions its products as modular, so a buyer should establish which components fit its architecture rather than assume every product is required. The vendor also reports more than 150 processor connections, but that count does not establish availability for a particular merchant, region, or integration.

NMI's homepage names product-level integration surfaces: its Payments solution, white-label Payment Gateway, and Merchant Central. These cover payment acceptance and merchant workflows, but the vendor doesn't publish an API protocol, SDK languages, CLI, or webhook details on the homepage. The site also does not identify a specific plugin or framework integration.

Before implementation, ask NMI for its API reference, supported SDKs and languages, authentication model, sandbox access, webhook events, and versioning policy. Confirm how the gateway connects to your checkout, how merchant onboarding data moves into your systems, and whether Merchant Central can exchange the records your operations team needs. The homepage presents the products as modular and integrated, but that alone is not enough to estimate engineering effort. Review the vendor's technical documentation and confirm SDK support for your stack before choosing an integration path.

The pricing page doesn't publish plan prices or monthly versus annual billing terms. The current pricing record lists no free plan, and trial terms are unknown. There is no published starting price to use for an initial budget.

That leaves the main production cost drivers unanswered: transaction fees, gateway fees, processor charges, merchant or device fees, and any minimums or contract terms. The vendor also does not publish usage bands, overage rates, or add-on prices in the pricing information available to buyers. NMI's platform is designed for payment providers and software vendors that may share in net payment revenue, but that does not establish the partner's margin or the costs passed through to merchants.

Ask for a written quote based on expected volume, payment methods, processor connections, merchant count, and required products. Confirm billing frequency, minimum commitments, termination costs, and whether support, onboarding, and compliance services are separate charges. Without those figures, comparing NMI's value with a per-transaction or usage-priced alternative is difficult.

NMI is presented as a vendor-operated payments platform, not a self-hostable server or open-source library. The vendor doesn't publish a source licence or self-hosting option, so teams should not plan to run the gateway in their own environment without written confirmation.

Data export and portability terms also need to be confirmed in contract and technical documentation. Ask which merchant, transaction, and configuration data can be exported, in what formats, and whether payment credentials can move to another provider. Payment credentials and processor-specific setup can make a migration more involved than replacing an application dependency; the exact path depends on NMI's data and token portability terms. Confirm ownership of merchant relationships and residuals, export access after termination, and any transition assistance before routing production payments through the platform.

The homepage describes the white-label gateway as secure and says the platform supports card, bank, and real-time payment rails. Those claims do not replace a production review. Ask NMI for its service-level commitments, incident history, support escalation path, maintenance policy, and recovery procedures. The vendor's homepage reports more than 150 processor connections and 300-plus EMV device certifications; confirm that the specific processor and devices your deployment needs are supported.

The vendor doesn't publish request limits, rate limits, or plan-based capacity figures in its pricing information, so get those limits and any throttling behavior in writing. Confirm sandbox and certification steps, transaction reconciliation, webhook or event delivery behavior, retries, idempotency, and handling of processor outages. Review security and compliance responsibilities across NMI, your software, and each processor. Before launch, test failure paths and settlement workflows in the agreed environment, and establish how you will export operational and merchant data if you later move providers.