> 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/partners/partner-dashboard/creating-a-pos-register-and-pairing-a-sensepass-tag.md).

# Creating a POS / Register and pairing a SensePass tag

A POS / Register is a checkout point in a location. To connect a SensePass tag to a location, you create a register and pair the tag with it.

1. Open the location's three-dot menu and select **POS / Register**.
2. Click **+ Create POS / Register**. The **Create POS / Register** window opens.
3. In **POS / Register Name**, enter a name you will recognize, for example *Front Counter*.
4. In **POS Vendor**, keep **Standalone** if the merchant does not use a POS system with SensePass.
5. In **Type**, select the register type. See the table below.
6. Check that **Location** shows the correct location.
7. Pair the tag using one of the options below.
8. Click **Save**.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2F0rfP4g8AS6Ef3pW3brBf%2Fp-register-filled.png?alt=media" alt="Create POS / Register: name, POS Vendor, Type, Location and Serial"><figcaption><p>Create POS / Register: name, POS Vendor, Type, Location and Serial</p></figcaption></figure>

| Type       | What the customer sees after tapping the tag                                                                                                                                               |
| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Standalone | A page where the customer enters the amount and the reason for the payment. Use it when no POS sends the amount.                                                                           |
| POS Paired | The amount and transaction come from the POS or platform. If the transaction has not arrived yet, the customer sees a waiting page. If it has arrived, the customer sees the payment page. |

**Pairing Mode** has two options: **QR Code** and **Serial**.

**Option A: select or type the tag serial**

1. In **Pairing Mode**, keep **Serial**.
2. Click the **Serial** field. A list of tags opens. Type part of the serial to find the tag, then select it.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FW4tP1tnOogDH49r47cuq%2Fp-register-serial-list.png?alt=media" alt="The Serial list. Type to search, then select the tag."><figcaption><p>The Serial list. Type to search, then select the tag.</p></figcaption></figure>

**Option B: scan the tag**

1. Click **Scan** and scan the QR code on the SensePass tag with your device's camera.

{% hint style="warning" %}
**Important:** After you click **Save**, the tag is paired with this register and location. Make sure you pair each tag with the correct location.
{% endhint %}

The new register appears in the list with **Has Box** set to **Yes**, which shows that a tag is paired.

<figure><img src="https://3556089516-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbqMA3Kf8t2xEX9F6y9%2Fuploads%2FFNNm5i07DHu3nBt0RwhZ%2Fp-register-created.png?alt=media" alt="The new register in the POS / Register list (device identifier hidden)"><figcaption><p>The new register in the POS / Register list (device identifier hidden)</p></figcaption></figure>


---

# 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/partners/partner-dashboard/creating-a-pos-register-and-pairing-a-sensepass-tag.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.
