We have tested cciDEAL for implementing Rabo OmniKassa in HikaShop, there were no problems. The fastest and easiest way to implement Rabo OmniKassa is to use our cciDEAL extension. We will regularly test our Rabo OmniKassa integration with new Hikashop versions.
- First install Hikashop in the Joomla! website.
- Then download the latest cciDEAL version from our downloads section, and install it.
- Configure the Hikashop plugin
- In the Joomla! administrator, go to Hikashop > System > Payment Methods
- Open the cciDEAL plugin “Hikashop – cciDEAL”
- Optional: click on the edit icon next to Zone (on the right) and select Netherlands (or any other country) if you want cciDEAL not to work for all countries, but only the selected. If you want cciDEAL to work for all countries, do not use this function.
- At the statusses, choose your desired status after different payments.
- Invalid status could be “Geannuleerd” or “Canceled”
- Pending status could be “Geplaatst” or “Created”
- Verified status could be “Betaald” or “Confirmed”
- Because Rabo OmniKassa supports muliple payment methods, you can choose if and how you want to display them in HikaShop to the webshop customers.
- Use the Media Manager (Content > Media Manager) or FTP to go to /media/com_hikashop/images/payment.
- Download and unzip this file with payment method logos here iDEAL_logos.zip.
- The file contains different images with the payment methods supported by Rabo OmniKassa. The PSD’s are also included so you could also edit the images.
- iDEAL only: If you only use iDEAL in Rabo OmniKassa, there are small, medium and large (in English and Dutch) iDEAL logos which can be used, there file name starts with “ideal_”.
- All payment methods: if you use all payment methods supported by Rabo OmniKassa, use the image “all_payment_methods.png”.
- Some payment methods: if you use only a few of the payment methods supported by Rabo OmniKassa, open all_payment_methods.psd in Photoshop (or similar software) and re-arrange the payment method layers.
- PostNL: we have also added a PostNL logo for your convience, which can be used for your shipping methods.
- After you have chosen/modified a payment method image, upload it to the “payment” folder.
- Go back to Hikashop and click “Save” in the toolbar, so the Configuration tab is refreshed.
- On the right, click on the edit icon next to “Images”, and select the preferred OmniKassa logo.
- Now, if needed, also edit the payment method Name and Description (on the left).
- Click on save, without changing anything else. The configuration should now be correct.
You can now configure your Rabo OmniKassa account in the “Configuration for cciDEAL” chapter.
Continue Reading
It is possible to accept Rabo OmniKassa payments from within Joomla! articles with great flexibility and ease. With this function you could for example accept donations or get payments for an invoice/order. The amount to be paid and payment ID can be fixed by you or kept “open” so the user can enter his/her preferred value. It is also possible to use a dropdown from which the user can select an amount to be paid.
To use this function you need to enable the cciDEAL plugins first. Go to Extensions > Plug-in Manager and search for “iDEAL” in the filter. Enable the “Editor button – cciDEAL” and “Content – plugin – cciDEAL” plugins.
Rabo OmniKassa button in Joomla! articles
To add an cciDEAL form to any Joomla! article, a simple “tag” is added to the article. That tag will then in the site generate an cciDEAL form. An example cciDEAL form is shown below. The form can handle all payment methods supported by your Rabo OmniKassa account and your contract with the Rabobank, not just iDEAL!
cciDEAL tag in the administrator
On installation cciDEAL will also install an editor plugin, which shows an Rabo OmniKassa button, as marked in the below image. When that button is clicked, the default cciDEAL tag is added to the Joomla! article. That tag can be customized to fit your needs, and will generate the cciDEAL form in the website.
The default cciDEAL tag is:
{cciDEAL title=”Nu_betalen” amount_by_user amount=”15.00,22.00″ amount_text=”Kies_bedrag:” paymentid_none paymentid_by_user paymentid=”399″ paymentid_text=”Kenmerk:” extra_textfield extra_textarea extra_textfield_required extra_textarea_required extra_text=”Informatie:” submit_button=”Verder” }
Customizing your cciDEAL form
The above code has to be customized to your wishes before it is usable. All possibilities are explained in below table and image.
Please note that all values between braces “..” should use an underscore _, not spaces!
You can add only one “type” per button, for extended forms consider our integration with RSForm Pro.
| Type |
Possible values |
| title |
Title above the form, “Betaal_met_Rabo OmniKassa” by default |
| amount |
There are three options for the amount shown in the form
- A fixed single amount can be created by adding: amount=”15.00″
- Multiple fixed amounts in a dropdown can be created by: amount=”15.00,22.00″
- An input field so a user can enter an amount can be created by: amound_by_user
|
| amount_text |
The title of the amount field, “Kies_bedrag:” by default |
| paymentid |
There are a few different options for the payment ID in the form
- To set a fixed payment ID, use the code: paymentid=”399″
- For no payment ID to be visible to the user at all (cciDEAL will generate one), the following code should be used: paymentid_none
- To allow the user to enter a payment ID himself, add the code: paymentid_by_user
This value can be removed from the tag if you don’t want to show a payment ID. |
| paymentid_text |
The title of the payment id, “Kenmerk:” by default. This value can be removed from the tag if you don’t want to show a payment ID. |
| extra_text… |
This can be used to collect just a little bit more information about the user or payment. The field will change nothing about the Rabo OmniKassa payment, it will only register the information submitted by the user, and show it in the “Extra information” field in the cciDEAL Payments page. These fields will accept letters, numbers, spaces and . , ? ! @ #. Other symbols are blocked for security reasons.
These fields can be used to collect, for example names, e-mail addresses, comments or other short messages. They allow you to easier identify the payment then with only the paymentid fields mentioned above.
- optional text field, maximum input 100 characters, use the code extra_textfield
- required text field, maximum input 100 charecters, use the code extra_textfield_required
- optional text area, use the code extra_textarea
- required text area, use the code extra_textarea_required
This value can be removed from the tag if you don’t want to show an extra text field or area.
|
| extra_text |
The title of the extra text field or extra text area, “Informatie:” by default. This value can be removed from the tag if you don’t want to show an extra text field or area. |
| submit_button |
Text of the submit button, “Verder” by default |
A few cciDEAL tag and form examples
You can copy/paste these examples to your article, they should immediately work!
|
|
{cciDEAL title=”Betaal_met_iDEAL” amount=”15.00,22.00″ amount_text=”Kies_bedrag:” paymentid=”399″ paymentid_text=”Kenmerk:” submit_button=”Verder” }
|
|
|
{cciDEAL title=”Betaal_met_iDEAL” amount=”15.00″ amount_text=”Bedrag:” paymentid_by_user paymentid_text=”Uw_factuur:” submit_button=”Verder” }
|
|
|
{cciDEAL title=”Betaal_met_iDEAL” amount_by_user amount_text=”Uw_donatie:” paymentid_none submit_button=”Verder” }
|
|
|
{cciDEAL title=”Betaal_met_iDEAL” amount=”15.00″ amount_text=”Kies_bedrag:” paymentid=”399″ paymentid_text=”Kenmerk:” submit_button=”Verder” }
|
Continue Reading
We have just released cciDEAL 2.2.7 which adds support for Virtuemart 1.1.8 to cciDEAL for Virtuemart. We advice you to upgrade to Virtuemart 1.1.8 as soon as possible, as 1.1.8 is a security release!
Read more for details and update instructions. Updating ccDEAL Virtuemart to 2.2.8 is relatively easy, but you should be careful with updating Virtuemart!
Continue Reading
We received a report that there was a security issue in the current ccNewsletter (Joomla! newsletter) versions. After investigation I can confirm that there is a SQL injection issue in the ccNewsletter module versions 1.0.7 threw 1.0.9. There is already a known security issue in 1.0.6 and earlier, so I advice everyone using a ccNewsletter version before 1.0.10 to upgrade!
You can download ccNewsletter 1.0.10 from our downloads section here. If you need details (because you have done custom modifications to the module), please create a support email where we will share them.
A thank you to Fiona from Spiral Scripts Joomla! Extensions for the report!
Continue Reading
On Saturday April 2 and Sunday April 3, the Dutch Joomla! days will be held in Doorn, the Netherlands.
I can really encourage any Dutch Joomla! user to visit these days! The presentations that will be held sound extremely informative and are well selected to please a wide range of Joomla! users. A few well known Joomla! enthusiasts will also be attending, including Joomla! priest Brian Teeman and OSM president Ryan Ozimek.
Learn more about the Dutch Joomla! Days on www.joomladagen.nl!
Continue Reading
The e-commerce platform Magento has only been around a few years but it can offer e-commerce business owners a very competent alternative to a Joomla! Virtuemart setup. Although I’m not entirely unbiased, I’m happy to admit that Magento offers the user lot of great functionalities. What should you consider when making your choice?
The state of Joomla! e-commerce blogs are a series I am writing about Joomla! e-commerce extensions. Click the “e-commerce” label/tag to read more articles about this subject. A previous blog post was “The state of Joomla! e-commerce in December 2010“.
Continue Reading
This is not an elaborate overview of the advantages and disadvantages of osCommerce and Virtuemart, but merely a brief summary that I’ve borrowed from a fellow forum member on a Dutch Joomla! forum. Dimage works with both systems and because of this he was able to compile a good overview. Read on for the advantages and disadvantages of osCommerce and Virtuemart!
There are going to be some interesting changes in the Joomla! e-commerce area in 2011 as some of the new extensions (like Magebridge, Tienda and redSHOP) become more mature. The state of Joomla! e-commerce blogs are a series I am writing about these changes. Click the “e-commerce” label/tag to read more articles about this subject. Two previous blog posts are “The state of Joomla! e-commerce in December 2010” and “A short history of Joomla! e-commerce“.
Continue Reading
After we dove into a bit of history concerning Joomla! e-commerce, lets have a look at Joomla! e-commerce today. What are the new Joomla! e-commerce extensions, and what do Joomla! developers tend to think about them?
Joomla! e-commerce finally took off in 2010, with a few serious extension developers entering the ring with there brand new Joomla! e-commerce extensions, and a few examples are Magebridge, Tienda. The state of Joomla! e-commerce blogs are a series about the developments in the Joomla! e-commerce area.
Continue Reading
The Virtuemart team has released two new versions! Virtuemart 1.1.6 is a bug fix release which fixes many long standing bugs. It also introduces some bugs, that could potentially disable your site. So only upgrade to Virtuemart 1.1.6 is you have time to backup, test and fix your site before you put it online. There are already 11 bugs reported for Virtuemart 1.1.7, so it is not a strange idea to wait for that version.
Continue Reading
You can now get your hands on a release candidate for Joomla! 1.6. But it’s actually not that stable, so don’t use it on production websites just yet.
When Joomla! 1.6 Beta 14 and 15 where released a few weeks ago, there was lots of buzz about a Joomla! 1.6 Release Candidate before Christmas. Well, here it is, Joomla! 1.6 RC!
Continue Reading
