Multi-brand payment stack for a franchise system

A franchise payment stack looks like an agency platform at first glance, but the mechanics are different. Franchisees are licensees, not clients. Royalties are owed automatically. Brand consistency on customer statements is mandated in the Franchise Disclosure Document. Disputes sometimes involve the franchisor even when the franchisee processed the transaction.

Franchisors who treat payment as an ops checkbox end up overbuilding it, under-automating royalties, and creating friction between corporate and franchisees every month-end.

The three stakeholders

Franchisor (corporate)

• Wants brand consistency on descriptors
• Wants automated royalty calculation and collection
• Wants portfolio-level reporting (unit economics, same-store sales, chargeback trends)
• Wants defensive structure if a franchisee misbehaves or fails

Franchisee

• Wants fast onboarding (days, not weeks)
• Wants fair pricing (not a 50 bps markup over wholesale)
• Wants clean split between gross and net (transparent royalty math)
• Wants own bank settlement (not funds held by corporate)

End customer

• Wants recognizable brand on statement
• Wants a phone number to call with disputes
• Doesn't care about the franchise model at all

The franchise-specific structural options

Option 1 — franchisee self-managed

Each franchisee has their own merchant account (Stripe, Square, or local ISO). Franchisor collects royalties via separate invoicing or ACH pull from franchisee bank.

• Pros: simple legally, franchisee has full control.
• Cons: no descriptor consistency, no portfolio reporting, royalty collection is manual and error-prone, franchisor can't enforce PCI standards across system.

Option 2 — corporate-managed payfac

Franchisor runs a payfac-style platform, onboards each franchisee as a sub-merchant, settles to franchisee bank net of royalty split.

• Pros: brand consistency, automated royalty, portfolio reporting, franchisor controls compliance.
• Cons: franchisor assumes money-transmitter-adjacent risk, needs platform-level underwriting, franchise disclosure document (FDD) needs to cover the payment stack.

Option 3 — parent merchant + franchisee sub-merchants (this is what works)

Franchisor is the parent merchant of record with an acquirer. Each franchisee is a sub-merchant with their own DBA, descriptor, bank account. Royalty split happens automatically at settlement.

• Pros: descriptor consistency enforced at acquirer level, automated royalty via split-settlement, franchisee retains ownership of their sub-merchant, lower regulatory complexity than payfac.
• Cons: requires acquirer that supports sub-merchant + split-settlement structure, needs orchestration layer.

How royalty automation actually works

The breakthrough in 2026 franchise payment stacks is split-settlement. When a customer pays $100 at a franchisee location:

• Customer card charged $100 on the franchisor's parent MID, descriptor shows "BRANDNAME #042"
• At settlement, acquirer splits: $5 (5% royalty) to franchisor bank, $95 minus processing fees to franchisee bank
• Both parties see settlement reports the next day
• No month-end royalty invoicing, no franchisee delays, no disputes

This requires acquirer-level split-settlement capability. Not all acquirers offer it. Stripe Connect has partial support (payouts only). Dedicated franchise platforms offer full support.

Royalty structures that work with split-settlement

• Flat percent of gross — simplest. 5% of every transaction to franchisor.
• Flat percent + marketing fund — 5% royalty + 2% marketing contribution = 7% total split.
• Tiered by volume — 6% on first $50k monthly, 5% above. Requires monthly calculation at settlement.
• Flat fee per transaction — $0.50 per transaction regardless of amount. Unusual but exists.

Complex structures (volume tiers, product-category splits) require orchestration-layer calculation before settlement.

Branded descriptor strategy

Franchise FDDs typically require consistent customer-facing branding. Descriptor should:

• Include brand name
• Include unit identifier (location code, city, or store number)
• Include support phone (franchisor or local)

Example: "PIZZA BRAND #042 DENVER 555-0100" — brand recognizable, unit identifiable, callback available. Dynamic descriptor capability is mandatory for this.

Franchisee onboarding

Fast franchisee onboarding is a competitive advantage. Target: 5-7 business days from franchise agreement signature to live processing.

• Day 0 — franchise agreement signed
• Day 1-2 — franchisee submits entity info, bank details, principal KYC
• Day 3-5 — platform runs sub-merchant underwriting
• Day 5-6 — sub-merchant approved, descriptor configured
• Day 7 — POS/ecom integration live

Chargeback handling in franchise systems

Customer disputes the charge. Is the franchisee liable or the franchisor? Depends on structure:

• Sub-merchant model: franchisee's sub-merchant owns the chargeback. Franchisor may provide dispute representment support.
• Corporate payfac: franchisor owns all chargebacks, deducts from franchisee settlement or invoices separately.
• Hybrid: franchisor handles dispute representment (brand consistency), franchisee bears financial loss if representment fails.

Portfolio KPIs for franchisors

• Same-store sales per unit
• Average ticket per unit
• Royalty revenue collection rate (target: 99%+ via automated split)
• Chargeback ratio per unit (identify problem franchisees early)
• Unit onboarding cycle time
• Blended effective rate across system

FDD disclosure

Most FDDs require disclosure of mandatory payment-stack participation. Franchisors moving to parent-merchant structure need to:

• Disclose required payment processor in Item 8 (sources of products and services)
• Disclose fees in Item 6
• Justify "approved" processor designation if franchisee can't choose
• Update existing FDDs when system changes processor

Not legal advice — franchise counsel reviews.

What not to do

• Don't let each franchisee pick their own processor. Brand consistency collapses.
• Don't hold franchisee funds for more than 48 hours without a compelling reason. Cash-flow starvation causes unit failures.
• Don't run royalty collection on a separate schedule from the payment flow. Split-settlement is vastly cleaner.
• Don't underwrite the franchisee sub-merchant as if it's the franchisor's direct risk. Franchisee risk is isolated if structured correctly.

What to do next

Franchise system with 20+ units: audit your current royalty collection rate. If below 95% or if collection takes more than 7 days post-month-end, parent-merchant with split-settlement pays for itself in staff time saved. The 12-question application covers franchise system assessments.

Related reading: franchise payment rollups, 1099-K reporting for franchise rollups.