This plugin has reached END OF LIFE support. Therefore, it is no longer maintained. The documentation is here for historical references only.
Prestashop Resurs Checkout
This extension helps merchants to integrate Resurs Bank Payment Gateway to their PrestaShop based e-commerce stores. There are two versions of this plugin and they are currecntly only supporting Resurs Checkout.
KNOWN PROBLEMS
There are a few known problems in the core functions of Prestashop, some of them are not related to our module at all. Take a look at the bottom at this page for more information.
CUSTOMIZABLE PRODUCTS for PrestaShop 1.7
Prestashop offers customizable products. For example, you can add custom texts on your products in the sample store. This product type is not (as of june 2020) not supported by the module for version 1.7.6.
Compatibility
This plugin is tested in “vanilla environments”, which means that the plugin is installed with a default installed store. If there are plugins installed, they are usually installed from for example a marketplace. We can not fully guarantee functionality if you have other plugins installed, that uses overriders and such.
Plugin versions
| Name | Tested with | PHP | Details | Country | Repos | Download | Dev Tracking | Status |
|---|---|---|---|---|---|---|---|---|
| Resurs Checkout - PrestaShop | 1.6 | >= 5.4 | Resurs Checkout | SE (Confirmed) | Master branch (1.6) | Release-tags for v1.6 | JIRA for v1.6 | END OF LIFE |
| Resurs Checkout - PrestaShop | 1.7.6.x1.7.7.x | >= 5.4 | Resurs Checkout | SE (Confirmed) | Master branch (1.7) | Release-tags for v1.7 | JIRA for v1.7 | END OF LIFE |
| Resurs Simplified Flow (SOAP) | >= 1.7.7 | >= 7.4 | INSTALL WITH COMPOSER | SE (Confirmed) | CoreSimplified AddonPartpayment WidgetOrder Management Addon | END OF LIFE |
The above RCO-1.6/1.7 was splitted into separate modules when the development of the module for Prestashop v1.7 was initiated. The module for v1.6 went up to 2.6.5 with some updates that was brought into the v1.7-module - and the 1.7 module became 2.7.0
END OF LIFE (EOL)
End Of Life plugins are no longer supported due to End Of Life states for the platform releases and PrestaShop 1.7 is such release. Therefore, support for Prestashop 1.6 and 1.7 has ended. This is a way to maintain stability with fewer glitches than if we supported long range versions.
PrestaShop Lifecycle
The support for PrestaShop 1.7.7 ended when version 1.7.8 was released. According to the PrestaShop development documentation, when a new minor version is released, the previous version reaches its end of life, meaning no more patch releases for bug fixes or security issues.
PrestaShop 1.7 entered extended support after the release of PrestaShop 8.0 in October 2022, which included only critical security fixes. This extended support is expected to continue until the release of PrestaShop 9.0, estimated by the end of 2023. Therefore, it is advisable for users of PrestaShop 1.7.7 to upgrade to a newer version to ensure continued support and updates.
Requirements
- Supported platforms should follow the PrestaShop requirements. However, as of april 2019, none of those plugins supports PHP 5.3 anymore.
- Merchant credentials from Resurs Bank (ID and Password).
- Full SSL support for communicating with Resurs Bank.
- PHP module activated to support curl.
- PHP module activated to support soapclient and XML .
Upgrading
For each upgrade you do, make sure you clear all cache data in PrestaShop admin (Via the Advanced->Performance tab). As there are front end scripts that may require extra cleanups, this is also necessary.
Installation
The below instruction is based on a basic installation, where you have direct access to the server. By means, you probably have ssh access at the hosting provider or something similar. If you’re using ftp, it’s probably best to extract the zip (described below) at your local computer first - rename the folder, and then upload the file structure to the modules-directory at your shop.
There are other ways, which is in this case unsupported. There is also a “Prestashop Marketplace” where the plan is to get our modules distributed. When this part is fulfilled, it may be possible to install it directly from there. Unfortunately, as of april 2019, this is currently not possible yet.
- For both Prestashop 1.6 and 1.7, grab a tagged release from our repos (do not use the master-branch as this usually is a development branch - and even if it’s for the moment stable, we can’t guarantee full production support at this level).
- Unzip the downloaded file into <primary folder of your shop>/modules (the downloaded file may look like this:resursbankplugins-resurs-checkout-prestashop16-ff8652e77e83.zip)
- Make sure you rename the primary directory that you unzipped to the modules directory.
If the zip looks like above (resursbankplugins-resurs-checkout-prestashop16-ff8652e77e83.zip), the directory that the module will land under may look like this:resursbankplugins-resurs-checkout-prestashop16-ff8652e77e83 - Make sure your cloned or extracted directory under modules is renamed toresursbankcheckout, or the module won’t be found by prestashop therefore not work.
- Activate the module and configure it through the admin module panel. Do not forget to put the username and password in the credentials field.
- Also do not forget to register payment methods and callbacks (see screen dump below)!
- Before going production mode, make sure you test the module so you know it covers your needs!
Module configuration example
Registered payment methods and callbacks
**
**
Known problems and (eventually) the solutions
Handling unfinished orders
Sometimes, customers decide to not fullfill their payments and shuts down their payment session/browsers faster than we can handle the cancellation. This means that some orders may look active, but in reality they are cancelled. In Prestashop, we have added an adapted shellscript written in PHP that is supposed to handle this kind of problems. It is not really supported, and is more to consider an extra addin-tool than something that really belongs to the plugin. It is located under modules/resursbankcheckout/shell/Cleaner.php, if you want to try it out. It is usually not recemmended to install this to run under the Prestashop internal cron handler, but externally like a shellscript. For shelled-cronjob, the crontab should look like below and it is fine running it once per hour:
0 * * * * /bin/php /var/www/prestashop/modules/resursbankcheckout/shell/Cleaner.php
From /etc/cron.d it could also be added as a generic cronjob:
0 * * * *
<owner>/bin/php /var/www/prestashop/modules/resursbankcheckout/shell/Cleaner.php
Do not forget to change the paths, binaries and the ownership for both above examples.
SSN/Government ID’s and direct debiting methods (like SWISH)
If a customer chooses to change their billing/delivery address in the checkout without using the getPayment-features (meaning there may be some missing government id’s through the checkout), Prestashop will be unable to catch this information on the payment. If you use features in the plugin that collects data for insurances, the module will be unable to store this data for you. By means, it may be “bad for business” especially insurance-features, if the customer somehow are not required to enter this information during the payment.
Going from cart to checkout has weird URL
When you use swedish translations the url, depending on your platform, may show up as “https://your-site/För”. The “För” link is a typo related to a redirect_url that went wrong when it was installed in the database. It looks ugly but is normally not destroying anything.
Solution:
If you want to report this as a bug to Resurs Bank - don’t. We can’t solve it from our side. Instead, update your database. If you are unsure of what to look for, the above query could probably be changed to something like this:
SELECT * FROM ps_meta_lang WHERE url_rewrite = 'För'
If you find a row that contains “För” in the url_rewrite-field, change it to “order”. If you only have access to prestashop admin and the sql editor there, you could run something that looks like the query below.
Best practice is to look for the correct “wrong row” and change it, just so nothing else is changed by mistake.
UPDATE ps_meta_lang SET url_rewrite = 'order' WHERE url_rewrite = 'För'
Just make sure your tables are not prefixed as something else.