Home > Processing iDEAL Transactions > Transaction Flow


Transaction Flow

 

An iDEAL transaction flow can be viewed here:

https://www.ideal.nl/demo/

For a complete transaction flow diagram see:

http://apps.cybersource.com/library/documentation/dev_guides/OnlineBankTransfers/iDEAL.pdf

1Display the iDEAL payment method on your checkout page.

You can display your logo (640 w x 150 h) and a wallpaper (1920 w x 1080 h) as part of the payment flow. If the bank option ID is not included in the sale service request, the logo and wallpaper are displayed.

 

2Request the options service (apOptionsService) once each day, at any time, to retrieve the list of bank names. Each name represents the bank identification code (BIC, also known as a swift code) associated with the bank and is prefixed with ideal, for example: ideal-BUNQNL2A.

Cybersource recommends caching the information and displaying the bank name to the customer in a drop-down menu on your checkout page.

3The customer chooses the iDEAL payment method and chooses their bank from the list of options that you have cached.

A list of all available banks can be displayed in a drop-down menu in any order you choose. Cybersource recommends displaying the following six bank names and their logos at the top of the list:

nING Bank

nRabobank

nABN AMRO

nSNS Bank

nASN Bank

nTriodos Bank

4Request the sale service (apSaleService) and include the optional corresponding bank ID for the bank that the customer chooses (apSaleService_paymentOptionID). Also send the success, cancel, and failure return URLs so that the bank can return the customer to your page.

5Cybersource responds with a merchant URL to direct the customer to their online banking page to confirm payment details.

If the option ID (apSaleService_paymentOptionID) is not included in the sale service request, the customer is directed to a URL where they must choose their bank from the list displayed. (The redirect URLs are not supported with inline frame integrations.)

 

 

6When the payment is successful, the bank directs the customer to the success URL included in the sale service request.

When the payment is canceled, the bank directs the customer to the cancel URL included in the sale service request.

When the payment fails, the bank directs the customer to the failure URL included in the sale service request.

7When a customer is directed to the success URL, you can request the check status service (apCheckStatusService) to retrieve the current status of the payment.

The transaction statuses are:

nAbandoned—the customer did not complete the transaction within 15 minutes.

nFailed—the payment failed. Look at the reasonCode field for a description.

nPending—the payment was initiated. Do not ship the goods.

nSettled—the payment is complete. You can ship the goods.

If the check status reply is pending, wait 5 minutes before making the check status request again. If there is still no status change, wait 20 minutes before making another check status request. After 20 minutes, the status should be settled, abandoned, or failed.

8When the payment status is updated to settled, you can request the refund service (apRefundService) to refund a customer’s payment.

iDEAL transactions support:

nFollow-on refunds of payments that have a status of settled.

nPartial refunds and multiple refunds.

nRefunds for the original payment amount and the addition of 25 EUR. If the original payment amount was 45 EUR, you can refund up to 70 EUR.