Magento Platform
Open Source (CE)
2.0, 2.1, 2.2, 2.3

Tech Specifications

Current Version:
Stable Build
03 April, 2020
Extensions, Payments & Security, Payment Integration
License Type:
Open Software License 3.0 (OSL-3.0)


Support MultiSafepay Payment methods within your Magento 2 store.

MultiSafepay makes both online and mobile payments easy for your customers.


Back to top

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.


Account & Pricing

Pricing for MultiSafepay services start at EUR 0,15 per transaction. Depending on volumes and agreement terms other pricing conditions can be agreed. You'll need a MultiSafepay account, created separately, to use the plugin. You can create an account via https://merchant.multisafepay.com/signup


Supported Payment Methods

  • iDEAL
  • Dotpay
  • Pay After Delivery
  • E-invoice
  • Klarna
  • Bancontact
  • Visa
  • Eps
  • Ferbuy
  • Mastercard
  • Bank transfer
  • Maestro
  • PayPal
  • Giropay
  • SOFORT Banking
  • Direct Debit
  • AfterPay
  • Alipay
  • American Express
  • Belfius
  • Betaalplan
  • iDEAL QR
  • ING Home'Pay
  • Paysafecard
  • Trustly


Supported Gift cards

  • 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 gift cards can be restricted to country
  • Payment methods and gift cards can be restricted to shipping method
  • Payment methods and gift cards can be restricted to currency
  • Payment methods and gift cards can be restricted to customer group
  • Payment methods and gift cards can be restricted to an order minimal amount
  • Payment methods and gift cards can be restricted to an order maximum amount



The MultiSafepay Magento 2 extensions allows you to process client payment details in a secure way. The extensions redirects your customer to the secure payment pages of MultiSafepay where the payment processing takes place and payment details are provided (submitted using a secure TLS connection), so no card details are entered or stored within the Magento environment.

The MultiSafepay secure payment pages are PCI-DSS certified and audited on an annual basis by a PCI-DSS QSA, making sure the payment is processed securely.
After the payment processing has finished a callback to your Magento environment is processed, activating a transaction status request to receive the payment status of the order (again using a secure TLS connection). Using this flow, the complete payment and notification process is safe, and you are sure hackers can’t intercept any payment/credit card data.

For further questions about security in combination with MultiSafepay you can also contact us directly by using security@multisafepay.com

Release Notes

Back to top


  • Compatible with Open Source (CE) : 2.2 2.3
  • Stability: Stable Build
  • Description:

    PLGMAGTWOS-597: Add Direct Bank Transfer

    PLGMAGTWOS-544: Replace creditcard gateway with improved creditcard gateway
    Discontinue support for Magento 2.1.x


  • Compatible with Open Source (CE) : 2.2 2.3
  • Stability: Stable Build
  • Description:

    PLGMAGTWOS-506: Enable fail save option for saving transactions.
    PLGMAGTWOS-504: Add link to the MultiSafepay update and install notification message that redirects to the MultiSafepay documentation.
    PLGMAGTWOS-483: Add Magento 2 module dependencies to composer.
    PLGMAGTWOS-479: Add PHP dependencies to composer.
    PLGMAGTWOS-471: Add option to hide MultiSafepay payment method from checkout.
    PLGMAGTWOS-454: Add translation for 'Choose your creditcard' in German.

    PLGMAGTWOS-473: Mark MultiSafepay configuration values as environment specific.
    PLGMAGTWOS-481: Change configuration allowed groups when selecting '-- Please Select --' to show payment method for all groups.
    PLGMAGTWOS-468: Decline orders if refund contains adjustments.

    PLGMAGTWOS-505: Prevent refunds at MultiSafepay with zero amount.
    PLGMAGTWOS-284: Fix error when redirecting to payment page if cart contains configurable and simple product in this order.
    PLGMAGTWOS-498: Fix uncaught TypeErrors when FastCheckout is enabled.
    PLGMAGTWOS-449: Fix payment redirect to cart instead of success page if the payment is done with the iDEAL app and iOS.

    PLGMAGTWOS-514: Remove FerBuy payment method.
    PLGMAGTWOS-452: Remove Klarna reservation number from order note.


  • Compatible with Open Source (CE) : 2.1 2.2 2.3
  • Stability: Stable Build
  • Description:


    PLGMAGTWOS-282: Added MultiSafepay payment method.
    PLGMAGTWOS-308: Added tokenization for the creditcard gateway.
    PLGMAGTWOS-404: Added payment link to order confirmation email.
    PLGMAGTWOS-350: Added order log record if MultiSafepay amount is not identical to order amount.
    PLGMAGTWOS-375: Added validation on cancel URL
    PLGMAGTWOS-376: Added validation input on redirect and notification url
    PLGMAGTWOS-365: Added globally observe shipment and order placement.
    PLGMAGTWOS-288: Added payment specification when paid with coupon and payment method.


    PLGMAGTWOS-390: Changed parsing of address fields into street and apartment.
    PLGMAGTWOS-315: Corrected spelling for ING Home'Pay.
    PLGMAGTWOS-298: Corrected spelling for default selected method.
    PLGMAGTWOS-371: Extract setMultisafepayStatus so it can be used by third party plugins
    PLGMAGTWOS-302: Changed VVV Bon to VVV Cadeaukaart.


    PLGMAGTWOS-459: Fixed orders not completed when having a prefix
    PLGMAGTWOS-381: Fixed incorrect amount for shipping cost in combination with tax and discount.
    PLGMAGTWOS-370: Fixed getMethodInstance error after checkout.
    PLGMAGTWOS-339: Fixed Api key not found for Fastcheckout on the live environment.
    PLGMAGTWOS-346: Fixed module.xml missing sequence breaking filters in sales_order view
    PLGMAGTWOS-277: Prevent protected propery error in rare cases.
    PLGMAGTWOS-331: Prevent htmlParseEntityRef in exception.log when viewing orders


    PLGMAGTWOS-287: Remove Klarna invoice link.
    PLGMAGTWOS-383: Remove support for days and seconds active for bank transfer.
    PLGMAGTWOS-301: Remove manually created payment links for Klarna, Pay After Delivery, AfterPay and Betaalplan
    PLGMAGTWOS-418: Remove second chance mail on backend orders.


  • Compatible with Open Source (CE) : 2.1 2.2 2.3
  • Stability: Stable Build
  • Description:

    PLGMAGTWOS-222: Remove PHP requirement from composer.json to fix incompatible issue with Magento 2.3.0 and PHP 7.2 requirement


  • Compatible with Open Source (CE) : 2.1 2.2
  • Stability: Stable Build
  • Description:

    # Release Notes - Magento 2 MultiSafepay plug-in 1.6.2 (Oct 24, 2018) #

    ## Changed ##
    + PLGMAGTWOS-328: Update Dutch translations. Thanks to [jeroenalewijns](https://github.com/jeroenalewijns)

    ## Fixed ##
    + PLGMAGTWOS-324: Fix expected identifier error in checkout with Internet Explorer 11. Thanks to [lexbeelen](https://github.com/lexbeelen)
    + PLGMAGTWOS-322: Fix reopened paid orders which didn't get an invoice
    + PLGMAGTWOS-231: Enable refund shipping amount when shipping includes tax


  • Compatible with Open Source (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)

    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

    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)

    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)

    When using Magento 2.1 this release or higher should be used. Older plugin releases are not compatible with Magento 2.1
    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.

    Release Notes - Magento 2 MultiSafepay plug-in 1.0.4 (Jne 23th, 2016)

    Fixes bug causing empty options within the iDEAL issuer selection

    Release Notes - Magento 2 MultiSafepay plug-in 1.0.3 (Jne 22th, 2016)

    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.

    Release Notes - Magento 2 MultiSafepay plug-in 1.0.2 (May 26th, 2016)

    Fixed an undefined notice and some issues with Klarna en PAD. Shipping percentage was calculated wrong resulted in wrong amounts (1027 error for PAD)/li>
    Fixes undefined index bug in magento caused by Magento not checking for missing data
    Fixed bug with banktransfer not showing
    Added missing namespace declaration in unused gateways and issuers files in API wrapper
    Removed beta version from composer file and update name


Back to top
The best place to start if you need help with a specific extension is to contact the developer. All Magento developers have both a contact email and a support email listed.

Q & A

Back to top


Back to top