Rating: 1 star

All Credit Card payments are failing as of Sept 6th. The logs in WooCommerce state that there is no Name filled out. Well….you should add that to the form! The name field is now missing, if it was ever there to begin with. So now, we have to use PayPal for our customers to be able to use a credit card. The issue with this is that those payments don’t flow into Clover, thus our reporting is not correct. Your plugin hasn’t had an update in over 6 months….that’s absolutely unacceptable. I’m honestly at my wits end with Clover and am about to tell my customer to get a new system.

Rating: 1 star

Does not work

Transaction could not be processed, please retry

• This topic was modified 4 months ago by andriy063.

Rating: 1 star

Plugin is active , with keys and, still showing, no payment option added, how to fix?

Rating: 3 stars

This review is for the version info listed below.
WordPress 6.5.3
WooCommerce 8.9.1
Clover Payments for WooCommerce 1.0.12

The plugin does NOT work with the current blocks implementation of WooCommerce. The checkout page will say “no payment method available”. You’ll need to replace the checkout page with the WooCommerce checkout shortcode.

Product information does not get sent to Clover, just the sale value. That’s mostly useless.

• This topic was modified 6 months ago by heroagency.

Rating: 1 star

This plugin just doesn’t cut it out of the box.

• Custom CSS styling of the fields is confusing
• Does not break out sales taxes or fees in the Clover dashboard – this should be a no-brainer
• Does not support Tips, Additional Charges, Service Charges etc…honestly it doesn’t even have any configuration options outside of configuring the environment(sandbox/production) it uses and whether the option is auth or auth + capture.
• Codebase is inconsistent; accesses woocommerce class properties directly (causing errors) in several places, while using the proper getters elsewhere.
• Running newer PHP versions causes massive error log writes since the plugin creates class properties within constructors without declaring them first.
• Weird behaviors while filling out the credit card form & poor user experience
• Requires jQuery but doesn’t register the dependency
• Plugin & Clover JS SDK (remote script) runs everywhere, on every page, doesn’t limit payment scripts to cart/checkout pages.
• Zero support from Clover. It’s quite obvious they don’t care much about this plugin beyond making sure it will Activate & Deactivate.

If you’re ok with a haphazard plugin then use it; otherwise I recommend finding an alternative or rolling a custom plugin; tbh just change credit card processing companies/gateways and save yourself the trouble.

• This topic was modified 7 months, 3 weeks ago by Circuitbomb.
• This topic was modified 7 months, 3 weeks ago by Circuitbomb.

Rating: 1 star

This is the first time I’ve ever left a bad review. This plugin should be removed from the repository. The support doesn’t exist, it does not work with CAPTCHA, and it’s a card attack magnet.

Rating: 1 star

The WooCommerce CLOVER Plugin has the following issues:

#1 issue: the native WooCommerce plugin doesn’t work at all, and debugging provides no plausible?causes or potentials for a “fix”.

#2 Issue: Visually and functionally?poorly executed and needs updating badly:

—“Card number invalid” shows before you finish typing = negative customer experience and confusion for customers
—Unprofessionally aligned text boxes
—Undersized card number in text field = lower level of confidence
—No credit card logos = lower level of customer confidence
—Text fields don’t look aligned nicely.
—No option in the plugin to remove the “ZIP” field which is a barrier sometimes for customers who want to checkout quicker.

<u>If there was ANY way you could get this fixed</u> it would make a huge effect on your usage of this app on WooCommerce, I would even help champion your adoption into the WooCommerce adoption?of Clover. ?I would even be willing?to pay, or find a developer to take your code and fix / improve it because I believe you have a chance to do even better than Stripe but currently it looks like I am going back to Windows 95!

You could set the benchmark for a high quality trust-evoking input field and sequence with the WooCommerce app if some refinement could be made and I HOPE you can find a few funds for your development team to take this seriously.

Also, it looks like many other support inquiries seem to be ignored by developers which is a sign that nobody cares about this plugin. I sure wish a new team member could get on board with the maintain and updates of this plugin!

Rating: 5 stars

Crazy how a big company can’t even make a gateway plugin. “No payment methods available even once configured properly (I do this for a living) and activated.

Rating: 1 star

I set it up according to the instructions, but it doesn’t actually show up as a payment method. Instructions are not current.

Rating: 1 star

We are a Clover Merchant, formerly with Payeezy. We have been trying for almost a week now to get the fraud filters to work correctly. I have a case # with Clover, because the settings in the dashboard do not work correctly. I am not sure if it is the plug-in or Clover dashboard. Any help would be appreciated.

It accepts payments, the problem is it will accept a payment with a fake address.

• This topic was modified 1 year, 2 months ago by gotchall.

Rating: 1 star

Clover customer support is the WORST. Almost 2 hours on hold, passed from one unhelpful person to the next. Make Customer Support Great Again…

Second attempt. Hot Garbage support. Their server will not respond. Do not use.

• This topic was modified 9 months, 2 weeks ago by aaronsingler.

Rating: 4 stars

Had a client that needed to connect to Clover – this plugin did that without a separate plugin on clover’s side that I had to install. The styling in the checkout isn’t great but with a little css this works well.