multiflow vs. NMI Gateway

A gateway sits between the ecommerce checkout and the acquirer. When a customer submits payment, the checkout sends card data (or a tokenized form) to the gateway; the gateway handles encryption, fraud scoring, authentication (3DS), vault storage for recurring charges, and forwards the authorization request to the acquiring bank. NMI is one of the dominant gateways for mid-market and high-risk merchants. It is commonly paired with vertical-specialized acquirers for nutra, peptides, CBD, fantasy sports, and adult-content verticals where Stripe and Braintree won't board merchants.

NMI's differentiation from Authorize.net (its biggest gateway peer): stronger fraud scoring, multi-gateway smart routing (automatic failover between acquirers if one declines or goes down), and broader high-risk compatibility. If your ISO placed you on NMI, the placement was deliberate — NMI was chosen because your vertical's compatibility needs matched NMI's tooling.

Fraud scoring at the gateway layer. iSpyFraud and Kount integration run before the transaction reaches the acquirer, catching fraud attempts early. For high-volume high-risk merchants, gateway-level fraud scoring is a meaningful fraud-loss reducer.

Multi-acquirer smart routing. Operators who want failover between acquirers (if acquirer A declines, retry at acquirer B) get it natively from NMI. This is a gateway-layer capability.

Customer vault (CIM / Customer Information Manager) is mature. NMI's vault handles recurring billing, card-on-file updates, subscription management at scale. Works for most volume operators without customization.

Developer ergonomics are solid. NMI's direct-post API and iframe integration are well-documented and stable. Not as modern as Stripe's SDK, but reliable.

NMI's reporting is per-merchant-account. If you run four sub-brands under four NMI-integrated merchant accounts, you have four reporting dashboards. Cross-brand reporting is manual CSV export + VLOOKUP.

NMI's chargeback management is per-account. Four sub-brands = four chargeback queues. Operations staff log into four systems daily.

NMI's descriptor handling is per-transaction API config. Setting per-brand descriptors across four merchant accounts means four custom integrations, four testing cycles, four maintenance points of failure.

multiflow takes NMI's strengths (gateway, fraud scoring, vault, smart routing) and adds a parent-level orchestration layer: one parent merchant account under which all sub-brands run with clean soft descriptors; consolidated reporting across the portfolio; one chargeback queue with sub-brand context; one descriptor configuration layer. NMI stays where it is; multiflow adds what NMI doesn't handle natively.

At transaction time: checkout → NMI gateway → NMI fraud scoring → acquirer (via multiflow-placed parent merchant account) → network.

At reporting time: NMI captures transaction data per account; multiflow pulls the consolidated view across all your NMI-integrated merchant accounts into one dashboard.

At dispute time: NMI's chargeback feed flows through to multiflow's unified queue, with sub-brand context added.

Existing NMI configuration stays. Existing NMI fraud rules keep firing. Existing NMI vault stays active. multiflow adds orchestration; it doesn't modify NMI's gateway behavior.

If you run one brand, one merchant account, under one NMI gateway, you don't need multiflow. NMI's native tooling handles single-brand operators well. Come back when brand #3 launches.

If your internal team has built custom multi-brand tooling on top of NMI and it works, you also don't need us. Maintenance cost is the question — whose job is it when the custom scripts break, and what's the opportunity cost of that person's time.

If you're starting fresh and NMI hasn't been deployed yet, you have a choice: NMI (gateway) + multiflow (orchestration at parent), or Stripe (gateway + processor) + multiflow. Depends on your vertical's PayFac compatibility.

Day 0–2: multiflow underwriting at a compatible acquirer. Existing NMI relationship stays untouched.

Day 3: parent merchant account wired in; multiflow orchestration layer configured against your NMI account.

Day 4–5: first sub-brand routed through orchestrated parent. NMI gateway still handling card-data transport; acquirer relationship now consolidated. Live charges clear; descriptor confirmed.

Day 6–10: remaining sub-brands batched in. Consolidated reporting live. Chargeback queue unified. NMI fraud rules unchanged.

Day 11+: business as usual, minus three chargeback dashboards and plus one consolidated ledger.

If NMI is your gateway and you run 3+ brands: stack multiflow on top. They complement. If you run one brand on NMI and reconciliation fits in your head: stay on NMI alone, don't add unnecessary complexity.