What is iDEAL?
iDEAL is a set of standards developed to facilitate online payments through the online banking applications that most Dutch banks provide.
If a consumer already has online banking with ABN AMRO, Fortis, ING/Postbank, Rabobank, or SNS Bank, they can make payments using iDEAL in a way that they are already familiar with.
In order to use iDEAL you will need to get an iDEAL merchant account from your bank. Every bank offers âcomplete paymentâ services, which can obfuscate the right choice. The payment product that you will want to get, in order to use this gateway class, is a bare bones iDEAL account.
- ING/Postbank: iDEAL Advanced
- ABN AMRO: iDEAL Zelfbouw
- Fortis: ? (Unknown)
- Rabobank: Rabo iDEAL Professional. (Unverified)
- SNS Bank: Not yet available
If you implement tests for other banks, if they require such acceptance tests, please do submit a patch or contact me directly: firstname.lastname@example.org.
As a gem:
Add the following to your environment.rb:
As a plugin:
./script/plugin install git://github.com/dovadi/active_merchant_ideal.git<br />
Generate private keys and certificates
Messages to, and from, the acquirer, are all signed in order to prove their authenticity. This means that you will have to have a certificate to sign your messages going to the acquirer and you will need to have the certificate of the acquirer to verify its signed messages.
The latter can be downloaded from your acquirer after registration. The former, however, can be a certificate signed by a CA authority or a self-signed certificate.
To create a self-signed certificate follow these steps:
Substitute _the_passphrase__ with your own passphrase.
With the ING bank you upload your private certificate with your iDEAL Dashboard. Be aware that there are two dashboards, one dashboard for the test environment and one dashboard for the production environment!
For more information see:
Test the gem
You can run the tests from this gem with (inside the active_merchant_ideal directory):
Run the remote tests
- Create .active_merchant directory in your own home directory
- Copy test/fixtures.yml to the .active_merchant directory
- Fill in your own merchant id, passphrase and the correct locations to your private key and certificates.
- For running the seven prescribed remote test transactions (ING bank) which are needed to activate the iDEAL account use
First configure the gateway
Put the following code in, for instance, an initializer:
1 2 3 4 5 6 7 8
Give the consumer a list of available issuer options:
1 2 3 4
1 2 3 4 5 6 7
First you’ll need to setup a transaction and redirect the consumer there so she can make the payment:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
After the consumer is done with the payment she will be redirected to the :return_url. It’s now your responsibility as merchant to check if the payment has been made:
1 2 3 4 5 6 7 8 9 10 11
In 2006 an iDEAL payment library was written in Ruby for a web shop build in Rails for selling mobile phone credits. It was basically a translation of the PHP example given by the iDEAL organization (see iDEAL Advanced Integration Manual PHP). Is was released as the ideal-on-rails plugin.
In 2007 this code was refactored as a patch for the ActiveMerchant library, this was mainly done by Fingertips for a client project. This patch was never accepted due to the fact it was too different (and maybe too obscure) from the ‘normal’ credit card gateways.
In 2009 Fingertips forked the ActiveMerchant library and added an iDEAL gateway (presumable based on the first ActiveMerchant patch) to a new ideal branch.
In 2010 this code was extracted and converted into a separate gem, so it can be more easily used in combination with the latest version of ActiveMerchant. This library is just an extraction, nothing more and nothing less. There are no fundamental changes between the code from the ideal branch and the code of this gem.