MANGOPAY for WooCommerce vs WeeConnectPay – Clover Payment Gateway for WooCommerce

Caution – Deprecated and no longer available This plugin has been deprecated and should no longer be used for new integrations. As per Mangopay’s email of June 2025, Mangopay clients must integrate directly, rather then using this plugin, to continue using Mangopay’s services. Any existing plugin users must contact Mangopay as soon as possible via the Mangopay Dashboard. The plugin will be removed from WordPress once there are no further users. MANGOPAY is a payment solution which allows marketplaces to process third-party payments and collect their commissions in a secure and compliant environment. Our wordpress plugins enable an easy and fast integration to create a marketplace from start to finish and process payments. Plugged to WC Vendors and WooCommerce’s plugins, the MANGOPAY WooCommerce plugin gives the ability to marketplaces hosted on WordPress to accept worldwide credit/debit card payments. It enables the management of vendors’ commissions within the wordpress interface, including payouts, transfers, and platform fees collection. Some key features include: Multi-currency support Handle international and local payment methods Seamlessly escrow and split funds between users Safeguard transactions with our fraud prevention tools and built-in anti-fraud engine White-label payment page PCI DSS, DSP2 and AML4 compliant For more information please visit MANGOPAY.COM Plugin usage The MANGOPAY plugin simply connects your WordPress stores with MANGOPAY’s API. The payment workflow is as follows: Step 1 : Vendors sign-up to the marketplace. An associated user is created in MANGOPAY’s environment. Step 2 : Vendors complete their profile with the right verification documents. The documents are verified by MANGOPAY’s compliance team. Step 3 : Products are assigned to vendors. Step 4 : An order is placed. E-money is stored in the buyer’s e-wallet. Step 5 : Vendors mark each product as dispatched. Step 6 : The marketplace operator marks the order as completed. Funds are now transferred from the buyer’s e-wallet to the vendor’s e-wallet. Marketplace commissions are collected here. Step 7 : The marketplace operator initiates the vendor payout. Funds are paid from the vendor’s e-wallet to his bank account. Documentation This document will guide you through 3 plugin setups which will enable your marketplace to accept worldwide credit/debit card payments, manage vendors, payouts, transfers, and platform fees. External services This plugin connects to an online banking API to perform payment validation, it is needed to accept Mangopay as a payment gateway. The domains used by this API are: * www.mangopay.com (for service sign-up and access to the marketplace operator dashboard) * api.mangopay.com (for production shops) * api.sandbox.mangopay.com (for testing and debugging) * docs.mangopay.com (for documentation) It sends the user’s Mangopay account as well as any information related to payment data and order history, whenever a user creates an account, performs payment operations, or consults order payment information. This service is provided by “Mangopay S.A.“: terms of use, privacy policy. Depending on payment settings, the Mangopay payment gateway uses Payline services when enabled. This will embed the third-party payline widget from its remote official source location at payline.com (remotely-loaded JavaScript and CSS files) The embedded form takes care of securely transmitting credit card information online when a shopper performs a credit card payment. This service is provided by “Monext”: terms of use, personal data and privacy policy. The domains used by this service are: * payment.payline.com (for production shops) * homologation-payment.payline.com (for testing, debugging and vendor homologation process) Embedded code This plugin includes the Mangopay PHP-SDK maintained and secured by Mangopay S.A. It is necessary for secured communication with the Mangopay banking API. This code is located in the /sdk folder of the plugin. More information here: https://github.com/Mangopay/mangopay2-php-sdk To use this SDK, you will need (as a minimum): * PHP 5.6 or newer * cURL (included and enabled in a standard PHP distribution) * OpenSSL (included and enabled in a standard PHP distribution) Installation Before starting, make sure your WordPress environment meets the requirements listed above. To install the MANGOPAY Woocommerce plugin: Go to your WordPress admin plugin section. Add new plugin. MANGOPAY WooCommerce. Install the plugin (automatic plugin installation is fully supported). Activate the plugin. From the main left menu choose “MANGOPAY”. It will lead you to the settings page. Enter your ClientId/API key. Save this info. Verify your configuration under the “MANGOPAY status”. The various checks should all be in green for your setup to function correctly. Updating Automatic updates should work as normal; as always, backup your website before proceeding with the installation.

WeeConnectPay connects your WooCommerce store to your Clover account. Shoppers pay by card or Google Pay without leaving your checkout, and every online sale lands in Clover next to your in-store sales, with the tax, stock, and order detail you choose to send along. Payments – Card details are entered in secure fields provided by Clover, directly on your checkout page, on both the Classic and Block-based checkout. Card numbers never pass through your site. – Google Pay express checkout, when enabled on your store. – Three transaction modes, named for what they do: Charge at checkout, Hold and charge later, and Order and charge, which also creates the matching order in your Clover dashboard. – Refunds from WooCommerce’s own Refund button, including several partial refunds on the same charge, with a note on the order for everything that happens. Clover reporting, taxes, and stock – Tax reporting: link your WooCommerce tax rates to your Clover rates, then choose what each payment reports to Clover: nothing, the total only, or each rate by name. – Stock sync: link your products to your Clover inventory items and choose a mode: Off, Preview only, Follow Clover, or Two-way. – Inventory Tools: move your catalog in bulk. Export WooCommerce products to Clover, or import Clover items into WooCommerce. – All of this is off until you turn it on, and none of it can ever block a payment. Day to day – Fully available in English and in French. – Clear notes on every order: what was charged, what was refunded, and the real reason when a card is declined. – A visible notice when your Clover connection needs attention, which clears itself once you reconnect. Doing business together Doing business with WeeConnectPay means being heard. The team that builds the plugin is the team that answers you, and requests from merchants like you regularly become features in the next update. WeeConnectPay requires a Clover merchant account. You can apply through WeeConnectPay, where you will also find pricing and documentation. Privacy and Data Collection Payment processing. As a payment gateway, this plugin sends checkout and order information (line items, amounts, taxes, and the customer details required to process the payment) to the WeeConnectPay service you connected during onboarding, which processes the payment through Clover. This is the service the plugin exists to provide. Error diagnostics (off by default). The plugin can send technical error reports to WeeConnectPay to help diagnose a problem on your store. This is disabled by default and only turns on when you ask WeeConnectPay support for help and a support agent opens a temporary diagnostic window for your store. The window expires automatically after at most 7 days and can be closed earlier by support on request. While the window is open, if the plugin’s own code encounters an error, a report is sent to WeeConnectPay containing: the technical error type and message, the location of the error inside this plugin’s files, and the plugin, WooCommerce, WordPress, and PHP version numbers. Error reports never include customer names, emails, addresses, order contents, payment details, cookies, or form submissions. When the window is closed or expired, nothing is sent. No analytics, usage tracking, or advertising data is ever collected. Bot protection (optional, off by default). If you turn on Google reCAPTCHA v3 in the plugin settings, your checkout page loads Google’s reCAPTCHA script (https://www.google.com/recaptcha/api.js) and Google assesses each checkout attempt. Google receives the shopper’s IP address, browser information, and interaction signals from the page, and returns a score the plugin uses to decide whether to let the payment through. Google’s handling of that data is covered by the Google Privacy Policy (https://policies.google.com/privacy) and the Google Terms of Service (https://policies.google.com/terms). Nothing is sent to Google when this setting is off, which is the default.