The short answer
A sub-merchant is a business that accepts card payments under someone else's merchant account, not its own. The master account holder (the "payment facilitator" or "parent merchant") has the acquiring bank relationship; the sub-merchant operates under that umbrella. This is the model Stripe, Square, PayPal, and most modern platforms use — every Stripe user is technically a sub-merchant under Stripe's master account.
The two master-merchant models
1. Payment Facilitator (PayFac)
Stripe, Square, PayPal, Adyen (for Platforms), Braintree, Shopify Payments, Checkout.com — all PayFacs. The PayFac holds a master merchant account at an acquirer. They onboard sub-merchants using a streamlined KYC / KYB workflow (often automated within minutes). Regulatory responsibility for the sub-merchant's compliance rests partly on the PayFac.
Pros for sub-merchant: fast onboarding, no direct underwriting, simple API.
Cons for sub-merchant: flat-rate pricing (usually 2.9% + $0.30), limited control, can be offboarded (Stripe dropping you) with minimal notice.
2. Parent merchant account
A parent merchant account is a traditional acquirer relationship where the parent entity holds the account, and sub-brands operate as sub-merchants under it using soft descriptors. Each sub-brand shares the parent's underwriting, reserves, and compliance profile, but customer-facing (descriptor, refund flow, brand identity) is per sub-brand.
Pros: interchange-plus pricing, consolidated volume for negotiation, no PayFac offboarding risk, one operator relationship with the bank.
Cons: harder to onboard (full underwriting for the parent, though sub-brand rollup is lighter).
When each model fits
| Stage | PayFac (Stripe/Square) | Parent merchant account (multiflow) |
|---|---|---|
| First $10k-$50k/mo | Best fit — fast onboarding | Overkill |
| $50k-$200k/mo | Works but expensive | Savings start to justify switch |
| $200k+/mo | Leaving money on the table | Best fit — IC+ pricing + stability |
| High-risk vertical | Likely offboarded | Best fit — high-risk-compatible acquirer |
Sub-merchant obligations
- Follow the PayFac or parent's PCI guidelines. Usually this means using their hosted checkout or tokenization API — keeping your PCI scope minimal.
- Accurate MCC. Declare your actual business category. Misdeclaration = offboarding.
- Branded descriptors. PayFacs typically put their own name in the descriptor (e.g., "SQ *MERCHANT NAME"). Parent merchant accounts give you cleaner descriptors.
- 1099-K reporting. The PayFac or acquirer reports your gross card volume to the IRS via Form 1099-K.
Sub-merchant risks
- Account freeze / offboard. PayFac can drop you with minimal notice. Every operator in peptides, SARMs, CBD, etc., has a Stripe / Square horror story.
- Reserve hold. PayFacs may hold settlements for 90-180 days if they perceive risk.
- Blended pricing. Flat rate hides your true cost — you're paying the same on debit as on premium rewards credit.
- Loss of customer data. If offboarded, getting your customer list / subscription data out is a fight.
How multiflow positions
multiflow operates the parent merchant account model at scale for multi-brand operators. Each of your brands is a sub-brand (not technically a sub-merchant — a named division of your parent merchant account), keeping descriptors clean and pricing at interchange-plus. No PayFac offboarding risk, since the account is yours at an acquirer we introduce, not ours.