...

...

On a high level, iDEAL offers several key features:

• iDEAL Payment (Standard)

  • Payment without profile recognition enables Users to pay with iDEAL without the need of a registered profile, by means of a manual bank selection or QR code, offered on an iDEAL payment page.

  • Payment with iDEAL profile recognized via a cookie enables iDEAL to recognize the User based on a cookie stored on the User’s device, and show the User’s payment preferences.

• Payment with iDEAL profile recognized via iDEAL User Tokenallows the Merchant to immediately present the User with his preferred IBAN, and redirect the User to his preferred bank (with preferred IBAN preselected). A unique iDEAL UserToken (expectedDebtor.usertoken) can be provided to the Merchant upon request. Upon future visits, the Merchant can use this token to retrieve and/or make use of the User’s payment preferences in the iDEAL transaction.

• iDEAL Checkoutallows the User to share his centrally stored address and contact details with Merchants upon request. This means that Users, for example, do not have to enter their address details each time they shop at a different Merchant. iDEAL QR payment allows Users to scan a QR code (i.e. a QR code that is generated before the payment flow, such as a code on physical paper) to start the payment flow.

Ecosystem overview

The iDEAL ecosystem is composed of several parties that interact in order to fulfill an iDEAL transaction. The focus of this document is on the direct integration of Merchants/CPSPs to the iDEAL Hub. The overview below illustrates the interaction between the parties involved. These interactions take place through REST APIs that are defined by iDEAL. A list of all currently available APIs is included in the overview below. Detailed API specifications can be found on Confluence: Direct Connection Merchant/CPSP APIs .

...