# Wero Wero 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 Wero payments with Saferpay requires: * A [corresponding license ](https://docs.saferpay.com/home/master/licensing)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 Wero contract * Currently available in Belgium, France and Germany. {% hint style="info" %} For Wero activation on the Saferpay terminal, please contact your account manager at our sales, or [the sales directly](https://docs.saferpay.com/home/support#worldline-sales-team). {% endhint %} ### Technical requirements The general integration of Wero can only be done via the [Payment Page](https://docs.saferpay.com/home/integration-guide/licences-and-interfaces/payment-page) and requires the following things to be noted: * **Spec-Version 1.38**, or higher is required. * The **`Payment.OrderId`** parameter is **mandatory**. * Maximum length for Wero is 35 characters. * [Refunds](https://docs.saferpay.com/home/integration-guide/licences-and-interfaces/transaction-interface/refunds) cannot be cancelled, once executed, even if the [capture](https://docs.saferpay.com/home/integration-guide/licences-and-interfaces/capture-and-daily-closing) has not been executed. * While not mandatory for payments, it is highly recommended to use `Payment.PayerNote`, as it is displayed during checkout. * However, **PayerNote is mandatory in Wero refunds** and can only include SEPA characters. {% hint style="info" %} Supported SEPA characters contain: Letters (a–z, A–Z), digits (0–9), and the symbols / ? : ( ) . , ' + - as well as whitespaces. {% endhint %} {% hint style="info" %} Saferpay will automatically **sanitize** submitted values. {% endhint %} {% hint style="info" %} If **`PayerNote`** has not been set, Saferpay will use the **`OrderId`** instead. {% endhint %} Furthermore, for other flows (Refunds etc.), please also refer to the table below. ### Supported features Unlike other payment methods, Weros featureset is highly dependent on a configured plan. So the following table will show the available featureset, based upon the configured plan for Wero.

Feature
Feature	Single Immediate	Event Dependent
Capture/Cancel	❌	✅
Multipart Captures	❌	✅
Secure Card Data	❌	❌
Refunds	✅	✅
Recurring Payments	❌	❌
3D Secure	❌	❌
Dynamic Currency Conversion (DCC)	❌	❌
Mail Phone Order	❌	❌
Testing	✅	✅
Omni-Channel	❌	❌

#### Adfditional Information about the different plans Due to their specific nature, different plans may also have additional features and restrictions, outside of the general requirements. * **Event Dependent:** * **Reservation times:** The maximum time-frame an authorization will be open for capture, is seven days, which can be set to a maximum of 10 days. Please make sure to capture your transaction within this time frame, otherwise the reserved money will be released. ## Testing Please refer to [this chapter](https://docs.saferpay.com/home/testing-and-go-live#wero), if you want to test Wero. --- # Agent Instructions: 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: ``` GET https://docs.saferpay.com/home/integration-guide/payment-methods/wero.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.