> 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/cashiers.md).

# Cashiers

A **cashier** is a person who operates a POS business. Each cashier has a name, a short code for identification, and a numeric PIN for logging in.

## Creating a Cashier

Navigate to **Dashboard > POS > Cashiers** and click **Create Cashier**.

### Required Fields

| Field          | Description       | Rules                                                          |
| -------------- | ----------------- | -------------------------------------------------------------- |
| **Name**       | Display name      | Free text (e.g., "John Doe", "Sarah")                          |
| **Short Code** | Unique identifier | 1-10 characters, letters and numbers only, stored as UPPERCASE |
| **PIN**        | Login code        | **8 or more digits, numbers only**                             |

### Important Rules

* **PIN is numbers only.** No letters, no special characters. Just digits.
* **PIN must be at least 8 digits** (e.g., `12345678`).
* **Each PIN must be unique.** No two cashiers can share the same PIN, because the system identifies cashiers by their PIN at login.
* **Short codes must be unique** per merchant.

## Short Code vs PIN (Important!)

> **Short Code** = A label. NOT secret. Shows in Order IDs and reports.
>
> **PIN** = A password. SECRET. Numbers only. Used to log in.

|              | Short Code                    | PIN                     |
| ------------ | ----------------------------- | ----------------------- |
| **What**     | A label / identifier          | A login password        |
| **Format**   | Letters + numbers (e.g. `JD`) | Numbers only, 8+ digits |
| **Secret?**  | No                            | Yes                     |
| **Used for** | Tracking in Order IDs         | Logging into business   |

**The short code is a label. The PIN is a password.**

## Managing Cashiers

### Edit a Cashier

You can change:

* Name
* Short code
* Active/inactive status

You **cannot** view a cashier's current PIN. PINs are hashed and cannot be retrieved.

### Reset a PIN

If a cashier forgets their PIN:

1. Go to **Dashboard > POS > Cashiers**
2. Click the cashier's menu and select **Reset PIN**
3. Enter a new PIN (8+ digits)
4. The cashier's old PIN no longer works
5. All active sessions for that cashier are terminated

### Deactivate a Cashier

Deactivating a cashier:

* Prevents them from logging into any business
* Ends all their active sessions
* Does not delete payment history
* Can be reactivated later

## Cashier Accountability

Every payment created by a cashier is tracked via the Order ID:

```
POS-R1-JD-1707842400000
         ^^
         Cashier short code
```

This means merchants can:

* See which cashier processed each payment
* Filter payment history by cashier
* Audit cashier activity across businesses


---

# 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/cashiers.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.
