You've installed a Clover gateway, but at checkout there's no Clover option — customers can't pay, or they're forced onto another method. The gateway is almost never "broken"; it's ineligible to render for one of a few specific reasons. Here's the checklist, ordered from most to least common.
1. The gateway isn't actually enabled
Go to WooCommerce → Settings → Payments. Confirm the Clover method toggle is ON (not just installed). A freshly installed gateway is off by default. If it's on here but still missing at checkout, continue down the list.
2. OAuth was never completed (no token)
A Clover gateway can't render until it has a valid merchant token. If you pasted credentials but never clicked through the "Connect to Clover" OAuth flow — or the token later expired — the gateway silently hides itself rather than showing a broken option. Reconnect via the plugin's Connect button and confirm it reports a connected status.
3. Store currency doesn't match the merchant account
Most Clover gateways only render when the WooCommerce store currency matches the currency the Clover merchant account is provisioned for. A USD merchant account on a store set to EUR (or GBP) will hide the gateway entirely. Check WooCommerce → Settings → General → Currency against your Clover account's currency.
4. Block checkout vs classic checkout
WooCommerce's newer Blocks (Gutenberg) checkout only displays gateways that ship a Blocks integration. An older gateway built for the classic shortcode checkout won't appear on a Blocks checkout page at all. Two fixes: either switch that page back to the classic [woocommerce_checkout] shortcut, or use a gateway that declares Blocks (and HPOS) compatibility. Check WooCommerce → Status → the page is using the block, then test with the classic shortcode to confirm this is the cause.
5. Conditional / country / amount restrictions
If you (or another plugin) set the gateway to only appear above a minimum amount, for certain countries, or for specific shipping methods, it will correctly hide outside those conditions. Review any conditional-gateway rules and the gateway's own "Enable for shipping methods / countries" settings.
6. App not approved / sandbox environment
If the Clover Developer app is still pending payment approval, or the plugin is pointed at the Sandbox environment, some gateways refuse to render against live traffic. Confirm the app is approved for production and the environment is set to Production.
7. Cache / JS error swallowing the gateway
Aggressive page caching or a JavaScript error from another plugin can prevent the checkout from finishing its render, dropping the gateway. Clear your site + CDN cache, then load checkout in an incognito window with the browser console open and watch for red JS errors. Temporarily switching to a default theme and disabling other checkout plugins isolates a conflict fast.
How CloverWoo avoids this
Most "gateway missing" reports trace back to Blocks incompatibility, an incomplete OAuth connection, or currency/region mismatch. CloverWoo declares both HPOS and Blocks checkout compatibility, walks you through OAuth with a clear connected/disconnected status, and supports NA, EU, and LATAM regions — so the gateway renders on modern checkouts without the guesswork. It's payments plus two-way sync and auto-print in one plugin, $60/mo flat.
Frequently asked questions
Why does Clover show in settings but not at checkout?
The gateway is installed and toggled on, but ineligible to render — most often because OAuth isn't completed (no token), the store currency doesn't match the Clover merchant account, or you're on a Blocks checkout with a gateway that only supports the classic checkout.
Does WooCommerce Blocks checkout break Clover gateways?
It can. The Blocks (Gutenberg) checkout only shows gateways that ship a Blocks integration. Older Clover gateways built for the classic shortcode checkout won't appear on a Blocks page. Use a gateway that declares Blocks compatibility, or switch the page to the classic [woocommerce_checkout] shortcode.
Could caching hide the payment method?
Yes. Full-page or CDN caching, or a JavaScript error from another plugin, can stop the checkout finishing its render and drop the gateway. Clear all caches and load checkout in incognito with the browser console open to spot JS errors.
Clover only disappears for some customers — why?
That's usually a conditional rule: a minimum order amount, a country/region restriction, or a per-shipping-method setting. The gateway is correctly hiding outside those conditions. Review your conditional-gateway and 'enable for' settings.