> For the complete documentation index, see [llms.txt](https://docs.makapay.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.makapay.io/point-of-sale-pos/terminals.md).

# Businesses

A **business** is a virtual POS register tied to a single location. Each business gets its own URL that can be opened on a tablet, phone, or any browser. Businesses are identified by a **short code** -- a human-readable label, not a password.

## Creating a Business

Navigate to **Dashboard > POS > Businesses** and click **Create Business**.

### Required Fields

| Field                | Description                                  | Rules                                                          |
| -------------------- | -------------------------------------------- | -------------------------------------------------------------- |
| **Location**         | Display name for the business (its location) | Free text (e.g., "Front Counter", "Downtown Branch")           |
| **Short Code**       | Unique identifier for this business          | 1-10 characters, letters and numbers only, stored as UPPERCASE |
| **Merchant Address** | Wallet address where payments are received   | Must be a valid wallet address                                 |

### Optional Fields

| Field                | Description                                                                                                                                        |
| -------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Default Chain**    | Pre-selected blockchain network for payments                                                                                                       |
| **Default Token**    | Pre-selected token for payments                                                                                                                    |
| **Allowed Cashiers** | Restrict which cashiers can log into this business (see [Cashier Restrictions](https://docs.makapay.io/point-of-sale-pos/cashier-restrictions.md)) |
| **Restrict Tokens**  | Restrict which tokens are available on this business (see [Token Restrictions](https://docs.makapay.io/point-of-sale-pos/token-restrictions.md))   |
| **Tipping**          | Ask customers for a tip at checkout with preset percentages or a custom amount (see [Tipping](https://docs.makapay.io/point-of-sale-pos/tips.md))  |

## What a Business Looks Like

> **Business: Front Counter**
>
> **Important:** The short code (`FC`) is NOT a password. It's just a label that appears in Order IDs and reports. The cashier PIN is the password.

| Setting          | Value              |
| ---------------- | ------------------ |
| Location         | Front Counter      |
| Short Code       | `FC`               |
| Wallet           | `0x1234...abcd`    |
| URL              | `/pos/term_abc123` |
| Allowed Cashiers | John, Sarah        |

## Business Short Code

The short code is **not a password**. It is a human-readable identifier that:

* Appears in every Order ID created at that business (e.g., `POS-FC-JD-1707842400000`)
* Helps merchants track which business processed a payment
* Must be unique across your businesses
* Is automatically converted to uppercase

**Good short code examples:** `FC` (front counter), `DRIVE`, `MAIN`, `BAR`, `R1`, `R2`

## Business URL

Each business gets a unique URL:

```
https://your-domain.com/pos/{terminalId}
```

The `terminalId` is a system-generated unique identifier (format: `term_<random>`), different from the short code. Share this URL or bookmark it on your POS device.

## Managing Businesses

### Edit a Business

Click the edit button on any business to change:

* Location
* Short code
* Default chain/token
* Allowed cashiers (see [Cashier Restrictions](https://docs.makapay.io/point-of-sale-pos/cashier-restrictions.md))
* Allowed tokens (see [Token Restrictions](https://docs.makapay.io/point-of-sale-pos/token-restrictions.md))

### Deactivate a Business

Deactivating a business:

* Prevents cashiers from logging in
* Ends all active sessions on that business
* Does not delete payment history
* Can be reactivated later

## Multiple Businesses

A merchant can create as many businesses as needed. Common setups:

| Setup                   | Businesses                      |
| ----------------------- | ------------------------------- |
| Single register         | `R1`                            |
| Two registers           | `R1`, `R2`                      |
| Counter + drive-through | `CTR`, `DRIVE`                  |
| Multiple locations      | `LOC1-R1`, `LOC1-R2`, `LOC2-R1` |


---

# 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.makapay.io/point-of-sale-pos/terminals.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.
