This is the full list of messages WeeConnectPay can put in front of you or your customer, grouped by where you see them. Find the wording you saw, read what it means, and take the next step. Every message below is quoted exactly as the software writes it.
Messages appear in the language your store or dashboard is set to. The English wording is given here.
Start here: which problem do you have?
"Checkout doesn't work" is two different situations with two different answers.
- WeeConnectPay is not offered at checkout. Customers never see it as a payment option. Go to Notices in your WordPress admin below: when the connection to Clover is broken, WeeConnectPay hides itself from checkout on purpose rather than letting customers attempt payments that cannot be processed.
- The payment is attempted and fails. The customer enters card details and gets a message. Go to What your customer sees at checkout below.
Within the second case, separate a decline from an error:
- A decline means the payment reached the card networks and was refused: insufficient funds, wrong card details, or the issuing bank saying no. It sits between the customer and their bank. If every card is refused, including cards you know are good, read it as an error instead.
- An error means the payment did not complete for a technical reason. The order notes on the WooCommerce order carry the specific message: WooCommerce → Orders → the order → Order notes.
One cause covers a large share of errors on an otherwise healthy store: currency. Your Clover account processes in its own currency. If a cart is in a currency your Clover account cannot process, the charge fails at payment time even though checkout looks normal up to that point. Compare WooCommerce → Settings → General → Currency with the Processing currency shown on the Processing profile page of your WeeConnectPay dashboard.
What your customer sees at checkout
These messages appear on the checkout page. Your customer sees them, you usually do not.
The card form is incomplete or invalid
| Message | What it means | Next step |
|---|---|---|
| "Please enter your payment information." | The payment form was submitted untouched. | The customer fills in the card fields. |
| "Please enter a valid credit card number." | The card number field is empty or not a valid number. | The customer re-enters the card number. |
| "Please enter a valid credit card expiry date." | The expiry field is empty or not a valid date. | The customer re-enters the expiry date. |
| "Please enter a valid credit card CVV number." | The security code field is empty or not valid. | The customer re-enters the three or four digit code from the card. |
| "Please enter a valid credit card postal code." | The postal code field is empty or not valid. | The customer re-enters the postal code that belongs to the card's billing address. |
| "A shipping address state, county or province is required for this gateway." | The order reached payment without a state, county, or province on the shipping address. | The customer completes the shipping address. If this happens on every order, check the address fields your checkout collects. |
The card was refused
| Message | What it means | Next step |
|---|---|---|
| "Your card was declined. Please try a different card or contact your bank." | The card issuer refused the payment. | Nothing to fix on your store. The customer retries with another card or contacts their bank. |
| "Your card has expired. Please use a different card." | The card's expiry date has passed. | The customer uses a valid card. |
| "The card security code (CVC) is incorrect. Please check your card details." | The security code did not match the card. | The customer re-enters the code. |
| "The card number is invalid. Please check your card details." | The card number was rejected as invalid. | The customer re-enters the number. |
| "The postal code does not match the card. Please re-enter your billing information." | The billing postal code did not match what the card issuer holds. | The customer corrects the billing address. |
| "There was a problem processing your card. Please try again." | A processing problem between Clover and the card network. | The customer retries. If it repeats across many customers, email support. |
| "Your card could not be verified with your bank. Please try again, or use a different card." | The card could not be verified with the issuing bank, so the payment stopped before the issuer was asked to approve it. | The customer retries or uses another card. |
| "The payment could not be processed. Please try again." | The payment did not go through and no more specific reason is available for the customer. | The order notes on the WooCommerce order carry the detail. |
The payment stopped before or after the card step
| Message | What it means | Next step |
|---|---|---|
| "Payment verification failed. Please try again or use a different card." | The extra card verification step did not complete. | The customer retries or uses another card. |
| "We could not complete the security check, so no payment was taken. Please refresh the page and try again. If you use an ad blocker or privacy extension, allow this page and retry." | The bot-protection check on your checkout could not run in the customer's browser. No money moved. | The customer refreshes and retries, allowing the page in any blocker. |
| "We could not complete the security check, so no payment was taken. Please try again in a few moments, and contact the store if the problem continues." | The bot-protection check could not return a result. No money moved. | The customer retries. If every order hits this, check the reCAPTCHA site and secret keys under WooCommerce → Settings → Payments → WeeConnectPay. |
| "We were unable to verify your checkout and no payment was processed. Please try again." | Checkout could not be verified and stopped before payment. | The customer retries. If it repeats, send us a debug log. |
| "The security check was closed before it finished, so the payment was not started. Please try again and complete the verification step." | The customer closed the bot-protection challenge before finishing it. No request reached the payment provider and no money moved. | The customer retries and completes the challenge. |
| "Too many payment attempts in a row. Please wait a few seconds before trying again." | The checkout was submitted several times within a few seconds, usually a double-click or a theme that fires the button twice. Nothing was sent. | The customer waits a few seconds and clicks once. If every order hits this, tell us which theme and checkout page you use. |
| "Clover’s card tokenization service did not respond, so the payment could not be started. This is not a problem with your card and not something this store can change. Please try again in a few minutes." | Clover, the payment provider, did not answer when the card was being secured. This is on Clover's side, it affects every store at once, and no money moved. After two such answers in a row, checkout stops calling Clover for a minute and shows this same message. | The customer retries in a few minutes. Check status.clover.com. If it lasts more than an hour with Clover reporting no incident, send us a debug log. |
| "The payment could not be started because Clover’s card tokenization service stopped responding. This is not a problem with your card. Please try again in a few minutes." | Clover took longer than 45 seconds to secure the card and the checkout gave up waiting. No money moved. | The customer retries in a few minutes. Same checks as the message above. |
| "Payment configuration incomplete. Please refresh the page." | The block-based checkout loaded without the payment settings it needs. | The customer refreshes. If it persists, confirm the gateway is enabled under WooCommerce → Settings → Payments. |
| "Payment failed. Please try again." | The payment did not complete. | The order notes carry the specific cause. |
| "Payment processing failed. Please try again." | Processing stopped before the payment completed. | The order notes carry the specific cause. |
| "An unexpected error occurred during payment processing. Please try again." | An unexpected condition stopped the payment. | The order notes carry the detail. Send us a debug log if it repeats. |
| "An unexpected error occurred while trying to update the payment method. Please try again." | The customer was replacing the card saved on a subscription or a pending order, and the change did not complete. | The customer retries. Send us a debug log if it repeats. |
| "No payment was processed." | Checkout ended without a payment being taken. | The order stays unpaid and can be retried. |
| "A malformed response was received. Our team has been notified. We are sorry for the inconvenience." | A response came back in a shape the plugin could not read. Our team is alerted automatically. | Retry the action. Email support with the order number if it repeats. |
Notices in your WordPress admin
These appear as banners across the top of your WordPress admin screens, and on the WeeConnectPay settings page.
| Notice | What it means | Next step |
|---|---|---|
| "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." | Clover no longer accepts the credentials your store uses. WeeConnectPay is hidden at checkout until it is reconnected. | Follow the notice's Go to WeeConnectPay settings link and sign in with Clover again. Full walkthrough in Reconnecting WeeConnectPay and Clover. |
| "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." | The credentials your store uses to talk to WeeConnectPay expired or were revoked. | Same fix: sign in with Clover again from the settings page. New credentials are issued automatically. |
| "Your WeeConnectPay integration is disconnected and is not processing payments. Please reconnect to continue accepting payments." | The integration is disconnected. | Reconnect from WooCommerce → Settings → Payments → WeeConnectPay. |
| "WeeConnectPay is hidden at checkout: your store sells in" one currency, "but your Clover account settles in" another, then "Clover refuses a payment in any other currency, so a card form would fail after the customer has entered their card. Set the WooCommerce store currency to" the Clover currency, "or connect the Clover account that uses" the store currency. | Your WooCommerce currency and your Clover processing currency differ. WeeConnectPay hides itself at checkout rather than let every payment fail after the card is entered. | Change WooCommerce → Settings → General → Currency to the currency the notice names, or connect the Clover account that processes in your store's currency. See Currencies your store can charge. |
| "WeeConnectPay has been reconnected and is awaiting your first transaction to confirm the connection." | The reconnection worked. The notice clears once a transaction confirms the connection end to end. | Nothing. Place or wait for an order. |
| "A Clover API key is needed to use this plugin." | The plugin has no Clover credentials yet. | Connect the plugin to Clover from the settings page. |
| "WeeConnectPay could not find an associated account with the provided Clover API Key. Log in the WeeConnectPay app through the Clover app market to resolve this." | The credentials do not match a WeeConnectPay account. | Open the WeeConnectPay app from the Clover App Market and sign in, then reconnect the store. |
| "An error occurred while trying to establish a connection with Clover, please try again in a few minutes." | The connection attempt did not complete. | Try connecting again in a few minutes. |
| "The connection with Clover has been successfully established!" | The connection is live. | Nothing. |
If there is no red notice and WeeConnectPay is still missing at checkout, check that the gateway is switched on under WooCommerce → Settings → Payments in the payment methods list.
Connecting a store: the connection code
Connecting a store shows a code in your plugin settings that you approve with your Clover account, on a page that asks you to "Enter the code shown in your integration's settings to link it to your Clover account." These are the messages that page can answer with.
| Message | What it means | Next step |
|---|---|---|
| "Invalid or expired code. Check the code shown in your store and try again." | The code was not recognized. | Copy the code again from your store's WeeConnectPay settings. Request a new one if it has been sitting for a while. |
| "This code has expired or is no longer valid." | The code ran out before it was approved. | Request a new code in the plugin settings and enter it right away. |
| "This code is no longer pending." | The code was already approved or denied. | Request a new code if the store still is not connected. |
| "Enter the code shown in your store before approving or denying it." | Approving was attempted before a code was entered and checked. | Enter the code first, then approve it. |
| "No Clover context found. Please sign in with Clover again." | Your session no longer carries a Clover merchant. | Sign in with Clover again, then enter the code. |
| "Your Clover account does not match this app. Please log in with the correct account." | The Clover account you are signed in with is not the one this connection is for. | Sign in with the Clover account that owns the store. |
| "App context mismatch. Please switch to the correct app context." | You are working in a different Clover app than the one that asked for the code. | Switch to the right app, then enter the code again. |
| "This code was requested for a different app. Please switch to the correct app context." | Same case, seen when the code belongs to another app. | Switch to the app your store is connecting to, then retry. |
| "This store is already connected to a different Clover merchant. Your request has been sent to them, and they can release the store from their WeeConnectPay dashboard. If you also have access to that merchant, switch to it, release the store, then enter this code again." | Another Clover merchant already holds this store. | The merchant holding it releases the store from their dashboard, then your code works. If both merchants are yours, switch to the other one, release the store, and enter the code again. |
Notes on the WooCommerce order
WeeConnectPay writes a note on the order for every payment outcome. Open WooCommerce → Orders → the order → Order notes.
Payment outcome notes
| Note | What it means | Next step |
|---|---|---|
| "Clover payment successful!" | The payment went through on the Order and charge transaction mode. The note carries the payment ID, amount, card details, and authorization code. | Nothing. |
| "Clover pre-authorization charge successful!" | Funds were held, not taken. This is the Hold and charge later mode. | Capture the charge from the order page when you are ready to take the money. |
| "Clover capture charge successful!" | The card was charged and the money is taken. This is the ordinary success note on the Charge at checkout mode, where the card is charged in one step. A hold you capture later leaves "Pre-authorized charge successfully captured!" instead. | Nothing. |
| "Clover custom tender payment successful!" | The order was recorded against a custom tender on Clover. The note names the tender. | Nothing. |
| "Clover payment successful (confirmed on retry)." followed by "The first payment attempt was interrupted before its result arrived, and the automatic retry confirmed the payment had already been completed on Clover. The shopper was charged exactly once." and "The payment reference is available in the WeeConnectPay dashboard activity for this order." | The first attempt was interrupted before its result arrived, and the automatic retry found the payment already completed on Clover. | Nothing. The customer was charged once. |
| "Successfully updated payment method!" | The card saved on a subscription or a pending order was replaced with a new one. The note carries the new token reference. | Nothing. |
| "3-D Secure" followed by the flow type and "flow initiated. Waiting for the browser to complete verification." | The customer's bank asked for a 3-D Secure check and the customer's browser is completing it. A payment note follows once it ends. | Nothing yet. If no payment note follows, the customer closed the check; they can retry. |
| "3-D Secure verification could not be completed. The outcome is unknown — check the charge in your Clover dashboard before retrying. Error:" followed by the technical message | The 3-D Secure check ended in an error and the plugin could not tell whether the charge went through. | Look the charge up in your Clover dashboard before asking the customer to pay again, so they are not charged twice. Send us a debug log. |
| "A previous attempt to create the Clover order did not complete." followed by "A Clover order may have been created without being linked to this order. A new one is being created now, so check the Clover dashboard for a duplicate unpaid order before taking payment again." | An earlier checkout attempt was interrupted while the Clover order was being created. The plugin creates a fresh one; the earlier one may exist in Clover unpaid. | Check your Clover dashboard for an unpaid duplicate and delete it. No money moved on the interrupted attempt. |
| "Clover payment failed." | The payment did not complete. | Read the rest of the note for the reason and code. |
| "Clover charge failed." | The charge did not complete. | Read the rest of the note for the reason and code. |
| "Clover custom tender payment failed." | The custom tender payment did not complete. | Read the rest of the note, then retry. |
| "Payment could not be processed." | Payment stopped. | The note carries the error code and message. |
| "Payment could not be processed: creating the Clover customer failed." | The customer record could not be created on Clover, so the payment stopped. | Retry the order. Send us a debug log if it repeats. |
| "Payment could not be processed: preparing the Clover order failed." | The Clover order could not be assembled, so the payment stopped. | Retry the order. Send us a debug log if it repeats. |
| "Payment could not be processed: the payment provider is unavailable." | The payment provider could not be reached. The note adds: "The outcome is indeterminate. A new attempt by the shopper safely reuses the same payment key: it cannot charge twice." | The customer can safely retry. A retry cannot produce a second charge. |
| "The Clover charge response was malformed and could not be processed. Check the WeeConnectPay debug log for the raw payload." | The response came back in a shape the plugin could not read. | Turn on Debug Mode, reproduce, and send us the log. |
| "Order sent to printing queue of your default Clover printing device." | The order reached your Clover printer queue. | Nothing. |
| "Clover order created." | A Clover order was created for this payment, with its ID. | Nothing. |
Fraud protection notes
| Note | What it means | Next step |
|---|---|---|
| "Payment blocked: missing reCAPTCHA token." followed by "The card was tokenized but no reCAPTCHA value was submitted, which points to an outdated cached copy of the checkout script in the customer's browser. Ask the customer to refresh the page and try again." | The checkout script was stale in that customer's browser. | Ask the customer to refresh and retry. Clearing your site cache stops it recurring. |
| "Payment blocked: missing reCAPTCHA token." followed by "The card token is also missing, so this submission did not go through the WeeConnectPay checkout script: it never loaded, crashed before tokenizing the card, or the form was submitted without it (broken or cached checkout page, blocked scripts). Check recent orders for reCAPTCHA error notes (for example an invalid site key) and ask the customer to refresh the page and try again." | The checkout script did not run at all for that submission. | Check recent orders for reCAPTCHA error notes, then have the customer refresh and retry. |
| "Payment blocked: Google reCAPTCHA did not return a result." followed by "The checkout script submitted an error instead of a reCAPTCHA token, so the customer could not be verified. If this affects every order, check the reCAPTCHA site and secret keys in the gateway settings. Reported error: " | reCAPTCHA returned an error instead of a score. | If it affects every order, check your reCAPTCHA site and secret keys in the gateway settings. |
| "According to your plugin settings for Google reCAPTCHA, the customer who paid for the order is likely a human being." | The reCAPTCHA score cleared your threshold. | Nothing. |
| "According to your plugin settings for Google reCAPTCHA, the customer who paid for the order is NOT likely a human being. The order will be cancelled. If you are sure that this order was legitimate, please decrease the minimum human score threshold in the gateway settings." | The score fell below your Minimum Human Score Threshold and the order was cancelled. | If the order was genuine, lower the threshold in the gateway settings. The settings page notes that "A threshold above 0.9 will likely reject legitimate customers. Most sites use 0.5." |
| "The hidden honeypot field was filled out. Likely a bot. Cancelling order. Field Value: " | A hidden field only a bot would fill was filled. | Nothing. This is the honeypot working. |
| "The request to Google reCAPTCHA triggered an exception. See exception message: " | Your store could not reach Google's reCAPTCHA service to score the customer. | If it repeats, check that your server can reach www.google.com; the message that follows names the cause. |
| "The response from Google reCAPTCHA contains errors. See error codes: " | Google answered with an error instead of a score, most often an invalid site or secret key. | Check the reCAPTCHA site and secret keys under WooCommerce → Settings → Payments → WeeConnectPay. |
| "The response from Google reCAPTCHA contains unexpected errors. Full response: " | Google's answer was in a shape the plugin did not expect. | Send us the order note. |
| "Warning: An error has occurred: We could not detect the postal code used for the transaction." | Postal code verification ran but no postal code was available to compare. | Informational. Check what address fields your checkout collects if you rely on this comparison. |
| "Info: Please note that the shipping ZIP/Postal code" and "and the billing ZIP/Postal code" and "are different." | Shipping and billing postal codes differ on this order. | Informational, for your own review. |
| "Warning: Please note that the billing ZIP/Postal code" and "and the payment card ZIP/Postal code" and "are different. These should be the same." | The billing postal code does not match the card's postal code. | Review the order before fulfilling if that matters to you. |
Refund and release notes
| Note | What it means | Next step |
|---|---|---|
| "Refund sent to Clover:" with the amount, then "Awaiting confirmation." | The refund request left for Clover and the answer has not arrived yet. A second note follows with the outcome. | Wait for the next note before refunding again. |
| "Refund rejected." followed by "No money was returned. Reason:" and Clover's reason | Clover refused the refund. Nothing moved. | Read the reason. A charge that has not been batched out yet, or one already refunded in Clover, are the usual causes. |
| "Refund outcome could not be confirmed." followed by "The refund was sent to Clover but the response was not recognised, so we cannot tell whether the money moved. The refund line has been kept on this order rather than removed. Check this charge in your Clover dashboard before refunding again: a second refund would return the money twice." | The refund may or may not have gone through. | Look the charge up in your Clover dashboard before doing anything else. |
| "The Clover refund succeeded, but WooCommerce could not record it." followed by "Amount refunded at Clover:", "Clover refund ID:", "WooCommerce refused the refund line because:" and "The money has left your account." then "Do not refund this charge again. WooCommerce order totals and Analytics will understate this refund until the refund line is added by hand." | The money went back to the customer, but WooCommerce would not save the refund line. | Do not refund again. Add the refund line by hand on the order so your totals and Analytics match Clover. |
| "Pre-authorization released." followed by "Amount released:", "Clover reference:" and "No money was ever captured, so no refund was issued and no refund line was added to this order." | A hold that was never captured was released back to the card. | Nothing. There was no money to refund. |
Tax and inventory notes
| Note | What it means | Next step |
|---|---|---|
| "Tax rate link mismatch detected." followed by "A WooCommerce tax rate on this order no longer matches its linked Clover rate, so Clover did not record that rate by name for this charge. The charge and its tax amount are correct." and "Review the tax rate links in the WeeConnectPay settings to restore it." | A rate drifted apart from its Clover pairing. Money and tax amounts are correct; only the rate name is missing in Clover reporting. | Open the Taxes tab in the plugin settings and relink the rate. See Linking your tax rates to Clover. |
| "Tax breakdown could not be verified." followed by "The tax details sent with this charge did not add up, so no tax information was forwarded to Clover. The charge and the WooCommerce tax amounts are correct and unaffected. Check the WeeConnectPay debug log for details." | The tax details did not reconcile, so none were forwarded. WooCommerce keeps the full breakdown. | Check your WooCommerce tax configuration. See How WeeConnectPay reports your taxes to Clover. |
| "Some items on this order were not matched to Clover inventory." followed by "The payment and order totals are correct and unaffected." | Some lines could not be attributed to Clover items. | Read the sentences that follow in the same note for which case applies. |
| The same note continuing with "apply their own taxes in Clover, so online sales cannot be counted against them. No change to the product links can fix this, and their stock sync stays paused to keep counts correct." | Those Clover items carry their own taxes, so web sales cannot be counted against them. | Nothing to fix in the links. Change the item's taxes in Clover if you want those sales attributed. |
| The same note continuing with "One or more products could not be checked against their linked Clover items, so Clover was not told which items those lines were for. Review the product links in the WeeConnectPay settings to restore stock sync and sales reporting for them." | The product links could not be checked for those lines. | Open the Inventory tab in the plugin settings and review the links. See How inventory sync works. |
Refunds, captures and voids
These appear in the WeeConnectPay Charges panel on the order edit page, or from WooCommerce's own Refund button.
| Message | What it means | Next step |
|---|---|---|
| "Partial refunds are not supported for order-based charges. Only a full refund of the entire charge amount can be processed." | The order was paid on the Order and charge mode, where refunds work on whole line items. | Refund the whole charge, or refund whole line items. See Refunds on Order and charge. |
| "Only full refunds are supported for order-based charges." | Same case, raised when a partial amount is submitted. | Refund the full amount. |
| "Due to an undocumented breaking change in the Clover API, we have temporarily disabled partial refunds." followed by "This request to refund will not be processed. Should you want to do a partial refund, you can do so through your Clover web dashboard." | Partial refunds are blocked on the Order and charge mode. | Refund whole line items, refund the full charge, or issue the partial refund in your Clover dashboard and update the WooCommerce order status yourself. |
| "This partial refund was declined because the transaction has not been closed out yet. Partial refunds on captured pre-authorizations are only available after the daily batch closeout. You can try a full refund, or retry after the batch has closed." | A captured hold cannot take a partial refund until the day's batch has closed. | Issue a full refund now, or retry the partial refund after closeout. |
| "Partial refunds on captured pre-authorizations may only be available after the daily batch has been closed out. If the partial refund is declined, you can try a full refund instead." | The same rule, shown ahead of time on the refund form. | Nothing yet. It tells you what to expect. |
| "A return has been processed for this order. Order-based charges cannot be refunded further once any items have been returned." | A return already ran against this order. | Check in Clover what was already returned. |
| "This order contains gift card or loyalty card payments. For security reasons, partial refunds are not available when multiple payment methods are used." The message continues by pointing you at the Refund button in the WeeConnectPay Charges section above, for a full refund of each transaction. | The order has more than one charge, so a line-item refund cannot be routed unambiguously. | Refund each charge in full from the WeeConnectPay Charges panel. |
| "Order has been already refunded" | The order is already fully refunded. | Nothing. |
| "Refund amount must be higher than 0." | The refund amount was zero or empty. | Enter an amount. |
| "Please enter a valid refund amount." | The amount entered could not be read as a number. | Re-enter the amount. |
| "Refund amount cannot exceed the remaining charge amount." | The amount is larger than what is left to refund on that charge. | Lower the amount. The form defaults to the remaining balance. |
| "Refund exceeds the remaining refundable amount on this charge" | Same case, with the remaining amount named in the message. | Lower the amount. |
| "Please select a reason." | The refund form needs a reason. | Pick one from the dropdown. |
| "That charge does not belong to this order." | The charge and the order do not match. | Refund from the order the charge belongs to. |
| "No charges found for this order." | No WeeConnectPay charge is recorded on this order. | Confirm the order was paid through WeeConnectPay. |
| "No refundable charge found. Please use the WeeConnectPay Charges metabox for individual charge refunds." | WooCommerce's own Refund button has nothing to act on here. | Use the WeeConnectPay Charges panel on the same page. See Partial refunds on Direct Charges. |
| "An error occurred while processing the refund." | The refund did not complete. | Retry. Send us a debug log if it repeats. |
| "An error occurred while processing the void." | The void did not complete. | Retry. Send us a debug log if it repeats. |
| "The preauthorized charge has already been captured. Did you capture it directly in the Clover dashboard?" | The hold was already captured, most often in Clover directly. | Refund instead of capturing. |
| "Capture already in progress. Please wait." | A capture is already running for this charge. | Wait a moment and reload the order. |
| "No pre-authorized charge found for this order." | There is no hold on this order to capture. | Check the order's charges in the WeeConnectPay Charges panel. |
| "An error occurred while capturing the charge. Please try again." | The capture did not complete. | Retry. Send us a debug log if it repeats. |
| "Charge capture failed." | The capture did not complete, recorded as an order note with the error code and message. | Retry, then send us a debug log with the order number. |
| "Invalid response from payment processor." or "Unexpected response from payment processor." | A response came back in a shape the plugin could not read. | Reload the order to see the current state, then send us a debug log. |
Taxes tab messages
These appear under WooCommerce → Settings → Payments → WeeConnectPay → Taxes.
| Message | What it means | Next step |
|---|---|---|
| "WeeConnectPay: a WooCommerce tax rate no longer matches its linked Clover tax rate." followed by "Payments are not affected and tax amounts stay correct, but Clover stops naming that rate on charges until the link is fixed." | A linked pair drifted apart. | Use the Review tax rate links button in the notice. |
| "Connect the plugin to Clover to load and link tax rates." | The plugin is not connected yet. | Connect from the settings page. |
| "Clover tax rates could not be loaded right now. WooCommerce rates are shown; linking will be available once the connection is restored." | Clover could not be reached for the rate list. | Retry once the connection is back. |
| "No WooCommerce tax rates found. Add rates under WooCommerce, Settings, Tax to link them with Clover." | Your store has no tax rates to link. | Add rates in WooCommerce first. |
| "Clover tax rates have not been synced yet. Refresh to fetch them from Clover." | The Clover rate list has never been loaded. | Use Refresh Clover rates. |
| "No matching Clover rate" and "Only Clover rates with exactly the same percentage can be linked. Create a matching rate in Clover, then refresh." | No Clover rate sits at exactly this percentage. | Create the matching rate in Clover, then refresh. |
| "Compound rates have no Clover equivalent. Amounts stay correct, Clover just will not name this rate." | Compound rates stay unlinked by design. | Nothing. Amounts are still charged correctly. |
| "That tax class already has a rate at this priority. WooCommerce only applies one rate per priority, so adding another here would quietly undercharge tax. Change the priorities under WooCommerce, Settings, Tax, then try again." | Two rates at the same priority in one class would mean only one is applied. | Change the priorities under WooCommerce → Settings → Tax, then retry. |
| "This is a flat-fee Clover rate. WooCommerce rates are percentages, so a flat fee cannot be created or linked here." | Flat fees and percentage rates are different shapes. | Nothing. |
| "Clover has two live rates with this exact name and percentage, so a link could point at the wrong one. Remove the duplicate in Clover first." | Two identical Clover rates make the link ambiguous. | Remove the duplicate in Clover, then retry. |
| "This Clover rate has more decimal places than WooCommerce can store, so it cannot be matched exactly here." | The precision does not fit. | Nothing. |
| "The chosen tax class no longer exists. Reload the page and pick another class." | The class was removed while the form was open. | Reload and pick again. |
| "A tax class with this name already exists. Pick a different name." | The name is taken. | Choose another name. |
| "WooCommerce refused to save the new rate. Check your WooCommerce tax settings and try again." | WooCommerce rejected the write. | Check your tax settings, then retry. |
| "The link could not be saved, so the new rate was removed again. Refresh the Clover rates and try again." | The rate was created but the link failed, so the rate was rolled back. | Refresh and retry. |
| "Your tax reporting choice could not be loaded right now. Charges keep using your saved choice. Try again once the connection is restored." | The forwarding mode could not be read. Your saved mode keeps running. | Retry later. |
| "Connect the plugin to Clover before choosing a tax forwarding mode." | The plugin is not connected. | Connect first. |
| "The mode could not be saved. Please try again." | The change did not save. | Retry. |
Inventory tab messages
These appear under WooCommerce → Settings → Payments → WeeConnectPay → Inventory, on the product link rows.
| Message | What it means | Next step |
|---|---|---|
| "Paused: tax rates differ" with "Sales are not counted against this Clover item and its stock is not syncing, because their taxes do not match." | The product and its Clover item apply different taxes. | Change the product's tax class, link the rates on the Taxes tab, or change the item's taxes in Clover. |
| "Paused: tax rate link missing" with "Sales are not counted against this Clover item and its stock is not syncing, because one of its tax rates is not linked yet." and "Nothing is wrong on either side, a link is just missing. Add it on the Taxes tab." | A rate simply has no link yet. | Add the link on the Taxes tab. |
| "Paused: tax setup unconfirmed" with "This Clover item’s taxes could not be confirmed yet, so sales are not counted against it and its stock is not syncing. Refreshing from Clover usually sorts it out." | The item's taxes have not been confirmed. | Use Refresh from Clover. |
| "Attribution blocked by Clover item taxes" with "This Clover item applies its own taxes in Clover, so sales are not counted against it and its stock is not syncing." | The Clover item carries its own taxes. | Change the item's taxes in Clover if you want web sales attributed to it. |
| "SKU mismatch" | The product SKU and the linked Clover item SKU no longer match. | Fix the SKU on either side, or relink the product. |
| "Clover item deleted" | The linked Clover item no longer exists. | Recreate the item in Clover and relink, or remove the link. |
| "WooCommerce product deleted" | The product behind the link is gone. | Remove the link, or relink if you recreated the product. |
| "No stock count in Clover" with "This Clover item has no stock count yet, so there is nothing to bring over. Open the item in Clover, turn on stock tracking and set a count, then use Refresh from Clover." | Clover holds no count for that item. | Set a count in Clover and refresh. |
| "Stock management off in WooCommerce" | The product is not tracking stock in WooCommerce, so the Clover count is not used. | Switch on Manage stock on the product, or let the next sync turn it on in Follow Clover or Two-way. |
| "Connect the plugin to Clover to load and link inventory items." | The plugin is not connected. | Connect first. |
| "Clover inventory items could not be loaded right now. WooCommerce products are shown; linking will be available once the connection is restored." | Clover could not be reached for the item list. | Retry once the connection is back. |
| "Stock sync is paused because your current plan does not include your saved mode. Your choice is saved. Upgrade or re-check your plan on the Inventory tab." | Your Clover plan does not include the mode you picked. | Upgrade in the Clover App Market, then use I've upgraded: re-check my plan. |
| "The stock sync mode could not be loaded right now. Syncing keeps using your saved mode. Try again once the connection is restored." | The mode could not be read. Your saved mode keeps running. | Retry later. |
Inventory Tools transfers
These appear in Inventory Tools, the bulk import and export screen.
| Message | What it means | Next step |
|---|---|---|
| "Connect your Clover account first" with "Inventory Tools needs a connected Clover account. Head to the WeeConnectPay settings page to sign in, then come back here." | Not connected yet. | Connect, then return. |
| "Inventory transfers need a subscription upgrade" with "Transfers require the" plan named, then "subscription tier. Your selection is kept, so you can upgrade and submit again without re-picking." | Transfers need a higher Clover plan. | Upgrade in the Clover App Market. Your selection is kept. |
| "Select at least one product to export." or "Select at least one Clover item to import." | Nothing was selected. | Pick at least one row. |
| "A transfer is limited to 1000 products. Trim the selection and run another transfer for the rest." | The selection is over the per-run limit. | Split it into several runs. |
| "Some selected products can no longer be exported. Review the reasons below and adjust the selection." | Something changed since you picked them. | Read the per-row reasons and adjust. |
| "A transfer is already running for this direction. Attaching to it." | A run is already in flight. | Nothing. The page attaches to the existing run. |
| "This transfer already finished, so there is nothing to cancel." | The run ended before the cancel arrived. | Nothing. |
| "The import is paused. Products are only created while this page is running the import." | The import needs the page open. | Use Resume import and keep the page open. |
| "The import hit a problem and paused. Nothing is lost, resume to continue." | The run paused on an error. | Resume. |
| "Some items are still held by an earlier import. They free up within 15 minutes, and this import keeps waiting for them." | An earlier run still holds those items. | Wait. The run keeps waiting. |
| "This transfer has been quiet for a while. It will pick back up or stop on its own. Nothing for you to do." | The run went quiet. | Nothing. |
| "The WooCommerce product catalog could not be read. Make sure WooCommerce is active, then reload this page." | The catalog could not be listed. | Confirm WooCommerce is active and reload. |
| "We could not reach our service. Check your connection and try again." | The request did not reach us. | Check the connection and retry. |
| "Something went wrong on our side. Try again in a moment." | An unexpected condition on our side. | Retry shortly. |
Per-item outcomes shown after a run include "SKU already used by a WooCommerce product", "Tax rates not linked yet, link them first", "Already linked to a WooCommerce product", "Already linked to a Clover item", "Item no longer exists", "Product no longer exists", "Product is in the trash", "Only simple products can be exported", "Product has no regular price", "A Clover item already uses this SKU", "Clover rejected the tax association", "Stock quantity could not be written", "Name is missing or longer than Clover allows", "Clover connection was unavailable", "Processing gave up after repeated errors", "Processing stalled", "Run was canceled before this item", "WooCommerce product could not be created", and "Skipped by your choice". Each names the one thing that stopped that row; the rest of the run still completes.
In your WeeConnectPay dashboard
| Message | What it means | Next step |
|---|---|---|
| "Session expired" with "Your session has ended due to inactivity. Sign in again to continue where you left off." | You were signed out for inactivity. | Use Sign in again. |
| "No merchant context found. Please log in again." | The dashboard could not tell which merchant you are working in. | Sign in again. |
| "This page is taking too long" with "We stopped loading this page because it was taking longer than we allow. Nothing is broken and nothing was lost. Try again in a moment, or ask for a smaller date range." | The request hit its time limit. | Retry, or narrow the date range. |
| "Something went wrong" with "An unexpected error occurred while rendering this page." | The page could not render. | Reload. Email support if it persists. |
| "Not included in your Clover plan" with "Tax tools are not part of your current Clover plan. To use them, upgrade your plan in your Clover account. Your checkout and payments are not affected." | The Taxes page needs a higher Clover plan. | Upgrade in your Clover account. |
| "Not included in your Clover plan" with "Inventory tools are not part of your current Clover plan. To use them, upgrade your plan in your Clover account. Your checkout and payments are not affected." | The Inventory page needs a higher Clover plan. | Upgrade in your Clover account. |
| "Not synced yet" with "We have not synced this merchant's Clover tax rates yet. Refresh to load them now." | The rate snapshot has never been loaded. | Use Refresh from Clover. |
| "Not synced yet" with "We have not synced this merchant's Clover inventory yet. Refresh to load it now." | The inventory snapshot has never been loaded. | Use Refresh from Clover. |
| "Not confirmed yet" with "Your processing details are confirmed from Clover when you sign in. Sign in again to load them." | The processing profile has not been confirmed yet. | Sign in again. |
| "This store's forwarding mode needs linked rates, but none are linked. Clover receives no rate attribution until rates are linked in the plugin settings." | The mode expects links that do not exist yet. | Link rates in the plugin settings. |
| "Inventory sync is on for this store, but no products are linked. Nothing is attributed or kept in step until products are linked in the plugin settings." | Sync is on with nothing linked. | Link products in the plugin settings. |
On the Transactions page, a failed or declined payment opens a panel titled "Why this payment did not go through" carrying the same explanations you get in an order note, for example "The customer's card issuer refused the payment. Nothing is wrong with your store. The customer can retry with another card or contact their bank." or "The payment could not be processed for a technical reason, not a card refusal. If this continues, contact WeeConnectPay support."
On the API Clients page, each connection carries a status: "Connected", "Needs attention", "Disconnected: Clover authorization expired", "Disconnected: WeeConnectPay key invalid", "Disconnected: app uninstalled", "Disconnected", or "Status unknown". Anything reading Disconnected is fixed by reconnecting from your store, as described in Reconnecting WeeConnectPay and Clover.
Gathering more detail: Debug Mode
When a message here does not settle the question, a debug log does. It records exactly what your store and our servers exchanged with Clover for the action that failed.
Step 1. Turn on Debug Mode. Go to WooCommerce → Settings → Payments → WeeConnectPay → Advanced, find the Debugging section, and switch on Debug Mode, described there as "Enable debug logging. Logs can be viewed below when enabled." The setting saves as soon as you flip it.
Step 2. Reproduce the issue. Trigger the same action again: place the order, attempt the refund, run the transfer. The failure is now captured in full. If you cannot reproduce it, send the log you have with the timestamp and order number.
Step 3. Download the log. Return to the same Advanced tab and scroll to the Debug log panel below. Click Download. Your browser saves a text file. The Clear button beside it wipes the on-disk log if you want a clean slate before reproducing.
Step 4. Send it to us. Email the file to support@weeconnectpay.com with the order number, the time of the attempt, what you expected, and what actually happened including any message from this catalog. Our AI triage agent replies first and asks follow-up questions; a member of our team reviews every ticket.
The debug log contains information specific to your store and your customers, so send it by email rather than posting it on a public forum.
Two messages can appear in the log panel itself: "Error fetching logs. Please make sure debug mode is enabled." and "No logs found. Make sure debug mode is enabled and there are logs in the system." The panel only exists once Debug Mode is on, so both mean nothing has been logged since you switched it on.
Debug Mode is intentional verbosity for troubleshooting. The Automatically clear logs setting beside it offers Never (clear manually), After 3 days, After 1 week, and After 1 month, described on the page as: "Log entries older than this are deleted once a day, so debug mode can stay on without files growing forever."
Keeping this catalog current
Every message above is copied from the software itself, not written from memory. When a WeeConnectPay release adds, changes, or removes a message a merchant can see, this article is updated in the same release, and the Last verified date at the top moves with it. If you meet a message that is not listed here, email it to support@weeconnectpay.com with a screenshot and we will answer you and add it.