Overview

MultiSafepay makes both online and mobile payments easy for your customers. Our ecommerce payment solutions and conversion increasing tools simplify the process of accepting, managing, and stimulating online payments. Our smart ecommerce tools ensure a seamless and secure payment process. MultiSafepay’s mobile channel supports responsive payment pages and several in-app payment solutions. thanks to a complete range of local and international payment methods, simple integration processes, and our international expertise, we make it easy for the commerce industry to sell products online all over the world.

The extension is developed by MultiSafepay. It can be connected to our payment platform and gives you access to several payment methods, including credit cards (VISA, MasterCard, American Express) and local payment methods (e.g. iDEAL, Bancontact, and more). Our extension is updated regularly to ensure that you have access to the newest features.

Pricing for MultiSafepay services start at EUR 0,15 per transaction. Depending on volumes and agreement terms other pricing conditions can be agreed.

Supported Payment Methods

DEAL

DotPay

Betaal na Ontvangst

E-invoice

Klarna

Bancontact

Visa

Eps

Ferbuy

Mastercard

Bank transfer

Maestro

PayPal

Giropay

Sofort

DirectDebit

Support Giftcards

Webshopgiftcard

Babygiftcard

Boekenbon

Erotiekbon

Parfumcadeaukaart

Yourgift

Wijncadeau

Gezondheidsbon

Fashioncheque

Fashiongiftcard

Podium

Vvvbon

Sportenfit

Goodcard

Nationaletuinbon

Nationaleverwencadeaubon

Beautyandwellness

Fietsenbon

Wellnessgiftcard

Winkelcheque

Givacard

Special features

Payment methods and gifcards can be restricted to country

Payment methods and gifcards can be restricted to shipping method

Payment methods and gifcards can be restricted to currency

Payment methods and gifcards can be restricted to customer group

Payment methods and gifcards can be restricted to an order minimal amount

Payment methods and gifcards can be restricted to an order maximum amount

MultiSafepay is fully PCI compliant so you don't need to worry about the payment details of your customer. Payment details are processed securely by following PCI regulations. Consumers within your Magento 2 webshop will be redirected to the MultiSafepay payment platform where they need to enter their payment details (if needed).

After a payment the extension will request the payment details of the order using a secure SSL connection to verify the transaction status.

Release Notes

1.1.0:

Compatible with CE:
2.0 2.1

Stability:
Stable Build

Description:

div id="container" style="width:900px; margin-left:100">

Release Notes - Magento 2 MultiSafepay plug-in 1.1.0 (Okt 13th, 2016)

Changes
Better check on redirect data, fixing error when transaction details are not available yet.
Added check if API key is configured on issuer request. The issuer request is done when reaching the checkout page using the config provider. Not checking if the API key is configured will cause an exception after installation when the key is not yet configured but the static-content is already deployed.
Fixed bug with the ACL.xml. User roles can now select the MultiSafepay tabs to allow/disallow access for a certain user
Fixed bug with Language detection, causing transaction language always be set to nl_NL and resulting in Dutch language pages and transaction e-mails
Fixed the path of the gateway images that was hardcoded to "pub", this is now dynamically set by the config provider
Fixed a bug causing uncleared transactions not being updated after the transaction status has been changed to completed

Features
Added support for EPS
Added support for Ferbuy
We added an option to configure when the order confirmation email needs to be submitted. You can select "after order placing", "After a processed transaction" and "after a paid transaction"
Added official support for the "one-step-checkout" from MagePlaza
Added configuration options for more transactions statuses. You can now configure the status for "Expired", "Cancelled", "Chargeback", "Declined" and "New Order"
We added a multisafepay.log logger that will store all API requests
Added support for E-invoicing

Release Notes - Magento 2 MultiSafepay plug-in 1.0.6 (Jul 21th, 2016)

Changes
Extended the gateway configuration file so that all restrictions valus are set, causing them to be configured one saving of the configuration. This would reduce the support questions because of merchants that forget to configure the restrictions. Default all is now configured.
This fix sets the payment method to disabled by default so it only has to be enabled to show it on the frontend. This change was needed because of PLGMAGTWO-25. PLGMAGTWO-25 now sets the restrictions by default, causing all payment method to show on config save. PLGMAGTWO-24 prevents everything to show as it must be enabled first.
Check was nog complete as we checked if the housenumber was set, not if it had an empty value, causing the check to fail and no housenumber to be added to the transaction request. This caused a rejection for Pay after Delivery and Klarna.
Added gateway images in the same format as the default PayPal plugin. Restructured the folder so in is setup in a way it can be copied to the root of the Magento installation as it was not clear for merchants that the code folder needed to be created when it was not existing yet. Added all images.
Changed the banktransfer payment method to a "direct" payment method. This will remove the MultiSafepay payment page and submit the payment details by e-mail to the consumer.

Release Notes - Magento 2 MultiSafepay plug-in 1.0.5 (Jne 29th, 2016)

Important
When using Magento 2.1 this release or higher should be used. Older plugin releases are not compatible with Magento 2.1
Changes
Added more space tween the iDEAL issuer selection and the address data.
Magento 2.1 update changed the way you could get the version number of Magento, this causing our extension to fail. This has been updated to the new way to get the Magento version information.
Updated the version within the module.xml so it matches the real Multisafepay used version number
Configuration file was not yet correct for Multistore support, causing configuration options not to show within the backend. Due to this issue payment method didn't show within the extra store.
Added a check for the quote. Seems like Magento update 2.1. introduced a bug causing Magento not to call the isavailable function with the quote param.

Changes
Ideal issuer selection can now be done during checkout
Refunding from within Magento using PAD or Klarna is not possible. This will be integrated when Partial Refunds are also possible.
Discounts/coupons did not yet get processed for PAD/Klarna. This is now solved. Important: Tax settings should be set to: Apply Customer Tax= Before Discount, Apply Discount On Prices= Including tax. Using other settings results in a 1027 error because Tax can't be calculated based on the other settings.

Error notice when Pay After Delivery was used with a zero shipping cost. This resulted in a division by zero within the calculation.
Added option to disable shippingmethod restriction. This can be used when third party shipping extensions are used that are not loaded to the list by Magento
Check for empty shipping method. If shipping method is emtpy then do show the payment methods as it can also be downloadable goods
Added Dotpay gateway
Renamed paypal xml to paypalmsp to avoid conflict with existing paypal extensions.