- This topic has 7 replies, 3 voices, and was last updated 9 months ago by
.
-
Posts
-
I recently updated the WooCommerce Square plugin in my staging environment from version 4.0 to the newest version, 4.4.0. Since this update, credit card payment processing is failing on the VerifyBuyer step of payment processing. To troubleshoot, I deactivated all plugins on my WooCommerce site and set the theme of the site to the default Storefront. I reactivated WooCommerce and the WooCommerce Square plugin as well as ensured that WooCommerce, WordPress and WooCommerce Square were fully updated. In testing against the Square sandbox environment, credit card processing succeeded. I then added each plugin back in, testing whether credit card processing would succeed or fail. All plugins work with the newer version of the WooCoomerce Square plugin except for TeraWallet. I tried multiple versions of WooCommerce Square plugin (4.1, 4.2, 4.3, 4.4) and multiple versions of the TeraWallet plugin (1.4.10, 1.4.9, 1.4.8, 1.4.5, 1.4.0, 1.3.15, etc.) and each was incompatible.
Right now I am stuck not updating WooCommerce square to any version higher than 4.0 because it will cause payment processing to fail with any version of TeraWallet. Both of these plugins are business critical so a resolution is much needed.
Is there any support available for the above? This is still an ongoing issue. I have reached out to WooCommerce Square who provided support and concluded that it was not anything that they could solve on their end as the plugin works as expected until TeraWallet is activated.
Hi there,
Did you get any resolution to this problem? I’ve just encountered the same thing on our site: on updating our site, which included updating to a more recent WooCommerce Square plugin (4.5.1 from an earlier 4.x?) any orders placed using Square as a payment are stalling. After clicking the ‘place order’ button the page just ‘spins’ the order ball endlessly and nothing happens. Nothing appears to be logged from what I can see. I’ve done the usual testing with various plugins on and off, and it appears to be Terawallet. Deactivating Terawallet solves the problem. Reactivating it brings the problem back. We’re only using Terawallet (now 1.5.0) to store things like refund credit, we’re not actively using it as a wallet that users can charge/top-up etc. Current Woocommerce version is now 8.6.1. We’re currently having to rely on Paypal as an alternative payment method.Sorry to say that I did not. I have reached out via this forum, contacted support via email and created a thread on the WordPress plugin sites forum and have never heard anything regarding this. I am also only using TeraWallet to store credit and not using the additional features. Right now I am leaving Square at its compatible version (4.0) and currently looking into replacement plugins for TeraWallet since it has been ~6 months of this issue persisting with no support.
Yes, I’ve dropped a direct message to support as well, but not heard anything back. We’ve taken the decision to temporarily disable Terawallet, as having Square available for general order payment is far more important to us and I didn’t want to stay stuck on an older Square plugin. We were using TeraWallet only to support refunds, such as for cancelled orders or items etc, and allow customers to have their refund amounts held as store credit if they wanted (we’re a charity; people are nice like that and usually want to re-spend their funds with us), but for now we’ve just switched to refunding everything straight back to the payment method, and we’re now manually handling/adjusting orders for anyone with an outstanding balance. It’s a bit of a pain, and will be for a while – or until a fix, or until we find another solution – but luckily the numbers are manageable as balances were only ever for refunded orders which are only a small percentage of things. *sigh*. For those refunds where customers would like us to retain funds we’re considering issuing digital ‘gift cards’ instead (which we already have as a purchase option), but it’s a few extra admin steps.
Hi,
We fixed this issue in our GitHub repository with commit 762dad5. And will upload the fix to our next plugin update to the WordPress plugin directory. For the time you can download the updated plugin from our GitHub repository.
- You must be logged in to reply to this topic.
