Nexi XPay Build vs WeeConnectPay – Clover Payment Gateway for WooCommerce

This module allows you to connect your e-commerce website to the XPay payment gateway. XPay is Nexi’s service that enables you to accept online and mobile payments easily and quickly. XPay is the payment gateway provided by Nexi, a leading group in Italy with the goal of shaping the future of digital payments. Nexi has a strong market position, managing 44 million payment cards and processing transactions totaling 186 billion euros. It has 860,000 affiliated points of sale in Italy, including over 18,000 e-commerce platforms that use the XPay payment gateway. XPay allows you to accept online payments and is compatible with all major payment circuits. It can handle all sales channels, including e-commerce and mobile. The XPay Build extension for WordPress/WooCommerce enables you to integrate the XPay payment gateway into your website without additional implementations. XPay Build is a solution that allows, through the use of a Javascript SDK client, to host the payment form within your site, without redirecting the customer to the XPay checkout page, but at the same time avoiding to manage the card data. The extension is regularly updated to incorporate the advancements and improvements of XPay. To use the extension, you need an XPay account, which you can easily obtain online at https://ecommerce.nexi.it/. XPay Module Features XPay Build: Entry form for card data on your site without redirections on external cash pages. One-Click Payment: Allows the end customer to store their credit card data and use it for future purchases with a single click. Recurring Payment: Enables the merchant to tokenize the customer’s card data, allowing for recurring billing and subscriptions. To enable recurring payments, you need to install the WooCommerce Subscriptions extension. Pay-By-Link: Enables sending a payment link to the customer via email or social media. Transaction Management: Supports international payment circuits such as Visa, Mastercard, Visa Electron, V-Pay, Maestro, American Express. Acceptance of Alternative Payment Systems: (PayPal, Amazon Pay, Apple Pay, Google Pay, Bancomat Pay, MyBank, iDeal, Bancontact, GiroPay, etc.) Easy Checkout: Provides a simple and intuitive payment interface (Nexi checkout page with merchant logo). Testing Area: Allows testing the module’s functionality using dummy parameters and cards, without conducting real transactions. Multilingual Support: Recognizes the language of the merchant’s portal and automatically sets it in the XPay checkout page. Accounting Management: Allows configuring the collection mode (total or partial, immediate or deferred) directly from the module. Back-Office Operations: Enables refund and cancellation operations directly from the CMS order management, without accessing the XPay back office. 3D Secure 2: Implemented by major international circuits (Visa, MasterCard, American Express), introduces new authentication methods to enhance and expedite the cardholder’s purchasing experience. Depending on your agreement and plugin configuration, the availability of XPay features may vary. For more information, please consult the technical specifications in the subscribed service’s developer portal. You can find the link to the technical specifications in the welcome email received upon service activation. For more information, please visit https://ecommerce.nexi.it. Configuration Go to the WooCommerce settings and click on “Payments.” Click on Nexi XPay Build to proceed with the configuration. Enable the payment method. Choose between the options Alias – MAC Key or API Key based on the subscribed service. Enable/Disable the test mode to test the module using the test credentials provided by Nexi. Click on Save. Adding/Removing Alternative Payment Methods To add or remove alternative payment methods, you need to access the XPay back office. After making any changes, save the XPay module configuration to update the payment methods. Bancomat Pay The plugin updates the order status through a notification sent by Nexi’s servers. If the module doesn’t receive the notification correctly, it won’t be able to update the status. By default, in case of notification issues (unreachable site, errors received from the merchant’s site), the transaction is canceled, even if the payment is successfully completed. This behavior ensures that the status of Nexi transactions aligns with the order status in the CMS. The option to cancel the transaction in case of failed notification is not available with the Bancomat Pay payment method. In case of notification anomalies, there might be discrepancies between the order status returned by the plugin and the actual transaction status on the Nexi side. Therefore, the following scenario may occur: the Bancomat Pay payment is successfully made with a positive outcome, but due to a notification problem, the plugin is unable to update the order status to “Processing.” This payment method doesn’t support transaction refunds. In case of a refund, the merchant will need to proceed with a bank transfer or another method.

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.