If you installed the official "Clover Payments for WooCommerce" plugin and it's misbehaving — failed checkouts, the gateway not appearing, no subscription support, or silence from support — you're not imagining it. The official plugin has a long tail of unresolved complaints, and most of the failures fall into a handful of fixable categories. This guide walks through each one, and is honest about when the plugin simply can't do what you need.
First, a 60-second triage
- Open a WooCommerce order that failed and read the order notes — the gateway usually logs the actual decline code or error there.
- Enable WooCommerce → Status → Logs and reproduce the failure once. The Clover log entry tells you whether the problem is auth (OAuth/token), config (sandbox/region), or a bank decline.
- Check whether ANY card succeeds. If 100% fail, it's almost always configuration (below). If only some fail, it's bank declines — see our decline-codes guide.
The Clover option doesn't show at checkout
If "Clover" isn't listed as a payment method at checkout, the gateway is installed but not actually enabled or eligible. The usual causes: the gateway is toggled off under WooCommerce → Settings → Payments; OAuth was never completed so the plugin has no token; your store currency doesn't match the Clover merchant account currency; or a Blocks-based checkout is rendering before the gateway registers. We cover this end-to-end in our dedicated guide on the Clover gateway not showing at checkout.
Every card is declining
A 100% failure rate is rarely the customers — it's configuration. The four that account for most cases:
- Sandbox credentials live in production. Every real card fails. Confirm environment = Production and that the PAKMS key, App ID, and App Secret are all the production values.
- The Clover Developer app isn't approved for payments. New apps sit in pending approval; until Clover approves payment processing, charges fail with a generic gateway error.
- Region mismatch. A US merchant account can't process a charge initiated against the EU endpoint (or vice versa). Match the environment to the merchant's actual region.
- AVS set to reject. If the gateway rejects on any address-verification mismatch, ordinary customer typos kill good cards. Relax AVS to ZIP-only or off unless you're high-fraud.
Our full diagnostic for this is here: why Clover is declining every WooCommerce order.
It worked, then stopped (token/OAuth errors)
If payments worked for weeks and then broke, the OAuth token likely expired or was revoked, or someone re-saved credentials and broke the PAKMS key. Reconnect through the plugin's OAuth flow and re-paste the production PAKMS key. Our Clover OAuth error guide covers the eight most common messages and the exact fix for each.
No subscriptions, no saved cards, no tipping
This one isn't a bug — it's a ceiling. The official plugin is a basic, payment-only gateway. It does not support WooCommerce Subscriptions (recurring billing), and saved-card and tipping support is limited or absent. If you sell memberships, meal plans, or any recurring product, no amount of troubleshooting will add that capability; you need a gateway that supports tokenised recurring billing.
If you've outgrown the official plugin
Two honest paths, depending on what you actually need:
- You only need payments. A maintained payment-only gateway (e.g. Kestrel) processes Clover cards on WooCommerce with subscriptions and saved cards, for a one-time license. It does payments well — and nothing else.
- You need payments AND your catalog/orders/inventory in sync. The official plugin only moves money; it doesn't keep Clover and WooCommerce in step. CloverWoo bundles the Clover payment gateway (with saved cards, tipping, and WooCommerce Subscriptions) plus two-way sync of products, inventory, orders and customers, plus auto-print to your Clover POS — one plugin, $60/mo flat, with a 7-day refund.
Switching is low-risk: install alongside the official plugin, complete OAuth, enable the new gateway under Payments, run a test transaction, then disable the old one. Your existing WooCommerce orders and products are untouched.
Frequently asked questions
Why is the official Clover Payments for WooCommerce plugin rated so low?
The most common complaints are failed or inconsistent checkouts, no support for WooCommerce Subscriptions, and slow or absent vendor support. Many of the checkout failures are fixable configuration issues (sandbox-in-production, unapproved app, AVS, region), but the missing-features and support complaints are structural — the plugin is a basic payment-only gateway.
Does the official Clover plugin support recurring payments / WooCommerce Subscriptions?
No. It's a basic gateway with no tokenised recurring billing. If you sell subscriptions, memberships, or meal plans, you need a gateway that supports saved cards and recurring charges — the official plugin can't do it regardless of configuration.
Will switching plugins lose my orders or products?
No. Payment gateways don't own your catalog or order history — those live in WooCommerce. You can install an alternative alongside the official plugin, test it, and disable the old one without touching existing data.
How do I tell a configuration problem from a bank decline?
Check the failure rate. If 100% of cards fail, it's almost always configuration (sandbox credentials, unapproved app, region, AVS). If only some fail, those are bank declines tied to specific decline codes — see our Clover decline codes guide.