The short answer
A sub-merchant account is the account record a payment facilitator or parent merchant creates for an operator that wants to accept cards without holding a direct merchant account at an acquiring bank. The master entity (PayFac like Stripe, or a parent merchant account) carries the acquirer relationship; the sub-merchant account is a bookkeeping and identity layer beneath it.
Account-level mechanics
A true merchant account has its own unique 15-digit MID issued by the acquirer, its own Visa/Mastercard Merchant Identifier, and its own direct funding relationship with Wells, Chase Paymentech, WorldPay, or similar. A sub-merchant account has none of that. Instead:
- Sub-merchant ID (SMID): a 10–16 character identifier issued by the PayFac or parent, not the acquirer. Visible only within the master's reporting.
- Funding flow: the acquirer funds the master account; the master redistributes to sub-merchants per a payout schedule the master controls.
- KYB/KYC: handled by the master as part of sub-merchant onboarding. For PayFacs this is fast (minutes); for parent merchant accounts this is slower (24–72h) but results in better pricing.
- Regulatory footprint: the master is the regulated entity. The sub-merchant inherits compliance obligations but is not directly registered with Visa/Mastercard as a merchant of record.
What operators need to know
- Visa/MC dollar-volume caps exist. Under Visa PayFac rules, a sub-merchant processing over $1M/year may be required to move to a direct merchant account. Stripe, Square, and PayPal generally migrate you automatically, but this triggers fresh underwriting.
- Termination risk concentrates. Because the master holds the acquirer relationship, an acquirer-level risk event (the master's portfolio hitting chargeback thresholds) can cascade to you even if your own brand is clean.
- Descriptor control is limited. On a PayFac you usually get prefix + name format ("SQ *BRAND" or "PYPL *BRAND"). On a parent-merchant sub-account you get clean soft descriptors.
- Data portability varies. Exporting your customer payment-method vault out of a sub-merchant relationship is PayFac-policy-dependent. Parent merchant accounts under an ISO give you cleaner data exit.
Sub-merchant account vs. dedicated MID
A dedicated MID is a direct merchant account with the acquirer — you appear in their system as your own merchant of record, with your own chargeback ratio, reserve, and funding relationship. A sub-merchant account does not. The trade: dedicated MID = more control, slower to set up, interchange-plus pricing; sub-merchant account = instant setup, flat pricing, less control. multiflow's parent-merchant model gives operators a hybrid: consolidated underwriting at the parent, clean descriptors at the sub-brand, interchange-plus economics across both.