Multi-brand payment stack for a DTC agency

DTC agencies that run paid media + creative + ops for ecommerce brands often end up owning the payment stack too. "You're running our funnel, just put it on your Stripe" turns into a $4M/month pass-through that nobody sat down to structure. Five years later the agency has 15 client brands on 15 merchant accounts, half of them on the agency's entity, half on the client's entity, and reconciliation is a nightmare.

The structural question: whose name is on the MID? Answer changes ownership, liability, tax treatment, and operational model.

The three models agencies actually use

Model 1 — client-owned MID

Each client's legal entity holds the merchant account. Agency operates it on the client's behalf but doesn't receive the funds.

• Ownership: client. Agency cannot lose the account if they lose the client.
• Liability: client owns chargebacks, refunds, compliance.
• Tax: client gets the 1099-K. Agency invoices separately.
• Onboarding: slow — requires client principal to sign, provide docs.
• Fit: long-term retainer clients with their own finance teams.

Model 2 — agency-owned MID

Agency's legal entity holds the merchant account. Funds flow into agency. Agency pays out to client net of fees + agency take.

• Ownership: agency. Clients can't move the account without the agency cooperating.
• Liability: agency owns chargebacks, refunds, compliance exposure.
• Tax: agency gets the 1099-K. Agency issues 1099s to clients or W-9 tracked differently.
• Onboarding: fast — no client-side underwriting.
• Fit: short-term engagements, testing phases, or clients who don't have their own entity setup.

Model 3 — agency-platform with client sub-merchants (hybrid)

Agency runs a payfac-style platform. Each client is a sub-merchant with their own descriptor, their own underwriting, their own 1099-K, but onboarding through the agency's platform.

• Ownership: client owns their sub-account but agency owns the platform relationship.
• Liability: sub-merchant owns chargebacks; agency owns platform-level risk.
• Tax: clients get their own 1099-K (correct).
• Onboarding: faster than Model 1 because platform does some underwriting pre-approval.
• Fit: growing agencies with 10+ clients, predictable churn, desire to scale.

When each model fits

Boutique agency (3-5 clients)

Model 1 usually. Client-owned MIDs keep the relationship simple. Agency stays in its lane.

Growth agency (10-30 clients)

Model 3 (platform + sub-merchants). This is the sweet spot for the hybrid structure. Agency can onboard new clients in days, not weeks. Clients keep ownership. Tax and liability allocate correctly.

Aggressive scale agency (30+ clients)

Model 3 essentially mandatory. Model 1 can't keep up with onboarding throughput. Model 2 concentrates too much risk on the agency.

High-risk vertical agency

If your clients are in peptide, CBD, SARMs, etc., aggregator platforms (Stripe Connect, Square) aren't available. The platform has to run on high-risk-capable underwriting. This is where specialist parent-merchant structures beat payfac SaaS.

The 1099-K trap for Model 2

Agencies running Model 2 (agency-owned MID, funds pass through to client) often misclassify the 1099-K. The agency receives a 1099-K for the full flow, but only keeps a fee portion — the rest passes to the client.

The IRS increasingly views this as the agency reporting revenue it doesn't actually retain. 1099-MISC/1099-NEC issued to the client doesn't fully offset. In 2026 tax enforcement on payment facilitator structures is tighter. See 1099-K reporting for marketplaces and TIN matching for 1099-K.

Clean answer: if funds pass through, your structure should be a payfac or a sub-merchant platform where clients get their own 1099-Ks. Not a pass-through on the agency's single merchant account.

Operational mechanics — platform/sub-merchant

Onboarding flow

• Client signs agency master agreement
• Client fills sub-merchant application (entity info, principal, product, volume estimate)
• Platform runs underwriting (often 24-72 hours, faster than full merchant account)
• Sub-merchant approved, receives credentials
• Agency integrates client's checkout with sub-merchant ID

Daily operations

• Transactions flow to platform, routed to client sub-merchant
• Descriptor shows client brand
• Funds settle to client bank (or to agency for net-of-fee split, depending on contract)
• Chargebacks route to client or agency per contract
• Reconciliation breakdown per sub-merchant

Reporting

• Agency dashboard shows portfolio metrics (total GMV, blended rate, aggregate chargebacks)
• Per-client drilldown available
• Client gets access to own sub-merchant data only

Liability and chargeback allocation

Key contract decision: who eats chargebacks when a client's reserve doesn't cover?

• Platform-level guarantee (agency eats it) = attractive for clients but concentrates risk.
• Client-level only = correct allocation but hits small clients hard on spike events.
• Hybrid with platform reserve = agency holds a platform reserve from client settlements to cover short-term chargeback spikes; clients settle up.

Agencies typically move to hybrid by year 3.

Switching costs and lock-in

Clients on your platform can leave. If they built their store around your sub-merchant ID, moving off takes:

• New merchant account underwriting on their end
• Checkout integration migration
• Subscription migration (if applicable — requires network token transfer, see network tokenization)
• Chargeback / reserve wind-down

This is a real switching cost that benefits the agency but also creates long-term friction. Healthy agencies design their contracts to make offboarding clear-cut.

What not to do

• Don't run 15 clients through one Stripe account. Terminated quickly.
• Don't issue 1099-MISC to clients while keeping the 1099-K in the agency's name — IRS matching flags it.
• Don't skip client-side KYC on the sub-merchant structure. Schemes require it.
• Don't promise clients "no reserves, no holds" on their sub-merchant — you can't guarantee acquirer behavior.

What to do next

Audit your current client roster by model. Count how many are on Model 1, Model 2, or hybrid. If Model 2 is majority, the 1099-K exposure is real and the restructure is worth it. The 12-question application covers agencies exploring the parent-platform model.