MultiSafepay plugin for WooCommerce
| 开发者 | multisafepayplugin |
|---|---|
| 更新时间 | 2026年3月11日 19:41 |
| PHP版本: | 7.3 及以上 |
| WordPress版本: | 6.9.3 |
| 版权: | GPL-3.0-or-later |
标签
下载
6.7.2
6.8.0
6.1.0
6.1.1
4.4.1
4.1.5
4.5.0
3.7.0
4.1.3
4.1.4
3.6.1
4.13.1
5.2.2
3.5.2
4.2.0
6.5.0
4.1.1
4.8.0
6.12.0
4.1.8
6.7.0
3.8.0
4.10.0
4.11.0
4.12.0
4.15.0
4.8.1
4.8.3
4.16.0
4.17.0
4.17.1
4.5.1
4.6.0
4.7.0
4.9.0
4.17.2
3.6.0
6.11.0
6.6.2
6.8.2
6.9.0
4.1.2
4.3.0
5.1.0
5.1.2
5.2.0
5.3.0
5.4.0
5.4.1
3.5.1
4.14.0
5.2.1
6.0.0
6.10.0
6.11.1
6.8.3
4.1.7
5.0.0
6.1.2
6.3.0
6.4.0
6.4.1
4.8.2
6.4.2
4.13.0
4.2.1
6.2.0
6.2.1
6.4.3
6.5.1
6.6.1
6.7.1
3.5.0
4.1.0
4.1.6
4.2.2
4.4.0
5.1.1
6.3.1
6.6.0
6.7.3
6.8.1
详情介绍:
About MultiSafepay
MultiSafepay is a collecting payment service provider which means we take care of the agreements, technical details and
payment collection required for each payment method. You can start selling online today and manage all your transactions
from one place.
Supported Payment Methods
Payment methods:
By default, any payment method you activate in your MultiSafepay account will be available to be activated in the plugin, but you can also choose to show only specific payment methods in your checkout.
The plugin supports all the payment methods available in your MultiSafepay account, including but not limited to:
- AfterPay
- Alipay
- American Express
- Apple Pay
- Bank transfer
- Bancontact
- Belfius
- Dotpay
- E-Invoicing
- EPS
- Giropay
- iDEAL
- iDEAL+in3
- in3
- KBC/CBC
- Klarna
- Maestro
- Mastercard
- Pay After Delivery
- PayPal
- Paysafecard
- Request to Pay
- SEPA Direct Debit
- SOFORT Banking
- Trustly
- Visa
- Baby Cadeaubon
- Beauty & Wellness
- Boekenbon
- Fashioncheque
- Fashion Giftcard
- Gezondheidsbon
- GivaCard
- Good4fun Giftcard
- Goodcard
- Fietsbon
- Nationale Tuinbon
- Parfum Cadeaukaart
- Podium
- Sport & Fit
- VVV Giftcard
- Webshop gift card
- Wellness gift card
- Wijncadeau
- Winkelcheque
- YourGift
安装:
To use the plugin you need a MultiSafepay account.
Create an account
Automatic Installation
- Search for the 'MultiSafepay' plugin via 'Add New' from the WordPress menu
- Press the 'Install now' button
- Download the plugin from the WordPress Plugin Directory
- Unzip the downloaded file to a local directory
- Upload the directory 'multisafepay' to /wp-content/plugins/ on the remote server
- Activate the 'MultiSafepay' plugin via 'Plugin' from the WordPress menu
- Navigate to WooCommerce -> MultiSafepay Settings
- In Account tab, set the API key. Information about the API key can be found on our API key page. Click on Save changes button.
- Go to Order Status tab and confirm the match between WooCommerce order statuses and MultiSafepay order statuses. Click on Save changes button.
- Go to Options tab and confirm the settings for each field. Click on Save changes button.
- Navigate to WooCommerce -> Settings -> Payments. Click on the payment methods you would like to offer, check and set or confirm the settings for those been enabled. Click on Save changes button.
屏幕截图:
常见问题:
How can I install the plugin for WooCommerce?
- Installation instruction can be found in our Manual page.
How can I update the plugin for WooCommerce?
Before you update the plugin, we strongly recommend you the following:
- Make sure you have a backup of your production environment
- Test the plugin in a staging environment.
- Go to our Manual page, download the plugin and follow the instructions from step 2.
How can I generate a payment link in the backend of WooCommerce?
It is possible to generate a payment link when an order has been created at the backend in WooCommerce. The customer will receive the payment link in the email send by WooCommerce with the order details. Also, the payment link will be added to the order notes. Please follow these steps:
- Login into your backend and navigate to WooCommerce -> Orders -> Add order.
- Register the order details as explained in WooCommerce documentation.
- In "Order actions" panel; select the option "Email invoice / order details to customer".
- Click on "Create" order button.
- An email will be sent to the customer with the details of the order and a payment link to finish the order.
- The payment link will be available for the customer in their private account area, in "Orders" section.
Can I refund orders?
Yes, you can fully or partially refund transactions directly from your WooCommerce backend for all payment methods. You can also refund from your MultiSafepay Control
更新日志:
Release Notes - MultiSafepay 6.12.0 (Mar 11th, 2026)
Added
- DAVAMS-980: Add confirmation prompt when enabling direct Google Pay or Apple Pay
- PLGWOOS-1037: Potential fix for 'No payment method provided' error on WooCommerce Checkout Blocks
- PLGWOOS-1035: Fix incorrect plugin version constant in settings and order request
- PLGWOOS-1018: Add payment icons to WooCommerce Checkout Blocks
- PLGWOOS-1032: Fix WC_Blocks_Utils::has_block_in_page() fails to detect checkout block when nested inside other blocks
- PLGWOOS-1019: Fix the duplicated 'multisafepay_time_unit' setting field argument
- PLGWOOS-1029: REST Response Cache Control
- PLGWOOS-1010: Add contract type selection for Billink between B2C and B2B
- PLGWOOS-1006: Add support custom image size for Bancontact QR codes
- PLGWOOS-956: MultiSafepay PostePay is being listed as only one payment method, but it should be two
- PLGWOOS-1003: Add zip code and email format validation to QR code implementation
- PLGWOOS-1001: Improvement over QR code implementation validating checkout when "ship to a different address" is checked.
- PLGWOOS-1009: Fix Bancontact QR showing up even when it hasn’t been explicitly enabled
- PLGWOOS-1007: Refund request based on amount is including the checkout data, even when it's not needed.
- PLGWOOS-997: Validate zip code checkout fields to prevent payments via Wallets
- PLGWOOS-1002: Payment Component shows "Store my details for future visits" field, when user is not logged in
- PLGWOOS-999: Fix URL Parameter Concatenation in QR Payment Redirect Flow
- PLGWOOS-1000: Remove unneeded get_customer_ip_address() and get_user_agent() methods in QrCustomerService
- PLGWOOS-1005: Adjusting the minimum discrepancy allowed to filter Billink tax rates
- PLGWOOS-1004: Adding shipping method name in the Order Request, instead of generic label "Shipping"
- PLGWOOS-992: Prevent processing a request on the REST QR related endpoints using a security token
- PLGWOOS-990: Prevent processing a request on the REST QR related endpoints if this one is disabled
- PLGWOOS-989: Fix system report payment type to show when QR or QR only is enabled
- PLGWOOS-987: Typecast as string the value that will be defined as merchant Item ID within the QR request
- PLGWOOS-984: Catch and handle InvalidArgumentException when validating the IP Address within the order request
- PLGWOOS-982: Return early when QR webhook request fails
- PLGWOOS-978: Add Payment Component QR
- PLGWOOS-957: Fix filter that returns payment methods that supports payment component to return only enabled methods
- PLGWOOS-973: Round shopping cart item tax rates in BILLINK gateway
- PLGWOOS-971: Fix iDEAL payment method not being shown on WooCommerce Checkout Blocks
- PLGWOOS-968: Add system report values from the payment method's user role setting and enhance logging for filter methods
- PLGWOOS-967: Add filter per user role
- PLGWOOS-960: Add a transaction link in the order detail view in admin
- DAVAMS-868: Block refunds for Multibanco
- DAVAMS-875: Setup gift cards max amount to 0, because it allows partial payment
- PLGWOOS-963: Fix redirection after canceling a payment, when the user is using the "order-pay" endpoint
- PLGWOOS-961: Add double-check before addDelivery() in the order request builder
- PLGWOOS-953: Change label of the group cards setting field
- PLGWOOS-952: Fix System Report failing because WC_API not found
- PLGWOOS-950: Remove iDEAL issuers of the payment component
- PLGWOOS-946: Add support for branded credit and debit cards
- PLGWOOS-943: Refactor PaymentMethodCallback class (#574)
- PLGWOOS-948: General improvements to increase unit test coverage
- PLGWOOS-936: Fix the values set as min and max amount from payment method API request
- PLGWOOS-937: Fix Payment Components, where the amount is wrongly being set
- PLGWOOS-925: Add support for missing payments methods in WooCommerce Checkout Blocks
- PLGWOOS-933: Fix conflict with Query Monitor
- PLGWOOS-934: Fix the Google Pay button duplication issue
- PLGWOOS-935: Fix Payment Component on order-pay page endpoint, not loading if the shopping cart is empty
- PLGWOOS-922: Reduce the amount of API request improving general performance of the plugin
- PLGWOOS-922: Reduce the amount of request done to the payment-methods endpoint, from the admin
- PLGWOOS-920: Fix Apple Pay and Google Pay being shown in WooCommerce blocks, when are using direct payment buttons
- PLGWOOS-915: Add 'direct' transaction type for 'Bank Transfer' payment method
- PLGWOOS-918: Fix overwriting the payment methods name in WooCommerce Blocks
- DAVAMS-747: Fix 'template_id' within the Payment Components
- PLGWOOS-911: Fix initialisation or refreshing of the Payment Component when payment methods are assigned to specific country
- PLGWOOS-912: Ignore offline action - notifications related with pretransactions
- PLGWOOS-866: Add Apple Pay and Google Pay direct
- PLGWOOS-902: Support for WooCommerce Checkout Blocks for redirect payment methods
- PLGWOOS-901: Remove duplicated method reinit_payment_component()
- PLGWOOS-872: Add support for High-Performance Order Storage
- PLGWOOS-886: Fix the assignation of the payment method, when the selected payment method changes on the payment page, and is selected a credit card or debit card payment method, and "Group Credit Cards" setting field is enabled.
- PLGWOOS-890: Bring back the payment component setting field to allow users to disable it.
- PLGWOOS-887: Disable Payment Components for Gift Cards payment methods, even when API is returning Payment Component is allowed
- PLGWOOS-884: Add in the system report missing settings for each payment method
- PLGWOOS-882: Enable Payment Components by default in all payment methods where is available
- PLGWOOS-803: Add support to register the payment methods dynamically, via API request.
- PLGWOOS-859: Trigger checkout validations of the fields related to the payment component on checkout submission.
- PLGWOOS-857: Add support for partial refunds for BNPL payment methods