Multi-location payment setup
Do I need a separate merchant account for each location?
Not always. Some payment platforms let one business manage multiple locations under one account, while other arrangements call for separate merchant accounts or location identifiers. The right structure depends on who owns each location, how customers see the business name, where deposits go, how reporting should be separated, and what the provider supports.
The short answer
One account may support several locations
A separate merchant account for every storefront is not a universal requirement. Square's current U.S. support documentation, for example, says a single Square account can create multiple locations for one business. It also describes location-specific business profiles, reporting, devices, and bank-account choices. That example shows a multi-location structure is possible, but it does not establish a rule for every provider or business.
Ask the prospective provider to document the proposed hierarchy before you sign or migrate. Confirm whether it uses one master account with location records, separate merchant IDs under a common relationship, or fully separate accounts. The labels and capabilities vary, so compare the actual operational result rather than relying on terminology alone.
Decision factors
Review how the locations are organized
Ownership and legal entities
Locations owned by the same legal entity may be structured differently from independently owned businesses, franchisees, or subsidiaries. Give the provider accurate ownership information and ask how each entity should be boarded.
Customer-facing identity
Confirm the business name and location information that may appear on receipts, statements, and transaction records. Clear descriptors can help customers recognize purchases, but the provider controls the available configuration.
Deposits and reconciliation
Decide whether locations share a bank account or need separate destinations. Square documents both shared and unique linked bank-account options for locations, illustrating why deposit routing should be confirmed during setup.
Reporting and access
List who needs company-wide reporting, location-only views, device access, refunds, and administrative permissions. Verify that the proposed account structure preserves the separation your accounting and operations teams need.
Planning workflow
Map requirements before opening accounts
Create a location inventory
For each location, record the legal owner, customer-facing business name, address, payment channels, expected bank destination, reporting owner, and required user roles. Do not include full bank or taxpayer credentials in a general planning document.
Separate business needs from platform labels
Write down the result you need: consolidated oversight, separate deposits, distinct statements, location-level reports, or independent administration. Then ask each provider how its account, merchant ID, and location concepts produce that result.
Confirm changes and exits
Ask what happens when a location opens, closes, changes ownership, changes its bank destination, or moves to another system. Document who can make those changes, which verification steps apply, and how historical reports remain accessible.
Test the reporting design
Before full rollout, inspect sample or test reports if the provider offers them. Confirm that transactions, refunds, disputes, deposits, and user activity can be attributed to the correct location without exposing one location's data to unauthorized users.
Questions for a provider
Get the structure confirmed clearly
- Can one business account manage every proposed location, and are there circumstances that require separate accounts?
- Will each location have its own identifier, receipt profile, statement descriptor, user permissions, and reports?
- Can deposits use one shared bank account, separate accounts, or a configurable mix?
- How are refunds, disputes, equipment, online payments, and account changes assigned to a location?
- What documentation is required for each legal entity, owner, bank destination, and customer-facing business name?
Answers may differ by provider, payment channel, business model, and underwriting decision. Treat written provider documentation and the final agreement as authoritative for the account being established. This page is general operational guidance, not legal, tax, accounting, or approval advice.
Related resources
Continue planning your payment setup
Common questions
Multi-location account FAQ
Can locations share one bank account?
Some platforms allow it. Square's current documentation says its locations can share a bank account or use unique linked accounts. Confirm the options and verification rules for your provider.
Does one login mean one merchant account?
Not necessarily. A dashboard may organize multiple locations or merchant identifiers under one administrative login. Ask for a diagram of the actual account hierarchy.
Should separate legal entities share an account?
Do not assume they can or should. Disclose the ownership structure and have the provider confirm its onboarding requirements for each entity.
What should I prepare first?
Prepare a location inventory covering ownership, business names, payment channels, deposit routing, reporting, and user access, using masked or non-sensitive planning details.
Last editorial review: August 13, 2026. Multi-location features and provider requirements can change, so verify the current documentation and agreement for your account.
Next step
Document the account hierarchy before rollout
Map each location's owner, banking, reporting, access, and customer-facing identity, then obtain written confirmation of the provider's proposed structure.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US