> For the complete documentation index, see [llms.txt](https://docs.saferpay.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saferpay.com/home/interfaces/backoffice/transactions/sepa-refunds-export.md).
# SEPA Refunds Export
Saferpay does offer the possibility to accept refunds for certain SEPA-based payment methods. However, those need special attention. Reason being that SEPA does not directly offer refunds, which is just in the nature of the payment system itself. Due to this, Saferpay offers a workaround to make manual SEPA refunds easier for the merchant.
{% hint style="warning" %}
Before this feature can be used, it must be activated under [**Settings > Processing**](/home/interfaces/backoffice/settings.md#processing)**.**
{% endhint %}
Each SEPA-based refund is filed into this special journal, where you - the merchant - can request an export of these transactions by either selecting the transactions you want, or you simply export all the new refunds that haven't been exported yet.
## Example Export
{% hint style="warning" %}
This export was created on the Saferpay Test Environment and does not include real bank account information! It can merely be used to get an understanding of the file format.
{% endhint %}
{% hint style="warning" %}
Not all banks may support this upload feature. Please contact your bank for further information.
{% endhint %}
{% file src="/files/-McK8CSKUSaea4D6AiFC" %}
Example SEPA-Refund File Export
{% endfile %}
---
# 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.saferpay.com/home/interfaces/backoffice/transactions/sepa-refunds-export.md?ask=&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.