WeeConnectPay
Forum Replies Created
-
Hi @wpdv, thanks for the report. That error comes from a UX gap on our end, not a misconfiguration on yours. Quick explanation, then the fix.
Why you saw that message
WeeConnectPay supports two payment flows today, and the gap that hit you sits between them.
- Direct Charges (Authorization + Capture, Pre-Authorization): one Clover charge per order, no per-item breakdown on Clover’s side. This is what your store is set to, and it’s what we now use across our newer integrations (Zoho, PrestaShop). It’s simpler, more maintainable, and where new feature work lands first.
- Orders + Payment (the older WooCommerce flow): every cart line becomes a Clover line item. Some merchants depend on this for Clover-side order printing, kitchen tickets, and inventory tracking, so we keep supporting it. We don’t want to pull the rug on those workflows, especially before our own inventory support is in place.
The Refund button at the bottom of WooCommerce’s Order items table is WooCommerce’s own UI, built around refunding line by line. That fits Orders + Payment well, but on Direct Charges there are no line items to refund against, just one charge for the whole cart. So that button can only handle full refunds on Direct Charges today, and any partial amount entered there produces the “Partial refunds are not supported for this payment type” message you got. We can’t change the wording of that button (WooCommerce owns it and doesn’t expose a per-gateway hook), which is part of why it doesn’t tell you where to go instead.
Partial refunds on Direct Charges work fine, just from a different panel on the same page.
How to do a partial refund
Partial refunds work fine, they just live in the WeeConnectPay Charges metabox on the same order page rather than in WooCommerce’s refund interface.
Step 1: Open the order. Scroll to the WeeConnectPay Charges metabox. The panel circled green below is the right one. The red button at the bottom is the WooCommerce one that gave you the error.
Step 2: Click Refund on the charge card.
Step 3: Enter the partial amount (or use a preset: 25% / 50% / 75% / Custom / Full), pick a reason, and confirm. You can issue further partial refunds against the same charge until it’s fully refunded.
If you hit any other issue
Please reach us at [email protected] rather than posting your store details here. Our AI triage agent replies first (trained on common refund and configuration issues), and a human reviews every ticket too. It’s a faster loop than this thread.
If your email is about a refund or transaction issue, attaching a debug log helps us pinpoint the cause without back-and-forth:
- WooCommerce → Settings → Payments → WeeConnectPay → Advanced, turn on Debug Mode.
- Reproduce the issue.
- In the Debug Logs section just below, click Download.
- Email the file to [email protected] with the order number and what you tried.
Making WooCommerce’s interface clearly guide merchants to the right refund path, in both flows, is genuinely tricky, and feedback like yours is what moves it. If you have thoughts on what would have made the right path obvious to you, this thread is the place to share them. We’ll either confirm we already know about it or pass it to the team.
Hi @22wpexpert ,
The reason you’re seeing a 100% decline rate is due to the Address Verification System (AVS) settings in your Clover merchant account.
With WeeConnectPay, our payment gateway securely integrates Clover’s iframe, significantly reducing PCI-DSS compliance burdens and keeping your customers’ data safe.Currently, our Clover iframe includes these fields:
- Card Number
- Card Expiry Date
- Card CVV
- Card Postal Code
All of these iframe fields are validated by Clover. However, AVS (and all other Clover fraud tools) validates fields according to your chosen settings. Since the street address field isn’t enabled on our iframe but street address verification is enabled in your AVS settings, these transactions fail the street address validation and be declined. We’ve intentionally disabled this field because enabling it would negatively impact user experience—customers would have to enter their billing address twice: once for WooCommerce and again within the Clover iframe.
Also, due to Clover’s strict security protocols, neither WeeConnectPay nor any scripts can access the card or address data entered into the iframe. This safeguards card data from malicious scripts but also prevents automatic filling or transferring data from WooCommerce fields.
To resolve this issue, please review your Clover fraud tool settings and ensure the AVS checks align with these supported fields. You can safely enable other available anti-fraud options such as Google ReCaptcha, which we noticed isn’t activated yet.
We recommend removing any sensitive information, like screenshots containing detailed order notes, from your public posts to help protect your and your customers’ privacy.
If you need additional help optimizing your Clover fraud settings or enabling Google ReCaptcha, please reach out to our support team directly at [email protected] —we’re happy to help!
Thanks again for working with WeeConnectPay!