The installation can be carried out in three ways:
In this manual we describe the installation via Composer.
This manual helps merchants to process MultiSafepay payments as quickly as possible from a Magento 2 webshop. For some steps in this manual, assistance from your technical partner may be required.
We recommend you to install the plugin first on a test environment, and make sure you have made a backup.
We advise you to install the plugin through the recommended ways of the specific webshop system.
If you need any technical help, please contact us.
To use the plugin you need a MultiSafepay account. You can create a test account on https://testmerchant.multisafepay.com/signup
If you would like to set up a live account, please contact the MultiSafepay sales department:
Run the following commands via the CLI:
composer require multisafepay/magento2msp php bin/magento setup:upgrade php bin/magento setup:static-content:deploy
After running these commands, the latest stable release is downloaded and installed within your Magento 2 webshop.
Depending on your webserver/webshop configuration you also need to check:
Login on the backend of your webshop and navigate to Stores -> Configuration -> MultiSafepay x.x.x -> MultiSafepay Settings.
This page contains all main settings and is used for all gateways and gift cards.
Information on where to find your Account ID, Site ID, Site code or API key can be found on our API key page.Your Account ID is shown in the dashboard of your MultiSafepay Control in the top right corner
Navigate to Stores -> Configuration -> MultiSafepay x.x.x-> MultiSafepay Gateways.
This page contains the configuration options for all payment methods supported by MultiSafepay.
Be sure that you have the selected payment methods active in your MultiSafepay Control
MultiSafepay Gift cards
This page contains the configuration options for all gift cards supported by MultiSafepay.
Gift cards need to be activated, more information can be found on our gift card page
This page contains the Fastcheckout specific settings.
More information about the Fastcheckout can be found on https://www.multisafepay.com/fastcheckout-payments
You have installed and configured the plugin successfully. If you have any questions regarding the plugin, feel free to contact our Integration Team at [email protected] or start a discussion in our Magento Slack channel #multisafepay-payments
Run the following commands via the CLI:
composer update multisafepay/magento2msp php bin/magento setup:upgrade
Depending on your webserver/webshop configuration you also need to check: - check the rights on files correctly. Our files can be found at vendor/multisafepay/magento2msp - Empty static files when running in production mode - Flush cache.
Yes, it is possible to refund orders or credit memo from within the Magento 2 backend.
In the Magento backoffice, go to the Invoices tab, click on the invoice that was created by MultiSafepay and then click Credit Memo. Now you see 2 refund buttons: * Offline refund: refund request will not be sent to MultiSafepay * Refund: a refund request will be sent to MultiSafepay.
You can also refund from your MultiSafepay Control
Note: Refunding from the Magento 2 backend is disabled when the order has a Fooman Surcharge. It is still possible to refund those orders through MultiSafepay Control
Generally, there are three ways to update a plugin. This can be done through the backend and through the marketplace from a CMS or through SFTP. However, for Magento 2 we will be describing the necessary steps via Composer
Before you update the plugin, we strongly recommend you the following:
Go to our Manual page, download the plugin and follow the instructions from step 2.
Adding a payment fee or Surcharge is no longer supported within the plugin in Magento 2.
However, an external package of Fooman is available. This allows you to still add a payment fee or surcharge within the desired payment method.
Refunding from the Magento 2 backend is disabled when the order has a Fooman Surcharge. It is still possible to refund those orders through MultiSafepay Control
Do mind that because an external module has to be installed, our Integration Team’s help will be limited.
Of course, we do our best to support and assist as best as possible, but we investigate or reproduce on the core of a plugin. Therefore, we do not guarantee a perfect compatibility when installing an external package.
Please keep in mind that the Payment Services Directive 2, also called PSD2, is now in place and may have implications on your webshop. PSD2 was first released in 2015 by the European Commission. This directive compelled the Member State to effectively intervene and regulate the payment service industry. See how applying payment fees or surcharges for your customers may affect your webshop on our PSD2 documentation page
It may be the case that unwanted ‘Custom Order Totals’ will appear on the MultiSafepay payment page. If you wish for this amount to be excluded, there is an option in the backend of our plugin in Magento 2, which can exclude such ‘Totals’. This option will however not be required if the plugin or module removes the custom total from the order when it is not being used.
The lifetime of orders marked as pending payments in Magento 2 is determined by the Order Cron Settings configuration. The default value is set to 480 minutes (8 hours)
When you offer payment methods whose validation period is more than 8 hours, the order in Magento 2 will automatically be marked as cancelled due to the default setting in Magento 2.
In use with an ERP system, for example, where an order is marked as declined, a successful payment will often not be processed to an order that is marked as cancelled.
The lifetime of a bank transfer is 86400 minutes (60 days)
The order will set to cancelled in Magento 2 before a payment can be linked.
To set pending payments order lifetime, see the Magento Documentation page
From version 1.9.0 and higher, all the order totals, including custom ones, are automatically read and shown on the MultiSafepay payment page.
Some Magento 2 plugins that provide custom order totals do not completely remove these totals from the order and only remove them from the frontend in order for the user not to see them. This results in our plugin picking up the custom order totals that were not visible in the webshop and showing them on the payment page.
To prevent this from happening, these custom totals can be excluded in the advanced section of the webshop configuration: Stores > Configuration > MultiSafepay > MultiSafepay Settings > Advanced Settings > Exclude custom totals.