> 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/the-five-levels.md).

# The five levels

Every SensePass account is built from the same five levels. Knowing them helps you set up a new business in the right order and give each person the right access.

```mermaid
flowchart TD
    P[Partner] --> M1[Merchant]
    P --> M2[Merchant]
    M1 --> L1[Location]
    M1 --> L2[Location]
    L1 --> R1[POS / Register]
    L1 --> R2[POS / Register]
    L2 --> R3[POS / Register]
    R1 --> T1[SensePass tag]
    R1 --> C1[Card terminal / PinPad]
    R2 --> T2[SensePass tag]
    R2 --> C2[Card terminal / PinPad]
    R3 --> T3[SensePass tag]
    R3 --> C3[Card terminal / PinPad]
```

### The five levels

| Level              | What it is                                                                                                           | Good to know                                                                                                                                                                                                                                              |
| ------------------ | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Partner**        | The organization that onboards and manages merchants: a POS vendor, ISV, reseller, franchisor or group HQ.           | A partner is linked to many merchants. A merchant can also work with more than one partner, for example a POS vendor and a reseller.                                                                                                                      |
| **Merchant**       | The business entity. Holds the business details, default settings, Backoffice users and all transaction reporting.   | Create one merchant per legal entity, or per account that settles separately.                                                                                                                                                                             |
| **Location**       | A store, branch, site, online store or vehicle. Holds the payment methods, processor accounts and checkout settings. | A new location uses the merchant's details unless you override them.                                                                                                                                                                                      |
| **POS / Register** | A checkout point in a physical location, such as a counter, a lane or a truck.                                       | Created on its own (**Standalone**: the customer enters the amount) or paired with your POS (**POS Paired**: the amount comes from the POS). Registers are for physical locations; an online store takes payments through web checkout and payment links. |
| **Devices**        | What the customer pays with at the register: a **SensePass tag** (NFC / QR) and/or a **card terminal (PinPad)**.     | A register can have a tag, a card terminal, or both. Tags are paired on the register; card terminals are added as EMV terminals.                                                                                                                          |

{% hint style="info" %}
**Tip:** Settling to more than one bank account is usually the signal that you need a separate merchant. Many sites with the same owner are usually locations of one merchant.
{% endhint %}

### What is set at each level

| Setting                                    | Partner       | Merchant             | Location                       | POS / Register     | Devices  |
| ------------------------------------------ | ------------- | -------------------- | ------------------------------ | ------------------ | -------- |
| Merchant portfolio and onboarding          | Set here      | -                    | -                              | -                  | -        |
| Business details                           | -             | Default              | Use the merchant's or override | -                  | -        |
| Payment methods and processor accounts     | -             | -                    | Set here                       | -                  | -        |
| Payment page and checkout options          | -             | Default              | Use the merchant's or override | -                  | -        |
| Surcharge                                  | -             | Default              | Use the merchant's or override | -                  | -        |
| Receipts                                   | -             | Default              | Use the merchant's or override | -                  | -        |
| Users                                      | Partner users | Merchant Full Access | Location Full Access           | -                  | -        |
| Register type (Standalone / POS Paired)    | -             | -                    | -                              | Set here           | -        |
| Tag pairing, card terminals (EMV / PinPad) | -             | -                    | -                              | -                  | Set here |
| Transactions and reports                   | -             | All locations        | Filter by location             | Filter by register | -        |

In short: payment methods and processor accounts live at the **location**. Business identity, defaults and reporting live at the **merchant**. The **partner** manages the portfolio. The **register** and its **devices** show where a payment started.

### Set once at the merchant, override where needed

A new location starts from the merchant's settings. Only the values you change are stored on the location, so a change that applies to the whole business is made once, at the merchant.

**Example:** a merchant with an airport store.

|                   | Merchant default               | Airport store (location)                                     | What the customer gets |
| ----------------- | ------------------------------ | ------------------------------------------------------------ | ---------------------- |
| Business details  | Retail Co, head office address | **Override Merchant Details** selected, address "Terminal 3" | Airport store address  |
| Checkout branding | Brand standard                 | Not changed                                                  | Brand standard         |
| Send By SMS       | On                             | Not changed                                                  | On                     |

To override at the location, open the location in SensePass Partners and select **Override Merchant Details**, or use the location's **Settings**, **Surcharge** and **Receipts** pages.

### Next steps

* **Users and access**: who can see and do what.
* **Choose your account structure**: examples for single stores, chains, groups, franchises, fleets and platforms.


---

# 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/the-five-levels.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.
