> For the complete documentation index, see [llms.txt](https://docs.sensepass.com/sensepay/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sensepass.com/sensepay/get-started/choose-your-account-structure.md).

# Choose your account structure

Two questions decide most cases:

1. **How many legal entities or settlement accounts are there?** Separate settlement or separate data ownership means separate merchants.
2. **Who needs to see whose data?** Many sites with the same owner are locations of one merchant.

### Which structure fits your business?

| If your business...                    | Set it up as                                                               |
| -------------------------------------- | -------------------------------------------------------------------------- |
| Is one company with one store          | 1 merchant, 1 location, its registers and devices                          |
| Is one company with many stores        | 1 merchant, 1 location per store                                           |
| Also sells online                      | Add an e-commerce location                                                 |
| Has several legal entities or brands   | 1 merchant per entity, the group HQ as partner                             |
| Is a franchise with independent owners | The franchisor as partner, 1 merchant per franchisee                       |
| Is a franchise running trucks or vans  | The franchisor as partner, 1 merchant per franchisee, 1 location per truck |
| Sells software or services to stores   | You as partner, 1 merchant per store customer                              |

Models can be combined, for example a chain with an online store and delivery trucks. Start small: a single store can grow into a chain by adding locations, without rebuilding anything.

### Single store

One business, one location, one or more registers. Each register has a SensePass tag and a card terminal (PinPad).

```mermaid
flowchart TD
    M[Merchant: Cafe Aroma] --> L[Location: Main Street]
    L --> LR[Register: Counter]
    LR --> LT[SensePass tag]
    LR --> LC[Card terminal / PinPad]
    L --> L2R[Register: Bar]
    L2R --> L2T[SensePass tag]
    L2R --> L2C[Card terminal / PinPad]
```

| Area                  | How it is set up                                                                         |
| --------------------- | ---------------------------------------------------------------------------------------- |
| Payment methods       | Set once on the location, with your processor account.                                   |
| Registers and devices | One register per checkout point, each with a SensePass tag and a card terminal (PinPad). |
| Checkout              | Branding, payment page options and receipts on the location.                             |
| Surcharge             | Location Type **In-store**; the store's state is used for surcharge rules.               |
| Users                 | Owner: Merchant Full Access. Staff: Location Full Access.                                |
| Reporting             | One dashboard; filter by register and payment method.                                    |

### Multi-store chain

One company with many stores and an online store.

```mermaid
flowchart TD
    M[Merchant: Retail Co] --> L1[Location: Store 101, NY]
    M --> L2[Location: Store 102, NJ]
    M --> L3[Location: Online store]
    L1 --> L1R[Register: POS 1]
    L1R --> L1T[SensePass tag]
    L1R --> L1C[Card terminal / PinPad]
    L2 --> L2R[Register: POS 1]
    L2R --> L2T[SensePass tag]
    L2R --> L2C[Card terminal / PinPad]
    L3 --> W[Web checkout, payment links]
```

| Area            | How it is set up                                                                                               |
| --------------- | -------------------------------------------------------------------------------------------------------------- |
| Payment methods | Per location: the same set everywhere, or a different processor account per store or region.                   |
| Store details   | Use the merchant's details; override the address and checkout settings per store.                              |
| Surcharge       | Stores: **In-store**, each with its own state. Online store: **E-commerce**, the customer's state at checkout. |
| Users           | HQ finance: Merchant Full Access. Store managers: Location Full Access.                                        |
| Reporting       | HQ sees every store; filter by store, register and payment method.                                             |

The online store is another location. Processor accounts can be shared or different per location, which also supports stores in several countries or currencies.

### Group of companies or brands

Several legal entities or brands under one HQ.

```mermaid
flowchart TD
    P[Partner: Group HQ] --> MA[Merchant: Brand A Ltd]
    P --> MB[Merchant: Brand B Inc]
    MA --> A1[Location: Store A1]
    MB --> B1[Location: Store B1]
    MB --> B2[Location: Online store B]
    A1 --> A1R[Register: POS 1]
    A1R --> A1T[SensePass tag]
    A1R --> A1C[Card terminal / PinPad]
    B1 --> B1R[Register: POS 1]
    B1R --> B1T[SensePass tag]
    B1R --> B1C[Card terminal / PinPad]
    B2 --> W[Web checkout, payment links]
```

| Area           | How it is set up                                                                                         |
| -------------- | -------------------------------------------------------------------------------------------------------- |
| Legal entities | One merchant per company, each with its own processor accounts and settlement.                           |
| Group HQ       | Set up as a partner linked to all group merchants: onboards stores, sets payment methods, creates users. |
| Surcharge      | Per location, using each company's own processing costs.                                                 |
| Users          | Brand finance: Merchant Full Access. Store managers: Location Full Access.                               |

### Franchise

Independent owners under one brand. There are two ways to set it up.

|             | A. Franchisee = merchant (recommended)                                                            | B. Franchisee = location                                                              |
| ----------- | ------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| Structure   | The franchisor is the partner. Each franchisee is its own merchant, and its stores are locations. | The brand is one merchant. Each franchisee's store is a location.                     |
| Settlement  | Each franchisee settles to its own bank account.                                                  | All payments are collected under one merchant account.                                |
| Data        | Each franchisee sees only its own data.                                                           | Less separation between owners; franchisee users are limited by Location Full Access. |
| When to use | Every franchise, by default.                                                                      | Only when the franchisor must collect all payments under one account.                 |

```mermaid
flowchart TD
    P[Partner: Brand HQ, franchisor] --> F1[Merchant: Franchisee 1 LLC]
    P --> F2[Merchant: Franchisee 2 LLC]
    F1 --> S12[Location: Store 12]
    F2 --> S15[Location: Store 15]
    S12 --> S12R[Register: POS 1]
    S12R --> S12T[SensePass tag]
    S12R --> S12C[Card terminal / PinPad]
    S15 --> S15R[Register: POS 1]
    S15R --> S15T[SensePass tag]
    S15R --> S15C[Card terminal / PinPad]
```

**Who controls what (option A):**

| Area            | Franchisor (partner)                                      | Franchisee (merchant)                                       |
| --------------- | --------------------------------------------------------- | ----------------------------------------------------------- |
| Onboarding      | Creates the franchisee, its stores, registers and devices | -                                                           |
| Payment methods | Sets the brand's standard list of payment methods         | Own processor account per store                             |
| Checkout look   | Brand header, colors and payment method order             | -                                                           |
| Surcharge       | Configured per franchisee store                           | Own processing costs, the store's state rules               |
| Users           | Partner users for the brand team                          | Owner: Merchant Full Access. Managers: Location Full Access |
| Day to day      | A Backoffice user per franchisee                          | Own transactions, refunds, payment requests and reports     |
| POS vendor      | Can be linked as a second partner                         | Uses the integrated POS as usual                            |

### Fleets of trucks or vans

A truck franchise follows option A: the brand HQ is the partner, each franchisee is its own merchant, and each truck or website the franchisee runs is a location.

```mermaid
flowchart TD
    P[Partner: Brand HQ] --> F1[Merchant: Franchisee 1 LLC]
    P --> F2[Merchant: Franchisee 2 LLC]
    F1 --> T1[Location: Truck 01]
    F1 --> W[Location: Website]
    F2 --> T3[Location: Truck 03]
    T1 --> T1R[Register: Truck 01]
    T1R --> T1T[SensePass tag]
    T1R --> T1C[Card terminal / PinPad]
    T3 --> T3R[Register: Truck 03]
    T3R --> T3T[SensePass tag]
    T3R --> T3C[Card terminal / PinPad]
    W --> WC[Web checkout, payment links]
```

| Area       | How it is set up                                                                                    |
| ---------- | --------------------------------------------------------------------------------------------------- |
| Franchisee | Its own merchant: own settlement, own data, any number of trucks.                                   |
| Truck      | A location with its own register; on the register, a card terminal (PinPad) and/or a SensePass tag. |
| Website    | An e-commerce location: web checkout and payment links.                                             |
| Surcharge  | Truck: its operating state. Website: the customer's state at checkout.                              |
| Users      | Franchisee owner: Merchant Full Access. Driver: Location Full Access.                               |

{% hint style="info" %}
**Tip:** A truck that regularly works in more than one state can get a location per state, so the right surcharge rules apply.
{% endhint %}

### A platform that serves stores

For POS vendors, ISVs, resellers and distributors that bring stores onto SensePass.

```mermaid
flowchart TD
    P[Partner: Your POS / ISV platform] --> A[Merchant: Store customer A]
    P --> B[Merchant: Store customer B]
    A --> A1[Location: Main store]
    B --> B1[Location: Store B1]
    A1 --> A1R[Register: from your POS]
    A1R --> A1T[SensePass tag]
    A1R --> A1C[Card terminal / PinPad]
    B1 --> B1R[Register: from your POS]
    B1R --> B1T[SensePass tag]
    B1R --> B1C[Card terminal / PinPad]
```

| Area            | How it is set up                                                                                                                         |
| --------------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Onboarding      | Add each store in SensePass Partners or with the Partner API.                                                                            |
| Integration     | Your POS integration sends payments; registers are created from your POS (POS Paired), each with its card terminal and/or SensePass tag. |
| Payment methods | Per store location, with each store's own processor account.                                                                             |
| Surcharge       | Enabled store by store, with the store's processing costs.                                                                               |
| Users           | Your team: partner users. Each store: its own Backoffice users.                                                                          |

Every store is its own merchant, so data and settlement stay separate per store, while you manage the whole portfolio. A store can be linked to more than one partner, for example the POS vendor and a local reseller.

### From structure to first payment

| Step                      | What you do                                                                 |
| ------------------------- | --------------------------------------------------------------------------- |
| 1. Create the merchant    | Business details and defaults.                                              |
| 2. Add locations          | Name and number; use the merchant's details or override them.               |
| 3. Payment methods        | Per location, with the processor credentials.                               |
| 4. Registers              | One per checkout point: Standalone or paired with your POS.                 |
| 5. Devices                | On each register: pair a SensePass tag and/or add a card terminal (PinPad). |
| 6. Checkout and surcharge | Branding, payment page options, surcharge rules.                            |
| 7. Users                  | Merchant or location access, refund confirmation.                           |

Repeat steps 2 to 5 for every additional location. Partners do these steps in SensePass Partners: see the **Partner Dashboard guide**. To map your structure with us, contact <support@sensepass.com>.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sensepass.com/sensepay/get-started/choose-your-account-structure.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
