WooCommerce Rabo OmniKassa Gateway

WooCommerce Rabo OmniKassa (a Rabobank product) is a payment gateway that allows you to accept iDEAL, Mastercard, VISA, Maestro and other payment methods in your WooCommerce store. When Rabo OmniKassa is selected as the payment method, the customer is redirected to the Rabo OmniKassa server to make the payment and then brought back to the Thank You page on your site. This plugin only supports Rabo OmniKassa 1.0, not 2.0!

Requirements

↑ Back to top

• A business account (Dutch: zakelijke rekening) with Rabobank.
• A Rabo OmniKassa account.

To get an account, contact your local Rabobank or submit an application at Rabobank.nl.

Installation

↑ Back to top

1. Download the .zip file from your WooCommerce account.
2. Go to: WordPress Admin > Plugins > Add New and Upload Plugin with the file you downloaded with Choose File.
3. Install Now and Activate the extension.

More information at: Install and Activate Plugins/Extensions.

Setup and Configuration

↑ Back to top

Rabo OmniKassa setup

↑ Back to top

To use WooCommerce Rabo OmniKassa, you need the Merchant ID, Key and Key version. These details are either sent to you by the bank or need to be created on the Rabo OmniKassa download page.

1. Go to the Rabo OmniKassa download page https://download.omnikassa.rabobank.nl/
2. To login use the username and password you received from the Rabobank
3. If you logged in for the first time, you will need to change your password, just follow those steps on your screen now
4. After changing your password, click on “Geheime sleutels” in the top right blue button
5. In the new page, section “Geheime sleutels: informatie webwinkel” add any information that is missing
6. If you do not know your Merchant ID, it can be found on this page (a.k.a. Winkel-ID)
7. In section “Lijst van geheime sleutels”, there are probably no secret keys at first
8. In section “Genereren geheime sleutel”, click “Vragen om genereren” and confirm
9. It can take some time for the Key to generate. After 5 minutes refresh the page if its not created yet. If it takes longer than 5 minutes, come back later.
10. When the Key is generated, it is shown in section “Lijst van geheime sleutels”, and it should be activated (Actief = Ja)
11. From column “Versie” write down the Key version number.
12. From column “Sleutel” copy the Key.

Save the Key version and Key in a secure backup location.

Extension setup

↑ Back to top

With the collected details you can now configure WooCommerce Rabo OmniKassa on your site.

1. Go to: WooCommerce > Settings > Checkout > Rabo OmniKassa.
2. Tick the Enable Rabo OmniKassa checkbox when ready to go live.
3. Under Account details, set status depending on the account details used. If you are using the test details mentioned above, set to test. If you are using your production details, set to production.
4. Enter the Merchant ID, Key and Key version for the test or your production account
5. Save changes.

All other configuration options are not required, but explained below in Extension settings.

Extension settings

An explanation of the plugin settings for Rabo OmniKassa:

• Enable/Disable: Enable or disable the entire Rabo OmniKassa payment method.
• Title: The payment method name/title shown during checkout.
• Description: Payment method description shown during checkout.
• Status: Payment status, what kind of payments do you want to accept?
• Merchant ID: After completing the contract the Rabobank will send you a Merchant ID. The Merchant ID can also be found in the Rabo OmniKassa dashboard.
• Key: Can be found (and created) in the Rabo OmniKassa dashboard.
• Key version: Can be found in the Rabo OmniKassa dashboard. Default value is 1.
• Redirect customer to bank?: How to redirect customers after they confirmed the order in WooCommerce. We advise to always automatically redirect customers.
• OmniKassa language: By default Rabo OmniKassa will display in the language the customer has enabled for his browser. Use this option to force another language.
• Payment methods: Select “All” or one of the specific payment methods. Available methods also depend on your contract with the Rabobank.

Testing

↑ Back to top

We advise performing a few test payments in test and in production.

1. Go to WooCommerce > Settings > Checkout > Rabo OmniKassa
2. Set status to “Test” (You DO NOT need to enter the test account details!)
3. Go to the store and place a few test payments. Do as many test payments as you wish, testing different products, shipping methods or currencies depending on your store.
4. Satisfied? Go to WooCommerce > Settings > Checkout > Rabo OmniKassa.
5. Set status to “Production” and enter the production account details
6. Complete at least one real payment (where you actually pay yourself)
7. If the real payment is successful (check payment status in WooCommerce!), Rabo OmniKassa is now implemented successfully!

Test account details

↑ Back to top

Rabo OmniKassa has test details you can use on any website for testing. But you do not have to enter these under “Live account details”. The plugin has these details integrated, so when you set “Status” to test, the test details will be used, even when you entered your live details under “Live account details”. Just for reference, the test account details are:

• MerchantID: 002020000000001
• Key: 002020000000001_KEY1
• Key Version: 1

Usage

↑ Back to top

The Rabo OmniKassa plugin will add a Rabo OmniKassa payment method (the name in the checkout can be changed) to the WooCommerce checkout. This will allow store customers to select and pay orders via Rabo OmniKassa.

• A customer can select the Rabo OmniKassa payment method in the checkout
• After confirmation of the order, the customer is redirected to Rabo OmniKassa
• If applicable, the customer can select one of the payment methods you have enabled in your Rabo OmniKassa account
• Depending on the payment method selected a few things might happen. For iDEAL, customers will be redirected to their own bank to pay for the order. For credit cards, the customer can enter credit card details in Rabo OmniKassa
• After payment, the customer will see a final confirmation on the Rabo OmniKassa server and can select to return to the store.
• When returning to the store, the customer will get a confirmation from WooCommerce that the order is submitted (and paid)

Troubleshooting

↑ Back to top

Encountering issues? Please review the Rabo OmniKassa status page first at www.rabobank.nl/omnikassa-actueel. Rabobank will communicate downtime and other issues on this page. If no issues are reported, see below.

Payment status not updated or always failed

↑ Back to top

Situation: after multiple successful payments you return to the store and every time still get any status or response that is not confirmed, successful or paid. When this happens, it is not unlikely that the communication from the Rabo OmniKassa is being blocked (not received by the store).

• You can not test Rabo OmniKassa or iDEAL payments on your localhost. Move the store to a live server (a test directory is allowed) and test the payments there.
• The store is using some kind of “Offline page” or “Coming Soon” plugin which shows a placeholder and not the actual store. Some of these plugins also block all other requests to the store. Disable them during testing.
• Security plugins or a very strict security rule in the .htaccess file might also block communication from the Rabo OmniKassa server. Some of these plugins will even keep blocking the communication when they are deactivated in the Plugin manager. Remove them to be sure or contact the plugin developer and try to find the specific cause of the communication blockade.

Er is een fout opgetreden, neem contact op met uw dealer

↑ Back to top

First, contact the Rabobank (your dealer) and make sure the selected payment method (iDEAL, credit cards etc) is activated for your Rabo OmniKassa account. Second, the URL of the store requesting the payment might not be the same as the URL that is registered with the Rabobank. Realise that http://www.yourdomain.com and http://yourdomain.com are two different URLs. Contact the Rabobank and make sure the URL they have on file is the same as that is used for payments. And use a .htaccess rule to redirect the URL from non-www to www.

How to use different numbers for my bookkeeping?

↑ Back to top

It’s often a challenge for bookkeepers to identify payments via a payment service provider (PSP), the transactions on a bank account statement and the orders in a online store. The easiest solution would be to show all relevant numbers (payment number, transaction number, order number) on every single statement. Unfortunately, this is not possible. The Rabo OmniKassa plugin for WooCommerce is already sending all possible details to the Rabo OmniKassa server. The bank chooses what information it does and does not display on different screens and statements. Order number on your bank statement The Rabo OmniKassa will never show the order number on your bank statement. Revenue generated via Rabo OmniKassa is paid to your bank account in one payment batch that includes the revenue from multiple orders. Payments for individual orders or therefor not identifiable in your bank statement. Order number in your customers bank statement The order number might be shown on your customers bank statement, but most often it is not. The Rabobank has confirmed the order number is not a mandatory field that other banks are required to show in their bank statements. This is not a bug in our plugin. Solution: do a cross reference You can however do a cross reference between WooCommerce orders and your bank statement by using the Rabo OmniKassa CSV export that you can download via the Rabo OmniKassa dashboard.

After returning to store, a pop-up error appears about insecure items.

↑ Back to top

The full error in Dutch: “Hoewel deze pagina is beveiligd zal de informatie die u hebt ingevuld over een niet-beveiligde verbinding worden verzonden en kan deze gemakkelijk worden gelezen door derden. Weet u zeker dat u wilt doorgaan met het versturen van deze informatie?” The full error in English: “Although this page is encrypted, the information you have entered is to be sent over an encrypted connection that could easily be read by a third party. Are you sure you want to continue sending this information?” This happens with sites that are not secured with a HTTPS communication (which not required for Rabo OmniKassa) and only in some browsers, as far as we know: Firefox, Safari and some versions of IE. The Rabobank has confirmed that we can not fix this from our side, the only solution is to either live with it or use HTTPS communication for your store.

Redirect to Rabo OmniKassa “Server detected an error.”

↑ Back to top

This error might appear when you are testing multiple payments and have Rabo OmniKassa cookies already (automatically) installed in your browser. Our tip is to use the browser “Google Chrome” in Incognito mode or “FireFox” in Private mode. Using the Incognito or Private mode makes sure cookies will not be saved and you can test your Rabo OmniKassa installation without the above issue.