Failed payments

Good Afternoon @willd2568,

Your private key is like a password. Without it you cannot access sensitive information. So with a reinstall your private key will always have to be re-entered to prevent unauthorized access and for your security. If you do not have direct access to your companies credentials you should reach out to those with admin access. Once you have access, Please refer to the installation instructions on our plugin page where we provide steps and screenshots corresponding to each step to configure your plugin.

If you have any further issues after following these steps please reach back out and we will be happy to help you troubleshoot.

Your plugin update broke my site. The new version no longer accepts any API keys. Nobody at Clover tech support on the telephone knows anything about this plugin despite your use of their name and logo. I suspect fraud.

Hi @willd2568,

Upon reviewing your multiple replies across the Support Threads, it seems you have been encountering multiple issues. To clarify and help us better understand the problem, can you specifically outline what your situation is currently?

You previously mentioned you don’t have access to the Clover account to obtain the API keys. Were you able gain access to the account?

You mentioned not being able to enter the API keys. Is this still an Issue?

You mentioned our plugin “breaking” your site. Could provide us with more context on this?

– Clover eCommerce

Get rid of 2.0.0 immediately. It’s got a bug. Don’t upload updates you haven’t tested. WTF were you thinking? Ever since 2.0.0 was uploaded to my site I have received “Transaction could not be processed: Clover Token does not exist.” entries in the logs. I replaced 2.0.0 with 1.0.12 and it fixed the issue. Your mistake of uploading an untested plugin update has cost me nearly $200 in lost revenue from customers. Your incompetence is not appreciated. This is a mission critical plugin that needs to be thoroughly tested before launching it.

• This reply was modified 3 months, 1 week ago by willd2568.

@willd2568 Your reply has been removed. It is not acceptable to abuse people here. No one is obligated to reply to you, especially when you’re trolling. If you continue, your account will be banned.

• This reply was modified 3 months ago by Steven Stern (sterndata).

Rolling back to 1.0.12 fixed my issue as well. All orders since 12/18 failed, but after going back to the previous version, my test order went through successfully. Something about 2.0.0 definitely doesn’t work well with the latest versions of either Elementor and/or WooCommerce.

Hi @solutioinc,

We’re sorry to hear you were having issues with our plugin. We wanted to let you know, we heard your feedback, and added back support for WooCommerce’s Classic (shortcode) Checkout in our latest version (2.1.0). This update should resolve any issues you were having with Elementor.

Let us know if you have any other questions.

– Clover eCommerce

Woocommerce Version 2.1 support for classic  and block checkout pages  
We are excited to announce the release of version 2.1 of the Clover Plugin for WooCommerce, which resolves the recent issue related to the classic checkout that some merchants have encountered.

What’s New?

• The new version includes support for the classic checkout option.
• Bock-based checkout page design will function as it typically does.
• Merchants and developers can now toggle between classic and block-based designs based on their e-commerce store needs.

Action Required:
The plugin will automatically install if Auto-updates are enabled. Otherwise, you can install the latest version, 2.1, by going to your WordPress dashboard and then clicking on Plugins -> Install Plugin -> Update Clover Payments for WooCommerce.

Thank you for your continued support. We look forward to hearing from you.