> 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/payment-methods/eps.md).

# eps

eps is a third-party means of payment by the Austrian banks. To process eps via the Saferpay JSON API, a few things must be observed.

## General requirements

The handling of eps payments with Saferpay requires:

* A [corresponding license](/home/master/licensing.md) and thus a valid identification with a username and password for the Saferpay system.
* Availability of at least one active Saferpay terminal via which payment can be carried out and availability of the associated Saferpay TerminalId.
* A valid acceptance agreement for eps.

For eps activation Saferpay needs:

* Your eps Merchant ID.
* Your eps IBAN.
* Your eps BIC.
* Your eps PIN.
* The currency your customers will purchase with eps.
* Your Saferpay Customer ID.
* The ID of the Saferpay eCommerce Terminal eps has to be added.

{% hint style="info" %}
For eps activation on the Saferpay terminal, please [**inform our customer service**](/home/integration-guide/support.md#customer-services) about your eps credentials and the desired currency.
{% endhint %}

### Technical requirements

The general integration of eps can only be done via the [Payment Page](/home/integration-guide/licences-and-interfaces/payment-page.md) and requires the following things to be noted:

* The notification URLs inside the **`Notification`** container are **mandatory** in order to avoid missing payment successes. See the [Payment Page process](https://docs.saferpay.com/home/integration-guide/payment-methods/pages/-Me4jFEJClrxX7AII0gz#notification.successnotifyurl-and-notification.failnotifyurl) for further information.
* Transactions made before **18.05.2021** cannot be refunded as they're made via an old protocol version!
* Sometimes, Saferpay will not receive the information necessary from eps to be able to do a refund. In this case a refund will also not be possible!
* Only [referenced refunds](/home/integration-guide/licences-and-interfaces/transaction-interface/refunds.md#method-1-referenced-refunds) are possible as eps does not support the generation of an alias.
* eps does not support the [iframe integration](/home/integration-guide/general-information/iframe-integration-and-css.md#iframe-integration). [Saferpay will break out of the iframe if necessary](/home/integration-guide/general-information/iframe-integration-and-css.md#iframe-support).

Furthermore, for other flows (Refunds etc.), please refer to the table below.

## Supported features

| Feature                                                                                     |                                                          Support                                                          |
| ------------------------------------------------------------------------------------------- | :-----------------------------------------------------------------------------------------------------------------------: |
| Capture/Cancel                                                                              |                                                             ❌                                                             |
| Multipart Captures                                                                          |                                                             ❌                                                             |
| Secure Card Data                                                                            |                                                             ❌                                                             |
| [Refunds](/home/integration-guide/licences-and-interfaces/transaction-interface/refunds.md) | <p>✅</p><p><a href="/home/integration-guide/payment-methods/eps.md#integration"><strong>Needs attention!</strong></a></p> |
| Recurring Payments                                                                          |                                                             ❌                                                             |
| 3D Secure                                                                                   |                                                             ❌                                                             |
| Dynamic Currency Conversion                                                                 |                                                             ❌                                                             |
| Mail Phone Order                                                                            |                                                             ❌                                                             |
| [Testing](#testing)                                                                         |                                                             ✅                                                             |
| Omni-Channel                                                                                |                                                             ❌                                                             |

## Testing

Please refer to [this chapter](/home/integration-guide/testing-and-go-live.md#eps) if you want to test eps.


---

# 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/integration-guide/payment-methods/eps.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.