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 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.
Technical requirements
The general integration of Wero can only be done via the Payment Page and requires the following things to be noted:
Spec-Version 1.38, or higher is required.
The
Payment.OrderIdparameter is mandatory.Maximum length for Wero is 35 characters.
While not mandatory, it is also highly recommended to use
Payment.PayerNote, as it is displayed during checkout.
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.
Refunds are currently not supported and will be delivered at a later date.
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, if you want to test Wero.
Last updated
Was this helpful?
