Toggle Nav
Menu
Account
  • Sign In
    • Search

    Powered by Adobe Commerce 2.4.6-p4

    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.
    logomps240.png

    MultiSafepay Payments

    by MultiSafepay B.V.
    main product photo
    PRODUCT:
    0
    TOTAL:
    Contact Vendor

    Overview

    Back to top

    MultiSafepay is a leading end-to-end processing and acquirer payment platform for European merchants, providing frictionless online, in-person, and omnichannel payment solutions. Through our cutting-edge, in-house developed technology, more than 20,000 European businesses of all sizes have been able to focus on growth and innovation.

    As an acquirer for the major card schemes and provider of more than 40 global and local payment methods across 35 integrations, our merchants have access to advanced omnichannel technology for a wide range of markets. 

    Our top-of-the-line Magento 2 plugin can be connected to your payment platform and gives you access to all features of our payment platform - ranging from all major European payment methods and security systems to various tools to grow your Magento shops, 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.

    Features

    Our plugin, your 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. 

    One tool to manage your operations: 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. 

    Always receive the latest updates: Our highly skilled and dedicated in-house Magento 2 developers constantly create innovative solutions tailored to your needs. By using our own code, we maximize the safety of our plugin.

    Boost your conversion: Use our very own Buy Now, Pay Later solution, Pay after Delivery, or our MultiSafepay payment links to improve your business operations and work more efficiently.

    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. 

    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: Enable your customers to purchase products directly through an instant purchase button. If your customer has several checks enabled (e. g. default billing/shipping address and payment methods), they can use this button to pay directly from your product page.

    Second chance emails: If customers abandon their purchase early, you can automatically send payment links to your customers and bring them back to finish their order. 

    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 such as digital wallets and Buy Now, Pay Later solutions.

    Customized checkouts: Create the right checkout for your customers. Show or hide payment methods based on specific conditions, such as min/max cart amount, currency, customer group, and 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, giving you access to over 40 local and international payment methods.  

    You can pick and choose from this payment mix to create the best payment method mix. We recommend picking payment methods that are popular in your markets and displaying them as the top ones. If you need advice for this, our experts will gladly assist you. 

    Our Magento plugin supports the majority of our payment methods, but here's a selection of some of them: 

    • Apple Pay
    • Google Pay
    • PayPal
    • iDEAL
    • Bancontact
    • MyBank
    • Klarna
    • Riverty
    • Pay After Delivery
    • Mastercard
    • Visa
    • American Express

    If you'd like to see the full overview, please visit our dedicated page 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. Using our own code 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 ensures 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 order's payment status (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

    3.4.0

    Adobe Commerce platform compatibility

    Adobe Commerce (cloud): 2.4 (current), 2.3 (obsolete)

    Adobe Commerce (on-prem): 2.4 (current), 2.3 (obsolete)

    Magento Open Source: 2.4 (current), 2.3 (obsolete)

    Type

    Stable Build

    Updated

    19 February, 2024

    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

    3.4.0:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Added
      -DAVAMS-716: Add Multibanco
      -DAVAMS-724: Add MB WAY

      ### Fixed
      - PLGMAG2V2-728: Add recurring data when customer_id is in additional info
      - PLGMAG2V2-725: Fix broken gift card gateway ids
      - PLGMAG2V2-727: Fix payment component sometimes not loading

      ### Removed
      - PLGMAG2V2-726: Remove startSetup and endSetup commands from UpgradeData

    3.3.2:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Changed
      - PLGMAG2V2-718: Remove gateway codes from Edenred title
      - PLGMAG2V2-716: Refresh API Token and component after expiry
      - PLGMAG2V2-720: Only set order canceled on notification controller

    3.3.1:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Fixed
      - PLGMAG2V2-715: Fixed an issue where pretransaction notifications would be processed for canceled orders

      ### Changed
      - DAVAMS-700: Refactored in3 Direct to only make gender mandatory
      - PLGMAG2V2-714: POST notifications will now always be logged, instead of only when the verification fails
      - PLGMAG2V2-709: The DataAssignObserver for Card payments will now return early whenever the payload is already defined

      ### Removed
      - DAVAMS-708: Removed Santander Betaal Per Maand

    3.3.0:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Fixed
      - PLGMAG2V2-705: Fixed a bug where the notification process would not finish due to an empty 'Auth' header in the POST webhook request
      - PLGMAG2V2-708: Fixed Hyva React Checkout OutOfBoundsException when it is installed through app/code
      - PLGMAG2V2-688: Fixed an issue where coupons would not be restored if the payment was canceled/declined
      - PLGMAG2V2-711: Fixed an issue where it was not possible to do refunds for a generic gateway that requires the shopping cart

      ### Added
      - DAVAMS-531: Added an advanced setting for adding a template ID to be used for payment components
      - DAVAMS-676: Added preset gateway filters for Zinia
      - DAVAMS-596: Added a setting to choose SVG icons instead PNG

      ### Changed
      - PLGMAG2V2-704: For E-invoicing, there will be no invoice e-mails sent from Magento, since E-invoicing handles invoice e-mails on the payment side

    3.2.1:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Fixed
      - PLGMAG2V2-702: Fixed an issue where in some cases the wrong transaction_type would be used for some 'Direct' payment methods

    3.2.0:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Added
      - PLGMAG2V2-700: Added Edenred Consumption Voucher (EDENCONSUM)
      - PLGMAG2V2-699: Added support for simple products that have custom options configured with no custom SKU
      - DAVAMS-661: Added the Zinia payment method
      - PLGMAG2V2-687: Added support for adjustment refunds

      ### Fixed
      - PLGMAG2V2-690: Fixed direct payment methods doing redirect when direct is configured
      - PLGMAG2V2-692: Fixed bundle product shopping cart refund

      ### Changed
      - PLGMAG2V2-688: Changed notification delay to add Canceled, Void, Expired and Declined statuses
      - PLGMIRAKL-58: Excluded custom total 'marketplace_shipping' from Mirakl since it will be added by the MultiSafepay Mirakl module instead
      - DAVAMS-643: Refactored and improved the processing of payment component recurring tokens

    3.1.3:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Added
      - PLGMAG2V2-681: Added translations for title and placeholder HTML attributes

      ### Fixed
      - PLGMAG2V2-691: Fixed an issue with Pay After Delivery Installments refunds
      - PLGMAG2V2-696: Fixed an issue where notification requests would require a lot of time to process, in some cases causing a timeout

      ### Changed
      - PLGMAG2V2-683: API tokens are now stored and retrieved through the cache
      - PLGMAG2V2-680: Replaced var with let in validate API key button function

      ### Removed
      - PLGMAG2V2-694: Removed class import dependency on Magento_Giftcardaccount for CustomTotalBuilder
      - PLGMAG2V2-676: Removed unused getCheckButtonId() function

    3.1.2:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Fixed
      - PLGMAG2V2-682: Fixed an issue where Google Pay and Apple Pay were not redirecting to the payment page
      - PLGMAG2V2-675: Fixed an issue where cron job sales_clean_orders failed when order contains no payment method
      - PLGMAG2V2-679: Fixed an issue where the integration tests were reporting the wrong code coverage percentages

      ### Changed
      - PLGMAG2V2-664: Refactored the CreateInvoice procedure.

      ### Removed
      - PLGMAG2V2-669: Removed the setup_version from the module.xml
      - PLGMAG2V2-674: Removed use of SecureHtmlRenderer to be backwards compatible with version 2.3

    3.1.1:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Added
      - Added the functionality to add plugin data information for other enabled third party plugins, starting with Hyva React Checkout

      ### Fixed
      - Fixed an issue where incorrect item prices would show in combination with the Meetanshi Vat Excemption module

      ### Changed
      - Changed the OrderItemBuilder to make the procedure of modifying the merchant item id using a plugin interceptor class easier
      - Changed the 'Credit Card' method default title to 'Card Payment' according to the latest standards
      - Changed the scope of some variables in Config and SdkFactory

      ### Removed
      - Removed the setup_version from the module.xml

    3.1.0:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Added
      - Add payment component for Pay After Delivery installments
      - Give the option to set 3 different icons for payment method Credit Card
      - Add a setting field to exclude utm_nooverride from the redirect_url

      ### Changed
      - Refactor Credit Card Payment Components
      - Rebrand Sofort

      ### Fixed
      - Fix Riverty and in3 component rendering, failing in some third party checkouts

    3.0.0:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Added
      - Added new service interfaces, processes and a controller for processing notification webhooks

      ### Changed
      - Changed to use asString methods in Customer and Delivery Builders
      - Refactored notification webhook process. Notification webhooks are now processed in the core module and not in the frontend module

      ### Removed
      - Removed the dependency for zendframework/zend-http and laminas/laminas-http, to be compatible with Magento ^2.3.0 and ^2.4.0
      - Removed capture options from manual invoice in credit card methods to make that process have one manual action less

    2.22.0:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Added
      - Added support for optional customer city argument
      - Added raw response data to Apple Pay Merchant Session request logs for better debugging possibilities
      - Added improved response handling for Pay After Delivery and Klarna refunds

      ### Fixed
      - Made all the config field labels translatable
      - Fixed '1000 Required Fields error' in rare cases when creating a shipping update request
      - Made sure checkout loads correctly if API is unreachable

      ### Changed
      - Rebranded AfterPay to Riverty
      - Changed labels of when to send the order confirmation email
      - Retrieving issuers for a gateway will only be done when the gateway has been activated
      - The payment will now only be saved after redirect whenever sensitive information has been detected and removed from the payment additional information
      - Changed the POST notification process to only retrieve the order after POST validation has passed
      - Improved the error message that is shown to the customer whenever the payment fails.
      - Checking for recurring tokens will only occur now when Magento Vault is enabled.

    2.21.1:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Fixed
      - Fixed a TypeError which happened in some instances when trying to retrieve E-invoicing dynamic checkout fields.
      - Fixed an issue where overriding when to send the order confirmation e-mail on gateway level sometimes did not work.
      - Fixed an issue where it was not possible to refund orders created with a generic gateway
      - Fixed references related to the E-Invoicing configurable 'account_number' field

      ### Changed
      - Skipped E-invoicing validation if payment method is set up as redirect

    2.21.0:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Added
      - Payment links will now always be added to the order comment history again. For backend orders it happens immediately, for frontend orders it now happens when the first MultiSafepay notification arrives.
      - Added Amazon Pay.
      - Added an option for E-invoicing to assign collecting flow ids to specific customer groups.
      - Added an option for E-invoicing to turn on and off certain checkout fields.

      ### Changed
      - Magento Vault stored payment methods now change to the gateway where the card was last used.

    2.20.1:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Fixed
      - Fixed a bug where in rare instances Magento Vault would cause a 'unique constraint violation' when trying to save a payment token.
      - Fixed an Uncaught TypeError when trying to log the order if the order ID can't be found.

    2.20.0:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      ### Added
      - Added the MyBank payment method
      - Improved logging for failed POST notifications
      - Added support for keeping the cart alive when using FireCheckout (Thanks to @mlaurense)

      ### Fixed
      - Fixed an issue where in some cases VISA transactions could not be refunded through the backend
      - Fixed dead docs links in the configuration and support page for specific articles like tokenization and vault.
      - Prevented double execution of order transaction processing when the POST notification fails

      ### Removed
      - Removed payment method docs links in the configuration page

    2.18.0:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 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 Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 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 Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 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 Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 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 Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 2.3 2.4
    • Stability: Stable Build
    • Description:

      Fixed
      - Fixed notification process for sequential offline actions

    2.11.0:

    • Compatible with Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 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 Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 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 Adobe Commerce (cloud) : 2.3 2.4
    • Compatible with Adobe Commerce (on-prem) : 2.3 2.4
    • Compatible with Magento Open Source : 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