About iDEAL

General information about iDEAL

Like giropay in Germany, Dutch banks established the iDEAL money transfer standard. Approximately 50% of all e-commerce payments in the Netherlands are processed with iDEAL. Offering iDEAL is a vital success factor for e-commerce business wanting to sell in the Netherlands. The customer is using the familiar and trusted online banking of its own credit institution, just the same as with online banking.

With online banking, the data disclosed in the online transfer is encrypted with SSL (Secure Sockets Layer) to prevent manipulation.

Further information can be found on iDEAL-website in Dutch and English (www.ideal.nl).

Specific requirement iDEAL Mobile: Redirect to Issuer (no in-app browser)

The Merchant needs to provide the redirect to the Issuer from the browser window or Merchant app where the Consumer selected the Issuing bank. If it is not possible to keep the Consumer in the same browser window then this should be communicated to the Consumer (e.g. ‘You will now be redirected to the app or mobile website of your bank’).

In case of a payment initiated in the Merchant app, it is not allowed to present the Issuer approval screens in a webview component within the Merchant’s own app (in-app browser). The complete payment flow, up to the redirect back to the Merchant’s app, must take place in an app that is trusted by the Consumer, either the Consumer’s chosen browser or the Issuer’s mobile app. Thus, for execution the issuerAuthentionURL must be offered to the operating system at all times. During the payment flow it must not be possible for the Consumer to initiate another payment through the Merchant’s original app.

Relevant details about the redirect from the Merchant to the Issuer’s mobile channel:

• The Issuer decides which Consumers to redirect to which channel. For example some Issuers may treat users of tablet devices the same as mobile users while others will treat them like PC users;

• The Merchant should not intervene with the redirect. There is only one issuerAuthenticationURL for the Merchant to use in all transactions, not a separate URL for mobile iDEAL transactions. The issuerAuthenticationURL should be executed by the operating system at all times;

• If the Issuing bank has integrated iDEAL mobile in its mobile banking app, the Consumer is offered the option, on a ‘landing page’, to open the app or pay via the (mobile) web page. On this ‘landing page’ the Consumer might be offered the option to download the latest version of the mobile banking app, if it is not yet installed on the Consumer’s device.

Process flow chart

iDEAL process flow

interface

Calling the iDEAL interface

To process a payment with online transfer with iDEAL, please use the following URL:

Parameters for online transfers with iDEAL

Return parameters for URLSuccess, URLFailure and URLNotify with iDEAL

Notice: Please note that for IDEAL transactions which are processed via PPRO, in rare cases there may be delayed notifications up to 5 days after the payment has been completed. This changes the payment status. Therefore we ask you to take this into account so that your store is able to process such notifications.

Querying the stored iDEAL banks

offers merchants the possibility to query which banks are stored for the merchant before the actual payment process. Since the configured bank list rarely changes, this does not need to be queried for each bank transfer. For this verification please use the following URL:

The following table describes the encrypted payment request parameters: Please note that the Merchant-ID plus Len and Data must be transferred every time as with all requests:

Parameters for requesting the stored iDEAL banks

Please transfer the MerchantID both in the unencrypted as well as the encrypted string.

The following table describes the result parameters, which sends in response:

Result parameters for requesting the stored iDEAL banks

Credit with reference

Credits (refunds) are possible via a Server-to-Server connection. permits only credits for iDEAL that reference on a captured transaction previously made via . The amount of the Credit is limited to the amount of the previous capture.

Please note that in case of EMS only one refund request can be processed. Submitting multiple refunds is not allowed.

To carry out a credit for iDEAL, please use the following URL:

Notice: Please note that credits (refunds) for iDEAL can be processed only when using the processing partners EMS, PPRO, Rabobank Omnikassa and additionally with EVO Payments Debtor Management. With a direct connection to the respective Dutch bank there are no credits possible via .

Parameters for credits of iDEAL payments

Result parameters for credits of iDEAL payments

Batch processing via the interface

This section describes the parameters which must be transferred within the data set (Record) for executing a iDEAL credit and which information can be found within the response file about the payment status.

Notice: Please note that Batch processing for iDEAL is possible only via EMS, EVO and PPRO connection.

Following table gives an overview of all batch versions that are possible for a specific action an their specialities:

Description of the possible batch versions

The structure for an iDEAL payment within a Batch file to be submitted is the following:

HEAD,<MerchantID>,<Date>,<Version>
IDEAL,Credit,<Amount>,<Currency>,<TransID>(<RefNr>),<PayID>
FOOT,<CountRecords>,<SumAmount>

Example for Master MID function:

HEAD,[Master]MerchantID,Date,2.x
Type,Action,[Slave]MID,Amount,Currency,TransID,Data (depends on Action)
FOOT,CountRecords,SumAmount

Description of fields within the record for Batch files

The record area within the response file for Batch transactions looks the following way:

HEAD,<MerchantID>,<Date>,<Version>
IDEAL,Credit,<Amount>,<Currency>,<TransID>(<RefNr>),<PayID>,<Status>,<Code>
FOOT,<CountRecords>,<SumAmount>

Description of result parameters within the record for Batch files