> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-nordics/tcs-client/refunds/how-to-approve-or-reject-a-refund-request.md).

# How to Approve or Reject a Refund Request

Approve or reject refund requests in TCS so they can be processed.

{% hint style="info" %}
**Use this when** a refund request is waiting for approval in TCS.
{% endhint %}

{% hint style="warning" %}

* **Refund requests must always be approved before they're processed.**
* You **can't approve your own** refund requests. The only exception is the root user.
  {% endhint %}

{% stepper %}
{% step %}

### Open Refund requests

Click the **Refund requests** tab. You'll see all requests waiting for approval, and requests that have already been processed.

<figure><img src="https://content.gitbook.com/content/H3VBt0P9E0VJDk5TJ2jp/blobs/0ZEbjt2X8srYkZuXPZCq/tcs-refund-requests.png" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Process the request

Click **Process** next to the request.
{% endstep %}

{% step %}

### Approve or reject

In the pop-up window, enter a **reply** — this field can't be left empty — then click **Approve refund** or **Reject refund**.

<figure><img src="https://content.gitbook.com/content/H3VBt0P9E0VJDk5TJ2jp/blobs/Z1iq3UgdiOkM0vTU8Z9l/tcs-process-refund-request.png" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

For who can approve refunds, see [User Roles and Permissions](/support-nordics/tcs-client/user-management/user-roles-and-permissions.md).

<details>

<summary>Keywords</summary>

Also called: approve refund, reject refund, refund request, process refund. Search terms: approve, reject, refund request, process, root user.

</details>


---

# 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.verifone.com/support-nordics/tcs-client/refunds/how-to-approve-or-reject-a-refund-request.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.