Payment Processing for Franchises in 2026: Multi-Location MID Structures, Royalty Billing, and Centralized Reporting

Call 866-305-6454 now for a franchise payment processing review.

Franchise payment processing is not one merchant account multiplied across locations. It is a portfolio structure.

Each location may have a different legal owner, physical address, terminal estate, sales mix, settlement account, chargeback profile, and customer-facing descriptor. The franchisor may control the brand, technology, reporting, and operating standards. The franchisee may own the business, employ the staff, receive settlement, and carry the customer-service obligation.

The payment model must reflect those facts.

A merchant account broker can help align the acquiring relationship, MID structure, gateway, underwriting file, reporting hierarchy, and fee model before locations go live. The objective is not simply to activate terminals. The objective is to create a payment environment that supports growth without obscuring ownership, settlement, disputes, or risk.

This article addresses payment processing for franchise systems in 2026. It covers:

• Multi-location MID structures.
• Royalty and advertising fund billing.
• Centralized reporting.
• Chargeback ownership.
• PCI DSS v4.0.1 scope.
• Underwriting documentation.
• Gateway and POS compatibility.
• Portfolio-level risk controls.

1. Treat the franchise as a portfolio

A single independent merchant usually has one operating entity, one location, one settlement relationship, and one primary risk profile.

A franchise system may have:

• A franchisor corporation.
• Corporate-owned units.
• Independent franchisee corporations or LLCs.
• Separate bank accounts.
• Shared brand standards.
• Shared technology.
• Centralized marketing.
• Royalty obligations.
• Location-specific sales and dispute data.

That creates a portfolio problem.

The franchisor may set rules for approved equipment, payment pages, customer receipts, refunds, and reporting. It may also require a specific processor or gateway. However, brand control does not automatically make the franchisor the merchant of record for every sale.

The entity that owns the location, sells the goods or services, signs the merchant agreement, receives settlement, and responds to disputes must be identified clearly.

The FTC Franchise Rule, 16 CFR Part 436, provides a disclosure framework for franchisors. It is not payment-processing authorization and is not legal advice. The franchise disclosure document and franchise agreement should accurately describe:

• Who contracts with the acquirer.
• Who receives settlement.
• Who pays processing fees.
• Who funds refunds.
• Who carries chargeback and reserve exposure.
• Whether the franchisor can require a particular processor.
• How technology and royalty fees are calculated.
• Whether fees can be netted from settlement.
• What happens when a location closes or changes ownership.

The FTC Franchise Rule requires disclosure of specified franchise information. Payment obligations and processing controls should be reviewed with franchise counsel before implementation.

Brand standards and payment liability are separate issues. A franchisor can require a standard POS configuration while each franchisee remains responsible for its own merchant agreement. A franchisor can also own and operate corporate units while using a different structure for independently owned locations.

Start with an entity and location map. Do not start with a terminal order.

2. Compare MID structures before signing agreements

A merchant identification number, or MID, connects payment activity to an acquiring relationship. The MID structure determines how transactions are identified, settled, monitored, disputed, and underwritten.

Four models are common.

One MID for all locations

A central franchisor-owned MID may route transactions from multiple locations into one acquiring relationship.

Potential advantages:

• Centralized settlement.
• One enterprise reporting relationship.
• Consistent configuration.
• Fewer contracting points.
• Easier corporate treasury management.

Potential problems:

• The central entity may appear to be the seller for every transaction.
• Location-level liability can become difficult to separate.
• Chargebacks may route to the franchisor.
• Reserves may be calculated against the consolidated portfolio.
• Franchisee ownership may not match network data.
• A problem at one location can affect the broader account.
• Descriptor accuracy can become difficult.

Use this model only when the franchisor is genuinely the merchant or the acquirer has approved the arrangement based on the actual business model.

Per-location MIDs under a shared master

Each location receives its own MID or sub-MID. The locations remain grouped under an enterprise relationship.

Potential advantages:

• Location-level settlement.
• Clearer chargeback routing.
• More precise monitoring.
• Better underwriting separation.
• Centralized reporting without erasing local identity.
• Easier location-level fee allocation.

This model often fits systems with independently owned units that still require centralized oversight.

The registry should connect each location to:

• Legal entity.
• DBA.
• Physical address.
• MID or sub-MID.
• MCC.
• Settlement account.
• POS device.
• Gateway account.
• Descriptor.
• Franchise agreement.
• Corporate or franchisee ownership status.

Sub-merchant or PayFac-style onboarding

A payment facilitator or similar sponsored-merchant model may onboard franchisees beneath a larger platform or acquiring relationship.

This is not a reporting shortcut.

The structure may create formal responsibilities for onboarding, monitoring, transaction data, reserves, prohibited activity controls, and termination treatment. The sponsor, acquirer, or network requirements must be satisfied.

A franchisor should not assume that controlling the brand creates the right to onboard franchisees as sub-merchants. The acquiring institution must approve the model.

Hybrid structures

A hybrid can use:

• Corporate MIDs for corporate-owned units.
• Separate MIDs for franchisee-owned units.
• A shared reporting hierarchy.
• Centralized gateway administration.
• Location-level settlement.
• Separate royalty billing.

This may provide operational flexibility. It also requires stronger governance. Each transaction must retain accurate ownership and location data.

The Visa Core Rules and Visa Product and Service Rules address merchant identification, merchant location, merchant name, and transaction data. Review the current Visa rules publication and Visa Merchant Data Standards Manual with the acquirer.

A fixed-location transaction should not be presented as though it came from an unrelated central office. A location descriptor should use a consistent format across the system. For example, a brand may use a brand name with city or store number, subject to acquirer approval, field limits, and network rules.

Mastercard also addresses merchant identification, location, sponsored merchants, transaction-message data, and termination treatment in its Mastercard Rules.

Legal entity → location → MID/sub-MID → terminal or gateway → settlement account → reporting node

That chain should be documented before production.

3. Identify who signs the merchant agreement

The merchant agreement is not a formality. It determines who accepts the acquiring relationship and who faces contractual exposure.

Franchisor-owned account

The franchisor may sign when it owns and operates the locations, sells directly to customers, and receives settlement.

This structure may be appropriate for corporate-owned units. It should not automatically be extended to independent franchisees.

If the franchisor signs for franchisee activity, the agreement should address:

• Authority to process franchisee transactions.
• Ownership of customer funds.
• Refund authority.
• Chargeback responsibility.
• Reserve funding.
• Data access.
• Franchisee termination.
• Location closure.
• Sub-merchant obligations.
• Audit rights.

Franchisee-owned account

The franchisee signs its own merchant agreement and remains responsible for its sales.

This structure usually provides a clearer relationship between:

• Seller.
• Settlement recipient.
• Customer-service operator.
• Dispute respondent.
• Refund funder.
• Risk owner.

The franchisor can still standardize the technology, gateway, POS, descriptor format, receipt requirements, and reporting feeds.

Corporate guarantee

A franchisor may provide a corporate guarantee for franchisee obligations. A guarantee does not automatically convert the franchisor into the seller or merchant of record.

The guarantee should state what it covers. Possible areas include:

• Unfunded chargebacks.
• Reserve shortfalls.
• Negative balances.
• Processor fees.
• Fraud losses.
• Refund obligations.
• Data security liabilities.
• Post-termination amounts.

The agreement should not leave the acquiring institution to infer these relationships from a brand name.

4. Separate royalty and franchise-fee billing

Customer sales and franchisee obligations are different payment streams.

Customer sales may include:

• Product purchases.
• Food and beverage.
• Services.
• Delivery charges.
• Tips.
• Refunds.
• Customer credits.

Franchisee obligations may include:

• Royalties.
• Advertising fund contributions.
• Technology fees.
• Training charges.
• Supply charges.
• Equipment charges.
• Approved service fees.

Do not combine these streams in a way that obscures the payee, purpose, or settlement trail.

A royalty invoice should identify:

• The franchisor or affiliated payee.
• The billing period.
• The calculation basis.
• The location.
• The amount.
• Any adjustments.
• The authorization method.
• The debit date.
• The return or cancellation process.

ACH authorization

ACH debits for franchisee obligations require a documented authorization process.

Where Regulation E applies, the Consumer Financial Protection Bureau’s Regulation E, 12 CFR Part 1005, addresses preauthorized electronic fund transfers. Section 1005.10 requires written or similarly authenticated authorization for covered preauthorized transfers and requires a copy of the authorization to be provided. See the CFPB Regulation E text and 12 CFR 1005.10.

A franchisee business account may involve commercial ACH rules and contract law instead. That does not justify using a generic authorization form. The payment provider should determine which rules apply to the account holder, payer, authorization method, and transaction.

The authorization record should capture:

• Payer name.
• Account information.
• Authorization date.
• Authorization language.
• Amount or calculation method.
• Frequency.
• Effective date.
• Revocation procedure.
• Notice process.
• Copy-delivery method.
• Authorization channel.

ACH entry codes

The entry code should match the authorization channel and transaction type.

Nacha rules address ACH authorization, entry classifications, company entry descriptions, return handling, and risk monitoring. Review the Nacha Operating Rules resource and the Nacha company entry description rules.

For example, Internet-authorized debits may require WEB treatment. Telephone-authorized debits may require TEL treatment. The processor and originating depository financial institution should confirm the correct code.

Do not hard-code a retry policy without reviewing the applicable return code, authorization status, notice requirement, and Nacha limits.

Sold or closed locations

A location sale or closure should trigger a billing workflow.

The system should:

1. Freeze new royalty calculations at the effective date.
2. Determine the final billing period.
3. Reconcile outstanding fees.
4. Stop future debits when authorized.
5. Update ownership records.
6. Remove or suspend the location from the reporting hierarchy.
7. Preserve historical transaction and dispute data.
8. Confirm equipment return or reassignment.
9. Update the descriptor and settlement destination.
10. Document any reserve or chargeback tail.

Do not leave a closed location active because the franchise database and payment database were not synchronized.

5. Map card acceptance by location type

A brand can have materially different payment activity at each location.

Corporate-owned units

Corporate-owned stores may use standardized:

• POS devices.
• Networks.
• Refund controls.
• Employee permissions.
• Settlement accounts.
• Reporting feeds.

Central control can simplify deployment. It can also concentrate operational and security risk.

Franchised units

Franchisees may use different:

• Internet providers.
• POS equipment.
• Operating systems.
• Bank accounts.
• Staff practices.
• Local delivery partners.
• Refund workflows.

A standard brand policy does not prove standard technical scope. Each location must be assessed.

Food service and tip handling

Food service locations may accept tips at the point of sale, through a digital receipt, or through a later adjustment process.

The implementation should define:

• When the tip is entered.
• Who can adjust it.
• How the employee receives attribution.
• How the adjustment appears in reporting.
• How refunds and disputes treat the tip.
• Which systems retain the transaction record.

Tip processes can create reconciliation differences if the POS, gateway, settlement report, and payroll system use different dates or identifiers.

Retail countertop

Retail locations may use countertop terminals, integrated POS devices, contactless acceptance, and barcode workflows.

The franchise system should control:

• Approved terminal models.
• Key injection and device management.
• Replacement procedures.
• Location assignment.
• Software versions.
• Refund permissions.
• Offline transaction rules.

Mobile and delivery

Mobile, curbside, and delivery transactions may combine card-present, card-not-present, keyed, wallet, or platform-mediated payments.

The transaction record should still identify the selling location and correct merchant relationship. A central mobile application should not automatically make the franchisor the seller.

Review retail credit card processing requirements alongside the online payment model. Retail acceptance and online credit card processing may require different fraud controls, routing, evidence, and PCI scope.

6. Assign chargeback and dispute ownership

A dispute should route to the entity that can produce the evidence.

Evidence may originate at:

• The location.
• The franchisor support team.
• The POS.
• The gateway.
• The delivery platform.
• The customer relationship system.
• The inventory system.
• The franchisee’s email or phone records.

The merchant account structure should identify who receives the dispute notice and who must respond.

A useful workflow assigns:

• A central dispute administrator.
• A location-level evidence owner.
• A response deadline monitor.
• A refund approval owner.
• A reserve and settlement contact.
• A final escalation owner.

The location should provide operational evidence. The central team should package and submit it when the merchant agreement or gateway model requires central control.

Evidence may include:

• Receipt.
• Order record.
• Delivery confirmation.
• Refund record.
• Customer communications.
• Device or terminal details.
• Signed pickup record.
• Terms accepted at checkout.
• Item or service description.
• Cancellation policy.
• Franchise location identifier.

The response should not substitute a generic brand statement for transaction-specific evidence.

Franchise systems can accumulate disputes faster operationally because the evidence is distributed across many locations. The issue is not necessarily that every franchise system has a higher dispute rate. The issue is that missing evidence, inconsistent refunds, and delayed escalation can multiply across the portfolio.

The central platform should monitor disputes by:

• Location.
• Franchisee.
• Product category.
• Entry method.
• Device.
• Gateway.
• Employee or register where appropriate.
• Reason code.
• Transaction date.
• Settlement date.

7. Define PCI DSS v4.0.1 scope by environment

PCI scope should be documented by system and responsibility. A franchise logo does not create one uniform environment.

The PCI Security Standards Council describes PCI DSS as a baseline of technical and operational requirements for entities that store, process, transmit, or can affect the security of payment account data.

Centralized scope

A franchisor may centralize:

• Payment page administration.
• Gateway configuration.
• Token services.
• Device management.
• Reporting.
• User access.
• Security monitoring.
• Vendor management.

Centralization can improve consistency. It does not automatically remove the environment from scope.

A corporate reporting database may be in scope if it receives payment data, stores sensitive information, connects to the cardholder data environment, or can affect payment security.

Per-location scope

Each location should document:

• Terminals.
• Network connections.
• POS integrations.
• Wireless configuration.
• Local administrators.
• Paper records.
• Payment applications.
• Remote support.
• Incident procedures.
• Vendor responsibilities.

Do not reuse one SAQ across materially different locations without confirming eligibility.

SAQ B and SAQ B-IP

SAQ B is narrow. It applies to eligible merchants using certain standalone, dial-out terminals or imprint machines without electronic cardholder data storage and without connections to other systems or the internet.

SAQ B-IP applies to eligible merchants using standalone, PCI-listed approved PTS point-of-interaction devices with an IP connection to the processor. The exact eligibility criteria matter.

Neither form should be selected merely because a location uses a countertop terminal.

SAQ D

SAQ D may apply where the environment does not meet another SAQ’s eligibility conditions. E-commerce, broader integrations, electronic storage, and complex system connections can introduce additional requirements.

Payment page script controls, administrative access, APIs, segmentation, service providers, and connected POS systems require review.

Franchisee-selected equipment

Franchisees selecting their own terminals creates a control problem.

The franchisor should maintain an approved equipment list. The list should identify:

• Model.
• Firmware.
• Processor compatibility.
• PTS status where applicable.
• Encryption or tokenization behavior.
• Remote-management method.
• Replacement process.
• Support owner.
• Retirement process.

A location should not add equipment to the production environment without an approval and scope review.

8. Build centralized reporting with local accountability

Centralized reporting should answer two questions at the same time:

1. What happened across the brand?
2. What happened at each location?

The reporting hierarchy should support:

• Gross sales.
• Refunds.
• Chargebacks.
• Fees.
• Reserves.
• Net settlement.
• Tips.
• Taxes where applicable.
• Royalty basis.
• Advertising fund basis.
• Technology fees.
• Settlement date.
• Transaction date.
• Location.
• Legal entity.
• MID or sub-MID.
• Gateway.
• Payment channel.

Fee allocation

If the processor bills centrally, the franchisor needs a documented allocation method.

Possible allocation dimensions include:

• Transaction count.
• Gross volume.
• Location-specific fees.
• Equipment charges.
• Gateway usage.
• Chargeback fees.
• Reserve costs.
• Shared platform fees.

The allocation formula should be disclosed in the franchise agreement or related operating documents.

Royalty reporting

Royalty reporting based on card volume requires a clear definition.

The system should specify whether the calculation uses:

• Authorized sales.
• Captured sales.
• Settled sales.
• Gross sales before refunds.
• Net sales after refunds.
• Sales excluding taxes.
• Sales excluding tips.
• Sales from designated channels.

Do not calculate royalties from one report and settle merchant fees from another without reconciling the identifiers.

Settlement reconciliation

A useful reconciliation compares:

Transaction detail
+ refunds
- chargebacks
- processing fees
- reserves
+ or - adjustments
= settlement amount

The formula is a reporting model, not a network rule. The platform should document how each line is sourced.

Royalty debits should remain separately identifiable from customer settlement. Netting may be operationally convenient but should not hide the amount, payee, or calculation method.

Review merchant account features and payment gateway integration when evaluating reporting, gateway, and settlement requirements.

9. Assemble underwriting documents in two layers

A franchise underwriting file should contain a system layer and a location layer.

Franchisor-level package

The franchisor may provide:

• Corporate formation documents.
• Ownership chart.
• Franchise disclosure document.
• Franchise agreement template.
• Brand and website information.
• Business model description.
• Payment flow diagram.
• Processing history.
• Refund policy.
• Chargeback procedures.
• Technology architecture.
• Gateway details.
• Vendor list.
• Data security controls.
• Settlement model.
• Royalty calculation.
• Advertising fund structure.
• Corporate-owned location information.
• Franchisee onboarding process.

The processor needs to understand what the brand sells, how it sells, who receives funds, and how the network controls locations.

Franchisee-level package

Each franchisee may supply:

• Legal entity documents.
• Ownership information.
• Tax identification.
• Physical location.
• Lease or occupancy information.
• Bank account.
• Website or ordering page.
• Expected sales channels.
• Product or service details.
• Refund policy.
• Processing history.
• Chargeback history.
• Equipment list.
• Delivery or marketplace relationships.
• Beneficial ownership information.

A franchisor-owned unit may use the corporate package with location-specific documentation. An independent franchisee generally needs its own underwriting file.

If one location has unusual risk, the portfolio should not conceal it. Review high risk merchant account requirements when a location sells regulated, restricted, subscription, high-ticket, or dispute-sensitive goods or services.

10. Apply portfolio-level risk controls

A franchise payment program needs controls at three levels:

• Brand.
• Franchisee.
• Location.

Location-level monitoring

Monitor:

• Refund spikes.
• Dispute volume.
• Unusual ticket changes.
• Card-not-present growth.
• Manual entry.
• Repeated failed payments.
• Excessive declines.
• Sudden sales increases.
• Unusual geographic activity.
• Settlement account changes.
• Device substitutions.
• Multiple locations sharing credentials.

The objective is early intervention. Do not wait for an acquiring relationship to place the full portfolio under review.

New-unit standards

Before activation, require:

• Approved legal entity.
• Approved bank account.
• Verified physical address.
• Approved equipment.
• User access assignment.
• Refund training.
• Dispute training.
• PCI responsibility assignment.
• Descriptor approval.
• Reporting validation.
• Settlement test.
• Royalty billing setup.

A new location should not inherit production access from a closed or sold unit.

Brand-wide termination

A problem at one location does not automatically mean every location has the same status. Common ownership, control, processing, transaction data, or conduct can create broader underwriting consequences.

Mastercard’s merchant monitoring and termination materials describe how acquirers may record qualifying termination information for due diligence. Review the current Mastercard Rules and obtain acquirer guidance before restructuring a terminated location.

Do not move a terminated location to a new MID without investigating:

• The termination reason.
• The ownership.
• The activity.
• The website.
• The customer offer.
• The dispute history.
• The reserve position.
• The acquirer’s approval.

11. Select the broker and gateway for the whole estate

A franchise system should evaluate a merchant account broker on portfolio execution, not only advertised rates.

Review whether the broker can support:

• Corporate and franchisee underwriting.
• Multiple MIDs or sub-MIDs.
• Location hierarchy.
• Centralized reporting.
• Separate settlement.
• Royalty billing.
• Chargeback routing.
• Reserves.
• High-risk locations.
• Retail acceptance.
• Online credit card processing.
• MOTO and delivery transactions.
• International activity where applicable.
• Gateway-to-POS compatibility.
• Franchisee onboarding.
• Equipment replacement.
• Data exports.
• API access.
• Role-based permissions.

Transparent credit card processing pricing should show how fees apply at each layer:

• Transaction processing.
• Gateway.
• Equipment.
• Chargebacks.
• Refunds.
• ACH.
• Reserves.
• Monthly platform access.
• Statement or reporting services.
• Location additions.
• Termination.

Review transparent credit card processing pricing and interchange rates when comparing proposals. The correct comparison is the total operating model, not a single quoted rate.

Gateway-to-POS compatibility

A mixed estate may contain:

• Legacy countertop terminals.
• Integrated POS systems.
• Mobile readers.
• Online checkout.
• Call-center tools.
• Delivery applications.
• Franchisee-selected platforms.

The gateway should be tested against each approved configuration.

Validate:

• Authorization and capture.
• Partial approval behavior.
• Refunds.
• Voids.
• Tip adjustments.
• Recurring or stored payment workflows where applicable.
• Duplicate prevention.
• Transaction identifiers.
• Location identifiers.
• Descriptor fields.
• Webhooks.
• Settlement files.
• Chargeback data.
• Outage behavior.
• Token portability within the approved environment.
• User permissions.

A gateway that works for one corporate store may not work for a franchisee’s POS, internet connection, receipt configuration, or delivery workflow.

12. Use a franchise rollout checklist

Structure

• Identify every legal entity.
• Classify corporate-owned and franchisee-owned locations.
• Select the MID, sub-MID, sponsored-merchant, or hybrid model.
• Obtain written acquirer approval.
• Define merchant of record.
• Define settlement ownership.
• Define chargeback ownership.
• Define reserve responsibility.

Network data

• Map each location to a physical address.
• Assign MCCs.
• Approve merchant names.
• Approve descriptor format.
• Use consistent location data.
• Document mobile and delivery treatment.
• Confirm applicable country and acquiring relationships.

Agreements

• Review the merchant agreement.
• Review the franchise agreement.
• Describe processing fees.
• Describe refunds and chargebacks.
• Describe reserves.
• Describe technology fees.
• Describe royalty calculations.
• Describe advertising fund billing.
• Describe settlement netting.
• Describe closure and sale procedures.
• Obtain legal review.

ACH billing

• Determine whether Regulation E applies.
• Capture written or authenticated authorization.
• Deliver a copy.
• Record amount and frequency.
• Select the correct SEC code.
• Provide required notices.
• Track revocation.
• Track returns.
• Control re-presentment.
• Stop debits when the location closes.

PCI and technology

• Inventory terminals and payment pages.
• Document each environment.
• Assign PCI responsibilities.
• Approve equipment.
• Control scripts and integrations.
• Restrict administrative access.
• Segment systems where appropriate.
• Confirm service-provider responsibilities.
• Reassess scope when a franchisee selects new equipment.

Reporting

• Build the location registry.
• Reconcile transaction and settlement identifiers.
• Report by legal entity and location.
• Allocate fees transparently.
• Separate customer sales from royalty billing.
• Track refunds and chargebacks.
• Validate settlement before launch.
• Preserve historical records after closure.

Operations

• Train location staff.
• Train franchise support staff.
• Assign dispute owners.
• Test refunds.
• Test voids.
• Test tips where applicable.
• Test offline and outage procedures.
• Test device replacement.
• Test new-unit onboarding.
• Test location closure.

Final action

Franchise payment processing should be designed around ownership, location, settlement, and evidence.

A central reporting dashboard does not replace accurate MID data. A brand standard does not replace a merchant agreement. A gateway connection does not resolve franchisee liability. A royalty debit does not replace a documented authorization.

Build the structure before adding locations.

Call 866-305-6454 to review multi-location merchant account architecture, retail credit card processing, gateway compatibility, transparent credit card processing pricing, or high-risk franchise locations.