Payment gateway (card data transport)
multiflow
Compatible — works with NMI
NMI
Full-featured gateway
Honest comparison
NMI (Network Merchants Inc) is a payment gateway that pairs with acquirers to deliver full-stack processing — similar category as Authorize.net, often picked specifically because NMI's fraud scoring and high-risk tooling is more aggressive. If you're on NMI, you're probably in a higher-risk vertical. multiflow doesn't replace NMI; we orchestrate above it when your portfolio is 3+ brands.
| Feature | multiflow | NMI |
|---|---|---|
| Payment gateway (card data transport) | Compatible — works with NMI | Full-featured gateway |
| High-risk vertical tooling | Orchestration at parent | Strong at gateway level |
| Per-brand descriptors (multi-brand) | Automatic | Per-transaction API config |
| Cross-brand consolidated reporting | Native | Per-account only |
| Native CRM + vault | Compatible | Strong customer vault |
| Fraud scoring (iSpyFraud, Kount integration) | Complementary | Native integration |
| Multi-gateway smart routing | Native across acquirers | Native via NMI |
| Consolidated chargeback queue | All brands in one view | Per-merchant view |
| Apple Pay / Google Pay per brand | Automatic | Manual per-account |
| Subscription engine | Compatible | Native recurring |
| Developer API | Routes above NMI API | Mature REST + direct post |
| Multi-brand operator overhead reduction | Core value prop | Not its design |
NMI has built a strong position as the go-to gateway for operators whose risk profile exceeds Authorize.net's comfort zone. NMI's fraud scoring (iSpyFraud, Kount integration), multi-gateway smart routing, and partner ecosystem skew toward high-risk verticals — nutra, peptides, CBD, vape, fantasy sports. If you're on NMI, your ISO likely placed you there deliberately.
Gateway-level fraud scoring is strong. Multi-gateway smart routing lets you fail over between acquirers if one goes down. CRM + vault product is solid. For a single-brand high-risk operator, NMI + a vertical-specialized acquirer is often the best full-stack setup available.
Multi-brand orchestration NMI doesn't handle natively.
Multi-brand orchestration NMI doesn't handle natively. Per-brand descriptors across a portfolio of 4+ brands means writing 4 custom integrations to NMI's API. multiflow sets descriptors at the parent level so every charge inherits the right brand.
Cross-brand ledger consolidation is not an NMI gateway function. Their reporting is per-account. multiflow's consolidated view pulls from every sub-brand into one dashboard.
Consolidated chargeback queue across brands: one queue vs N queues when running 4 merchant accounts.
Some NMI operators have built custom portfolio-management tooling in-house — scripts pulling from multiple NMI accounts, Airbyte/Fivetran ETL, internal BI dashboards. If that's you and the tooling works, you don't necessarily need multiflow. The decision point is maintenance cost: whose job is it when the tooling breaks, and what's the opportunity cost of that person's time.
Day 0–2 multiflow underwriting. Day 3 parent account wired in via NMI API. Day 4–5 first sub-brand live with per-brand descriptor confirmed. Day 6–10 rest batched. NMI gateway relationship stays identical. Acquirer relationship stays identical.
Stay on NMI. Layer multiflow on top if your portfolio is 3+ brands and cross-brand orchestration is the pain. They stack, they don't compete.
Single-brand high-risk operators running NMI + a vertical-specialized acquirer don't need multiflow. NMI's native tooling covers the job.
If your internal team has already built custom multi-brand tooling on top of NMI and it works, stick with it. multiflow doesn't justify replacing working infrastructure.
FAQ
One ledger, per-brand descriptors, consolidated dispute queue. Apply in 12 questions — no hard pull.
Start your applicationParent ledger, sub-brand routing, per-brand descriptors, payout fan-out — the mechanics behind the comparison.
How it worksTalk to an operator
Human reply within 2 business hours. No chatbot.