WeeConnectPay – Clover Payment Gateway for WooCommerce

Beskrivning

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.

Skärmdumpar

Installation

Minimum Requirements WooCommerce >= 3.0.4

Further minimum requirements for WooCommerce: PHP 7.4 or greater PHP Module INTL enabled MySQL 5.6 or greater WordPress 5.6 or greater Permalink URL structure to be set to anything other than ’plain’ WP Memory limit of 64 MB or greater (128 MB or higher is preferred)

Additional Plugin Requirements WordPress database table prefix must be properly set and not left empty

In addition, you need an approved business account with Clover. You can submit a request through WeeConnectPay.

Automatic Installation This is the easiest way to install the WeeConnectPay plugin:

  1. Log into your WordPress installation.
  2. On the left menu bar, select ”Plugins”, then ”Add New”.
  3. Search for ”WeeConnectPay”. In cases where several plugins are listed, check if ”WeeConnectPay” is the plugin author.
  4. Click ”Install Now” and wait until WordPress confirms the successful installation.
  5. Activate the plugin. You can find the settings here: WooCommerce > Settings > Payments > WeeConnectPay.
  6. Click ”Connect to Clover” on that settings page and sign in with the Clover account that owns your merchant business. The setup wizard then walks you through the rest (transaction mode, payment methods, fraud protection).

Important: You need WooCommerce 3.0.4 or higher to use WeeConnectPay. Otherwise, the settings page of the plugin won’t be available. You will get a notification in your WordPress backend if you don’t use the correct WooCommerce version.

Manual Installation In case the automatic installation doesn’t work:

  1. Download the plugin from here via the Download button.
  2. Unpack the archive and load the folder via FTP into the directory wp-content/plugins of your WordPress installation.
  3. Go to Plugins => Installed plugins and click Activate on WeeConnectPay for WooCommerce.

Vanliga frågor

I installed a previous version of WooCommerce. Will I be able to use WeeConnectPay for WooCommerce?

No, the plugin is only compatible with WooCommerce versions >= 3.0.4 and we advise you to update to one of these versions. But don’t forget to make a backup of your installation first. For making a backup use our free WordPress backup plugin BackWPup.

Am I able to use WeeConnectPay for multiple ecommerce shops?

Yes, you can use the WeeConnectPay plugin on various online stores with WooCommerce.

With WeeConnectPay for WooCommerce, which payment methods can I integrate into my shop?

With our plugin, you can integrate both credit and debit card payment options.

Can I use WeeConnectPay for digital products?

Yes!

Does WeeConnectPay allow subscription payments?

Yes! WeeConnectPay fully supports subscription and recurring payments. You can use WooCommerce Subscriptions or other compatible subscription plugins with WeeConnectPay. Subscription payments are also manageable through the Clover web portal.

Does the vendor get their money directly no matter the used payment option?

Vendors receive their money the next morning. Banks are closed on weekends or holidays, so you will receive your money the next working day.

Does WeeConnectPay work for international transactions too?

At this time WeeConnectPay can only be used by a Canadian bank account holder. But their buyers can buy and pay all over the world.

Where are the plugin settings?

Under WooCommerce > Settings > Payments > WeeConnectPay. That page holds the connection to your Clover account, the setup wizard, and the Payments, Taxes, and Advanced sections (transaction mode, Google Pay, fraud protection, tax rate linking, debug mode).

Which transaction modes are available?

Three: Authorization + Capture (the usual choice; full and partial refunds, all tax forwarding modes), Authorization Only (place a hold now, capture later), and Orders + Payment (creates a Clover order with line items, for stores that print orders on Clover devices). The setup wizard shows each mode’s trade-offs, and you can change the mode later; changes apply to new orders only.

Can Clover show the taxes my store charges?

Yes. Link your WooCommerce tax rates to your Clover rates in the Taxes section of the plugin settings, then pick a tax forwarding mode. WooCommerce always calculates the taxes; the mode only controls how much detail appears in Clover reporting, and no mode can ever block a payment.

Does WeeConnectPay support Google Pay?

Yes, on the classic (non-Block) checkout, for supported browsers and devices. You can enable it in the setup wizard or the plugin settings.

Recensioner

1 augusti 2026
I will only say one thing: if you ever think you need a product that will keep developing in the future and you can really build something with, I will recommend this to you. If you ever run into any problem on your website that you cannot fix on your own, Ben’s team will help you figure it out. This is the best plugin I’ve ever used for my website and the best customer service ever.
3 maj 2026 1 svar
Rarely do I see a company who does such in-depth and dedicated work. Ben found a deeply embedded malware on our site that security scans missed and detailed it so that I was able to get a developer to find and remove it. He also reported the malware. He is always there to assist and check to make sure everything is working properly. Highly recommend this company! Thank you for all your great work! Your CBD Source.
15 november 2025
Ben has been incredibly helpful. He is one of the lead software developers—an awesome guy. Every time I had an issue, he was just a minute away with a response; no one replies that fast. If anyone needs a plugin from someone who is actively improving their product, I highly recommend checking out this plugin. It’s far better than the regular Clover plugin
8 juli 2024 1 svar
The installation and setup process was straightforward and user-friendly. The detailed documentation and intuitive interface made it easy to configure the settings according to my needs. Ben was great to work with as well.
20 juni 2024 1 svar
The assisted me with complicated command line and they found solutions when things got complicated.
Läs alla 10 betyg

Bidragsgivare och utvecklare

”WeeConnectPay – Clover Payment Gateway for WooCommerce” är programvara med öppen källkod. Följande personer har bidragit till detta tillägg.

Bidragande personer

Ändringslogg

4.13.1

  • Fixed: On some stores the product list could show the same product more than once, which also prevented the inventory link check from completing. Each product now appears once, with the same price and stock settings WooCommerce shows.
  • Improved: Compatibility fixes.

4.13.0

  • Improved: The transaction modes are renamed for what they actually do. ”Authorization + Capture” is now ”Charge at checkout”, ”Authorization Only” is now ”Hold and charge later”, and ”Orders + Payment” is now ”Order and charge”. Your current mode is unchanged and nothing needs to be reconfigured.
  • Improved: The stock sync modes and the tax reporting choices are renamed the same way. Stock sync now reads Off, Preview only, Follow Clover and Two-way; tax reporting now reads Off, Total only and Each rate by name.
  • Improved: The settings and setup wizard now describe every choice by what you get from it rather than how the payment is built, and both use the same names for the same setting.
  • Improved: A paused product link now says in one line why sales are not counted against a Clover item, and what to change to fix it.
  • Improved: A card that fails 3-D Secure verification now says the card could not be verified with the bank, instead of reporting it as an ordinary decline. The order note tells you nothing is wrong with your store.
  • Improved: Locked stock sync modes now explain, right at the mode you reached for, which plan they need and that your saved choice is kept.
  • Improved: The selected station in the settings status strip is now clearly marked, and the panel below it names the station it is describing.
  • Improved: Card details and connection credentials are no longer written anywhere they can be read from the browser or from an order’s stored data.
  • Improved: The card entry page now loads its payment scripts only from WeeConnectPay and Clover addresses, and keeps any security attributes your site adds to them.
  • Improved: The reCAPTCHA request no longer carries your WordPress version to Google, and the Privacy and Data Collection section now lists Google as a data recipient.
  • Improved: The connection environment can only be set to a secure address.
  • Improved: A 3-D Secure payment is now tied to the exact transaction it was started for, and an attempt that is interrupted and retried by the shopper cannot become a second charge.
  • Improved: A refund that could not finish in the time available is now refused before it is sent, rather than being interrupted partway.
  • Improved: Catalog jobs that run over large inventories are now processed in bounded batches so they complete reliably.
  • Improved: The Logs tab opens quickly even on very large debug logs, and the log download returns the most recent entries.
  • Improved: The plugin package no longer includes files that are only needed to build it.
  • Fixed: The sign-in card no longer shrinks and springs back while your pairing code is being generated.
  • Fixed: Parts of the plugin were still showing English text when WordPress was set to French. The French translation now covers the whole settings area, the setup wizard, Inventory Tools, and the notes added to your orders.
  • Fixed: If the payment provider cannot be reached during checkout, the shopper now sees a clear message and the order records what happened, instead of a site error.
  • Fixed: Shoppers no longer see technical text when a payment response cannot be read. They now see the standard message, in their language.
  • Fixed: 3-D Secure verification now records the outcome on the order in every case, including when the shopper abandons it or the result cannot be confirmed, and the reason from the bank is shown instead of a generic one.
  • Fixed: A refund that completes at Clover is now always recorded on the order, with a note, even when WooCommerce cannot create the refund record itself.
  • Fixed: Releasing an uncaptured authorization is now recorded as a release and the order is set to Cancelled. It no longer creates a refund line, marks the order Refunded, adds to Analytics refunds, or emails the customer about a refund.
  • Fixed: A refund can no longer exceed the amount remaining on a transaction, and two refunds for the same transaction can no longer run at the same time.
  • Fixed: The order refund path no longer reports an error after the money has already moved, and every refund outcome now writes an order note.
  • Fixed: A capture can no longer exceed the amount originally authorized, the order note shows the amount actually captured, and a capture that Clover declines can be retried right away instead of waiting.
  • Fixed: On orders paid with more than one payment method, the card transaction is now recorded for the amount the card actually took.
  • Fixed: When the result of a gift card or other custom payment method cannot be confirmed, it is now recorded as unconfirmed rather than failed, and the order says so.
  • Fixed: Whether a transaction can be refunded or voided is now decided by the recorded transaction type.
  • Fixed: If creating the Clover order does not complete, the order now notes that a duplicate may exist in your Clover dashboard.
  • Fixed: Debug logs are now kept only in the plugin’s own protected log folder. Clear logs works with debug mode turned off and removes every log file, and uninstalling the plugin leaves none behind.
  • Fixed: Information shown on the order screen is now displayed exactly as it was recorded.
  • Fixed: The settings link on the Plugins page now works in every case.

4.12.0

  • New: Inventory Tools page for bulk catalog transfer. Export selected WooCommerce products to Clover or import Clover items into WooCommerce, with a guided picker, a review step, and live progress. Runs can be resumed if the page is closed, and imported products can be created as drafts or published right away.
  • New: Tax-aware transfers. Exports carry each product’s tax status to Clover, and imports match Clover taxes to your linked WooCommerce rates. An item whose taxes cannot be matched is skipped rather than created with the wrong taxes, and the run results name the exact Clover taxes involved.
  • New: Rate coverage panel on the Taxes tab with a two-sided comparison of your WooCommerce and Clover tax rates, so you can see at a glance which rates exist on only one side.
  • New: Create a missing WooCommerce tax rate from its Clover counterpart, or a combined tax class for multi-rate items, straight from the Rate coverage panel. Newly created rates are linked to their Clover rates automatically.
  • New: Before a transfer starts, a summary warns about products that will be skipped or need attention, with badges in the picker explaining why.
  • Improved: When stock pull is paused for a product, the notice now states the exact reason: the product’s taxes and its linked Clover item’s taxes are not the same.
  • Improved: The product catalog panel now shows each product’s tax status and warns when a linked product is in the Trash.
  • Improved: The Taxes tab now says clearly when your Clover tax rates have not been synced yet, instead of showing an empty comparison.
  • Fixed: The deleted-product links list is now scrollable and searchable.
  • Fixed: Products with only zero-rate shipping tax now export with the correct tax status.

4.10.0

  • New: Inventory sync. Link your WooCommerce products to your Clover inventory items in the settings panel, then choose a sync mode: Off, Detect only, Pull stock, or Two-way. Pull stock keeps WooCommerce stock quantities up to date from Clover; Two-way also sends your WooCommerce stock edits to Clover. Off by default, and no mode can ever block a payment.
  • New: Orders + Payment transactions now send each order line’s tax detail and real line-item quantities to Clover, so the Clover order matches what WooCommerce calculated, line for line.
  • New: Partial refunds on Orders + Payment transactions can target individual units, and refunds keep working even after a product is renamed in WooCommerce.
  • New: Debug log retention setting in the Advanced section. Choose how long debug logs are kept; older entries are purged automatically.
  • New: Optional error diagnostics for support, disabled by default. Nothing is ever sent unless you ask WeeConnectPay support for help and an agent opens a temporary diagnostic window for your store. See the Privacy and Data Collection section for details.
  • Improved: The settings panel was redesigned to fit in a single view.
  • Improved: A declined payment now keeps the shopper on the checkout page with a clear message instead of a technical error.
  • Improved: Clearer wording on the banner shown when your store’s Clover connection needs attention.

4.5.1

  • Fixed: The tax forwarding mode section in the settings panel could not load or save the mode because two internal classes were not registered. Card payments were unaffected and kept using the saved mode.

4.5.0

  • New: Tax forwarding mode in the settings panel. Choose what each card payment sends to Clover for tax reporting: nothing, the amount only, automatic attribution (the default), linked rates only, or full attribution, which runs eligible payments through a Clover order so every linked rate appears as its own named line, even multi-rate carts like TPS + TVQ. WooCommerce always calculates the taxes and no mode can ever block a payment.
  • New: Interactive preview under the mode picker showing how a sample WooCommerce order lands in Clover reporting for each mode, cart shape, and transaction mode.
  • Improved: The transaction mode cards in the setup wizard and the settings panel now show the same capability summary for each mode, covering refunds, taxes, and Clover order printing, with each mode’s limits stated plainly. Orders + Payment refunds are line-item returns at the full item cost, with no partial item refunds, and that path is not covered by tax forwarding modes yet.
  • Changed: Authorization + Capture is now the recommended and default transaction mode when no mode has been chosen. Existing stores keep their saved mode.

4.4.0

  • New: Tax Rates section in the settings panel. Link your WooCommerce tax rates to your Clover tax rates so Clover reporting attributes tax to the right rate. Only rates with exactly the same percentage can be linked, and an auto-link action handles exact matches for you.
  • Charges now send a detailed tax breakdown to WeeConnectPay. WooCommerce still calculates all taxes; charged amounts are unchanged.
  • Fixed a rounding issue where the tax amount sent with a charge could carry fractional cents.
  • Editing, adding, or deleting a WooCommerce tax rate now instantly rechecks its Clover link. A mismatch shows up in the settings panel, as an order note on affected charges, and as a dismissible admin notice. Payments are never blocked by tax checks.

4.3.9

  • Fixed ”Pay for order” links failing with ”We were unable to verify your checkout and no payment was processed.” The card was never tokenized on the order-pay page, so the payment was rejected before it started. Paying for an existing order now works the same as a normal checkout.

4.3.8

  • Fixed the checkout spinner hanging forever when the configured Google reCAPTCHA site key is invalid. The payment now proceeds and the order notes call out the reCAPTCHA error so the key can be corrected.
  • Added a 10-second safety timeout on reCAPTCHA token generation so checkout can never get stuck waiting on Google.
  • Clearer order notes and logs when a payment submission arrives without checkout data.

4.3.7

  • Fixed intermittent ”Missing reCAPTCHA token” checkout failures. When Google’s reCAPTCHA script cannot load in the customer’s browser (ad blockers, privacy tools, caching plugins), the payment now goes through and a diagnostic note is added to the order, matching the existing Block-based checkout behavior.
  • The Google reCAPTCHA script is now marked so caching and optimization plugins (LiteSpeed Cache, WP Rocket, Cloudflare) do not delay or rewrite it.
  • Better order notes and logs when a reCAPTCHA token is missing, to help pinpoint whether checkout scripts loaded at all.

4.3.6

  • Fixed an issue where checkout could request more than one payment token per attempt, which sometimes caused ”invalid token” errors. Each checkout attempt now creates a single token.

4.3.4

  • Debug logs now persist across plugin updates. Previously, updating the plugin reset your debug logs. They are now stored safely and kept between updates.

4.3.3

  • Fixed Google reCAPTCHA at checkout on Classic and Block-based checkout.
  • Improved checkout error handling so the form recovers cleanly after a failed payment.

4.3.2

  • The redesigned card form now renders correctly on Block-based checkout. The card-number, expiry, CVV, and postal-code fields, the inline per-field validation, and the secured-payment footer now match the Classic checkout introduced in 4.3.0, instead of showing as unstyled fields.

4.3.1

  • 3-D Secure now appears as ”Coming soon” in the settings and cannot be enabled yet, while we finish the supporting checks on your Clover account. It was introduced in 4.2.

4.3.0

  • Redesigned card form on both Classic and Block-based WooCommerce checkout: cleaner layout, clearer per-field validation as the customer types, and a smoother Google Pay handoff that stays in sync with the cart total.
  • Card brand, expiry, CVV, and postal-code fields now surface inline validation feedback the moment the customer leaves each field, so mistakes are caught before Place Order.
  • Google Pay (when enabled on the store) now confirms readiness with a clear ”Place Order to confirm” prompt, and customers can switch back to entering card details without losing their cart.
  • WeeConnectPay now detects when your store’s Clover connection has stopped working and shows a clear notice that links back to the connection page, instead of the settings continuing to look connected. The notice clears on its own once you reconnect.
  • Switching environments is now explicit: a confirmation step explains that switching disconnects your current connection, and a standing warning appears whenever you are on a non-production (test) environment that does not process real payments.
  • The WeeConnectPay Charges box now appears on the order screen for stores still using legacy (non-HPOS) order storage, so those merchants can view and refund charges from the order page too.
  • You can now issue partial refunds, including several successive partial refunds on the same charge, directly from WooCommerce’s native Refund button on card (charge-based) payments, up to the remaining refundable amount.

4.2.0

  • Added the foundation for 3-D Secure cardholder verification at checkout on both Classic and Block-based checkout, including subscription purchases that save the card for renewals. It is held back as ”Coming soon” as of 4.3.1.
  • Failed payments now show full Clover error context in WooCommerce order notes (error code, decline reason, Clover error message, card brand, last 4), matching the level of detail on successful charges.
  • Successful charges now explain what was checked (authorization outcome, AVS, CVV) instead of a vague ”no authentication data returned”.
  • Successful charge order notes now carry amount, currency, card type, last 4, auth code, and reference number.

4.1.2

  • Polished the device-flow login: clearer copy, loading state, and a more prominent connect button
  • Improved settings accessibility: clickable toggle rows, proper label/input wiring, and visible keyboard focus

4.1.1

  • Fix: Token refresh lock no longer shared across environments

4.1.0

  • New: Manual environment switcher — connect independently to Sandbox, Staging, and Production
  • Credentials are now stored per-environment with automatic migration from previous versions

4.0.0

  • New: Connect your Clover account with a short authorization code — no more manual credentials
  • New: Rebuilt admin dashboard with guided setup wizard
  • New: Three transaction modes — Order Payment, Auth & Capture, and Pre-Authorization
  • Redesigned charges metabox with multi-refund support and confirmation flow
  • Added French Canadian translations for the admin dashboard and charges metabox

3.17.2

  • Rebuilt the admin dashboard with React, Vite, and Tailwind — includes a new guided setup wizard
  • Added three transaction modes: Order Payment (Clover order + printing), Auth & Capture (immediate), and Pre-Authorization (capture later)
  • Redesigned the order charges metabox with card-based layout and 3-step confirmation for refunds and voids
  • Added refund and void support for charge-based transactions
  • Blocked partial refunds for order-based charges to prevent inconsistencies
  • Added French Canadian translations for the admin dashboard and charges metabox
  • Improved payment processing type safety and error handling
  • Various UX fixes: settings save race condition, debug log viewer, browser navigation, inline error messages

3.17.0

  • Added support for pre-authorized payments with later capture
  • Added partial refund support for pre-authorized charges (Only applies to pre-authorized transactions for now. Documentation will be published soon. Please contact support if you have any questions in the meantime)
  • Added a ”Capture Preauthorized Charge” button in the WooCommerce admin panel with confirmation prompts, progress indicators, and AJAX-based capture handling
  • Updated order payment details to display card type on receipts and order pages
  • Added custom order update messages for both HPOS and legacy admin workflows

3.16.2

  • Fixed Google Pay not loading anymore

3.16.1

  • Updated the translation warning fix to prevent other plugins from interfering with the plugin load order

3.16.0

  • Added a toggle for Google Pay (Classic Checkout). As of writing this, the Clover SDK does not generate the Google Pay button in production. As such, the default for this setting is ”disabled” even for existing integrations

3.15.4

  • Fixed translation warnings polluting PHP’s error log

3.15.3

  • Added some missing translations
  • Updated pre-authentication flows to log unhandled errors as critical, ensuring that logs are available at different levels
  • Added gateway icon

3.15.2

  • Fixed a fatal error while attempting to display an error message during plugin activation

3.15.1

  • Added Clover order printing functionality – orders are now automatically sent to your default Clover printer after successful payment
  • Added merchant-facing order notes when print requests are sent to provide visibility into printing status
  • Enhanced logging for Clover print request operations
  • Added settings to control printing for regular and recurring/subscription orders

3.14.4

  • Enhanced payment gateway compatibility with improved event handling for multi-gateway environments
  • Optimized checkout flow to ensure seamless operation alongside other payment methods
  • Improved payment method detection and processing logic for better merchant experience

3.14.3

  • Improved WooCommerce Subscription logic

3.14.2

  • Enhanced logging security with improved file protection and unpredictable naming
  • Added critical log level for important system messages
  • Improved log management with automatic cleanup and audit tracking
  • Enhanced environment validation for better deployment security
  • Added comprehensive error handling and stability improvements

3.14.1

  • Added WooCommerce Subscription support

3.13.12

  • Enhanced WeeConnectPay payment charges display with a dedicated meta box for improved visibility and organization of transaction details

3.13.11

  • Updated gateway name from ”Clover Integration” to ”Clover via WeeConnectPay” for clarity
  • Updated logger to use a dedicated log file in the plugin’s logs directory
  • Improved logging reliability by not depending on WordPress debug settings
  • Added fallback to WordPress error_log for critical errors

3.13.10

  • Updated failed payment order notes to show more information
  • Fixed a bug that could happen preventing failed order notes from being displayed under certain circumstances

3.13.6

  • Fixed a generic plugin error that could affect plugin activation or checkout

3.13.5

  • Fixed Google Pay with Gift Cards
  • Added warning message to inform merchants that when an order contains gift cards or mixed payment methods (gift cards + credit cards), they must process full refunds for each transaction separately through the WeeConnectPay Charges section.

3.13.4

  • Enhanced security measures for payment processing
  • Improved transaction reliability and error handling
  • Optimized checkout performance for high-traffic stores

3.13.1

  • Various bug fixes and optimizations to support multi-charge orders with custom tenders
  • Enhanced support for gift card and loyalty card payment processing
  • Improved handling of multiple payment methods in a single order
  • Optimized order processing workflow for custom tender transactions

3.13.0

  • Added a debug option
  • Updated the frequency and quality of log messages
  • Added a debug log viewer in the plugin settings page

3.12.5

  • Added additional information for transactions being displayed in the order edit page — This information changes nothing for your PCI-DSS compliance and allows for custom and/or automated fraud prevention for merchants
  • Added a way to refund the full amount of a transaction
  • Added additional functions for developers through the gift card helper class to support custom payment and refund flows

3.12.1

  • Added gift card partial payment support

3.11.5

  • Updated the state tracking for the front-end to prevent other plugins

3.11.4

  • Updated the Clover SDK Tokenization logic to handle less than ideal environments

3.11.3

  • Updated Clover SDK initialisation for WooCommerce Blocks – This should fix iframe placeholder translation issues

3.11.2

  • Updated plugin to show more information about the mismatched amounts when checkout amounts would not match — This is mostly to help us help the merchants figure out which plugin is conflicting and to help us add support for these plugins faster

3.11.1

  • Added the following requirements: WordPress database must be properly set and not empty
  • Updated plugin to show when an authentication was successful instead of simply showing the settings as a landing page

3.11.0

  • Updated plugin to log the merchant out if the WeeConnectPay API key is invalidated or expired — We now email your Clover Employee (Also to the Clover Merchant Owner If they are not the same) to notify you and give you a link to reconnect

3.10.7

  • Added clickable Clover receipt links to WooCommerce order notes
  • Updated the permalinks dependency notice to include localized clickable instruction to resolve the issue
  • Updated plugin name to include WooCommerce in the Plugin Directory
  • Updated requests timeout to help with the refresh token implementation

3.10.0

  • Added support for order fees

3.9.0

  • Added card brand as a column in the WooCommerce Orders listing page. This feature is available in both Classic and Blocks checkout. It is also available for both the HPOS and legacy data storage modes.
  • Added card brand in the order notes as well

3.8.0

  • Added High Performance Order Storage (HPOS) compatibility

3.7.12

  • Updated plugin to declare compatibility with WooCommerce Checkout blocks, as well as tested up to version and minimum supported versions detectable by WooCommerce
  • Updated compatibility values detected by WordPress
  • Additional changes not included in the plugin, related to the pipeline / build process

3.7.9

  • Updated pipeline to include folders needed for the WordPress SVN

3.7.5

  • Fixed a bug where the edit page for block checkout showed that the gateway did not support block-based checkout

3.7.3

  • Updated certain pre-authentication values to be trimmed from extra spaces in order for them to pass the validation in the event extra spaces are added by another plugin or theme

3.7.0

  • Added WooCommerce Blocks Support
  • Fixed an issue that prevented unmet dependencies from displaying upon activation and instead displayed a fatal error
  • Added workaround for the ’Pro’ theme which was preventing the Clover SDK from detecting its environment
  • Updated the temporary workaround for refunds to also include shipping fees. This is still related to the bug introduced by an undocumented Clover API breaking change that could affect refunds
  • Updated the logic for validation before payment processing for WooCommerce Blocks Checkout (This change does not apply to Classic Checkout)

3.6.4

  • Added a temporary workaround (Exact refund validation) to prevent a bug introduced by an undocumented Clover API breaking change that could affect refunds.

3.6.0

  • Feature: Google reCAPTCHA is now supported as an additional security measure for merchants
  • Added other security related options to detect automated transactions

3.5.2

  • The plugin should now be fully translated in French Canadian. (Added fr_CA translation files)

3.5.1

  • Added more information in the order notes (with improved formatting!) from the Clover response when the payment fails.
  • Updated some strings to better fit the format of different languages for translators

3.5.0

  • Feature: WeeConnectPay will now detect if the Clover API key has been invalidated and require re-authenticating when it happens in order to re-generate a new Clover API key. This scenario only happens when any API calls to Clover would fail otherwise, due to the key not being valid anymore.
  • Updated fraud analysis new feature notice to include a link to the integration settings and added a title in the settings.

3.4.0

  • Updated WeeConnectPay to comply with a new security requirement by Clover; Sending the IP address of the customer to Clover with the payment request. This change is required by Clover before Sept 1st, 2023, to continue processing payments.

3.3.1

  • Removed debug logging before releasing new feature

3.3.0

  • Feature: Introducing order notes as a fraud risk assessment tool for WeeConnectPay. Evaluates mismatches in shipping/billing or billing/credit card postal codes

3.2.6

  • Added SiteGround Optimizer support

3.2.5

  • Updated plugin to check for PHP intl module

3.2.4

  • Fixed php warning

3.2.3

  • Updated plugin to only display standard payment fields if Google Pay does not load properly
  • Fixed payment fields not showing when Google Pay did not load properly

3.2.2

  • Updated plugin activation to validate prerequisites before attempting anything else
  • Updated plugin activation to display validation errors for pre-authentication in the admin panel

3.2.1

  • Updated plugin admin options to gracefully display an error if something goes wrong with the requests. (IE: Expired or invalid SSL certificate)

3.2.0

  • Feature: WeeConnectPay will now suggest autocompleting the credit card information if the browser has access to it

3.1.2

  • Updated settings and authentication verification failure to reset database values to what a fresh installation would be. This should allow for seamless installation through FTP

3.1.0

  • Improved the authentication verification to detect database exports/imports that create issue due to partially invalid data
  • Feature: WeeConnectPay will now log you out of the integration and clean the database entries if the authentication data is not valid. This allows the integration to fetch valid data to authenticate properly afterwards.

3.0.7

  • Removed (Secured by clover) from the gateway label to better fit our updated style
  • Fix CVV placeholder being too high when the gateway is not open by default (French-specific bug)
  • Improved CSS compatibility with FF, IE, Opera, Safari

3.0.6

  • Added secured by footer on the gateway
  • Added credit card logos on the gateway header
  • Updated CSS to be sturdier to themes style collisions

3.0.5

  • Added support for a wide range of WooCommerce order item types

3.0.4

  • Added an error notice on checkout when totals do not match due to unsupported discount or gift card plugins

3.0.3

  • Updated CSS rules for Google Pay button
  • Added fallback for Google Pay button required values

3.0.0

  • Improved payment processing flow

2.5.7

  • Update singleton design to prevent PHP8 from throwing warnings

2.5.6

  • Update plugin display name
  • Improve order notes for some more edge cases

2.5.5

  • Improved logic and order notes to gracefully handle edge cases in the unlikely event of a Clover service interruption

2.5.5

  • Updated CSS rules for Google Pay button
  • Added fallback for Google Pay button required values

2.5.4

  • Fix cache-busting for seamless updates when scripts or styles are modified as part of an update

2.5.3

  • Add specific CSS to try and prevent themes from breaking the card tokenization methods separator

2.5.2

  • Update tested-up-to to 6.0.2

2.5.1

  • Add min-height and width for Google Pay with higher specificity to prevent themes breaking the button layout
  • Add separator for the 2 card tokenization methods – Clover iframe OR Google Pay

2.5.0

  • Feature: Add Google Pay card tokenization support. This allows customer to use Google Wallet to provide a tokenized card for the payment with Clover instead of typing the card in your website.
  • Fix: No longer prevents users from clicking elements on the page where the error fields would normally appear.

2.4.9

  • Fix: Plugin no longer attempts to charge when the order total amount is 0 or less

2.4.2

  • Add minimum required WordPress and PHP versions to plugin header

2.4.1

  • Fix: A Clover customer creation bug when some fields were null. All edge cases should now be covered and allow a customer to be created properly regardless of available data given by WooCommerce.

2.4.0

  • Feature: Add customer creation and link customer data to orders (Data available in the merchant Clover dashboard)

2.3.0

  • Feature: Add support for multiple employees authenticating with the plugin
  • Change refund payload …