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

# Resources

Help for merchants, partners and developers who use SensePass.

| Page                | Use it to                                                    |
| ------------------- | ------------------------------------------------------------ |
| **FAQ**             | Find quick answers to common questions                       |
| **Troubleshooting** | Fix common problems with sign-in, payments, refunds and tags |

## Contact support

Email SensePass Support at **<support@sensepass.com>**, or contact your SensePass account manager or partner.

To help us answer quickly, include:

* Your business name and location
* Whether it happened in **Sandbox** or **Production**
* The transaction number, if there is one (you can copy it from the transaction details in the Merchant Dashboard)
* What you did, what you expected and what happened, with a screenshot if you can

{% hint style="danger" %}
**Never send** passwords, API keys, full card numbers or other secrets to Support.
{% endhint %}


---

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