> 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/get-started/glossary.md).

# Glossary

| Term                   | Meaning                                                                                                                                        |
| ---------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Partner                | The organization that onboards and manages merchants: a POS vendor, ISV, reseller, franchisor or group HQ.                                     |
| Merchant               | The business entity that accepts payments through SensePass. One per legal entity or per account that settles separately.                      |
| Location               | One site or unit of a merchant, such as a store, branch, online store or vehicle.                                                              |
| POS / Register         | A checkout point in a physical location. Standalone or POS Paired. A SensePass tag and/or a card terminal (PinPad) is set up under a register. |
| Card terminal (PinPad) | An EMV card reader added to a register as an EMV terminal.                                                                                     |
| SensePass tag          | An NFC / QR tag that a customer taps or scans to pay. It has a 9-character code (XXX-XXX-XXX) printed under the QR code.                       |
| Merchant Dashboard     | The merchant web portal for transactions, refunds, payment requests, the Digital Terminal, customers and products.                             |
| SensePass Partners     | The partner web portal for merchants, locations, registers, users and API keys.                                                                |
| Backoffice user        | A person who signs in to the Merchant Dashboard, with Merchant Full Access or Location Full Access.                                            |
| Digital Terminal       | The Merchant Dashboard screen for taking a payment while the customer is present.                                                              |
| Payment request        | A payment link sent to the customer by SMS and/or email. Types: Payment, Capture+Tokenize, Tokenization and Authorization.                     |
| Refund confirmation    | How a user confirms a refund: SMS Verification, Password or No Confirmation.                                                                   |
| Registration link      | A link SensePass sends to a new merchant to open the registration wizard.                                                                      |
| Welcome pack           | A download at the end of registration with usernames, temporary passwords and location API keys. Keep it confidential.                         |
| Sandbox                | The test environment. No real money moves.                                                                                                     |
| Production             | The live environment.                                                                                                                          |
| API key                | A credential for API calls. A merchant API key also needs a branchId; a location API key does not.                                             |
| Terminal Agent         | Windows software that connects a POS or pinpad to SensePass.                                                                                   |
| Payment Commit         | The back-end step that confirms and completes a payment.                                                                                       |
| Callback (webhook)     | A server-to-server notification sent to the merchant's URL.                                                                                    |
| Token                  | A stored card reference used instead of the card number.                                                                                       |
| Surcharge              | A fee added to card payments where it is allowed.                                                                                              |
| AVS                    | Address Verification Service: a card-not-present check of the billing address.                                                                 |
| BIN                    | Bank Identification Number: the first digits of a card number, which identify the issuer.                                                      |


---

# 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/get-started/glossary.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.
