> 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/eprzelewy.md).

# Przelewy24

Przelewy24 payments can be processed with Saferpay without much effort. This chapter describes what needs to be considered in this regard.

## General requirements

The handling of Przelewy24 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 Przelewy24 contract.

{% hint style="info" %}
For Przelewy24 activation on the Saferpay terminal, please contact your sales contact.
{% endhint %}

### Technical requirements

The general integration of Przelewy24 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:

* Payer email address is **mandatory**. This means that either `Payer.BillingAddress.Email` or `Payer.DeliveryAddress.Email` needs to be sent with the initial request, or captured through the respective form.
* The parameter **`OrderId`** is limited to 50 characters.
* The notification URLs, inside the`Notification` conatiner 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.

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

### Supported features

| Feature                                                                                                                                                                               |    Support   |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :----------: |
| [Capture](/home/integration-guide/licences-and-interfaces/capture-and-daily-closing.md)/[Cancel](/home/integration-guide/licences-and-interfaces/capture-and-daily-closing.md#cancel) | <p>❌<br></p> |
| Multipart Captures                                                                                                                                                                    |       ❌      |
| Secure Card Data                                                                                                                                                                      |       ❌      |
| [Refunds](/home/integration-guide/licences-and-interfaces/transaction-interface/refunds.md)                                                                                           |       ✅      |
| Recurring Payments                                                                                                                                                                    |       ❌      |
| 3D Secure                                                                                                                                                                             |       ❌      |
| Dynamic Currency Conversion (DCC)                                                                                                                                                     |       ❌      |
| Mail Phone Order                                                                                                                                                                      |       ❌      |
| [Testing](#testing)                                                                                                                                                                   |       ✅      |
| Omni-Channel                                                                                                                                                                          |       ❌      |

## Testing

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


---

# 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/eprzelewy.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.