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

# FAQ

## Accounts and sign-in

**How do I get a user for the Merchant Dashboard?** Your business administrator or SensePass partner creates your user and gives you a temporary password. The Merchant Dashboard is at <https://merchant.sensepass.com>.

**I forgot my password. What do I do?** Click **Forgot Password?** on the sign-in screen, or ask your administrator to set a new one. Partners reset passwords in SensePass Partners under **Management** > **Backoffice Users** > **Change Password**.

**Why am I asked for a code by SMS?** If your user has MFA, a code is sent to your phone the first time you sign in from a new device.

**How do I change the display language?** Click your name at the top right and select **Locale**.

## Sandbox and Production

**What is the difference between Sandbox and Production?** Sandbox is for testing and no real money moves. Production is the live environment. Merchants, users, tags and API keys in one environment do not exist in the other. See **Sandbox and Production** in Get started.

**How do I get a Sandbox account?** Every partner gets a Sandbox account. Merchants can ask their SensePass partner for a Sandbox user.

## Payments

**What ways can I take a payment?** From the Merchant Dashboard you can send a payment request (a payment link by SMS and/or email) or take a payment now with the **Digital Terminal**. At a register, the customer taps or scans a SensePass tag, or pays on a card terminal (PinPad). Online stores use web checkout and payment links.

**What types of payment request are there?** Payment, Capture+Tokenize, Tokenization and Authorization. See **Payment requests** in the Merchant Dashboard pages.

**Can I send many payment requests at once?** Yes. Use **Bulk Upload** on the payment request screen with the Excel template (.xlsx, up to 1 MB).

**What happens when a customer taps a SensePass tag?** On a **Standalone** register, the customer enters the amount and reason. On a **POS Paired** register, the amount comes from the POS or platform, and the customer sees the payment page (or a waiting page until the transaction arrives).

## Refunds

**Can I refund part of a payment?** Yes. Open the transaction details, click **Refund** and choose **Partial Refund**. The window shows how much you can still refund.

**Can I cancel a refund?** No. A refund cannot be undone. Check the amount before you confirm.

**When does the customer get the money back?** The refund is processed right away. The money reaches the customer according to their bank's timing.

**Why do I need to enter a password or SMS code to refund?** Your administrator sets how each user confirms refunds: password, SMS code or no confirmation.

## Set-up (partners)

**Where do I set up payment methods?** In SensePass Partners, per location: open the location's three-dot menu and select **Payment Methods**. The credentials come from the payment processor, not from SensePass.

**How do I connect a SensePass tag?** Create a POS / Register in the location and pair the tag by its serial or by scanning its QR code. See **Creating a POS / Register and pairing a SensePass tag**.

**Who should get an API key?** Only the developer who sets up the integration. Treat every API key as a secret and never send it by unsecured email or chat.

**Who is responsible for surcharges?** You are responsible for making sure surcharges and service fees comply with card network rules and local laws.


---

# 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/resources/faq.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.
