iDEAL 2.0

iDEAL transactions can be processed via the Saferpay JSON API. However, as iDEAL is a third party provider, there are a few things to consider.

General requirements

The handling of iDeal 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.
An iDeal contract with Worldline. Others are not supported.

For iDeal activation on the Saferpay terminal, please contact your sales contact.

The general integration of iDEAL can only be done via the Payment Page and requires the following things to be noted:

The notification URLs, inside theNotification conatiner are mandatory, in order to avoid missing payment successes. See the Payment Page process for further information.
The parameter Payment.Payernote is mandatory. If it is not set, Saferpay will set the Saferpay Transaction.Id as its value.
The Payment.OrderId is limited to a length of 18 and no special characters. Saferpay will automatically filter any special character, to prevent issues.
iDEAL does not support the Iframe integration. Saferpay will break out of the IFrame, if necessary.
Refunds are technically not directly supported by iDeal. Due to that, Saferpay will perform the refund through other means. Thusly, the payer will not see the refund in their iDeal-App. Aside that, the refund is processed normally.

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

Feature

Support

Capture/Cancel

❌

Multipart Captures

❌

Secure Card Data

❌

Recurring Payments

❌

3D Secure

❌

Dynamic Currency Conversion (DCC)

❌

Mail Phone Order

❌

✅

Omni-Channel

❌

iDeal is integrated via the standard Payment Page integration.

Please refer to this chapter, if you want to test iDEAL.

Last updated 3 months ago

Was this helpful?