How franchise payments and payouts should work

Why are payments harder for a franchise network?

A single business takes payments into one account, and that is the end of the story. A franchise network is many independent businesses under one brand, so the same customer payment now raises questions a single operator never faces. Who receives the money first? Who pays whom, and when? Who carries the risk when a collection fails or a refund is due?

These are not just plumbing questions. They decide the franchisor’s regulatory exposure, each franchise’s cash flow, and how much reconciliation the network does every month. Get the money flow wrong and you inherit a permanent operating cost. Get it right and payments become a source of clean, trusted data about the whole network.

The core decision: where does the money land?

Everything else follows from one choice, so make it deliberately. There are two models.

• The pooled model. Customers pay head office, which holds the money and pays each franchise its share on a schedule. It looks simple and it centralises control, but it turns the franchisor into a payment intermediary. Head office now holds other businesses’ money, carries the settlement and refund risk, and may stray into regulated money-services territory. Reconciliation, disputes, and cash-flow delays for franchises all grow with the network.
• The connected-account model. Each franchise has its own payment account, and customer payments settle straight into it. The franchisor never holds the funds. The network still provisions the accounts, controls who can set them up, and sees every transaction for reporting, but the money belongs to the franchise from the moment it is paid.

For most networks the connected-account model is the safer default, because it removes head office from the money flow while keeping it in control of the setup. The pooled model earns its place only where central collection is a genuine requirement and the network is prepared to manage the compliance that comes with holding funds.

How does Stripe Connect fit?

The connected-account model is exactly what marketplace-payment products are built for, and Stripe Connect is the most widely used. The pattern is the same across similar products: the platform creates a connected account for each business, and that business onboards itself into it.

In a franchise setting that means four things:

• An account per franchise. Each franchise gets its own connected account, created from inside the network’s platform rather than by wiring up a separate processor per location.
• Self-service onboarding. The franchise completes its own identity checks (know your customer, or KYC) and adds its payout bank through the provider’s hosted onboarding, so the platform never handles raw bank details.
• Direct settlement. Card payments and subscriptions are taken as charges on the franchise’s own account, so funds settle to the franchise rather than a central pot.
• Central oversight without custody. The network sees who is onboarded, holds credentials securely, and reconciles every transaction, without ever holding the money.

This is the model we build on. Stripe Connect for franchises covers how the connected accounts, onboarding, and reconciliation work in practice, and it sits within the wider Franchising module.

Where does Direct Debit still win?

Card is not the whole story, and for recurring revenue it is often not the best rail at all. Bacs Direct Debit remains one of the strongest options for any franchise network that bills on a schedule, such as memberships, classes, or tuition.

• Cost. Direct Debit is typically a small flat fee per collection, where card is a percentage of every payment. On recurring, higher-value collection the difference compounds.
• Retention. A Direct Debit mandate does not expire when a card does, so it removes the involuntary churn that quietly cancels good customers every year.
• Predictability. Collections run on a known cycle with advance notice, and the Direct Debit Guarantee gives customers the confidence to set one up.

None of this competes with connected accounts; it sits inside the same decision. A franchise can hold its own connected account and still collect its recurring revenue by Direct Debit. For the full trade-offs, see switching from card billing to Direct Debit, and estimate the difference for your own numbers with the savings calculator.

Card or Direct Debit: which for what?

The honest answer for most networks is both, matched to the type of payment.

The pattern that works is Direct Debit for the recurring backbone, and card, taken into each franchise’s connected account, for joining fees and one-off sales. The goal is to route each payment down the rail that fits it, not to force everything onto one.

One-off, subscription, or instalments: which structure?

Choosing a rail is only half the design. The other half is how the charge is structured over time, and there are three common patterns. Most franchise networks use all three.

• One-off charge. A single, immediate payment, authorised in seconds on card. Use it for joining and registration fees, one-off classes or workshops, retail, and anything bought and fulfilled on the spot. It is the simplest structure and the right default whenever there is no ongoing commitment.
• Subscription. A recurring charge collected automatically on a schedule, with the provider managing renewals and retries until the customer cancels. Use it for open-ended memberships and ongoing services. A subscription on a connected account means recurring revenue settles to the franchise like any other payment. For recurring collection, weigh a card subscription against Bacs Direct Debit on cost and churn, as above.
• Instalments, often invoiced. A fixed total split into a known number of scheduled payments, for example a term of tuition paid in three, or a course paid monthly across its length. Because the total and the end date are fixed, instalments suit an invoice: issue one invoice and collect it in parts, or issue an invoice per instalment, each with its own due date. Use instalments when the customer is committing to a defined total rather than an open-ended service, and wants to spread the cost.

The quick test is the commitment. Is it paid once (one-off), paid until cancelled (subscription), or a fixed total spread over time (instalments)? That decides the structure, and the rail sits underneath it. A term paid in three by Direct Debit and a monthly membership on a card subscription are different structures on different rails, and a capable platform supports the whole grid rather than forcing every payment into one shape.

What about the franchisor’s fee?

Whatever rail collects the money, the network usually needs its cut, the management service fee (MSF) or royalty. There are two honest ways to handle it, and the choice matters.

• Deduct at the payment rail. A marketplace product can take an automatic fee as money moves, so the network’s share is separated at the point of payment. It is tidy, but it puts head office back into the money flow and ties the fee to individual transactions.
• Settle in full, reconcile separately. Payments settle to each franchise in full, and the network calculates and invoices the fee separately, from the same operational payment records. Each franchise’s revenue stays clean, and the fee is a transparent, auditable calculation rather than a deduction.

Many networks prefer the second approach, because it keeps the connected-account model’s main benefit intact: the franchise owns its money. It depends on the platform recording every charge, payment, and refund against the right franchise, which is what per-transaction attribution in the franchise hierarchy is for.

How should you decide?

Work through four questions in order.

• Whose money is it, and who should hold it? If the answer is the franchise, the connected-account model follows.
• What are you collecting? Recurring revenue points to Direct Debit; one-off and instant sales point to card.
• How does the network take its fee? Decide deliberately between a rail deduction and separate reconciliation.
• Can your platform attribute and reconcile every transaction? Without that, neither model gives you trustworthy network reporting.

Answer those and the payment architecture largely designs itself. The technology is mature. The risk lives in the design choices, and in whether your software operates them cleanly, month after month.

How we build this

We build franchise platforms where payments are part of the operating model, not a bolt-on. Each franchise gets its own Stripe Connect account with hosted onboarding and direct settlement, recurring collection runs through the Billing Engine, and every transaction is attributed to the right franchise and territory for network reporting. The same recurring-payments backbone runs in production for multi-site membership operators, including the Third Space Atlas platform.

If you are designing this for a network, we can help you weigh the models against your real numbers and operating model. See how we deliver bespoke franchise platforms, or book a consultation to work through it.

Payments involve regulatory and banking questions that sit outside software. Talk Think Do builds and operates the platform; we are not a bank, a payment institution, or a regulated advisor, and decisions about holding funds, money-services permissions, and scheme access should be confirmed with your payment provider and a qualified advisor.