Disconnected means one thing: the credentials that let your store talk to Clover through WeeConnectPay are no longer usable, so payments stop until you sign in with Clover again. Everything else stays where it is. Your orders, your transaction history, and your plugin settings are all untouched, and reconnecting takes a few minutes.
How you find out
Three signals, and you may see any or all of them.
A red banner across your WordPress admin. It stays until the connection is restored, and it names the fix:
- "WeeConnectPay can no longer reach your Clover account, so payments are not being processed. Please go to WeeConnectPay settings and sign in with Clover again to reconnect."
- "Your WeeConnectPay credentials are no longer valid, so payments are not being processed. Go to WeeConnectPay settings and sign in with Clover again to issue new credentials."
- "Your WeeConnectPay integration is disconnected and is not processing payments. Please reconnect to continue accepting payments."
Each one ends with a Go to WeeConnectPay settings link that takes you straight to the right screen. The banner follows you onto every screen of your WordPress admin, so you cannot miss it. The one place it stays quiet is the WeeConnectPay settings screen itself, which already shows you the reconnect steps.
WeeConnectPay disappears from your checkout. This is deliberate. While the connection is down a card payment can only fail, so the payment method hides itself rather than letting customers try. It returns on its own once you reconnect.
An email. Subject "Action Required: Your Clover connection is disconnected" or "Action Required: Your WeeConnectPay integration is disconnected". It goes to the person whose Clover account connected the store and to the merchant owner, and it carries the reconnect steps for your platform. You receive at most one of these per 24 hours, so a message on several consecutive days means the store was still disconnected each day.
When the disconnection was deliberate, for example someone revoked the connection or uninstalled the WeeConnectPay app from Clover, the email arrives under the calmer subject "Your WeeConnectPay integration has been disconnected" instead.
The two messages, and why they differ
| The message says | What it means | What you do |
|---|---|---|
| WeeConnectPay can no longer reach your Clover account | The Clover credentials your store uses stopped working. | Sign in with Clover again from your store. |
| Your WeeConnectPay credentials are no longer valid | The credentials your store uses to reach WeeConnectPay were replaced or revoked. | Sign in with Clover again from your store, which issues new ones. |
The distinction tells our support team which side to look at. Your action is the same either way.
Reconnect on WooCommerce
Step 1. Open the plugin settings. In your WordPress admin, go to WooCommerce → Settings → Payments → WeeConnectPay. The banner's Go to WeeConnectPay settings link lands on the same screen.
Step 2. Get to the sign-in card. If the screen shows Connect your Clover account, you are already there; click Sign in with Clover.
If the screen shows WeeConnectPay Settings instead, open the Advanced tab, find Disconnect this store under Connection, and click Logout, keep settings. The plugin asks "Disconnect from Clover and keep settings?" and answers itself: "Your payment preferences (printing, fraud protection, etc.) will be remembered when you reconnect." Confirm with Yes, disconnect. The sign-in card then appears, and you click Sign in with Clover.
Step 3. Approve the connection. The plugin shows a connection code and an Open WeeConnectPay button. Open it, sign in with the Clover account that owns the business, enter the code on the Connect an Integration screen, click Verify Code, and approve on the Authorize Connection screen.
The code lasts 15 minutes, with a countdown beside Code expires in. If it runs out, Generate New Code gives you a fresh one.
Step 4. Done. The plugin shows Connected successfully!, payment processing resumes, and WeeConnectPay reappears at your checkout on its own. On a store that has been set up before, you land back on WeeConnectPay Settings with your configuration intact.
Using a Clover account other than the one that owns the business is the most common snag in this flow.
The message you see just after reconnecting
Right after a reconnect you may see an informational notice reading "WeeConnectPay has been reconnected and is awaiting your first transaction to confirm the connection.", and a Reconnected, awaiting first transaction badge on the settings page beside your merchant name.
That is the all-clear. The connection is restored and the store is taking payments again; the notice simply says that no transaction has run through the new credentials yet. It clears itself on your first successful payment.
Reconnect on PrestaShop and on a Zoho storefront
On PrestaShop, log in to your back office, go to Modules → Module Manager, open the WeeConnectPay module settings, and start the reconnection there. On a Zoho storefront, open the WeeConnectPay settings panel in your Zoho application and start it from there.
Both then follow the same path as WooCommerce: sign in with the Clover account that owns the business and confirm the short code. The integration restores itself once the request is approved.
Zoho Books is a separate connection
If you take card payments on Zoho Books invoices, that connection is its own thing and it is not reconnected from inside any Zoho application. It lives on the Zoho Books page of your WeeConnectPay dashboard, and it has two sides that can need attention independently.
Your Clover connection is the one this article covers, and everything above applies to it.
Your Zoho authorisation is what lets us read invoices and record payments in Zoho Books. When it stops working, the organisation's row on the Zoho Books page carries the message "Zoho Books can no longer read invoices for [your organisation]. Payments already taken are safe. New pay links for this organisation stop working until you reconnect." Click Reconnect on that row and approve at Zoho again.
You may also see "This connection was authorised before Zoho Books gained its current permissions. Reconnect to grant them. Nothing already linked changes." in the Zoho account block. Zoho only grants permissions at its consent screen, so reconnecting is how a connection picks up a permission we have added since you first approved it. Nothing already linked changes, and no payment is affected.
Either way, payments you have already taken are safe and your payment history is kept. Connect Zoho Books to WeeConnectPay covers the connection in full.
Why it happened
The common causes, none of which mean anything is wrong with your store:
- The WeeConnectPay app was uninstalled from your Clover account, which revokes the credentials for every store connected through it.
- Someone revoked the connection from the WeeConnectPay dashboard. Revoking API access disconnects your store covers that case in full.
- The employee whose Clover account connected the store was removed from the Clover account, or their Clover permissions changed.
- A different person reconnected the store, which replaces the previous credentials.
- The Clover account changed hands.
Frequently asked questions
Will I lose my transaction history? No. Reconnecting only re-establishes credentials. Your orders, your customers, and every payment already recorded stay exactly as they are on both sides.
Do I need to configure the plugin again? Reconnecting with Logout, keep settings preserves your payment preferences: your transaction mode, your order printing and Google Pay choices, and your fraud protection settings all come back with the connection. Your tax rate links and product links are rebuilt after you reconnect, from the Taxes and Inventory tabs.
I reconnected and it disconnected again. Email support@weeconnectpay.com and say that the disconnection recurs after reconnecting. Forwarding the original disconnection email is the fastest way for us to find your store.
The email mentions Staging or Sandbox. Your store is pointed at a test environment rather than the live one. If you are not deliberately testing, email support@weeconnectpay.com and we will sort it out with you.