Powered by Adobe Commerce 2.4.5

This extension is in our Payment category. Please remember that it is the merchant’s responsibility to ensure the proper PCI compliance level of their store, as applicable by PCI regulations. The PCI Self-Assessment is one tool you can use when evaluating Payment extensions and how they may affect your PCI compliance level. For more information on Marketplace policies, please review the Marketplace Terms & Conditions.
multisafepay_payments.png

MultiSafepay Payments

PRODUCT:
0
TOTAL:

Overview

Back to top

MultiSafepay is a Payment Service Provider working to remove barriers for commerce. We help you make online, mobile and in-store payments easy for your customers while ensuring a seamless and secure payment process with our in-house developed solutions and ecommerce tools.

Our recently released Magento 2 plugin can be connected to your payment platform and gives you access to all features of MultiSafepay's payment platform - ranging from all major European payment methods, and security systems to various tools to grow your Magento shop, such as Magento Vault, Instant Purchase and many more. Our plugin is professionally supported by a certified Magento 2 Solution Specialist who constantly develops and updates his product to ensure that you always have access to the newest and best features. Our plugin makes the integration of various payment methods and solutions easier than ever - don’t risk losing conversations because you don’t offer your customers preferred payment method.

 

Account & Pricing

You'll need a MultiSafepay account, created separately, to use the plugin. You can create an account here.

Your pricing can be individually calculated for your needs - depending on volumes, order value, and relevant payment methods. For more information on pricing contact us.

 

Features

  • Personalized and easy integration. The installation process of our integrations is easy and entirely modular. Choose what you need and simply test our integrations and all payment methods by switching between test and live environment during setup.
  • Get started today. Setting up and activating your MultiSafepay account is fast and allows you to start accepting payments today. Create your account
  • MultiSafepay control. Get access to a suite of specialized tools and solutions. Manage all your payments via one platform: Payout balances, make refunds, import transaction data directly into your accounting software, and much more. 
  • In-house development. Our highly skilled and dedicated in-house Magento 2 developers are constantly creating innovative solutions specifically tailored to your needs - maximal safety by using our own code.
  • Conversion increasing tools. Our ecommerce solutions such as our very own “buy now - pay later” option Pay After Delivery or our MultiSafepay Payment Links will allow you to generate key profits.

 

Integration specific features

  • Magento Vault: Our latest Magento 2 integration provides you with Magento Vault, which is essentially Tokenization. Storing related payment methods as a token in the Magento database facilitates a fast and secure checkout process for your returning customers. 
  • Magento Instant Purchase: This feature enables your customers to directly purchase products through an instant purchase button if your customer has several checks enabled (e. g. default billing/shipping address and payment methods).
  • Second chance emails: Automatically send payment links to your customers and recover abandoned transactions. 
  • Popular payment methods and gift cards: Being an acquirer and processor for credit cards such as VISA and Mastercard, we offer you a complete range of local and cross-border payment methods including innovative digital solutions (digital wallets, buy now - pay later solutions).
  • Customized checkouts: Show/hide payment methods by specific conditions: Min/max cart amount, currency, customer group, country
  • Fully-compatible with GraphQL for easy integration in PWA storefront: Possibility to use GraphQL queries, set custom cancel, success redirect URLs, and much more.

 

Payment methods supported

The integration can be connected to our payment platform and gives you access to over 30 local and international payment methods.  

This way, we make it possible to create the best payment method mix by offering the most frequently used payment methods of the countries you are operating in. Easily expand your cross-border sales and explore new markets.

MultiSafepay's integration currently supports the following payment methods: AfterPay, Alipay, American Express, Apple Pay, Bancontact, Bank transfer, Belfius, Betaalplan, CBC, Direct Bank Transfer, Direct Debit, Dotpay, E-Invoicing, EPS, Giropay, iDEAL, iDEAL QR, in3, ING Home'Pay, KBC, Klarna, Maestro, Mastercard, MultiSafepay, Pay After Delivery, PayPal, Paysafecard, SOFORT Banking, Trustly, Visa.

Full list of supported payment methods and gift cards you can find here.

 

Security

At MultiSafepay, we pride ourselves on ensuring maximal safety and security. All our payment pages are PCI-DSS certified and offer optimal fraud protection, such as the highest. Using our own codes and developing all our integrations in-house, we can ensure maximal safety and security and detect any potential problems early. Being an acquirer and processor for credit cards such as VISA and Mastercard, MultiSafepay does not rely on third-parties to process transactions and manages the entire end-to-end payment flows.

The MultiSafepay Magento 2 integration redirects your customer to the secure payment pages of MultiSafepay, where the payment takes place, and payment details are processed (submitted using a secure TLS connection). This way, no card details are entered or stored within the Magento environment. 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). During this flow, the complete payment and notification process is safe, and you are sure hackers cannot 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.

 

Need assistance?

Find out everything you need to know in the MultiSafepay Documentation Center, from Integration to Frequently Asked Questions.

Set up your account and get started today. If you need help from the integration team, want to contact our sales department or have any questions, please contact us.

Technical Specifications

Back to top

Seller profile

MultiSafepay B.V.

Seller contact

E-mail

Current Version

2.18.0

Adobe Commerce platform compatibility

Open Source (CE): 2.3 (current), 2.4 (current)

Commerce on prem (EE): 2.3 (current), 2.4 (current)

Commerce on Cloud (ECE): 2.3 (current), 2.4 (current)

Type

Stable Build

Updated

04 July, 2022

Categories

Extensions, Payments & Security, Payment Integration

Supported Browsers

Chrome, Firefox, Opera, Safari, Edge, IE

Documentation

User Guides

License Type

Open Software License 3.0 (OSL-3.0)

Policy

Privacy Policy

Quality Report

Back to top

Installation & Varnish Tests

Passed

Coding Standard

Passed

Plagiarism Check

Passed

Malware Check

Passed

Marketing Review

Passed

Manual Testing

Passed

All tests were conducted on the latest versions of Adobe Commerce that existed for the compatible release lines at the moment of the extension submission. Latest versions of all other software were used, as applicable.

Release Notes

Back to top

2.18.0:

  • Compatible with Open Source (CE) : 2.3 2.4
  • Compatible with Commerce on prem (EE) : 2.3 2.4
  • Compatible with Commerce on Cloud (ECE) : 2.3 2.4
  • Stability: Stable Build
  • Description:

    ### Added
    - Added Vault for Maestro
    - Added the Alipay+ payment method
    - Added Tokenization (embedded) for the following gateways:
    - American Express
    - Credit Card
    - Maestro
    - Mastercard
    - Visa

    ### Fixed
    - Fixed an issue where placing orders through some gateways with GraphQL returns an error
    - Fixed an issue where there would be duplicated tokens stored in Vault in some rare cases
    - Fixed the sorting of the generic gateways to be always at the bottom
    - Fixed field dependencies of all the gateways to always depend on the 'active' field

    ### Changed
    - Changed the styles and images according to the new rebranding guidelines

2.17.2:

  • Compatible with Open Source (CE) : 2.3 2.4
  • Compatible with Commerce on prem (EE) : 2.3 2.4
  • Compatible with Commerce on Cloud (ECE) : 2.3 2.4
  • Stability: Stable Build
  • Description:

    ### Fixed
    - Fixed an issue with the timing of request timeouts for incoming notifications

2.17.1:

  • Compatible with Open Source (CE) : 2.3 2.4
  • Compatible with Commerce on prem (EE) : 2.3 2.4
  • Compatible with Commerce on Cloud (ECE) : 2.3 2.4
  • Stability: Stable Build
  • Description:

    ### Fixed
    Fixed an issue where in rare cases the salable quantity would be incremented twice when a transaction is canceled or declined

2.17.0:

  • Compatible with Open Source (CE) : 2.3 2.4
  • Compatible with Commerce on prem (EE) : 2.3 2.4
  • Compatible with Commerce on Cloud (ECE) : 2.3 2.4
  • Stability: Stable Build
  • Description:

    ### Added
    - Added an option to skip the bank details page after placing an order for the Bank Transfer payment method
    - Added AfterPay terms and conditions checkbox to the checkout fields

    ### Fixed
    - Fixed an issue where MultiSafepay orders in state pending_payment could not go to processing if the order was paid through another way.
    - Fixed an issue with a circular dependency in the Config, which shows up during a setup:upgrade command.
    - Fixed an issue with the custom REST API endpoint for retrieving the payment URL for a specific logged in customer, where it returned an incorrect type use error.
    - Fixed an issue with the Amasty_OrderStatus module where it wasn't able to correctly save an order comment after placing it.
    - Fixed the alignment of the CCV field inside the Credit Card Payment Component

    ### Changed
    - Deprecated ING Home'Pay
    - Added changes that are required for PHP 8.1:
    - Added function type declarations
    - Changed namespaces to be declared on a single line
    - Added null coalescing operator for when haystack parameter for the strpos() function is null
    - Removed the dependency for Guzzle 6 and replaced it with a custom client implementation based on the Magento Curl Adapter
    - Removed the dependency for php-http/guzzle6-adapter and replaced it with nyholm/psr7

2.16.1:

  • Compatible with Open Source (CE) : 2.3 2.4
  • Compatible with Commerce on prem (EE) : 2.3 2.4
  • Compatible with Commerce on Cloud (ECE) : 2.3 2.4
  • Stability: Stable Build
  • Description:

    Fixed
    - Fixed notification process for sequential offline actions

2.11.0:

  • Compatible with Open Source (CE) : 2.3 2.4
  • Compatible with Commerce on prem (EE) : 2.3 2.4
  • Compatible with Commerce on Cloud (ECE) : 2.3 2.4
  • Stability: Stable Build
  • Description:

    Added
    - Added automatic cancellation of MultiSafepay pretransactions for non-paid canceled orders.
    - Added plugin version to the system report log
    - Added possibility to skip automatic invoice creation after MultiSafepay payment.

    Fixed
    - Fixed a bug where manual invoices for backend created orders did not go to processing state.
    - Fixed a bug where filling in certain wrong values for the Date of birth field for AfterPay and in3 caused an error
    - Fixed a bug where "Unable to unserialize value" errors were logged for every product.
    - Fixed a bug where the shipping description in the transaction would cause an error if it was null
    - Fixed a bug where some header elements were still visible inside the checkout
    - Fixed a bug where the MultiSafepay payment component external js file could not be loaded when using Magento javascript minification

    Changed
    -Improved several UI and UX elements:
    -- Added a notice with a link to the MultiSafepay Merchant Control Panel under the API key field
    -- Added enabled/disabled indicators next to the gateways and giftcards
    -- Added a MultiSafepay mention to the Payment configuration page at Stores > Configuration > Sales > Payment Methods with a link to sign up. Clicking on configuration will redirect to the MultiSafepay General Settings page

2.7.0:

  • Compatible with Open Source (CE) : 2.3 2.4
  • Compatible with Commerce on prem (EE) : 2.3 2.4
  • Compatible with Commerce on Cloud (ECE) : 2.3 2.4
  • Stability: Stable Build
  • Description:

    Added:
    -Added option to set no default for default selected payment method.
    -Added a download button to download a zip file with the MultiSafepay log files

    Fixed:
    - Fixed an error that happened when trying to open orders with an expired transaction.
    - Fixed issue related to a missed tax amount in Fooman Surcharge custom totals
    - Fixed error when choosing 'miss' gender with Afterpay
    - Fixed an error that happened during checkout when there is a custom total in the cart with float as a string value ("0.000")
    - Fixed issue where default pending status would get used instead of the one from the MultiSafepay config

    Changed:
    - For bank transfer payments, the redirect to the payment page has been brought back. Like with Magento 1, customers will now get redirected to the payment page where they can see the bank transfer details.

    Removed:
    - Removed order status check and reopening a cancelled order process from the Success controller, since it is already being done by the Notification controller instead.

2.6.0:

  • Compatible with Open Source (CE) : 2.3 2.4
  • Compatible with Commerce on prem (EE) : 2.3 2.4
  • Compatible with Commerce on Cloud (ECE) : 2.3 2.4
  • Stability: Stable Build
  • Description:

    Added support for disabling the shopping cart on the MultiSafepay payment page
    Added information about the Magento edition to the order request.
    Added additional quote masked_id and entity_id parameters to the cancel and success payment urls
    Fixed error when creating transaction without available phone number
    Fixed a bug where the wrong processing status was set for the notifications
    Removed obsolete emandate field from Direct Debit checkout
    Changed validation for direct payment methods to prevent 400 (Bad Request) errors on selecting payment method
    Improved the logging for the notification offline actions

Support

Back to top

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

Contact Vendor

Q & A

Back to top

Reviews

Back to top