> 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/merchants/merchant-dashboard/refunds.md).

# Refunds

You can refund an approved transaction in full or in part from its details page.

1. Open the transaction details (see **Transactions**) and click **Refund**.
2. Select **Full Refund** (refund the full amount to the customer) or **Partial Refund** (refund only part of the amount).
3. For a partial refund, enter the amount in **Enter refund amount**. The window shows the **Current balance** you can still refund. Click **Continue**.
4. Check the amount on the **Confirm Refund** screen. Optionally, enter a reason in **Enter Reason for Refund**. Click **Continue**.
5. Confirm the refund. Depending on your user settings, enter your password or the code sent to your phone by SMS, then click **Continue**. Some users do not need to confirm.
6. The refund is processed right away. A **Refund** line is added to **Payments** in the transaction details.

{% hint style="info" %}
**Note:** How you confirm a refund (password, SMS code or no confirmation) is set for each user by your administrator. The money reaches the customer according to their bank's timing.
{% endhint %}

{% hint style="warning" %}
**Important:** A refund returns money to the customer and cannot be undone. Check the amount before you confirm.
{% 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/merchants/merchant-dashboard/refunds.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.
