> 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/platforms/rmh-retail-management-hero.md).

# RMH (Retail Management Hero)

With the SensePass add-in for Retail Management Hero (RMH), customers pay an RMH POS sale by scanning or tapping the SensePass tag at the register and choosing how to pay on their phone.

## Requirements

| Item             | Requirement                                                                             |
| ---------------- | --------------------------------------------------------------------------------------- |
| Operating system | Windows 10 (64-bit) on the POS stations                                                 |
| RMH              | Retail Management Hero v3.11.11 or later                                                |
| .NET             | Microsoft .NET Framework 4.7.2                                                          |
| Database         | SQL Server 2014 or later (Express is allowed). The SQL Browser service must be running. |
| Other            | Internet connection and a SensePass account                                             |

## Before you install

Have these ready:

* The RMH version (in RMH Store Administrator, click **File** > **About**).
* The SQL Server details for the RMH database: server name or IP address, database name, login ID and password.
* The SQL Server port. The default is 1433.
* From SensePass: the **SensePass tag ID** for each register and the location **API key**.

## Install the add-in

1. Run the SensePass installation program on the POS station.
2. Review the welcome screen and click **Next**.
3. Enter the SQL Server details for your RMH database:
   * **Server**: the SQL Server address, for example `(local)` or an IP address
   * **Port Override** and **Port Number**: only if SQL Server does not use the default port
   * **Username**, **Password** and **Database**
4. Click **Test** to check the connection, then click **Install**.
5. Click **Next** and **Finish**.

## Configure each register

1. Open **SensePay Configuration Management** from the desktop.
2. Select the register number and enter the configuration password you received with the installation.
3. Under **Tenders**, click **Create Tender** and set:
   * **Type**: Credit, PayPal, Google Pay, Apple Pay or Other
   * **Display Order**: the position of the tender in the RMH tender window
   * **Code**: a unique ID, up to 17 characters
   * **Description**: the name shown in the RMH tender window, up to 25 characters
4. Click **Save Tender**.
5. Enter the **Tag ID** and **API Key** from SensePass, then click **Get Device ID**. The **Device ID** field fills in automatically.
6. Optional: on the **Misc** tab, turn on **Card on File** and **Automatically Save Customer Tokens**.
7. Click **Save**.

Each register has its own settings. Repeat for every register.

## Take a payment

1. In RMH POS, enter the amount in the SensePass tender and press **OK**.
2. The customer scans the QR code or taps the SensePass tag, chooses a payment method on their phone and clicks **Pay**.
3. The customer sees the result on the phone, and the sale completes in RMH POS.

The customer can split the payment across more than one card or payment method.

## Returns and voids

* **Void**: cancels a transaction from the same day. In RMH POS, click **Transaction** > **Recall Transaction**.
* **Return**: for a transaction from an earlier day, recall the original transaction (or press **F11**) and make a dependent return.

{% hint style="warning" %}
**Not supported:** debit transactions and independent returns (returns without the original transaction).
{% endhint %}

## Card on file

When **Card on File** is on, a customer's card can be saved as a token and used again.

1. Assign a customer to the sale and click **Assign Payer Token**.
2. Click **New Card**. The customer selects a payment method on their phone.
3. Next time, when that customer is assigned and you choose the credit tender, RMH offers the saved card.

## Receipts

The add-in installs two receipt templates for 40-column printers: `SensePay-RMH.xml` and `SensePay-RMHSinglePage.xml`. They are not turned on automatically. To use one, open RMH Store Manager, go to **Setup** > **Hardware** > **Receipt Formats**, edit the format and select the template next to **Sales**. If you already use a custom receipt, merge the changes instead.

## Troubleshooting the database connection

* Test the connection in RMH Store Administrator (**File** > **Configuration**).
* Use the server's IP address instead of its name.
* If SQL Server has more than one instance, add the instance name, for example `192.168.1.111\SQLEXPRESS`.
* If SQL Server does not use port 1433, enter the port in **Port Override**.
* Check that the firewall allows the SQL port.


---

# 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/platforms/rmh-retail-management-hero.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.
