NMI built one of the most recognizable partner-channel gateway brands in payments. For many ISOs and ISVs it has been the default choice for a decade, and we respect that history. Several Fluid Pay partners came to us from NMI portfolios. This page is for partners actively evaluating both platforms today and trying to make a defensible call.
A few things have changed in the last 12-18 months that materially shift the comparison:
- NMI now operates its own acquiring business and runs direct-to-merchant sales programs alongside its partner channel. The partner-only positioning that defined the brand for a decade no longer matches the structure of the business.
- NMI has raised partner-program pricing multiple times in recent months. Renewals and tier reviews have surfaced increases that several of our newest partners cited as a reason they started evaluating alternatives.
Fluid Pay's position is the opposite on both counts: we do not own an acquirer, we do not sell to merchants, and our partner pricing has held steady for years. Those are the two rows of the matrix that have moved most for partners in 2026, and they are why this conversation is happening.
The rest of this comparison covers the things partners actually ask us about on discovery calls: omnichannel coverage, residual ownership, fraud and recurring depth, and EMV device fleets.
| Capability | Fluid Pay | NMI |
|---|---|---|
| Non-compete commitment The trait competitors cannot match without restructuring the business. | Structural: Fluid Pay does not sell to merchants directly. Partner-only since 2017. We do not own an acquirer, we do not board merchants, and we have no plan to do either. | NMI now operates its own acquiring business and runs direct-to-merchant sales programs alongside its partner channel. There is no structural non-compete. |
| Deployment model | Cloud-native, multi-region, single API surface for CP and CNP. | Cloud gateway with broad omnichannel coverage; product surface is larger and more layered after years of M&A and the move into acquiring. |
| Omnichannel (CP + CNP) | Card-present, ecommerce, recurring, and vault on one stack and one dashboard. | Strong omnichannel via NMI Payment Gateway plus acquired terminal management and ecommerce stacks. |
| White-label / private label | Full white-label included: custom domain, logo, colors, hosted pages, branded merchant portal. | White-label is a foundational NMI value prop; configuration depth and portal customization vary by plan. |
| Processor relationships | Multiple processor connections. You keep your acquirer relationship and your residuals - we are not in the acquiring business. | Processor-agnostic for routing, but NMI now operates its own acquiring program. Partners share a vendor that is also a competing acquirer. |
| Residual ownership | Partner owns the merchant relationship and residual. Fluid Pay charges flat partner pricing that does not change as your portfolio grows. | Partner owns the merchant relationship; pricing is partner-negotiated. Recent partner-tier price increases have shown up in renewal cycles. |
| Pricing stability | Partner-negotiated pricing that has not changed in years. No per-feature unlocks for core gateway capabilities; we work collaboratively with partners on pricing rather than push periodic rate adjustments. | Pricing is partner-negotiated. Multiple partner-program rate increases have been pushed through over the last several months. |
| Vault & tokenization portability | Network tokens supported. Vault export available to your acquirer or backup gateway on request. | Customer Vault with network token support; export terms are partner-program-specific. |
| Recurring & subscription engine | Native subscription engine with retry logic, dunning, smart card updater, and partner reporting. | Recurring billing module included; subscription depth depends on plan and integrations. |
| Fraud (Watchdog / Kount-class) | Watchdog fraud module included with rules, velocity, BIN/IP intelligence, and 3DS routing. | iSpyFraud rules engine plus Kount integration; Kount has additional cost. |
| Surcharging / dual pricing | Compliant surcharging and dual pricing built into the gateway, no third-party module required. | Surcharging available via partner integrations; configuration varies. |
| EMV / device support | Cloud EMV with curated device list (PAX, Ingenico, Dejavoo); branded TMS for partners. | Broad terminal coverage including Creditcall (acquired) and partner SDKs across many device families. |
| API & webhook breadth | REST + JSON, idempotency keys, signed webhooks with retry, full sandbox parity. | Long-standing Direct Post / Three-Step Redirect / QuickClick APIs; XML and form-post heritage alongside newer surfaces. |
| Sandbox & developer docs | Public sandbox with full API parity; docs at sandbox.fluidpay.com/docs. | Test account on request; documentation portal is partner-account gated for portions. |
| Support model | Direct partner support with named integration engineer during onboarding. | Tiered support based on partner program and volume. |
- Non-compete commitment
The trait competitors cannot match without restructuring the business.
Fluid PayStructural: Fluid Pay does not sell to merchants directly. Partner-only since 2017. We do not own an acquirer, we do not board merchants, and we have no plan to do either.NMINMI now operates its own acquiring business and runs direct-to-merchant sales programs alongside its partner channel. There is no structural non-compete. - Deployment modelFluid PayCloud-native, multi-region, single API surface for CP and CNP.NMICloud gateway with broad omnichannel coverage; product surface is larger and more layered after years of M&A and the move into acquiring.
- Omnichannel (CP + CNP)Fluid PayCard-present, ecommerce, recurring, and vault on one stack and one dashboard.NMIStrong omnichannel via NMI Payment Gateway plus acquired terminal management and ecommerce stacks.
- White-label / private labelFluid PayFull white-label included: custom domain, logo, colors, hosted pages, branded merchant portal.NMIWhite-label is a foundational NMI value prop; configuration depth and portal customization vary by plan.
- Processor relationshipsFluid PayMultiple processor connections. You keep your acquirer relationship and your residuals - we are not in the acquiring business.NMIProcessor-agnostic for routing, but NMI now operates its own acquiring program. Partners share a vendor that is also a competing acquirer.
- Residual ownershipFluid PayPartner owns the merchant relationship and residual. Fluid Pay charges flat partner pricing that does not change as your portfolio grows.NMIPartner owns the merchant relationship; pricing is partner-negotiated. Recent partner-tier price increases have shown up in renewal cycles.
- Pricing stabilityFluid PayPartner-negotiated pricing that has not changed in years. No per-feature unlocks for core gateway capabilities; we work collaboratively with partners on pricing rather than push periodic rate adjustments.NMIPricing is partner-negotiated. Multiple partner-program rate increases have been pushed through over the last several months.
- Vault & tokenization portabilityFluid PayNetwork tokens supported. Vault export available to your acquirer or backup gateway on request.NMICustomer Vault with network token support; export terms are partner-program-specific.
- Recurring & subscription engineFluid PayNative subscription engine with retry logic, dunning, smart card updater, and partner reporting.NMIRecurring billing module included; subscription depth depends on plan and integrations.
- Fraud (Watchdog / Kount-class)Fluid PayWatchdog fraud module included with rules, velocity, BIN/IP intelligence, and 3DS routing.NMIiSpyFraud rules engine plus Kount integration; Kount has additional cost.
- Surcharging / dual pricingFluid PayCompliant surcharging and dual pricing built into the gateway, no third-party module required.NMISurcharging available via partner integrations; configuration varies.
- EMV / device supportFluid PayCloud EMV with curated device list (PAX, Ingenico, Dejavoo); branded TMS for partners.NMIBroad terminal coverage including Creditcall (acquired) and partner SDKs across many device families.
- API & webhook breadthFluid PayREST + JSON, idempotency keys, signed webhooks with retry, full sandbox parity.NMILong-standing Direct Post / Three-Step Redirect / QuickClick APIs; XML and form-post heritage alongside newer surfaces.
- Sandbox & developer docsFluid PayPublic sandbox with full API parity; docs at sandbox.fluidpay.com/docs.NMITest account on request; documentation portal is partner-account gated for portions.
- Support modelFluid PayDirect partner support with named integration engineer during onboarding.NMITiered support based on partner program and volume.
Comparison reflects publicly available product information as of 2026-05-06. Capabilities and pricing may change; verify with each provider before procurement.
Where Fluid Pay is the right pick
Fluid Pay is the cleaner choice when structural non-compete actually matters to your board, your investors, or your sales team. NMI's move into acquiring puts every NMI partner one boardroom decision away from sharing underwriting and merchant data with a vendor that is also competing for the same accounts. Fluid Pay is not in the acquiring business and is not going to be. That is a deliberate, durable structural choice, not a slogan.
Fluid Pay is also the right pick when you want price stability you can forecast. We do not publish a public rate card - partner pricing is negotiated and kept private, the same way most gateways handle it - but our partner pricing has held steady for years. We do not have a contractual multi-year price lock; we simply work collaboratively with our partners and stand by the pricing model we agree to. Several partners we onboarded in the last quarter came to us specifically because their NMI tier review surfaced a rate increase they could not pass through to merchants without churn risk.
Pick Fluid Pay when you want modern REST and JSON everywhere - signed webhooks with retry, idempotency keys, and full sandbox parity from day one. Partners migrating from older Direct Post or Three-Step Redirect integrations consistently report fewer engineering surprises with our single API surface.
The fourth reason partners pick us is bundled capabilities. Surcharging, dual pricing, Watchdog fraud, the recurring engine with smart card updater, and the white-label merchant portal are all included in partner pricing. You do not unlock features one at a time as the merchant book grows.
Finally, partners pick Fluid Pay when they want a smaller, more curated EMV device list with a branded terminal management system. PAX, Ingenico, and Dejavoo families cover the dominant retail and restaurant use cases without the long tail of legacy device certifications that comes with broader gateway portfolios.
Where NMI is the right pick
If you already have deep, multi-year NMI integrations across the gateway, terminal management, and recurring stacks, and the alignment risk does not yet outweigh the switching cost in your specific situation, NMI is still a working gateway. The honest read is that this calculus has tightened sharply with the move into acquiring; many partners we talk to now conclude the opposite within a quarter, but every portfolio is different.
NMI is also the right pick when your team depends on a specific legacy API contract - QuickClick or a particular Direct Post field convention - that your roadmap can't justify refactoring right now. We would rather tell you that honestly than discover it after the fact.
Pricing and total cost of ownership
Neither Fluid Pay nor NMI publishes a public partner rate card, and that is the honest baseline for the comparison. The differences are in what is included and in what happens to your pricing over time.
Fluid Pay's partner pricing covers the gateway, white-label portal, recurring engine, vault, Watchdog fraud, surcharging and dual pricing, and partner-level reporting in a single quote - your team is not unlocking core gateway capabilities a feature at a time as your book grows. We do not have a contractual multi-year price lock in place, but our partner pricing has not changed in years. We work collaboratively with partners on pricing and stand by the model we agree to.
NMI's pricing is partner-program-specific and negotiated privately, and has moved upward in multiple recent partner-program adjustments. That is the single most-cited reason partners contacted us in the last quarter. When you request quotes from both vendors, normalize the comparison by asking each side to break out:
- Per-transaction gateway fee (CP and CNP separately)
- Monthly partner minimums and volume tiers
- Vault and tokenization fees, including network token usage
- Recurring billing - per-subscription vs per-transaction
- Surcharging and dual pricing - included or add-on
- 3DS, fraud, and chargeback tooling - included or add-on
- Terminal management, key injection, and per-device fees
- Any acquirer-tied bundles or pricing dependencies
- Sandbox, dev account, and certification costs
- Onboarding and one-time integration assistance fees
It is common for a "headline" rate to look attractive until bundled capabilities are itemized in. Insist on the breakout, and ask each vendor about their actual pricing track record over the last 24 months.
You want a gateway whose business model is structurally aligned with your portfolio - one that does not own an acquirer, does not sell to merchants, and has held its partner pricing steady year after year. Plus a single modern REST surface for CP and CNP, native surcharging, and Watchdog fraud included.
You already have deep NMI integrations across multiple acquired stacks and the switching cost outweighs the alignment win, you depend on a specific NMI-only legacy API contract, or your current NMI partner-program pricing is locked in for long enough that the most recent rate increases do not yet apply to your book.
Frequently asked questions
Is Fluid Pay a payment gateway or a payment processor?
Fluid Pay is a payment gateway and partner-first payments platform. We do not own an acquirer and we do not sell to merchants directly. Partners bring or keep their acquirer relationship; we provide the rails, the white-label experience, and the engineering.
Does NMI compete with its partners?
NMI now operates its own acquiring business and runs direct-to-merchant sales programs alongside its partner channel. That means partners share a vendor that is also a competing acquirer in many of the same accounts. NMI is still a real partner-channel provider, but the structural alignment is no longer the same as a partner-only gateway. Confirm current terms with NMI directly.
Has NMI raised partner pricing recently?
Multiple partner-program rate adjustments have been pushed through over the last several months, surfacing on partner renewals and certain transaction-tier reviews. Fluid Pay quotes partner pricing privately, like NMI, but our partner pricing has held steady for years - we work collaboratively with partners on pricing rather than push periodic rate increases.
Can I keep my existing acquirer if I move to Fluid Pay?
Yes. Fluid Pay is processor-agnostic, supports multiple acquirer connections, and is not in the acquiring business itself. You keep your acquirer relationship, your residual structure, and the merchant relationship - we are not the acquirer of your portfolio and we never will be.
Does Fluid Pay support surcharging and dual pricing without an add-on?
Yes. Compliant surcharging and dual pricing are native to the gateway and included in standard partner pricing - no third-party module, no per-feature unlock.
What about fraud tooling - do I need a separate Kount contract?
Fluid Pay's Watchdog module includes rules, velocity controls, BIN/IP intelligence, and 3DS routing without a separate Kount-style add-on. Partners with extreme-volume or vertical-specific fraud needs can still bring third-party tooling.
Talk to a partner specialist
Get a Fluid Pay walkthrough side-by-side against Network Merchants, Inc. (NMI) for your specific portfolio, processor relationships, and migration timeline.