Free sub-merchant fit check — parent MID eligibility tool

(function(){ var qs = [ {id:"q1", text:"How many active brands do you operate?", opts:[["1","1 brand",-2],["2-4","2-4 brands",1],["5-10","5-10 brands",3],["10+","10+ brands",4]]}, {id:"q2", text:"Combined monthly processing volume", opts:[["lt50","Under $50k",-1],["50-500","$50-500k",2],["500-2m","$500k-2M",3],["gt2m","Over $2M",3]]}, {id:"q3", text:"Primary vertical", opts:[["lowrisk","Low-risk ecommerce",1],["midrisk","Supplements / nutra",3],["highrisk","CBD / peptides / adult",4],["saas","SaaS / digital goods",0]]}, {id:"q4", text:"Do your brands share common operator/entity?", opts:[["same","Same entity, different DBAs",3],["shared","Shared holding company",2],["separate","Fully separate LLCs",1]]}, {id:"q5", text:"Current processor situation", opts:[["happy","Happy with current processors",-2],["issues","Some brands frozen / under-pricing",3],["shopping","Actively shopping",3]]}, {id:"q6", text:"Reserve burden", opts:[["none","No reserves",0],["some","Some brands have 5-10% reserve",2],["heavy","Heavy reserves across brands",4]]}, {id:"q7", text:"Finance team size", opts:[["solo","Solo operator / 1 bookkeeper",2],["small","2-3 finance staff",2],["larger","4+ finance staff",1]]}, {id:"q8", text:"Need per-brand branded descriptors?", opts:[["yes","Yes, critical",3],["nice","Nice to have",1],["no","Parent descriptor OK",0]]}, {id:"q9", text:"Integration effort capacity", opts:[["low","Can't rewrite checkout",2],["medium","2-4 weeks dev available",1],["high","Can build anything",0]]} ]; var c = document.getElementById("sm-qs"); qs.forEach(function(q){ var div = document.createElement("div"); div.style.cssText = "margin-bottom:14px;"; div.innerHTML = ''; q.opts.forEach(function(o, i){ div.innerHTML += ' '+o[1]+''; }); c.appendChild(div); }); document.getElementById("sm-calc").addEventListener("click", function(){ var score = 0; qs.forEach(function(q){ var v = parseFloat(document.querySelector('input[name="'+q.id+'"]:checked').value); score += v; }); var verdict, color, rec; if (score >= 18){ verdict = "Strong fit — parent MID / sub-merchant model"; color = "#52c41a"; rec = "Your portfolio profile maps cleanly to a parent merchant account. Expect 40-80 bps processing savings, consolidated reconciliation, isolation from single-brand risk reviews, and per-brand descriptors under one MID. Engage a PayFac or sub-merchant acquirer."; } else if (score >= 10){ verdict = "Good fit — consider hybrid"; color = "#ffd666"; rec = "You have meaningful portfolio value but not full parent-MID economics yet. Consider: one parent MID for risky brands, direct acquirer for cleanest brand, preserves flexibility while you grow toward 8+ brands."; } else if (score >= 4){ verdict = "Weak fit — stay direct"; color = "#ffa940"; rec = "Direct acquirer relationships per brand still make sense at your stage. Revisit when you add 3-5 more brands or hit significant processor pain."; } else { verdict = "Not a fit — sub-merchant structure would add overhead"; color = "#ff5a5a"; rec = "Stay on direct acquirer (Stripe, Braintree, or traditional processor). The operational complexity of sub-merchant structure outweighs benefits at your profile."; } var html = ''; html += ''; document.getElementById("sm-result").innerHTML = html; }); })();

What the sub-merchant model actually is

A sub-merchant structure means multiple independent brands process payments under a single parent merchant account (parent MID) instead of each brand having its own direct merchant account with the acquirer. The parent holds the merchant agreement with the acquirer. Sub-brands operate as authorized sub-merchants under the parent, typically with per-brand descriptors, per-brand checkout experiences, and per-brand reporting — but with one set of underwriting, one reserve structure, and one aggregated processing history.

This is how Shopify Payments, Square, and PayPal work under the hood. They're PayFacs (payment facilitators) — they hold one giant MID with an acquirer, and every Shopify/Square/PayPal merchant is a sub-merchant under it. For multi-brand operators, running your own "private PayFac" via multiflow or a similar platform gives you the same aggregation benefits but with more control and better economics.

When the structure works

Multi-brand portfolios at scale

Five or more brands with combined volume above $500k/mo is the rough threshold where sub-merchant economics beat direct acquiring. Below that, the fixed costs (setup, ongoing platform fee, integration) outweigh the aggregation benefits.

High-risk verticals with common operators

If you operate 8 peptide brands under one holding company, every brand faces the same underwriting difficulty, the same reserve requirements, the same chargeback scrutiny individually. Consolidating under a parent MID means underwriting happens once at the parent level, and sub-brand onboarding is faster (a few days vs 2-6 weeks per brand).

Processor-risk isolation

When each brand has its own Stripe account, a Stripe risk review of Brand 3 doesn't affect Brands 1, 2, 4-8 — technically. In practice, Stripe correlates accounts by beneficial owner and a review of one often triggers reviews of all. A parent MID with an alternative acquirer sidesteps Stripe's correlation entirely.

Branded descriptor needs

Every brand wants its own descriptor on the customer's statement. On a parent MID with soft descriptor support, each brand passes its own per-transaction descriptor. The parent's hard MID descriptor sits in the background; customers see the brand they bought from.

When it doesn't work

Single-brand operators

If you operate one brand, direct acquiring is simpler and usually cheaper. Sub-merchant overhead adds complexity with no portfolio benefit to offset it.

Sub-$50k/mo combined

At low combined volume, Stripe's flat-rate beats most IC+ or sub-merchant structures. Growth-stage operators should stay on Stripe/Braintree flat-rate until volume justifies the switch.

SaaS with clean chargeback profile

SaaS doesn't benefit much from parent-MID aggregation. Clean chargeback ratios mean direct acquirer underwriting is easy. The sub-merchant structure adds complexity without the risk-absorption benefit that ecommerce gets.

Brands that need completely separate legal entities

Sometimes brands must remain fully separate for legal or regulatory reasons. Sub-merchant structures can accommodate this but with additional compliance overhead. Sometimes direct acquiring per brand is cleaner.

The nine questions and why they matter

Brand count — strongest single signal. 5+ brands is the line.

Combined volume — economics kick in at $500k+ combined.

Vertical — high-risk verticals benefit more; low-risk verticals benefit less.

Common operator — sub-merchant works best when brands share an entity or holding structure.

Current processor pain — operators with frozen accounts or over-priced contracts have the biggest delta to capture.

Reserve burden — consolidated reserves on the parent are typically 30-50% lower than summed sub-brand reserves.

Finance team size — smaller teams benefit disproportionately from consolidated reconciliation.

Descriptor needs — if per-brand descriptors are critical, sub-merchant models handle this natively.

Integration capacity — sub-merchant migration requires 2-8 weeks of checkout work. Teams without that bandwidth should delay.

What "good fit" looks like in practice

The highest-fit profile: 8-15 brands, $1-5M combined monthly volume, high-risk ecommerce vertical (peptides, CBD, nutra, adult), same holding company, currently on Stripe/Braintree with some accounts frozen or under punitive reserve, small finance team (1-3 people), needs per-brand branded descriptors, has 4-6 weeks of dev bandwidth available for migration.

This profile captures: 40-80 bps in processing savings, 60-80% reduction in finance reconciliation time, isolation from single-brand Stripe risk reviews, per-brand descriptors, one audit trail, one point of contact.

What "not a fit" looks like

The lowest-fit profile: 1 brand, under $50k/mo volume, SaaS, solo operator, happy with Stripe, no integration bandwidth. This operator should stay on Stripe. Sub-merchant structure would add 3-5 weeks of overhead for no real benefit.

The hybrid path

Not all 8 brands need to move at once. Many operators run a hybrid: most brands stay on Stripe (where they're already integrated and clean), the 2-3 "problem" brands (higher risk, frozen, underpriced) move to a parent MID. The parent MID handles the bottom quartile of the portfolio; Stripe handles the top.

This preserves Stripe's excellent infrastructure for the clean brands while giving you a fallback and isolation for the risky ones. It's often the right move before full consolidation.

FAQ

Is sub-merchant structure legal?

Yes. Payment facilitation is regulated but legal. Shopify, Square, PayPal all operate this model. Private PayFacs (like multiflow) follow the same rules with registration through Visa and Mastercard.

Will my brands keep their own Stripe-like checkout?

Yes. Modern sub-merchant platforms provide hosted checkout, iframe fields, or API primitives. Your checkout UX is preserved.

What happens if one sub-brand has a huge chargeback spike?

The parent MID absorbs the spike. The parent's ratio may rise but the other brands are insulated. The parent then isolates or terminates the problem sub-brand.

Can I use multiple parent MIDs?

Yes — common for large portfolios. One parent for high-risk brands, another for low-risk, distributes risk across acquirer relationships.

What if I need to exit the sub-merchant model?

Each brand can be re-onboarded to a direct acquirer with standard merchant onboarding. Reserve on the parent releases per agreement. Takes 4-8 weeks per brand. Reversible but not instant.