WL SIPS DOCS

Release 22.5

go directly to content

Search by keywords

iDEAL integration

To search in the page use Ctrl+F on your keyboard

WL Sips is a secure multi-channel e-commerce payment solution that complies with the PCI DSS standard. It allows you to accept and manage payment transactions by taking into account business rules related to your activity (payment upon shipping, deferred payment, recurring payment, payment in instalments, etc.).

The purpose of this document is to explain the iDEAL means of payment integration into WL Sips.

This document is intended to help you implement the iDEAL means of payment on your e-commerce site.

  • If you have integrated the means of payment since October 2018, please refer to the document iDEAL payment guide (new contracts).
  • If you have integrated the means of payment before October 2018, you can consult this document.

It includes:

  • functional information for you
  • implementation instructions for your technical team

To get an overview of the WL Sips solution, we advise you to consult the following documents:

  • Functional presentation
  • Functionality set-up guide

iDEAL is a means of payment widely used in the Netherlands.

This means of payment allows customers to make online direct transfer purchases from their bank account.

In order to settle their order online, via iDEAL, the customers must first select their bank from a drop-down list. Once redirected to the interface of their bank, all they have to do is to authenticate themselves and confirm the bank transfer.

Moreover, the customers don't have to register for this service. They can use iDEAL directly if they are customer of one of the participating banks.

Payment channels
Internet V Default payment channel
MAIL_ORDER, TELEPHONE_ORDER X
Fax X
IVS X
Means of payment
Immediate payment V
End-of-day payment X
Deferred payment X
Payment upon shipping X
Payment in instalments X
Subscription payment X
Batch payment X
OneClick payment X
Currency management
Multicurrency acceptance X EUR only
Currency settlement X EUR only

In some use cases, the bank does not immediately decide on the payment response and returns a code 60, which means the transaction is in the process of validation. Therefore, when your customer navigates back to your website, you don't know whether you can deliver the goods. Upon receipt of the bank response, WL Sips sends you an automatic response with the final payment result, which lets you know if the iDEAL payment has been authorised or rejected.

Finally, for the "code 60" use cases, you receive 2 automatic response messages:

  • 1 message with the code 60 ;
  • 1 message with the definitive response code (response code 00 if the payment is accepted, other code if not accepted).

Example of an accepted payment page

In order to offer the iDEAL means of payment on your website, you have to sign an acceptance contract with Worldline Sweden. Thereafter, you transmit us the contract number for recording in our information system.

You can offer the iDEAL means of payment through the Sips Paypage which directly acts as the payment interface with customers via their web browser.

For iDEAL payments, it is not allowed to defer the remittance, you cannot adjust the date of funds transfer (immediate payment).

The diagram below explains the different transaction statuses according to the chosen capture mode:



if capture mode equals to AUTHOR_CAPTURE, moving to Author_capture, and then captured if respondecode equals to 00 else refused.

The payment process for Sips Paypage is described below:



The customer proceeds with the payment (order finalisation). After the customer is redirected to the SIPS payment page. The customer selects IDEAL, then selects his/her bank. He/she is redirected to his/her online bank for authentification. Then the customer is redirected back to SIPS payment finalisation. The receipt and the payment result are displayed. Also the customer is redirected to your website (manual response). The SIPS server sends an automatic response to your website (automatic response).

The following fields have a particular behaviour:

Field name Remarks/rules
captureMode Tհe value sent in the request is ignored.
The capture mode is forced to AUTHOR_CAPTURE.
captureDay Tհe value sent in the request is ignored.
The capture delay is forced to 0.
customerLanguage Allows to choose the language used on WL Sips and iDEAL pages.
paymentPattern Tհe value sent in the request is ignored.
The payment type is forced to ONE_SHOT.
statementReference The value sent will appear on your account statement. The allowed characters are [a-zA-Z0-9 /\+=.].

The following table summarises the different response cases to be handled:

Status Response fields Action to take
Payment accepted acquirerResponseCode = 00
authorisationId = (cf. the Data Dictionary).
paymentMeanType = CREDIT_TRANSFER
You can deliver the order.
Pending transaction acquirerResponseCode = (cf. the Data Dictionary). You must wait until you receive the second automatic response for this transaction to know its final status and whether you can ship the goods. If you do not receive the automatic response, you will need to check the transactions report regularly.
Acquirer refusal acquirerResponseCode = (cf. the Data Dictionary). The authorisation is refused for a reason unrelated to fraud.
If you have not opted for the "new payment attempt" option (please read the Functionality set-up Guide for more details), you can suggest that your customer pay with another means of payment by generating a new request.
Refusal due to the number of attempts reached responseCode = 75 The customer has made several attempts that have all failed.
Refusal due to a technical issue acquirerResponseCode = 90-98
responseCode = 90, 99
Temporary technical issue when processing the transaction. Suggest that your customer redo a payment later.

For the complete response codes (responseCode) and acquirer response codes (acquirerResponseCode), please refer to the Data dictionary.

The iDEAL means of payment acceptance is not available through the Sips Office solution.

The following operations are available on iDEAL transactions:

Cash management
Cancellation X The operation is not available because a transfer cannot be cancelled.
Validation X
Refund V
Duplication X
Credit X

The diagram below explains which cash management operation is available when a transaction is in a given status:



Partial repayment is possible in "CAPTURED" status and will keep the "CAPTURED" status. A total refund will change the status from "CAPTURED" to "CREDITED".

The reports provided by WL Sips allow you to have a complete and consolidated view of your transactions, cash management actions, accounting situation and chargebacks. You can use this information to consolidate your information system.

The availability of iDEAL transactions for each type of report is summarised in the table below:

Reports availability
Transactions report V
Operations report V
Reconciliations report V
Chargebacks report X
Note: for iDEAL transactions, the paymentMeanBrand field is populated with the value IDEAL.

You can view your iDEAL transactions and perform various cash management operations with Sips Office Extranet.

Here are the details of an iDEAL transaction:


reference, identifier, date, type, amount, server response and payment method

This site uses trackers to improve your experience, perform analysis and researches on your use of WL Sips documentation website.
You have several options:
Closing this banner you refuse the use of trackers on your device.

Configuration