> 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/integration-guide/licences-and-interfaces/transaction-interface/refunds/sepa-refunds.md).

# SEPA Refunds

Saferpay does offer the possibility to accept refunds for certain SEPA-based payment methods. However, those need special attention. SEPA does not natively support refunds. Due to this, Saferpay offers a workaround to make manual SEPA refunds easier for the merchant.

## Supported payment methods

The following payment methods are supported:

* [SEPA Direct Debit](/home/integration-guide/payment-methods/sepa-direct-debit.md)
* [SOFORT by Klarna](broken://pages/-Me-qXuBnE3GLyVLwwv2)

## Activation

Before you -the merchant- can start accepting refunds, they need to be activated inside the Saferpay Backoffice: 

![(click to enlarge)](/files/sh45PvmkPBmdOgKQgiVs)

## Executing refunds

Once the activation has been done, you can execute refunds, like any other payment method. Either [via API](/home/integration-guide/licences-and-interfaces/transaction-interface/refunds.md) or [inside the Saferpay Backoffice](/home/interfaces/backoffice/transactions/journal-details.md#refund).

{% hint style="warning" %}
When using the API, please make sure to use the[ Referenced Refund](/home/integration-guide/licences-and-interfaces/transaction-interface/refunds.md#method-1-referenced-refunds) method, as the Alias method can lead to issues.
{% endhint %}

## Uploading the refunds into your online-banking

This is where SEPA refunds deviate from other payment methods, like credit cards. As mentioned before, SEPA does not offer direct refunds via the processing itself. This is why Saferpay first collects all executed refunds inside the Backoffice: 

![(click to enlarge)](https://raw.githubusercontent.com/saferpay/sndbx/master/images/BO_Manual_Refund_Export.png)

These refunds then need to be exported into a special XML file, which can be done right there inside the Backoffice. The created XML-file can then be uploaded into your online banking-portal, which executes these refunds in a batch, eliminating the need perform them manually. 

{% hint style="info" %}
This XML file follows [ISO 20022](https://en.wikipedia.org/wiki/ISO_20022). Also [see official message-specification](https://www.iso20022.org/sites/default/files/documents/D7/ISO20022_RTPG_pacs00800106_July_2017_v1_1.pdf).
{% endhint %}

{% file src="/files/-MeA5gYwd0frDQmC0AfF" %}
Example File
{% endfile %}

{% hint style="danger" %}
SEPA-refund-files from the test-environment cannot be uploaded into online-banking portals, since they only contain test-data, thus non-valid IBANs!
{% endhint %}

{% hint style="warning" %}
It may be necessary to contact your bank, to activate this import-feature! Some also may not offer it at all!
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.saferpay.com/home/integration-guide/licences-and-interfaces/transaction-interface/refunds/sepa-refunds.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.